- Notifications
You must be signed in to change notification settings - Fork1.2k
Conversation
e2bab84 toea9f5b9Comparedeansheather approved these changesJun 5, 2025
bb2c195 intomain 56 checks passed
Uh oh!
There was an error while loading.Please reload this page.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Labels
None yet
2 participants
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.
Uh oh!
There was an error while loading.Please reload this page.
Related to#15109.
This PR will bring in new flakes that stem from cancelling postgres initialization in the CLI, like this one:https://github.com/coder/coder/actions/runs/15401304931/job/43488409311?pr=18195#step:13:312. They were previously unseen because we didn't run CLI tests with postgres. I decided not to fix them in this PR - I'd rather we created follow up issues as these flakes manifest on main.