Yu Ding

maybe make everything depend on `tag` is a better choice? it'll take a while to update all dependencies under mesalock-linux, and then every dependency would be forced to add `tag...

@brenzi Plan to merge from branch v1.1.1-testing to master this weekend, followed by tagging every dependencies. It'll be a breaking change. We wonder if using `+` is better, which means...

> The `+` makes sense IMO how do we handle rustcrypto styled repo? such as https://github.com/mesalock-linux/rustcrypto-utils-sgx they contain multiple crate in one single repo. it's really hard to tag it...

thanks! I just tried with toml version. result shows that we can sgx info in Cargo.toml like ```toml [package] name = "xxx" version = "0.1.0+sgx1.1.1" authors = ["Yu Ding "]...

and i have a tool to inspect dependencies: cargo-deplist https://github.com/dingelish/cargo-deplist it outputs a topological sort of dependency graph along with `source` metadata. it seems we can find duplication or errors...

agree! seems to be something like "core-customizable xargo". am i correct? it'll be fantastic for embedded systems and TEEs!

@elichai Wow! Let me dig into it. My current thought is that let me upgrade to Intel SGX SDK v2.7 and provide threading support in the current style. And then...

The 3rd party problem still persists, because we may adjust something on file access such as tweaking `std::untrusted::fs`, or `std::sgxfs`. But I believe that some foundation crates would be fine...

Hey @elichai , could you please provide a minimal enclave to replay this error? I think I can resolve it :-)

Oh I understand. I remember this may be a long-lasting problem. The most convenient way could be building with Xargo and add a "backtrace" feature for std. Then import backtrace...