Merged #559 into master.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/pull/559#event-5412730954
> I have fixed in PR #561. Please help to review and approve this PR (we won't
> merge any PR without review). Thanks.
Will review and verify it, thanks.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
I have fixed in PR #561. Please help to review and approve this PR (we won't
merge any PR without review). Thanks.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
> The CI identified the following issue.
> ![image](https://user-images.githubusercontent.com/10856796/135905616-60640390-262a-47a3-9201-495bb7f62377.png)
> Is it related to this PR? or anything I should fix in this PR? thanks.
This is caused by the CI environment. We didn't pin openssl to a
The CI identified the following issue.
![image](https://user-images.githubusercontent.com/10856796/135905616-60640390-262a-47a3-9201-495bb7f62377.png)
Is it related to this PR? anything I should fix in this PR? thanks.
--
You are receiving this because you are subscribed to this thread.
Reply to
> I see several docs also contain instructions to use `docker-compose` to start
> services. Can you also change these? Thanks.
>
> * `docs/my-first-function.md`
> * `docs/azure-confidential-computing.md`
sure, will do. thanks.
--
You are receiving this because you are subscribed to this
I see several docs also contain instructions to use `docker-compose` to start
services. Can you also change these? Thanks.
- `docs/my-first-function.md`
- `docs/azure-confidential-computing.md`
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or
My colleague helped me to identified an issue on his icelake server, I will add
a fixup on top of this PR, thanks.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Thanks. This is really cool!
Let me test it on servers with different kinds of SGX drivers. (This also
bother me since we cannot test this in our CI)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
## Description
Added a bash script to detect sgx device and aesm service
heuristically, and start teaclave services without needing to specify
corresponding docker compose file manually. this script can detect and
handle containerized aesm service as well.
Fixes #553
## Type of change (select
10 matches
Mail list logo