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 issue requests the addition of unit tests for the `MarshalBinary` interface implementations in the Go SDK's command types. The goal is to ensure that the binary serialization and deserialization of commands are correct and compatible with the Iggy server's expected format. This will improve data integrity and protocol reliability.

This issue identifies several "click handlers without keyboard equivalents" across various components in the Kubestellar Console. This means that users relying solely on keyboard navigation may not be able to interact with these elements, creating an accessibility barrier. The fix involves ensuring these interactive elements are focusable and operable via keyboard.

This enhancement request aims to improve the user experience by allowing a global refocus after performing a search. Currently, refocusing only works locally within certain panels. The goal is to return the user to their previous context, such as a specific message, if they were not in a list view before initiating the search.

This issue proposes improving the translation of Pygments styles into Urwid by automatically converting Pygments' style syntax (like spaces between combined styles) into Urwid's comma-separated format. The goal is to eliminate the need for manual overrides in themes and ensure compatibility with newer Pygments versions, with added runtime checks and tests for robustness.

This issue proposes implementing a custom backward pass for LoRA projections within the Fast-LoRA framework to improve efficiency. The current generic autograd is inefficient for LoRA due to repeated computations and separate kernel calls for operations like GEMMs, scaling, and elementwise additions. A hand-written backward pass can optimize this by concatenating matrices, accumulating gradients, and reducing saved context.

This issue aims to improve test coverage for the `report_results.py` script by adding tests for two specific scenarios: shell script suites that don't produce JUnit files and cases where JUnit files are missing. The goal is to ensure these edge cases are correctly handled and reported.

The `docker.yml` workflow incorrectly applies the `latest` tag to all release events, including older versions. This can lead to the `latest` tag pointing to outdated releases, especially when security fixes are applied to older lines. The proposed solution is to conditionally apply the `latest` tag only when a release corresponds to the highest version tag in the repository.

This issue proposes adding tests to verify that the default values for CUBRID_MCP_* settings listed in the README files (both English and Korean) accurately reflect the actual configuration defaults. This aims to prevent documentation from becoming stale and misleading if configuration defaults change without corresponding updates to the READMEs.

This issue addresses a lack of test coverage for the `describe()` function in `scripts/latest_server.py`. Specifically, the tests do not cover the `not-newer`, `newer`, and `unverified` summary statuses, nor the fallback behaviors for image tables and dates. The goal is to add tests that ensure these statuses are correctly reported and that the `unverified` summary never indicates a 'passed' status.

This issue identifies several inaccuracies in the MLX documentation regarding preference tasks, DoRA support, and installation requirements. The documentation incorrectly states which preference tasks support `eval_steps`, omits DoRA from several refused-at-load lists, and inaccurately describes the minimal installation needed for MLX-only backends.

The `soup train --dry-run` command incorrectly bypasses validation for evaluation gates configured in `soup.yaml`. This allows training to proceed even with invalid or empty gate configurations, such as suites with no tasks or duplicate task names, which would be rejected by `soup eval gate` or `soup train --gate`. The issue stems from a lack of upfront validation for gates specified in the configuration file.

This issue proposes the implementation of a `pgvector` VectorStore for the `@chatcops/core` library. This new store will allow users to store and query vector embeddings directly within their PostgreSQL databases, integrating with services like Neon, Supabase, and self-hosted instances. The implementation requires adhering to a defined `VectorStore` interface, handling migrations for `pgvector` extension, and creating a specific table schema with appropriate indexing.

This issue proposes adding a new VectorStore implementation to the `@chatcops/store-sqlite` package using the `sqlite-vec` library. The goal is to provide a single-file vector storage solution for SQLite, adhering to the existing `VectorStore` interface and its conformance tests. This involves setting up `sqlite-vec` as an optional dependency and integrating it with SQLite's extension loading capabilities.

This issue proposes adding a new VectorStore implementation to the `@chatcops/store-cloudflare` package using Cloudflare Vectorize for vector storage and Cloudflare D1 for text and keyword search. The implementation needs to adhere to the `VectorStore` interface, handle metadata filtering, and be tested against conformance tests. It also requires documentation updates and a changeset.

This issue identifies several hard-coded strings within DBeaver's plugin XML files that are missing corresponding localization properties. The reporter has found these instances after updating the develop branch and intends to create the necessary localization files to complete Simplified Chinese translation.

This issue proposes the creation of a new `@chatcops/store-upstash-vector` package to integrate Upstash Vector as a vector store. The implementation needs to adhere to the `VectorStore` interface defined in `@chatcops/core`, including methods for upserting, querying, and deleting vectors, as well as supporting metadata filtering. The package should be structured similarly to the existing `@chatcops/store-redis` and include comprehensive tests and documentation.

This issue tracks the migration of several CRM-related modules to version 17.0 of the OCA framework. It lists modules that have been completed (marked with 'x') and those that are still pending. The issue also provides a link to the official migration guide and a FAQ for missing modules.

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. The governor will periodically post summaries of these advisory findings. It's crucial not to close this issue as it's intended to be a continuously updated document.

The user is unable to access SMART data or array status for individual member drives within a JMicron JMS561 (152d:a561) based hardware RAID1 enclosure (Acasis EC-7252). Standard `smartctl` options for JMicron devices fail, and the `sat` option only reports the logical volume, not the underlying drives.

This issue proposes adding a 'fail-fast' connection option to the Rust and Python quick-start guides. Currently, the `connect()` function can hang indefinitely if the server is unreachable due to unlimited retries. Including this option in the quick-starts will provide users with a bounded connection attempt and a clear error message instead of a silent hang.

Setting the `ListView.CheckBoxes` property after assigning an `ImageList` to `StateImageList` corrupts the user-supplied image list. This issue affects both .NET Framework and .NET Core 3.1, and can even lead to unintended side effects on other ListView instances with similar image lists due to potential native caching.

This issue requests the addition of unit tests for the `currentLocale`, `currentTimezone`, and `setLocale` functions within the `date.ts` utility file. The goal is to ensure these stateful functions correctly handle stored values, fallbacks, and their impact on subsequent date formatting, thereby increasing test coverage for critical UI components.

The VS Code plugin incorrectly displays a "Click to reconnect" message in the status bar even after the URL has been cleared. This is because the status bar component retains the old URL state even when the underlying configuration is updated. The fix involves ensuring the status bar component forgets the URL when "Clear URL" is selected.

The `crux-publish.sh` script copies `README.md` to `docs/MODULE.md` in the published repository. Relative links within this README, which are designed for the source tree's structure, break when placed in the `docs/` directory of the published repo. The proposed fix involves rewriting these relative links to absolute GitHub URLs.