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.

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.

The auto-compaction feature silently falls back to a less sophisticated mechanical method when the LLM summarization fails. Users are not notified of this degradation, leading to lower-quality summaries without their knowledge. The proposed solution is to add a clear indicator to the compaction message when the LLM fails.

The user is seeking clarification on the expected behavior of an OAuth 2.0 client when it specifies `token_endpoint_auth_method` as `private_key_jwt` but fails to provide either `jwks` or `jwks_uri` in its metadata. They suspect this should result in an `unauthorized_client` error.

The `detectProvider()` function incorrectly categorizes Gemini models, causing them to fall back to a generic tokenizer. This leads to inaccurate token counts and context capacity percentages displayed in the UI, potentially being off by 2-3x for Gemini users. An update to `tokenizer-factory.ts` is needed to correctly identify Gemini models and apply a more accurate heuristic.

This meta-issue outlines the need for dedicated maintainers to implement and support screen and audio capture functionality on Windows and macOS. It details specific APIs and pipeline components to be used for each operating system, emphasizing zero-copy pipelines and native encoding capabilities for optimal performance.

This issue identifies numerous unnecessary Checkstyle suppressions in seven Maven plugins (mojos) due to misconfigured `@Parameter` annotations. The fields are named in camelCase, violating the `MemberNameCheck` rule, and the suppressions are present because the developers assumed Maven binding required them. The solution involves renaming these fields to a single lowercase word and adding an `alias` attribute to maintain backward compatibility with user configurations.

The time picker's "Relative Time" (live tail) feature incorrectly greys out all preset time ranges longer than 1 hour, preventing users from selecting them via the UI. While longer live ranges can be set via the URL, the UI provides no explanation for this limitation, leading to user confusion. The issue stems from the `RELATIVE_TIME_OPTIONS` configuration where longer ranges are not marked as supporting relative time, causing the picker to disable them.

This issue proposes a comprehensive review, migration, and enhancement of dubbo-go's adaptive service throttling capabilities. The goal is to move these features to `dubbo-go-extensions` for a lighter main repository, accompanied by performance testing, sample implementations, and potential upgrades to address identified issues.

The current mock generator, Counterfeiter, creates mocks that import the interface's defining package. This creates a circular dependency issue, preventing the use of mocks in unit tests that also import the same package, particularly hindering client-side interface definitions. The goal is to find or create an alternative mock generator that avoids this package import dependency.

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 missing test coverage in `secret_readers.rs` for two specific scenarios: a missing muster roll file and duplicate application names within the roll. The proposed fix involves adding tests to cover these edge cases, ensuring the code behaves as expected and preventing silent failures, particularly with the duplicate app name scenario.

The `CodeBlock.astro` component reserves 56px of horizontal padding on the right side for a copy button that is not always rendered. This wasted space causes code lines to wrap prematurely. The proposed fix involves conditionally applying this padding only when the copy button is visible.

The `Counters` struct in `shep-daemon/src/handover/blob.rs` is documented to reset to zero in its constructors, but it lacks a `Default` implementation. This requires explicit initialization of its fields at every zero-initialization site. Implementing `Default` for `Counters` would align the code with its documentation and simplify initialization.

This issue proposes adding multi-turn session resume functionality for Grok Build within Studio. The goal is to allow follow-up design directions to maintain context from previous turns without resending the entire web transcript, by leveraging Grok's native session resume feature. This involves capturing session IDs from completed turns and using them to resume sessions on subsequent turns, with specific handling for session invalidation and failure.

The `BinaryClickerV2/BinaryToggle` node type is failing to compile due to an incorrect API call in its layout source. The code attempts to use a non-existent `host.GetData<BinaryToggleData>()` method, instead of the documented `host.Workspace.GetStream<MeshNode>()` or `workspace.GetMeshNodeStream(path).Select(n => n.ContentAs<T>)` pattern used by its V1 counterpart. This is a contained bug affecting only this specific node type.

This issue proposes adding `Default` implementations for the `MemSize` and `UpDuration` newtypes in the `shep-core` crate. Currently, the lack of these implementations prevents structs containing them from automatically deriving `Default`, hindering their usability. The fix involves providing a `Self(0)` implementation for `MemSize` and the equivalent of `Duration::ZERO` for `UpDuration`.

The `glob_to_regex` function unnecessarily compiles glob patterns twice and creates an extra string clone on every call. The proposed fix is to have `glob_to_regex` return a compiled `regex::Regex` directly and optimize the string cloning logic to only occur when necessary. This is a minor performance enhancement for a private function.