Skip to content
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

Invalid documents errors are swallowed and not reported #7323

Closed
dotansimha opened this issue Jan 5, 2022 · 6 comments
Closed

Invalid documents errors are swallowed and not reported #7323

dotansimha opened this issue Jan 5, 2022 · 6 comments
Labels
stage/0-issue-prerequisites Needs more information before we can start working on it

Comments

@dotansimha
Copy link
Owner

Context: https://twitter.com/agarithm/status/1478725479678898177

Seems like invalid syntax queries are not being reported.

query {
   ...
}

image

image

image

@n1ru4l
Copy link
Collaborator

n1ru4l commented Jan 31, 2022

As a reference for those who want to see the errors currently:

DEBUG=1 VERBOSE=1

@n1ru4l
Copy link
Collaborator

n1ru4l commented Jan 31, 2022

Expected behaviors:

On CI: Error
Locally Single run: Error
Locally Watch mode: warning

@charlypoly charlypoly added stage/0-issue-prerequisites Needs more information before we can start working on it and removed bug/0-needs-repro labels Mar 14, 2022
@Slessi
Copy link

Slessi commented Oct 25, 2022

I used to be satisfied with the DEBUG=1 workaround, but since a recent update, the CLI prints a lot of information with DEBUG=1 which masks errors for me regardless.

Would be nice to get error output for syntax errors without needing to specify DEBUG=1

@charlypoly
Copy link
Contributor

charlypoly commented Oct 25, 2022

Merged with #8366

@charlypoly charlypoly closed this as not planned Won't fix, can't repro, duplicate, stale Oct 25, 2022
@Slessi
Copy link

Slessi commented Oct 25, 2022

@charlypoly I dont think thats the same issue.

The linked issue is about truncated error messages, but this issue is about syntax errors not being printed at all, unless you specify DEBUG=1.

@charlypoly
Copy link
Contributor

I've merged it with the other issue bc they share the same root cause, cf: #8366 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stage/0-issue-prerequisites Needs more information before we can start working on it
Projects
None yet
Development

No branches or pull requests

4 participants