The user has identified a potential bug in the `uki-generate` script within the Qubes OS project. They point out a line of code where `max_vma` is calculated using `max(max_vma, size, + start_vma)`. The user suggests this might be an error and that it should likely be `max(max_vma, start_vma + size)` to prevent overlapping sections.
The engine fails to detect when a relay goes down, preventing automatic reconnection. This means users must manually restart the engine to re-register it after a relay failure, impacting operational continuity.
This issue proposes a strategy for automatically generating names and handling name collisions for Clients, Relays, and Engines. It aims to prevent unintended sharing of resources and ambiguous connections by defining clear naming conventions and conflict resolution mechanisms, independent of VM isolation.
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.
This issue proposes isolating client execution environments by having the Engine manage separate BEAM VMs for each client. This aims to prevent interference between modules and runtime states of different clients, as the current implementation allows for module overwrites and execution of code from other clients. The proposed solution involves the Relay handling client-specific module storage and engine selection, while the Engine manages the mapping between clients and their respective BEAM VMs for module loading and function execution.
This issue proposes to introduce a default mode where the Relay component manages and starts its own Zenoh Router. This aims to simplify the initial setup for users trying out Giocci. An alternative mode will be retained, allowing users to continue connecting to an externally managed Zenoh Router.
This bug report indicates that source distributions (sdists) are missing for versions 0.1.15 and 0.2.0 of the kornia-rs project on PyPI. The last version with an sdist was 0.1.14. This prevents users from easily installing the package from source.
The CALM Hub UI is experiencing a false positive warning from React Flow regarding new `nodeTypes` and `edgeTypes` on each diagram mount in development. This occurs because `StrictMode` causes `useMemo` to run twice, leading React Flow to believe new types are being created when they are actually module constants. The warning, while harmless, can obscure genuine errors in the development console.
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.
When manually editing the URL hash in the calm-hub-ui, the application incorrectly displays the previous resource instead of navigating to the new one. This is because the router's key comparison logic doesn't account for manual URL changes when the key is 'default', leading to the current resource not being cleared.
This issue reports that seed data for AI governance controls and architectures in CALM Hub is not valid against CALM schemas. Specifically, control requirements use incorrect field names (`id`, `summary` instead of `control-id`, `description`), and architecture nodes/relationships incorrectly use an array for `controls` instead of an object keyed by control ID. This leads to the hub serving invalid documents.
This issue is an introductory translation task for the Linux kernel documentation on Ramoops. The goal is to translate the existing English Markdown file into Simplified Chinese, maintaining formatting and technical terms. The task involves translating text, updating metadata, and ensuring the translated document renders correctly.
This issue proposes to incrementally type-annotate six legacy core modules within the skillware framework. The goal is to remove existing mypy overrides and enforce strict type checking across the entire skillware package, improving runtime reliability and developer experience.
This issue proposes enhancing the search functionality by adding a "Search all cellars" option when an in-cellar search yields no results. Additionally, it suggests implementing a '/' keyboard shortcut on desktop to focus the search box, mimicking common web conventions. This aims to improve the user experience by providing clearer pathways to broader searches and quicker access to the search functionality.
On Android and iOS, navigation arrows within the expense details screen disappear after an expense is deleted while the app is offline and then synced online. This occurs when the user navigates to a different expense after the deleted one has been removed from the 'Recently added' list.
The 'In-Place Upgrade Smoke' GitHub Actions workflow failed during its execution. The issue is automatically reported and requires investigation of the provided run link to identify and fix the root cause. The issue should remain open until the workflow successfully passes on the main branch.
The storefront is incorrectly configured with a `permissions-policy: payment=()` header, which prevents Apple Pay and Google Pay from initializing via the Payment Request API. This issue needs to be resolved by adjusting the permissions policy, likely within the EmDash framework or Cloudflare adapter, to allow payment functionality for Stripe's Payment Element.
This bug report details how specific C++ macro usages, particularly those involving arguments or qualified identifiers, cause the AST parser to incorrectly identify function names and parameters. Macros like `JSON_HEDLEY_NON_NULL(2)` result in `<anonymous>` function names and no parameters, while `GTEST_API_` combined with qualified return types leads to functions being parsed with zero parameters despite their presence in the code.
The session list incorrectly reports that a project has no dev script when the application is located one level down from the agent's task folder, and the task folder itself lacks a package.json. This occurs because the detection logic only checks direct children listed in a workspace file, and a folder without a package.json has no workspace. The fix involves enhancing the detection to scan direct child folders for a package.json with a dev script when the parent folder lacks one.
A user reported that the title bar color in TeXstudio changed from black to white on Windows 10 when dark mode is enabled, specifically after updating from version 4.9.8 to 4.9.9. This issue did not occur on Windows 11, and the user desires the title bar to remain black as it was in the previous version.
This issue involves porting an existing script that benchmarks vectorized environment speed to a new location within the repository. The task requires moving the script, ensuring it runs correctly, and updating documentation to reflect its new location and usage. The goal is to have the benchmark script executable with specific parameters and passing CI tests within a time limit.
This issue requires porting error recovery mechanisms for `SimWorker` processes from an older `vector_env.py` file to a newer one. The goal is to ensure that worker exceptions are propagated to the parent process with tracebacks and that crashed workers can be optionally restarted.
This issue proposes adding a new Halton mask scheduler as an alternative to the existing cosine scheduler in Genie's dynamics model. The Halton scheduler will use a low-discrepancy sequence to select tokens for unmasking, offering a deterministic ordering. This change requires configuration updates and thorough testing to ensure correctness and maintain the behavior of the cosine scheduler.
This issue proposes to allow the DiT training task to select between AdamW and the new Muon optimizer. The implementation should handle splitting parameters for Muon (2D weight matrices) and AdamW, provide an error for older PyTorch versions, and include a basic test to ensure functionality and checkpoint resumption.
This issue proposes adding MLflow as a new backend for the `MetricsLogger` utility. The implementation should mirror the existing Weights & Biases integration, allowing for optional MLflow logging with a lazy import and no hard dependency. It requires logging scalars and videos as artifacts, defining an `mlflow` extra in `pyproject.toml`, and including a test case and documentation update.
This issue requests the addition of 'IRIS' as a new playable module within the `simulusion play` command. It needs to support both a 'REAL' mode (interactive or policy-driven) and a 'DREAM' mode (world model imagination), following the patterns of existing modules like 'diamond' and 'dreamer'. The implementation will involve modifying the CLI, inference logic, and potentially agent interaction.
This issue proposes adding a headless evaluation command for the DIAMOND agent. The goal is to enable running a specified number of real-environment episodes and reporting per-episode and mean returns, suitable for CI environments and machines without a display. The existing `simulusion.inference.eval_diamond` module will serve as a pattern for implementation.
This issue proposes adding an on-demand feature to save dream trajectories in `simulusion play diamond`. Users will be able to press 'S' to save the last N dreamed frames, along with associated actions and predicted rewards, as an MP4 video and a JSON file. This provides more flexibility than the current requirement of specifying recording upfront.
This issue requests the creation of comprehensive documentation, tutorials, and example notebooks for environment descriptors and generator APIs. The goal is to provide a start-to-finish guide for creating a generator and training an agent, with specific acceptance criteria including a docs site skeleton and three distinct tutorials.