Find meaningful ways to contribute

A test in the `PerformanceCounterCategory_GetCounters` test suite is failing on an ARM64 Windows build. The error indicates that a required performance counter category, 'PerformanceCounterCategory_GetCounters_Category', does not exist, suggesting a potential race condition or setup issue during test execution.

Users are encountering a persistent "Are you enjoying New Expensify?" pop-up that repeatedly reappears after dismissal, preventing them from accessing the application. This issue is reproducible on both web and mobile platforms, and standard troubleshooting steps like clearing cache or signing out have not resolved it.

This issue proposes a new feature: a translation glossary for models with large context windows. The glossary would allow users to define specific word replacements and provide translation context, potentially improving terminology accuracy. The suggestion includes a user-configurable tab in settings for managing the glossary.

The user is reporting that their correctly written code for step 30 of the "Learn Tree Traversal by Building a Binary Search Tree" curriculum is failing the tests. They have provided a link to a forum post for further context and suggest that the tests themselves might be the issue.

This issue addresses two related problems in the project's test suite. First, a test that checks for database provider documentation citations can become vacuously true if no citations are found, leading to a false positive. Second, seven provider documentation files incorrectly cite a specific line number within `factory.ts` for the `createDatabaseProvider()` function, which has changed.

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 proposes refactoring a large `server.py` file (6.2k lines) into a more modular structure. The goal is to separate routing logic from domain-specific API handlers, improving maintainability and reducing change risk. The refactoring will be done incrementally, ensuring no behavioral changes and leveraging existing tests.

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 proposes adding internationalization (i18n) support to dayGLANCE, starting with German. The goal is to enable UI translations by integrating an i18n library, extracting hardcoded strings, implementing locale detection, and adding a language switcher. The initial German translation will be included.

This GitHub issue announces a challenge to rigorously test the mathematical reasoning capabilities of the Spark-X2.5 language models. Participants are required to download the models, conduct evaluations on math benchmarks or specific problem types, and publish their reproducible results on Hugging Face Discussions. Submissions are open from September 7th to September 13th, 2026, with judging and awards following.

This issue is a beginner-friendly task to add a new Japanese idiom to a JSON file. No coding is required, and the contribution can be made directly from the browser in under a minute. It's designed for first-time open-source contributors and is part of a Hacktoberfest initiative.

The user reports that the Checkstyle Eclipse plugin (version 8.12.0) does not correctly handle formatting for lambda expressions. Specifically, the 'LAMBDA' token is not being processed by the code formatter transformer, leading to incorrect brace placement for lambda bodies. The user suggests a specific code addition to resolve this issue.

Users are reporting a regression in OpenMPTCProuter v0.64.1 where the MQVPN tunnel fails to establish, resulting in the 'tun0' interface not being created. This issue occurs even with identical configurations that worked on v0.63, and despite the router being able to reach the VPS and validate UDP traffic.

A critical health check endpoint for the docs site was defined but never implemented with alerting. This means production outages due to issues like missing content volumes would go unnoticed, impacting users. The recommendation is to create a scheduled workflow that polls this endpoint and opens an issue on failure.

An automated weekly check identified 838 dead or unreachable source URLs in the CCTV camera database. These URLs, which point to product pages or official OEM sites, are returning errors like 404 (Not Found), 410 (Gone), and 403 (Forbidden). The issue requires re-sourcing these URLs to working alternatives, preferably official ones.

The Maka application is crashing due to a "Minified React error #185". The user is unable to provide specific steps to reproduce the issue, but has provided detailed environment information and a diagnostic report. This error typically indicates a problem with how React components are being rendered or updated.

This issue proposes adding support for generating CSV on the Web (CSVW) metadata, which describes CSV files and their schemas. The goal is to enable better integration and understanding of tabular data by providing a standardized way to define CSV structures and relationships, including single and multi-table scenarios.

This issue highlights a significant gap in the project's roadmap, identified by three converging adopter demands for per-repository scoping of policies. Currently, policies are hive-wide, leading to operational inefficiencies and potential incoherence as these demands are addressed independently. The proposal is to treat 'per-repo policy scoping' as a single roadmap theme to ensure a unified design.

The Maka Desktop application is crashing when using the grok-4.6 model. The crash is identified as a 'renderer_crash' and is linked to a minified React error (#185). This suggests a problem within the application's user interface rendering logic, potentially related to how the grok-4.6 model's output is being processed or displayed.

This issue requests the implementation of a drag-and-drop functionality for adding files. The goal is to improve user experience by providing a faster and more convenient alternative to the traditional file selection method.

This issue describes a bug where Claude Code's `tool_result` entries without explicit token counts are estimated based on character count. This estimated count is then billed separately, leading to double-counting of usage that has already been accounted for in the next assistant turn's input tokens. The fix needs to be applied in the `tokscale-core` repository, not the current one.

This issue proposes implementing auto-scrolling functionality for the canvas when a user drags a 'brick' to the edge. The goal is to enhance the user experience by allowing continuous dragging across the canvas without manual panning, by detecting when the dragged item is near an edge and initiating viewport scrolling.

The user is proposing a new feature to add clipboard history for images. They suggest two potential implementation approaches: integrating image history with existing text clipboard history or creating a separate prefix for image history, with a preference for the latter due to better discoverability and preview capabilities.

There's an inconsistency in the liveness/readiness endpoint path across different parts of the application. While the server route and architecture docs specify `/health`, the web UI, server README, and API client expect `/api/health`, leading to 404 errors when the web UI tries to access the health endpoint.

When tracking GPS distance for an expense, resuming tracking while offline and then reconnecting to the internet does not update the map to the user's current location. The map continues to display the old location, even after walking a few meters offline and restoring connectivity.

This issue proposes to de-duplicate the `AGY_PUBLIC_MODELS` and `ANTIGRAVITY_PUBLIC_MODELS` lists, which are currently maintained as separate, identical copies. This duplication leads to redundant maintenance and potential for drift, as evidenced by their identical content for over a month. Consolidating these lists will streamline updates and prevent inconsistencies.

This issue addresses the truncation of feature flag descriptions on the settings page, where they are limited to two lines, hindering usability for administrators. The proposed solution introduces a "On hover / Full text" control in the header, allowing users to either see full descriptions on hover or always display them, with the preference persisted in localStorage.

When navigating back from an expense report on staging.new.expensify.com, the scroll position is not maintained, and the user is returned to a different, earlier scroll position. This issue occurs when an account has more than 50 reports and requires users to manually re-scroll to find their previously viewed report.