Solve issue about return already existing request_ids #36
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
…stem cannot locate enough nodes it fails and doesn't check the already existing requests. Solution: Execute the already request_id check before getting the existing nodes, allowing to return the existing ones also if any good node is found.
hoh
approved these changes
Sep 27, 2024
nesitor
deleted the
andres-fix-solve_existing_request_id_check_order
branch
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.
Problem: If a user request an already generated request_id and the system cannot locate enough nodes it fails and doesn't check the already existing requests.
Solution: Execute the already request_id check before getting the existing nodes, allowing to return the existing ones also if any good node is found.