This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-12-05
Channels
- # adventofcode (89)
- # announcements (9)
- # babashka (11)
- # beginners (8)
- # biff (5)
- # calva (4)
- # cherry (121)
- # clara (15)
- # clerk (16)
- # clj-kondo (20)
- # clj-otel (2)
- # cljdoc (20)
- # clojure (84)
- # clojure-austin (1)
- # clojure-bay-area (3)
- # clojure-berlin (1)
- # clojure-czech (2)
- # clojure-europe (59)
- # clojure-nl (1)
- # clojure-norway (12)
- # clojure-poland (1)
- # clojure-uk (15)
- # cursive (16)
- # datomic (46)
- # events (3)
- # fulcro (85)
- # graalvm (20)
- # hyperfiddle (11)
- # improve-getting-started (1)
- # lsp (7)
- # off-topic (48)
- # overtone (8)
- # podcasts-discuss (4)
- # re-frame (31)
- # releases (1)
- # ring (12)
- # sci (13)
- # shadow-cljs (8)
- # specter (3)
- # squint (26)
- # xtdb (5)
- # yamlscript (6)
I'm on io.github.nextjournal/clerk {:git/sha "e8f275b5cf077ec9441e404c1885ff0b6ee0aef9"}
and I've noticed I'm suddenly having issues with exception/error reporting.
I rarely get the expected error popup until I restart my serve process, otherwise I get a blank notebook.
I've recorded a sample below (spoilers for aoc day 5, for trivial cases it seems to be fine. Also bear with the loading, I think it's because I was also capturing the video)
No errors in the browser console other than it trying to render a null element
hi @U043RSZ25HQ. Unfortunately I cannot reproduce this issue with the same clerk version. I’m causing the same exception (assoc on cons) but the error message renders as expected when the expression is evaluated. Maybe we need more context to reproduce, or the notebook source...
Sure, my repo is https://github.com/elken/aoc; I can replicate it with pretty much any notebook, I randomly picked 2023/day04 and changed one of the functions to be an invalid symbol and it triggered. Huh, interesting note that I have a block at the start of all my solution notebooks to pull the problem HTML from AOC; if I comment that out it seems to work fine...
Not merged yet, but that’d be great if you could give "eb89e0b2e9edf8937c7c4a14c6df0ebc3217adeb"
a spin and see if it still reproduces?
Seems to still work fine, but it points out that stack trace CSS might need some changes for larger displays 😄
@U043RSZ25HQ thanks for checking! And come color adjustments.