Skip to content

fix: fetch provisioner logs after end of logs message #6495

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

Merged
merged 1 commit into from
Mar 8, 2023
Merged

Conversation

kylecarbs
Copy link
Member

I think this should actually fix it. See
https://github.com/coder/coder/actions/runs/4358242625/jobs/7618562167

The problem was that this loop is ran async so even though messages are sent in order, we were processing too slowly and the end of logs was published first.

@kylecarbs kylecarbs requested a review from deansheather March 7, 2023 20:57
@kylecarbs kylecarbs self-assigned this Mar 7, 2023
@kylecarbs kylecarbs enabled auto-merge (squash) March 7, 2023 21:56
I think this should _actually_ fix it. See
https://github.com/coder/coder/actions/runs/4358242625/jobs/7618562167

The problem was that this loop is ran async so even though
messages are sent in order, we were processing too slowly and
the end of logs was published first.
@kylecarbs kylecarbs merged commit 524b14a into main Mar 8, 2023
@kylecarbs kylecarbs deleted the logsafterend branch March 8, 2023 15:13
@github-actions github-actions bot locked and limited conversation to collaborators Mar 8, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants