Skip to content

Fix the CodeGenerationFailed notification code #166

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.

Sign up for GitHub

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 2 commits into from
Aug 13, 2024
Merged

Fix the CodeGenerationFailed notification code #166

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b183507
Fix the `CodeGenerationFailed` notification code
NataliaIvakina Aug 12, 2024
799580e
Update modules/ROOT/pages/notifications/all-notifications.adoc
NataliaIvakina Aug 13, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions modules/ROOT/pages/notifications/all-notifications.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -616,7 +616,7 @@ MATCH ()-[r: KNOWS]->() WHERE r.since IS NOT NULL RETURN r
=====

[#_neo_clientnotification_statement_codegenerationfailed]
=== Unsupported runtime - CodeGenerationFailed
=== Failed code generation

The `CodeGenerationFailed` notification is created when it is not possible to generate a code for a query, for example, when the query is too big.
For more information about the specific query, see the stack trace in the _debug.log_ file.
Expand All @@ -633,10 +633,10 @@ a|The database was unable to generate code for the query. A stacktrace can be fo
|Category
m|PERFORMANCE
|GQLSTATUS code
m|01N40
m|03N96
|Status description
a|warn: unsupported runtime.
The query cannot be executed with `preparser_input1`, `preparser_input2` is used. Cause: `$msg`.
a|info: failed code generation.
Failed to generate code, falling back to interpreted $enginetype engine. A stacktrace can be found in the debug.log. Cause: $msg.
|Classification
m|PERFORMANCE
|SeverityLevel
Expand Down