[JENKINS-44972] Truncated log displayed in middle of line, showing Base64-encoded ConsoleNote garbage
Author: jenkins-infra-botCreated Jun 19, 2017Updated Sep 16, 2026
Labelsgood first issueimported-jira-issuecomponent:corepriority:minorresolution:unresolved
When you view a truncated log file (Skipping ... Full Log) often the text will resume in the middle of a line. This is ugly enough but when the offset happens to be in the middle of an encoded ConsoleNote you get a confusing batch of Base64 garbage before the stream corrects itself.
Either console.jelly should employ a more sophisticated core API to find an offset which is at a line boundary (which might be inefficient); or AnnotatedLargeText.writeHtmlTo should skip any initial partial line, for example by using start - 1 and using a wrapper OutputStream which discards everything prior to the first newline character and thereafter mirrors its input; or ConsoleAnnotationOutputStream should have an option to do that.
--- Originally reported by- assignee: shreygupta198
- status: Open
- priority: Minor
- component(s): core
- label(s): newbie-friendly
- resolution: Unresolved
- votes: 2
- watchers: 4
- imported: 2025-11-24
When you view a truncated log file (Skipping ... Full Log) often the text will resume in the middle of a line. This is ugly enough but when the offset happens to be in the middle of an encoded ConsoleNote you get a confusing batch of Base64 garbage before the stream corrects itself.
Either console.jelly should employ a more sophisticated core API to find an offset which is at a line boundary (which might be inefficient); or AnnotatedLargeText.writeHtmlTo should skip any initial partial line, for example by using start - 1 and using a wrapper OutputStream which discards everything prior to the first newline character and thereafter mirrors its input; or ConsoleAnnotationOutputStream should have an option to do that.Source: jenkinsci/jenkins