RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), GitHub, YouTube, LinkedIn, and Amazon. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[Kubeflow] Add terminationGracePeriodSeconds to PodSpecPatch in TrainJob

Add `terminationGracePeriodSeconds` field to `PodSpecPatch` to allow users to configure the pod termination grace period per TrainJob via `RuntimePatches`.

Original Source

@@efazal | 2 pts | 3/9/2026

## What you would like to be added? Add `terminationGracePeriodSeconds` field to `PodSpecPatch` so users can configure the pod termination grace period per TrainJob via `RuntimePatches`. > **Depends on:** #3199 (`RuntimePatches` API) must be merged first. Currently, `PodSpecPatch` (introduced in #3199) supports these fields: - `serviceAccountName`, `nodeSelector`, `affinity`, `tolerations`, `volumes`, `initContainers`, `containers`, `schedulingGates`, `imagePullSecrets`, `securityContext` But it does not expose `terminationGracePeriodSeconds`, which is a standard `corev1.PodSpec` field. The field already exists in the TrainingRuntime CRD as part of the full embedded `corev1.PodSpec` (e.g., line 7507 in `trainer.kubeflow.org_trainingruntimes.yaml`), so runtime authors can set it. However, users cannot override it per-TrainJob. Proposed API change in `pkg/apis/trainer/v1alpha1/trainjob_types.go`: ```go type PodSpecPatch struct { // ... existing fields ... // terminationGr

Discussion

Loading comments...