Mark S. Miller

Closing as won't fix. But see https://github.com/endojs/endo/issues/576#issuecomment-800840188 We should report this bug upstream to regenerator-runtime.

Hi @Jack-Works , Reopening, thanks. Do you have a taming in mind? Happy to review a PR.

Could we exempt whole directories, so we don't need to exempt test262 tests individually? Since they are not under our control anyway?

Hi @boneskull , thanks for this! As you suspect, it intersects a lot of error issues I'm wrestling with, so I assigned myself. A key issue is to find an...

Why would `@endo/compartment-mapper` not have the same constraints as ses? Not rhetorical. I genuinely am not oriented enough to have a strong opinion, but I am skeptical.

> We should continue to discourage callers to classify errors based on message name. @kriskowal , I have been encouraging exactly this. Clearly this is another error issue we need...

That is, I encourage `.name`. I don't know if this is what you mean by "message name". I certainly discourage treating `.message` as semantic.

> To that end, I'm not sure exactly what SES is redacting from exceptions or why (but I'd love to know!). Primarily two things: # Redaction of sensitive user data...

Some info on "1. broken functionality". All examples are from Brave unless stated otherwise. which is from https://github.com/endojs/endo/blob/f8aa142fb0fd70c366296e168097ff4d819db1e5/packages/ses/src/error/tame-console.js#L159 As seen in the hover, `event.error` is `null`, which I think is...

The full event is in which the `ErrorEvent`'s `message` is the less informative `'Script error.'` and there is no filename or linenumber.