Find meaningful ways to contribute

This issue is a beginner-friendly task to add a new color theme called "Kyoto Kimono" to the KanaDojo project. It requires no coding and can be completed entirely through the browser by editing a JSON file. The contributor needs to fork the repository, add the theme details to a specific JSON file, and submit a pull request.

This issue is a beginner-friendly task to add a new fun fact about Japan to a JSON file. No coding is required, and the contribution can be made directly through the browser in under a minute, making it ideal for first-time open-source contributors and Hacktoberfest participants.

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 making the OPNsense Gateway plugin an official plugin within the OPNsense ecosystem. The core task involves adhering to the contribution guidelines outlined in the provided link to integrate the plugin.

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 Datadog tracing support within the project. It involves integrating the `dd-trace-ot` library and potentially leveraging Datadog's own tracing annotations to enable distributed tracing capabilities, similar to how Micronaut's `@NewSpan` and `@ContinueSpan` annotations work.

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 is a follow-up to a previous one that updated CI workflows. It aims to update several other GitHub Actions workflows (`release.yml`, `pages.yml`, `deploy-docs.yml`, `npm-publish.yml`) to use current major versions of their respective actions. The primary focus is on `release.yml`, and it requires verifying changes against release notes before updating.

This issue serves as a discussion point to identify and backport specific changes made in the mainnet integration of "indiv pallets" to the "paseo" testnets. The goal is to ensure test environments mirror production configurations, with an initial example being the `TxExtensionVersion` which is backward compatible and would improve parity with Polkadot.

This issue tracks the ongoing development and optimization of batch invariant feature for LLM inference, building upon existing work. Key tasks include integrating various hardware and software optimizations like Flashinfer, DeepGEMM, Torch compile, and Cuda Graph support, as well as improving usability and documentation. Some aspects, like FLASHINFER_MLA support and further performance optimizations, still require community help.

The `tinypool` package, when configured as an ES module (`"type": "module"`), fails to correctly access its `package.json` version. This is because the `__dirname` global variable, used in the `Tinypool.version` getter to locate the `package.json` file, is not defined in ES modules, leading to a `ReferenceError`. The issue is likely unnoticed as it only affects direct access to the `version` property.

This issue aims to fix silent truncation of long documents in the legacy `ModelSpanExtractor` path. The current implementation stops processing sentences once a `max_length` limit is hit, discarding all subsequent sentences. The goal is to implement a sliding-window approach for this legacy path, similar to the v2 path, to ensure all sentences are considered and scored, while preserving original sentence order and handling potential aggregation of scores.

This issue proposes to refactor the fuzzy span validation in `LLMSpanExtractor` to use an asymmetric scoring model. The current symmetric approach using RapidFuzz's `partial_ratio_alignment` incorrectly handles certain cases. The new model will ensure all extracted content exists in the source in order, while allowing specific source-only artifacts between matched content.

The frontend's `package-lock.json` file is pinning several vulnerable transitive dependency versions, including critical ones like Vite and Rollup. These vulnerabilities can be resolved by simply updating the lock file using `npm audit fix`, without altering the `package.json` dependencies or requiring a `--force` flag. The goal is to regenerate the lock file and commit it, ensuring no new vulnerabilities are reported and the build process remains successful.

Nine components in the frontend are unreachable and import non-existent modules, causing build issues only on case-sensitive file systems like Linux. The proposed solution is to delete these unused components as they are remnants of a previous UI library.

This issue proposes adding validation checks to OpenSSL's X509V3_EXT_nconf_nid and X509V3_EXT_nconf functions. The goal is to prevent the use of specific keyUsage extension bits (keyEncipherment, dataEncipherment, keyAgreement, encipherOnly, decipherOnly) for ML-DSA keys, as mandated by RFC 9881.

This issue describes a bug in OpenSSL's CRL scope checking where it incorrectly accepts a CRL if the distribution point omits the `distributionPoint` field but includes `cRLIssuer`. The current implementation fails to perform the required name comparison between the IDP and `cRLIssuer` as specified by RFC 5280, potentially leading to revoked certificates being incorrectly covered by an out-of-scope CRL.

This issue proposes adding a dedicated health check abstraction to the Parallel Consumer interface. Currently, users approximate health by checking if the consumer is closed or failed. An unmerged pull request exists that implements this feature, and it's considered a top revival candidate, suggesting a good starting point for implementation.

This issue identifies a memory leak vulnerability in OpenSSL's ASN.1 handling for EC private keys. Specifically, the `privateKey` field within the `EC_PRIVATEKEY` structure is not properly cleansed during deallocation, unlike RSA keys which have a dedicated callback for this purpose. This oversight could lead to sensitive private key data persisting in memory after it should have been freed.

The documentation for the `OPENSSL_INIT_LOAD_CONFIG` flag in `OPENSSL_init_crypto` is misleading. Users interpret "This is a default option" to mean configuration loading happens even without the flag, but code suggests the flag is necessary. The documentation needs clarification to accurately reflect that the flag must be explicitly provided to load configuration files.

This RFC proposes refactoring the `vllm_omni_async_server.py` file to align it with the upstream `verl` project and remove temporary patches. The current implementation has diverged significantly, leading to behavioral differences, code complexity due to interleaved logic, and reliance on fragile, untested workarounds.

This issue proposes adding a CI check to verify the syntax of shipped man pages using a real man-page parser like `mandoc` or `groff`. The goal is to catch syntax errors that existing structural tests might miss, ensuring the man pages are correctly formatted and renderable before release. The check should be fast, require no network access or special privileges, and not introduce broader style policies.

Tests in the 4.1 master branch are frequently hanging during OpenSSL shutdown, a problem not present in 4.0.2. The hangs occur in unthreaded 64-bit builds on Nonstop x86 systems, potentially related to signal handling. The user requests assistance in debugging and isolating the root cause.

This issue addresses the omission of typed DSL accessors for two Kubernetes resources, PodCertificateRequest and DeviceTaintRule, in the Kubernetes client library. The goal is to add specific methods for these resources to improve type safety and IDE support, similar to how other resources are handled. This involves updating interfaces, implementing client methods, and adding corresponding tests.

This issue describes a bug where Bitbucket providers for publishing inline comments incorrectly expect a line number as an integer, while the base contract and other providers expect line text. This inconsistency leads to API errors when callers adhere to the base signature. The fix involves resolving line text to a line number, similar to how other providers handle it, and adding a payload test to ensure this behavior.

The current slider nodes in menus use the default Godot theme, making them visually inconsistent with the rest of the hand-drawn user interface. This issue requests that the sliders be restyled to match the established aesthetic, improving the overall visual harmony and user experience.

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.

The user is requesting that an AppImage be published for the project. This would provide a convenient, self-contained way for Linux users to run the application without needing to install it through a package manager.

A user is experiencing a timeout when attempting to call a simple `Echo` tool via `@modelcontextprotocol/inspector`. The issue occurs even though the connection to the ASP.Net Core server on local Kubernetes is successful. No logs are available, and Postman also reports no tools found on the server.