Post #2971424
2026-05-14 18:23 UTC
@encthenet@flyovercountry.social ah, I was reading “no clue where it’s being called from” as a bit more load-bearing to the problem here. I was incorrectly assuming that any sensible call site would have its own exception reporting and so the issue you were looking for was more “wait why isn’t the existing except: around this showing me what I need to know” rather than “what was the exception”
Replies (2)
-
@glyph@mastodon.social 2026-05-14 18:24
@encthenet@flyovercountry.social this is very much framework-maintainer brain
-
@encthenet@flyovercountry.social 2026-05-14 20:31
@glyph@mastodon.social Yeah, the upper layers were reporting the exception, but only the exception, so not that useful in the general case, but it makes sense for this since it's more end user facing, so dumping a long stack trace isn't that useful.