Fix JSON errors after inline exports - #442
Merged
Merged
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes the client response before inline background processing starts, preventing successful long-running exports from surfacing gateway responses as invalid JSON in the Command Center. Releases PHP session locks and finalizes FastCGI or LiteSpeed requests once, while preserving existing behavior on unsupported hosts. Clears retained page errors when a new fetch attempt begins so successful retries do not show stale temporary-file failures. Adds regression coverage for inline continuations and retried redirect fetches; the full PHPUnit suite passes with 357 tests and 4,541 assertions.