Help Wanted

AI Summary: This GitHub issue reports deprecation warnings for Node.js 20 actions within GitHub Actions workflows, specifically affecting `actions/checkout@v4`, `actions/upload-artifact@v4`, and `nick-fields/retry@v3`. GitHub will force these actions to run on Node.js 24 by June 2nd, 2026. The task is to update these actions to their latest versions to ensure compatibility with Node.js 24, or to explicitly opt into Node.js 24 now.

AI Summary: This GitHub issue proposes implementing `views::slice` for C++29. Described as a relatively simple range adaptor, `views::slice` conceptually combines the functionality of `take_view` and `drop_view` to extract a specific sub-range from a given range.

AI Summary: This is a beginner-friendly "Good First Issue" designed for new contributors. The task involves adding a new Japan fact (fact #149) about the origin of the word 'shiawase' to a collection. It requires no coding, setup, or cloning, and can be completed directly from a browser in under a minute.

AI Summary: This GitHub issue requests the addition of a new UI card titled "How it works" to a specific page. The design for this card is provided via an image and a Base44 link, and it needs to be placed directly below existing cards on the page. Developers should note that the section order on the live website may differ from the Base44 UI reference.

AI Summary: This issue requests adding a new CLI option, `cache-dir`, to allow users to specify a custom directory for downloading imagery. This argument needs to be passed from the `predict` and `predict_point` CLI commands to the `CyFiPipeline`, along with corresponding unit tests.

AI Summary: The `ModalNavigationDrawer` in Slint loses its selected item state (current group and index) when closed and reopened. This happens because the drawer object is deleted and recreated upon each `show()` call, causing its selection to reset to the default first element.

AI Summary: This GitHub issue is a beginner-friendly task to add a new "Kintsugi Gold" color theme. It's explicitly designed as a "good first issue" requiring no coding, no setup, and can be completed in under a minute by adding simple JSON data directly from the browser.

AI Summary: This issue highlights inconsistent text formatting for atlas names (e.g., "Allen Mouse Brain Atlas" vs. "Smoothed version of the Kim et al. mouse reference atlas") across the project's readmes, tutorials, and website. The goal is to establish a standard formatting strategy and apply it consistently.

AI Summary: This issue aims to refactor Playwright end-to-end tests in `pools.spec.ts` and `PoolsPage.ts` to align with Playwright Best Practices. The task focuses on improving test patterns, such as using locator-based waiting and web-first assertions, without changing test coverage or behavior. It is part of a larger effort to modernize testing patterns.

AI Summary: This GitHub issue reports incorrect browser compatibility data for the `writing-mode: vertical-*` CSS property in Safari on iOS. While the current data indicates support from iOS 9, the property specifically fails to render correctly on `<th>` or `<td>` elements for iOS versions prior to 17. The user confirmed this discrepancy by testing on an iPhone running iOS 16.7.14.

AI Summary: This issue proposes centralizing the management of export directories by introducing a singleton `Exporter` class. Currently, export directories are passed manually and repeatedly, leading to scattered configuration. The new `Exporter` will be initialized from a YAML configuration and provide a consistent method to retrieve the export path, streamlining configuration and improving consistency.

AI Summary: This GitHub issue addresses the problem of over 20 empty `__init__.py` files across the codebase, which leads to poor IDE autocomplete, ineffective `import *` statements, and an implicit public API. The goal is to populate these files with `__all__` exports to explicitly define each package's public interface, requiring careful identification of key symbols for each module.

AI Summary: The issue proposes adding native support for Google Cloud Spanner's new Spanner Graph capabilities as a graph backend for Cognee. Currently, Cognee users in GCP must integrate a separate graph database, but Spanner Graph's native property graph model and GQL support make it a viable direct option. The solution involves creating a new `SpannerGraphStore` adapter to map Cognee operations to Spanner Graph queries.

AI Summary: The Planning Agent occasionally displays raw code in the `Plan.md` output, rather than a human-readable plan. This issue occurs in both the Planning tab and the conversation timeline when interacting with the agent to build a feature. The user also suggests improving the naming of `GLOB` and `GREP` in the timeline for better clarity.

AI Summary: The issue requests a new `edit` command for `greywall templates`. This command should automatically open the user's default text editor with the template content, and upon the editor's closure, it should validate any changes made to the template.

AI Summary: This issue addresses an inconsistency in terminology within the platform. The 'Verification Request' table currently labels a status column as 'Postado', while the standard and correct term used elsewhere is 'Publicado'. The task is to update this column label to 'Publicado' to ensure consistent terminology.

AI Summary: This issue involves implementing two new domain objects, `AnswerSubmittedEventLogEntry` and `BlogPostReadEventLogEntry`, each requiring a comprehensive `validate()` function. Before coding, developers must describe the domain object properties and validation checks for approval. A key refactoring step is to ensure that the corresponding storage models are exclusively used within `get/save` methods for conversion, with all other codebase usages replaced by the new domain objects, following the `ExplorationModel` example.

AI Summary: The `debian/build.sh` script uses `git describe --tags` to determine the package version, which conflicts with the project's release-cycle strategy. This causes builds from `develop` or `beta` branches to incorrectly use an old version tag from `master`, resulting in `.deb` packages with the wrong version number and potential installation issues.

AI Summary: This GitHub issue outlines a refactoring effort to migrate existing test setups within the `nerdctl` repository. The primary goal is to rewrite all tests that currently use `testutil.NewBase` to instead leverage `nerdtest.Setup`, which is part of the Tigron testing framework. While the task for each individual test file is considered straightforward and suitable as a "good first issue," the overall migration requires multiple pull requests due to the large number of affected files.

AI Summary: This GitHub issue requests the addition of a `make uninstall` target to the project's Makefile. This new target would be responsible for removing all files and directories that were previously installed by `make install`, providing a clean way to revert the installation.

AI Summary: This bug report describes an issue where selling an appliance to a customer via the UI incorrectly creates a duplicated, non-primary address record for that customer. The expected behavior is that the customer's existing address information should remain untouched. The issue is reproducible by creating a new customer and then selling them an appliance.

AI Summary: This GitHub issue requests the implementation of filtering capabilities on the "All Transactions" screen. Users should be able to filter their transactions by specific categories, assigned tags, and the amount of money spent. The goal is to enhance transaction searchability and management.

AI Summary: This GitHub issue requests the creation of a new example in the `examples/` directory, demonstrating a DevOps/Infrastructure focused agent team. The example should cover IaC, containerization, CI/CD, and monitoring, following the established format of existing examples including agent definitions, skills, and configuration files. It is explicitly marked as a "Good First Issue" and a documentation-only task.

AI Summary: This GitHub issue describes a task to migrate the `circexplorer2/parse` component to a new "topics channels" system. The core work will involve adapting the existing parsing logic within `circexplorer2` to integrate with and utilize this new topic-based channel architecture. The lack of a detailed description suggests that the specifics of this migration and the "topics channels" system are likely well-understood by the development team.

AI Summary: This GitHub issue asks whether it's possible to use `pipx` as a runner for the 'MCP server' and if the maintainers have attempted or support this configuration. It's a direct question about compatibility and existing usage patterns.

AI Summary: This GitHub issue is a 'Good First Issue' designed for absolute beginners to contribute by adding a specific common Japanese learner mistake. The task involves adding a predefined 'wrong' and 'correct' phrase pair, can be completed in under a minute directly from the browser, and requires no coding or setup.

AI Summary: The user is experiencing slow initial indexing times, taking about an hour for a 4GB codebase. They are requesting an optimization to speed up this process, specifically suggesting the implementation of parallelized indexers.

AI Summary: The Airflow `BatchOperator` fails to retrieve CloudWatch log links for multi-node AWS Batch jobs, even after the jobs complete successfully. This issue stems from the `Batch.Client.describe_jobs` API returning a different response schema for multi-node jobs compared to single-node jobs. The current Airflow code incorrectly expects log stream names only within `attempts.[].container.logStreamName`, missing the correct path for multi-node job logs.

AI Summary: This issue is a feature request to add support for both Svelte and Vue frameworks. It asks for the integration of these two distinct JavaScript frameworks into the existing project or tool.

AI Summary: The `HITLOperator` incorrectly passes `execution_timeout` directly to `BaseOperator`, causing the task to start a timeout countdown immediately upon execution. This can lead to a premature task timeout *before* the operator defers to the `HITLTrigger`. The `HITLTrigger` itself is intended to use `execution_timeout` for its own timeout duration after deferral, creating a conflict where the task might time out before it even reaches the deferred state.