Current behavior
We've had reports that this error is displaying for some users. This error should never be shown in Cypress. There's also not currently a great way to track down why this was thrown (what was the stacktrace or shape of error that made this occur).
Desired behavior
We should better handle when the stack is undefined. Do not throw an error here and don't display the stack trace. This would unblock people who see this error.
Test code to reproduce
This happens intermittently in CI on a large project, so there hasn't been a provided example. Although I don't think this is necessary in order to create a fallback solution and to test it.
Cypress Version
7.5.0
Other
No response
Current behavior
We've had reports that this error is displaying for some users. This error should never be shown in Cypress. There's also not currently a great way to track down why this was thrown (what was the stacktrace or shape of error that made this occur).
Desired behavior
We should better handle when the stack is undefined. Do not throw an error here and don't display the stack trace. This would unblock people who see this error.
Test code to reproduce
This happens intermittently in CI on a large project, so there hasn't been a provided example. Although I don't think this is necessary in order to create a fallback solution and to test it.
Cypress Version
7.5.0
Other
No response