quick-fix: assertion contracts tests #2924
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
0xverin
force-pushed
the
quick-fix-assertion-contracts-tests
branch
from
c829e1c to
61be53a
Compare
higherordertech
approved these changes
Jul 23, 2024
Kailai-Wang
requested changes
Jul 23, 2024
0xverin
force-pushed
the
quick-fix-assertion-contracts-tests
branch
from
f5617bd to
e58acb4
Compare
Kailai-Wang
approved these changes
Jul 23, 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.
Context
fix https://github.com/litentry/litentry-parachain/actions/runs/10047804865/job/27782346298
Reason: ts-tests only set one secret when deploying contracts, that when requesting
bnb, noderealclient needs to be used,it needs secrets[1], which is out of index of array,that causes the secret to be unable to be decoded when requesting dynamic contracts.Solution: Adding at least 3 secrets.