Lua good first issues

This issue requests the addition of the Topiary formatter package. Topiary supports a wide range of languages and is distributed through multiple package managers including Cargo, OPAM, Nix, AUR, and Homebrew. The request also notes that Topiary is used as a library in other projects.

The user is experiencing a 2-minute freeze every full hour after updating their code from a specific date. This issue was not present in a previous version of the code, suggesting a regression introduced in the recent update. The user acknowledges having many productions, which might be a contributing factor.

This issue is a template for community members to submit translations of project strings. It specifies a required format for submissions, including translator name and native language status, and allows for the removal of the '[EN]' prefix if no translation is needed. The goal is to facilitate the translation process for the project.

This issue identifies locations with existing public transport data on Google Maps that is not regularly published elsewhere. The goal is to contact these companies and municipalities to encourage them to make their data publicly available, potentially using provided email templates.

This issue addresses a visual bug where treadmarks left by units are no longer continuous lines. The problem stems from outdated `TreadMarksInterval` values in unit blueprints that don't align with recent speed adjustments. The fix involves identifying affected units and recalibrating this interval, potentially through a combination of automated analysis and manual visual inspection.

This issue details the platform dependencies of a system named 'finn' which runs on routers. It lists the specific system commands and files 'finn' uses for sensing various network and device states. The goal is to document what's needed to port 'finn' to other router operating systems like Asuswrt-Merlin and Ubiquiti EdgeOS.

This issue requests a new feature for the PIN lock screen to allow user notes to be permanently visible instead of requiring a tap to reveal them. The primary use case is to ensure contact information is easily accessible if a device is lost, particularly for a child's device.

The user reports that KOReader's swipe gestures, specifically a diagonal swipe for page refresh, fail to function when the user is zoomed into a panel on their Kobo Libra Color. This gesture works correctly when not zoomed in, indicating a potential conflict between zoom functionality and gesture recognition.

The user is requesting a feature to synchronize their annotations and thoughts made while reading with the WeChat Read (微信读书) application, similar to how reading duration is currently synchronized. This would allow users to have their reading notes accessible within the WeChat Read ecosystem.

This bug report describes an issue where Tarantool's test runs inadvertently write to the user's `~/.tarantool_history` file. The proposed solution is to introduce an environment variable that allows users to specify a different history file location, preventing this "spamming" during test execution.

This issue tracks the progress of translations for a project, indicating which languages have been completed. It serves as a checklist for ongoing translation efforts and encourages community contributions for new languages.

This feature request proposes adding an option to `pi.nvim` to connect to an existing, already running headless `pi` instance via RPC. This would allow users to manage separate sandbox profiles for Neovim and `pi`, granting them independent permissions while maintaining the `pi.nvim` user experience.

This GitHub issue is a call for player feedback on the 'Stress System' within an 'Advanced Damage System' mod. The goal is to balance breakdown probabilities so that players who adhere to maintenance schedules and use equipment appropriately do not experience unreasonable mechanical failures. Players are encouraged to report any perceived issues or share their 'success stories' using a provided template.

This issue requests the addition of support for MemorySanitizer (MSan) when using GCC version 7 or later, and Clang. This would involve integrating MSan's capabilities into the project's build and testing processes.

This issue addresses a validation flaw where duplicate component and capability IDs are accepted in device profiles, despite the schema indicating they should be unique. The problem is reproducible through an automated patching script and the `edgeloom validate` command fails to detect it, undermining the validator's assurance role.

This issue requests graphical updates for several in-game elements, specifically pipes for Steam Inserters, Electronics Assembling Machines, and Chemical Furnaces, as well as the base and shadow of a Water Miner. The 'help wanted' label suggests the developers are seeking contributions for these visual enhancements.

This user is requesting support for the Kindle Scribe device within the KOReader application. They are specifically interested in the device's pencil input capabilities for note-taking or annotation features within KOReader.

The user updated a plugin for KOReader on their Kobo Clara 2E, but it no longer appears in the menus. They have tried reinstalling it manually without success, and there are no relevant errors in the crash log. This suggests a potential compatibility issue or a problem with how the plugin is being registered after the update.

Tests for the haunt.nvim plugin are failing on macOS due to a path resolution discrepancy. macOS symlinks /var to /private/var, causing `vim.fn.tempname()` to return a path that Neovim resolves differently when setting the buffer name. This leads to tests failing because the expected and actual paths do not match.

A user is requesting support for stylus input on their reMarkable device within KOReader. They have provided output from `evtest` showing that the device generates pen input events, including `BTN_TOOL_PEN`, `ABS_X`, `ABS_Y`, `ABS_PRESSURE`, and tilt information, which could be leveraged for scribble functionality.

This issue describes a bug where commenting out top-level JSX elements in Neovim fails after the first attempt. The problem appears to stem from the `ts_context_commentstring` plugin incorrectly identifying the commented JSX as a JavaScript object on subsequent uncommenting attempts.

This issue requests an external security review of EdgeLoom's threat model and its implementation. Specifically, it asks if the current threat model accurately reflects the security implications of injecting executable Lua code into drivers and addresses the unresolved question of capability namespace usage in patched drivers.

This issue requests the addition of the 'spring-javaformat' package, a Java code formatter from the Spring ecosystem. The package is distributed via Maven Central and can be used as a standalone CLI tool by leveraging its VS Code extension's shaded JAR.

This issue concerns the behavior of the `--limit 0` option in discovery functions. Currently, a limit of 0 is treated as no limit, processing all eligible drivers. The developers need to decide whether to change this behavior to process zero drivers when `--limit 0` is specified, or to keep it as an alias for unlimited discovery and document it accordingly.

The `router.callbre()` function incorrectly resets the balancing cursor to the master node instead of rotating it. This leads to an uneven distribution of heavy requests, with the master node disproportionately handling them when mixed with lighter requests from `router.callbro()`.

The `edgeloom translate` command writes Home Assistant long-lived access tokens to a world-readable file (`config/ha_devices.yaml`) without being gitignored. The issue also points out that the token doesn't need to be written to a file at all, as environment variables are supported and recommended.

The user is requesting a feature to display damage absorption (like Warrior's 'Ignore Pain') on the player's health bar. They note that other UI addons already implement this functionality, suggesting it's technically feasible.

This issue requests the addition of capability mapping for an unmapped sensing driver within the EdgeLoom project. The goal is to expose useful device attributes that are typically omitted by stock drivers, such as sampling interval and sensitivity. The specific driver to be mapped will be chosen by someone knowledgeable about sensing modalities.

This issue proposes adding a new `restore` subcommand to the `edgeloom` CLI tool. This subcommand will provide a user-friendly way to restore a driver from its backup, mirroring the existing `patch` functionality and addressing documentation inconsistencies. The implementation requires modifying the CLI parsing logic and adding a new command handler.

The `--limit` flag in the `edgeloom discover` command incorrectly counts drivers that have a `fingerprints.yml` file, even if they don't contain any Zigbee fingerprints. This leads to the command returning no results when a small limit is set, as it might exhaust the limit on non-Zigbee drivers. The proposed solutions involve modifying how drivers are counted to ensure the limit applies to drivers that actually yield Zigbee fingerprints.