Find meaningful ways to contribute

This issue proposes the creation of a validating webhook for the Burrito project. The webhook will be responsible for validating resources before they are applied, specifically focusing on the `remediationStrategy` enum and complex interactions between various options.

This issue requests the implementation of a new Git provider for Bitbucket. It specifically mentions building upon the new structural changes introduced in a recent pull request, indicating a need to integrate with an existing framework.

This issue proposes adding a new configuration setting to the Burrito tool. This setting would prevent Burrito from executing 'apply' operations if the 'plan' output indicates that any resources are scheduled for destruction. The goal is to enhance safety and facilitate adoption on critical Terraform code by preventing accidental resource deletion.

This issue is a beginner-friendly task to add a new fun fact about Japan to a JSON file. No coding is required, and the contribution can be made directly from the browser in under a minute, making it ideal for first-time contributors and Hacktoberfest participants.

This issue proposes improving the error message for first-time users encountering a CORS (Cross-Origin Resource Sharing) error. Currently, the error is only visible in the browser's developer console (F12), which can be confusing for new users. The request is to provide a more direct and user-friendly explanation within the application itself, including potential workarounds.

The documentation for v6 runs states that owners can reset or abandon escalated stages, but the implementation lacks an 'abandon' route. The 'reset' functionality is also limited, only allowing movement strictly backwards in stages, which is not possible for spec-stage runs. This leads to escalated leases being kept alive indefinitely, with 'triage_fix' being the only, undocumented, recovery option for spec-stage runs.

This issue describes a conflict in REST API path definitions for the tracker service. Specifically, connection-scoped paths like `/v1/tracker/{username}/{connection}/routes` are shadowing the general connection retrieval path `/v1/tracker/connections/{username}/{name}` when a connection is literally named 'routes' or 'issues'. This makes it impossible to access connections with these specific names via REST.

This bounty seeks to establish an end-to-end test for the `copperhead create` pipeline, which generates manufacturable KiCad artifacts from a natural-language brief. The goal is to automate the entire process, fix any blocking issues encountered during a full run, and provide automated coverage to prevent future regressions.

This issue requires documenting why the `atlas/bench` tool intentionally uses a neutral-scoring lens path. The documentation should explain that this path is necessary for benchmarking models that lack a lens bundle and is never used in production, preventing confusion for users familiar with the lens requirement.

This issue proposes to remove two unused development dependencies, `tsx` and `rimraf`, from the project's `package.json`. The functionality of `rimraf` will be replaced with Node.js's built-in `fs.rmSync` function, simplifying the build process and reducing the number of dependencies.

This issue seeks to re-evaluate the 'changed-file-intersection' gate within the `pr-auto-update.sh` script. The goal is to decide whether to keep, modify, or remove this gate, considering its impact on avoiding churn versus potentially delaying necessary updates for PRs that fall behind their base branch. The decision should be made after observing the performance of a new marker-driven re-run feature.

The v6 CI pipeline is failing due to merge conflicts when backporting a fix from v5. The conflict arises because the same fix was already applied to v6 with slightly different content, causing the automated merge to fail. A human intervention is required to resolve these conflicts by prioritizing the v6 version of the code and documentation.

This issue requires CNCF Hive maintainers to link their GitHub handles to their Linux Foundation IDs (LFID) via openprofile.dev. This is a prerequisite for provisioning service access and ensures CNCF can identify their primary email for project services. The process involves signing into the LFID, connecting GitHub, and verifying the primary email address.

This issue proposes making review bot settings, specifically `classification.review_bots` and `min_priority`, editable directly from the dashboard's Review card. Currently, these settings can only be modified by directly editing the project file on the host, which is inconvenient. The goal is to expose these settings in the API and UI for easier management, similar to other Review settings.

This issue serves as a central hub for advisory findings from Hive agents, particularly at lower ACMM levels where agents analyze code without creating direct issues or PRs. A governor agent periodically posts digest comments summarizing these advisory findings. This issue is intended to be a living document and should not be closed.

This issue reports several warnings from Renovate, including configuration issues, missing release timestamps, and package lookup failures. It also indicates that a specific dependency update for Konflux references has been manually edited and is now blocked from further Renovate changes.

This issue proposes adding a new lint rule to Deno that identifies and flags the use of `exports` or `module.exports`. The goal is to encourage developers to migrate from CommonJS module syntax to ECMAScript Modules (ESM) by providing helpful suggestions.

The user is encountering an installation error ('error curl 23, failure, cant open file /root/stream.py, errono 2') when trying to run `modmium.sh` on versions 152 and 150. While `quickinstall` appears to work, the system boots to OOBE without VT2 access after a restart, and recovery keys are also affected.

This issue proposes strategies to increase the visibility and reach of the 'first-contributions' project, which helps newcomers learn to contribute to open source. The goal is to find more effective ways to promote the project to individuals seeking guidance on starting their open source journey. Ideas can be shared in the comments, and successful promotions should be linked.

A bug exists where an issue can become label-less if all label projections fail, leading to a second, unnecessary run. The system should either skip or retry labeling until successful, or a human intervenes, and the design documentation needs to be updated to reflect this behavior.

This issue is a simple request for community feedback on the usage and interest in a feature called 'FNCache'. The author is trying to gauge adoption or interest levels without providing technical details.

This issue proposes creating a new documentation page for AI/SRE agents that will include an evaluation checklist. The checklist will guide users on how to pair the MCP endpoint with a Prometheus reporter and demonstrate real investigation scenarios, clarifying the distinction between instance MCP and hosted MCP.

This issue requests adding unit tests to cover specific scenarios for the `flattenMenuItems` function in the Kestra UI. The goal is to ensure that nested menu items are correctly flattened and handled, preventing issues in the sidebar customization dialog. The tests should cover various nesting depths, empty children arrays, and empty menus.

This issue proposes moving the application's tabs to occupy the title bar space, similar to applications like Brave and Telegram. The user believes this would be a better use of screen real estate and suggests it could be an optional feature, as it was previously implemented before being removed in a previous PR.

This issue is a beginner-friendly task to add a common Japanese learner mistake to a JSON file. It requires no coding and can be completed in under a minute by forking the repository, editing the specified file, and submitting a pull request.

Production workers running Kubernetes plugin tasks are experiencing a thread leak, leading to OutOfMemory errors after approximately 24 hours. This is characterized by an excessive number of threads, many stuck in a TIMED_WAITING state, and orphaned executor pools. The issue appears to be specific to the `PodCreate` task, with evidence pointing to an asynchronous executor within `PodLogService` not being fully terminated.

This issue requests the addition of a Job DSL extension to configure folder-level Jira sites using code. Currently, only global Jira sites can be configured via Configuration as Code (JCasC), while folder-level sites require Groovy init scripts. The proposed solution involves creating a Job DSL extension that allows defining Jira sites within a folder's properties in a `jobs:` script.

The `docker-compose.yml` file incorrectly hardcodes `DB_TYPE` and `ARTIFACT_SERVICE`, overriding `.env` settings and forcing SQLite and Supabase respectively. It also mandates a `DB_PASSWORD` even when not needed for SQLite, causing unnecessary failures during `docker compose up`.

This issue highlights three discrepancies between the dashboard's UI and its actual functionality. Specifically, the "hallucination" check is mislabeled as a "stub," the "throttle" option for rate limits incorrectly implies it delays all types of limits when it only affects per-minute requests, and a Serbian sentence appears on an English dashboard page. The proposed fixes involve updating UI text, adjusting functionality, and translating the Serbian sentence.

The agent server is incorrectly started using the system's 'python' command from the PATH, rather than the specific Python interpreter running the authentication server. This leads to `ModuleNotFoundError` when the agent server tries to import modules within the virtual environment, causing chat failures while the auth server continues to run.