Open imarquart opened 10 months ago
fig doctor
fig restart
macOS 13.6.0 (22G120)
Fig is running.
Fig is not running at all. Fig doctor or Fig restart does not help
Fig doctor shows:
✘ Daemon diagnostics: Daemon websocket error Websock next error: Io(Os { code: 60, kind: TimedOut, message: "Operation timed out" })
My guess this is related to MacOS.
A separate issue #1822 has been files a long time ago - but it is a different issue. In this thread, several MacOS users recently reported this issue
fig-details: - 2.17.0 hardware-info: - model: - model-id: - chip-id: Apple M1 Pro - cores: 10 - mem: 32.00 GB os-info: - macOS 13.6.0 (22G120) environment: - shell: /bin/zsh - terminal: iterm - install-method: unknown - env-vars: - FIGTERM_SESSION_ID: 1279c603-c84a-4c9a-8720-eaf46ed49347 - FIG_SET_PARENT_CHECK: 1 - FIG_TERM: 2.17.0 - PATH: /opt/homebrew/opt/python@3/libexec/bin:/opt/homebrew/Caskroom/miniforge/base/condabin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/share/dotnet:/usr/local/munki:~/.dotnet/tools:/Library/Apple/usr/bin:/Library/Frameworks/Mono.framework/Versions/Current/Commands:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Users/ingomarquart/.cargo/bin:/Users/ingomarquart/.fig/bin:/Users/ingomarquart/.local/bin - SHELL: /bin/zsh - TERM: xterm-256color - __CFBundleIdentifier: com.googlecode.iterm2 - FIG_PID: 19058 - FIG_SET_PARENT: 1279c603-c84a-4c9a-8720-eaf46ed49347
Thanks for reporting @imarquart! I'm taking a look.
Checks
fig doctor
in the affected terminal sessionfig restart
and replicated the issue againOperating system
macOS 13.6.0 (22G120)
Expected behaviour
Fig is running.
Actual behaviour
Fig is not running at all. Fig doctor or Fig restart does not help
Fig doctor shows:
Steps to reproduce
My guess this is related to MacOS.
A separate issue #1822 has been files a long time ago - but it is a different issue. In this thread, several MacOS users recently reported this issue
Environment