Forrest

Yeah work is here: https://github.com/bacalhau-project/examples/pull/186 Will close this ticket and track in example repo

Stopping the job with its long JobID appears to work: ``` bacalhau job stop ed1966b2-fa70-4010-be05-083db4bfb325 Checking job status Connecting to network ................ done ✅ 0.0s Verifying job state ................ done...

Yes, I understand this behavior is expected given the current implementation of the code - but from a UX perspective this unexpected imo. We're basically saying "You're holding it wrong"...

Would something like: ``` job-j-1234/ node-n-abc/ exitcode stderr stdout output-name/ ... node-n-def/ exitcode stderr stdout output-name/ ... ``` be acceptable?

> the problem is you won't get deterministic outputs or structure of the result directory Is determinism in output still something we care about? I'm not sure I see this...

Hey @Nasfame what is the problem we are trying to fix here? I think `bacalhau serve --private-internal-ipfs=false --ipfs-connect=/ip4/127.0.0.1/tcp/5001` works, right?

We'd make use of this logic in lily when loading things such as actor states (as you are already doing in [filexp](https://github.com/aschmahmann/filexp)), miner sectors, miner precommits, and any other information...

Thanks for getting this started @vinhloc30796 ❤️. You can now rebase this onto master, the changes this was based on have merged.

Here are some ideas for the layout for message number to method name mapping:: # Miner Actor ## Codes | Version | Code | | ------- | ------------------------------------------------------------ | |...

You could put the details from the above on its own page and link to it from the Message section of the page: https://lilium.sh/data/chain/#messages If you want to automate printing...