Skip to content
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

Remove expect in data conversion. #603

Open
wants to merge 14 commits into
base: main
Choose a base branch
from
Open

Conversation

musitdev
Copy link
Contributor

@musitdev musitdev commented Sep 16, 2024

Summary

  • RFCs: Link to RFC, Link to RFC, or $\emptyset$.
  • Categories: any of protocol-units, networks, scripts, util, cicd, or misc.

From issue #511

Changelog

  • Change From<Vec<u8>> to TryFrom<Vec<u8>>. Update trait bound.
  • Trace error on channel send error instead of expect().

Testing

Outstanding issues

@0xmovses
Copy link
Contributor

cargo test --test eth_movement -- --nocapture --test-threads=1

failures:
    test_movement_client_should_successfully_call_lock_and_abort
    test_movement_client_should_successfully_call_lock_and_complete

test result: FAILED. 8 passed; 2 failed; 2 ignored; 0 measured; 0 filtered out; finished in 132.92s

@musitdev
Copy link
Contributor Author

Do you have the same error as me: Error: FaucetClientError { inner: Inner { kind: HttpStatus(500), source: None } } ?
I don't understand why the faucet fail.
I rebuild movement cli from the current main.

@musitdev
Copy link
Contributor Author

I think it comes from the fact that the movement process is not killed correctly or take time to kill.

@musitdev
Copy link
Contributor Author

It's a timing issue, on my PC the node take time to start. It has a big local db so it take several seconds to start and when the faucet fund request is sent the node is not completely started. The faucet take some more time to be ready.

@musitdev
Copy link
Contributor Author

I get the error: Transaction submission error: Unknown error Transaction committed on chain, but failed execution: NUMBER_OF_ARGUMENTS_MISMATCH
related to the other PR.

@0xmovses
Copy link
Contributor

Yes this error is expected now, and I'm working on a fix on this branch #614

@mzabaluev
Copy link
Collaborator

This needs updating from main.

Yes this error is expected now, and I'm working on a fix on this branch #614

@0xmovses That PR got closed without merging, is there another fix?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants