You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since debugging the extension on someones machine may be problematic (or even asking to provide console logs), I was thinking it could be beneficial to write extension logs to a file additionally (maybe even without verbose flag on). Then when there is an issue with extension we can just ask to provide log dump (there could be a command to show it) and analyze it which could help with debugging/solving the issues which are hard to reproduce.
This should be done in a way to not impact extension performance and keep the log file at reasonable size, etc.
The text was updated successfully, but these errors were encountered:
Since debugging the extension on someones machine may be problematic (or even asking to provide console logs), I was thinking it could be beneficial to write extension logs to a file additionally (maybe even without
verbose
flag on). Then when there is an issue with extension we can just ask to provide log dump (there could be a command to show it) and analyze it which could help with debugging/solving the issues which are hard to reproduce.This should be done in a way to not impact extension performance and keep the log file at reasonable size, etc.
The text was updated successfully, but these errors were encountered: