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.

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

Jump to bottom

Bug: stream error: stream ID x; INTERNAL_ERROR is not handled #21

Closed
BenB196 opened this issue Sep 23, 2019 · 1 comment
Closed

Bug: stream error: stream ID x; INTERNAL_ERROR is not handled #21

BenB196 opened this issue Sep 23, 2019 · 1 comment

Comments

@BenB196
Copy link
Owner

BenB196 commented Sep 23, 2019 •
edited
Loading

The following error can be thrown, but should be handled:

error getting file events for ffs query: main_query
panic: stream error: stream ID 2223; INTERNAL_ERROR

goroutine 32318 [running]:
github.com/BenB196/crashplan-ffs-puller/ffsEvent.queryFetcher(0xc000116c90, 0xa, 0xc0000fc580, 0x17, 0xc000116ca0, 0xf, 0xc000116c9a, 0x2, 0xc000116c9c, 0x3, ...)
        /app/ffsEvent/ffsEvent.go:233 +0x1d6a
created by github.com/BenB196/crashplan-ffs-puller/ffsEvent.FFSQuery.func5
        /app/ffsEvent/ffsEvent.go:180 +0x206
@BenB196 BenB196 changed the title Bug: Bug: stream error: stream ID x; INTERNAL_ERROR is not handled Sep 23, 2019
BenB196 added a commit that referenced this issue Oct 1, 2019
@BenB196
Added the ability to retry queries for known issues with the FFS API.
987ccc3 
A limit of 10 retries for a query is set to prevent a runaway of resource utilization/infinite in progress queries.

Resolves issue #21
Resolves issue #30

Corrected issue with logstash output location not being properly handled.

Resolves #31
@BenB196
Copy link
Owner Author

BenB196 commented Oct 1, 2019

Fixed in release v0.1.1.

@BenB196 BenB196 closed this as completed Oct 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@BenB196