Sorry for the late response. You are encountering a bug that happened in URBANopt, which is essentially the same as what happened here:
The same solution there will work for your case and your issue will be fixed if you run the LB Versioner. This will give you the latest version of the URBANopt GemFile, which has a correct version of the adressable gem that is failing there. FYI, if you’re ever curios, here is where you can always find the latest Gemfile that we use:
You can see that both the addressable and the parser gems have given us a bit of a headache recently.
Also, that’s a really clever solution, @Rowena. I’ll keep this in mind and point people to this discussion if they are looking for a way to get around the download of all the ruby gems for each project folder.