Raphael Gaschignard

Confirming this issue as well (`typescript-mode`)

Serious question: while synchronisity is a problem for JS because of the interaction model with the top level, if Pyodide's code evaluation entrypoints were _all_ async (that is to say,...

I'm actually a _bit_ convinced [the stack trace breakage was at one point being done intentionally](https://github.com/stripe/stripe-node/blob/18f88e487723cba994afd38dc645a709211e33b3/lib/utils.js#L317) from this utility function, at least for some methods. While if you do things...

@yejia-stripe sorry for taking a while to get back. Unfortunate the workaround does not work for usages around async iteration: ``` for await (const sub of wrappedStripe.subscriptions.list({limit: 10})) { console.log(sub)...

After working on this more, and trying to get the proxying to work, I found that using the proxy means that `autoPagingEach` and friends will also not work. I would...

We're running into this as well, after thinking about how the reading and writing works, it kinda feels like the best option for files relying on streaming is to say...

I've hit a similar issue here, the following html file will hit the Maximum call stack size exceeded error on Chrome but not on FF or Node ``` let scriptToRun...

``` let scriptToRun = ` import sys print(sys.getrecursionlimit()) # locally, this causes nasty crashes at 1500 in Chrome, 10000 in Firefox sys.setrecursionlimit(10000) class AlwaysDefault: def __init__(self, default): self.default = default...

Another thing I noticed here (though I don't know if it's really solvable at all?) is that after this happens Pyodide is placed in a permanently disabled state. Are there...

To be clear, currently, when hitting the error, Pyodide wraps the error and says to report it upstream. Doing this sort of error filtering would make it obvious that this...