You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
quicer:open_lib() crashes with noproc if called early in node boot #80
Taking a look at using quic in an "Alternative Carrier for the Erlang Distribution", and it appears that file:read_file_info/1 cannot be called that early in node startup. The crash I see originates from
You'll have clarify what you mean by "boot script" for me. Currently I'm just starting a couple of erlang shells interactively and testing with those, so erl -sname lead -proto_dist inet_quic with an appropriate ERL_LIBS. So I guess that implies the default boot script?
So far testing this on macos, and I have since realized that quicer:accept_stream/3 times out when I follow the example in the README. make test does pass, though.
Yes. I just want to ensure we are looking at the same boot script.
quicer:accept_stream/3 times out
Are you on master branch?
note that client side must send something on the started stream otherwise the stack will not init the stream to the remote server side.
Activity
qzhuyan commentedon Mar 21, 2022
@pjk25 thanks, run Erlang Distribution over QUIC is also in my TODO list. Could you share your boot script? running on linux right?
HoloRin commentedon Mar 21, 2022
You'll have clarify what you mean by "boot script" for me. Currently I'm just starting a couple of erlang shells interactively and testing with those, so
erl -sname lead -proto_dist inet_quicwith an appropriateERL_LIBS. So I guess that implies the default boot script?So far testing this on macos, and I have since realized that
quicer:accept_stream/3times out when I follow the example in the README.make testdoes pass, though.qzhuyan commentedon Mar 21, 2022
Yes. I just want to ensure we are looking at the same boot script.
Are you on master branch?
note that client side must send something on the started stream otherwise the stack will not init the stream to the remote server side.