Incompatibility with Hashbrown 0.11

[haerdib]

I'm facing the current problem while updating to substrate v4.0.0-dev:

sp-trie, which our enclave depends on, has been updated in v4.0.0:

• new sp-trie cargo.toml
• memory-db cargo.toml
• issue: Incompatible with hashbrown 0.11 apache/incubator-teaclave-sgx-sdk#326

mesalock has forked getrandom but only to v0.1, not v0.2

How should we proceed here?

[clangenb]

I believe we need to fork getrandom v0.2 on our own and make it sgx-compatible.

Reason:

• we can only patch crates if they have the same version number. I was unable to run cargo tree with the upgrade branch, but I believe, we can't get rid of it in the sgx-runtime. So, we need to patch it.

We can issue a PR-afterwards to getrandom-sgx, which might get included somewhen.

[brenzi]

Consider requesting a version update with teaclave/mesalock. They are very helpful and quick

[haerdib]

This issue is temporarily fixed with the local fork integritee-network/getrandom-sgx#1. But before closing this issue I would like to either have the tests of the PR pass or use an updated fork from teaclave. I'm still waiting for a response on apache/incubator-teaclave-sgx-sdk#350.

[brenzi]

status? @haerdib

[clangenb]

I have checked @haerdib pr to upstream. She said she had some issues running the tests, which are blocking to make it work. However, this is only a rust-toolchain problem, I think. I could take a look at it and make sure the tests pass, such that nothing is in the way of the upstream merge.

[haerdib]

I believe this issue is no longer necessary, as mesalock seems to be dead. So we need to maintain it ourselves anyway if we want to stay up to date.