Skip to content

quicer:open_lib() crashes with noproc if called early in node boot #80

Closed

Description

@HoloRin

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

case file:read_file_info(PrivDir) of
and results in the following error:

The on_load function for module quicer_nif returned:
{noproc,{gen_server,call,[file_server_2,{read_file_info,[...]},infinity]}}

Activity

  1. qzhuyan commented on Mar 21, 2022

    @qzhuyan
    Collaborator

    @pjk25 thanks, run Erlang Distribution over QUIC is also in my TODO list. Could you share your boot script? running on linux right?

  2. self-assigned this
    on Mar 21, 2022
  3. HoloRin commented on Mar 21, 2022

    @HoloRin
    Author

    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.

  4. qzhuyan commented on Mar 21, 2022

    @qzhuyan
    Collaborator

    So I guess that implies the default boot script?

    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.

  5. locked and limited conversation to collaborators on Mar 21, 2022
  6. converted this issue into a discussion #82 on Mar 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions