refactor(backend_log): improve getBackendLog
#926
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
pano9000
changed the title
getBackendLog
using synchronous functions on the backend is not recommended, as it is "blocking the event loop", i.e. no other tasks get executed/processed, while the file is being read
handle errors more "user friendly" and actually let the user know, that either the file is not existing (yet), or that reading the log failed.
pano9000
force-pushed
the
refactor_backend_log
branch
from
2aa249a to
949c4ac
Compare
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.
Hi
this PR aims to improve the
getBackendLogfunction in thebackend_logroute:most notable: