Opened 4 weeks ago
#62807 new enhancement
Protect `env:start` command against connection issues
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Future Release | Priority: | normal |
Severity: | normal | Version: | |
Component: | Build/Test Tools | Keywords: | needs-patch |
Focuses: | Cc: |
Description
[59231] moved the composer update
command from the test:php
script to env:start
to prevent the command from running every time unit tests are run.
ticket:57189#comment:22 from @flixos90 mentions a situation where packagist.org was experiencing some down time and caused the env:start
command to fail. The reason for this can be hard to decipher and it's easy to assume that you are experiencing a Docker issue.
Ideally the composer update
command catches errors and displays a more informative notice to the user. "There was a failure running composer update
." with some guidance to fix the issue.
See #57189.
Note: See
TracTickets for help on using
tickets.