sorbet: Could not find sorbet-static-0.4.5079-universal-darwin-14 in any of the sources
Input
On Linux (running on Ubuntu 18.04 in Github Actions):
bundle install --jobs $(nproc) --retry 3 --without metrics --path vendor/bundle
Observed output
Fetching gem metadata from https://rubygems.pkg.github.com/tricycle/...
Fetching gem metadata from https://rubygems.org/...........
Fetching gem metadata from https://rubygems.pkg.github.com/tricycle/..
Fetching gem metadata from https://rubygems.org/.
Resolving dependencies...
Could not find sorbet-static-0.4.5079-universal-darwin-14 in any of the sources
Expected behavior
Our builds are failing for every one of our private gems, for the same reason. It appears as though the Linux version of this build has not been pushed to Rubygems.
Because these are gems, we are following best practice and not including a Gemfile.lock in each project, so locking down the version is impractical.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 5
- Comments: 37 (7 by maintainers)
Everything was working for me fine, until I recently updated sorbet, and CI started failing with this issue. I update all gems every week or so, so my guess is something sorbet has done in shipping gems change recently.
I was on bundler 2.1.4 for a long time, and it just started to fail. @Zelnox thanks, upgrading from 2.1.4 to 2.2.3 appears to have fixed it for me too. It added a bunch of new Darwin builds, then also a linux one, which is what CI needed.
We encountered a similar issue this week on CI (linux). I managed to resolve it by updating locally (OSX) bundler from 2.1.4 to 2.2.3 and updating both sorbet and sorbet-runtime. This finally included in the gem lock file both the darwin and linux dependencies for sorbet-static.
Bundler 2.1.4 was including only the Darwin version of the gem in the lock file.
Using the previous version works:
gem 'sorbet', '0.4.5072'It looks like sorbet-static gem for linux platforms is not uploaded at rubygems for version 0.4.5079.
Hi guys, I have the issue when putting it the gem in the gemfile,
It look something like that and then fail:
@xcskier56 Unfortunately not. In the end I removed Sorbet from the project because I couldn’t get it to work. Hoping to use it again when/if this issue is fixed.
There’s an issue with yesterday’s changes, linux and darwin-19 versions are missing.
that is indeed the job that builds it, and it’s run both by linux and mac. If both succeed, nightly will run the following
https://github.com/sorbet/sorbet/blob/master/.buildkite/publish-ruby-gems.sh
and is supposed to upload both
I’m seeing this failure on Debian Buster running Ruby 2.6.3: