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.

A hive instance encountered a runtime error where all references failed a freshness check, preventing it from proceeding. This issue is being reported across the fleet to consolidate similar defects.

This issue is a call for community contributions to integrate AVA's data analysis and visualization capabilities with other tools. It encourages developers to share existing integrations, contribute code, testing, examples, and documentation, or propose new ideas for integrations.

This security issue, currently blocked by another PR, concerns how `parkText` processes untrusted comments. It allows non-hive commenters to potentially influence which cross-repo PR patches are fetched and can lead to a `/fixed` offer being presented based on manipulated text. While the impact is limited, a fix is needed to prevent this manipulation.

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.

When resizing the browser window after opening a context popup in the Wallet settings, the popup does not reposition correctly. This issue has been reproduced on Windows and MacOS Chrome and Safari browsers.

When approving expenses in a report, the total incorrectly includes held expenses alongside approved ones. The total corrects itself only after the user clicks on an approved split expense and then navigates back to the report. This bug was reproduced in both staging and production environments.

This bug report identifies a division-by-zero error in the `shortest_distance_to_arc()` function when arc endpoints are identical or antipodal. The function attempts to normalize a zero-magnitude cross product, leading to NaN values that corrupt further calculations. The expected behavior is to explicitly handle these degenerate cases to prevent NaN propagation.

The user is inquiring about the status of a CVE ID for a previously fixed XSS vulnerability (GHSA-6q59-m6vq-x65x). They want to add this to their profile for identity verification and noticed that a CVE was requested but not yet listed on the advisory. They are asking for an update on whether a CVE has been assigned or is still pending.

This issue proposes a new architecture for underwater robot simulation, prioritizing MuJoCo (via URLab) for physics and HoloOcean for visuals, while deprecating the AirSim ROV route. The core task involves integrating the 'underwater' components with CarlaUE4, ensuring MuJoCo handles all physics and Unreal Engine focuses on rendering and sensors. Key steps include resolving URLab's compilation issues, verifying its functionality with specific models, and addressing potential conflicts and coordinate system mismatches with other plugins.

This issue addresses numerous "not wrapped in act" warnings in frontend Vitest tests, indicating that state updates are occurring after assertions. The proposed solution involves explicitly waiting for these updates within the tests using methods like `findBy`, `waitFor`, or `act` to ensure accurate test results and prevent hidden asynchronous bugs. The goal is to fix these warnings by properly wrapping asynchronous operations in 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.

The Microcks project is migrating its website from Hugo to Docusaurus and Netlify to improve maintainability and developer experience. A temporary preview site is available for community validation and feedback.

This issue tracks the integration of llm-d deployments into k8s-aibom. Part 1, already merged, adds support for `DisaggregatedSet` which is used on NVIDIA hardware. Part 2, planned for v1.7, will incorporate `InferencePool` membership as a routing fact to accurately represent llm-d's model deployments.

This issue describes a "Maximum update depth exceeded" error occurring in the `useSidebarOrderedReports` hook on the web platform, specifically when users are on the `/search` route. The error is suspected to be caused by a state update loop within a `useEffect` hook that copies `reportsToDisplayInLHN` to state, while a memoization hook intentionally omits this state from its dependencies. This suggests that other dependencies of the memo are changing identity on every render, triggering the loop.

This issue reports a problem where bitmap images, specifically black and white topographic maps, are not displaying correctly. While a workaround exists by converting images to RGB or grayscale, the core issue requires a proper fix.

This issue proposes migrating existing NumPy testing assertions from `assert_almost_equal` to the recommended `assert_allclose` function. The goal is to improve the consistency of floating-point comparisons in the project's test suite. A detailed to-do list outlines the specific steps required for this migration across test files.

This bug report indicates that comparisons using the `==` operator with a fixed number in the CMS are always evaluating to false. This is because the number is being published as a string (e.g., `== "10"`), and the Liquid templating engine does not automatically convert strings to numbers for comparison. A potential fix involves checking the type of the field on the left side of the comparison and publishing numeric literals without quotes if the field is also numeric.

This issue aims to verify and document KiviDB's compatibility with popular AI frameworks like LangChain, LangGraph, LlamaIndex, LiteLLM, and Mem0. The process involves creating compatibility harnesses to test KiviDB against each framework's Redis integration, publishing the results, and contributing documentation and examples to the respective projects.

KiviDB's command-line interface incorrectly refuses several directives that are accepted by its configuration file and are commonly used with Redis. This prevents users from starting KiviDB with standard Redis command-line arguments, causing failures in environments like Dify's tests and Docker Compose setups.

The `INFO commandstats` command in KiviDB (and potentially other Redis-compatible databases) fails to count the `WATCH`, `UNWATCH`, and `HELLO` commands. These commands are functional but are not being recorded in the command statistics, leading to an incomplete view of command usage.

The OTP device picker in Keycloak's v2 login theme is not keyboard accessible or operable. Users relying on keyboards or screen readers cannot select an OTP device if they have multiple registered, as the current implementation uses non-focusable divs instead of native form elements like radio buttons. This violates WCAG 2.1.1 and 4.1.2 standards.

The InstCombine pass in LLVM is missing an optimization for the `log(exp10(y))` pattern when `exp10` is used as an intrinsic. Currently, this optimization only applies to the libcall version of `exp10`, not the intrinsic. This issue requires adding support for the intrinsic version to the existing simplification logic.

YouTube has implemented a change that prevents desktop users from posting GIF comments, resulting in various error messages. This issue appears to be server-side and not related to user installations, browsers, or VPNs. The maintainer is seeking community assistance to identify a solution.

This issue requests the addition of native Zoo Code Go configurations for three newly listed OpenCode Go models: LongCat 2.5 Preview Free, Step 5 Preview Free, and Space Bunny. Currently, these models lack specific configurations, leading to generic settings and unclear pricing. Adding these configurations will ensure their displayed settings and costs accurately reflect the gateway's offerings.

The user is reporting an issue where thermostat parameter changes made through the EMS-ESP UI or Home Assistant are not being correctly applied to the physical thermostats when the heat pump is in cooling mode. However, changes made on the physical thermostats or the Bosch app are reflected correctly in EMS-ESP.

This enhancement request aims to prevent contributors from being directed to issues that are already assigned. The proposed solution is to modify the issue extraction logic to exclude assigned issues from the search results, leveraging GitHub's search API capabilities. This change will improve the contributor experience by ensuring they are presented with genuinely available tasks.

This issue requests to stop reporting a specific `IllegalArgumentException` related to Termux integration in crash reports. The exception is considered noise because it's user-actionable, affects highly technical users, and the developers cannot directly fix it. The proposed solution involves verifying the exception is shown to the user, adding a regression test, and filtering the exception before it's sent to ACRA.

This issue requests the addition of unit tests for the `BackfillBanner` Vue component. The tests should cover various scenarios related to progress calculation, button visibility based on the `paused` state, and ensuring that the pause, resume, and stop buttons emit the correct events.

The `extract_issues_by_user` function in `IssueManager` incorrectly limits the GitHub Search API results to 100 issues per organization. This prevents the retrieval of all 'good first issues' when an organization has more than 100. The fix involves implementing pagination to fetch all available issues up to the API's limit of 1,000.