Find meaningful ways to contribute

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 is a tracker issue for implementing SciPy's API functions within CuPy's `cupyx.scipy` namespace. It outlines the current status of various SciPy modules, indicating which are fully implemented, partially implemented, not yet available, or out of scope for CuPy.

This issue proposes modernizing the `/example` application's tech stack and practices to align with current production full-stack development. The goal is to create a simple yet production-like local example, focusing on best practices for authentication, storage, and database interaction (Kysely), while excluding cloud deployments and remote services.

This issue proposes adding support for date and time placeholders (e.g., {{YYYY-MM-DD}}) to automation session names. This will allow recurring automation runs to be automatically named with their execution date and time, making them easier to distinguish and track. The implementation details specify various formatting options, token rules, and error handling for invalid patterns.

The `withEvlog` and `defineWorkerFetch` functions in `evlog/workers` are incorrectly typing the `ctx` parameter as `WorkerExecutionContext`. This limits access to properties like `waitUntil`, `exports`, `props`, and `passThroughOnException`, which are available on Cloudflare's actual `ExecutionContext`.

The PR Agent currently loads configuration from `pyproject.toml` without applying a host-only filter, potentially allowing a reviewed repository to override sensitive host-specific settings. The suggested solution is to either apply the same filtering mechanism used for `.pr_agent.toml` to the `pyproject.toml` section or remove `pyproject.toml` loading if it's not essential.

This issue reports two visual bugs in JabRef's entry editor, specifically within the linked files field of the main tab. The first bug concerns incorrect text and background colors in dark mode, making the text unreadable. The second bug is an incorrect highlighting behavior where clicking on a linked file highlights more than just the selected file.

This issue aims to validate the build and real WebGPU output of the Eidoverse music-video container. The current implementation relies on mocks, and the goal is to run the adapter image and a synthetic scene on a Linux host with Docker to ensure correct rendering and identify any compatibility issues.

This bug report highlights an inconsistency where `QubitUnitary` in PennyLane rejects 1x1 matrices on zero wires, despite this being a valid quantum operation equivalent to `GlobalPhase`. The desired behavior is to allow `QubitUnitary` to accept these inputs, aligning with PennyLane's existing support for zero-wire circuits and the `GlobalPhase` alias.

This issue is a "Dependency Dashboard" generated by Renovate, listing detected dependencies and potential updates for the repository. It indicates that the repository currently has no open or pending branches, and details the various GitHub Actions and their versions used across different workflow files.

This issue introduces an opt-in feature for a contributor quota system, allowing banked resets for weekly reserves under specific conditions. It requires a new environment variable `HIVE_CODEX_AUTO_USE_BANKED_RESET` and modifies admission logic based on available credits and the opt-in status. The change focuses solely on relaxing the weekly reserve, leaving other limits unaffected.

This feature request proposes an opt-in mechanism for unattended Codex contributors to automatically use banked resets when their weekly quota is exhausted. This aims to prevent manual intervention by allowing the contributor to resume accepting work without requiring explicit user action for each reset. The implementation should be contributor-local and clearly documented as an explicit consent action.

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 proposes adding a `size` prop to the `Button2` component to standardize button sizes across the application. The prop will accept values like 'small', 'medium', 'large', and 'extra-large', with responsive adjustments for different screen sizes (desktop, tablet, mobile). This enhancement aims to improve UI consistency.

This issue proposes adding a new command, `subsonicupdate`, to manually trigger a Subsonic library update. It also suggests a configuration option `auto` to control whether updates are made automatically, defaulting to `false` to maintain existing behavior. The goal is to provide explicit control over Subsonic library updates, especially when the Subsonic library is managed independently.

The 'Bob' agent is failing because the system cannot find the executable at '/usr/bin/bob'. This indicates a missing dependency or incorrect path configuration for this specific agent. Further investigation is needed to determine if Bob is a required component and how to resolve the missing executable.

This issue proposes adding a project setting to toggle the visibility of the navigator (minimap) in the viewer. The motivation is to prevent the navigator from obstructing screenshots, figures, and small screens. The proposed solution is to add a switch to the render settings in the Project panel, which will control the `showNavigator` option and be saved with the project.

This issue proposes adding a configurable option to disable the automatic injection of service environment variables into pods. This is intended to reduce unnecessary environment variables and prevent potential information leakage, as the SciServer use case does not require them. The change is considered cheap and easy to implement.

This issue proposes adding a 'Home' button to the viewer interface, positioned next to the point size slider. The button's functionality would be to reset the view to display all data, addressing the current lack of a quick way to return to the full view after zooming and panning. This is a straightforward enhancement to improve user navigation.

The v6 CI pipeline is failing due to merge conflicts between v5 and v6 branches. Specifically, there are five files with textual conflicts and one semantic conflict where a function `mustParseRFC3339` was redeclared in different files. A resolved merge commit exists on the `ci-maintainer/sync-v5-to-v6` branch, but it requires human intervention to be merged into the v6 branch as a merge commit to resolve the CI failures.

This is a tracker issue for implementing missing NumPy API functions within the CuPy library, which provides GPU acceleration for NumPy operations. The issue categorizes remaining tasks by difficulty, aiming to guide contributors in selecting appropriate tasks for implementation. Many of these functions have already been implemented, but several remain open for contribution.

This issue outlines the comprehensive checklist for the HugeGraph 1.8.0 release, focusing on functionality, compatibility, documentation, and cross-repository integration. It details specific tasks for HugeGraph Server, Toolchain, AI, website, and documentation, including Kubernetes/Helm support, various deployment configurations, and authentication mechanisms.

This issue addresses several bugs and missing features on the Mentor Dashboard. It requires fixing broken buttons, adding navigation to detail pages, improving table rendering for mentee cards, and handling null/undefined dates in the applied column. The goal is to enhance the usability and completeness of the mentor's view of their mentees and applications.

This issue proposes to extend the SimplifyDemandedVectorElts pass in LLVM's InstCombine to handle more trivially vectorizable intrinsics beyond SMULH/UMULH. It suggests incorporating intrinsics like min/max and ensuring proper poison value propagation using intrinsicPropagatesPoison(). The primary effort will be in developing adequate test coverage.

A build fails with an MSBuild error when a non-existent fallback NuGet package folder is specified in the generated .csproj.nuget.g.props file. This issue occurs with SDK-style projects using PackageReference and seems to stem from an incorrect or default configuration of fallback folders.

When restoring a NuGet package with an invalid (non-boolean) value for the `copyToOutput` attribute in its content files, the build process throws a generic `System.FormatException` instead of a more informative `PackagingException`. This makes it difficult to diagnose the root cause of the restore failure, which stems from malformed package metadata.

The scripts in the `tools/` directory lack a consistent way to display help messages. Many scripts either ignore `--help` or accidentally appear to work when given it because they accept no arguments. The proposed solution is to implement `argparse` with the script's docstring as the help message for all scripts, making `--help` functional and unknown flags an error.

This issue aims to clean up linting errors in existing Jupyter notebooks that were previously ignored to prevent CI failures. The goal is to remove the `--select=E999` override in the `nbqa-ruff-check` configuration, allowing it to enforce the full Ruff linting ruleset. Most findings are auto-fixable, with a few requiring manual intervention.

This issue proposes adding layer-wise dropout to ConvNeXt blocks. This would involve modifying the existing ConvNeXt block implementation to incorporate dropout at different layers, potentially improving model regularization and performance.

This issue requests the creation of a new testing suite to specifically address issues arising from the recent addition of a custom allocator API. The goal is to ensure that collections, particularly `SmallVec`, function correctly with custom allocators by replicating relevant tests from `tests/main.rs`.