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.

Production workers running Kubernetes plugin tasks are experiencing a thread leak, leading to OutOfMemory errors after approximately 24 hours. This is characterized by an excessive number of threads, many stuck in a TIMED_WAITING state, and orphaned executor pools. The issue appears to be specific to the `PodCreate` task, with evidence pointing to an asynchronous executor within `PodLogService` not being fully terminated.

This issue proposes developing a hierarchical model to analyze the results of RAG component composition across an entire sweep of experiments. Instead of pairwise tests, this model would analyze all per-query scores simultaneously, accounting for component effects, interactions, query difficulty, and run-to-run variability. This aims to provide a more coherent and robust understanding of how RAG components perform together.

This issue requests the migration of specific acceptance tests for the 'interested-partner-organization' feature from Puppeteer to Playwright. The goal is to fully retire Puppeteer from the acceptance test suite by rewriting the existing specs in Playwright syntax and updating configuration files. The process involves code migration, verification, and stress testing to ensure stability.

This issue proposes displaying the effective file directory as placeholder text in the empty directory fields within JabRef's library properties. This would help users understand where files are stored or searched for, especially when switching machines or collaborating.

The CrossGL compiler incorrectly represents matrix and array type arguments in function calls using their Python internal representation instead of their CrossGL spelling. This leads to compilation errors in various target languages like Rust, HLSL, and Metal, as these representations are not valid types in those languages. The expected behavior is for the compiler to use the correct CrossGL type names or to refuse the call with a more informative error.

This issue aims to enhance the Trino JDBC plugin by introducing a multi-statement `Queries` task, typed connection properties for various authentication methods and configurations, and improved query observability. This will bring the Trino plugin in line with other JDBC plugins, making it easier to manage Trino operations and trace them on the cluster side.

A race condition exists in the access code generation endpoint for quizzes. When multiple users request a code simultaneously, the system can generate and assign duplicate codes, violating the requirement for unique quiz session join codes. The expected behavior is that all generated codes must be globally unique and collisions should be handled gracefully.

This issue proposes adding a new `/health` API endpoint to the project. This endpoint will provide status information for various components like the database, RPC services, disk, and memory, allowing load balancers to accurately determine the application's health. The response should indicate overall health and include per-component status with latency, with a cached response for efficiency.

The `octomind workflow` command incorrectly attempts to read a directory as a TOML file when a workflow name matches an existing directory. This happens because `path.exists()` returns true for directories. The fix involves changing the check to `path.is_file()` so that directory names are correctly treated as potential tap workflows.

The user is encountering an issue with their Windows desktop app build pipeline, specifically related to CEF and zip generation. They are unsure of the next steps and are seeking assistance from the community as they are not a Windows user.

This issue highlights a security vulnerability where the backup and restore process in Qubes OS does not detect if entire VM data is missing from the archive, only corrupted data. This could lead to incomplete restores without explicit notification, potentially compromising system integrity. The fix would involve enhancing the verification and restore mechanisms to identify and report missing VM data.

This issue points out that a linter rule, `wrong_self_convention`, fails to check the return type of functions. Specifically, it doesn't enforce the convention that `as_` methods should return borrowed types, as outlined in the Rust API guidelines.

This issue proposes adding 'Pause' and 'Resume' actions for Deployments in both the UI and MCP, mirroring the functionality of `kubectl rollout pause` and `kubectl rollout resume`. This is needed because the current system, Radar, cannot manage paused Deployments, forcing users to switch to kubectl for these operations. The implementation will follow the pattern of the existing 'Restart' action across core, REST, MCP, and UI layers.

This issue proposes separating Node.js version requirements for development and runtime environments. Development will require a newer Node.js version (>=22.22.1) for tooling, while the runtime requirement will align with PostCSS unless the plugin specifically needs a newer version. The changes involve updating `package.json` and ensuring CI configurations are compatible.

The social links in the Community section of the Reframe landing page are broken, with Twitter and Instagram buttons redirecting to their home pages instead of the Reframe accounts. Additionally, the Twitter logo is outdated and needs to be updated to the new X logo.

This feature request addresses the inability for users to replay the onboarding tour after dismissing it. Currently, a permanent localStorage flag prevents the tour from reappearing. The proposed solution is to add a "Replay tour" link or button in a convenient location, such as the footer or keyboard shortcuts panel, to allow users to reset the flag and re-initiate the tour.

The OpenWebNet community is requesting real-world gateway traces to improve testing and ensure reliability across various hardware configurations. They are specifically seeking traces for gateways that are currently unverified in their CI pipeline, such as the Legrand 3578 USB / Serial Interface, to address "hardware blind spots" and prevent regressions.

On Android, after uploading a new avatar in the profile settings, the change is not reflected. This issue occurs even after going offline and then back online, and attempting to upload a different avatar. The problem is reproducible in both staging and production environments.

The documentation tab within the flow editor is not displaying the possible values for enum properties. While these values are available through autocompletion and on the plugin page, they are absent in the Docs tab, requiring users to rely on other methods to discover them.

This issue proposes adding a feature to display the total count of open tasks within project folders. Currently, only individual projects show their open task count, and this enhancement would provide a similar overview for folders, especially useful when they are collapsed.

This issue proposes refactoring the `function_call_continuation?` method in the Google LLM provider. The goal is to avoid redundant calculations by passing the already derived `last_call` and `delta_call` hashes directly to the method, rather than having the method re-derive them. This change aims to improve efficiency without altering the existing behavior.

This issue requests a clarification of a comment in the Google stream parser code. The current comment only explains one scenario of merging function calls, while the code handles a broader 'no-shared-id' rule. The goal is to update the comment to accurately reflect the full rule and its associated trade-offs, specifically how unidentifiable calls are merged to preserve incremental argument functionality.

The Skia renderer incorrectly inverts the weight parameter for `CrossFadeEffect` compared to WinUI and other backends. This means a weight of 1.0 displays Source1 instead of Source2, breaking the intended behavior for features like AcrylicBrush's dormant cross-fade path. The issue is currently latent as the problematic path is not actively used.

This issue serves as a central point for tracking various code quality and bug reports generated by different analysis tools. It aggregates findings from GCC, Clang-Tidy, Cppcheck, cpplint, an include analyser, an O2 linter, and unused file detection. The goal is to systematically address these identified issues within the codebase.

This issue describes the porting of a specific blend step from the smlib library to solidcore. It addresses how the end of a round's face is handled when it becomes tangent to the next face, redefining the end rib's construction and using a B-spline for G2 rounds. This change aims to resolve issues with coincident control points and improve the representation of tangent ends.

This issue proposes changing a boolean test in the perforated plate's 2D operation from being gated by timing ratios to being gated by counts. The goal is to address issues where the timing-based gate would trip under load, ensuring the test accurately reflects the expected number of face pairs examined and inner loops classified during the operation.

This issue requests the translation of core website templates and specific chapter content into Turkish. The task involves updating HTML templates, a Python language configuration file, and JSON configuration files for various years, as well as translating individual chapter files located in the content directory.

This issue highlights confusion and potential inaccuracies in the documentation regarding Spring Cloud Config's remote property overriding behavior. The user points out that `spring.cloud.config.allowOverride` must be set remotely, contrary to what the documentation implies, and that the interaction between `allowOverride` and the finer-grained `overrideNone` and `overrideSystemProperties` properties is unclear. The goal is to improve the documentation to accurately reflect these behaviors.

The Hungarian (hu-HU) localization for DISMTools is incomplete, with context menus and dropdowns failing to apply translations and displaying hardcoded English strings. The user has provided a valid translation file, but certain UI elements and strings are not being localized, suggesting potential issues with how the application handles dynamic menus or missing localization keys.