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 mobile viewports, longer Table of Contents (TOC) links within the Layer5 Community Handbook are clipped and unreadable. This occurs because the text overflows its container instead of wrapping. The expected behavior is for all TOC links to be fully visible and wrap appropriately on smaller screens.

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 requests the ability to rotate shapes independently for each frame in an animation. Currently, all frames share the same rotation, limiting animation possibilities. Implementing this would allow for more dynamic and varied shape movements over time.

The developers are seeking testers with LG TVs running webOS 5 or newer to test a "URI mode" for media playback. They need to determine if this mode can successfully bind the video plane from a native app on these newer webOS versions, which could potentially enable playback of formats currently unsupported by the buffer-feed method. Testers will need a rooted TV to run debug builds and provide event logs.

This issue requires developers to verify and update a list of migrated developer guides against the current codebase. The task involves checking all mentioned code elements (functions, classes, routes, etc.) within each guide, fixing discrepancies, and adding missing information. The goal is to ensure the guides accurately reflect the code and that the documentation generation script passes.

This issue requests the addition of component tests for four specific dialog components that currently lack test coverage. The goal is to ensure these dialogs correctly trigger their associated actions, handle validation, and manage their closing and cancellation logic, following established testing patterns within the project.

This issue requests an update to the documentation for Biome, specifically to add missing rules to the rule-data. The goal is to ensure the documentation accurately reflects all available Biome rules.

This issue requests help to publish the 'CutVoke' project to the official MCP Registry. This involves creating an MCPB bundle, adding a `server.json` file to the repository, and documenting the publishing process. The goal is to make CutVoke more discoverable and installable from various clients and directories that rely on the registry.

Users can accidentally drag and drop BibTeX files into an open library in JabRef, which can be difficult to undo, especially for large files. The proposed solution is to implement a confirmation dialog that appears when a BibTeX file is dragged into the current library, preventing accidental imports.

This issue proposes integrating an error tracking service like Bugsnag into the project. The goal is to improve the ability to identify, diagnose, and resolve bugs by automatically capturing and reporting errors.

The generated backend code for a new project incorrectly defaults to port 3000 in `src/index.ts`, despite `service.json`, Dockerfile, and `flisk networks` all correctly specifying port 4000. This discrepancy causes confusion and potential development server conflicts, as the CLI output and tooling expect port 4000. The suggested fix involves updating the backend template to use the configured port as the fallback.

This issue describes a performance problem where moving or importing many curves in the application is significantly slower than handling the same number of polylines, with performance degrading quadratically as the number of curves increases. The suspected cause is inefficient point comparison during movement and sequential processing of curves during import and kernel operations.

The `skein.Run` function currently does not return `ErrStopped` when a run is fenced by a stop command, leading to stopped swarms being indistinguishable from completed ones. This issue aims to fix this by ensuring `skein.Run` returns `ErrStopped` in such scenarios while still providing the report with the correct `Stopped` status.

The initial `flisk up` command for the SaaS starter fails because the `billing-api` Docker image build cannot find the `prisma-cli` directory, despite it being created in a previous step. This appears to be a race condition within the BuildKit cache, where one of two identical Prisma backend builds succeeds while the other fails.

This issue proposes a privacy enhancement for the NWS integration in Home Assistant. Instead of sending precise GPS coordinates to the NWS API, the integration would locally resolve the device's location to nearby forecast and county zones. This local resolution would then be used to query NWS alerts by zone codes, significantly reducing the amount of location data shared with the third-party service.

The `AvgOf` function in the SQL Server dialect incorrectly truncates the average of an integer column, returning an integer instead of a float. This is because SQL Server's `AVG` function on integer columns returns an integer, unlike other databases. The proposed fix is to cast the integer column to a float before applying the `AVG` function.

The `Limit` and `Offset` functions in the query builder incorrectly accept negative values. This leads to inconsistent behavior across different databases, with SQLite treating negative limits as no limit, while PostgreSQL and SQL Server reject them. The proposed fix is to validate and reject negative values for `Limit` and `Offset` on all builders to ensure consistent database behavior.

The `anttest.Load` function incorrectly uses double quotes for identifiers in SQL INSERT statements. This causes syntax errors on MySQL and MariaDB, which do not use double quotes by default. The proposed fix is to use the database handle's dialect-specific quoting mechanism instead of a hardcoded double quote.

The current implementation for generating OpenTelemetry span names in `contrib/otel` incorrectly parses SQL statements, leading to malformed span names that include comments, newlines, tabs, and leading parentheses. This breaks span grouping and can introduce high-cardinality names. The proposed fix is to share a common helper function between `metrics` and `contrib/otel` to correctly extract span names.

The antvet tool incorrectly passes checks for certain API calls that involve non-probe pointers, leading to runtime errors. The issue stems from missing entries in antvet's internal tables that map API names to their expected pointer types. The proposed fix involves updating these tables and adding a test to prevent future omissions.

The system incorrectly allows two different fields to map to the same database column, leading to one field being silently ignored and potential errors during table creation. The fix involves detecting and rejecting such duplicate column mappings during schema building.

A medium-severity security vulnerability (CVE-2026-118764) has been identified in the minimatch library, specifically affecting versions between 7.0.0 and 11.0.0. The vulnerability allows for a denial-of-service attack through glob pattern amplification, leading to excessive resource consumption. The bun.lock file in this repository pins minimatch to version 10.2.6, which is within the vulnerable range, and requires an update to version 11.0.1 to be fixed.

A security vulnerability (GHSA-g3hv-75wg-m249) has been identified in the minimatch package, affecting versions prior to 11.0.1. This vulnerability allows for a denial-of-service attack through glob pattern amplification, potentially leading to excessive resource consumption. The fix involves updating minimatch to version 11.0.1.

This issue proposes a significant UI/UX overhaul for inline autocomplete suggestions, aiming to modernize their presentation and interaction to match standards set by platforms like Gmail Smart Compose and Cursor. The current implementation is described as a detached overlay with problematic caret positioning and aggressive dismissal, affecting both Lexical composer and textarea prompt inputs.

This issue is a placeholder for daily automatically generated morning reports. It serves as a repository for this information, with the label 'good first issue' suggesting it's intended for new contributors.

The user is requesting examples on how to create and retrieve SSH keys using the 1Password Terraform provider. They've observed that the API supports SSH key items and provided a `curl` example showing the structure of an SSH key item retrieved from the API.

The 'zizmor' CI check is failing simultaneously on 10 open pull requests in the projectbluefin/server repository. This widespread failure suggests a shared root cause, likely related to the base branch, a workflow configuration, a pinned GitHub Action, or the runner image, rather than individual code changes. The issue is being tracked centrally to address the underlying problem efficiently.

This issue proposes an enhancement to the contributor claim system. Currently, all contributors are limited to one open curated claim, regardless of their experience. The proposed fix allows 'returning' contributors (those with five or more merged pull requests) to hold up to two claims simultaneously, improving their experience and encouraging continued contributions.