Ruby good first issues

This issue proposes marking the String#% method as returning a StringExact type within the ZJIT (presumably a Just-In-Time compiler for Ruby). This change aims to improve type inference and optimization by providing more specific information about the return type of this method. The task involves updating the relevant method definitions and adding a test case to verify the change.

CI jobs are experiencing intermittent "Bus error: 10" failures during the doxygen documentation generation step on specific macOS architectures (arm64). This issue appears to be related to doxygen itself and has a corresponding upstream issue report.

This feature request aims to improve the usefulness of diffs in email notifications by adding syntax highlighting. The proposed solution involves leveraging an existing diff component in the codebase, requiring a separate stylesheet for HTML emails to avoid Bootstrap dependencies.

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.

The Maven API incorrectly generates download URLs that assume a JAR artifact, leading to 404 errors when the actual published artifact is an AAR or POM. This occurs because the API always appends `.jar` to the download URL, regardless of the artifact's true packaging type. The issue needs to be fixed to correctly identify and provide download URLs for AAR and POM artifacts.

The `LLM::Context: tool stream` example incorrectly stubs `Kernel.system` with a string, which is not a valid return type for the actual function. This leads to unrealistic tool results being passed to the model. The issue proposes re-recording cassettes and potentially adding provider-specific options to ensure the stub's return type aligns with `Kernel.system`.

This issue proposes adding a new model entry, "enso-auto", to the `data/hanzo.json` configuration file. This is necessary because the default Hanzo model returns "enso-auto", but it's not currently recognized by the LLM registry, leading to errors. The fix involves adding the new entry with specific metadata and ensuring it's covered by a test.

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 proposes to remove the session key `_chatwoot_session` from the application. The key is no longer in use, and its removal is a straightforward cleanup task.

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.

This issue proposes adding 'Smclic' to the system, likely a new instruction set extension. It requires adding data definitions and potentially hart-visible additions in IDL, indicating a need for integration with the ISA specification and data entry processes.

This issue proposes rewriting the `Integer#upto` method in Ruby's JIT (Just-In-Time) compiler. The motivation is to have parity with the existing `downto` method and to potentially improve performance, as `upto` is used in libraries like chunky-png.

The blog article creation page displays a duplicate sentence describing how to add tags. The sentence "入力してエンターキーを押すとタグになります（スペースは入力できません）。" appears twice consecutively. This issue is reproducible by logging in as a mentor and navigating to the new article creation page.

This issue proposes to optimize the ZJIT (presumably a Just-In-Time compiler) by specializing the `Hash#fetch(key, default)` method. The goal is to avoid unnecessary variadic setup, suggesting a simpler and more efficient implementation for this specific case.

This issue proposes adding two new reader methods, `compactor` and `compactor_options`, to the `LLM::Agent` class. These methods will delegate to the `LLM::Context` object to expose the configured compactor class and its options, improving how agents access and utilize compaction strategies.

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 feature request aims to automatically populate social media handles and other relevant user information from various supported channels into Chatwoot contact profiles. The goal is to ensure consistency, display this data correctly on the dashboard, and add support for channels like Line and fields like Website URL that are currently missing or inconsistently handled.

This issue proposes an enhancement to the agent view in Chatwoot to handle long incoming messages. The suggestion is to truncate messages exceeding a certain character limit (e.g., 800 characters) and provide a "read more" button to reveal the full content, preventing them from overwhelming the screen.

The user is requesting a feature to disable the "message delete" button within the Chatwoot application. This would prevent agents from deleting messages, potentially for audit or compliance reasons. The issue is tagged as a "feature-request" and a "Good first issue".

This issue proposes adding class-level accessors for `compactor` and `compactor_options` to `LLM::Agent`. This will allow agent classes to declare their compaction strategy directly, rather than only being able to set it during instantiation. The implementation involves adding new class methods and updating internal field handling.

This issue proposes implementing an inline annotation for the `Integer#pred` method within the ZJIT (likely a Just-In-Time compiler for Ruby). The goal is to optimize this method by directly translating it to a `FixnumSub 1` operation, which should improve performance.

A recent commit introduced a bug on mobile devices where tapping an upvote button to scroll inadvertently toggles its upvoted state. This issue is difficult to reproduce in browser developer tools, suggesting it's specific to actual mobile hardware. The reporter suggests a CSS media query for hover effects as a potential solution.

This issue requests the implementation of a "Set Ownership" functionality for the Container Project page. The goal is to have a button that, when clicked, opens an ownership form similar to a provided screenshot. The request also seeks guidance on the best implementation approach, such as adding missing attributes or exploring alternative methods.

The user is encountering issues with RuboCop's Layout/LineLength cop when generating schema output. They propose that AnnotateRB should be configurable to wrap long comment lines to improve readability and prevent RuboCop violations.

This issue requests community contributions to translate the Potter DB documentation into various languages to improve global accessibility. Contributors are asked to clone the repository, translate `.en.mdx` files, and update configuration files to add their language.

The compliance status screen incorrectly displays the entire compliance history for a VM or Host, rather than just the most recent compliance check. This issue is linked to two Bugzilla entries and is marked as a bug with a 'help wanted' label.

This issue proposes to remove support for the Yajl JSON adapter from the LLM library. The Yajl gem is no longer compatible with newer Ruby versions and its upstream is inactive. The Oj adapter already provides a faster alternative, making Yajl redundant and a maintenance burden. The steps involve removing Yajl-specific code, CI configurations, and documentation.

This issue requests contributions to expand the signature coverage for standard library classes. The project currently has signatures for only a small subset of these classes and is actively seeking help to add more.

When a moderator deletes a comment, the visual indicator for an upvote incorrectly disappears. Upon refreshing the page, the upvote indicator reappears, indicating a frontend rendering or state management issue.

The user is reporting a bug where the search functionality on lobste.rs is not returning relevant results, specifically failing to find an article titled 'There's No Limit How Bad Code Can Get' when searching for the keywords 'how bad code can get'. The provided search URL and screenshot indicate the query was performed correctly, but the results are unrelated.