C good first issues

This issue proposes the integration of the QR-UOV signature algorithm, a NIST on-ramp candidate, into the liboqs library. The goal is to add support for this specific post-quantum cryptography algorithm.

This issue requests help to continue development for the VW e-Golf vehicle integration. An initial adaptation was started but stalled due to lack of a test car. The existing code accesses some OBD values, but the comfort CAN bus needs decoding and operates at a different speed than the e-Up.

This issue requests the removal of redundant catch-all implementation stubs from the `Color` type hints in `buildconfig/stubs/pygame/color.pyi`. These stubs are unnecessary after overload declarations and weaken type information. The goal is to ensure that each affected `Color.from_*` method retains only its complete overload signatures and its documentation.

This issue proposes creating a shell script to simulate various kernel stresses, including disk I/O, CPU contention, memory pressure, TCP retransmits, and file descriptor usage. The script is intended for demo purposes and integration testing of the `kerno doctor` tool, requiring root privileges and proper cleanup of resources.

This issue proposes adding comprehensive unit tests for the diagnostic rules within the `internal/doctor/rules.go` file. The goal is to ensure all 11 rules correctly identify signal conditions, including healthy inputs, warning and critical thresholds, and edge cases, with specific focus on ETA calculations for certain rules.

This issue proposes adding a new command-line flag `--rule <name>` to the `kerno explain` command. This flag will allow users to retrieve detailed documentation for a specific rule, including its signal, severity, trigger conditions, explanation, and suggested fixes, without invoking the AI analysis. It also specifies behavior for non-existent rules and when the flag is used without an argument.

This issue proposes adding micro-benchmarks for two critical, but currently un-benchmarked, operations: `Histogram.Merge` and `LRU.Put`. The goal is to ensure the performance of these hot-path functions is monitored and to prevent regressions. The work involves adding new benchmark functions in the `internal/collector/aggregator` package and ensuring they meet specific performance and reporting criteria.

This issue proposes adding a new "Chaos Engineering" section to the project's README file. The goal is to introduce users to the `kerno chaos` feature, explain its purpose, demonstrate its usage with an example, and provide a link to further documentation. This will make a powerful feature more discoverable and understandable for new users.

This issue identifies a bug where AI provider HTTP clients lack request timeouts, potentially causing indefinite blocking of the doctor cycle if a provider is unresponsive. The proposed solution is to implement timeouts either at the HTTP client level or by wrapping provider calls with a per-request context timeout to ensure graceful degradation.

The `doctor` tool incorrectly calculates the estimated time to file descriptor exhaustion. It uses a system-wide net change in file descriptors over an observation window instead of the actual open file descriptor count for a specific process. This leads to misleadingly optimistic ETAs, especially for processes already close to their limits.

This issue proposes refactoring the `rules_test.go` file to use table-driven tests. Currently, each rule and its test cases are defined as separate, repetitive functions. The goal is to consolidate these into a single table-driven test structure, improving readability and maintainability while preserving existing test coverage and enabling parallel execution of subtests.

The user is not experiencing any problems but is proactively inquiring about potential updates or refreshes for existing components. They have already performed patching and checked against the latest source code.

This issue outlines a "Project Joy" initiative for the next six months focused on addressing all minor annoyances within the 'kew' project. Developers are encouraged to create individual issues for small bugs, glitches, or UI problems, or to discuss them directly in this thread.

This issue proposes to update the `platformio.ini` file for the ESP32-S3-N16R8 board to specify a 16MB partition table. This change will allow for better utilization of the available flash memory, enabling features like proper OTA updates and a larger SPIFFS partition for web interfaces and data.

This issue requests the addition of regression tests for the `i16toav()` function, which handles variable-length telemetry fields. The goal is to ensure that future code changes do not inadvertently alter the format of transmitted data, particularly around important decimal boundaries. The task involves adding specific test cases to existing number-format tests and verifying the results.

This issue requests the creation of a supplier-neutral guide for new builders of the PicoTracker hardware. The guide should clearly differentiate between historical components and current candidate options, outlining essential electrical/RF characteristics and providing status (verified, candidate, not yet tested) for each suggestion, along with links to relevant documentation.

This issue proposes adding a CSV export functionality to the PicoTracker's telemetry decoder. The goal is to make captured flight data easily accessible for analysis in spreadsheets and other tools by adding a new command-line option to output CRC-valid frames in a CSV format. The implementation should maintain existing decoder behavior and include comprehensive testing and documentation.

This issue proposes enhancing graph library support for parallel edges, allowing multiple edges between the same two vertices. The existing implementation already handles this by counting parallel edges for degree calculations and allowing distinct metadata. The task involves adding a new flag to detect parallel edges, creating new source files for edge detection logic, and implementing a new data structure and associated methods to manage this detection.

This issue addresses a compatibility problem when building the `apbs-3.0.0` project with SWIG version 4.5.0. The core of the bug lies in the removal of certain Python 2 C API macros, which are now replaced with their Python 3 equivalents to ensure successful compilation.

This issue proposes adding a new command to the firmware that allows developers to read the configuration registers of the CC1120 radio module. This command will utilize SPI to access the registers and then downlink the data over UART for easy verification during development and production.

This issue requests the addition of a CI/CD build check for the OBC Rev4 hardware configuration. The goal is to ensure that the firmware can be successfully built for this new revision, expanding the existing CI/CD coverage which currently supports launchpad, Rev1, and Rev2.

This issue proposes adding a new driver for the OBC Rev4 watchdog, which will then be integrated into the existing state machine. The goal is to enhance system reliability by incorporating this watchdog functionality.

This issue aims to enable flashing firmware onto OBC boards using a Raspberry Pi. The goal is to integrate the Raspberry Pi as a tool for firmware deployment, likely for embedded systems development or maintenance.

Tests in the 4.1 master branch are frequently hanging during OpenSSL shutdown, a problem not present in 4.0.2. The hangs occur in unthreaded 64-bit builds on Nonstop x86 systems, potentially related to signal handling. The user requests assistance in debugging and isolating the root cause.

This issue proposes refactoring the `kuratowski_subgraph` function in the Express API. The function will be generalized to accept different output graph formats and moved to a new file, `planarity_functions.py`. The existing `planarity_networkx.py` file will be removed, and related example files will be renamed and updated to reflect these changes. A new example program will be created to demonstrate the generalized function.

This issue requires adding three missing artwork files (two PNGs and one SVG) for the QIDI Box printer backend. These assets are needed to display a specific icon in the UI, as the current generic icon is a fallback due to their absence. The task involves placing the files in the `assets/` directory and updating a script, with no code changes beyond removing a placeholder marker.

This issue proposes aligning the `kernel::types::ScopeGuard` API with the upcoming stabilized `DropGuard` API in upstream Rust. A new `kernel::mem::DropGuard` type will be introduced to match the upstream version, and existing users will be migrated. Eventually, the old API will be removed, and the new type will be replaced with a direct re-export of `core::mem::DropGuard` once the MSRV allows.

This issue proposes adding Flatpak support for the IDE, allowing Linux users to install and run it via the Flatpak packaging system. This enhancement aims to improve accessibility and ease of installation for Linux users.

Ableton Live crashes or becomes unresponsive when moved to a different monitor within the Niri window manager. The application continues to run in the background, requiring manual process termination to reopen. Additionally, fullscreening Ableton does not hide the bottom taskbar as expected with other applications.

Users are encountering unsuppressible libpng warnings when loading certain PNG files with GD, specifically those with an invalid sRGB profile from applications like Photoshop. The proposed solution is to add a new GD function to allow users to selectively suppress these libpng warnings, improving workflow and avoiding the need to disable all PHP warnings.