CSV uploads for Zod 3 instruments hang indefinitely when a data row has fewer cells than the header. This occurs because the code attempts to trim `undefined` values when a cell is missing, leading to a `TypeError` that is not caught, preventing the upload promise from resolving. The fix involves handling missing cells gracefully, similar to the Zod 4 implementation.
BugPriority: MediumDifficulty: LowArea: WebGood First Issue
This issue is a call for user feedback on performance and graphical issues encountered with the latest Alpha 5 release of Savage Wind, particularly on older or integrated GPUs. Developers are requesting detailed reports, including logs, hardware specifications, and specific problem descriptions, to help identify and resolve these issues.
The mojo-lsp-server crashes when requesting code completion for files that import modules with `__init__.mojo` files defining functions with arguments. This appears to be a bug in how the LSP server processes function signatures during documentation generation for completions, leading to an LLVM error.
buggood first issuemojoacceptedbug_feature_triaged
After clearing the cache and restarting the Expensify app, users are experiencing an infinite loading loop when trying to view a split expense preview. This issue leads to a "not here" page being displayed instead of the expected preview, impacting the Money Requests component.
This issue proposes to remove a file-wide ESLint disable directive in the retention job by correctly handling the promise returned by `setInterval`. Additionally, it aims to replace anonymous inline object types with named types inferred from existing Zod schemas in the retention update methods for better code clarity and maintainability.
This feature request aims to simplify the installation and management of etcd and minio by adding support for Homebrew. The user wants to be able to install and run these services easily on macOS, Ubuntu, and CentOS, with macOS being the initial priority.
This issue proposes improvements to the GitHub Actions scanner to reduce spam. Specifically, it aims to prevent comments on mutation error verdicts, empty PR overlap notifications, and when maintainer/bot-authored issues are closed, aligning with a broader spam reduction effort.
help wantedtriage/acceptedagent/scannerstage/040-covered-by-pr
This issue proposes to refactor how certain follow-up items are displayed within a scanner interface. Specifically, the 'P3 follow-up checklist' will become a collapsible section, and 'pr-link' and 'ready-for-human-merge' notices will be displayed as status card lines, while 'Needs-decision' will remain a comment. This is part of a larger spam reduction effort.
help wantedtriage/acceptedagent/scannerstage/040-covered-by-pr
When a user removes a term from a project in Traduora and then navigates to the translations page for any locale, they are unexpectedly redirected to a 404 error page. The expected behavior is to see the remaining terms listed, ready for translation.
A configuration setting `TR_MAX_PROJECTS_PER_USER=0` is intended to disallow project creation, but the system incorrectly interprets this as allowing unlimited projects. This allows any user to create an unlimited number of projects, posing a potential denial-of-service risk through resource exhaustion.
The reference text for strings is being truncated, causing confusion for translators and resulting in incomplete translations. This issue is impacting the translation workflow and needs to be addressed.
This issue requests a new grid example that demonstrates streaming 50,000 rows to showcase progressive loading. The goal is to make large initial loads feel faster by allowing users to interact with data as it arrives, and to fill the grid's progress hook in the footer toolbar.
This issue proposes creating a new grid example that demonstrates server-side paging, sorting, and filtering. The current examples store all data in the browser, which is not suitable for large datasets. The fix involves implementing a simulated server to handle these operations, similar to existing examples but with a focus on a functional backend.
This issue proposes adding a new example to showcase the grid's CSV export functionality. The goal is to create a practical demonstration where users can filter and sort data, then export the visible rows as a CSV file, and also view a preview of the exported CSV.
This issue proposes creating a new grid example to showcase all the built-in cell types that are currently not demonstrated in any existing examples. The goal is to make it easier for users to discover the capabilities of the grid's various column types without having to delve into the source code.
This issue proposes creating a new grid example that demonstrates filtering a large dataset (at least 10,000 rows) using the header row filters. The example should include various data types like text, category, number, date, and boolean, with appropriate filter configurations.
This issue requests the creation of a new, user-friendly example for the Grid component demonstrating pinned columns. The current example is a test fixture and doesn't effectively showcase the feature's aesthetic or functional capabilities to visitors. The fix involves creating a new example with a more relatable data set and proper page structure.
This issue is an open call for article submissions to the GallantTarry project. Contributors can submit articles in any language and on any topic, following a simple two-line Markdown header format. Submissions can be made by commenting on the issue or by creating a pull request.
The 'treeBigData' example in the grid component currently opens with all rows collapsed, requiring a click to reveal the tree structure, helper lines, and value banding. The proposed fix is to have the tree open with at least the first level expanded by default, making the tree's visual elements immediately visible.
The 'big data grid' example in the Neo.js project incorrectly represents its scale to new users. While the page title and catalog record claim large dimensions (100k rows, 5M cells), the grid initially displays a much smaller subset (20k rows, 50 columns) with no visible indication of the larger available data. This issue requires updating the UI to accurately reflect the grid's capacity.
This issue requests documentation for the PeaZip command-line interface. PeaZip is an archive tool that acts as a frontend for other utilities, and the goal is to document its various command-line options for creating and extracting archives. The provided link offers a starting point for understanding its CLI usage.
This issue proposes to completely remove Mockito from all tests within the project. The goal is to replace existing Mockito usages with 'fake objects' as part of an ongoing effort to improve testability and reduce external dependencies.
This issue identifies a violation of Java coding conventions within the `PrepareSql.java` file. Specifically, lines 79-85 contain tab characters instead of the required spaces for indentation. The fix involves replacing these tabs with the appropriate number of spaces to adhere to the project's coding standards.
The user reports a significant discrepancy between the decode throughput reported by the `bench_serving` script and the actual decode throughput logged by the engine. This inconsistency is more pronounced with smaller models and higher concurrency levels, suggesting a potential issue in how throughput is calculated or reported in the benchmarking tool.
This issue is a call for help to test a location-based sign-in feature for "雨课堂" (Yuke Tang). The code for this feature is already written, but the developers lack a reliable way to test it. They are inviting users who are experiencing issues with this sign-in method to volunteer for testing.
This RFC proposes a new "Thinker-only" mode for full-duplex serving in real-time multimodal assistants. This mode optimizes resource allocation by disabling server-side speech synthesis, focusing solely on input processing, understanding, and text generation. The goal is to enable applications that handle their own speech output or display text responses, while still leveraging the assistant's continuous input processing and response timing capabilities.
The Jira Assistant browser extension (v3.0.0) is failing to inject content scripts into Jira pages on Firefox. This is due to the content script attempting to access the browser API via `window.chrome` or `window.browser`, which are undefined in Firefox content scripts, causing it to crash on load.
Multiple users on the same "hive" are encountering issues with Spektacular's shared workflow state. When one user starts a spec and leaves it unfinished, it blocks or overwrites subsequent specs started by other users on the same hive, as Spektacular uses a single state file within a shared repository checkout.
help wantedstage/040-covered-by-prhive/claimed-by-human
The report title is incorrectly displaying the formula `{report:autoReporting:end}` instead of the expected date. This issue occurs when a specific formula is set for report titles in the workspace settings and is reproducible on Windows and MacOS Chrome.
This issue reports a UI inconsistency on the Google Summer of Code page, specifically a large empty space on the right side and the absence of the scroll-to-top navigation feature found on other Meshery website pages. The goal is to make the GSoC page layout consistent with the rest of the site and restore the missing navigation functionality.