fix: remove error log when notification manager is already closed #18264
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes coder/internal#677
Resolves flakes such as:
These error logs are caused as a result of the
Manager
Run
start operation being asynchronous. In the flaking test case we immediately callStop
afterRun
. It's possible forStop
to be scheduled to completion before the goroutine spawned byRun
callsloop
and checksclosed
. If this happens,loop
returns an error and produces the error log.We'll address this by replacing this specific error log with a warning log.