Find meaningful ways to contribute

This issue proposes the creation of a singleton pattern for managing logging within the project. The goal is to ensure a single, shared instance of the logger is used throughout the application, simplifying logging management and potentially improving performance.

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 reports a panic in the `Grad.get` function when an ID is not found in `GradientsParams`. The user proposes a fix by changing the `unwrap()` to return `None` when the ID is absent, ensuring graceful handling of missing gradient IDs.

The user is asking for a way to round tensor elements to a specified number of decimal places within the Burn framework, similar to how `numpy.round` functions in Python. This enhancement would allow for more controlled numerical representation of tensor data.

This issue requests the addition of a 'source' button to the burn-rs documentation. This button would link directly to the source code definition of modules, similar to what is present in the tch-rs documentation, to improve navigation and understanding of the codebase.

This issue requests the implementation of an L2 Pooling layer, similar to PyTorch's LPPool2d, suggesting that L2 pooling would suffice for most use cases. The goal is to add this functionality to the project.

This issue proposes adding integration tests for the `burn-wgpu` backend using Deno's experimental WebGPU support. The goal is to ensure the backend's correctness by setting up Deno, automating test cases for `burn-wgpu` functionality, and integrating these tests into the CI/CD pipeline.

The current tests for raising shipment disputes only cover scenarios where the shipment is in transit. The functionality to raise a dispute after a shipment has already been marked as delivered is completely untested, leaving a gap in the test coverage.

This issue proposes creating a repository template using `cargo-generate` to streamline the setup process for new contributors. The goal is to provide a pre-configured project structure, making it easier for newcomers to get started with the project.

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 is a beginner-friendly task to add a new anime quote to a JSON file. It requires no coding and can be completed directly in the browser by forking the repository, editing the `anime-quotes.json` file, and submitting a pull request.

The `ensure_v1` and `v2_to_v1` functions in the KDL library are not correctly converting KDLv2 documents to KDLv1 in certain edge cases. Specifically, they fail to add a trailing semicolon after the last node in a block and do not properly quote values within slashdashed segments, leading to invalid KDLv1 output.

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 `opencode-pty` plugin fails to load in OpenCode versions 1.14.x and later due to the plugin host switching from Bun to Node ESM. This switch causes Bun-specific imports like `bun:semver` and `bun-pty/package.json` to fail, as they are not recognized in the Node environment.

The `get_total_ratings` function in the reputation contract is not behaving as expected. It currently reports the total number of ratings ever submitted, rather than the number of currently active ratings, because it doesn't account for voided ratings. This behavior is undocumented and lacks a specific test to verify its current (and potentially incorrect) semantics.

When editing an expense description from the Reports/Expenses (Search) tab, the new description does not immediately update. Instead, the page reloads showing the old description, and the new text may appear after a delay or require a page refresh/reopening the expense.

This issue proposes adding a new feature to the moonray_gui_v2 application: a hotkey to capture the current image and copy it to the system clipboard. This would allow users to easily share or paste the image into other applications like emails or chat clients.

This issue requests the addition of unit tests for the `useIsMobile` hook located in `apps/web/hooks/useIsMobile.ts`. The tests should utilize `renderHook` to cover the hook's primary states and ensure that `pnpm test` passes upon completion.

This issue requests the addition of unit tests for the `api-errors.ts` file within the `apps/web` directory. The tests should cover both normal input scenarios and edge cases like empty or invalid values to ensure the robustness of the API error handling.

This issue requests the addition of unit tests for the `funnel-analytics.ts` utility file. The tests should cover both normal input scenarios and edge cases like empty or invalid values. The goal is to ensure the functionality of the funnel analytics utility is adequately tested.

The user is encountering a `ModuleNotFoundError: No module named 'cutlass_library'` when attempting inference within the Openfold3 Docker image. This prevents the prediction process from completing successfully. The issue appears to be related to the Python path not including the necessary directory for the `cutlass_library` module.

This issue requests the addition of more training metrics to the 'burn-train' framework. Several metrics are already implemented, but the user desires a broader selection, including general GPU utilization, AUC-ROC, BLEU, and ROUGE scores.

The current documentation system fails to render a `<meta name="description">` tag when a document lacks a specific meta description. This means search engines must generate their own snippets, which may not be optimal. The proposed solution involves implementing a fallback mechanism to use a default site description when a page-specific one is absent, ensuring a meta description is always present.

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.

The fuzzing function `FuzzerTestOneInput` in `provider.c` incorrectly returns `1` for inputs of 16 bytes or more. This violates libFuzzer's contract, which expects `0` for success and `-1` for rejected inputs, potentially leading to unexpected behavior or crashes in the fuzzer.

The tracing quickstart guide incorrectly instructs users to place API keys and host URLs in a `.env` file. Neither the Python nor the TypeScript SDKs automatically read this file, leading to tracing being disabled or exports failing. This is confusing because other examples and the CLI do support `.env` files.

This RFC proposes extracting Hive's provider headroom probers into a standalone Go library and CLI named 'ccleft'. The goal is to create a reusable component for determining remaining quota, addressing current issues within Hive's probers and enabling other projects to access this functionality without reimplementing it.

The TypeScript documentation for cost-tracking and the SDK incorrectly nests `model` and `usage` within `metadata` when calling `updateCurrentSpan`. This leads to these fields not being recognized by the SDK, resulting in no cost being reported and no errors. Additionally, some documentation snippets are non-functional due to undefined variables or syntax errors.

This issue identifies unchecked arithmetic operations on fee and timelock counters in the `onboarding-bridge` contract. The current implementation uses raw operators, which can lead to unexpected panics with opaque errors in release builds instead of graceful `BridgeError::Overflow` reporting. The fix involves converting these operations to use `safe_math` functions, propagating errors, and adding unit tests for underflow cases.