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 a setting assignment in the settings/preferences controller which had a side effect of mutating the global setting defaults, which then caused an issue in the api notifications spec, but only when the preferences spec ran first, which is why the failure was intermittent.
This should fix what have been intermittent CI failures like https://travis-ci.org/tootsuite/mastodon/jobs/224311789
I left an
xit
spec in here with a note about whats happening, because I don't know how to resolve this. It seems like that assignment style should not be mutating the setting defaults, but that's probably happening in therails-settings-cached
gem itself, or in our interaction with it.Steps to replicate the failure, prior to these changes: