Find meaningful ways to contribute

This issue aims to investigate and reduce latency variance in checkpoint state-store benchmarks for Apache Seatunnel. The goal is to identify the source of this variance, whether it's in the production code, benchmark setup, or execution environment, and then optimize the production code if a bottleneck is found, while ensuring checkpoint correctness.

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 addresses the asynchronous nature of Web Components, which can cause timing problems when interacting with them, such as using lifecycle modifiers like `onMountFocus`. The author needs to understand the Web Components loading timeline, specifically the `WebComponentsReady` event, to determine when it's safe to interact with components and how to handle cases where components are added dynamically. The goal is to improve Laminar's integration with Web Components.

This RFC proposes a standardized approach for kernel reuse and hardware integration within vLLM-Omni, which supports various AI models like diffusion and speech. The goal is to create clear contracts for shared computations, enabling easier integration of new consumers and backends by addressing variations in tensor shapes, ownership, and execution requirements, exemplified by three diffusion model cases.

Kubestellar hive agents are failing to start, reporting a false lack of Copilot license. This issue began after the agents were configured to use Copilot, despite the user being a member of the CNCF Maintainers organization, which should grant them a license.

This issue serves as an umbrella request for community members to claim and implement new data connectors. It lists various connectors, their current status, and associated issue numbers for claiming. Contributors are asked to claim work by commenting on the relevant issue and update the table accordingly.

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.

This issue is a "Good First Issue" that asks contributors to add a new trivia question about Japanese festivals to a JSON file. No coding experience is required, and the task can be completed directly in the browser within a minute.

The upstream CNI version 1.22.1 requires additional IAM permissions for subnet discovery, which are not currently included in the Terraform module. This can cause the CNI to fail on startup. The issue suggests adding two specific IAM permissions to the `node_groups.tf` file to resolve this.

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.

A bug in the host orphan reaper causes it to permanently wedge, leading to a massive accumulation of zombie processes. This is due to a head-of-line blocking issue where a tracked PID prevents further reaping, compounded by leaked runner entries and PID reuse, which creates a persistent zombie that stalls the entire process.

This issue reports six broken links (404 errors) found in the project's published README file. The reporter has identified potential replacement links for some of these broken entries, but further verification of content match is needed. The issue also clarifies that some links returning 403/502 errors are due to bot filtering and not actual link rot.

This issue proposes to improve the test coverage across various packages within the reposcan project. The goal is to reach near 100% test coverage for all packages, with a specific list of current coverage percentages provided. Contributors are asked to comment if they are working on a particular package to avoid overlapping efforts.

The user is asking how to increase the default 10MB upload limit for Telegram within the application. They suspect the relevant settings might be the `BATCH_SIZE` and `INDEX_CHUNK_SIZE` variables in `functions/utils/indexManager.js` and are seeking confirmation or guidance on modifying these values.

This issue identifies significant code duplication and large file sizes in the `Navbar.tsx` and `DocsNavbar.tsx` components. The `DocsNavbar.tsx` component re-implements logic already abstracted into tested hooks in `Navbar.tsx`, specifically for fetching GitHub stats and managing dropdown states. The proposed solution involves extracting the duplicated logic into shared hooks and further abstracting the search functionality into a new hook.

This issue is an umbrella task to migrate existing imperative validation logic (if/throw checks) in Seatunnel's connector and transform components to a new declarative `optionRule()` system. The goal is to improve maintainability and expressiveness of validation rules using predefined conditions like numeric ranges and cross-field comparisons. This is Phase 2 of a larger effort, with the framework already in place.

Three separate PrometheusRule resources are defining overlapping and conflicting alerts for the docs API. This leads to duplicate alert notifications with inconsistent thresholds and a lack of runbook links for some alerts, making it difficult for responders to understand and address issues.

NetBSD runtime tests are experiencing intermittent failures following a recent code change (CL 526118). The failures appear to be concentrated in OS thread-specific tests, suggesting a potential connection to the recent CL.

This issue reports intermittent, unreliable failures occurring on NetBSD systems running on ARM architecture. The provided code snippet suggests a mechanism to filter for these specific environments, indicating a need to consolidate and investigate these flaky tests in a central location.

This issue reports intermittent test timeouts specifically on the s390x Linux architecture. The timeouts appear to be related to the Go runtime, potentially involving finalizers or I/O operations exceeding their deadlines. Further investigation is needed to pinpoint the root cause of these flaky tests.

This feature request aims to improve experiment lifecycle decisions by ensuring they are based on complete metric evaluation. Currently, the system aggregates metric results, potentially masking issues where individual metrics are missing or failed, leading to inaccurate decisions. The goal is to provide users with clear visibility into which metrics were evaluated and how their completeness impacts the final recommendation, ensuring decisions are only made when all expected metrics are accounted for.

This issue proposes a feature to link lifecycle experiment decisions to their immutable launch configurations. Currently, experiment data can be correlated by IDs but not definitively tied to the specific configuration active at launch, leading to potential issues with configuration drift affecting later analysis. The goal is to ensure that experiment evidence is always bound to the exact configuration that produced it, preventing incorrect recommendations due to changes after launch.

This issue addresses a bug in trigonometric functions where large finite floating-point angles are not accurately reduced. The current method of taking the remainder against 2π loses precision for very large inputs, leading to incorrect results in `sin_f64`, `cos_f64`, and `tan_f64`. The fix requires a more robust range reduction strategy that preserves phase information for large magnitudes and includes comprehensive accuracy tests.

This issue describes a bug where non-ASCII byte escapes (\xNN) in string literals are incorrectly converted to Unicode characters instead of preserving their raw byte values. This leads to incorrect UTF-8 encoding and potential issues with embedded NUL characters. The goal is to ensure \xNN escapes represent exact bytes as documented and are handled correctly throughout the compiler frontend and backend.

This issue addresses inconsistencies in how the lexer handles carriage return (CR) and line feed (LF) line endings. Currently, CR is treated as whitespace but doesn't advance the logical line number, leading to discrepancies in token tracking, column calculations, and diagnostic reporting, especially in CR-only source files. The goal is to ensure consistent newline handling across all lexer operations, treating CRLF as a single newline and lone CR consistently.

The `memory_dir_exists` diagnostic check incorrectly reports a critical success even when the memory directory is not writable. This leads to silent failures when saving data. The proposed solution is to add a new `memory_dir_writable` check with critical severity, similar to how the audit log writability is handled, to ensure the directory is both writable and executable.

The `palinode doctor` command incorrectly references private issue tracker numbers in its diagnostic checks. These references, especially one linking to an unrelated public issue, can mislead users. The fix involves updating these references to point to valid public URLs or removing them entirely.

The `read_to_end` function in `std::fs::file` can experience a signed overflow when doubling the buffer capacity. This overflow is not checked, and the subsequent fallback logic can lead to an incorrect, smaller capacity, potentially causing issues with growth requests. The fix involves using checked arithmetic for capacity growth and ensuring appropriate error handling.