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.
Using SHA1 instead of SHA256 for script's hexdigest to match the expectations of the graphql-pro gem.
That gem is a private/pro gem doesn't have a visible repo of source code, but I'll copy relevant code here. When it is registering its redis scripts, it uses a SHA1 hexdigest.
Our mock_redis_lua_extension2 gem had been using SHA256, which results in this error in tests
Using a matching SHA/hexdigest will eliminate this error from tests (see clean build here)