Skip to content
New issue

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

Error when running Blast with Invoker #61

Open
nathangross opened this issue Nov 1, 2022 · 1 comment
Open

Error when running Blast with Invoker #61

nathangross opened this issue Nov 1, 2022 · 1 comment

Comments

@nathangross
Copy link

I just tried out Beyond Code's Invoker app and upon launch, I got an error that seemed to be related to this package. So I figured I'd cross-post this issue here too:

beyondcode/invoker-community#318


OS: darwin
Invoker Version: 2.10.0
Laravel Version: 9.34.0
Local project: true
PHP Binary: /opt/homebrew/bin/php
Route: /project/placeholder?project=local-jNgTuLwmLanmNUq8TaxKzz

Error:

ErrorException 

  mkdir(): Read-only file system

  at /Users/nathan/Code/pigworks/vendor/laravel/framework/src/Illuminate/Filesystem/Filesystem.php:631
    627▕         if ($force) {
    628▕             return @mkdir($path, $mode, $recursive);
    629▕         }
    630▕ 
  ➜ 631▕         return mkdir($path, $mode, $recursive);
    632▕     }
    633▕ 
    634▕     /**
    635▕      * Move a directory.

      �[2m+3 vendor frames �[22m
  4   [internal]:0
      A17\Blast\DataStore::__construct(Object(Illuminate\Filesystem\Filesystem))

      �[2m+19 vendor frames �[22m
  24  phar:/Applications/Invoker.app/Contents/Resources/invoker.phar/src/Actions/GetCommandsAction.php:22
      Illuminate\Foundation\Console\Kernel::all()

This happens as soon as I open this particular project. I'm not sure what directory is failing to create. Does Invoker create a file or directory per project?

As soon as I removed this package, the project opens in Invoker without error. I wasn't really sure how to parse this. Any ideas what might be going on?

@mrtimbrook
Copy link
Collaborator

Blast needs to be able to write to the filesystem. It stores the story files generated from the blade files, the parsed tailwind config used for the auto-documentation, etc in the vendor/area17/blast directory.

I'll add a better test and error message for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants