Find meaningful ways to contribute

This issue requests the addition of a README file to the Python console example application. The README should explain what the example demonstrates, how to run it, where the output is located, and clarify the RGBA requirement and dependencies. It also asks to correct a misleading comment in the Python script.

This issue requires a complete rewrite of the Spanish version of the 'Creating links' documentation page to align it with the latest English version. The current Spanish translation is based on an outdated English source and has structural differences, including a different number of sections and an incorrect `original_slug` in the front-matter.

This issue requests a full synchronization of the Spanish version of the 'HTML table basics' documentation with its English counterpart. The task involves comparing the entire document, translating any missing or outdated content, and ensuring the structure, headers, and order of sections match the English source. The `l10n.sourceCommit` also needs to be updated to the latest English SHA.

This issue requires updating the Spanish translation of the 'Responsive Design' page to match the latest English version. The Spanish version is significantly outdated and needs a complete rewrite due to structural changes in the English source since the last synchronization. The task involves comparing the English source, updating the Spanish content, and removing outdated metadata.

This issue requests a complete rewrite of the Spanish translation for the '2D Breakout Game with Phaser' tutorial. The English source has been significantly updated, and the current Spanish version is outdated, requiring a full re-translation and structural alignment with the new English content. The task involves ensuring consistency in headings, code examples, and macros, while also updating the `l10n.sourceCommit` to reflect the latest English version.

The `usePlugins` hook, responsible for aggregating 25 plugin factories for the marketplace catalog, currently has 0% unit and end-to-end test coverage. This lack of testing means potential issues like duplicate plugin IDs, missing fields, or broken translator wiring could go unnoticed, impacting marketplace listing correctness. The recommendation is to add direct unit tests using `renderHook` to verify the catalog's integrity and recomputation.

The documentation for npm scripts in the `docs/docs/internal/scripts/` directory is outdated and describes commands that no longer exist after a monorepo refactor. This issue requires updating these documentation pages to accurately reflect the current set of available scripts, which now primarily use `just` and are located in different `package.json` files.

This issue proposes two enhancements for callable bonds: implementing American-style optionality and adding a "notice period" feature. The notice period would allow for pricing in a mandatory delay before a bond can be called, eliminating the need for manual adjustments to the call schedule.

On Windows, the update progress bar in the 'About' settings page appears visually incorrect, stopping partway across its row. This is due to a `max-width` constraint on the progress bar's track, causing it to not fill its containing column. The proposed solution is to remove the `max-width` to ensure the progress bar spans the full width of the row.

This issue identifies several incorrect links and swapped content within the project's documentation, specifically in the API bindings tables. The C and JavaScript API references are linked to the wrong pages, and status badges point to incorrect source directories. Additionally, a "refactor" issue template link is broken and needs to be corrected to point to the existing "feature request" template.

This issue is a beginner-friendly task for Hacktoberfest, asking contributors to add a single markdown line to a specific file in the repository. No coding or local setup is required, making it accessible for absolute beginners.

This issue proposes integrating Git's new reftable reference backend into the git2-rs library. The goal is to ensure seamless integration by testing the reftable support that has already been merged into libgit2's main branch.

The user is requesting an update to the bibliography template, which currently uses `biblatex-gost` with the `gost-numeric` style. This style adheres to the outdated GOST 7.1-2003 standard. The user points out that GOST R 7.0.100-2018 is the current standard in Russia and highlights specific formatting differences that need to be implemented.

The `validate-scripts` command crashes with a TypeError when a `package.json` script lacks a corresponding `scriptsInfo` entry. This issue occurs because the script incorrectly assumes the presence of `_meta` and its `ignore` property, leading to a crash instead of a clear error message. The fix involves treating missing `_meta` or `ignore` properties as empty lists to ensure the intended validation message is displayed.

The C API documentation contains usage examples with incorrect image buffer sizes, leading to memory corruption. The examples assume RGB or greyscale images but the underlying functions expect RGBA, causing buffer overflows. Additionally, the documentation lacks clarity on memory ownership for SVG functions, the error API, and correct CMake linking.

This enhancement proposes exposing the current test partition number to tests. This would allow tests to create partition-specific resources, such as sharded databases, improving test isolation and reliability when running large, computationally expensive test suites across multiple processes.

This issue requires a minor documentation update in the `CATALOG_LISTING.md` file. The goal is to correctly list Db2 LUW as supporting inline row editing in two specific sections of the file, aligning it with the actual capabilities defined in the codebase. The contributor explicitly states this is a small fix with no local setup needed.

This issue addresses several bugs in the `console-c` example application. The primary problems include a failure on fresh builds due to incorrect directory creation, the second SVG output being discarded, memory leaks in error paths, and a lack of informative error messages. Additionally, there are minor issues with missing header includes and inconsistent error output.

The MIGraphX Python API does not expose settings to control the logging level, preventing users from suppressing INFO messages. The `migraphx::log::set_severity` function, which controls logging levels, is not integrated into the Python API or accessible via environment variables.

The `OptimizeInstructions` pass incorrectly lowers `memory.fill` operations with a constant value and size 16 into two `i64.store` instructions. This can lead to partial writes and incorrect behavior when the operation is out of bounds, as the first store might succeed before the second traps, altering memory state unexpectedly.

The Docker Compose quick start guide for Hive incorrectly leaves the dashboard port at 3001 in `src/hive.yaml`. This conflicts with the Node proxy, causing the `hive` container to fail its healthcheck and preventing the gateway from starting. The suggested fix is to update the documentation to instruct users to change the port to 3002.

The "Edit this page" links on the website currently point to the `main` branch, which is not where pull requests are accepted. This causes users to incorrectly propose changes to `main` and have their pull requests fail. The fix involves changing the `editUrl` configuration to point to the `dev` branch instead. Additionally, a minor typo in the `EditThisPage` component's styling needs to be corrected.

The `img2num` Python wheel incorrectly includes files unrelated to the Python package, such as a Docker launcher script and static library files, in the `site-packages` directory. This is likely due to incorrect configuration in `pyproject.toml` and scikit-build-core's build process, causing potential namespace collisions and unintended installations.

This issue proposes adding an optional seed to the K-Means algorithm to ensure reproducible results. Currently, the algorithm uses `std::random_device` for seeding, leading to different outputs on each run, which hinders testing and comparison. The proposal includes design questions regarding API integration across different bindings (C++, C, Python, JavaScript) and the exact reproducibility guarantees, considering potential differences in standard libraries and GPU drivers.

This issue proposes refactoring the `labels_to_svg` function in C++ by removing unused code. Specifically, it targets an unnecessary recolor pass, dead helper functions like `visualize_contours`, and unused local variables. The goal is to simplify the code and reduce its size without altering the SVG output.

This issue proposes adding a `__version__` attribute to the `img2num` Python package. Currently, attempting to access `img2num.__version__` results in an `AttributeError`. The proposed solution is to define this attribute in the `__init__.py` file, either by reading from installed metadata or using a literal value that is automatically updated during releases.

Code blocks for shell, PowerShell, batch, and CMake are not rendering with syntax highlighting on the documentation website. This is because these languages are not included in the Prism build bundled with Docusaurus. The fix involves adding these languages to the `additionalLanguages` configuration in `docs/docusaurus.config.js` and retagging a few specific code blocks.

The `labels_to_svg` function in the `img2num` library is producing non-deterministic output. When called multiple times with identical image and label inputs, it generates different SVG files, indicating an underlying issue with how neighboring nodes are processed and compared.

This issue addresses several inaccuracies in the JSDoc comments within the `safeWasmWrappers.js` file. The goal is to correct descriptions, remove stale to-do items, and fix typos to ensure the generated API documentation accurately reflects the code's behavior. No functional changes to the code are required.

This issue proposes to fix two logging problems in the core library. First, it suggests redirecting all library logs from stdout to stderr, which is the standard practice for diagnostics. Second, it aims to assign appropriate severity levels (ERROR, WARN, INFO, DEBUG) to existing log messages, as currently all messages are logged as INFO, making it difficult to filter or prioritize them.