Joan López de la Franca Beltran

> One common issue encountered by users is that JS tends to be rather slow when performing parsing operations. Take this just a simple idea rather than something that's really...

Pushing to https://github.com/grafana/k6/milestone/42 while waiting for news.

Hey @cchamplin, Could you try to address what @olegbespalov suggested, please? Once done, I think we'll be ready to merge it. Thanks! 🙇🏻

Hi @pablochacin, Looking at the k6 codebase, that's the expected behavior, because [it explicitly sets one output format](https://github.com/grafana/k6/blob/master/cmd/state/state.go#L67-L69) or the other depending whether k6 is executed in a terminal or...

I'm wondering, if there's any other way to bypass that, or if the change we could make is to leave the default behavior as-is but add a mechanism to bypass/force...

Hey @gm42, How often have you been able to reproduce it? I tried multiple times, simulating an OOM scenario in the server side, with no luck. That said, have you...

Any news @gm42? I spent some more time trying to reproduce this by reproducing a few more corner cases, as well as intentionally faking the `14 UNAVAILABLE` gRPC status code,...

Considering that: - this seems to be happening because there's some "remaining" code running even after [calling `close(samples)`](https://github.com/grafana/k6/blob/master/cmd/run.go#L274) - [the `AsyncInvoke` code ](https://github.com/grafana/k6/blob/master/js/modules/k6/grpc/client.go#L291) specifically looks pretty safe in terms of...

Hi @AugustoRickes, Have you seen the k6 docs around [using Node.js modules](https://grafana.com/docs/k6/latest/using-k6/modules/#use-nodejs-modules)? I'd say that, at first glance, this looks like an expected error. Could you double-check that, and confirm...

Closing as there has been no reply for a while, and because this looks more like a discussion that can be handled in https://community.grafana.com/c/grafana-k6/70, instead of an actual bug or...