Problem:
We've gotten very good at fixing bugs that can be reproduced in our dev environments. However, bugs we can't reproduce in dev are typically ignored -- even if they happen frequently in production. We have added better diagnostics tools via the About > Troubleshooting > Client side logging toggle. However, currently it takes you out of the context in which the bug is actually happening to enable. This means to use it you must:
- Experience the bug
- Leave that context to go to
About > Troubleshooting > Client side logging
- Enable client side logging
- Go back to the original context
- Try to reproduce the bug
- Leave that context to go to
About > Troubleshooting > Client side logging
- Open the console
- Save the file
- Disable client side logging
In that whole process, the logs are filled with tons and tons of extraneous lines, making it very hard to isolate the problem -- assuming you can even reproduce it.
Solution:
Margelo recently added a "four finger tap" to enable low-level performance logging:

This works great because:
- You can enable and disable right where you experiencing the problem, without needing to leave that context. This tightens up the focus on the actual problem period, avoiding extraneous sampling.
- It automatically saves the file to local storage when disabled.
Let's expand that as follows:
- Allow enabling/disabling the console log directly from the "four finger tap menu"
- Automatically save the logs to disk when disabled (in either the four-finger menu, or in the
About > Troubleshooting menu)
- Show the filename that it was saved to, along with the platform
Share button to share it (this is already being used for the profile traces, so let's use it for logs as well)
Problem:
We've gotten very good at fixing bugs that can be reproduced in our dev environments. However, bugs we can't reproduce in dev are typically ignored -- even if they happen frequently in production. We have added better diagnostics tools via the
About > Troubleshooting > Client side loggingtoggle. However, currently it takes you out of the context in which the bug is actually happening to enable. This means to use it you must:About > Troubleshooting > Client side loggingAbout > Troubleshooting > Client side loggingIn that whole process, the logs are filled with tons and tons of extraneous lines, making it very hard to isolate the problem -- assuming you can even reproduce it.
Solution:
Margelo recently added a "four finger tap" to enable low-level performance logging:
This works great because:
Let's expand that as follows:
About > Troubleshootingmenu)Sharebutton to share it (this is already being used for the profile traces, so let's use it for logs as well)