Open lzkelley opened 6 years ago
MichaelScript
commented
6 years ago It looks like you have to use a different API than the one Zmq uses (which can't be fixed by 0rpc), see: https://stackoverflow.com/questions/41674063/is-it-possible-to-create-a-tcp-client-with-electron
Either way I don't believe this is something that can be fixed within the ZeroRPC repo as it's sockets come from https://github.com/JustinTulloss/zeromq.node
lzkelley
commented
6 years ago Thanks @MichaelScript I'll try looking into monkey-patching something to test this....
It's still also possible it's an issue with spawning the python process specifically in a packaged app (i.e. a problem unrelated to zerorpc-node). I'll update if I find anything.
sunhwan
commented
6 years ago Maybe this helps? https://github.com/fyears/electron-python-example/issues/8
Rachana-dot
commented
2 years ago Hello, Any Update on the solution, I have been having same issue for some time?
When my electron application in a development environment, zerorpc works perfectly and my javascript code communicated well with a background python process. When I package the application as a mac app, however, zerorpc is unable to connect and I eventually get a
Lost remoteerror.This problem is at the interface of zerorpc and electron, but I'm wondering if anyone on this side has any suggestions, or even ideas on where to start debugging... Unfortunately I'm new to Node and js as a whole.
Could it be some sort of (permissions?) issue with access to tcp or the local port when running as an app? Thanks!
node 6.11.5
electron 1.8.1
zerorpc 0.9.7
zmq 2.15.3
MacOS 10.12.6
Edits:
1) The python process is initially launched (based on logging the result of
require('child_process').spawn('python', [pyPath, port]);)2) If I manually run my python backend from the command line, then the electron front-end is able to communicate with it properly.
So I guess this suggestions that either A) the python process is terminating immediately (or soon) after launching; or B) for some reason the communication is failing specifically with the internally launched python process...