Testcafe fails while establishing connection with chrome browser
Closed this issue · 9 comments
What is your Scenario?
We have a set of tests which executes every 30 mins 24/7
What is the Current behavior?
We have around 50 executions per day, but starting from yesterday, about 20-30% of these executions started failing with the following error:
The "concurrency" option from the configuration file will be ignored.
ERROR Unable to open the "chrome:headless" browser due to the following error:
Error: WebSocket connection closed
at /home/runner/work/tests/node_modules/chrome-remote-interface/lib/chrome.js:94:35
at Chrome._handleConnectionClose (/home/runner/work/tests/node_modules/chrome-remote-interface/lib/chrome.js:256:13)
at WebSocket. (/home/runner/work/tests/node_modules/chrome-remote-interface/lib/chrome.js:243:22)
at WebSocket.emit (node:events:519:28)
at WebSocket.emit (node:domain:488:12)
at WebSocket.emitClose (/home/runner/work/tests/node_modules/ws/lib/websocket.js:246:10)
at Socket.socketOnClose (/home/runner/work/tests/node_modules/ws/lib/websocket.js:1148:15)
at Socket.emit (node:events:519:28)
at Socket.emit (node:domain:488:12)
at TCP. (node:net:339:12)
Type "testcafe -h" for help.
We already tried to change browsers value to the following, but it didn't change anything:
browsers: "chrome:headless --disable-search-engine-choice-screen",
Here is the testcafe debug log for such failure:
2024-10-18T11:41:45.966Z testcafe:cli
[
'/opt/hostedtoolcache/node/18.20.4/x64/bin/node',
'/home/runner/work/tests/node_modules/gherkin-testcafe/main.js',
'--param-type-registry-file',
'./guide-to-common/features/steps/transformers.js',
'--concurrency',
'2',
'--src',
'./some.feature',
'./some.js'
]
2024-10-18T11:41:46.262Z testcafe:hammerhead:proxy:router register route GET /hammerhead.js
2024-10-18T11:41:46.269Z testcafe:hammerhead:proxy:router register route GET /transport-worker.js
2024-10-18T11:41:46.269Z testcafe:hammerhead:proxy:router register route GET /worker-hammerhead.js
2024-10-18T11:41:46.269Z testcafe:hammerhead:proxy:router register route GET /messaging
2024-10-18T11:41:46.269Z testcafe:hammerhead:proxy:router register route POST /messaging
2024-10-18T11:41:46.270Z testcafe:hammerhead:proxy:router register route OPTIONS /messaging
2024-10-18T11:41:46.270Z testcafe:hammerhead:proxy:router register route GET /task.js
2024-10-18T11:41:46.270Z testcafe:hammerhead:proxy:router register route GET /iframe-task.js
2024-10-18T11:41:46.274Z testcafe:hammerhead:proxy:router register route GET /browser/connect/{id}
2024-10-18T11:41:46.274Z testcafe:hammerhead:proxy:router register route GET /browser/heartbeat/{id}
2024-10-18T11:41:46.274Z testcafe:hammerhead:proxy:router register route GET /browser/idle/{id}
2024-10-18T11:41:46.274Z testcafe:hammerhead:proxy:router register route GET /browser/idle-forced/{id}
2024-10-18T11:41:46.275Z testcafe:hammerhead:proxy:router register route GET /browser/status/{id}
2024-10-18T11:41:46.275Z testcafe:hammerhead:proxy:router register route GET /browser/status-done/{id}
2024-10-18T11:41:46.275Z testcafe:hammerhead:proxy:router register route GET /browser/init-script/{id}
2024-10-18T11:41:46.275Z testcafe:hammerhead:proxy:router register route POST /browser/init-script/{id}
2024-10-18T11:41:46.275Z testcafe:hammerhead:proxy:router register route GET /browser/active-window-id/{id}
2024-10-18T11:41:46.275Z testcafe:hammerhead:proxy:router register route POST /browser/active-window-id/{id}
2024-10-18T11:41:46.275Z testcafe:hammerhead:proxy:router register route POST /browser/ensure-window-in-native-automation/{id}
2024-10-18T11:41:46.275Z testcafe:hammerhead:proxy:router register route POST /browser/close-window/{id}
2024-10-18T11:41:46.275Z testcafe:hammerhead:proxy:router register route POST /browser/open-file-protocol/{id}
2024-10-18T11:41:46.275Z testcafe:hammerhead:proxy:router register route POST /browser/dispatch-native-automation-event/{id}
2024-10-18T11:41:46.275Z testcafe:hammerhead:proxy:router register route POST /parse-selector/{id}
2024-10-18T11:41:46.275Z testcafe:hammerhead:proxy:router register route POST /browser/dispatch-native-automation-event-sequence/{id}
2024-10-18T11:41:46.275Z testcafe:hammerhead:proxy:router register route GET /browser/connect
2024-10-18T11:41:46.275Z testcafe:hammerhead:proxy:router register route GET /browser/connect/
2024-10-18T11:41:46.275Z testcafe:hammerhead:proxy:router register route GET /service-worker.js
2024-10-18T11:41:46.276Z testcafe:hammerhead:proxy:router register route GET /browser/assets/index.js
2024-10-18T11:41:46.276Z testcafe:hammerhead:proxy:router register route GET /browser/assets/styles.css
2024-10-18T11:41:46.276Z testcafe:hammerhead:proxy:router register route GET /browser/assets/logo.svg
2024-10-18T11:41:46.276Z testcafe:hammerhead:proxy:router register route GET /about:error
2024-10-18T11:41:46.276Z testcafe:hammerhead:proxy:router register route GET /testcafe-core.js
2024-10-18T11:41:46.277Z testcafe:hammerhead:proxy:router register route GET /testcafe-driver.js
2024-10-18T11:41:46.277Z testcafe:hammerhead:proxy:router register route GET /testcafe-legacy-runner.js
2024-10-18T11:41:46.278Z testcafe:hammerhead:proxy:router register route GET /testcafe-automation.js
2024-10-18T11:41:46.279Z testcafe:hammerhead:proxy:router register route GET /testcafe-ui.js
2024-10-18T11:41:46.279Z testcafe:hammerhead:proxy:router register route GET /testcafe-ui-sprite.png
2024-10-18T11:41:46.279Z testcafe:hammerhead:proxy:router register route GET /testcafe-ui-sprite.svg
2024-10-18T11:41:46.279Z testcafe:hammerhead:proxy:router register route GET /favicon.ico
2024-10-18T11:41:46.279Z testcafe:hammerhead:proxy:router register route GET /testcafe-ui-styles.css
2024-10-18T11:41:46.355Z testcafe:utils:temp-directory Found temp directories: []
2024-10-18T11:41:46.363Z testcafe:utils:temp-directory Temp directory path: /tmp/testcafe/chrome-profile-1923Vmfd3pmgFwZl
2024-10-18T11:41:46.369Z testcafe:utils:temp-directory Found temp directories: [ 'chrome-profile-1923Vmfd3pmgFwZl' ]
2024-10-18T11:41:46.369Z testcafe:utils:temp-directory:lockfile Failed to init lockfile /tmp/testcafe/chrome-profile-1923Vmfd3pmgFwZl/.testcafe-lockfile
2024-10-18T11:41:46.420Z testcafe:utils:temp-directory:lockfile Error: EEXIST: file already exists, open '/tmp/testcafe/chrome-profile-1923Vmfd3pmgFwZl/.testcafe-lockfile'
at Object.openSync (node:fs:596:3)
at Object.writeFileSync (node:fs:2322:35)
at LockFile._open (/home/runner/work/tests/node_modules/testcafe/src/utils/temp-directory/lockfile.js:17:16)
at LockFile.init (/home/runner/work/tests/node_modules/testcafe/src/utils/temp-directory/lockfile.js:46:18)
at TempDirectory._findFreeTmpDir (/home/runner/work/tests/node_modules/testcafe/src/utils/temp-directory/index.js:40:26)
at TempDirectory.init (/home/runner/work/src/js/tests/node_modules/testcafe/src/utils/temp-directory/index.js:89:48)
at Function.createDirectory (/home/runner/work/tests/node_modules/testcafe/src/utils/temp-directory/index.js:73:9)
at default_1 (/home/runner/work/tests/node_modules/testcafe/src/browser/provider/built-in/dedicated/chrome/create-temp-profile.ts:7:28)
at ChromeRuntimeInfo.createTempProfile (/home/runner/work/tests/node_modules/testcafe/src/browser/provider/built-in/dedicated/chrome/runtime-info.ts:23:16)
at Function.create (/home/runner/work/tests/node_modules/testcafe/src/browser/provider/built-in/dedicated/chrome/runtime-info.ts:30:42)
at BrowserProviderPluginHost.openBrowser (/home/runner/work/tests/node_modules/testcafe/src/browser/provider/built-in/dedicated/chrome/index.js:75:31)
at BrowserProvider.openBrowser (/home/runner/work/tests/node_modules/testcafe/src/browser/provider/index.ts:327:9)
at BrowserConnection._runBrowser (/home/runner/work/tests/node_modules/testcafe/src/browser/connection/index.ts:282:13)
2024-10-18T11:41:46.426Z testcafe:utils:temp-directory Temp directory path: /tmp/testcafe/chrome-profile-19233oqYvuVtZ4q0
2024-10-18T11:42:07.573Z testcafe:compiler:typescript path: "typescript"
2024-10-18T11:42:07.712Z testcafe:bootstrapper tests compilation took 21 s
2024-10-18T11:42:07.727Z testcafe:browser-tools:open '"/usr/bin/google-chrome-stable" --remote-debugging-port=45855 --user-data-dir=/tmp/testcafe/chrome-profile-1923Vmfd3pmgFwZl --headless=new --disable-search-engine-choice-screen --disable-popup-blocking --disable-infobars --disable-session-crashed-bubble --no-first-run --new-window --disable-background-networking --disable-ipc-flooding-protection --disable-background-timer-throttling --disable-backgrounding-occluded-windows --autoplay-policy=no-user-gesture-required "http://localhost:36845/browser/connect/-QjC8mz" 0<&- >/dev/null 2>&1 &'
2024-10-18T11:42:07.732Z testcafe:browser-tools:open '"/usr/bin/google-chrome-stable" --remote-debugging-port=44471 --user-data-dir=/tmp/testcafe/chrome-profile-19233oqYvuVtZ4q0 --headless=new --disable-search-engine-choice-screen --disable-popup-blocking --disable-infobars --disable-session-crashed-bubble --no-first-run --new-window --disable-background-networking --disable-ipc-flooding-protection --disable-background-timer-throttling --disable-backgrounding-occluded-windows --autoplay-policy=no-user-gesture-required "http://localhost:36845/browser/connect/mCY9Z3X" 0<&- >/dev/null 2>&1 &'
2024-10-18T11:42:08.566Z testcafe:browser:connection:-QjC8mz status changed to 'ready'
2024-10-18T11:42:08.616Z testcafe:browser:connection:mCY9Z3X status changed to 'ready'
2024-10-18T11:42:09.081Z testcafe:browser:provider:built-in:chrome:browser-client:mCY9Z3X CDP method 'PageEnable' took 16 ms
2024-10-18T11:42:09.083Z testcafe:browser:provider:built-in:chrome:browser-client:-QjC8mz CDP method 'PageEnable' took 547 μs
2024-10-18T11:42:09.087Z testcafe:native-automation starting
2024-10-18T11:42:09.089Z testcafe:native-automation starting
2024-10-18T11:42:09.094Z testcafe:native-automation started
2024-10-18T11:42:09.125Z testcafe:browser:provider:built-in:chrome:browser-client:-QjC8mz CDP method 'PageEnable' took 824 μs
2024-10-18T11:42:09.128Z testcafe:browser:provider:built-in:chrome:browser-client:-QjC8mz CDP method 'Emulation.SetDeviceMetricsOverride' took 1.13 ms
2024-10-18T11:42:09.129Z testcafe:browser:provider:built-in:chrome:browser-client:-QjC8mz CDP method 'Emulation.SetVisibleSize' took 297 μs
2024-10-18T11:42:09.129Z testcafe:browser:provider:chrome browser opened -QjC8mz
2024-10-18T11:42:09.130Z testcafe:browser:connection:-QjC8mz status changed to 'opened'
2024-10-18T11:42:09.891Z testcafe:native-automation:request-pipeline:service-request requestPaused 2108.13 interception-job-1.0 request http://localhost:36845/browser/status/-QjC8mz
2024-10-18T11:42:09.895Z testcafe:native-automation:request-pipeline:service-request requestPaused 2108.13 interception-job-1.0 response http://localhost:36845/browser/status/-QjC8mz
2024-10-18T11:42:09.900Z testcafe:native-automation:request-pipeline:service-request requestPaused 2108.14 interception-job-2.0 request http://localhost:36845/browser/init-script/-QjC8mz
2024-10-18T11:42:09.904Z testcafe:native-automation:request-pipeline:service-request requestPaused 2108.14 interception-job-2.0 response http://localhost:36845/browser/init-script/-QjC8mz
2024-10-18T11:42:10.807Z testcafe:native-automation:request-pipeline:service-request requestPaused 2108.15 interception-job-3.0 request http://localhost:36845/browser/heartbeat/-QjC8mz
2024-10-18T11:42:10.811Z testcafe:native-automation:request-pipeline:service-request requestPaused 2108.15 interception-job-3.0 response http://localhost:36845/browser/heartbeat/-QjC8mz
2024-10-18T11:42:10.908Z testcafe:native-automation:request-pipeline:service-request requestPaused 2108.16 interception-job-4.0 request http://localhost:36845/browser/status/-QjC8mz
2024-10-18T11:42:10.913Z testcafe:native-automation:request-pipeline:service-request requestPaused 2108.16 interception-job-4.0 response http://localhost:36845/browser/status/-QjC8mz
2024-10-18T11:42:10.915Z testcafe:native-automation:request-pipeline:service-request requestPaused 2108.17 interception-job-5.0 request http://localhost:36845/browser/init-script/-QjC8mz
2024-10-18T11:42:10.920Z testcafe:native-automation:request-pipeline:service-request requestPaused 2108.17 interception-job-5.0 response http://localhost:36845/browser/init-script/-QjC8mz
2024-10-18T11:42:11.919Z testcafe:native-automation:request-pipeline:service-request requestPaused 2108.18 interception-job-6.0 request http://localhost:36845/browser/status/-QjC8mz
2024-10-18T11:42:11.923Z testcafe:native-automation:request-pipeline:service-request requestPaused 2108.18 interception-job-6.0 response http://localhost:36845/browser/status/-QjC8mz
2024-10-18T11:42:11.927Z testcafe:native-automation:request-pipeline:service-request requestPaused 2108.19 interception-job-7.0 request http://localhost:36845/browser/init-script/-QjC8mz
2024-10-18T11:42:11.930Z testcafe:native-automation:request-pipeline:service-request requestPaused 2108.19 interception-job-7.0 response http://localhost:36845/browser/init-script/-QjC8mz
2024-10-18T11:42:12.809Z testcafe:native-automation:request-pipeline:service-request requestPaused 2108.20 interception-job-8.0 request http://localhost:36845/browser/heartbeat/-QjC8mz
2024-10-18T11:42:12.813Z testcafe:native-automation:request-pipeline:service-request requestPaused 2108.20 interception-job-8.0 response http://localhost:36845/browser/heartbeat/-QjC8mz
2024-10-18T11:42:12.929Z testcafe:native-automation:request-pipeline:service-request requestPaused 2108.21 interception-job-9.0 request http://localhost:36845/browser/status/-QjC8mz
2024-10-18T11:42:12.934Z testcafe:native-automation:request-pipeline:service-request requestPaused 2108.21 interception-job-9.0 response http://localhost:36845/browser/status/-QjC8mz
2024-10-18T11:42:12.936Z testcafe:native-automation:request-pipeline:service-request requestPaused 2108.22 interception-job-10.0 request http://localhost:36845/browser/init-script/-QjC8mz
2024-10-18T11:42:12.940Z testcafe:native-automation:request-pipeline:service-request requestPaused 2108.22 interception-job-10.0 response http://localhost:36845/browser/init-script/-QjC8mz
2024-10-18T11:42:13.937Z testcafe:native-automation:request-pipeline:service-request requestPaused 2108.23 interception-job-11.0 request http://localhost:36845/browser/status/-QjC8mz
2024-10-18T11:42:13.941Z testcafe:native-automation:request-pipeline:service-request requestPaused 2108.23 interception-job-11.0 response http://localhost:36845/browser/status/-QjC8mz
2024-10-18T11:42:13.948Z testcafe:native-automation:request-pipeline:service-request requestPaused 2108.24 interception-job-12.0 request http://localhost:36845/browser/init-script/-QjC8mz
2024-10-18T11:42:13.952Z testcafe:native-automation:request-pipeline:service-request requestPaused 2108.24 interception-job-12.0 response http://localhost:36845/browser/init-script/-QjC8mz
2024-10-18T11:42:14.090Z testcafe:browser:connection:mCY9Z3X Error: Unable to open the "chrome:headless --disable-search-engine-choice-screen" browser due to the following error:
Error: WebSocket connection closed
at /home/runner/work/tests/node_modules/chrome-remote-interface/lib/chrome.js:94:35
at Chrome._handleConnectionClose (/home/runner/work/tests/node_modules/chrome-remote-interface/lib/chrome.js:256:13)
at WebSocket. (/home/runner/work/tests/node_modules/chrome-remote-interface/lib/chrome.js:243:22)
at WebSocket.emit (node:events:517:28)
at WebSocket.emit (node:domain:489:12)
at WebSocket.emitClose (/home/runner/work/tests/node_modules/ws/lib/websocket.js:246:10)
at Socket.socketOnClose (/home/runner/work/tests/node_modules/ws/lib/websocket.js:1148:15)
at Socket.emit (node:events:517:28)
at Socket.emit (node:domain:489:12)
at TCP. (node:net:350:12)
at BrowserConnection._runBrowser (/home/runner/work/tests/node_modules/testcafe/src/browser/connection/index.ts:291:32)
2024-10-18T11:42:14.093Z testcafe:browser:connection:mCY9Z3X status changed to 'closing'
2024-10-18T11:42:14.094Z testcafe:browser:connection:-QjC8mz status changed to 'closing'
2024-10-18T11:42:14.117Z testcafe:native-automation nativeAutomation disposed
2024-10-18T11:42:16.122Z testcafe:browser-tools:exec Error: Command failed: /home/runner/work/tests/node_modules/testcafe-browser-tools/bin/linux/glibc-64/find-window mCY9Z3X
at ChildProcess.exithandler (node:child_process:422:12)
at ChildProcess.emit (node:events:517:28)
at ChildProcess.emit (node:domain:489:12)
at maybeClose (node:internal/child_process:1098:16)
at Socket. (node:internal/child_process:450:11)
at Socket.emit (node:events:517:28)
at Socket.emit (node:domain:489:12)
at Pipe. (node:net:350:12)
at Pipe.callbackTrampoline (node:internal/async_hooks:128:17) {
code: 104,
killed: false,
signal: null,
cmd: '/home/runner/work/tests/node_modules/testcafe-browser-tools/bin/linux/glibc-64/find-window mCY9Z3X'
}
2024-10-18T11:42:16.125Z testcafe:browser:provider UnableToOpenDisplayError: The /home/runner/work/tests/node_modules/testcafe-browser-tools/bin/linux/glibc-64/find-window process cannot open the display.
at runFindWindowBinary (/home/runner/work/tests/node_modules/testcafe-browser-tools/src/api/find-window.js:33:19)
at Object.default_1 (/home/runner/work/tests/node_modules/testcafe-browser-tools/src/api/find-window.js:43:15)
at BrowserProvider._ensureBrowserWindowDescriptor (/home/runner/work/tests/node_modules/testcafe/src/browser/provider/index.ts:186:36)
at BrowserProviderPluginHost.closeLocalBrowser (/home/runner/work/tests/node_modules/testcafe/src/browser/provider/plugin-host.js:59:9)
at BrowserProviderPluginHost.closeBrowser (/home/runner/work/tests/node_modules/testcafe/src/browser/provider/built-in/dedicated/chrome/index.js:121:13)
at BrowserProvider.closeBrowser (/home/runner/work/tests/node_modules/testcafe/src/browser/provider/index.ts:342:13)
at BrowserConnection._closeBrowser (/home/runner/work/tests/node_modules/testcafe/src/browser/connection/index.ts:304:13)
at BrowserConnection.close (/home/runner/work/tests/node_modules/testcafe/src/browser/connection/index.ts:513:9)
2024-10-18T11:42:16.130Z testcafe:reporter begin dispatchToPlugin method: reportWarnings
[
{
message: 'Could not find the "chrome:headless --disable-search-engine-choice-screen" window. TestCafe is unable to resize the window or take screenshots.\n' +
'\n' +
'The following error occurred while TestCafe was searching for the window descriptor:\n' +
'\n' +
'The /home/runner/work/tests/node_modules/testcafe-browser-tools/bin/linux/glibc-64/find-window process cannot open the display.',
testRunId: undefined,
actionId: null
}
]
2024-10-18T11:42:16.130Z testcafe:reporter end dispatchToPlugin method: reportWarnings
2024-10-18T11:42:16.188Z testcafe:browser:provider:chrome browser closed mCY9Z3X
2024-10-18T11:42:16.188Z testcafe:browser:connection:mCY9Z3X status changed to 'closed'
2024-10-18T11:42:16.217Z testcafe:browser:provider:chrome browser closed -QjC8mz
2024-10-18T11:42:16.217Z testcafe:browser:connection:-QjC8mz status changed to 'closed'
What is the Expected behavior?
Should work as well as other successful executions
What is the public URL of the test page? (attach your complete example)
N/A
What is your TestCafe test code?
N/A
Your complete configuration file
module.exports = {
screenshots: {
path: "./artifacts/screenshots",
takeOnFails: false,
pathPattern: "${DATE}${TIME}/${TEST}/${FILE_INDEX}${QUARANTINE_ATTEMPT}.png",
thumbnails: false
},
disableMultipleWindows: true,
browsers: "chrome:headless --disable-search-engine-choice-screen",
concurrency: 2,
skipJsErrors: true,
browserInitTimeout: 120000,
pageLoadTimeout: 60000,
pageRequestTimeout: 65000,
selectorTimeout: 20000,
testExecutionTimeout: 900000,
quarantineMode: false,
disableNativeAutomation: false,
testResults,
}
Your complete test report
No response
Screenshots
No response
Steps to Reproduce
N/A
TestCafe version
3.6.0
Node.js version
Tried with both v18 and v20
Command-line arguments
yarn testcafe
Browser name(s) and version(s)
No response
Platform(s) and version(s)
No response
Other
No response
nothing works at all to me
After updating to chrome 130 all new executions fails with the same error:
The "concurrency" and "quarantineMode" options from the configuration file will be ignored.
ERROR Unable to open the "chrome:headless" browser due to the following error:
Error: WebSocket connection closed
at tests\node_modules\chrome-remote-interface\lib\chrome.js:94:35
at Chrome._handleConnectionClose (tests\node_modules\chrome-remote-interface\lib\chrome.js:256:13)
at WebSocket. (tests\node_modules\chrome-remote-interface\lib\chrome.js:243:22)
at WebSocket.emit (node:events:519:28)
at WebSocket.emit (node:domain:488:12)
at WebSocket.emitClose (tests\node_modules\ws\lib\websocket.js:246:10)
at Receiver.receiverOnFinish (tests\node_modules\ws\lib\websocket.js:1058:20)
at Receiver.emit (node:events:519:28)
at Receiver.emit (node:domain:488:12)
at finish (node:internal/streams/writable:953:10)
@AlekseyKravtsov17,
I've been following issue #8300, and there is a fix for it in the latest release candidate (3.7.0). However, after testing it, I encountered a new issue: I am unable to log in, as I can't interact with the page elements. The elements are detected, but I'm unable to write into or click on them. Could you please take a look?
I see some thumbs up for this issue under the first topic meant for this bug:
#8240
I will link it for the reference - We have the same issue, so I'm using Edge for now as a workaround. But this is very nasty and a complete blockage for us.
Hello @AlekseyKravtsov17,
We have released testcafe 3.7.0-rc.1, which addresses this issue.
Please take a look and let us know your results.
I will close this issue as a duplicate of #8300.
3.7.0-rc.1 does not work for me at all, it jsut failed on github actions timeout. Seems tests are just stuck
3.7.0-rc.1 does not work for me at all, it jsut failed on github actions timeout. Seems tests are just stuck
Same for me
3.7.0-rc.1 does not work for me at all, it jsut failed on github actions timeout. Seems tests are just stuck
Same for me.
3.7.0-rc.1 does not work for me at all, it jsut failed on github actions timeout. Seems tests are just stuck
Same for me
Same for me.
Explanation:
#8307
@Bayheck
I've noticed the spec reporter hangs when it needs to throw an error. It's quite easily reproduced on v3.7.0-rc.1
Hello @AlekseyKravtsov17,
I believe you have encountered this issue: #8300
Please stay tuned - we are already working on it.