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

VirtualBox filesystem bug causing exceptions #385

Closed
bilogic opened this issue Feb 15, 2022 · 2 comments
Closed

VirtualBox filesystem bug causing exceptions #385

bilogic opened this issue Feb 15, 2022 · 2 comments

Comments

@bilogic
Copy link

bilogic commented Feb 15, 2022

Hi,

I believe I'm running into this issue again (composer/composer#9627), this time with laravel-zero. Basically, there seems to be a race condition in the VirtualBox file system.

To be clear, this is not a bug with Laravel-zero, however, adding the code to handle this issue will be greatly appreciated. Hope a PR for this will be accepted.

Below is the output I'm getting when facing the issue


                Building process


 Build version? [1.0.0]:
 >

   1. Moving application to production mode: ✔
   2. Compile into a single file: ✔


   ErrorException

  rename(/example/example.phar,/example/builds/example): No such file or directory

  at vendor/illuminate/filesystem/Filesystem.php:307
    303▕      * @return bool
    304▕      */
    305▕     public function move($path, $target)
    306▕     {
  ➜ 307▕         return rename($path, $target);
    308▕     }
    309▕
    310▕     /**
    311▕      * Copy a file to a new location.

      +20 vendor frames
  21  example:37
      LaravelZero\Framework\Kernel::handle()
@bilogic
Copy link
Author

bilogic commented Feb 15, 2022

After some debugger, I don't think this is related to the filesystem issue.

I did a example build -v and got the following output... Any idea why?

? Dumping the Composer autoloader

    > '/usr/local/bin/composer' 'dump-autoload' '--classmap-authoritative' '--no-dev'

PHP Fatal error:  Uncaught Error: Call to undefined function get_debug_type() in phar:///media/sf_www/stage/example/vendor/laravel-zero/framework/bin/box/vendor/symfony/console/Application.php:528
Stack trace:
#0 phar:///media/sf_www/stage/example/vendor/laravel-zero/framework/bin/box/vendor/symfony/console/Application.php(521): _HumbugBox113887eee2b6\Symfony\Component\Console\Application->doActuallyRenderThrowable()
#1 phar:///media/sf_www/stage/example/vendor/laravel-zero/framework/bin/box/vendor/symfony/console/Application.php(496): _HumbugBox113887eee2b6\Symfony\Component\Console\Application->doRenderThrowable()
#2 phar:///media/sf_www/stage/example/vendor/laravel-zero/framework/bin/box/vendor/symfony/console/Application.php(86): _HumbugBox113887eee2b6\Symfony\Component\Console\Application->renderThrowable()
#3 phar:///media/sf_www/stage/example/vendor/laravel-zero/framework/bin/box/vendor/symfony/console/Application.php(106): _HumbugBox113887eee2b6\Symfony\Component\Console\Application->_HumbugBox113887eee2b6\Symfony\Component\Console\{ in phar:///media/sf_www/stage/example/vendor/laravel-zero/framework/bin/box/vendor/symfony/console/Application.php on line 528

@bilogic
Copy link
Author

bilogic commented Feb 15, 2022

Ok, found it, I added a scripts entry in composer.json, and it was the cause.

@bilogic bilogic closed this as completed Feb 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant