-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Uncaught Error: Mode graphql failed to advance stream. #735
Comments
I was able to resolve this by manually setting query=test as a URL parameter. There is likely a better solution, but at least that is available as a workaround. |
Same problem here. |
This seems to happen when the data in localStorage cannot be restored. Unfortunately clearing localStorage and then reloading does not resolve it because GraphiQL writes to local storage when the page reloads. I solved this in Chrome by:
|
Alternatively, run the following JS snippet and then reload the page:
|
I'm regularly running into the same issue. @darinallen your dummy URL parameter was a quick and easy fix, thank you 👍🚀 |
After running into this issue a few times, I've just figured out a way to reproduce it: In the GraphQL query editor, do Alt Gr + Space (or Option + Space): this will trigger this issue. I hope it will help fix it, that's pretty annoying when you do it without making attention... |
On Mac OS this can be reproduced by pressing Shift + Option + Space |
I ran into this issue on Firefox and neither the "killing the tab" nor the "localStorage.setItem" hacks worked. I finally managed to solve it by clearing localStorage, disabling javascript (through the built-in setting or by via an extension) and reloading the page. |
thanks for reporting this @yboulkaid In the mean time, there is a release of dist files here, if that works for anyone: |
good news! 0.13.2 has been released to npm. 0.13.1 contained this fix, however we decided to just publish 0.13.2 instead. can you confirm that this new version fixes the issue? |
Great news! Personally I'll be waiting until |
Hey @acao, unfortunately I think |
@robinmetral ill take a look tonight |
i did a manual pass/no pass with this bugfix PR before, so i remember seeing the issue before, however I cannot reproduce in master yet. installing the latest gatbsy cli now to give your case a try and see if i cant figure out whats up! |
I can't replicate it with your steps in the issue either, firefox 67, chrome 75 :(( |
Let me take a look tonight @acao (ECT) 🙂 |
@acao I just replicated on Ubuntu, Firefox 67 and Chrome 67. Could this be linked to the OS? It would be interesting to see if this happens for others as well, or just for me 😛 |
possibly? i was able to recreate this original issue on this same OS (OSX) in firefox beforehand. are you sure you are installing the latest version of gatsby CLI with that command? |
@robinmetral can you duplicate the bug here: https://graphiql-test.netlify.com/? |
ok @robinmetral so i've now been able to reproduce the bug it in the gatsby editor, but cannot reproduce it from the master build. can you confirm that |
a further update - the app.js bundle that i find in my node modules from the cli install shows a positive result for this (showing it contains 'graphiql'): conversely, if i add note that this was from a fresh gatsby cli install and creation following your example path in the the original ticket. |
Yes, I've reproduced it there as well 😕 Shortcuts recap🐛 is the bug
(let me know if you experience something else!) |
@robinmetral this is innacurate because i was able to reproduce the bug in OSX but only while using the gatsby dist, see above. |
Thanks @acao for investigating of course! I'll try to make sure the right version is installed at Gatsby, and this will most likely fix it for OSX users. Unfortunately I do still reproduce the issue on Ubuntu/Firefox on the Netlify link, in a provate window with a cleared localStorage. |
@robinmetral I'm now on Ubuntu (KDE), I've tried reproducing the bug on netlify using AltGr+space (where AltGr is the right alt key) and it just outputs a regular space character. I'm on an Apple keyboard using the GB layout, what's the keymap and key combo that's giving you the issue? (And is it still happening?) |
Hey @benjie, yes still getting it here on Ubuntu. I'm also pressing The combination outputs to
But remove
Is the first query string also failing on your end? I'm aware this is an edge case. Thank you for looking into it! |
Yeah; the first URL definitely fails with Potential sources of this issue:
Result of the issue:
Due to disabling GraphiQL from then on (without intervention) I'd say this issue is quite severe. |
Taking a look now. |
This should be fixed in #932 |
Thanks for investigating @benjie! Looking forward to the fix 🙂 |
@benjie @robinmetral thanks for seeing this through, if you find this bug, 0.14.0 is the fix! |
I am trying to use graphiql with a gatsby project and I am experiencing the same issue described in #163. As the author of that issue wrote, I can't type anything into the editor. The editor space is just blank. When looking at the developer tools I see:
Uncaught Error: Mode graphql failed to advance stream.
I've tried clearing the local storage, and that doesn't do anything. I believe this issue originated when I accidentally hit option-space instead of ctrl-space, which I've seen reported as an issue with another plugin:
JetBrains/js-graphql-intellij-plugin#33
The text was updated successfully, but these errors were encountered: