Skip to content

fix(logs): pick up the logparser fix for split lines that never end - #408

Merged
mayankpande88 merged 1 commit into
mainfrom
fix/logparser-split-line-pin
Oct 24, 2026
Merged

mayankpande88 merged 1 commit into
mainfrom
fix/logparser-split-line-pin

Conversation

@reckless-sherixx

Copy link
Copy Markdown
Contributor

Pins logparser to 38071d9 (nudgebee/logparser#37).

Since #407, a file's saved position advances only past delivered lines. A container that writes the first part of a split line and never ends it held back acknowledgements for every later line in that file, so its position stopped advancing. logparser#37 passes such a line on once its first part is ten collector timeouts old.

Verify: go list -m github.com/nudgebee/logparser prints v0.0.0-20261023171829-38071d9d9983. logparser's TestEndlessSplitLineDoesNotBlockAcknowledgements covers the behaviour.

Tested: go vet ./..., go test on every package CI runs, go test -race ./logs/ ×3, go build -mod=readonly.

Pins logparser 38071d9 (nudgebee/logparser#37). A container that writes
a line split across log records and never ends it no longer holds back
acknowledgements, so positions for its file keep advancing.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the dependency github.com/nudgebee/logparser to a newer version in go.mod and go.sum. I have no feedback to provide.

@mayankpande88
mayankpande88 merged commit 017225a into main Oct 24, 2026
7 checks passed
@mayankpande88
mayankpande88 deleted the fix/logparser-split-line-pin branch October 24, 2026 16:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants