Sorbet: Could not find sorbet-static-0.4.5079-universal-darwin-14 in any of the sources

[michaelwebb76]

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.

[arielj]

Same issue here. Just added sorbet and sorbet-runtime and when I run bundle install I get the exact same message Could not find sorbet-static-0.4.5079-universal-darwin-14 in any of the sources.

Inside my gemfile:
source 'http://rubygems.org'

(tried with https too, same error)

But that version can be found at rubygems https://rubygems.org/gems/sorbet-static/versions/0.4.5079-universal-darwin-14

My system:

• Linux Mint 19 64-bits
• Kernel: 4.15.0-70-generic
• Ruby 2.5.7 (using rvm)

[arielj]

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.

[benreyn]

Any update on when the 0.4.5079 for linux platforms will get uploaded?

[arielj]

Version 0.4.5083 has linux build:
https://rubygems.org/gems/sorbet-static/versions/0.4.5083-x86_64-linux

Version 0.4.5085 doesn't
https://rubygems.org/gems/sorbet-static/versions

[benreyn]

Curious why some versions are getting a linux build and some are not. 🤔

[arielj]

If I understand right, this script builds different versions and uploads them to rubygems https://github.com/sorbet/sorbet/blob/9e697d4d9882c1e3fad92073b68762f12abdfedc/.buildkite/build-static-release.sh. I'm guessing it has to be run on both mac and linux platforms and maybe sometimes it's only run on mac, I'm not sure what's the release process.

[michaelwebb76]

Why oh why oh why

[connorshea]

This is causing sorbet-rails' test suite to fail :(

[leighmcculloch]

I'm seeing this failure on Debian Buster running Ruby 2.6.3:

$ gem install sorbet
ERROR:  Could not find a valid gem 'sorbet-static' (= 0.4.5099) (required by 'sorbet' (>= 0)) in any repository
ERROR:  Possible alternatives: sorbet-static

[dmitry-stripe]

If I understand right, this script builds different versions and uploads them to rubygems https://github.com/sorbet/sorbet/blob/9e697d4d9882c1e3fad92073b68762f12abdfedc/.buildkite/build-static-release.sh. I'm guessing it has to be run on both mac and linux platforms and maybe sometimes it's only run on mac, I'm not sure what's the release process.

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

[dmitry-stripe]

https://buildkite.com/sorbet/sorbet/builds/7871 are logs for run that should have uploaded the 0.4.5099 for linux but didn't.

[dmitry-stripe]

We seem to have a bug in uploader job: it has downloaded an artifact from buildkite build(see https://buildkite.com/sorbet/sorbet/builds/7871#0dc74d76-13e4-40e3-896f-d2b0485be407/91-106)
but did not upload it to rubygems

[dmitry-stripe]

ok, so I think https://github.com/sorbet/sorbet/blame/master/.buildkite/publish-ruby-gems.sh#L55 is a buggy if: it might decide to not upload a platform if another plaform has been uploaded.
Given it's 1am where I am I'll not attempt to write a better one now.
Feel free to make a PR to fix it, would be super happy to review

[arielj]

Is that if even necessary? I mean, the script removes everything from the _out_ dir, then downloads the artifacts, and then only loops through the files with $release_version on the name. Maybe this should be checked outside the loop once and not for each file (just in case this release was already pushed), what do you think? If so, I could send a PR like:

if ! gem list --remote rubygems.org --exact 'sorbet-static' | grep -q "$release_version"; then
  for gem_archive in .....; do
    with_backoff gem push --verbose "$gem_archive"
  done
fi

Any thoughts?

[DarkDimius]

Should be fixed now^^^

[DarkDimius]

Thank you for your reporting and helping pinpoint the bug!

[leighmcculloch]

@DarkDimius Thanks! I just attempted running gem install sorbet on Debian Buster and I'm seeing the same result as here https://github.com/sorbet/sorbet/issues/2250#issuecomment-561529023.

[DarkDimius]

I'm seeing the same result

the cron job will kickoff in 2 minutes and should fix it(our nightly publish runs at 22:15 SF time)

[DarkDimius]

https://buildkite.com/sorbet/sorbet/builds/7914 is the build, you can monitor it with me :-)

[DarkDimius]

0.4.5109 - December 05, 2019 universal-darwin-19 (4.49 MB)
0.4.5109 - December 05, 2019 universal-darwin-14 (4.49 MB)
0.4.5109 - December 05, 2019 universal-darwin-15 (4.49 MB)
0.4.5109 - December 05, 2019 universal-darwin-18 (4.49 MB)
0.4.5109 - December 05, 2019 x86_64-linux (4.27 MB)
0.4.5109 - December 05, 2019 universal-darwin-17 (4.49 MB)
0.4.5109 - December 05, 2019 universal-darwin-16 (4.49 MB) 

could you check again?

[leighmcculloch]

It works! 👏 🎉 🌮

$ gem install sorbet
Fetching sorbet-static-0.4.5109-x86_64-linux.gem
Fetching sorbet-0.4.5109.gem
Successfully installed sorbet-static-0.4.5109-x86_64-linux

Thanks @DarkDimius !

[michaelwebb76]

Bloody legend @DarkDimius !! Thanks so much.

[arielj]

Great! I'll keep an eye for a few days since some times it was working without the fix (it could be a false positive) but I believe it's actually fixed.

[arielj]

I'm not sure if this broke something but it's build failed for mac, it looks like it's trying to upload all variants with one command

@DarkDimius

https://buildkite.com/sorbet/sorbet/builds/7970#54d3f6d0-8c3d-40f3-9bca-67fb77d24344/121-137

[arielj]

This commit is the problem https://github.com/sorbet/sorbet/commit/b255b4f7eaef7b8ee6975394124d4c80b8b850ec#diff-4eecb4b53b7482e8b253fc25c7c4a573

[marisveide]

I have the same error when running on ruby 2.6.5 (using rvm on MacOS Catalina).

maris@Maris-Mac ruby-types % bundle add sorbet    
Fetching gem metadata from https://rubygems.org/............
Fetching gem metadata from https://rubygems.org/.
Resolving dependencies...
Could not find sorbet-static-0.4.5158-universal-darwin-14 in any of the sources

[arielj]

There's an issue with yesterday's changes, linux and darwin-19 versions are missing.

[marisveide]

There's an issue with yesterday's changes, linux and darwin-19 versions are missing.

Thanks - please, ping somewhere when it's fixed... 🙇

[arielj]

@marisveide you can workaround that error specifying a version for sorbet-static on your gemfile until the publishing gets fixed. I suppose your problem is that the darwin-19 version is not published, so you can use an "old" version (from yesterday's morning) https://rubygems.org/gems/sorbet-static/versions, something like:

gem 'sorbet-static', '0.4.5144'

[chrismv48]

Hi, I'm running into this issue after attempting to bundle install a project onto my Raspberry Pi (Raspbian GNU/Linux 10 (buster)). It works fine locally on my mac.

I've tried some of the suggested workarounds such as specifying an older version for sorbet or sorbet-static in my Gemfile, but nothing works.

Error:

Could not find sorbet-static-0.5.6101-universal-darwin-14 in any of the sources

[xcskier56]

@chrismv48, have you solved this? I'm having an error that started with 0.5.6100 and after updating to the newest, it's still happening. I'm having the issue with CircleCI linux

[chrismv48]

@chrismv48, have you solved this? I'm having an error that started with 0.5.6100 and after updating to the newest, it's still happening. I'm having the issue with CircleCI linux

@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.

[toddsundsted]

@xcskier56 @chrismv48 i removed the lockfile from the project (and left Sorbet in place). the specific problem i had was the sorbet artifact (sorbet-static/0.5.6189-universal-darwin-14) that did not match the build platform (linux).

[Zelnox]

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.

[will]

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.

       sorbet-static (= 0.5.6189)
     sorbet-runtime (0.5.6189)
     sorbet-static (0.5.6189-universal-darwin-14)
+    sorbet-static (0.5.6189-universal-darwin-15)
+    sorbet-static (0.5.6189-universal-darwin-16)
+    sorbet-static (0.5.6189-universal-darwin-17)
+    sorbet-static (0.5.6189-universal-darwin-18)
+    sorbet-static (0.5.6189-universal-darwin-19)
+    sorbet-static (0.5.6189-universal-darwin-20)
+    sorbet-static (0.5.6189-x86_64-linux)
     spoom (1.0.7)
       colorize
       sorbet (~> 0.5.5)
@@ -260,4 +267,4 @@ RUBY VERSION
    ruby 2.6.6p146

 BUNDLED WITH
-   2.1.4
+   2.2.3