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 issue proposes a complete rewrite of the PDQ index implementation in Python to address design flaws in the original version. The goal is to create a simpler, more efficient solution by refactoring the hash-to-ID mapping, build process, and lookup mechanisms. The proposed changes include passing the index type as an argument and simplifying the internal state management.

This issue proposes migrating the `mosaicolabs.examples` command from the SDK's local CLI to the main `mosaico` CLI. The goal is to centralize example execution under the primary entry point, leveraging existing profile configurations for connection settings instead of explicit flags. This change also includes updating documentation and CI tests.

The project maintainer is seeking additional contributors due to a reduced availability of time. The primary need is for individuals to help maintain lists, which are frequently updated due to changing URLs. The maintainer is encouraging anyone interested and understanding of the project's goals to volunteer.

The `.git-blame-ignore-revs` file contains commit SHAs that are no longer ancestors of the `main` branch due to squash merges. This prevents `git blame` from correctly ignoring these commits. The proposed solution is to update the file with the correct squash commit SHAs from `main` and add a CI check to prevent this issue in the future.

This issue requests the addition of the Mosaico documentation version to be displayed within the documentation interface, likely in the menu bar. This would provide users with a clear and easily accessible way to identify which version of the documentation they are currently viewing.

The Part Design workbench's sprocket generator incorrectly calculates the roller diameter for ISO 606 10B roller chains, using the distance between plates instead of the actual roller diameter. This leads to incorrect sprocket geometry and a 'math domain error'. The user expects the tool to use the correct ISO 606 dimensions for accurate sprocket generation.

This issue proposes to enhance the validation rules for dashboard creation and updates. Specifically, it aims to enforce minimum and maximum length constraints on dashboard names, descriptions, and queries, and to ensure that time range values are valid ISO-8601 datetimes or null. New tests will be added to verify these validation rules.

The server currently reports generic "fetch failed" errors for HTTP, Slack, Teams, and Jira actions when they cannot reach their receivers. This issue proposes to improve error reporting by including the underlying `error.cause` message, which provides more specific details like connection refused or DNS resolution failures, making debugging easier. The fix involves modifying the `executeAction` catch block and adding relevant tests.

The Docker Pulls badge in the Meshery.io README.md incorrectly links to a non-existent Docker Hub repository. The issue is to update the hyperlink to point to the correct `meshery/meshery` repository, resolving a 404 error when the badge is clicked.

This is a tracking issue for implementing additional comparisons. The issue itself doesn't detail *what* comparisons need to be implemented, but it serves as a central point for future sub-tasks or discussions related to this feature.

This issue requests an enhancement to the Configuration controller to make its tab sub-components dynamically resize when the floating pane is resized. This aims to improve the user experience by ensuring content within the tabs remains visible and well-formatted regardless of the pane's dimensions.

A test in the CI pipeline is failing intermittently due to a race condition where a PID might be reused before a staleness check. The test relies on a PID remaining dead, which is not guaranteed in a busy parallel CI environment. The proposed fix involves ensuring the staleness check correctly verifies the PID's start time or using a PID that cannot be live.

The `tracekit last` command incorrectly informs Claude Code users that their open run closes when the agent's process exits. This issue requires updating the CLI output to accurately reflect that Claude Code runs close at the session's `SessionEnd` hook, not on process exit. Additionally, a new test needs to be added to verify the updated messaging for both Claude Code and SDK runs.

This issue requires modifying the `get_by_hash` and `update_memory_metadata` functions in both the Milvus and remote_http storage backends to correctly utilize the `store` parameter. The goal is to ensure that operations are scoped to the specified store, with specific instructions for handling older or incompatible peers in the remote_http backend. The work will be split into separate pull requests for each backend.

The user is encountering an 'ERR: end of input reached' error when trying to read the error history from their Vaillant heating system using `ebusctl`. They suspect the issue might be with the `errors.inc` configuration file, as they are unsure if it's working correctly.

KiviDB's command-line interface incorrectly refuses several directives that are accepted by its configuration file and are commonly used with Redis. This prevents users from starting KiviDB with standard Redis command-line arguments, causing failures in environments like Dify's tests and Docker Compose setups.

This issue requests the addition of a new "false friend" pair for Japanese learners. The task involves adding a JSON object to a specific file in the repository, which defines the Japanese term "マンション" (manshon) and its English counterpart "mansion," along with an explanation and example. No coding is required, and the contribution can be made directly through the browser.

This issue proposes to refactor the test suite for the `arrow-cast` module by splitting the large inline test module in `cast/mod.rs` into a dedicated crate-level test suite. The goal is to improve test organization, maintainability, and discoverability by creating separate test files for different cast families, similar to the Parquet crate's structure.

This issue is a call for contributions to a repository, expanding from its initial focus on collecting calculus midterm exams. The maintainers are now seeking a broader range of resources to add to the library.

The user reports that the `kubelet --eviction-max-pod-grace-period` parameter does not behave as documented when set to a negative value. Instead of deferring to the pod's `TerminationGracePeriodSeconds`, it appears to always send -1 to the CRI runtime, resulting in immediate container termination (SIGKILL) during soft eviction.

This issue is a request for user feedback on a new sensor page layout in version 0.15.0b3, specifically focusing on mobile usability. The changes aim to simplify tab structures, consolidate settings, and improve the overall user experience by making information more accessible and consistent across different sensor types.

The Heading 1 typography preview on the Sistent Design Tokens documentation page overflows and clips on smaller mobile viewports. This causes awkward text wrapping and makes the heading unreadable at widths around 414px and 360px. The expected behavior is for the preview to adapt responsively without overflow.

The user is reporting a bug where WebdriverIO's `getCSSProperty` command fails when trying to retrieve CSS custom properties (e.g., `--probe-size`) or when used with pseudo-elements (`::before`). This is contrary to the behavior of the native `getComputedStyle` API, which successfully retrieves these values.

This issue proposes switching the random number generator (RNG) in moocore from NumPy's MT19937 to PCG64 or PCG64DSXM. The author notes that MT19937 has known statistical weaknesses and can be slower on 64-bit systems, suggesting the change for improved performance and statistical robustness before a 1.0 release.

The user wants to execute JavaScript within a WordPress widget in Freescout, which is currently blocked by Content Security Policy (CSP) restrictions. They propose a solution involving dynamically injecting a nonce attribute into script tags by parsing the CSP meta tag, and are seeking feedback or implementation assistance.

This bug report highlights discrepancies between Gravitino's documentation (including OpenAPI definitions and Markdown examples) and its actual implemented REST and Java APIs. The issues involve incorrect field names for null ordering, outdated function alteration operations, misleading documentation on updating function comments, and inaccurate OpenAPI schemas for Python function implementations.

This feature request proposes renaming macro parameters named `__TIME__` within the STM32 HAL driver. The current naming convention conflicts with predefined C macros, causing build caches like ccache to disable their efficient direct mode, leading to significantly slower rebuild times. Renaming these parameters will resolve this issue without affecting the functionality of the macros.

This issue requests the implementation of comparison traits for `Box<[Item], Heap>`. The goal is to enable direct comparisons of boxed slices allocated on the heap, without requiring any other modifications to the codebase.

This issue reports a memory leak in the OpenSSL library related to the `X509_ALGOR_set0()` function, specifically within the `key_to_pubkey()` function. The leak occurs because a string (`str`) is not properly freed on failure, contrary to an incorrect comment, and was missed in a previous fix.