Elixir good first issues

Local websocket sessions in Codex are not renewing their leases, causing them to expire every 15 minutes. This leads to runtime cleanup marking streaming turns as failed with an 'owner_unavailable' error, even though the lease is technically still valid for a longer period. The issue stems from lease renewal logic only activating for HTTP transports or when owner forwarding is enabled.

The user is experiencing difficulties with the Erlang `:ssl` module's `verify_peer` option, finding that it fails to connect to most websites even with CA certificates from `erlang-certifi`. Despite attempts to use `verify_fun` and other workarounds, the issue persists, leading them to disable peer verification for now.

This issue requests the implementation of column sorting functionality for the user search results page in the teiserver admin panel. Users should be able to sort by various columns, including name, status, play time, game counts, hardware identifiers, and login/registration dates. Sorting by domain is a desirable but optional enhancement.

This issue proposes adding support for Stripe's v2 APIs, specifically starting with the Money Management product suite. The current library only supports v1, requiring users to manually handle v2's different request formats, preview API versions, context headers, pagination, and idempotency keys. The proposed solution involves updating the request layer and generating v2 resources using the existing OpenAPI codegen.

The user list page incorrectly forwards to a detail view when only one result is displayed on a page, even if there are more results across multiple pages. This is because the logic checks the length of the current page's results instead of the total number of results. The fix involves updating the logic to consider the total count of results.

This issue indicates a significant number of bugs and inaccuracies within the game's mechanics, effects, skills, and MobAI. The developer is seeking assistance to address these widespread issues, suggesting a broad review and correction effort is needed.

This issue requests the implementation of export buttons for all diagrams rendered within the application. Users should be able to download the diagram source and also in various formats like SVG.

This issue describes a bug in the Ash framework where resource-based inline aggregates fail when the target resources are defined in different database schemas. The generated SQL incorrectly attempts to query the target resource from the schema of the source resource, leading to runtime errors. The expected behavior is for the aggregate to correctly reference the target resource's schema.

Permanent deletion of upstream accounts fails for those with large request histories due to a combination of fixed batch sizes (500 rows) and a 10-second statement timeout in PostgreSQL. This leads to repeated job failures and leaves accounts in an unrecoverable state, preventing credential replacement or re-import.

This issue requests support for using the pipe character (`|`) within Markdown table cells, specifically for cases like function piping (`|>`) or literal pipe characters within strings. The current implementation incorrectly splits cells at pipe characters, requiring workarounds. Potential solutions include adding an escape character or recognizing `|>` as a distinct token.

The user wants to automatically generate a project changelog, similar to the example provided in the reactive-commons-java repository. This would involve creating a GitHub Action to automate the process from the project's inception.

This issue requests the addition of a new API service to check if a given user reference has an active channel. This functionality is needed by other backend services to determine if message delivery is possible before attempting it.

This issue proposes adding a fan-out message delivery feature to the system. Currently, messages are delivered point-to-point to a single channel. The proposed solution would allow a single message to be delivered to multiple channels or users simultaneously, enhancing the system's messaging capabilities.

This issue aims to reduce the size of the Engine by auditing its code for unnecessary components. The goal is to improve compilation times, reduce disk space usage, and adhere to the Engine's original design principle of being small. Specific areas to investigate include dead code, Forge code duplication, and functionality that could be moved to the Expert app.

This issue requests an audit of the Refactorex features integrated into the expert project. The goal is to verify that these features are functional and to document their usage in the project's documentation. This involves testing and potentially fixing any issues found.

This issue proposes making the syntax highlighting colors in the sql library configurable by users. Currently, these colors are hardcoded in specific files, and the goal is to allow users to customize them.

The user reports that the `ex_phone_number` library incorrectly identifies a valid US short code ("88811") as invalid. They are offering to fix the issue and are seeking guidance on the relevant parts of the `libphonenumber` library and its corresponding implementation in `ex_phone_number`.

The author proposes a 2.0 version for the Joken JWKS library to address several existing issues and incorporate new features. Key improvements include better handling of kid-less and duplicate keys, fixing process-related side effects, and enhancing flexibility for static and dynamic JWKS sources. The update also aims to improve security with JWKS claims like certificate thumbprints, better HTTP configuration, increased observability, improved documentation, and more robust fetching options.

The current email input field in the user form is using `type="text"` and is missing the `autocomplete="email"` attribute. This prevents password managers and browser autofill from correctly identifying and populating the email field. The suggested fix is to change the input type to `email` and add the `autocomplete="email"` attribute.

The `attach` action in Ash storage is not correctly passing context to the `create` action of the `ImageBlob` resource. This results in policy checks failing for the blob, even though context is successfully passed to related resources like `Post` and `ImageAttachment`. The user has found a workaround by directly authorizing the `ImageBlob` policy, indicating an issue with context propagation.

This issue requires adding executable metadata for OrcaRouter's shared ReqLLM adapter within the LLMDB catalog. The work involves defining provider runtime details, specifying executable chat completion models, and ensuring only verified entries are activated. A regression test and snapshot regeneration are also necessary before publishing the metadata.

This issue aims to make Windows a first-class operating system by improving the pure-Elixir terminal driver, integrating Windows into the CI pipeline, and finalizing the PowerShell installer. The goal is to ensure the pure-Elixir driver functions correctly, Windows CI passes for the Elixir path, and the installer is production-ready.

This issue proposes implementing a feature to retrieve vulnerability data from OSV.dev for various package managers and source code management systems. It requires integrating with different SCMs (Hex, Git, System/OTP, System/Elixir) to generate specific query formats and suggests using `querybatch` for efficiency. The feature should also include an on/off toggle, defaulting to on.

When acknowledged private broadcasts fail due to RLS denials or server errors, Realtime currently times out instead of returning a specific error. This makes it difficult for clients to distinguish broadcast failures from network issues. The fix involves modifying the server to send a structured error reply when `config.broadcast.ack` is true and a broadcast fails.

A NUL byte (0x00) within a text field, when processed by Ash and Postgrex, results in an `Ash.Error.Unknown` error instead of a more specific constraint violation error. This occurs because the `Postgrex.Error` for invalid UTF-8 sequences is not correctly mapped to an Ash-specific error class, leading to a generic server error response across different Ash interfaces.

This issue describes a bug in Ash where invalid `page` options, such as incorrect data types or unsupported keys, are not handled gracefully. Instead of returning a standard `Ash.Error.Invalid` with a 400 status code for API requests, the system either raises an unrendered `Spark.Options.ValidationError` or a `FunctionClauseError`, leading to unexpected behavior and potential 500 errors in JSON:API responses.

The current implementation of `blacklisted_phrase?` incorrectly handles banned phrases containing specific characters (1, 3, 4, 5, 7, 8, 0, -, _). These characters are leetspeak-replaced before the check, preventing matches for phrases that intentionally use these characters. This needs to be fixed to ensure accurate banned phrase detection.

Users are currently unable to report their friends due to a system limitation, receiving an error message instead. The goal is to remove this restriction, allowing users to report friends just like any other user. This change aims to provide a more comprehensive reporting system.

This issue requests the completion of the French translation for the user interface, emails, and error pages. It involves translating a significant number of messages, adapting number formatting to French conventions (using a narrow no-break space for thousands separators and a comma for decimals), and ensuring the use of formal "vous" register. The goal is to have a fully localized French experience.

This issue proposes introducing a `Config` module to manage environment variable loading, specifically to prevent race conditions in asynchronous tests. This module will ensure that environment variables are loaded safely and can be overridden by async tests, improving test stability. The migration should be phased, starting with areas already covered by async tests.