Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.
We catch SDODS errors in a small wrapper to add our own reporting. The self-healing guide's resolution diagram ends at a node labelled SdodsHealError, so I wrote:
if (err.constructor.name === 'SdodsHealError') { /* ... */ }which never fires. What we actually get is a SdodsError. Which one is right?
Accepted answer
The output is right and the diagram is wrong. There is no SdodsHealError. The healer throws SdodsError with the code HEAL_FAILED, a message naming the description and the primary selector, and a hint listing the probe scores.
Match on the code, never the class name:
if (err instanceof SdodsError && err.code === 'HEAL_FAILED') { /* ... */ }Every structured error carries code, message, hint and docsUrl, and with --json they are printed as JSON on stderr, so the code is the stable thing to key on in either shape. I will get the diagram label fixed.
Wrap commands and output in triple backticks and they will render as a code block.
Checking whether you’re signed in…
Have a different question? Ask it.