You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@teaclave.apache.org by gjj <no...@github.com> on 2020/06/22 01:52:07 UTC
[apache/incubator-teaclave] invoke
builtin_private_join_and_compute.py error (in simulation mode) (#366)
In simulation mode
--
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/366
Re: [apache/incubator-teaclave] invoke
builtin_private_join_and_compute.py error (in simulation mode) (#366)
Posted by Mingshen Sun <no...@github.com>.
Can you run the service with `RUST_LOG=teaclave=debug` env vars and paste the log here? 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/366#issuecomment-647248719
Re: [apache/incubator-teaclave] invoke
builtin_private_join_and_compute.py error (in simulation mode) (#366)
Posted by gjj <no...@github.com>.
builtin_gbdt_train.py can not work.
looks like the example with 'register_input_file' can not work . the other can work(mesapy_echo.py、builtin_echo.py 、builtin_online_decrypt.py...)
--
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/366#issuecomment-647225257
Re: [apache/incubator-teaclave] invoke
builtin_private_join_and_compute.py error (in simulation mode) (#366)
Posted by Mingshen Sun <no...@github.com>.
I saw an "ocall error" in the response. Maybe this is from the file agent. Since you are saying about using `file://` scheme, I guess this is because your registered file does not exist on the file system of the execution service.
--
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/366#issuecomment-647242271
Re: [apache/incubator-teaclave] invoke
builtin_private_join_and_compute.py error (in simulation mode) (#366)
Posted by Mingshen Sun <no...@github.com>.
Hi, any update on this issue?
--
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/366#issuecomment-652115453
Re: [apache/incubator-teaclave] invoke
builtin_private_join_and_compute.py error (in simulation mode) (#366)
Posted by Mingshen Sun <no...@github.com>.
From your previous screenshots of the log, I can see that you are using `docker-compose` to start the services. This command will launch services in different container with isolated file system, i.e., the execution service does not see files in your local file system. If that's the case, please use shared volume in docker with the host and preserve the same path. Or, do not run services in containers separated with the host file system. 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/366#issuecomment-647788812
Re: [apache/incubator-teaclave] invoke
builtin_private_join_and_compute.py error (in simulation mode) (#366)
Posted by gjj <no...@github.com>.
> I saw an "ocall error" in the response. Maybe this is from the file agent. Since you are saying about using `file://` scheme, I guess this is because your registered file does not exist on the file system of the execution service.
It exists in the local system
--
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/366#issuecomment-647247025
Re: [apache/incubator-teaclave] invoke
builtin_private_join_and_compute.py error (in simulation mode) (#366)
Posted by Qinkun Bao <no...@github.com>.
OK. Thanks for the information. Could you please type `make run-tests` or `make run-examples`
after you build the project?
--
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/366#issuecomment-647226849
Re: [apache/incubator-teaclave] invoke
builtin_private_join_and_compute.py error (in simulation mode) (#366)
Posted by gjj <no...@github.com>.
It exists.
--
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/366#issuecomment-647245957
Re: [apache/incubator-teaclave] invoke
builtin_private_join_and_compute.py error (in simulation mode) (#366)
Posted by gjj <no...@github.com>.
but
--
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/366#issuecomment-647329349
Re: [apache/incubator-teaclave] invoke
builtin_private_join_and_compute.py error (in simulation mode) (#366)
Posted by gjj <no...@github.com>.
> From your previous screenshots of the log, I can see that you are using `docker-compose` to start the services. This command will launch services in different container with isolated file system, i.e., the execution service does not see files in your local file system. If that's the case, please use shared volume in docker with the host and preserve the same path. Or, do not run services in containers separated with the host file system. Thanks.
As for the error "convert: failed to open SRC file", I read the source code of teaclave and found that the error was reported when reading outputFile. So I don't register outputFile anymore, just register inputfile. In this case, I can run through the python I wrote and read the data of inputfile normally. However, if I register outputFile, this error will be reported. This outputFile should also exist in teaclave_ execution_service docker container ?
--
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/366#issuecomment-647856360
Re: [apache/incubator-teaclave] invoke
builtin_private_join_and_compute.py error (in simulation mode) (#366)
Posted by Qinkun Bao <no...@github.com>.
Did you try other examples (e.g., builtin_gbdt_train.py)? Did they work as expected on your machine?
--
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/366#issuecomment-647223604
Re: [apache/incubator-teaclave] invoke
builtin_private_join_and_compute.py error (in simulation mode) (#366)
Posted by gjj <no...@github.com>.
It's really a non-existent error. but It exists in the local system
--
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/366#issuecomment-647254155
Re: [apache/incubator-teaclave] invoke
builtin_private_join_and_compute.py error (in simulation mode) (#366)
Posted by gjj <no...@github.com>.
make run-tests work。 i use the local file "file://" to register_input_file and register_output_file. is that a problem ?
--
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/366#issuecomment-647232073
Re: [apache/incubator-teaclave] invoke
builtin_private_join_and_compute.py error (in simulation mode) (#366)
Posted by Mingshen Sun <no...@github.com>.
Closed #366.
--
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/366#event-3500244968
Re: [apache/incubator-teaclave] invoke
builtin_private_join_and_compute.py error (in simulation mode) (#366)
Posted by Mingshen Sun <no...@github.com>.
If you are using docker, the file should be also in the container of the execution service.
--
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/366#issuecomment-647254949
Re: [apache/incubator-teaclave] invoke
builtin_private_join_and_compute.py error (in simulation mode) (#366)
Posted by gjj <no...@github.com>.
> Hi, any update on this issue?
you can close this one
--
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/366#issuecomment-652130552
Re: [apache/incubator-teaclave] invoke
builtin_private_join_and_compute.py error (in simulation mode) (#366)
Posted by Mingshen Sun <no...@github.com>.
Closed.
--
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/366#issuecomment-652130846