1438331 - Keep the last 5 debug messages in localStorage

Status: RESOLVED FIXED

(Taskcluster :: UI, enhancement)

Description

[Hassan Ali (:hassan)]

We don't always want to show an error when something goes wrong. For example,
when auth0 renewal fails, we currently use `console.error` without showing an error box since there was no user iteraction. That console error is invariably gone because the tab was closed by the time anyone notices.

We want to have a way to debug those issues when users report them. For example, this happened today:

<gerard-majax> is it normal that I get disconnected from taskcluster/auth0 often?
like I signed in this afternoon, and now I'm again signed off


One solution to that is to to keep the last 5 debug messages about auth in localStorage and show those in the "manage credentials" page.

Comment 1

[:Eli Perelman]

No new localStorage interactions. All new storage will be kept in IDB. This way we can structure data and not deal with serialization.

Comment 2

[Hassan Ali (:hassan)]

That works as well. Would you recommend https://github.com/localForage/localForage for interacting with IDB?

Comment 3

[:Eli Perelman]

If we are working with more than key-value pairs, which would seem to be the case if we are working with several rows of data, I'd recommend dexie.

https://www.npmjs.com/package/dexie

Comment 4

[:Eli Perelman]

https://github.com/dfahlander/Dexie.js/tree/master/samples/react

Comment 5

[Hassan Ali (:hassan)]

I wouldn't say that we'll be working with more than key-value pairs. For debug messages, we just need to store a key 'notifications' with the value being an array of strings or objects. I think this is doable with localForage imo.

Comment 6

[:Eli Perelman]

Now that I think of it, we should probably roll this into our analytics story. Tracking views, usage, errors, etc. by having them shipped off to a remote service.

Comment 7

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

Perhaps, but we need this done *now* as we are having lots of authentication failures and we have no idea why.  This is useful debugging information that we need, like, yesterday.

Comment 8

[:Eli Perelman]

https://github.com/taskcluster/taskcluster-web/issues/53

Comment 9

[Hassan Ali (:hassan)]

This will be handled by reporting to sentry which has been integrated in tc-web[1].

[1] https://github.com/taskcluster/taskcluster-web/commit/6f59e5e8e5169db652db0965ddf023223031d78c