A test in the `PerformanceCounterCategory_GetCounters` test suite is failing on an ARM64 Windows build. The error indicates that a required performance counter category, 'PerformanceCounterCategory_GetCounters_Category', does not exist, suggesting a potential race condition or setup issue during test execution.
The user is requesting the addition of a motion sensor entity for Tapo 420(S2) battery cameras within Home Assistant. Currently, this entity is missing, preventing users from creating automations based on motion detection, which is considered a critical functionality.
This issue proposes creating a new example checkout form that consolidates address (country, zip code, phone) and payment (currency, IBAN) fields. The goal is to demonstrate how these fields can validate input and dynamically adjust based on the selected country, addressing a user's question about the interconnectedness of these fields.
This issue proposes adding Mnemoverse as a new memory backend for Omnigent. Currently, users with memory stored in Mnemoverse must embed the Omnigent server to connect to it. This feature would allow users to configure Mnemoverse as a backend directly via server configuration, unifying memory storage and improving agent recall.
This issue proposes adding named Scribe colors to the app's resource files, including light and dark variants for common UI elements like background, text, and buttons. The primary goal is to introduce these named colors without altering the app's current visual appearance, ensuring all existing color names continue to function as before. A STYLEGUIDE.md file should also be created to document the new names and their corresponding hex values.
This issue aims to refactor the Compose theme to use shared Scribe color resources instead of duplicating hex values. It also specifies how to handle dark mode button colors and a potential change for dark captions, ensuring consistency and avoiding redundant color definitions.
This issue aims to refactor the keyboard component by replacing hardcoded hexadecimal color values with named color constants. The goal is to ensure consistency and maintainability, with a specific instruction to not alter the visual appearance where hex colors already match named colors, and to document any discrepancies.
This issue requires updating several Compose screens to use the new shared color palette instead of hardcoded hex values or outdated color definitions. The goal is to ensure consistency with the established theme, with a specific instruction to avoid silent color changes and to only update hex values if a corresponding named color is explicitly accepted.
This issue proposes bundling the Roboto font family (regular, medium, semibold, bold) directly within the application to replace the default system font. The goal is to ensure consistent typography across devices without relying on runtime font downloads or external dependencies, while also updating the `Typography.kt` file and XML `fontFamily` definitions to point to the bundled fonts. This change aims to maintain the appearance of phones already using Roboto and standardize it for others.
The EuiFilterButton incorrectly infers the `aria-expanded` state from `hasActiveFilters` when it's a collapsible chevron button. This can lead to incorrect accessibility announcements for screen reader users, as `hasActiveFilters` represents a visual state, not the actual open/closed disclosure state of a popover.
This issue aims to remove unused Material color swatches and their corresponding `AppTheme` styles from `colors.xml`. Before deletion, all references to these colors, including aliases, must be identified and verified as unused. Any remaining used grey colors will be retargeted to their hex values without altering the UI.
This issue proposes adding a new section to movie pages that displays related films based on their universe, franchise, or collection. The goal is to differentiate between films directly created by an author within a universe (e.g., Romero's "Dead" films) and the broader franchise that might include unrelated works or remakes.
enhancementhelp wantedgood first issuearea:сторінкаplanned
This issue requests the addition of two new optional window themes, 'Frost' and 'Liquid Glass', which will introduce different levels of blur and refraction effects. These themes need to be cross-platform compatible (macOS, Windows, Linux), gracefully fall back to solid themes when unsupported, and respect the operating system's reduce-transparency setting. Existing light and dark themes will remain the default.
The `unit-test` suite failed during a nightly run, indicating a regression. The provided log tail shows many successful tests, but the overall suite failure suggests an issue that wasn't captured in this snippet or a failure in a later part of the test execution. Further investigation of the full logs is required to pinpoint the exact cause.
This issue addresses a `MarkupNotFoundException` in Apache Wicket that occurs when an initially invisible component is later added to an Ajax update. The current exception message lacks crucial context, making it difficult to diagnose in large applications. The goal is to enhance the exception message to include the page class and the component's path, along with a hint for the common cause.
This issue requests the development of a plain HTML, CSS, and JavaScript age calculator. Users will input their date of birth to see their age in years, months, and days, along with total days lived and days remaining until their next birthday. The calculator must also validate against empty and future dates and feature a responsive layout.
This issue proposes expanding the known-value fingerprint vectors for the `observatory-interface` crate. The goal is to add more test vectors covering various data types (primitives, composites, UDTs, events, large interfaces) to ensure that serialization changes are detected. This will help prevent regressions where similar interfaces might change their serialization format without being caught by existing tests.
good first issuephase:fingerprintingtype:testingdifficulty/trivialStellar Wave
This issue aims to improve the troubleshooting documentation by adding detailed guidance for each `ErrorCode`. Currently, users struggle to understand the causes and remedies for specific error codes. The goal is to create a comprehensive entry for every `ErrorCode`, including typical causes and solutions, and link to relevant CLI exit codes.
good first issuephase:documentationtype:documentationdifficulty/trivialStellar Wave
This issue proposes adding Architecture Decision Records (ADRs) to the project's documentation. The goal is to centralize and make it easier to trace the rationale behind key technical decisions, with an initial set of five ADRs to be created and linked from the main architecture document.
good first issuephase:documentationtype:documentationdifficulty/trivialStellar Wave
This issue proposes adding a glossary to the project's documentation to define domain-specific terms used throughout. The goal is to help new contributors understand these terms without needing to search externally, with specific terms like SCVal and strkey listed for inclusion. The glossary will be located in `docs/glossary.md` and requires accurate definitions with sources.
good first issuephase:documentationtype:documentationdifficulty/trivialStellar Wave
This issue aims to improve operational diagnostics by introducing correlation IDs to link API requests with worker jobs, making it easier to trace issues. It also seeks to make frontend errors visible to users in production with actionable context, while ensuring secrets are redacted and intentional fallbacks remain silent.
This issue proposes adding a static visual indicator for synchronization progress when animations are disabled. Currently, users receive no feedback during sync in this mode, leading to uncertainty. A new icon state would provide clear confirmation that the sync is active, improving usability for users who prefer to disable animations.
This issue requests enhanced logging for the AllStar tool to provide administrators with visibility into configuration origins and final settings. Specifically, it aims to log details about which configuration files (org-wide vs. repository-specific) were used and the resulting final configuration applied to a repository, especially when repository-level overrides are in effect.
This issue proposes refactoring code to use Kotlin's `kotlin.time.Duration` type instead of raw `Long` values representing milliseconds for configuration and timeout parameters. This change aims to improve code readability, prevent unit errors, and align with idiomatic Kotlin practices without affecting the minimum supported Kotlin version.
The `document_set` and `entity_store` operators in the storage system incorrectly allow arbitrary `database_path` values from flow configurations. This bypasses path validation, enabling malicious flows to create directories and database files anywhere the server user has write permissions, posing a security risk.
This issue proposes adding support for parsing localized episode titles and descriptions from TMDB for TV series. The localized content could be displayed in a separate pop-up window, similar to how Apple TV presents extended information, to avoid cluttering the main series episode list.
enhancementhelp wantedgood first issuearea:сторінкаplanned
The user proposes replacing the text title of movies/series on a banner with logos parsed from TMDb. This enhancement aims to visually represent titles using logos, specifically for banner display, as demonstrated by an example image.
enhancementhelp wantedgood first issuearea:сторінкаplanned
This issue outlines a handoff task to synchronize the `BotHarness/dsh-im` fork with its upstream and then integrate a WhatsApp Direct Message (DM) tracer into the main `BotHarness/DeepSeekBot` project. The initial implementation should focus on handling text messages in self-chats for bound WhatsApp accounts, ensuring a clear contract between the provider and consumer for message handling and replies.
help wantedready-for-humanarea:fullstackfeature:messagingscope:hub
This issue is a "good first issue" and part of Hacktoberfest, requesting the addition of a new trivia question about a Japanese city famous for a floating torii gate. The task involves editing a JSON file directly in the browser, requiring no coding or local setup, and is estimated to take less than a minute.
help wantedgood first issuehacktoberfestcommunitylow hanging fruitup-for-grabs
The dashboard API endpoints `/api/resolve/{id}` and `/api/mode` are crashing with a 500 Internal Server Error when they receive a valid JSON request body that is not a JSON object (e.g., an array, string, or number). Instead of returning the expected 400 Bad Request error, the application raises an AttributeError because it attempts to access properties on a non-object JSON structure.