Find good first issues on GitHub

AI Summary: An agent configuration issue causes the system to launch a 'Bob' process but expect a 'Copilot' CLI prompt, leading to a perpetual 'hung' state. This misconfiguration is silently accepted and masks underlying issues like unauthenticated Copilot or invalid Bob API keys, causing repeated restarts and incorrect 'healthy' status for other agents.

AI Summary: This issue is a beginner-friendly task to add a single markdown line to a community notes file. It requires no coding or repository setup, and can be completed directly in the browser within a minute. The goal is to provide an easy entry point for new open-source contributors.

AI Summary: This issue proposes adding default implementations to the `QuantumResource` trait, where unsupported operations will return an `UnsupportedFunction` error. This change aims to reduce boilerplate for vendor implementations by allowing them to only override methods their backend supports, rather than implementing all methods even if they are not meaningful.

AI Summary: The Logger::Log function can enter infinite recursion and crash if called before Logger::Initialize or after Logger::Dispose. This occurs because the logging ring buffers are uninitialized (size 0), leading to a division by zero and out-of-bounds array access. The subsequent assertion failure within the array access then recursively calls Logger::Log, causing a stack overflow.

AI Summary: This issue is a beginner-friendly task to add a new wallpaper URL to a JSON file. No coding experience is required, and the contribution can be made directly from the browser in under a minute, making it ideal for first-time open-source contributors and Hacktoberfest participants.

AI Summary: This issue proposes adding an automated GitHub Actions workflow to label community pull requests. The labels will be assigned based on the file paths modified in the pull request, helping to categorize contributions. This will streamline the process of identifying and managing community involvement.

AI Summary: This issue requests the addition of a new quickstart guide to the project's documentation. The guide will use Docker Compose to help contributors set up the microservices infrastructure locally, including necessary databases, and run smoke tests. It should also be linked from the main README.

AI Summary: This issue proposes adding a regular expression to validate postal code formats for supported regions within the Delivery service. The goal is to ensure correct postal code entry by implementing this validation and providing comprehensive unit tests for both valid and invalid inputs.

AI Summary: This issue requests the addition of unit tests for the Pricing service to handle edge cases involving negative or invalid discount codes and percentages. The goal is to ensure that such invalid discount values are correctly rejected and that all existing pricing tests continue to pass.

AI Summary: This issue requests the addition of OpenAPI/Swagger documentation for the Customer Support microservice. The goal is to annotate controller actions with SwaggerOperation and XML summary tags to ensure accurate model schema generation in Swagger UI, while also ensuring all tests pass.

AI Summary: Agents connected to a misconfigured LiteLLM gateway are incorrectly displaying a "should be working" status despite failing gateway tests due to authentication errors. The system should accurately reflect the gateway's failure by marking agents as blocked and excluding them from the "able" fleet count, providing a clear error message instead of a misleading green status.

AI Summary: A fleet row incorrectly displayed both "advisories fresh" and "advisory stale" simultaneously. This occurred due to a misconfigured LiteLLM gateway, leading to inconsistent advisory status reporting. The expected behavior is a single, clear indicator of advisory freshness or an explanation of which specific artifact is stale.

AI Summary: The "Harness" system incorrectly re-prompts the user to execute a plan when the underlying provider API returns an error, instead of backing off and handling the provider failure gracefully. This leads to repeated errors and a stalled agent, as the system misinterprets provider errors as a failure to execute a plan.

AI Summary: This issue describes a bug where the Fleet system incorrectly reports a "GitHub App broken" error when the actual problem is a failure in the inference gateway. The root cause was a misconfigured LiteLLM gateway, leading to 502 and 401 errors, which were misinterpreted by Fleet as an authentication issue with the GitHub App.

AI Summary: This issue proposes an optimization for the pipeline log tab, aiming to improve its user interface or functionality. The accompanying image likely showcases the current state and the proposed changes for better log visualization or interaction.

AI Summary: This GitHub issue is a call for users of Cube Sandbox to share how they are using the tool. The maintainers want to understand real-world use cases to inform their roadmap, better support users, and foster community growth. They are asking for details about the organization, location, contact information, and the specific scenario in which Cube Sandbox is being utilized.

AI Summary: This issue proposes refactoring a large React component, `ConfigureCardModal.tsx`, into smaller, more manageable parts. The goal is to separate pure Natural Language (NL) parsing logic into a dedicated file and extract the content of three tabs (settings, behaviors, AI) into their own components. This will improve testability, maintainability, and reduce the complexity of the main modal component without altering its functionality.

AI Summary: The debug log message 'not supported (token: ...)' in the rtk tool incorrectly implies that a command is being refused when, in reality, the command is being passed through unmodified. This can lead to confusion, as demonstrated by a user who believed their 'cd' and 'tail' commands were rejected. The proposed fix is to reword the log message to accurately reflect that no rewrite is occurring and the command will run as-is.

AI Summary: This issue proposes adding a CDN variable for Chrome driver in WebdriverIO. The user wants to be able to specify a custom CDN path for Chrome driver, similar to how it's handled for Edge driver, to manage dependencies securely and avoid issues with blocked external URLs in their local environment and CI/CD pipelines. The proposed solution involves adding a `baseUrl` option to `chromedriverInstallOpts` in the `@wdio/utils` package.

AI Summary: This issue is a beginner-friendly task to add a common Japanese learner mistake to a JSON file. No coding is required, and the contribution can be made directly through the browser in under a minute. It's tagged for Hacktoberfest and aims to help new contributors get started.

AI Summary: The `assemble_module` function incorrectly reports missing variables by listing them multiple times if they appear in different runlists. This leads to a confusing error message where variables are named more often than they actually failed compilation.

AI Summary: The `handleTokenAccess` function in `api.go` has an untestable success path because it relies on a hardcoded file path for its log file. This prevents unit tests from verifying the logic for reading, trimming, and skipping blank lines in the log. The recommended solution is to change the hardcoded constant to a package-level variable, similar to a pattern used in `pkg/scheduler`, allowing tests to redirect the path to a temporary file.

AI Summary: The `check-unused-templates` pre-commit hook fails when the `vendor/infogami` git submodule is not initialized, causing a `RuntimeError`. The hook should be modified to gracefully handle this situation and still run, rather than failing entirely.

AI Summary: This issue seeks community help to verify the `email_verified` claim behavior of various OIDC identity providers, particularly Microsoft Entra ID. The goal is to understand if these providers emit the `email_verified` claim, as its absence prevents certain account provisioning and linking features. This information is crucial for ensuring the correct configuration of the system and is needed before the feature can be considered fully verified.

AI Summary: This issue identifies an inconsistency between breadcrumb trails and page headings on approximately seventeen admin pages, where the last crumb and the `h1` element often display different information. Additionally, the verbs used for initiating creation flows vary across buttons, breadcrumbs, and titles. The fix involves reviewing each page to ensure consistency where appropriate, distinguishing between display names and identifiers, and standardizing verbs within creation flows.

AI Summary: This issue aims to standardize row identification and clickability across admin console tables. Currently, different tables inconsistently use the first column as the row identity and clickable link. The fix involves applying a consistent rule where the first column is the identity and contains the link, ensuring a uniform user experience.

AI Summary: The `magicLinkTokenTtlMinutes` setting can be configured via the REST API but lacks a corresponding input field in the admin console. This enhancement proposes adding a field to the security policy form in the admin console to allow users to view and modify this setting, restoring its discoverability and configurability.

AI Summary: Users are unable to unlink their social identity providers from their accounts, and administrators also lack the functionality to perform this action. This prevents users from resolving situations where a brokered sign-in conflicts with an existing local account's verified email, requiring manual intervention that is currently impossible.

AI Summary: This issue is a beginner-friendly task to add a new Japanese example sentence to a JSON file. It requires no coding and can be completed in under a minute directly from the browser by forking the repository, editing the JSON file, and submitting a pull request.

AI Summary: This issue proposes refactoring a large test file (`auth_test.go`) into three smaller, more focused files based on the distinct concerns of JWT parsing, token revocation, and context handling. The goal is to improve maintainability and readability of the test suite without losing any existing test coverage.