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.

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. The governor will periodically post summaries of these advisory findings. It's crucial not to close this issue as it's intended to be a continuously updated document.

The user is expressing frustration and exhaustion ('力竭了') because they are unable to break through or effectively utilize Notion AI's built-in prompts ('破不开 Notion AI内置的提示词'). They are seeking help ('help wanted') to overcome this challenge.

When adding a bank account, an error message changes after a network reconnect. The expected behavior is for the error to remain consistent, but it appears to be different after the network is re-established and the user attempts to confirm again. This issue has been reproduced on both Android and iOS.

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.

The user is reporting an issue with JimuReport's MongoDB integration, specifically the inability to perform multi-field grouping. They've observed that the current implementation only supports the `find` syntax and fails when attempting to use `GROUP BY` with multiple fields via the `mongo.` syntax, leading to errors in Calcite's syntax parsing.

This issue requires the implementation of a custom C++ string class named MyString. The class needs to support various constructors, a destructor, and member functions for length, C-style string conversion, appending, and comparison. Additionally, it involves overloading operators for assignment, concatenation, equality comparison, and stream insertion, all while managing dynamic memory allocation and preventing memory leaks.

The "Show archived" button in eLabFTW is not functioning as expected, failing to display archived experiments. A workaround exists by manually navigating to a specific URL, and the issue may be related to API limitations on archived items.

The user is concerned that the decommissioning of MODIS (Terra and Aqua) will leave FORCE without a source for atmospheric parameter data needed for Landsat atmospheric correction. They are inquiring about plans to find and implement an alternative, suggesting Sentinel-3 as a possibility.

This issue proposes implementing a persistent on-disk cache for API-backed token counts from services like Anthropic and Gemini. This cache would store token counts keyed by tokenizer name, model, and tool fingerprint, preventing redundant API calls across different runs and improving performance, rate limit usage, and reliability. The cache needs to be safe for concurrent access, bounded in size, easily clearable, and gracefully handle corruption.

This issue requires replacing a single Bootstrap utility class (`p-3`) in the `FilterDateTime.vue` component with equivalent CSS using design system tokens. The goal is to remove all Bootstrap dependencies from the component and ensure visual consistency across light and dark modes, while also passing all relevant checks and tests.

This issue describes a potential database connection leak in the `BaseSQLDB.__aexit__` method. If the `commit()` operation fails, the connection's exit logic and the clearing of the connection variable are skipped, leaving the connection open. This could lead to subsequent connection attempts failing due to nesting assertions.

This issue seeks the creation of a reusable 'Sponsors Kit' to attract and onboard companies as sponsors for the WordPress Credits program. The kit should clearly communicate the program's value and encourage potential sponsors to take the next step, such as scheduling a call or submitting an application. The target audience includes decision-makers at companies within and beyond the WordPress ecosystem.

The current implementation of scrolling by a fraction in the browser adapter silently ignores out-of-range fraction values (outside 0-1) and instead performs a single step scroll. This leads to unexpected behavior and violates a rule requiring data loss to be reported. The expected behavior is to throw an error when an invalid fraction is provided, clearly indicating the acceptable range.

This issue outlines the migration of several modules (attribute_set, pim, product_attribute_set, product_attribute_set_list_view, website_attribute_set) to version 20.0. It provides a link to the OCA maintainer-tools wiki for migration guidance and a checklist for the modules that need to be updated.

When acquiring a lease on a URL that is different from the current URL of an existing leased tab, the system incorrectly reports the new URL but fails to navigate the tab. The tab remains on its old page, leading to a discrepancy between the reported state and the actual tab state.

The project maintainer confirms the project is still active, though maintenance is limited due to the original developer's other commitments. They encourage community contributions and offer opportunities for new maintainers to get involved.

The `jarl` linter incorrectly suggests replacing `any(is.na(x), is.na(y))` with `anyNA(x)`. This change breaks the functionality because `anyNA` only checks the first argument (`x`) and ignores subsequent arguments like `y`, leading to incorrect results when multiple `is.na()` calls are present.

This issue requests the creation of a no-account smoke test guide for the synthetic demo panel. The guide should walk first-time contributors through starting the demo, verifying image card appearance, testing various UI interactions like search, filtering, preview, pinning, and auto-select, and checking UI localization. It should also specify what to include in manual check notes, using only synthetic screenshots.

This issue requests the addition of a troubleshooting checklist to the installation guide for custom endpoints. The checklist should help users diagnose and describe issues with their custom endpoint setup before reporting a bug, covering client/plugin versions, endpoint functionality, API format, local engine ports, and necessary information for bug reports while emphasizing privacy.

This issue aims to improve keyboard accessibility for an image preview dialog by ensuring that the Tab and Shift+Tab keys keep focus within the dialog's interactive elements. The goal is to prevent focus from escaping the dialog and to maintain expected behavior for closing the dialog and interacting with its controls.

The `pythonversion` grain in SaltStack is structured as a list, which breaks the expected string or integer pattern for other grains like `osrelease`. The user suggests renaming the list variant to `pythonversion_info` and introducing a new `pythonrelease` grain, eventually deprecating `pythonversion` to maintain compatibility.

This issue proposes clarifying the documentation for the `safeParse` function. The goal is to accurately describe its behavior as a guard validation wrapped in a tagged result, rather than implying it performs actual parsing or transformation. This aims to differentiate it clearly from `safeJsonParse`, which does decode JSON text.

Tests are randomly failing in CI due to the teardown process being unable to remove temporary directories because something is still writing to them. This issue, characterized by an `ENOTEMPTY` error, occurs even when tests themselves pass and is not reproducible locally, suggesting a race condition or background process active under parallel CI load.

This issue proposes to make the simulated camera noise in uSim more physically realistic by applying Poisson noise based on beam current, exposure, and binning. Currently, the noise is unrealistically low, making simulations much cleaner than real detectors. An option will be added to reduce noise for fast tests that require clean images.

This issue aims to improve accessibility for icon-only buttons within the ChatInterface and VideoIngestionPanel components. The goal is to ensure screen readers announce the button's function rather than just 'button' by adding appropriate `aria-label` attributes and hiding decorative icons with `aria-hidden='true'`. The changes should not affect the visual appearance or structure of the components.

This issue proposes adding a visual indicator to support ticket previews within the Concierge chat to show the number of replies or if there are new comments. This aims to prevent customers from mistakenly replying in the main Concierge chat instead of the actual support ticket thread, improving user experience and reducing frustration.

This issue addresses accessibility concerns in the frontend by requiring the addition of `alt` attributes to `<img>` tags and accessible names (using `aria-label`) to icon-only buttons. The goal is to improve usability for users relying on screen readers by ensuring all interactive elements and informative images have proper descriptions.

This issue requires fixing TypeScript errors related to the `AssetType` definition in `types.ts`. The code in `ChatInterface.tsx` and `VideoGenerator.tsx` is assigning values not present in the `AssetType` union, and `ChatInterface.tsx` also attempts to access a `mimeType` property that doesn't exist on `ChatMessage`. The fix involves either updating the `AssetType` definition to include these values or modifying the code to use existing types, and potentially adding `mimeType` to `ChatMessage` if the data is present.

This issue requires fixing four TypeScript errors in `WorkflowNodes.tsx` related to the `NodeData` interface. The errors occur because the `@xyflow/react` library expects node data to be assignable to `Record<string, unknown>`, and an `interface` does not satisfy this. The solution involves changing the `NodeData` declaration to a `type` alias or an equivalent that meets the library's requirements, ensuring the node components still function correctly.