-
Notifications
You must be signed in to change notification settings - Fork 8
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
feat: complete ckb4ibc-test
with embedded forcerelay-ckb-sdk
#305
Conversation
@jjyr I'm refactoring ckb4ibc-test framework, I'm afraid it has impact on your current work of testing Axon Endpoints, so please check this PR |
5e4fac9
to
7d549a6
Compare
@Flouse I have completed the coding of packet test case embedded in |
366f08a
to
94cf4ba
Compare
@blckngm packet cell has successfully searched on chain_a, but the next problem is in |
a86cb96
to
b145d40
Compare
@blckngm current issue is blocked when searching RecvPacket through SDK, please take a moment to look at it synapseweb3/forcerelay-ckb-sdk#7 |
eb21636
to
94a8cc5
Compare
@blckngm after using the latest revision of forcerelay-ckb-sdk, the CI process has stuck in searching AckPacket cell on chain-a https://github.com/synapseweb3/forcerelay/actions/runs/6008594876/job/16296503004?pr=305, so please take a look at it |
It's still related to cursor usage. Use https://github.com/synapseweb3/forcerelay-ckb-sdk/tree/temp-fix-cursor for now. |
@jjyr please help me check it out, I got nothing from my failed CI and I found its processing list is different from yours, so have you done something on it in your PR ? https://github.com/synapseweb3/forcerelay/actions/runs/6012440875/job/16329029412?pr=305 |
rt.block_on(ckb::sighash::init_sighash_celldep(&rpc_client)) | ||
.unwrap(); | ||
let hash = send_transaction(&chain_a_url, send_packet_tx).unwrap(); | ||
println!( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A way to implement this test on ibc-test-framework is to call the contract from counterparty chain, and check the contract's state in the deployed chain.
We should implement a contract both in solidity and in CKB to do this test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what's your recommend on merging this PR? my opinion is to start a new branch and move essential changes of packet test into it from this PR, do you recommend just merging it exactly after rebasing? |
…ts, the next is debugging the relayer monitor logic
Don't block when the counterparty client type is already known!
…ten it through SDK
61aca69
to
ae57d4b
Compare
ae57d4b
to
3d534e0
Compare
@Flouse the next operation of coding to do in
|
f266d88
to
609e12a
Compare
ff0ecb8
to
e7cd6c0
Compare
@jjyr suggestions in comments are applied |
background:
change log:
*_type_args
config values from test-framework cratetype_args
totype_hash
for security concernsspecific_test_only_for_ckb
p.s.
integration-test
->ica-filter-test
seems cannot be fixed until we merge Hermes v1.6.0, it seems has pre-packed nix package that only matches latest Hermes version, which would cause failure while using previous version of Hermes framework