ergo: RPC call doesn't use timeout when an erlang node is down [v1.2.2]

Hello!

I’ve found a new defect after 1.2.2.

You can easily reproduce it. Just call CallRPCWithTimeout function when an erlang node is down.

Log:

2021/05/11 09:52:16 [test@MBP-Alexandr] RPC calling: demo@MBP-Alexandr:erlang:system_info
2021/05/11 09:52:16 [test@MBP-Alexandr] sending message by tuple [rex demo@MBP-Alexandr]
2021/05/11 09:52:16 [test@MBP-Alexandr] can't connect to demo@MBP-Alexandr: Can't resolve port for demo@MBP-Alexandr: desired node not found

And the app is stuck

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 15

Most upvoted comments

Haha, sorry for that 😃 And thanks a lot for your patience and help. Now it works! I hope it was the last issue from me.

Noksa on May 11, 2021