Horsty

I'm facing this issue, any news on it ?

Ok i have this bug =/ Same the run-id doesn't work

Hey :) i'm surprised this feature is available on docs, but not in blog What is the status about this feature ? I've start migration my old blog to new...

I'm facing this issue, but not on all my playwright project. I've 2 projects with e2e, both use chromium, and i mock request to get `postDataJson()` On the first project...

I've update to "vitest": "^1.2.0", "@testing-library/jest-dom": "^6.2.0", with the @andykenward docs and everything is working fine for `toBeInTheDocument` assert I don't have TS error

Hey @sethvanwykJET have you some news on this issue have you try some fix on CodeceptJs ? In time I have investigate due to same error and open an issue...

@kobenguyent after investigation, we have found that the issue is not about `retryTo` but occurs when a promise reject. This is enough to stale the process ```ts Scenario('Rejected promise stale...

I have "stale" process issue to, but i'm unable to determine why ? Any help on this ✌️

This will be a very usefull improvment for run-workers command It's frustrating to have `run-workers 8` and at the end see only 1 or 2 worker running the last 10/20...

I get this issue with another Capcom game "Dragon's Dogma Dark Arisen" =/