Edits to TRACE_FETCH debug messages #4645
Open
+17
−15
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
jjimenezshaw
approved these changes
Dec 30, 2025
Contributor
jjimenezshaw
left a comment
jjimenezshaw
left a comment
There was a problem hiding this comment.
I'm happy those traces were useful to somebody else.
willcohen
force-pushed
the
fetch-typo
branch
from
fd417e8 to
45bda9e
Compare
Contributor
Author
|
Force pushed to address linter from CI. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Small tweak to #4627, just updating formatting of the debug messages (noticed while using it to work on incorporating fetch into proj-wasm).