Skip to content

testkit: Fix Unknown request error path (#845) #866

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

Merged
merged 1 commit into from
Feb 4, 2022

Conversation

bigmontz
Copy link
Contributor

@bigmontz bigmontz commented Feb 4, 2022

There was two different errors during the unknown request error treatment.

First, the stringify function was not define in the LocalController scope. It get solve by extract this function to it own file and import it in the local.js.

Second, the backend was capturing the error in the request event and calling writeBackendError with the error object instead of the message.

There was two different errors during the unknown request error treatment.

First, the stringify function was not define in the LocalController scope. It get solve by extract this function to it own file and import it in the local.js.

Second, the backend was capturing the error in the `request` event and calling `writeBackendError` with the error object instead of the message.
@bigmontz bigmontz merged commit 8d79dbf into neo4j:4.4 Feb 4, 2022
@bigmontz bigmontz deleted the 4.4-fix-stringify-call branch February 4, 2022 17:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant