Allow server to print debug messages #478
Merged
Conversation
This file contains 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
vinistock
force-pushed
the
vs-allow-server-to-print-debug-messages
branch
from
3cbb146
to
836da15
Compare
vinistock
force-pushed
the
vs-allow-server-to-print-debug-messages
branch
from
836da15
to
32420d1
Compare
KaanOzkan
approved these changes
Oct 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I can be difficult to debug what's happening in the server or in a server add-on. I propose we make the stderr pipe as the means for the runtime server to send debug messages.
By dedicating a pipe exclusively for this, there's fewer risks of messing up with actual request/response cycles and we can easily print it asynchronously by adding a thread worker.