在做PSI时，如果一方运行，另一方不运行。在尝试连接超时时会出现段错误 about spu

[icavan]

Yes. This is expected behavior.

We do require our users to run both sides in a short time window if using SPU directly. If you wanna make life easier, you could try to call PSI in Secretflow, which will help dispatch MPI PSI codes to both sides simultaneously.

---

BTW, if you do want to play with the core c++ API. The link timeout could be set by calling void SetRecvTimeout(uint32_t recv_timeout_ms); in https://github.com/secretflow/yasl/blob/beta/yasl/link/context.h#L163. Our simple_psi example just serves as a simple demo for experiencing the core PSI API. You could play and adjust timeout as you needed.

[Cryptographer63]

Yes. This is expected behavior.

We do require our users to run both sides in a short time window if using SPU directly. If you wanna make life easier, you could try to call PSI in Secretflow, which will help dispatch MPI PSI codes to both sides simultaneously.

BTW, if you do want to play with the core c++ API. The link timeout could be set by calling void SetRecvTimeout(uint32_t recv_timeout_ms); in https://github.com/secretflow/yasl/blob/beta/yasl/link/context.h#L163. Our simple_psi example just serves as a simple demo for experiencing the core PSI API. You could play and adjust timeout as you needed.

Thank you for your reply！

Secretflow is too big, I just need the PSI module. Excuse me, why is it designed this way? Are there any real issues to consider?

I'll try using SetRecvTimeout to see if that solves my problem.

I think the C++ API is still very important, after all, these APIs are closer to the bottom layer, and many developers like me can have more room to play.

[icavan]

Yes. This is expected behavior.
We do require our users to run both sides in a short time window if using SPU directly. If you wanna make life easier, you could try to call PSI in Secretflow, which will help dispatch MPI PSI codes to both sides simultaneously.
BTW, if you do want to play with the core c++ API. The link timeout could be set by calling void SetRecvTimeout(uint32_t recv_timeout_ms); in https://github.com/secretflow/yasl/blob/beta/yasl/link/context.h#L163. Our simple_psi example just serves as a simple demo for experiencing the core PSI API. You could play and adjust timeout as you needed.

Thank you for your reply！

Secretflow is too big, I just need the PSI module. Excuse me, why is it designed this way? Are there any real issues to consider?

I'll try using SetRecvTimeout to see if that solves my problem.

I think the C++ API is still very important, after all, these APIs are closer to the bottom layer, and many developers like me can have more room to play.

We do plan to open source all layers of the SecretFlow stack, including the C++ core API layer. Since we still have lots of pending optimizations waiting for formal security review and open source procedure, you might need to wait for a few months to get better API documentation and performance.

I did not expect you guys will play the c++ core API this quick. Let me know what you need. This might affect some priority decisions for where we should improve first.

[rivertalk]

Fixed in latest beta branch, closing...