Find meaningful ways to contribute

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 bug report identifies that F# `elif` statements are not being counted towards cyclomatic complexity in the analysis tool. This leads to undercounting the complexity of F# functions that use `elif` ladders, potentially preventing the `complex_method` detection from triggering. The fix involves adding `elif_expression` to the relevant branch kind definitions for F#.

This bug report identifies that a large C file in SwiftNIO, generated by the llparse tool, is incorrectly classified as production code. This misclassification leads to inflated complexity metrics and false alarms, as the generated code should not be subject to the same analysis as hand-written production code. The proposed solution involves updating the code origin detection logic to recognize generated files based on specific markers like `llparse_blob`.

This issue requests an update to the C# projection of the WinUIEssential.WinUI3 library to support CsWinRT 3 and the newer Windows 10.0.19041.0 (.1) target framework revision. The goal is to leverage CsWinRT 3's reference projection model for improved compatibility and future migration, without altering the existing native C++/WinRT implementation.

A JavaScript library (`sorttable.js`) included in the ScalaTest project's resources is incorrectly classified as 'production' code because its name doesn't end with `.min`. This misclassification leads to inaccurate health scores and complexity reports for third-party code. The fix involves adjusting the logic that identifies vendored libraries to correctly handle JavaScript files in resource directories, even if they lack a `.min` suffix, while still respecting licensing information.

The `go_swallow` analysis incorrectly flags calls to `strings.Cut` and `runtime.Caller` as swallowed errors. This happens because the analysis assumes the last return value of any multi-value function call is an error, even when it's a boolean or integer. The fix involves exempting specific standard library functions from this rule.

This issue requests an update to the Meilisearch SDK to support the new `sampledCount` option for sorting facet values. The SDK needs to be modified to accept and handle this new value in its faceting settings API, including updating types, covering get/update/reset operations, and adding relevant test cases and code samples.

This issue proposes adding an automated GitHub Actions workflow to rerun CPU jobs that fail due to GitHub runner infrastructure issues, specifically when runners lose communication. The goal is to prevent manual intervention for these types of failures, ensuring PR checks don't remain red unnecessarily.

This issue proposes adding C API bindings for two RocksDB options: `memtable_op_scan_flush_trigger` and `memtable_avg_op_scan_flush_trigger`. These options are designed to trigger memtable flushes based on the number of entries touched during range scans, which is beneficial for range-scan-heavy workloads. The task involves implementing the corresponding Java methods and adding tests for them.

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 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 inviting a non-existent user to a workspace and attempting to edit their display name in the Members section of workspace settings, the application incorrectly navigates to a 'not here' page instead of the expected display name settings. This bug is reproducible on staging but not in production.

This issue proposes adding explicit support for mapping JSON data types to specific runtime object types within TypeChat. The goal is to allow for accurate representation of these runtime types in the language model's prompt schema, even when the JSON wire format doesn't directly support them (e.g., ISO timestamps to Date objects). The current implementation loses this type information in the generated prompt schema.

The grid guide is missing documentation for CSV export and reading cell values, despite these features being available in recent versions. Developers currently have to consult the source code to discover these functionalities, which are not covered in the guide's existing sections on data handling.

NVDA intermittently fails to fully pronounce the end of words or character names when navigating text character by character or word by word. This issue persists even after disabling add-ons, reinstalling NVDA, and running the COM Registration Fixing Tool, suggesting a deeper bug within NVDA itself.

This issue is a request to add several new projects to a list, likely for a curated collection or repository. The user has provided a checklist of GitHub repositories, with some already marked as completed. The goal is to review and potentially integrate these projects.

This RFC outlines a roadmap for enhancing vLLM-Omni's full-duplex capabilities, focusing on improving performance, accuracy, and functionality for various models like MiniCPM, JoyAI, and Qwen3-Omni. Key areas include architectural updates for tool calls and multi-replica support, alongside model-specific optimizations for long conversations, speech streaming, and caching mechanisms.

This issue proposes creating a "recipe" for the Flisk framework that allows developers to use AWS S3 and SQS services locally without needing an actual AWS account. It involves setting up local emulators for these services and integrating them as Flisk resources, enabling fully offline development and testing of applications that interact with S3 and SQS.

The `check_vendored_vectors.py` script incorrectly reports deleted files as 'BEHIND' because it assumes a deleted path has no associated commit. However, the GitHub API correctly identifies the commit that deleted the path, leading to this misclassification. The issue requires updating the script's logic and documentation to accurately reflect how deleted paths are handled.

The README file in the 'vectors' directory incorrectly states that btclib's own suite holds vendored test vectors. These vector files have been moved to other repositories (ecc, bip32-descriptors, and base58-bech32) and are no longer present in the main btclib repository. The fix involves updating the README to accurately reflect the current location of these files or removing the misleading statement.

This issue proposes to update the description of the `rocketmq-proxy-core` package in its `Cargo.toml` file. The current description, 'Runtime-neutral', is misleading as the package has runtime dependencies like Tokio and `rocketmq-runtime`. The suggested fix is to change the description to 'Shared RocketMQ Proxy service contracts and ingress state'.

This issue proposes to improve the documentation for the `ProxyRemotingRequestHandler::shutdown_until` method in the RocketMQ proxy. The goal is to clarify that this hook is intended to drain work owned by the specific handler within a given deadline, and to explain the no-op nature of the default implementation. The suggested fix involves updating the Rustdoc to accurately reflect the handler's scope, deadline, and default behavior without altering the code.

This issue proposes to clarify the documentation for the `TransactionService::transaction_producer_group` method in the RocketMQ proxy. The goal is to accurately describe that the transaction service selects the producer group for transactional sends and that the ingress layer treats this value opaquely for correlation purposes, with the naming policy belonging to the transaction service implementation.

When compressing Windows executables compiled with Go 1.9.1, the file's metadata (icon, manifest, version info) is lost. The user suspects this is due to Go's method of embedding resources, which UPX might not correctly handle during compression.

This issue requests a clarification in the Rustdoc for `ProxyRequestMetadata` within the rocketmq-proxy-core crate. The current wording implies the metadata is only for requests sent to an adapter, but it's also used for Proxy-handled requests. The suggested fix is to rephrase the description to accurately reflect its use for all ingress requests before dispatch.

This issue requests an improvement to the documentation of the `ProxyMode` enum in the RocketMQ proxy core. The current description is inaccurate, and the fix involves clarifying that `ProxyMode` defines how the proxy is deployed (client-backed remote cluster or embedded local broker) and adding concise Rustdoc comments for its variants.

This issue proposes to improve the `rocketmq-proxy-core/README.md` file by separating the "Backends and validation" section into two distinct sections: "Local and cluster adapters" and "Validation". This change aims to clarify the roles of different adapters and make validation instructions more accessible to readers.

This issue proposes improving the Rustdoc documentation for six traits in the `rocketmq-proxy-core` module. The goal is to rewrite the trait summaries to directly describe their service contracts (e.g., route lookup, message sending) rather than repeating that they are shared by adapters. This aims for clearer and more concise documentation.

This issue proposes updating documentation for the RocketMQ Proxy Core crate to accurately describe its role in managing shared service contracts. The current documentation incorrectly labels contracts as 'backend-neutral,' and the fix suggests clarifying that these are shared contracts implemented by service adapters, with the Core crate owning protocol bindings and state.