1505651 - tc-client-web WebSocket tests fail

Status: RESOLVED FIXED

(Taskcluster :: Services, enhancement)

Description

[Dustin J. Mitchell [:dustin] (he/him)]

I can't figure out why.  The WebSocket object emits an `error` event after construction, and the Event is basically content-less:
  https://stackoverflow.com/questions/18803971/websocket-onerror-how-to-read-error-description

So, something is going wrong opening a websocket from the headless browser to wss://events.taskcluster.net/v1/listen/websocket -- and the browser won't tell us what.

Comment 1

[Dustin J. Mitchell [:dustin] (he/him)]

Hassan, can you replicate this?  Any idea how to get more information?

Comment 2

[Hassan Ali (:hassan)]

I can replicate this when I run the tests locally. Inside `handleClose`, I noticed that if I put a log statement `console.log(e.code)` I get `1006`. A quick search showed https://stackoverflow.com/a/19305172/6150432.

Comment 3

[Hassan Ali (:hassan)]

We could probably try migrating tc-client-web to neutrino v9 and see if it magically gets resolved.

Comment 4

[Dustin J. Mitchell [:dustin] (he/him)]

Good find on the error code!

https://tools.ietf.org/html/rfc6455#section-7.4.1

   1006

      1006 is a reserved value and MUST NOT be set as a status code in a
      Close control frame by an endpoint.  It is designated for use in
      applications expecting a status code to indicate that the
      connection was closed abnormally, e.g., without sending or
      receiving a Close control frame.

a neutrino upgrade is a good place to start..

Comment 5

[Hassan Ali (:hassan)]

Opened https://github.com/taskcluster/taskcluster-client-web/issues/37.

Comment 6

[Hassan Ali (:hassan)]

Is this still an issue?

Comment 7

[Dustin J. Mitchell [:dustin] (he/him)]

It seems fine in CI..