This repository was archived by the owner on Nov 20, 2025. It is now read-only.
Bugfix: failed exception treated as successful should not trigger exception in pool#12
Open
gdebrauwer wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Linked to saloonphp/saloon#314 (test will succeed when code of that PR is merged)
If a failed response should not be treated as failure because the
hasRequestFailedreturns false, then the Laravel Http Sender currently throws aCan only throw objectsPHP error. That is caused by the fact that thetoException()method on the response returns null and you can not throw null.