You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use captainhook/captainhook-phar, which uses phar-io/composer-distributor. We wondered why sometimes, in CI, we get a GitHub timeout even though we use Private Packagist as a mirror. What we've seen:
- Installing captainhook/captainhook-phar (5.22.2): Extracting archive
WARNING
No GPG installation found! Use installed PHARs with care.
Consider installing GnuPG to verify PHAR authenticity.
If you need help installing GnuPG visit http://phar.io/install-gnupg
- Downloading artifact from https://github.com/captainhookphp/captainhook/releases/download/5.22.2/captainhook.phar
In Download.php line 26:
fopen(https://github.com/captainhookphp/captainhook/releases/download/5.22.
2/captainhook.phar): Failed to open stream: Connection timed out
However, our composer.lock file clearly defines a mirror for this package:
We use
captainhook/captainhook-phar
, which usesphar-io/composer-distributor
. We wondered why sometimes, in CI, we get a GitHub timeout even though we use Private Packagist as a mirror. What we've seen:However, our
composer.lock
file clearly defines a mirror for this package:Since the mirror is defined, the package should be downloaded from repo.packagist.com and not from github.com.
Would you be able to support this? 🫣 🙏
The text was updated successfully, but these errors were encountered: