Find meaningful ways to contribute

A single-expense report submitted by an employee (User A) is incorrectly appearing in the 'To-do' tab of the Inbox for an approver (User B), even when the expense has been held. This occurs despite the expected behavior being that held reports should not appear in the To-do list.

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.

This issue describes a problem where the script for downloading official RF (Receita Federal) data can stall or experience connection interruptions, preventing successful completion. The user is requesting the implementation of a timeout mechanism to handle these stalled downloads and ensure data consistency, as currently, the process must be manually restarted.

This issue proposes migrating from a BasedPyright baseline configuration to a Pyrefly baseline. The core challenge is determining the compatibility between the two baseline formats and devising a user-friendly migration strategy, as a direct 1:1 conversion might not be possible.

The nightly build for the cmux project is failing on the main branch, specifically during the 'publish-nightly' step. This failure prevents nightly updates from being released and will automatically resolve once a successful build on the main branch is achieved.

This issue is a beginner-friendly task to add a new Japanese idiom to a JSON file. It requires no coding and can be completed directly in the browser by forking the repository, editing the specified JSON file, and submitting a pull request. The contribution is intended for first-time contributors and Hacktoberfest participants.

This issue requires updating the Chinese (zh-CN) documentation for SETUP and TROUBLESHOOTING to match recent changes in their English counterparts. The task involves comparing the files, translating any new content, removing outdated information, and updating the commit hash indicating synchronization.

This issue is a meta-tracking issue for a project-wide effort to rename code elements for better clarity and descriptiveness. The goal is to improve readability by using more intuitive names and avoiding abbreviations, aligning with good programming practices.

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`.

The release workflow header incorrectly states that no secrets are involved, while the workflow actually uses seven different secrets for tasks like signing and publishing. This discrepancy can mislead maintainers when setting up releases or troubleshooting failures.

The GitHub issue chooser currently only displays 'Bug report' and 'Feature request' templates, lacking an option for private security vulnerability reporting. This forces users to manually find the SECURITY.md file, potentially leading to accidental public disclosure of sensitive information.

A Go linter incorrectly flags goroutine loops as unbounded when a buffered channel semaphore is used, provided the channel's capacity is defined by a variable or expression rather than an integer literal. This leads to false positives for a common and valid concurrency pattern.

This issue is a discussion about the best location for example data fetching functions within the ReCirq project. The core decision is whether to centralize these functions in a utility module or distribute them within their respective domain modules (QAOA and Fermi-Hubbard). The goal is to establish a consistent and maintainable structure.

This GitHub issue is a dependency dashboard report from Renovate, highlighting several pending updates for various actions and dependencies within the uPortal-Project/uPortal-start repository. It provides checkboxes to automate the creation of pull requests for these updates, including a consolidated option to approve all pending PRs.

The user is confused by the singular `site-package-path` in the documentation, as the standard Python directory is `site-packages/`. They are asking for clarification on the reasoning behind the singular name and suggest adding an alias for `site-packages-path`.

The command-line completion for `brig ls`, `brig agent ls`, and `brig secret ls` does not offer the `--json` flag, despite the flag being functional. This is due to hardcoded flag lists in the completion logic that do not include `--json` for these commands.

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 proposes adding a feature to Raven that allows users to double-click on nested compositions (like Tracks or Stacks) to either expand them in-place within the main window or drill into them in a separate tab, similar to the functionality in otioview. The in-place expansion could draw inspiration from how Non-Linear Editors (NLEs) handle nested compositions.

The `spike_injector.py` script, used for testing GNSS outlier detection, lacks clear documentation and tests. Users cannot determine how spikes are injected (added vs. replaced), their magnitude units (meters vs. degrees), or how they affect the fix's covariance, which is crucial for adversarial testing. The issue proposes adding tests and a docstring to clarify these behaviors and ensure the tool functions as intended.

This issue requests the implementation of a quantum algorithm for schoolbook multiplication, specifically aiming to reduce the number of Toffoli gates used. The implementation should follow the construction detailed in the provided arXiv paper.

The `react$` and `react$$` selectors in WebdriverIO are failing with React 18 and later versions due to changes in how React manages its internal structure. Additionally, these selectors can return outdated component tree information, leading to components not being found or appearing when they shouldn't.

When creating a variant using a 'LS action' in Rust, the module name is incorrectly duplicated in the generated code. This results in a path like `shadowfist.shadowfist.MainShot` instead of the expected `shadowfist.MainShot`. The user is seeking assistance to resolve this duplication.

The K8sGPT Operator is failing to apply a mutation due to a formatting issue within the K8sGPT custom resource definition. The user has provided the exact YAML configuration that triggers the problem, indicating a potential parsing or validation error in how the operator handles the provided `K8sGPT` spec.

This feature request proposes integrating IBM Bob Shell, a terminal-based coding agent with a TUI, into Omnigent. The integration would allow users to launch Bob from Omnigent, mirror its terminal session, and see its installation status. The proposed solution involves creating a new native TUI harness for Bob, managing its launch within a tmux pane, and handling its interactive dialogs safely.

Go and Node.js CI jobs are failing on self-hosted LKE runners because the runner image is missing Go and npm from the PATH. This prevents tools like golangci-lint and npm from being found, causing environment setup failures. The likely cause is a drift in the runner image used by the autoscaled nodes.

This issue proposes adding a simple toggle to the F3 Ship Lab UI. The goal is to allow users to hide the UI and informational text, making it easier to take clean screenshots for promotional materials and loading screens.

This issue proposes two enhancements for the cBioPortal homepage search functionality. First, the dropdown with search examples should only appear on the initial click and disappear once the user starts typing. Second, the reference genome selection should be moved to a separate button, similar to how datatype is handled.

This issue proposes a redesign of the homepage data display to better reflect current performance and areas for improvement. It suggests shifting focus away from 2019 benchmarks to a more dynamic, recent target and incorporating new performance metrics like delays.

This issue requests adding unit tests to cover specific scenarios for the `flattenMenuItems` function in the Kestra UI. The goal is to ensure that nested menu items are correctly flattened and handled, preventing issues in the sidebar customization dialog. The tests should cover various nesting depths, empty children arrays, and empty menus.