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
To resolve some issues, it's important to also show session logs. By default, the library limits outputting unnecessary logs and instead shows visually pleasing "spinner" logs. Unfortunately, if something goes wrong then these logs are usually not enough to identify a root cause of a problem and a potential fix. In these cases advanced logs are required within the issue template.
Here's how to turn on advanced logging in your sessions.
//config{"debug": true,"disableSpins":true,"logging": [{"type": "console"}],"logInternalEvents": true,//ONLY TURN THIS ON IF ASKED TO!"logConsoleErrors": true}
Now you have a terminal full of extra useful context to identify the root cause of an issue.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
To resolve some issues, it's important to also show session logs. By default, the library limits outputting unnecessary logs and instead shows visually pleasing "spinner" logs. Unfortunately, if something goes wrong then these logs are usually not enough to identify a root cause of a problem and a potential fix. In these cases advanced logs are required within the issue template.
Here's how to turn on advanced logging in your sessions.
CLI / Docker
Add the following flags to your start command:
Custom code [Config] / cli.config.json
Add the following values to your config:
Now you have a terminal full of extra useful context to identify the root cause of an issue.
Beta Was this translation helpful? Give feedback.
All reactions