-
Notifications
You must be signed in to change notification settings - Fork 123
TaskHandler state can be reset after error #297
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
Comments
artemredkin
added a commit
to artemredkin/async-http-client
that referenced
this issue
Aug 21, 2020
Motivation: Right now if task handler encounters an error, it changes state to `.endOrError`. We gate on that state to make sure that we do not process errors in the pipeline twice. Unfortunately, that state can be reset when we upload body or receive response parts. Modifications: Adds state validation before state is updated to a new value Adds a test Result: Fixes swift-server#297
Merged
artemredkin
added a commit
to artemredkin/async-http-client
that referenced
this issue
Aug 21, 2020
Motivation: Right now if task handler encounters an error, it changes state to `.endOrError`. We gate on that state to make sure that we do not process errors in the pipeline twice. Unfortunately, that state can be reset when we upload body or receive response parts. Modifications: Adds state validation before state is updated to a new value Adds a test Result: Fixes swift-server#297
artemredkin
added a commit
to artemredkin/async-http-client
that referenced
this issue
Aug 24, 2020
Motivation: Right now if task handler encounters an error, it changes state to `.endOrError`. We gate on that state to make sure that we do not process errors in the pipeline twice. Unfortunately, that state can be reset when we upload body or receive response parts. Modifications: Adds state validation before state is updated to a new value Adds a test Result: Fixes swift-server#297
artemredkin
added a commit
to artemredkin/async-http-client
that referenced
this issue
Aug 24, 2020
Motivation: Right now if task handler encounters an error, it changes state to `.endOrError`. We gate on that state to make sure that we do not process errors in the pipeline twice. Unfortunately, that state can be reset when we upload body or receive response parts. Modifications: Adds state validation before state is updated to a new value Adds a test Result: Fixes swift-server#297
artemredkin
added a commit
that referenced
this issue
Aug 24, 2020
* fail if we get part when state is endOrError * Prevent TaskHandler state change after `.endOrError` Motivation: Right now if task handler encounters an error, it changes state to `.endOrError`. We gate on that state to make sure that we do not process errors in the pipeline twice. Unfortunately, that state can be reset when we upload body or receive response parts. Modifications: Adds state validation before state is updated to a new value Adds a test Result: Fixes #297
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
.endOrError
should be terminal stateThe text was updated successfully, but these errors were encountered: