Find meaningful ways to contribute

This issue is a "good first issue" that invites contributors to add a new Japanese idiom to a JSON file. The task involves no coding and can be completed directly in the browser by forking the repository, editing the specified JSON file, and submitting a pull request. It's designed for absolute beginners and should take less than a minute.

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.

A test for the `agent decision` command's subcommand consistency is failing because it expects a specific set of subcommands but the actual registered subcommands include an unexpected 'list' command. The issue is to verify if 'list' should be public and then either update the test to include it or remove the registration if it's accidental.

Concurrent executions of `init-session.ps1` on Windows can fail when updating the active plan pointer, leaving behind temporary artifact files. This race condition occurs because `[IO.File]::Replace` can be interrupted by another process attempting to modify the same file, leading to errors and leftover temporary files. The suggested fix involves retrying the file operation and cleaning up any remaining temporary files.

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 requests the implementation of a feature to track the time Teaching Assistants (TAs) spend grading assignments. The proposed measurement would start when a TA opens an assignment for grading and end when they submit their feedback.

The user is trying to enforce a conditional check where the 'chat_id' column should not be null only when 'whatsapp_lead_source' is 'openlines'. They are encountering an `InvalidExpectationConfigurationError` when using the `expect_column_values_to_not_be_null` expectation with a `row_condition` in Great Expectations for a Redshift datasource.

The `init-session.ps1` script fails to correctly handle project paths containing square brackets (`[` or `]`) when run with Windows PowerShell 5.1. This is due to a known PowerShell 5.1 behavior where the working directory resets to `$PSHOME` in such cases, and `init-session.ps1` lacks the recovery mechanism present in `set-active-plan.ps1`.

On Windows, the `init-session.ps1` script fails when the `.active_plan` pointer file has the ReadOnly attribute. This causes the script to create a new plan directory but then fail to update the pointer, leaving an orphaned directory behind. The issue is specific to named-plan mode on Windows and does not affect the default root mode.

This issue proposes to truncate the content of the original message when displaying replies. Currently, entire messages are shown, consuming excessive vertical space, especially with images. The goal is to improve UI by showing a preview with an ellipsis instead of the full original message.

This issue proposes extending Codra's deployment capabilities beyond Cloudflare Workers to support Node.js servers, Docker containers, and other serverless runtimes. The goal is to enable developers to run Codra on their own infrastructure with a single codebase, offering flexibility in deployment targets like VMs, Docker platforms, and serverless functions.

This issue aims to centralize a check within `OtapLogsView` to ensure that OTAP Arrow ID columns are decoded before being used for grouping and indexing. This prevents silent data corruption when transport-optimized records are processed, building upon a previous fix that addressed a specific exporter.

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. A governor agent periodically posts digest comments summarizing these advisory findings. This issue is intended to be a living document and should not be closed.

Desktop notifications currently lack an indicator to distinguish between regular messages and those within a thread. This makes it difficult for users to quickly identify and prioritize threaded messages, impacting the user experience.

A newer Samsung Bespoke AI Combo Washer/Dryer is not discoverable by the library because it uses standard OCF ports (5683/5684) instead of the expected range, and its DTLS endpoint rejects the library's standard trust anchor (AC14K_M) due to a different Public Key Infrastructure (PKI) used by Samsung.

The user has a split keyboard with 324 LEDs, exceeding QMK's current 256 LED limit due to the use of `uint8_t` for LED indexing. They are seeking guidance on how to modify the codebase to support a larger number of LEDs, considering potential RAM limitations on AVR platforms and proposing a `typedef` solution.

The Hermes plugin incorrectly overwrites the content of the `.active_plan` file by truncation, which can lead to unintended modifications of linked files. This issue occurs when `.active_plan` is a hard link or symlink, and the fix involves adopting the safer temporary file and rename strategy used by the shell initializer.

This issue proposes to enhance desktop notifications for messages with attachments. Currently, these notifications only indicate that a file was sent, but they do not display any accompanying caption. The goal is to include the message caption in the desktop notification for a richer user experience.

The OpenCode plugin incorrectly overwrites the content of `.active_plan` when it's a hard link or symlink, instead of replacing the link itself. This is because it uses `fs.writeFileSync` which truncates the file in place. A fix is suggested to mirror the safer approach used in the shell initializer, which involves writing to a temporary file and then renaming it.

This issue aims to create clear, copy-pasteable configuration recipes for GitHub Copilot across three different surfaces: VS Code, Copilot CLI, and the GitHub.com coding agent. It requires documenting the correct configuration keys and file paths for each, providing evidence of successful setup for at least one surface, and noting any specific constraints for the GitHub.com agent.

When persisting task leases fails, the function currently logs a warning and returns, leading to the lease being lost on restart. This can cause contributors to resume tasks against a hub that has no record of their assignment, breaking the expected durable state. The fix involves returning an error from the persistence function, which will then propagate to refuse the grant or mark it as non-resumable.

The mutation journal in the convergence package lacks cross-process locking, unlike the claim ledger. This can lead to data loss if multiple processes attempt to write to the same journal simultaneously, as they might overwrite each other's operations. The fix involves implementing a cross-process lock for the journal or enforcing single-process access.

This issue reports that the watchdog update process currently provides no user feedback, meaning users don't know if the update was successful or if it failed. The goal is to implement a clear message indicating the outcome of the update.

The root ROADMAP.md file incorrectly states that Phase 2 of the Task-scoped MCP is blocked by a measurement that has since been completed. This is a documentation discrepancy, as other roadmap files have been updated to reflect the merged Phases 2 and 3, and the closure of RFC #8033. The proposed next step is to update the ROADMAP.md to accurately reflect the project's current progress and momentum.

This issue requests the addition of numerous missing primitive functions and API endpoints to the {anvl} package. The goal is to fill gaps that currently prevent the package from being used for practical problems, covering areas like reverse rules, general tensor operations, statistical distributions, and linear algebra.

This is an epic for maintainer discussion regarding the integration of Spektacular with Hive orchestration. It outlines a proposed division of labor where Spektacular handles specification, planning, validation, and artifacts, while Hive manages orchestration, agent handoff, state, autonomy policies, and the chat interface. The issue emphasizes that this is a design discussion and not ready for implementation.

This is an epic issue serving as an umbrella for a larger design discussion that ties together three separate RFCs related to long-running tasks. It aims to define archetypes, govern external workflows, and integrate a product called Spektacular, with decisions recorded so far focusing on the separation of admission, verification, and publication gates.

This RFC proposes adopting a standardized vocabulary (Oracle, Generator, Executor, Gate) for describing long-running tasks within the Hive system. The goal is to leverage existing Hive features like checkpointing and progress tracking for any complex task, not just traditional GitHub issue-to-PR workflows. The proposal focuses on naming and integrating these archetypes into the convergence layer rather than building new machinery.