withfig / fig

Public issue tracker for Fig.
https://fig.io
MIT License
2.04k stars 63 forks source link

Could not run simple workflow #2078

Closed mskora-dtiq closed 2 years ago

mskora-dtiq commented 2 years ago

Checks

Operating system

macOS 12.5.1 (21G83)

Expected behaviour

I would like to run my custom created workflow.

Actual behaviour

After creating new workflow from boilerplate, echo "Hello World!", everything seems fine, but once I apply some changes, add something, like,echo "Hello World! Michal" I got this error:

❱ fig run foobar
error: Could not execute @mskora/foobar since it requires features not available in this version of Fig.
Please update to the latest version by running fig update and try again.```

### Steps to reproduce

1. Create new workflow.
2. Run it.
3. Make some changes.
4. Run it again.

### Environment

```yaml
fig-details:
  - 2.7.9
hardware-info:
  - model: 
  - model-id: 
  - chip-id: Apple M1 Max
  - cores: 10
  - mem: 64.00 GB
os-info:
  - macOS 12.5.1 (21G83)
environment:
  - shell: /bin/zsh
  - terminal: iterm
  - cwd: /Users/michal/workspace/dtiq/DTiQ360CvatDevOps
  - exe-path: /opt/homebrew/bin/fig
  - install-method: brew
  - env-vars:
    - FIGTERM_SESSION_ID: e1363d85-6f64-411f-91f8-ed76ec02571f
    - FIG_HOSTNAME: MacBook-Pro-Michal.local
    - FIG_TERM: 2.7.9
    - PATH: /Users/michal/.bun/bin:/usr/local/sbin:/usr/local/opt/ncurses/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/Users/michal/opt/homebrew/bin:/Users/michal/.yarn/bin:/Users/michal/.asdf/shims:/opt/homebrew/opt/asdf/libexec/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin:/Users/michal/.fig/bin:/Users/michal/.local/bin:/Users/michal/Library/Application Support/JetBrains/Toolbox/scripts:/opt/homebrew/opt/fzf/bin:/Users/michal/.local/bin:/Users/michal/.dotnet/tools
    - SHELL: /bin/zsh
    - TERM: xterm-256color
    - FIG_PID: 48546
    - FIG_PARENT: e1363d85-6f64-411f-91f8-ed76ec02571f
    - FIG_SET_PARENT: e1363d85-6f64-411f-91f8-ed76ec02571f
grant0417 commented 2 years ago

I believe this was a bug last week, it was resolved and should no longer occur, just run the workflow again and it should work!