Find meaningful ways to contribute

This issue proposes integrating coding agent hooks into OpenHands' CLI and SDK. The goal is to allow custom logic to run before or after tool usage, with specific considerations for blocking behavior, configuration precedence, and execution environment. The hooks will receive event data and can either block tool execution or allow it to proceed.

This issue describes the implementation of chamfered corners in solidcore, specifically when three or more chamfered edges meet at a vertex. It details two types of corner closures: 'Mitre' where chamfer planes meet at a point, and 'Facet' where a new plane cuts off the corner. The work was intended to replace an older SMLib function and align with features found in other modeling systems.

The `YAXUNIT.cfe` file was placed in the wrong directory (`build/out/cfe`) and the standard decompile command failed because the YAxUnit extension was not present in the database. The correct procedure for decompiling test extensions like YAxUnit involves placing them in `build/out/tests/cfe` and using a specific command for test `.cfe` files, or using the 'Add YAxUnit' command which handles downloading and decompiling.

This issue tracks the implementation of structured serialization support for all layers within the PcapPlusPlus library. The goal is to ensure each layer has a `SerializedFields` struct, an overridden `serializeLayer` method, proper Doxygen comments, and corresponding tests.

The knowledge graph used for search expansion is stored in the memory of the ingestion process and is lost when the process restarts or when search is handled by a different process. This leads to ineffective graph retrieval in distributed environments like the Compose stack, after restarts, and during benchmark runs. The issue also causes graphs to grow indefinitely due to a lack of cleanup.

This issue tracks the porting of non-documentation commits from the `typesafe/config` repository to `ekrich/sconfig`. It serves as a reminder to periodically review and port new commits, with specific PRs listed and their porting status indicated. Some PRs require careful consideration due to platform-specific dependencies or potential conflicts.

This issue addresses inaccuracies in the current sample SST report screen, which incorrectly reflects GST logic and administrative bodies. The goal is to define the correct structure and fields for the SST-02 return based on specific knowledge of SST regulations, particularly regarding taxable periods and the distinction between sales and service tax.

The current implementation of simple span and log processors in OpenTelemetry does not properly handle in-flight exports during shutdown or force flush operations. This can lead to data loss as exports might be sent to an already shut-down exporter. The proposed fix involves tracking active export jobs, ensuring they complete before shutdown, and adding timeouts to prevent indefinite blocking.

This issue proposes refactoring the `header.js` file to utilize a function from `IssueRow` for label creation. The goal is to improve code organization and potentially reduce duplication by centralizing label generation logic.

This issue proposes adding a new `irreversible` effect tag to categorize actions that cannot be undone, such as sending an email. This tag would elevate the severity of unauthorized calls, treating them as critical findings similar to financial or deletion actions, and ensure this irreversibility is clearly indicated in various reporting formats.

This issue addresses excessive bot comments on GitHub issues, specifically focusing on "issue-side churn." The proposal aims to reduce comment volume by implementing an "edit-in-place" strategy for claim/release ledgers, needs-decision updates, and reviewer no-findings comments, rather than posting new comments for each change. This will improve clarity and reduce noise for human reviewers.

The German (DE) locale is not being correctly applied to the main navigation panel, causing it to display English translations instead. This appears to be due to missing German translation files and an incorrect locale mapping in the frontend's i18n handler. The suggested solution involves adding the missing translation resources and updating unit tests to reflect the correct German locale resolution.

The agent repeatedly performs overly broad searches, leading to an excessive number of results that overflow the context window. It then attempts to ingest all these results, causing performance issues and a confusing UI. The user expects the agent to refine searches and the CLI to prevent context limit breaches with a clear cancellation option.

This issue is a triage report identifying duplicate and overlapping open issues and pull requests within the hivecommons/hive repository. It specifically highlights near-duplicate issue pairs, duplicate PR pairs, a missing PR-issue link, and conflicting PRs, all related to the `human_merge_pin_only` exception. The goal is to consolidate these by deciding which items to keep and which to close.

The `LLM::Context: tool stream` example incorrectly stubs `Kernel.system` with a string, which is not a valid return type for the actual function. This leads to unrealistic tool results being passed to the model. The issue proposes re-recording cassettes and potentially adding provider-specific options to ensure the stub's return type aligns with `Kernel.system`.

This issue requests the design of a new custom icon for the 'Workflow' component within Meshery's MeshMap visualization tool. The icon should be provided in both white and colored SVG formats and must be distinct from existing model icons. The goal is to enhance visual clarity and consistency in the platform.

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.

This issue identifies a style-related inefficiency in a GitHub Actions script. The script `hive-status-card.sh` is refetching comment data that is already held by another script (`comment-merged-refs.sh`), leading to a duplicate API call. The proposed solution is to modify the helper script to accept data via standard input to avoid this redundancy.

This issue identifies a stylistic concern where the logic for paginating PR commits is duplicated three times within the codebase. The primary fix is blocked by another PR (#16400), and the recommendation is to refactor the code to export and reuse an existing helper function instead of maintaining separate implementations.

This issue aims to improve Hive-maintained GitHub Actions workflows by making them update or skip their comments if the runtime already reflects the necessary information. This prevents duplicate or redundant notifications. Additionally, external bots like Prow will be documented as outside Hive's control.

The `human_merge_pin_only` feature in the GitHub integration bypasses merge path holds based solely on the PR author's login being in a trusted list. This is a security vulnerability because it doesn't verify the actual commits in the head of the PR or the upstream reachability of the action SHA, allowing malicious code to be merged.

This issue tracks the migration of a large list of OCA modules to version 20.0. It serves as a checklist for maintainers to ensure all necessary modules are updated, referencing a wiki page for migration guidelines.

The HLSL output for a GLSL shader incorrectly attempts to call `.length()` on a `RWStructuredBuffer<float>` helper parameter, which is not a valid method in HLSL. This causes the DXC compiler to reject the shader. The expected behavior is to calculate the remaining length from an offset, similar to how GLSL output handles it.

The GLSL backend for crosstl incorrectly translates `StructuredBuffer.GetDimensions(n, s)` to glslang, causing compilation errors. The expected behavior is to translate this to `n = uint(values.length()); s = 4u;` with appropriate offset handling, or to provide a typed refusal. This issue was discovered during a review of a related pull request.

This issue requests community testing of a game build on various GPU architectures (AMD, Intel, and different NVIDIA cards) to identify driver-specific issues versus core game problems. Testers are asked to build the game, run it to a certain point, and report their GPU, driver version, OS, progress, and logs.

This issue requires a comprehensive accessibility review of the V1 version of the OTel Ecosystem Explorer, ensuring WCAG 2.1 AA compliance. The review involves automated checks (axe), manual keyboard and screen reader testing, and specific contrast checks across both light and dark themes for all critical routes. All identified accessibility failures are considered blockers for the V1 release.

This issue requests a user to follow the 'first-hour guide' on a clean machine (Windows, macOS, or Linux) and report any issues encountered. The goal is to ensure the guide is clear and functional for new users setting up the project.

This issue seeks to clarify the underspecified "fuzzy message expiry" feature in the SecureDrop protocol. It requires defining the exact semantics, including the distribution of the expiry time, potential quantization, and server-side behavior for message deletion. The goal is to formally specify this feature and potentially update the formal model.

The user is requesting that the default theme for the 'Drive' application be changed from blue to a neutral gray, similar to the themes used in 'Docs', 'Meet', and 'Conversations'. This change is desired to reduce styling efforts for the application.

This issue requires replacing Bootstrap utility classes within the `Gantt.vue` component with custom CSS using design system tokens. The goal is to remove all Bootstrap dependencies from the component, ensuring visual consistency across light and dark modes and passing all relevant UI checks.