Ned Andreev

We should probably also add a context to either the current `Stop()` function, or, ideally, to my proposed `wait() error` function, like this: ```go type Output interface { // The...

In the course of removing the `Engine` (https://github.com/grafana/k6/issues/1889) by rebasing and polishing [this old PoC commit](https://github.com/grafana/k6/pull/2438/commits/8850e35c674ff9c2428c35d0db0b202c165e622c) from https://github.com/grafana/k6/pull/2438, I started hitting some import cycles due to https://github.com/grafana/k6/pull/2536 :disappointed: :face_exhaling: But...

It seems worth it to also allow other request options (https://docs.k6.io/docs/params-k6http) to be specified globally. It'd be especially useful to be able add cookies or to change the global default...

https://github.com/loadimpact/k6/issues/1865 is a request to be able to specify the `Content-Type` header globally, which I'll close in favor of this issue. In general, it's not certain if we'll implement this...

Now that we have https://github.com/loadimpact/k6/pull/1768, this issue should be relatively easy to implement. Though we might need to refactor the `js.Runner` a bit, if we want to be a bit...

As has become apparent in the course of https://github.com/loadimpact/k6/pull/1849, this feature has a lot of hidden complexity and deserves a lot of consideration before we implement it. Specifically, we either...

Then doesn't it become too easy enough to trigger this accidentally? And very important that you don't accidentally pipe something to k6's stdin... Binding `Enter` would also preclude us from...

There was an attempt to implement this issue (https://github.com/grafana/k6/pull/1849), however, as it's obvious by the comments in the PR, there were some unexpectedly tricky issues around it (mostly in how...

Yeah, the size is a big part of it, but not all of it. Personally, given my already existing Go development setup, I see no reason whatsoever to introduce any...

I've been thinking on some related issues to this problem recently and I think I was wrong :arrow_up:, especially with this: > stopping and starting outputs doesn't really need to...