Good First Issues in Clojure

Describe the bug If Slack fails while Metabase is building or posting a subscription/alert (for example the Slack API rejects a file upload or a message post), the notification often never arrives but the parent send is still logged as Success. To Reproduce Set up a dashboard subscription (or alert) to Slack Cause Slack delivery to fail (bot missing from a private channel, revoked/invalid token, etc) Let the subscription/alert run. Check task history See it's logged as "successful" Expected behavior If Slack delivery fails, that send should not be recorded as a full success. The failure should show up on the send the user looks at (not only in server logs, and not only on a nested row that is easy to miss). Logs No response Information about your Metabase installation tested in 63.13 Severity delivery can fail silently from an admin’s point of view Additional context No response

What problem will this feature request solve? Alert task history doesn't distinguish between successful delivery and successful non-delivery. When “Don’t send if there aren’t results” is enabled, the alert can successfully run but intentionally not send anything because there are no results. If a user expected the subscription to be delivered or didn't expect the results to be empty, they may ask why they didn't receive it. For admins, it isn't easy to determine that this is what happened. From Admin, the run appears successful, with no indication that delivery was intentionally skipped. This creates ambiguity when troubleshooting a missing alert and can lead admins to investigate Slack, the alert configuration, or the underlying dashboard when nothing is actually broken. Describe the solution you'd like. Make intentional non-delivery visible in Admin tooling so admins can distinguish between: An alert that successfully ran and was delivered An alert that successfully ran but

Description of the bug The backend rejects the England flag emoji (🏴󠁧󠁢󠁥󠁮󠁧󠁿) when it is added as a reaction to a document comment. Backend validation limits emoji length to 10, while this emoji has length 14. Reproduction steps Open a document and create a comment. Add a reaction using the England flag emoji. Search for “England” in the emoji picker. Expected behavior The reaction is accepted and added to the comment. Logs The reaction request returns a 400 error. Diagnostic information Occurs on master. Severity P3

Describe the bug On the Alerts management page (/monitor/notifications), the count badge on the active tab is unreadable in dark theme: white text on a light blue background. To Reproduce Switch to dark theme Go to /monitor/notifications Look at the count badge on the selected tab (e.g. "All alerts") Expected behavior Count on the active tab is readable in both themes. Cause TabCountBadge in frontend/src/metabase/monitor/tools/notifications/NotificationsTabs/NotificationsTabs.tsx renders the active badge as: <Badge variant="filled" size="xs" color="brand" c="white"> The badge background resolves to --mb-color-background_surface-brand-strong, which is light blue in dark theme, while c="white" hardcodes the text color and overrides the badge's own --badge-color: var(--mb-color-text-primary-inverse) (which would resolve correctly). Dropping the hardcoded c="white" should fix it. Light theme is unaffected (dark blue background + white text).

When generating the OpenAPI spec of a public API using Reitit and Malli, I would like to be able to hide certain details of the Malli spec. Example: [:and :string [:enum {:openapi {:hide true}} "a" "b"]] ;-> only `:string` is encoded in the OpenAPI spec, `:enum` does not appear

If you are using Datalevin, please comment on this issue.

Describe the bug If you make a chart with pivoted view of normal table viz (NOT the pivot viz), the subscriptions containing the chart will show non-pivoted view To Reproduce Build a question "Count of orders by Product -> Category and User -> Source" Switch visualization to a table (not pivot table) Metabase should automatically build a pivoted view, but if not, open viz settings and toggle on Pivot table Add the table to a dashboard Set up a dashboard subscription and test it The table will be sent unpivoted Expected behavior Subscriptions should respect all viz settings, even the ones we don't like Logs No response Information about your Metabase installation 62.3.5 but most likely always has been like this Severity P3 Additional context No response

Is your feature request related to a problem? Please describe. In the workspace, once the search UI is open (either Search layers or Search on canvas), there is no keyboard way to dismiss it — closing requires reaching for the close (X) control with the mouse. Pressing Escape is the standard convention in most tools and operating systems for dismissing panels, dialogs, and overlays. Not supporting it here breaks a deeply ingrained habit and interrupts keyboard-first workflows. This is a small UX enhancement complementary to the toggle behaviour described in #9528, and sits on top of the search work landing in the 2.16 milestone (related context: PR #8899). Panels in scope The following panels have been identified as missing Escape-to-close support: Search (Search layers / Search on canvas) — related to #9528 and PR #8899 History Shortcuts Other panels in the workspace should be audited and brought into alignment with this behaviour where applicable. Describe the solution you'd li

Is your feature request related to a problem? Please describe. When a designer selects an element in the Penpot workspace, the only way to check its dimensions is to look at the Design panel on the right sidebar. There is no visual feedback directly on the canvas. This forces an eye movement away from the canvas even for the simplest sanity check — "is this box 240 px wide?" — adding friction that compounds during dense layout work or when reviewing someone else's design. Additionally, when resizing an element, the current tooltip only appears near the handle being dragged, far from the element's center. The size badge provides a stable, centered reference point that updates live during the entire resize interaction. Describe the solution you'd like Show a small read-only badge directly below the bounding box of the selected element (or combined bounding box for multi-selection), displaying width × height. The badge is always visible while an element is selected, and updates live

Hello :) Found myself having to make some stylistic compromises with decimals in my schema, and would have liked it if it was supported like a :double schema with min max preds and bound generation. Alternatives: use decimal? and custom generators / and :and for bounds define my own schema Thanks