Joan López de la Franca Beltran

Hey @mstoykov, thanks for the proposal! I haven't reviewed the PR in-depth yet, cause I guess there's some polishing still remaining. But here are my 2cts on the proposal: -...

Here's my take: > Currently I identify 3 API questions that can't be fixed with "we will add it later": > > ### String and Strings > ... > >...

To follow up on what's been discussed asynchronously, what do you prefer @mstoykov / @oleiade: to completely remove these loglines, or logging them as `trace`, as-is now? Thanks! 🙏🏻

> To be honest I do not think that the usage of this log in the way we had to diagnose it is ... good. But it happened to be...

> I have also fixed the imposter base path bug, that I later realized is already implemented by #173. I can remove it, but it would be nice to have...

Thanks for your contribution @alex-kattathra-johnson! 🙇🏻 Now, let's wait for my folks to review it and bring some feedback. I unassign myself meanwhile, as there's nothing else I can help...

Jfyi @mstoykov, this is fixed here: https://github.com/grafana/k6/pull/4787, but that PR also includes other changes that I don't think we want to merge as-is.

Hi @Fernando-hub527, We're discussing internally if really want to merge this new behavior for thresholds as-is, or perhaps offer another workaround to sort it out. So, could you please split...

Hey @Fernando-hub527, I'm going to close this pull request because after some internal discussions, I even stronger believe we won't want to change this behavior on thresholds, as it would...

Hi @silverskater, Thanks for your feature request, I definitely think that it would be nice to have support for such cases. However, after a quick look, I realized that the...