-
Notifications
You must be signed in to change notification settings - Fork 592
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pod's logs following continually switching off #13235
Comments
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
/remove-lifecycle rotten |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Hello Openshift console team! I've created a bug in follow feature for LogViewer component in Patternfly React but they suggested that the issue may be within the product. I'll copy+paste my report from patternfly/react-log-viewer#48.
Describe the problem
Hello, I am not a UI developer but I am encountering an issue with the LogViewer component in Openshift UI (logs of a pod), where the follow feature of LogViewer component is turning off after new lines of logs appear. Repeated resuming of following the log will resume the follow until a new lines appear when it turns off again.
Expected behavior
Turning on the feature of following logs should be kept on after new lines, otherwise the feature does not serve its purpose.
Is this issue blocking you?
It is not blocking me. The feature is very useful and manually scrolling down to follow logs is a big inconvenience.
Screenshots
What is your environment?
What is your product and what release date are you targeting?
The product is Openshift UI.
Any other information?
I'd like to emphasize that the feature works correctly on Google Chrome.
The text was updated successfully, but these errors were encountered: