Reporting here because in the past this has been the only way to indirectly report an issue to the GAE ruby standard environment team in lieu of appropriate tags on stackoverflow.
It looks like the ruby GAE standard team changed something in their runtime 1-2 days ago that has broken any new deploys that use nokogiri (which is 90% of ruby apps).
Deploys that were previously working two days ago will now fail when rails tries to run with:
Bundler::GemNotFound: Could not find nokogiri-1.10.7 in any of the sources
It is impossible to re-produce this error locally for affected projects, and re-installing gems, updating gems, changing ruby versions, etc., seems to have no effect.
I think previously the runtime was including some pre-compiled nokogiri versions, and with this latest change they dropped some of the versions they were previously including, or something. Just a guess.
Would really appreciate it @dazuma if you guys pass this along to the ruby standard environment team.
English stackoverflow issue: here
Japanese stackoverflow issue posted by someone else: here
Reporting here because in the past this has been the only way to indirectly report an issue to the GAE ruby standard environment team in lieu of appropriate tags on stackoverflow.
It looks like the ruby GAE standard team changed something in their runtime 1-2 days ago that has broken any new deploys that use nokogiri (which is 90% of ruby apps).
Deploys that were previously working two days ago will now fail when rails tries to run with:
It is impossible to re-produce this error locally for affected projects, and re-installing gems, updating gems, changing ruby versions, etc., seems to have no effect.
I think previously the runtime was including some pre-compiled nokogiri versions, and with this latest change they dropped some of the versions they were previously including, or something. Just a guess.
Would really appreciate it @dazuma if you guys pass this along to the ruby standard environment team.
English stackoverflow issue: here
Japanese stackoverflow issue posted by someone else: here