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 }}
This repository has been archived by the owner on Aug 1, 2023. It is now read-only.
This way, when we do: getWsStarAddr(nodeB.addrs)m we will have /p2p-circuit/p2p-websocket-star/ipfs/Qme9NFGddMSBQeQWkMEMJtnko9hA4pWhwPH9cJyteCkbyS for firefox and /ip4/127.0.0.1/tcp/24642/ws/p2p-websocket-star/ipfs/Qmbmj7h1QzP7EW5xvssMZogM1RB4zs8JRf5d1XJmkJ71Er for chrome
After debugging in the switch, I got a weird behaviour. In firefox, the second dial arrives to the switch, but only with Circuit, no websocket-star, which then fails. In chrome, the second dial does nothing. Basically, even before starting the tests, there is an attempt of nodeB connecting nodeA, and they get connected before the connect in the test. I disabled discovery and bootstrap is empty, so is really odd
The text was updated successfully, but these errors were encountered:
The firefox CI job was disabled, as a consequence of some inconsistencies between chrome and firefox tests for circuit ipfs/interop#62 https://travis-ci.com/ipfs/interop/builds/108339116.
After a small debugging session, the conclusions so far are the following:
Taking this test as an example of a failure: https://github.com/ipfs/interop/blob/master/test/circuit/browser.js#L103-L117 nodeB addresses are different in chrome and firefox
firefox:
chrome:
This way, when we do:
getWsStarAddr(nodeB.addrs)
m we will have/p2p-circuit/p2p-websocket-star/ipfs/Qme9NFGddMSBQeQWkMEMJtnko9hA4pWhwPH9cJyteCkbyS
for firefox and/ip4/127.0.0.1/tcp/24642/ws/p2p-websocket-star/ipfs/Qmbmj7h1QzP7EW5xvssMZogM1RB4zs8JRf5d1XJmkJ71Er
for chromeAfter debugging in the switch, I got a weird behaviour. In firefox, the second dial arrives to the switch, but only with
Circuit
, nowebsocket-star
, which then fails. In chrome, the second dial does nothing. Basically, even before starting the tests, there is an attempt of nodeB connecting nodeA, and they get connected before the connect in the test. I disabled discovery and bootstrap is empty, so is really oddThe text was updated successfully, but these errors were encountered: