-
Notifications
You must be signed in to change notification settings - Fork 268
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: memory access out of bounds in unit test #1112
Labels
Comments
bgrgicak
added
[Type] Bug
An existing feature does not function as intended
Tests
labels
Mar 18, 2024
This was referenced Mar 18, 2024
This test started failing after #1104 was merged. |
Log message returned by the failing unit test
|
|
adamziel
pushed a commit
that referenced
this issue
Mar 19, 2024
Fixes #1112 It fixes a bug in post_message_to_js that broke sending messages in Node. ## What problem is it solving? It checks if the response length of a message is larger than -1 before attempting to process the message. ## How is the problem addressed? By checking the response length. ## Testing Instructions - Confirm that all tests pass
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A few unrelated branches (#1083 and #1095) started failing the onMessage > should return null when JS message handler throws an error unit test.
Example error https://github.com/WordPress/wordpress-playground/actions/runs/8324683975/job/22776886035
This error also exists on
trunk
if you run tests locally, but for some reason,trunk
unit tests are passing.The text was updated successfully, but these errors were encountered: