Exceptions should not be represented with object declarations❗ Even though they look like having no mutable state, they do - each exception contains stacktrace, so each exception must be unique.

TC39 is working to standardize error stacktrace APIs and hopefully clean up this mess

u hate java stacktrace ? try elisp 😍

@tenderizzation [...] In ’21, PyTorch released torch._assert_async, their most sophisticated debugging API. Clean, efficient, asynchronous. It really lets you feel the stacktrace.

久しぶりにstacktraceにゴルゴ出てきた https://t.co/bwFry4mqRd

Exceptions should not be represented with object declarations❗ Even though they look like having no mutable state, they do - each exception contains stacktrace, so each exception must be unique.

New stacktrace layout in @reatom/core@1000.0.0-alpha.53 — much more compact, just as informative.

fly, my 7 km tall Vessel!

>get email >"help our requests are failing" >look at details >stacktrace of their own system i feel for juniors struggling to get jobs when """seniors""" do stupid shit like this

yeah mongodb, pls include the stacktrace in the subject too

Xcode 26, with Swift 6 on by default, with a project that compile with 0 warnings will ship with that. A fucking crash when you're apparently calling a framework from the wrong thread. But no stacktrace for you, no information. This is going on for a while, can't believe it.

Java developers can now read the whole stacktrace at once. ☕

something i think* could be really useful from codex/claude is ability to trace code and find all possible places where an obsercure javascript error like "TypeError: Cannot read properties of null (reading 'id')" might be coming from when there is no stacktrace available in the

If you click "Deep Profile" in Unity's profiler you can go into a single frame (=between two screen renders) and see exactly what all threads were doing millisecond for millisecond. It even saves a stacktrace for every single moment. 🤓

JavaScript Tip 💡 Use 𝙴𝚛𝚛𝚘𝚛.𝚌𝚊𝚙𝚝𝚞𝚛𝚎𝚂𝚝𝚊𝚌𝚔𝚃𝚛𝚊𝚌𝚎 to capture the stack-trace where you throw the error–especially useful when the error doesn't have a stacktrace. 𝙉𝙤𝙩𝙚: 𝙏𝙝𝙞𝙨 𝙛𝙚𝙖𝙩𝙪𝙧𝙚 𝙞𝙨 𝙣𝙤𝙣-𝙨𝙩𝙖𝙣𝙙𝙖𝙧𝙙

intuition be strong follow along but remember to backtrace cognitive stacktrace rekindled by @_TheResidency

unlocked some (for now) hidden @alchemy_run lore yesterday one of the best parts of alchemy is how easy they make it to handle env vars and secrets when using Cloudflare (and other clouds), surfacing errors sooner to preventing type errors and getting lost in a stacktrace while

Observer also has a new callout for tracking down where a span originated. This uses standardized opentelemetry attributes. Plain model queries use this to include a full stacktrace in local development, and in production you still get the file/line/function

Neovim、Vim(not 9) scriptと違って、エラーになったらstacktrace出るの、うれしすぎる…！！