Ruby good first issues

This GitHub issue serves as a tracking list for Homebrew formulae that have available updates but cannot be updated due to build or test failures. It categorizes these issues and highlights where community assistance is needed to resolve them. The issue also includes links to pull requests that show progress in updating these formulae.

This issue proposes cleaning up stale Flipper flags in the production environment. The task involves identifying and removing these flags after ensuring all their references have been removed from the codebase. It's labeled as a 'good first issue', suggesting it's suitable for new contributors.

This issue proposes the integration of a new PrusaLink API for printing functionality. The goal is to update an existing print service to autodetect the API version and support all Prusa printers. The developer needs to consult the provided OpenAPI specification and potentially find a way to test the new API with a Prusa printer.

The Wikidata stats card in the WikiEdu Dashboard is currently overwhelming due to its layout and design. To improve this, the card should be collapsible and hidden by default for non-Wikidata home wikis. Additionally, entries with zero edits, and entire categories with only zero edits, should not be displayed.

Admins currently can force a full course update, but this resets pageviews to zero due to a caching dependency. The desired behavior is to provide an admin interface for enqueuing a 'non-full' update that correctly populates pageviews without this side effect.

This issue proposes enhancing the accessibility of several interactive UI components by implementing ARIA labels and ensuring proper keyboard navigation. The goal is to make components like Modals, Dropdowns, and Tooltips more usable for individuals relying on assistive technologies and keyboard-only interaction.

This issue requests the addition of new flow cell kit types ('5B') and associated read length options to the SequenceScape submission forms for Illumina-HTP NovaSeqX paired end sequencing. It also introduces a constraint where a 300 read length is only permitted if the flow cell type is '1.5B'. These changes need to be reflected in both single and bulk submission forms, as well as the additional sequencing page.

This issue requests the implementation of an automated thank you email system for coaches who reach specific workshop attendance milestones (5, 10, 15, 20, etc.). The goal is to acknowledge and appreciate coaches for their continued engagement.

This issue requests the implementation of an automated email system to celebrate students reaching specific workshop attendance milestones (5, 10, 15, 20, etc.). The goal is to send a congratulatory message to students upon achieving these attendance thresholds.

This issue is a placeholder for automated comments from Testbot regarding problems with the homepage or source URLs of Homebrew Casks. These are intended to be simple fixes suitable for new contributors.

This issue requests that proposal filtering options (specifically 'Origins') should be hidden if there are no proposals associated with that origin within a given process. The goal is to improve the user experience by decluttering the filter sidebar when certain filtering criteria are irrelevant.

This feature request proposes implementing a soft delete functionality for 'Initiatives' within the admin panel. This would allow administrators to move initiatives to a 'Trash Bin' instead of permanently deleting them, with the ability to restore them later. The solution should be designed to be extensible for other components.

This issue addresses a problem in Batch Connect where jobs fail if the `run_script` file lacks execute permissions. The proposed solution is to automatically make the script executable using `chmod +x` before attempting to run it, ensuring job submission success.

This issue proposes leveraging Ansible Runner's execution environments (containerized environments) to manage Ansible dependencies and execution. The goal is to simplify dependency management, eliminate the need for manual appliance updates, and allow users to define custom execution environments. This would involve changes to how Ansible tasks are executed in a podified environment, potentially interacting with the Kubernetes API.

This issue proposes adding instrumentation for the `drop` and `has` operations of the LMDB database in the OpenTelemetry Ruby contrib library. The goal is to capture these specific LMDB methods to provide more comprehensive monitoring of database interactions, aligning with existing stable attributes.

This issue involves converting a Ruby-based form for adding new groups within Access Control/Groups/Configuration to use DDF/React and the API. It requires integrating existing components like a tree select and an expression editor, with the API state currently needing further information.

This issue proposes adding validation checks for Dialogflow credentials before they are saved. If the provided credentials are found to be invalid, the conversation status should be updated to 'open' from the bot.

This issue addresses a bug in the OpenTelemetry Ruby SDK where instrument names are treated as case-sensitive, violating the specification. The fix involves making the instrument name lookup case-insensitive by normalizing keys in the registry, ensuring that instruments with differing cases but the same underlying name are recognized as duplicates and logged appropriately.

This issue proposes adding a file upload dialog to the "add image" button in the editor. Currently, images can only be added via drag-and-drop, and this enhancement aims to make image uploading more discoverable and user-friendly for new users.

The application incorrectly displays schedule names containing German umlauts (ö, ü, ä) and eszett (ß) after a page reload. Instead of showing the characters as entered, they are rendered as HTML entities, breaking the intended display.

This issue requests the addition of ViewComponent previews for four specific UI components: Alert, Badge, Group, and Stat. These previews will allow developers to easily view and test different variations of these components within the Rails UI component browser. The task involves creating new Ruby files in a designated directory, following an existing pattern, and ensuring 2-3 key examples demonstrating main variants are included for each component.

This issue addresses the need to support the `OTEL_EXPORTER_OTLP_METRICS_DEFAULT_HISTOGRAM_AGGREGATION` environment variable in the OpenTelemetry Ruby SDK. Currently, users cannot configure the default histogram aggregation (e.g., to exponential buckets) via this environment variable, limiting their ability to customize metric collection without explicit view registration.

This issue addresses a discrepancy in the OpenTelemetry Ruby SDK's stdout exporter. Currently, it uses a default export interval of 60000ms, which deviates from the OpenTelemetry specification's recommended 10000ms for this specific exporter. The suggested fix is to explicitly set the `export_interval_millis` to 10000ms when configuring the default PeriodicMetricReader for the console exporter.

This bug occurs when creating a group without specifying any members, causing the `set_members` method to attempt to call `.split(',')` on a nil value. This results in a `NoMethodError` and a 500 server error. The expected behavior is to gracefully handle the absence of members by initializing an empty list.

This issue requests the addition of more search filters to the 'Desligamentos' (Disconnections/Terminations) screen. Specifically, users should be able to search by year, disconnection type, and enrollment level. This aims to improve the usability and efficiency of finding specific disconnection records.

This issue proposes improving error messages for Torque adapter configurations. Currently, errors like a missing 'host' are generic and don't specify which cluster they relate to. The suggested improvement is to prepend the cluster name to the error message for better clarity and debugging.

The LinuxHostAdapter in Open OnDemand incorrectly uses `Etc.getlogin` to determine the username, which returns 'root' in the Per-User NGINX (PUN) context. This leads to jobs being executed as root instead of the intended user, posing a critical security risk. The fix involves replacing `Etc.getlogin` with `Etc.getpwuid.name` to retrieve the correct effective username.

This issue proposes the removal of unused search helper methods (`process_special_case` and `find_match_in_text`) from the `MarkdownHelper` class. The goal is to clean up the codebase and clarify the responsibilities of `MarkdownHelper` to focus solely on Markdown conversion, without altering the application's behavior.

This issue is a request to correct a typo in the image upload instructions within two Slim template files. The typo needs to be corrected to "630px" in both `app/views/mentor/practices/_form.html.slim` and `app/views/articles/_form.html.slim`.

This issue proposes refactoring a Ruby class named `Redirection`. The goal is to rename the class and its `determin_url` method to more accurately reflect their responsibility of generating redirect URLs based on a resource's WIP (Work In Progress) status. The functionality of the application will remain unchanged, but the code will be more readable and maintainable.