-
Notifications
You must be signed in to change notification settings - Fork 267
Conversation
well, something in the build on circle CI causes it to come out with a different dna hash, then on my machine... |
hmmm dna address still coming back different that what happens when I run on my machine. I'm using the nix-shell command |
@zippy, I'm not sure but I guess any discrepancy in the toolchain will result in a different binary output. Maybe the hash should not be hardcoded in the test but rather taken from the DNA file under test? |
@@ -76,7 +74,8 @@ pub mod tests { | |||
|
|||
assert_eq!(globals.dna_name, "TestApp"); | |||
// TODO #233 - Implement agent address |
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.
// TODO #233 - Implement agent address | |
}; | ||
|
||
let dna = maybe_dna.or_else(|e: String| { | ||
let error_string = cx.string(format!("unable to call zome function: {:?}", &e)); |
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.
unable to call zome function?
…ochain-rust into globals-in-appspec
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.
Maybe just make sure that #233 ticket gets closed too. Awesome to have this in!
we have: We can access the app dna hash in the zome
and also
runtime globals are actually correct values (See invoke_init_globals) in the SoA.
as if they aren't implemented.
It actually looks to me like they are, at least partially, working. As these app_spec tests seem to show.
Feedback?