Find meaningful ways to contribute

The `generateRandomString` function in `CryptoUtils` currently accepts any length value, leading to potential low-level errors with invalid inputs like negative or fractional lengths. This issue requires adding validation to ensure only non-negative safe integer lengths are accepted, providing a clear contract for callers and preventing unexpected behavior.

This issue proposes to improve email address validation by rejecting malformed addresses containing repeated dots, or leading/trailing dots in the local or domain parts. The goal is to ensure that only deliverable email addresses are accepted by the system, preventing potential issues with support and KYC configurations.

This issue requests the addition of a configuration reference for optional sections of the project's documentation. It aims to clarify the purpose and current status of fields within operational, metadata, logging, monitoring, and plugin sections, which are currently not well-documented. This will help contributors understand which options are active, host-owned, or planned before implementing new features.

This issue requests adding guidance on how to gracefully shut down an Express host, specifically addressing how to close the HTTP server and prevent duplicate signal handlers. The goal is to provide a clear example for releasing resources like queues, databases, and listeners in a predictable order during shutdown.

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 beginner-friendly task to add a new regional Japanese dialect entry to a JSON file. It requires no coding and can be completed directly in the browser by forking the repository, editing the specified file, and submitting a pull request.

This issue serves as a comprehensive onboarding guide for Juan Yepez, a new developer joining the Hack for LA Website team. It outlines a sequential list of action items, including attending onboarding, setting up the development environment, and understanding team processes, which will remain open throughout his tenure on the team.

This is a feature request to create a new component: an animated multi-select dropdown with a cyberpunk aesthetic. The implementation should be pure CSS, leveraging existing design tokens and animations, and must be responsive and accessible, including support for reduced motion.

This issue is a "good first issue" that requires adding a new trivia question about the Japanese term for a convenience store to a JSON file. No coding is involved, and the task can be completed directly in the browser within a minute.

The user is reporting that the kernel parameter `xe.enable_psr=0` is no longer necessary for a display fix on their Asus Expertbook running a 7.1.6-1 kernel with OpenSUSE Tumbleweed. They are suggesting this parameter might be redundant and can be removed.

The user is experiencing issues with a custom download script on Android's Via browser when downloading more than 20 images from a post. The script sometimes fails to capture the correct number of images and occasionally uses an incorrect naming convention. The provided script adds a large download button and attempts to leverage existing download functionality or simulate clicks on download buttons.

This issue requests a community contributor to run the Claude Opus 5.5 model on the Enterprise-Bench L1-L2 benchmark and submit reproducible results to the public leaderboard. The goal is to evaluate Opus 5.5's performance on retrieval and analytical tasks, comparing it to previous Claude versions and assessing its claimed improvements for professional work.

This task involves researching the fairness of a 'ladder' (likely a performance benchmark or optimization) in relation to Spark's default input path and code generation. It requires comparing performance metrics against stock Spark 4.2.0 and potentially adding new benchmark arms to reflect a typical user's setup.

This issue proposes adding dark mode support to charts and the correlation heatmap, which were not included in the initial dark mode implementation. The goal is to dynamically derive chart and heatmap colors from the active theme, ensuring they render correctly in both light and dark modes without hardcoded palettes. This includes updating `ChartRenderer.tsx` and `CorrelationHeatmap.tsx` to use theme context and ensuring the heatmap's SVG export remains legible.

This issue asks users to test a new self-signed client certificate generation script on their appliances. The goal is to determine if the certificate works by default or if it fails authentication, providing appliance models for both success and failure cases to help identify firmware variations in certificate validation.

This issue tracks the remaining work for Linux support, focusing on the reliability and desktop compatibility of existing x86_64 AppImage and .deb packages. It details a specific AppImage catalog failure related to permissions and a glibc dependency, and outlines follow-up tasks including reproducing the error, fixing packaging issues, validating on real desktops, and verifying X11/Wayland behavior.

This issue proposes adding support for true 3-point affine transformations to the image processing pipeline. Currently, the operator only supports translation by manually constructing a translation matrix. The goal is to replace this with `cv2.getAffineTransform` which takes three source and three destination points, and to update the frontend block to expose these twelve coordinates.

This issue proposes adding a camera focal length control to the monitoring screen. The control will support both autofocus and manual focus modes, giving users direct control over the camera's focal length.

This feature request proposes adding a sorting option based on file creation date to address an issue where the 'date added' sort order becomes inaccurate after transferring music files. The current 'date modified' sort is not ideal as it changes with file edits. Implementing a file creation date sort would provide a stable and accurate way to order files as they were originally added.

The `parseXdrTransaction` function currently defaults to using the testnet passphrase, which can lead to incorrect transaction parsing when operating on other networks like public or futurenet. This issue proposes adding an optional network or passphrase parameter to allow callers to specify the correct network context, ensuring accurate hash and signature checks.

This pull request introduces enhanced control over the positioning of scale bar units in QGIS layouts. Users can now choose from a variety of placement options, including before/after the bar, above/below, and relative to distance labels, offering significantly more flexibility than the previous fixed placement.

This issue addresses a validation problem in the framework's plugin configuration where empty or duplicate plugin IDs are currently accepted. The task is to enforce non-empty, trimmed plugin IDs and reject duplicates to prevent silent overwrites and ensure stable identifiers, while leaving plugin-specific configurations unchanged.

This issue tracks efforts to stabilize flaky CI tests that are causing delays and consuming contributor time. The problems stem from race conditions with background work and intermittent hangs in tests related to health monitoring and RESP operations. The issue breaks down the work into three specific, independently claimable sub-tasks.

This issue addresses flaky test behavior in the `k3-multiprocess-test` suite where the time-to-first-token (TTFT) metric fluctuates, causing intermittent test failures. The goal is to modify the test script to ensure that L2 data-flow diagnostics are captured and checked even when performance thresholds are not met, preventing the test from exiting prematurely and masking potential issues.

This issue addresses a flaky test in the vLLM project that intermittently fails its time-to-first-token (TTFT) threshold. The problem arises because the test overwrites raw timing data when running the baseline and LMCache phases sequentially, making it difficult to investigate the cause of the flakiness. The proposed solution is to preserve separate per-request timings for both phases.

This issue aims to fix a flaky benchmark test in vLLM that shows inconsistent throughput results. The goal is to make the benchmark inputs reproducible by using a stable default seed and to improve auditability by saving a manifest of key parameters and results. This will help in understanding and resolving the intermittent performance fluctuations.

This issue requests the addition of a delete functionality for service points, as currently only an 'inactive' option exists. The proposed solution is to allow deletion of service points, with a safeguard to prevent accidental data loss by restricting deletion to service points that have no associated records like appointments or queues.

The `ValidationUtils.isValidStellarAddress` function currently only validates classic Ed25519 public keys, but payment XDRs can accept both classic and muxed accounts. This issue proposes to either update the existing validator to support muxed addresses or add a new one, ensuring consistent account validation across payment construction and validation utilities.