Clojure good first issues

Context menu items in Penpot, particularly in languages like French, are wrapping to two lines when their text is too long for the fixed menu width. This causes inconsistent padding and makes the text harder to read. The user suggests removing fixed sizing for menu items and allowing them to expand horizontally to accommodate longer text.

When sending a test alert from a question, the user receives no feedback if the send operation is successful. This differs from dashboard subscriptions, which provide a clear confirmation. The issue is that the current implementation only shows feedback for failed sends, leaving users unsure if the test alert was actually delivered.

When exporting elements in Penpot, zombie chrome-headless processes are being created on the server. These processes are children of the penpot-exporter Docker container and are not being properly cleaned up by the parent process. This leads to a buildup of defunct processes over time.

When editing the 'L' (lightness) value in HSL mode within the color picker, the 'H' (hue) and 'S' (saturation) values are unexpectedly reset to 0. This bug prevents users from adjusting lightness without losing their chosen hue and saturation, unlike editing other color channels or modes.

The Gauge visualization incorrectly removes all defined ranges when a minimum or maximum value is left empty in a range definition. This results in the gauge displaying a default scale of 0 to 1 and turning grey, with no user feedback in the editor indicating the invalid range. The expected behavior is for valid ranges to remain displayed and for the editor to clearly signal the requirement for both bounds in a range.

A bug is reported where the "Most active people on this dashboard" bar chart is rendering incorrectly. Specifically, the row labels are not aligned with the bars, and there are large gaps between bars. The issue appears to be resolved when the visualization stacking setting is changed to "Stack".

When a favorited page's capitalization is changed, it appears as a duplicate in the favorites sidebar. The expected behavior is for the page to remain listed only once.

Metabot action buttons are invisible when focused by keyboard users, making it difficult to navigate and understand which button is selected. The buttons are hidden by default with `opacity: 0` and are only revealed on hover or when they are the last message. The issue suggests adding a `.messageActions:focus-within` selector to make the entire set of actions visible when focus is within their container.

Users are unable to select values in a single-select dropdown filter using only the keyboard. While multi-select dropdowns are keyboard accessible, single-select options are skipped when tabbing, preventing keyboard-only users from interacting with this filter type.

The `remoteAddress` field in authentication rules currently only matches exact string equality, failing to support CIDR blocks as documented. This leads to rules intended for subnets not matching any callers and also causes issues with IPv6 loopback addresses due to string representation differences. The proposed solution involves parsing `remoteAddress` into an IP address or CIDR block at configuration load and performing proper `InetAddress` comparisons.

This issue proposes a minor UI enhancement to the "Update catalogue item" button. The suggestion is to make the button label plural, such as "Update catalogue items", and to potentially include a count of selected items, like "Update catalogue items (3 selected)". This change aims to improve clarity and user feedback when multiple items are being updated.

This feature request aims to improve the alert task history by distinguishing between successful alert deliveries and intentional non-deliveries due to empty results. Currently, both scenarios appear as successful runs, causing confusion for users and making troubleshooting difficult for administrators. The proposed solution is to explicitly indicate in the task history when an alert was skipped because it yielded no results.

A redundant scrollbar appears or flickers when scrolling a container that displays tooltips, specifically when hovering over ellipsified question names in the 'Add questions' sidebar. This issue seems to be app-wide and requires a holistic fix to prevent recurrence.

This issue proposes adding a feature to Metabase that would read and display descriptions for SQL Server tables and columns. These descriptions are stored in SQL Server's extended properties, a common practice for self-documenting databases. Implementing this would enhance Metabase's documentation capabilities for SQL Server users.

The "Quarter and year" date filter in Metabase displays "TT" for all quarters when the language is set to French, making it impossible to select the correct quarter. This issue is similar to previously reported bugs in Portuguese and Spanish localizations.

The issue describes a bug where range inputs in Metabase's chart settings (Gauge and Conditional Colors) only update the chart after the input field loses focus (on blur). This is inconsistent with other number inputs in the same sidebar, which update the chart in real-time as the user types.

This issue proposes an improvement to the 'Open Decklists' view by organizing cards by their type instead of alphabetically. The current presentation is shown in an attached image, and the desired change aims to enhance usability and readability for users viewing decklists.

A bug in XTDB's Flight SQL implementation causes writes with mixed-type arguments to fail before reaching the XTDB core. This issue is triggered by operations like `:put-docs` where a single field contains values of different data types, commonly seen with schemaless documents and FHIR resources. The problem manifests as a gRPC `INTERNAL` error on the client and an `ArrayIndexOutOfBoundsException` on the server.

This issue requests that the search query in the Swap component menu persist when a user switches between libraries. Currently, the search field is cleared upon library change, forcing users to re-type their search term for each library, which hinders efficiency, especially when dealing with multiple connected libraries.

Users are unable to rerun query builder previews after the initial run or by using the "Cmd + Return" shortcut, which is indicated as a way to trigger a preview. This prevents users from re-evaluating their query after source data changes without making modifications to the query itself.

The Cmd+Return shortcut for running SQL queries in the SQL transform editor only functions when the cursor is actively within the SQL text area. This is inconsistent with the main app's SQL editor and the editor's own hint, which suggest the shortcut should work from anywhere on the page.

When editing a 'Description' column in a table, the textarea editor grows vertically, causing the row to expand. This expansion pushes subsequent rows down visually, but the underlying grid layout doesn't adjust, leading to the editor rendering behind the rows below and creating visual overlap. Hovering over rows below the edited one also reveals the text from the editor behind them.

This issue requests the implementation of a standard user experience enhancement: closing the workspace search panel (for layers or canvas) by pressing the Escape key. Currently, users must use the mouse to click the close button, disrupting keyboard-centric workflows. The proposed solution is to dismiss the search panel and return focus to the canvas when Escape is pressed while the search panel has focus.

This issue is a simple request for users of Datalevin to publicly share their usage by commenting on the issue. It aims to gather information about companies and projects that have adopted Datalevin.

The `@penpot/plugin-styles` package currently loads the Work Sans font from a third-party CDN (`fonts.bunny.net`). This causes issues for air-gapped deployments, exposes user IPs to a third party, and violates the Content Security Policy. The expected behavior is for plugins to render with their intended typography using only resources from the Penpot installation itself.

This feature request proposes adding a visual indicator to the Penpot workspace that displays the dimensions (width x height) of a selected element directly on the canvas, below its bounding box. This aims to improve user experience by reducing the need to constantly check the right sidebar for size information and providing a more intuitive live feedback during resizing.

The Metabase sync-fields process is repeatedly fetching the same database cursor information from the application database, even though this information should be static during a sync. This leads to unnecessary database load and performance degradation.

This issue proposes optimizing frontend components by memoizing derived collections, specifically those generated by `d/enumerate` which adds indices. This aims to reduce unnecessary memory allocations and processing during component re-renders that are not related to the collection's data. The plan involves creating a shared indexing transducer and then systematically applying this memoization pattern to various components.

This issue reports that UI elements are overlapping their containers when the display is too narrow, indicating a responsive design or layout problem. The user has provided screenshots illustrating the issue and is seeking clarification on whether it's a bug or a feature request, along with potential micro-improvements.

This issue proposes extending support for `:median`, `:var` (variance), and `:percentile` aggregation types to additional databases. The goal is to identify and implement support for these functions in databases like Vertica, H2, and SQL Server, building upon existing work for other platforms.