Zig good first issues

This issue tracks the ongoing effort to expand the supported programming languages within a project. The "Shipped" section lists languages already implemented, while the "Plan" section outlines languages yet to be added. The maintainers are also soliciting community input on which languages users would prefer to see supported next.

This feature request aims to improve the robustness of MLX Core's server by implementing an automatic restart mechanism for unexpected crashes. Currently, when the `mlx-serve` process terminates unexpectedly, it displays a modal alert and remains stopped, requiring manual intervention. The proposed solution involves automatically relaunching the server with the last used options, incorporating a backoff strategy for retries, and providing non-blocking notifications during the restart process.

The user wants to generate video clips longer than a single window (10-15 seconds) while maintaining identities from reference images using mlx-serve. They are encountering a conflict where chaining windows and using REF2VA references are mutually exclusive, as chaining relies on FL2VA keyframe conditioning. The user is seeking a supported method or proposing this as a feature request, drawing parallels to a solution in the ComfyUI ecosystem.

This issue proposes adding a compiler warning and `roc fmt` behavior to handle redundant explicit exposures of a type module's main type. When a type module is imported, its main type is automatically brought into scope, making explicit re-exposure unnecessary and potentially confusing.

This issue proposes adding multi-language support for the application's user interface, specifically mentioning Japanese and Chinese as initial targets. It's marked as an enhancement and is seeking community contributions.

The CI pipeline is failing because the project's bundle size has exceeded 1MB. The proposed solution is to increase the allowed bundle size limit to 5-7MB, citing that comparable tools are larger. This is tagged as a bug and help wanted.

This issue proposes adding an optional idle timeout feature to automatically unload models after a period of inactivity. This would free up unified memory on Macs with limited resources, improving performance when running large models. The next incoming request would then reload the model.

This issue proposes an enhancement to the `git status` command to provide more detailed information. The suggested `lgtm status` command would display file statuses, line additions/removals per file, total line changes, and the last modification time for each file.

This issue aims to track and implement missing built-in functions for the Zig compiler, using modern Roc API conventions. The goal is to ensure all necessary built-ins are declared, implemented, supported by backends and interpreters, and tested, while prioritizing pure and Try-returning functions over effectful collection variants.

The Apple II support within the llvm-mos-sdk is currently based on an incomplete and likely unsupported package. This issue calls for improvements to address these deficiencies and ensure robust Apple II compatibility.

The task is to add Emscripten support to the SDL3 Zig project. This involves configuring the build system to correctly compile and link SDL3 for the Emscripten target, potentially requiring adjustments to the build scripts and handling of Emscripten-specific dependencies. The project README provides guidance on adding support for new targets, including examples for Linux and Windows.

This issue requests the implementation of all remaining WASI preview1 functions. Currently, many file system, path manipulation, and clock-related WASI functions are not supported, while some basic functions like argument retrieval, environment size, clock time, and I/O operations are implemented. The goal is to achieve full WASI preview1 compatibility.

This issue proposes removing a temporary override for the 'undici' package in the project's pnpm workspace configuration. The override was added to resolve Dependabot alerts but is no longer necessary if the 'miniflare' dependency requires 'undici' version 7.29.0 or higher. Removing it will prevent potential deployment failures caused by the override forcing an older version of 'undici'.

The user is seeking help testing the `lgtm` tool with various terminal multiplexers and built-in terminal features like ghostty, kitty, and wezterm. They are specifically asking for feedback on any issues encountered when using `lgtm` with these alternative tmux-like functionalities.

This issue requests that when `csvql` is run with only a CSV file path (no SQL query), it should provide a more informative summary before the data preview. This summary should include row and column counts, column names with inferred types and potentially null/distinct counts, and 2-3 example queries tailored to the CSV's structure. The goal is to make the no-query mode a useful data exploration tool.

The user is requesting support for a device named 'Vader 3 Pro'. The issue is currently marked as 'needs-info', indicating that more details are required to understand the scope and feasibility of adding this support.

This issue proposes enhancing the query fuzzer to generate SQL queries that include `SELECT DISTINCT` clauses and scalar functions (like `UPPER`, `LOWER`, `TRIM`, `ROUND`, `DATEDIFF`, `DATEADD`, `EXTRACT`) within `WHERE` clause comparisons, especially when combined with `AND`/`OR`. This aims to improve test coverage for previously unfuzzed but supported SQL features, which have historically led to parser bugs.

The differential fuzzer for DuckDB currently only generates queries with a simple `ORDER BY id`. This issue proposes enhancing the fuzzer to include more complex sorting scenarios like `ORDER BY DESC`, multi-column `ORDER BY`, and positional `ORDER BY` clauses, which are supported SQL features but not currently tested.

This issue proposes adding two new SQL string functions, LPAD and RPAD, to the project. These functions will pad a string column to a specified length with a given character, with a default of space if no character is provided. The implementation is expected to be straightforward, building upon existing multi-argument string function patterns.

This issue requests the addition of a new `REVERSE` string function to the database system. The implementation should follow the pattern of existing string functions like `UPPER`, `LOWER`, and `TRIM` in the `src/scalar.zig` file. This involves updating function name detection, adding an enum variant, implementing the evaluation logic, documenting the new function in the README, and adding a unit test.

This issue proposes adding a new SIGN scalar function to the database system. The function will take a single numeric argument and return -1, 0, or 1 based on the sign of the input. The implementation is expected to be straightforward, following the pattern of existing scalar functions like ABS.

This issue requests the addition of two new scalar functions, SQRT (square root) and POWER (exponentiation), to the SQL engine. The implementation should follow the pattern of existing scalar functions like ABS, CEIL, and FLOOR, involving updates to `src/scalar.zig`, the SQL Reference in `README.md`, and a new unit test.

The `extended-const` WebAssembly proposal is implemented and passes existing unit tests, but it lacks dedicated spec-corpus tests. This means regressions in its decoding or evaluation might go unnoticed. The proposed solution is to vendor the upstream proposal test files into a new corpus sub-directory and update the manifest to include `extended-const`.

This issue proposes to upstream a zwasm adapter to the official WebAssembly/wasi-testsuite repository. This will allow for independent verification of zwasm's WASI preview1 conformance and increase its visibility within the WebAssembly ecosystem.

Several toolchain directories expected for Phase 10 exit criteria are empty or only contain a `PROVENANCE.md` file, leading to a false positive in the testing lane. This issue stems from the runner not accounting for its own denominator, as prescribed by ADR-0210, and prevents accurate verification of GC and EH toolchain support.

This issue proposes to standardize the display of timing breakdowns in the CLI to use milliseconds consistently for all completed phases. This change aims to improve readability by preventing the mixing of units (like 'ms' and 's') which can make slow phases difficult to spot. The proposed solution includes formatting durations with underscores for thousands separators and right-aligning them for better scanning.

This issue requires verifying that the OTLP implementation correctly handles trace IDs and span IDs as hexadecimal values when exporting via OTLP JSON. The current implementation might be treating them as plain strings, deviating from the OpenTelemetry specification. A proposed solution involves a custom deserialization method, similar to what's used in the Go implementation.

This issue proposes adding hyperlink support to the project, similar to what is available in 'eza'. This feature would make entries clickable, enhancing user interaction. The author is not personally interested in implementing it but believes it could be a valuable addition for others.