Update ruby version and lockfile #3
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was recently a production outage, and I wondered why the status page was showing all "up"/green status.
After a bit of poking around in relevant systems, it turns out that a ruby upgrade that was implemented broke the uptime monitoring, due to lack of gems under new ruby version/strict ruby version enforcement in Gemfile.
I applied the Gemfile patch here by porting it across from QPixel, and then used bundler to reinstall the right gems under the new ruby version, hence the gem lock file update. After these changes, the system recovered and is now functional.
This patch is being used operationally right now, so this PR is made for transparency purposes.