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.

On iOS and Android, images uploaded to chats appear broken immediately after sending due to a race condition. The temporary file used for upload is deleted before it can be copied to the local attachment cache, causing a cache miss. This results in the image displaying as broken until the chat is refreshed.

This issue aims to standardize the "Back" caret header behavior within the onboarding flow. Currently, the header's animation and position are inconsistent across different onboarding steps. The proposed solution is to create a reusable, sticky header component, similar to `InteractiveStepWrapper`, to ensure a consistent user experience.

This issue proposes creating a constant for the string "(unset)" which is currently used as a literal in multiple places to represent null values in the config pane. This will improve maintainability by centralizing the definition of this sentinel value and prevent silent failures if the string is changed.

This issue involves removing the `Onyx.connect()` call for `ONYXKEYS.SESSION` within the `ClearReportActionErrors.ts` file as part of a larger deprecation effort. The task requires refactoring the relevant methods using Test-Driven Development (TDD), ensuring tests pass after the changes, and then reducing ESLint warnings.

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.

On iOS, users are unexpectedly logged out after pasting a verification code when attempting to add a work email that is not associated with an existing account. This bug occurs during the onboarding flow and has been reproduced in both staging and production environments.

This issue highlights outdated documentation that still directs contributors to use the 'v4' branch as the active development branch. Several files, including CONTRIBUTING.md, docs/development.md, docs/getting-started-contributing.md, and manual-provisioning.md, need to be updated to reflect that 'v5' is now the default and active development branch, and 'v4' is feature-frozen.

This issue proposes adding a new CI job to test Wagtail's publishing and search indexing functionality. The job will use a Python driver to simulate creating and publishing a page, then verify that the search index is updated correctly by the `django-tasks` backend. This aims to ensure the integration between Wagtail's publishing workflow and its search indexing is robust across different Django and Python versions.

This issue proposes to enhance the error handling for subdomain issue creation. Instead of failing silently or logging an error when an issue cannot be created in a target repository, the system should post a comment on the most recent pull request in the js.org repository for that subdomain, informing the maintainers about the issue.

The BinanceFeed in the SDK does not normalize the case of cryptocurrency symbols when fetching or watching tickers. This leads to requests silently hanging and timing out if the provided symbol's case does not exactly match the canonical uppercase format, unlike the ChainlinkFeed which correctly handles case normalization.

The documentation for security credentials incorrectly states that the Limitless venue only supports raw private keys. In reality, Limitless offers a delegated-signing mode using API keys and secrets, which does not require a private key.

The documentation for the `fetchMatchedMarketClusters` method in `docs/router/prices.mdx` is incomplete, listing only 4 out of approximately 16 available parameters. The issue highlights that the SDKs implement a much larger, fully functional parameter set for this method, which is also documented for a similar method (`fetchMatchedEventClusters`) on a sibling page, indicating a clear documentation gap.

This issue, part of a larger RFC for standby contributors, focuses on implementing manual dispatching of queued items or entire lanes to qualified standby contributors. It requires integrating dispatch controls into the dashboard and chat interfaces, ensuring proper gating and labeling of dispatched tasks, and depends on prior steps of the RFC being completed and verified.

This RFC proposes a new "standby contributor" system for Hive v6. When a hive owner runs out of budget tokens, their paused task queue will be offered to pre-approved volunteers. These volunteers can then run tasks on their own machines using their own models, preventing queues from growing indefinitely and ensuring that cheaper models don't silently replace higher-quality ones.

This issue seeks community input to define the first useful, domain-specific model Tapestry should build and release. The goal is a leading capability model (e.g., education, fraud detection, industrial AI) that is customizable, deployable, and trustworthy, likely built upon existing open bases rather than trained from scratch.

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 addresses a discrepancy in the #7721 plan following an emergency cut-over on 2026-09-21. Key steps like operator announcements and dual-version exercises were missed or became moot due to channel remapping and an immediate stable promotion. The goal is to update the tracking system to reflect the actual state of affairs and provide a post-hoc notice to self-hosted operators.

This is a bounty issue seeking reports of accessibility problems on the BoTTube UI. Contributors are asked to identify issues related to contrast, screen reader compatibility, and keyboard navigation, with a reward of 1 RTC for each valid report. The issue is tagged as 'good first issue' and 'easy', indicating it's suitable for beginners.

This issue serves as a tracker for v6 readiness, ensuring that specific criteria are met before v6 is considered ready. It outlines a checklist for channel binding, guard-invariant conformance across various communication surfaces, and live exercise of these surfaces, referencing existing PRs and documentation for evidence.

The user is encountering a `KeyError` when trying to load the Qwen3-Next-80B-A3B-Instruct-AWQ-4bit model, which is an AWQ-quantized Mixture of Experts (MoE) model, using the latest SGLang Docker image. The error suggests a mismatch between the expected model architecture and the keys in the provided checkpoint, specifically during the weight loading process.

The user is requesting a change to how `keyboard_post_init_user()` is implemented in the fork. Currently, many keyboard configurations directly define `keyboard_post_init_user()` and call a separate `kb_keyboard_post_init()` function. The user proposes modifying these to use the `keyboard_post_init_kb()` pattern, which then calls `keyboard_post_init_user()`, allowing for user-defined overrides as intended by the QMK documentation.

A Go program compiled with ThreadSanitizer for the s390x architecture failed to allocate memory when run within QEMU. The error indicates a failure to allocate 8MB of memory, suggesting a potential issue with memory management or resource limits in the QEMU environment for s390x.

This issue proposes improvements to the filter dialog in AntennaPod. The main suggestions are to remove the 'confirm' button as filtering happens in the background, and to reposition and visually distinguish the 'reset' button to avoid confusion with standard dialog buttons. The goal is to enhance user experience and consistency.

This issue highlights dependencies in the Pulsar-Native repository that Renovatebot has identified as potentially abandoned due to a lack of recent updates. It provides a list of 19 such dependencies, along with links to their respective repositories and last updated dates, and suggests consulting Renovatebot's documentation for more information.

Translators are encountering issues when attempting to edit images containing text within the platform's built-in SVG editor. This bug prevents proper translation of image-based content, forcing a cumbersome workaround using external tools like Figma. The core problem lies in the SVG editor's inability to reliably handle text elements during the translation process.

This issue addresses multiple bugs in the `vista deploy` command, specifically related to how it handles static hosts and platform adapters. The goal is to fix deployment failures across various platforms like Cloudflare Pages, Vercel, Netlify, and Render, ensuring correct file generation and server configurations.

This issue proposes implementing support for Gateway API's HTTPRoute timeouts in NGINX Gateway Fabric. It involves mapping the `timeouts.request` and `timeouts.backendRequest` fields from the Gateway API specification to appropriate NGINX configurations, as existing NGINX timeouts do not fully align with the API's requirements.

This issue is a beginner-friendly task to add a new Japanese haiku to a JSON file. It requires no coding and can be completed in under a minute directly from the browser by forking the repository, editing the specified JSON file, and submitting a pull request.