Repository navigation
fix(gfql): distinguish Call execution errors - #2199
Merged
Merged
Conversation
lmeyerov
force-pushed
the
fix/gfql-call-runtime-errors
branch
2 times, most recently
from
October 14, 2026 12:14
2535fe7 to
82e8538
Compare
lmeyerov
force-pushed
the
fix/gfql-call-runtime-errors
branch
from
October 14, 2026 12:34
82e8538 to
df9d7bf
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
GFQLCallExecutionError/E306(call-execution-error).__cause__.E303/E105parameter and reference validation errors and existingNotImplementedErrorengine-capability behavior.Exact head:
df9d7bf06Base:
master@0c71cc4bb8281ecc1f07de8657c4ec45c737a5c1Evidence
Closes #2196.