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 adding the `factorise` function to the `lock_exchange.cpp` example in Armadillo. This optimization allows for reusing the factorization of a sparse matrix when solving systems with a constant left-hand side, enabling users to run the example at higher resolutions and render more detailed visualizations.
The current temperament table in the singer module incorrectly clamps notes above E7 to the E7 frequency. This issue requires modifying the `temperament.ts` file to extend the frequency table's range, ensuring that higher notes are represented by their correct frequencies instead of being clamped.
The `validateImplementation` and `validateUpgrade` functions in the `openzeppelin-hardhat-upgrades` library fail when the implementation contract has constructor arguments. This is because the validation process attempts to encode deployment data without providing the necessary constructor arguments, leading to a type/value length mismatch error. A workaround exists by manually providing `constructorArgs`, but the issue should be fixed to handle this scenario automatically.
This issue proposes adding a new "Sandstone" dashboard theme preset, which offers a warm, off-white, paper-like light option for users who find existing dark or cool-toned themes unsuitable. The implementation involves creating a single YAML file for the theme and updating documentation and test lists, with no impact on existing users or contributors.
This issue aims to improve theme coverage across the application by making more widgets adopt the frame's theme. Currently, only a fraction of widgets utilize the `Frame.SetTheme` functionality, leading to a partially themed application. Developers are encouraged to pick a widget, implement theme fallback logic, add relevant tests, and maintain benchmark performance.
The iceoryx2 build process for QNX 8.0 fails due to an outdated Rust toolchain. The `libc` dependency, compiled with an older Rust version, encounters a compilation error on QNX 8.0. This is likely caused by changes in Rust's QNX platform support and target triplets in newer compiler versions.
This issue describes two bugs in the Cube writer for Semantic. First, applied files incorrectly become owner-only, preventing other users from reading them. Second, the apply process only re-checks reader errors, allowing invalid content to be written that the planning step would have rejected. The goal is to fix these issues to ensure proper file permissions and enforce write-time rules during apply, mirroring the behavior of the Metric View writer.
This issue proposes adding a new security rule (SG-106) to detect servers exposing an excessive number of tools (over 50). The goal is to prevent agent confusion and reduce the attack surface for tool poisoning. The implementation involves porting an existing rule from another project, adding tests, and ensuring efficient matching.
This issue proposes creating a new security rule (SG-103) to identify tools that have unrestricted path parameters in their input schemas. This vulnerability could allow malicious actors to access sensitive files like SSH keys or system configuration files. The rule will be ported from an existing tool called `mcpscan` and requires adding tests and documentation.
This issue requests help from users with Apple Silicon Macs to map the performance and numerical correctness "rooflines" of the Apple Neural Engine (ANE). Participants can run a simple 2-minute command to submit data from their machine, contributing to a comprehensive cross-chip analysis and receiving GitHub credit.
This issue proposes adding support for ONNX DFT and STFT operations within the aneforge framework. The core task involves mapping ONNX node attributes to existing FFT and DSP functions already present in aneforge, rather than implementing new numerical computations. The approach includes handling different input formats for DFT and mapping STFT parameters to the existing `aneforge.dsp.stft` function.
This issue proposes implementing `periodogram` and `cross-spectral density (csd)` functions for the dsp module, following the established pattern of the `welch` function. `periodogram` is a single-segment version of `welch`, while `csd` calculates the cross-spectrum between two signals. The implementation should adhere to SciPy's conventions and be verified on Apple Silicon Macs.
The user is experiencing flickering and blank screens on their 5.7" LVDS display connected to a CM4 when the battery voltage drops below approximately 11.8V. The CM4 itself remains responsive, suggesting a power delivery or display driver issue related to low voltage. The problem seems to be mitigated by higher voltage batteries like LiFePO4.
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.
help wantedagent/scannerhive/advisoryagent/security
The `unit-test` suite failed during a nightly run, indicating a regression. The provided log tail shows many successful tests, but the overall suite failure suggests an issue that wasn't captured in this snippet or a failure in a later part of the test execution. Further investigation of the full logs is required to pinpoint the exact cause.
This issue proposes migrating the "Current Limitations / TODOs" section from the project's README to GitHub Issues. The goal is to make these items visible to potential contributors, allowing them to identify and address outstanding tasks. This involves reviewing the existing list, creating new issues for actionable items, and adding relevant context and links.
This issue proposes to enable direct installation of the Hermes MCP (Multi-Cluster Platform) agent. Previously, the installer only printed the configuration due to an unverified format, requiring manual setup. The Hermes documentation has since been updated and authoritatively confirms the configuration format, justifying its promotion to direct installation.
The `flisk up` command incorrectly performs time-consuming Docker operations like pruning images and build cache before determining that it's not being run within a Flisk project. This leads to unnecessary delays and unintended modifications to the Docker environment, even when the command is destined to fail. The proposed fix involves checking for the project root earlier in the execution flow to avoid these wasteful Docker interactions.
documentationenhancementgood first issuehelp wantedagentsdifficulty: easy
The `flisk project fullstack` and `launch` commands incorrectly copy demo media files (like GIFs and MP4s) from the template into the user's new repository. This bloats the user's project and pollutes their git history with irrelevant files. The fix involves excluding these media files during the scaffolding process and updating the READMEs to remove references to them.
documentationenhancementgood first issuehelp wantedagentsdifficulty: easy
This issue describes a performance problem where forgotten Docker projects, each running its own Traefik and Postgres instances, consume excessive disk space and resources. The problem is exacerbated by leftover volumes from removed projects and Docker images that are not automatically cleaned up, leading to significant disk usage on the host machine.
buggood first issuearea: cliperformancetech: dockerclaimed
This issue addresses the problem of the ERP starter template in Flisk incorrectly including marketing files like SALES_PITCH.md and DEMO_GUIDE.md in the user's project. The proposed solution involves removing these files from the starter template or relocating them to a documentation folder, ensuring the scaffolded project only contains essential files for the user.
documentationenhancementgood first issuehelp wantedagentsdifficulty: easy
Several engine tests are failing locally on Python 3.9 on macOS, specifically related to code execution timeouts and daemon polling. There are also collection errors in two other test files, likely due to incompatible Python 3.10+ type syntax being used. These issues are not present in CI, indicating a local environment dependency.