Clojure good first issues

The backend rejects the England flag emoji (🏴󠁧󠁢󠁥󠁮󠁧󠁿) as a comment reaction because its length (14 characters) exceeds the allowed limit of 10 characters. This results in a 400 error when attempting to add the reaction.

Metabase incorrectly logs Slack subscription and alert deliveries as successful even when Slack API errors occur, leading to silent delivery failures. The issue requires that failures be clearly indicated in the task history rather than just in server logs or nested rows.

The text input field for renaming a card embedded within a document does not visually indicate when its content is selected. This can be confusing for users, as they might mistakenly believe the input has reverted to static text. The issue occurs when attempting to select text within the card's name input.

This enhancement request proposes adding web search capabilities to ECA, potentially through an MCP tool or a native ECA tool. Key considerations include handling API rate limits and key management, and the possibility of supporting multiple search providers, similar to the Zed editor.

In dark theme, the dashboard tab row scroll button displays a harsh, light-colored gradient instead of a smooth fade into the dark background. This is caused by the `alpha()` helper always using a light color scheme, resulting in white transparency stops that are visible against the dark theme.

Users are unable to navigate to the Admin area from an unsaved SQL question or document. Although a confirmation modal appears and the current page unmounts, the Admin page fails to mount, leaving the user on a blank or broken state.

This issue proposes optimizing the `get-view-only-bundle` function to fetch only the relevant share-link for anonymous users, preventing the loading of all sibling share-links into memory. This change aims to improve security by further protecting share-link secrecy and enhance performance on the anonymous viewer path.

A modal dialog unexpectedly remains open after a user navigates to the plans page via a "See my current plan" button. The modal should be dismissed automatically when this navigation occurs, ensuring the plans page is fully visible and accessible.

This feature request aims to improve the user experience when reordering layers in a sidebar. Currently, users cannot scroll the sidebar while holding a layer to reposition it, relying instead on auto-scrolling. The proposed solution is to enable simultaneous mouse scrolling and layer dragging for smoother repositioning.

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.

When a Metabase chart is configured with a pivoted table visualization (not the dedicated pivot table viz), dashboard subscriptions fail to render the chart in its pivoted state. Instead, the subscriptions consistently display the unpivoted version of the table, indicating a discrepancy in how visualization settings are applied to subscriptions.

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.

This issue reports a visual bug in Metabase's "Inspect" tab for transforms. Specifically, the text "To inspect the transform you need to run it first" and the chevron icon in the "Run now" button are not vertically centered as expected. This is a frontend styling issue.

This feature request proposes adding Penpot-specific board size presets to the "Size presets" panel. The goal is to provide users with readily available dimensions for file thumbnails, template covers, and plugin icons/covers, eliminating the need for manual lookups and streamlining the creation process for these assets.

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.

This issue highlights that several environment variables and flags related to MCP (Microservice Communication Protocol) and internal resolvers are not documented in Penpot's technical guide. The user requests that these undocumented configuration options, including PENPOT_MCP_URI, PENPOT_MCP_URI_WS, enable-mcp, and PENPOT_INTERNAL_RESOLVER, be added to the official documentation.

A bug exists where alerts continue to fire even after their associated webhook channel has been deleted. This leads to alerts appearing in activity logs with no destination, indicating a failure to properly clean up resources upon channel deletion. The desired behavior is to either notify an admin, delete, or stop these orphaned alerts.

When inspecting a Metabase transform, clicking on a lens card that displays a pie chart incorrectly opens the ad-hoc question as a bar chart. This occurs because the `displayIsLocked` flag is not correctly preserved when generating the URL for the opened question, causing the query builder to recompute the visualization.

The "undo" toast message in Metabase is displaying misaligned text content. Specifically, the text is not vertically aligned with the button, while the icon should remain centered. This issue is suspected to be a regression from a previous pull request.

Users are reporting that custom CSS styles applied to tags on Logseq pages are not being rendered correctly within query results. The styling works on regular pages but fails when tags are displayed as part of a query, specifically when tags are stored in properties. This suggests an inconsistency in how Logseq processes and applies CSS to tags in different contexts.

The issue describes a bug where column names in Slack and Email alerts do not match the column names displayed in the dashboard. Specifically, the first column name is duplicated in the alerts, while the data order remains correct. The reporter later found a workaround involving converting the model to a question, adjusting alignment and display settings for a specific column, suggesting a potential issue with foreign key handling.

In dark theme, the count badge on the active tab of the Alerts management page is unreadable due to white text on a light blue background. This is caused by a hardcoded white text color in the `TabCountBadge` component that overrides the intended inverse text color for the badge background.

This issue requests an enhancement to Reitit and Malli's OpenAPI generation to allow hiding specific parts of a Malli schema. The goal is to prevent certain details, like enum values, from being exposed in the generated OpenAPI specification, as demonstrated by a provided example.

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 main menu in the application is being obscured by the toolbar when the window is resized to a smaller width. This prevents users from interacting with the menu items. The issue is specific to the 'HOURLY' environment and does not occur in 'PRE' or 'PRO'.