[apache/incubator-teaclave] How to use _numpypy (#410)

Since numpy and _numpyy are used differently, can u list the usage of _numpyy ? -- 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/issues/410

Re: [apache/incubator-teaclave] About teaclave-file-128 encryption algorithm error (#404)

Since there is no update on this issue, I'm closing it. Feel free to reopen if you think it's still valid. Thanks. -- 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/issues/404#issue

Re: [apache/incubator-teaclave] About teaclave-file-128 encryption algorithm error (#404)

Closed #404. -- 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/issues/404#event-3692041950

[apache/incubator-teaclave] Use DISCLAIMER-WIP (#409)

## Description Use `DISCLAIMER-WIP` to disclaim potential issues. You can view, comment on, or merge this pull request online at: https://github.com/apache/incubator-teaclave/pull/409 -- Commit Summary -- * Use DISCLAIMER-WIP -- File Changes -- D DISCLAIMER (8) A DISCLAIMER-WIP (1

License Review

Hi all, I'm working on an Apache incubator release. We want to make sure there are minimal license issues. If there are any issues, we can put them in the DISCLAIMER-WIP file. Right now, I did a preliminary license review including license header in source code and third-party licenses review. I

Re: [apache/incubator-teaclave-sgx-sdk] How to handle too big of a memory allocation? (#254)

I haven’t found a simple way to recover from this, because the stack has been overused, and exceptions may occur when running any code. One possible way is to use another additional stack, just as the exception handler uses a separate stack. -- You are receiving this because you are subscribed

Re: [apache/incubator-teaclave-sgx-sdk] How to handle too big of a memory allocation? (#254)

Thanks for the prompt response @volcano0dr! Is there any way to recover from this, like we did above with `sgx_std::alloc::set_alloc_error_hook` for heap over-allocation? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https

Re: [apache/incubator-teaclave-sgx-sdk] How to handle too big of a memory allocation? (#254)

@assafmo If the enclave passes the stack size limit, EALL will return SGX_ERROR_STACK_OVERRUN. Enclave thread context memory layout: guard page | stack | guard page | TCS | SSA | guard page | TLS/TD When the stack is overallocated, the enclave will receive an exception, and the exception handl