We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fig doctor
fig restart
Debian
User was not authenticated to fig. Logs should not been spammed for wrong token or refresh token not set.
Logs are written about 30 times / sec for the same error resulting in high disk usage (50 go) for daemon.logs)
Daemon installed from desktop app I believe, (client did it) Don't authenticate to fig using any "fig login"
fig-details: - 2.15.0 hardware-info: - model: - model-id: - chip-id: AMD EPYC 9354P 32-Core Processor - cores: 4 - mem: 15.64 GB os-info: - kernel: 5.10.0-27-cloud-amd64 - distro: "Debian GNU/Linux" - distro-version: "11 (bullseye)" environment: - shell: /usr/bin/bash - terminal: <unknown> - cwd: /var/log - exe-path: /usr/bin/fig - install-method: unknown - env-vars: - SHELL: /bin/bash - FIG_SET_PARENT_CHECK: 1 - FIGTERM_SESSION_ID: 98ee96aa-eb27-4bf8-84c6-7f561fe0c407 - XDG_SESSION_TYPE: tty - FIG_TERM: 2.15.0 - TERM: xterm-256color - FIG_PID: 1397774 - PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/root/.local/bin:/root/.fig/bin
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Checks
fig doctor
in the affected terminal sessionfig restart
and replicated the issue againOperating system
Debian
Expected behaviour
User was not authenticated to fig.
Logs should not been spammed for wrong token or refresh token not set.
Actual behaviour
Logs are written about 30 times / sec for the same error resulting in high disk usage (50 go) for daemon.logs)
Steps to reproduce
Daemon installed from desktop app I believe, (client did it)
Don't authenticate to fig using any "fig login"
Environment
The text was updated successfully, but these errors were encountered: