Skip to content

Error after update node 8.7.0 #16190

Description

@Nastras

Hello, I have made an update to node on 8.7.0 I get the following error message. The same message I have already received with 8.6.0 and 8.5.0.

The last working version is 8.4.0 without this error.

I have had hope that it was fixed in the 8.7.0?

Hello, I have made an update to node on 8.7.0 I get the following error message. The same message I have already received with 8.6.0 and 8.5.0.

The last working version is 8.4.0 without this error.

I have had hope that it was fixed in the 8.7.0?

Okt 13 20:21:42 Server homebridge[27375]: /usr/local/bin/node[27375]: ../src/cares_wrap.cc:1944:void node::cares_wrap::{anonymous}::GetAddrInfo(const v8::FunctionCallbackInfov8::Value&): Assertion `args[4]->IsBoolean()' failed.
Okt 13 20:21:42 Server systemd[1]: homebridge.service: Main process exited, code=killed, status=6/ABRT
Okt 13 20:21:42 Server systemd[1]: homebridge.service: Unit entered failed state.
Okt 13 20:21:42 Server systemd[1]: homebridge.service: Failed with result 'signal'.
Okt 13 20:21:52 Server systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
Okt 13 20:21:52 Server systemd[1]: Stopped Node.js HomeKit Server.
Okt 13 20:21:52 Server systemd[1]: Started Node.js HomeKit Server.
Okt 13 20:21

Activity

  1. changed the title [-]Error after Update Node 8.7.0[/-] [+]Error after update node 8.7.0[/+] on Oct 13, 2017
  2. added
    c++Issues and PRs that require attention from people who are familiar with C++.
    on Oct 13, 2017
  3. Fishrock123 commented on Oct 13, 2017

    @Fishrock123
    Contributor

    @Nastra888 are you using any native C++ modules in your node_modules?

  4. evanlucas commented on Oct 13, 2017

    @evanlucas
    Contributor

    I'm guessing you are using homebridge (https://github.com/nfarina/homebridge)?

    Homebridge has a dependency on https://github.com/KhaosT/HAP-NodeJS, which has a dependency on https://github.com/agnat/node_mdns. mdns appears to be using some node internals (https://github.com/agnat/node_mdns/blob/756c6c27980c882eeb34022428711fa77d2b4ae6/lib/resolver_sequence_tasks.js#L103-L165) which is what appears to be causing this.

  5. bnoordhuis commented on Oct 14, 2017

    @bnoordhuis
    Member

    Closing, see agnat/node_mdns#199 and agnat/node_mdns#200.

    Duplicate of #15711, also by @Nastra888...

  6. added
    wrong repoIssues that should be opened in another repository.
    on Oct 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    c++Issues and PRs that require attention from people who are familiar with C++.wrong repoIssues that should be opened in another repository.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions