-
-
Notifications
You must be signed in to change notification settings - Fork 455
Add a MemoryStream buffer to ReadStream first #603
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
Conversation
|
@taooceros could you let me know what's tested please |
I have tested the scenario descripted in #598 (a very large json output). It works fine with very large json (1500000 items). The change is really simple. I just add a memorystream layer to read the console output from the process allowing it to exit, which causes the hang (not a lot refactor as I say in #598 due to consideration of possible future change). Probably a regular memorystream will be fine because we generally won't need to deal with that much item, but I just found the recycle one |
|
Testing in a moment, thank you so much for looking into this! |
|
@taooceros Works perfectly! All values are being returned and Flow Launcher no longer gets stuck in a loading state. |
Perfect! Thank you so much for reporting the bug! |
|
Not sure whats causing this error but it might be releated: Flow Launcher seems to work regardless |
|
This exception shouldn't be logged. Weird. Will take a look later. |
|
@taooceros let me know when this is ready, assuming you are still looking into the log above. |
|
@jjw24 Good to review. I add another manual |
|
Hold on, I found an issue, let me fix it. |
|
Done |
fix #598