-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Call ID Insertion and Resolution For #520 #533
Merged
Merged
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
drewstone
requested changes
Dec 9, 2024
blueprints/incredible-squaring/contracts/src/IncredibleSquaringBlueprint.sol
Show resolved
Hide resolved
Serial-ATA
force-pushed
the
call_id_insertion
branch
2 times, most recently
from
December 9, 2024 21:29
39065c2
to
f79195c
Compare
Serial-ATA
force-pushed
the
call_id_insertion
branch
from
December 9, 2024 21:30
f79195c
to
d79a805
Compare
Serial-ATA
approved these changes
Dec 9, 2024
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.
Resolves #520
Resolves #534
TangleClientContext
now requires a call_id field:NOTE: This only propagates the call_id from the pre-processor to the job function. The propagation from the job function to the post-processor is not covered.