Leland Takamine
Leland Takamine
Today the `nanoscope start` command only supports tracing a single thread. The data you see are the calls executed on the main thread only.
Sorry, we are not able to provide that at this time. There may be workarounds available if you do a quick internet search.
Got it - thanks for putting this on our radar. In case you feel so inclined, the code for key navigation is [here](https://github.com/uber/nanoscope/blob/master/src/main/resources/index.html#L834).
Looks like it's failing when trying to grab the name of a method. I would be able to debug with sample code that reproduces this issue. My initial guess is...
@g123k Thanks for reporting! We'll take a look into this! To help us out with debugging this, can you try quoting the "123123"? It may be that we are not...
Got it thanks @g123k - We'll dive into this!
Reopening as I believe we should investigate if we can fix this in Meastro itself
This is really good feedback @M-heiba and improved debuggability is definitely on the radar. Stay tuned!
This is indeed covered with the conditional runFlow execution
Note that this makes the most sense once Maestro is handling idb_companion internally. It's possible to implement the above (or part of it) before Maestro handles idb_companion internally, but the...