Find meaningful ways to contribute

This issue requests a new prop, likely named `iconClick`, for the TextInput component. This prop would allow developers to easily handle click events on icons within the TextInput, such as toggling password visibility. Currently, there isn't a straightforward method for this functionality.

This issue highlights a discrepancy between the Flowbite JavaScript alert component and its React counterpart, specifically regarding missing timing and transition options in the React version. The goal is to bring the React component's functionality in line with the JavaScript version by adding these missing options.

This issue proposes enhancing the Flowbite React Pagination component to improve SEO by allowing page numbers to be rendered as anchor (`<a>`) tags instead of buttons. This would be achieved by introducing a new `getPageUrl` prop that accepts a function to generate URLs for each page, ensuring search engines can properly index pagination links.

The user is requesting the addition of a 'ghost button' type to the Flowbite React library. This button style, which appears to be used internally in the documentation and some components, would provide a visually distinct option, particularly useful for icon-only buttons.

This issue proposes a fix to allow using regex or 'all-linear' for LoRA target modules in conjunction with layer freezing. Currently, these combinations fail because the `peft` library expects a list for `target_modules` when `layers_to_transform` is used, leading to an error after the model has already loaded. The proposed solution is to resolve the string target to an explicit list of module names before adapter creation, filtering them based on the freeze plan.

When the set of review perspectives is changed mid-review, Pull Requests that have already started reporting heads get stuck indefinitely. The system continues to wait for reports from the removed perspectives, which can never be fulfilled by the planner, preventing the PR from reaching a decision.

This issue serves as a central hub for advisory findings from Hive agents, particularly at lower ACMM levels where agents analyze code without creating direct issues or PRs. A governor agent periodically posts digest comments summarizing these advisory findings. This issue is intended to be a living document and should not be closed.

This RFC proposes reducing NCCL's GPU memory footprint by targeting its legacy code paths, which consume the most memory. The goal is to free up GPU memory for model state and activations, especially in large-scale distributed training scenarios. The project seeks collaborators to validate findings and prototype improvements, with success measured by reduced memory usage and maintained performance.

The sharding proxy in `src/sharding/proxy.rs` reads remote shard responses into a fixed 4096-byte buffer, leading to silent truncation of larger RESP frames. It also creates a new TCP connection for every request without pooling or timeouts, impacting performance and reliability. The proposed fix involves implementing proper RESP framing with connection pooling or gating the sharding functionality behind an experimental flag.

This issue aims to improve the onboarding experience for new contributors by identifying and labeling at least 10 suitable "good first issues" within the repository. The goal is to make it easier for newcomers to find manageable tasks and understand what constitutes completion for each, thereby addressing a current gap in discoverable entry-level contributions.

This issue requires implementing automatic token refresh for the ACP client within the t3code project. The solution involves detecting 401 Unauthorized responses, using Effect.retry for a single re-authentication attempt with a refresh token, and managing session lifecycle with Effect.acquireRelease. It also includes adding a callback for session expiry and handling concurrent requests during re-authentication.

This issue aims to improve code coverage for a GraphQL type field resolver related to recurring event instances. The task involves writing unit tests using mocked GraphQL contexts to cover authentication, authorization, empty/null scenarios, and successful data retrieval, following the project's black-box testing approach.

When using a whole-section comment argument like `--pr_description={...}`, the entire section is replaced instead of merging the new key-value pair. This leads to unexpected behavior and errors as existing keys are dropped and default values are used instead of configured ones. The suggested fix is to implement merging for these arguments, similar to how repository settings are handled.

This issue serves as a central hub for advisory findings from Hive agents, particularly at lower ACMM levels where agents analyze code without creating direct issues or PRs. The governor will periodically post summaries of these advisory findings. It's crucial not to close this issue as it's intended to be a continuously updated document.

This issue aims to onboard new contributors by having them fix Android Studio warnings within a single file. Contributors should run the code inspection tool, select a file with warnings (preferably under the Kotlin section), and resolve all reported issues, then submit a pull request referencing this issue.

This enhancement request proposes adding new "rewind" cards that display a user's top 5 most frequently watched directors and actors over the past year. The current "most popular movie" card is deemed less insightful due to infrequent rewatching of movies.

This enhancement request proposes adding theme songs for the top-ranked TV show and movie to play alongside their respective statistics. The goal is to mimic a feature found on platforms like Spotify, providing a more immersive experience when viewing show or movie details.

This issue is a beginner-friendly task for Hacktoberfest, asking contributors to add a new regional Japanese dialect entry to a JSON file. No coding is required, and the contribution can be made directly through the browser in under a minute.

The "View All" link for trainer attendance on the Lessons page incorrectly redirects trainers to the public landing page instead of the attendance list. This functionality works as expected for administrators, indicating a role-specific permission or routing issue.

This issue aims to enhance the CI/CD pipeline by introducing new safety checks for contributor contributions. It requires reviewing and adding tests for renderer syntax, native-bridge trust, and transfer integrity, while also ensuring untrusted forks are tested with restricted permissions. The goal is to prevent the execution of contributor code with sensitive secrets and to document the necessary review process before merging.

This issue requires developers to improve mutation testing coverage for the `src/core/logger` module. The task involves running mutation tests, identifying surviving mutants, and writing new unit tests to kill them. The goal is to increase the mutation score for this module and update its threshold in the configuration file.

This issue requires updating import paths within the project's examples to use only the published entry points defined in `package.json`. This ensures that examples are self-contained and can be directly copied into applications without relying on internal file structures. Additionally, a new linting rule needs to be implemented to prevent future use of restricted internal import paths within the examples directory.

This issue proposes to update the authenticated examples in the ESI.ts library. Currently, most examples hardcode a character ID, causing authentication errors for new users whose tokens belong to different characters. The task is to create a helper function to dynamically retrieve the character ID from either an environment variable or the access token itself, and then apply this to all affected examples.

This issue involves refactoring BDD tests for the 'paragon-hub' feature. The goal is to move the existing test definitions from a legacy step file into a new, modern structure that aligns with the project's current BDD practices. This includes creating a new spec file, organizing steps into shared libraries, and ensuring all tests still pass after the migration.

This issue involves refactoring BDD tests by migrating status-related scenarios from a legacy step file to a new, modern structure. The task requires creating a new spec file, moving individual steps to a shared library, and organizing fixtures, ultimately aiming to eliminate the legacy file and ensure all tests still pass.

This issue involves refactoring BDD (Behavior-Driven Development) tests for the search functionality. The goal is to move search-related scenarios from a legacy step definition file to a new, modern structure. This includes creating a new spec file, organizing steps into individual files, and migrating fixtures, ultimately aiming to improve test maintainability and adherence to current project standards.

This issue requires adding BDD (Behavior-Driven Development) tests for specific methods within the LoyaltyClient. These methods, which handle paginated data, need to be covered by EARS Rules or BDD steps to ensure they correctly follow all pages, maintain item order, and handle incomplete page scenarios as defined in the project's documentation. The task involves creating new feature files and step definitions, mocking only at the transport layer, and verifying coverage metrics.

This issue requires adding BDD (Behavior-Driven Development) tests for specific paging helper methods within the PiClient of the ESI.ts project. The goal is to ensure these methods correctly handle paginated API responses by following all pages, maintaining item order, and adhering to the specified behavior for incomplete page handling. The task involves creating new feature files and step definitions, mocking only at the transport layer, and verifying test coverage.

This issue requires adding new tests to cover previously untested schema exports in the `@lgriffin/esi.ts/schemas` package. The goal is to ensure each schema correctly validates valid input, rejects incorrect types, and handles unknown fields, following an established testing pattern. Successfully completing this task will result in the removal of these schemas from the coverage baseline.

This issue requires adding BDD (Behavior-Driven Development) tests for specific MailClient methods that handle paginated data. The goal is to ensure these methods correctly follow all pages, maintain item order, and handle incomplete page scenarios as defined in the project's pagination guide. The task involves creating new test files and corresponding step definitions, mocking only at the transport layer.