Find meaningful ways to contribute

The user is reporting a bug in Storybook v7 RC8 where changing `globalTypes` corrupts the query parameters. Previously, they used base64 encoding for query params to avoid issues with standard URL encoding in v6, but this workaround is now failing after the upgrade.

The Storybook interactions panel incorrectly displays errors, showing them even when they are handled within the `play` function. This leads to an incomplete view of the interaction steps, as subsequent actions are not reflected in the panel after an error is caught.

This issue reports a compiler warning in the `pyrefly_util` crate regarding the use of a deprecated associated function `max_value` for `u32`. The warning indicates that this function has been replaced by the `MAX` associated constant. The fix involves updating the `define_index_type` macro to use `MAX` instead of `max_value`.

When switching between Storybook's Docs and Story views, components that rely on JavaScript referencing DOM element IDs break. This occurs because the Docs view appears to remove and re-render DOM elements, invalidating existing ID references, while the Story view does not. The provided StackBlitz example demonstrates this issue with an Accordion component.

The user is reporting that the app is not functioning on custom ROMs like Graphene OS due to a "CTS profile match failed" error, which is a result of SafetyNet checks. They suggest that the app should either bypass these checks on non-official ROMs or implement a more robust hardware-based integrity check, as SafetyNet is easily bypassed and not necessary for this type of application.

A user is encountering a "module not found" error when trying to import JavaScript files using the '@/' alias in Storybook 7 with Vue 3 and Vite. The issue suggests that these JS files are not being bundled or made available to the Storybook client, preventing their import.

This bug report describes an issue where Storybook fails with a cryptic parse error when JSX is used in a `.js` file, specifically within Storybook stories. The user found that renaming the file to `.jsx` resolves the problem, but the error message is unhelpful and led to significant debugging time. The request is for improved error messaging to guide users when encountering this situation.

A bug in @storybook/react-vite@7.0.0-rc.3 causes a "Failed to fetch dynamically imported module" error when an asset in `public` has the same path as an asset imported from `src`. This occurs because Storybook incorrectly serves an image file with a JavaScript MIME type, leading to a strict MIME type checking error in the browser.

This issue flags an unrelated one-line rewording in the `scale-envelope.md` documentation that was introduced during a merge resolution in PR #14989. The change is accurate and semantically identical to the original text, so it has no operational impact and requires no action.

A security vulnerability (CVE-2026-78661) has been identified in the `golang.org/x/net` library, specifically affecting the HTML parsing component. The issue arises from inefficient string concatenation that can lead to quadratic complexity when coalescing text nodes. A patched version is not yet available, requiring manual verification and monitoring for a fix.

This issue addresses a security vulnerability (CVE-2026-97045) in the `golang.org/x/net` library, specifically affecting the `examples/byo/echo/go.mod` file. The vulnerability relates to how raw text is rendered within HTML, potentially leading to incorrect namespace resolution. A patched version is not yet available, and manual verification is required to determine if the current pinned version is affected.

A security vulnerability exists in the Echo web framework's proxy middleware where it forwards attacker-supplied `X-Real-IP` headers to upstream services by default. This can bypass IP-based security controls like access control, rate limiting, and logging. The issue is present in versions of `github.com/labstack/echo/v4` between 4.0.0 and 4.16.2.

This bug report indicates that keyboard shortcuts for navigating between stories do not function when using composed Storybooks. The issue prevents users from seamlessly switching stories across different composed Storybook instances, hindering workflow efficiency.

A security vulnerability exists in the default configuration of the Echo web framework (github.com/labstack/echo/v4) where the rate limiter can be bypassed by spoofing the X-Forwarded-For header. This occurs because the framework trusts this header without validating its origin when no explicit IP extractor is set.

This issue proposes upgrading the Ruff linter to its latest version and enabling new rule sets focused on bug detection. The goal is to identify and fix potential issues related to mutable default arguments, blocking async calls, security vulnerabilities, logging format, code complexity, performance bottlenecks, and Ruff-specific warnings. The process involves updating configurations, running checks, and addressing reported issues.

A bug has been reported where the count of components and stories displayed in the UI is incorrect. This is due to the logic not properly excluding "docs types" when calculating these counts, leading to an inflated display. The issue was identified during QA and a minimal reproduction is being sought.

This issue proposes adding comprehensive tests for the database migration process in the `packages/core` module. The goal is to ensure that all historical schema versions can be upgraded successfully without data loss and that a failed migration correctly rolls back the database to its previous state. This addresses a gap in current testing, which only covers upgrades from an empty database.

This issue proposes upgrading the `tsconfig.json` modification logic within the Node version migration script. The current script predates the use of `ast-grep`, and the author suggests leveraging `ast-grep` for a more robust and flexible approach to updating `lib` fields, especially considering newer Node versions support more granular `lib` values.

This issue proposes making the `Name` field within the `PolicyReference` struct a required field in the Custom Resource Definition (CRD). It also suggests enforcing a minimum length for this `Name` field to ensure valid policy references are always provided.

This issue aims to internationalize the 4diac IDE by extracting user-facing strings from `plugin.xml` files into property files. This involves locating strings, generating property files, and configuring plugins to use them, with an optional bonus of harmonizing with existing Java string extractions.

The user wants Antumbra to prompt them about which partitions to flash when using a scatter file, similar to how SPFT behaves. Currently, Antumbra overwrites the preloader partition by default, which can lead to unintended consequences and wasted credits for users.

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.

This feature request aims to improve the user experience for operators managing multiple spokes from the hub. It proposes adding a "Pause hive" action directly to the context menu of each spoke in the hub's hive list, eliminating the need to navigate into each spoke's individual dashboard to pause it. This is a purely additive change that leverages existing pause functionality.

The WebUI currently fails to distinguish between a healthy idle session and a session that has permanently stalled due to provider errors. This lack of visual feedback prevents users from understanding why a session is unresponsive, leading them to resend messages or create duplicates. The issue highlights a missing display state for failed sessions, causing confusion and inefficient user workflows.

This issue requests the creation of a quickstart tutorial for the `perform_research` tool. The tutorial should guide new users from setup to achieving their first result within 10 minutes, including a runnable example, explanation of output, and common flags. It needs to be linked from the README and tested for end-to-end reproducibility.

This issue proposes adding a Docker Compose setup to simplify the evaluation of the server. The goal is to allow users to run a fully functional demo with a single command, reducing setup time and complexity. This involves creating a `docker-compose.yml` file, a sample project, and updating documentation.

This issue proposes adding a "Tool Spotlight" section to the project's README file. This section will highlight 5-6 high-value MCP tools with brief descriptions and runnable invocation examples to improve user discovery and adoption. The goal is to make it easier for users to understand and experiment with the most useful tools available.

This issue is a pull request to update the `rand` crate from version 0.9.2 to 0.10.2 in the `fsrs-rs` project. This is a standard dependency version bump, likely to incorporate bug fixes, performance improvements, or new features from the updated `rand` library.

This issue is a request to update the `rand_distr` dependency in the `fsrs-rs` project from version 0.5.1 to 0.6.0. This is a standard dependency version bump, likely to incorporate bug fixes or new features from the updated library.

This issue tracks the progress of getting the 'Vela' application to work with Android Auto across various Android installation methods and ROMs, including stock, GrapheneOS, and rooted devices. Different approaches like KingInstaller, AAEnabler, PlayInstaller, and Gearslip are being tested, with varying degrees of success depending on the phone's setup and the car's head unit.