I think txn functions are allowed btw. I got the impression there's not any restrictions, as it's self-hosted.
I thought they said something about sucking in jars from an s3 bucket for example? Maybe I'll have to re watch, I guess I also don't understand the distinction of it being under their control either.
AMIs that are ran from the AWS marketplace are black boxes
The S3 jars thing was one of Stu's 'better' ideas and he was clear that they will not be supported in the first release
I thought it was all a weird presentation TBH ... he should announce things when they are real / ready rather than months beforehand. We are used to waiting 😉
I still find it odd that txor functions aren't supported, at all. As they're uploaded as a transaction type. If you need external jars, then I guess it makes some sense.
Agreed, in my case my txor fns are deployed using conformity so I don't need jars on the classpath. I'm hoping that might still work
what does this error mean in mach?
evalmachine.<anonymous>:98
throw ex;
^
Error: ENOENT: no such file or directory, open '.mach/cp'
at Object.fs.openSync (fs.js:652:18)
at fs.readFileSync (fs.js:553:33)
at evalmachine.<anonymous>:4299:43
at evalmachine.<anonymous>:4346:43
at mach$core$preprocess_dependencies_$_state_machine__4__auto____1 (evalmachine.<anonymous>:4367:4)
at mach$core$preprocess_dependencies_$_state_machine__4__auto__ (evalmachine.<anonymous>:4383:72)
at cljs$core$async$impl$ioc_helpers$run_state_machine (evalmachine.<anonymous>:90:74)
at cljs$core$async$impl$ioc_helpers$run_state_machine_wrapped (evalmachine.<anonymous>:93:63)
at evalmachine.<anonymous>:4398:67
at Immediate.cljs$core$async$impl$dispatch$process_messages [as _onImmediate] (evalmachine.<anonymous>:16:6)
it's hosted in your AWS but the AMI and all components are under their control (modulo an SSH entry point)