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 addresses how to render live React demos for Sistent documentation within a Hugo site. The current approach uses Hugo for prose and aims to integrate React components for interactive demos, exploring options like React islands via Hugo's `js.Build` or maintaining a separate React app. A spike is recommended to evaluate the impact of integrating React components on bundle size and build times.

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 identifies several accessibility problems in the Alby browser extension, primarily related to missing labels and keyboard navigation. The user found that elements like the balance display, recent transactions, QR codes, and transaction amounts are not properly labeled for screen readers. Additionally, some interactive elements, such as transaction type tabs and dropdowns, are not fully navigable with a keyboard, hindering accessibility for users with disabilities.

Users have requested more information about recommended Lightning Service Providers (LSPs) to aid in comparison. Currently, only basic details like name, logo, and channel limits are visible, with channel cost only appearing after an extra click. The goal is to display more comprehensive information upfront, including channel costs if technically feasible.

The bill history feature on the website is displaying raw HTML tags within the bill descriptions, which are scraped from an external legislative website. This occurs because the legislative website sometimes includes HTML in its history entries, and these tags are not being properly sanitized or rendered before being shown to the user.

A severe performance regression has been introduced in recent commits, posing a significant blocker for the upcoming release. The team plans to use a binary search approach on the commit history to pinpoint the exact commit causing this performance degradation.

This issue describes a dependency conflict where multiple crates require different versions of the `ndarray` crate. To resolve this, the team forked the `sprs` crate to enforce a specific `ndarray` version. The ongoing challenge is to regularly merge upstream changes into the forked `sprs` or find a more sustainable solution.

This issue proposes adding support for indefinite sums and products, which are generalizations of discrete integration and exponentiation. The goal is to enable symbolic computation for these operations, similar to existing libraries and concepts found in mathematical literature and online calculators. This enhancement would expand the library's capabilities for numerical and symbolic analysis.

This issue requests the translation of the AquaScope README's quickstart guide into Chinese, French, or Japanese. The goal is to make the documentation more accessible to a wider audience by providing localized content for installation and initial examples. Contributors are asked to pick one language per pull request and ensure the translations are linked from the main README.

This is a meta-issue serving as a central tracking point for all bug fixes and security patches specifically for the v2 branch of the project. It's intended to consolidate ongoing maintenance efforts for that version.

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 issue requests documentation for edge cases related to the admin router in version 2 of the project. The goal is to improve reliability and usability by identifying and documenting these specific scenarios, potentially with accompanying tests if user-facing behavior is affected.

This issue proposes exposing observability features within the admin router (v2) to enhance project reliability and usability. The goal is to implement this change without affecting existing functionality and to include relevant tests or documentation if user-facing behavior is impacted.

This issue tracks the ongoing development and optimization of batch invariant feature for LLM inference, building upon existing work. Key tasks include integrating various hardware and software optimizations like Flashinfer, DeepGEMM, Torch compile, and Cuda Graph support, as well as improving usability and documentation. Some aspects, like FLASHINFER_MLA support and further performance optimizations, still require community help.

Marking a chat as unread fails to persist due to two distinct bugs. On iOS, the client immediately re-reads the chat, undoing the unread status. On desktop, the client fails to receive the unread update from the server, causing it to display stale read status.

A hive instance reported an `unclassified_error_repeated` runtime error related to an `automerge sweep skipped PR`. The error indicates that a base refresh merge guard prevented a merge due to a destination merge already being in progress.