You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not completely sure what you mean with "whole TypeScript code". The project itself would be a lot, and it's under NDA.
Here is the relevant React useEffect hook.
fullScreen can be null/undefined while this React component initializes, and this useEffect waits for it to change to either true or false.
We have changed the code so that the console.log only runs whenever fullScreen is defined, and this panic does not occur anymore. This seems to prove that a console.log('something', null) (or undefined) leads to a panic in the go code.
@nuarhu this issue looks very similar to #793 and #777. We've marked those as resolved since #859 fixed the issue. Once we release v0.45.0 of k6 you should be able to test it against your website and see whether that fix also works for your case.
Brief summary
Logging a dynamic variable with console.log that can be null (or undefined) results in a go panic.
xk6-browser version
k6 v0.42.0
OS
macOS Ventura 13.1 (go1.19.4, darwin/arm64)
Chrome version
109.0.5414.119
Docker version and image (if applicable)
No response
Steps to reproduce the problem
The relevant code in TypeScript seems to be for example:
Expected behaviour
Just don't panic when there is null.
Actual behaviour
Panic (see stack trace above)
The text was updated successfully, but these errors were encountered: