Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Error when initiator is true
See original GitHub issuevar peer = new Peer({ initiator: true })
produces error:
[57803:1226/220911:ERROR:webrtcsession.cc(1384)] ConnectDataChannel called when data_channel_ is NULL.
in electron via electron-spawn
setting initiator to false does not cause an error.
Issue Analytics
- State:
- Created 8 years ago
- Comments:10 (9 by maintainers)
Top Results From Across the Web
Error: Initiator tried to bypass the security phase but we cannot
Hi,. I started working on new company and tonight we lost storage for about an hour and errors came: ERROR event from storage...
Read more >Solved: Error While creating Initiator group - NetApp Community
An initiator cannot be a member of two igroups of different OS types. For example, if you have an initiator that belongs to...
Read more >Error "Initiator not found in database" when creating/editing ...
Go back to the iSCSI Target created in Step 2 and edit it. You should find that it's "Initiator Group ID" value has...
Read more >What is "initiator other" in network in chrome console?
"Initiator Other" usually means the network request was made from a user, not from Chrome, a redirect or a script. The request was...
Read more >HPE MSA 2060 Connectivity to this host group is lo...
The initiator is stating that it is not Discovered, this means that the HBA with that WWID is not logged into the MSA....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
And with one comment, they just fixed the bug: https://bugs.chromium.org/p/chromium/issues/detail?id=579430 Will take a while to make it through the Chromium release process, but yay!
Related issue: https://github.com/feross/webtorrent-desktop/issues/85