[wp-trac] [WordPress Trac] #62807: Protect `env:start` command against connection issues

[WordPress Trac]

#62807: Protect `env:start` command against connection issues
------------------------------+----------------------------
 Reporter:  desrosj           |      Owner:  (none)
     Type:  enhancement       |     Status:  new
 Priority:  normal            |  Milestone:  Future Release
Component:  Build/Test Tools  |    Version:
 Severity:  normal            |   Keywords:  needs-patch
  Focuses:                    |
------------------------------+----------------------------
 [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.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/62807>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform