-
-
Notifications
You must be signed in to change notification settings - Fork 368
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
Log flooded by done: cannot close log stream
entries
#2036
Comments
The second error is a generic error the datastorge (db module) return, when an requested item was not found. So to fix that we need more infobwhat the originated request was |
The first err got added by #1802 and jas just droped in tje past. As it happens frequently, there is eiter an issue with either stream opening or it got closed before. in any case we should dig into it. Affected part: pubsub mod for live log streaming over eventstream |
Ah then its a easy fix ... will do so once i have a keboard on hand again |
I think we do have something like that: woodpecker/server/api/pipeline.go Line 148 in 1da0ad3
|
-> #2042 |
also the generic error will get less generic -> #2041 |
ok the first error is created here: Lines 295 to 297 in 3033abc
but the question is why! |
moved to bugfix version as it's non blocking :) |
this also happens to me and the last few characters or things in the log for a pipeline disappear even though it shows itself as successful/errored |
Previously, *all* log streams of the pipeline were closed everytime when a workflow is done, if you have multiple workflows, streams will be closed multiple times. Closes #2036
Previously, *all* log streams of the pipeline were closed everytime when a workflow is done, if you have multiple workflows, streams will be closed multiple times. Closes woodpecker-ci#2036
Component
server
Describe the bug
After a short period of time, I have already many of these entries in the log:
This one also occurs pretty often:
System Info
Additional context
No response
Validations
next
version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]The text was updated successfully, but these errors were encountered: