Add "bug report" tool to DevTools.

piotrswigon commented 5 years ago

It will allow downloading a file from DevTools that can be attached to the bug report. This file can then be opened by the debugging engineer using the standalone DevTools UI, or inspected manually.

The downloadable report will, among other information, contain a log of all the messages received by DevTools. This will allow to transparently snapshot the state of all the views it provides. Today this already includes:

History of Planning and Strategizing.
Log of communication between Particle Execution Host and Context.
State of all stores visible in arcs’ contexts. This is a decent start for debugging, but there is an expectation that this list will grow.

We should also have:

Serialization of all the opened arcs
Log of all the JavaScript errors that happened.
Full log from WebShell (what you get with &log).
Log of actions performed by Runtime - this ideally would be covered if we sprinkle in more tracing throughout the codebase.

mariakleiner commented 5 years ago

maybe this tool should be filing the bug itself as well?

shaper commented 5 years ago

Felt like a high p2, possibly p1. Piotr should review priority of dev tooling issues overall and revise to fit his plan.

shaper commented 5 years ago

@yuangu-google may be interested in helping here, adding him to consider.

piotrswigon commented 5 years ago

@yuangu-google when you have time to work on this (either as a fun 20% or as a main thing when other higher priority items are done) let's schedule a 1:1 . to discuss how exactly this could be done.

I have thoughts regarding Arcs Explorer and Arcs specific output, but I presume you may have ideas regarding enriching this with information from the Android system. I would be happy to design something together :)

PolymerLabs / arcs

Add "bug report" tool to DevTools. #2584