Restore Logs Manager - Logs Readers functions #2568 #2586
Merged
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.
Fixes #2568
@phillxnet, @Hooverdan96, ready for review
We currently have 2 different logs readers:
cat
, andtail
without the-f
flagtail -f
Both of these use
subprocess.Popen()
to read the log files.In line with most of the other fixes that we have had to make for our move to Python3 (#2567), we need to specify we want it to return a str rather than the new bytes default.
We also were failing in the static reader due to the use of the now deprecated
xrange()
function. Based on my research, Python3'srange()
behaves similarly to Python2'sxrange()
. Switching torange()
here fixes our issue.Functional testing
Under this branch, all static and live readers work in the webUI.
Unit testing