You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 3, 2023. It is now read-only.
currently it is quite fiddly to find a specific action in the history, it looks something like this:
while instance
.state().history.iter().find(|aw| match aw.action().signal(){Signal::ReturnZomeFunctionResult(_) => true,
_ => false,}) == None{println!("Waiting for ReturnZomeFunctionResult from genesis");sleep(Duration::from_millis(10))}
it seems like this could be wrapped up into some tooling, with or without the loop
the alternative is checking for unreliable properties of the state, like the length of history
the history length is being read in multiple places in the codebase making everything fragile
it is too easy for some action logic to change slightly somewhere and leave the test suite hanging with no explanation in some seemingly unrelated part of the codebase
The text was updated successfully, but these errors were encountered:
@thedavidmeister the test util depends on the signal implementation which still needs to be tested and vetted, so it can't really be isolated at the moment
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
currently it is quite fiddly to find a specific action in the history, it looks something like this:
it seems like this could be wrapped up into some tooling, with or without the loop
the alternative is checking for unreliable properties of the state, like the length of history
the history length is being read in multiple places in the codebase making everything fragile
it is too easy for some action logic to change slightly somewhere and leave the test suite hanging with no explanation in some seemingly unrelated part of the codebase
The text was updated successfully, but these errors were encountered: