CodeceptJS 3.7 + WebDriver 8 produce error 'Failed to execute WebDriver Bidi command "sessionSubscribe"'

[ngraf]

Current state

Given you use CodeceptJS 3.7 and WebDriver 8+
When you run npx codeceptjs run
Then you will see an errror
'Failed to execute WebDriver Bidi command "sessionSubscribe" as no Bidi session was established. Make sure you enable it by setting "webSocketUrl: true" in your capabilities and verify that your environment and browser supports it'

Target state
The Bidi error does not occur.

Info

• Tests are still functional. It seems like there is no direct negative functional impact other than the frightening STDOUT.
• I created a proof of concept how to reproduce it:
  1. Clone my fork of "codeceptjs-examples" from https://github.com/ngraf/codeceptjs-examples/tree/bugfix/failed-to-execute-webdriver-bidi-command
  2. Checkout branch "bugfix/failed-to-execute-webdriver-bidi-command"
  3. Install dependencies npm i
  4. Run examples tests with WebDriver npx codeceptjs run -c codecept.webdriver.conf.js
     -> You will then see the errors:

[ngraf]

I can confirm "3.7.2-beta.2" fixes the issue in the described case of https://github.com/ngraf/codeceptjs-examples/tree/bugfix/failed-to-execute-webdriver-bidi-command.

... but I am bit hesitant to say it will work in all cases.
When I use "3.7.2-beta.2" in my main complex test suite, the process hangs forever in a before hook.
✖ "before each" hook: codeceptjs.before for "My first Scenario"

I cannot yet figure out if it the root cause is the code change in "3.7.2-beta.2" or if it is a fault in my test suite configuraiton. What I know is that "3.7.1" worked at least and did not hang in "before" hook. I try to dig deeper if I can find the cause.

My hottest guess right now is that issue is BiDi+Selenoid. Selenoid is my default place to run WebDriver tests. If I use local WebdriverIO, the test is green.
By the change
8c1017f
config.capabilities.webSocketUrl = config.webSocketUrl || config.capabilities.webSocketUrl || true
in "3.7.2-beta.2" you now have strengthen the support/integration of BiDi protocol? But Selenoid does not support BiDi at all. If this assumption is right, I wonder what has changed in 3.7.0 compared to 3.6.x that now BiDi got on the stage? Before in 3.6.5 I used also WebDriver 8.x and Selenoid with no issue. Now the issues started with 3.7.x.

[DavertMik]

@ngraf could you get a stack trace on

✖ "before each" hook: codeceptjs.before for "My first Scenario"

Execute tests with --verbose flag

And check if there is stack trace

If nothing found run tests with DEBUG="codeceptjs:*"

And attach issue here