Fix for encrypted tasks #1008
Merged
Fix for encrypted tasks #1008
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
…gorithm container properly These requests were not picked up by the specialized proxy server endpoint due to the argument included in the route
The former does not make sense to have because in the run endpoint there are no results to decrypt
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.
Issue was that the request from the central container did not go through the proper specialized route in the proxy server, so the results were not decrypted when they got to the central part of the algorithm.
Also, a few things had to be fixed/renamed in the proxy routes (they had thus never been used on v4 and contained minor bugs).
Finally, improved a check in the CLI for encryption
Fix #955