Unable to check existence for: lasso/global/history.json

[ahaneef29]

Hi,

Laravel Version ........................................................................................................................... 9.39.0 PHP Version ................................................................................................................................ 8.1.5 Composer Version ........................................................................................................................... 2.2.8 Environment ................................................................................................................................ local

I'm using Digital Ocean Space for uploading & Downloading compiled assets using Lasso. php artisan lasso:publish command working without any error. But when using lasso:pull on deployment script, it's throwing an error.

php artisan lasso:pull

🏁 Preparing to download assets from "digitalocean" filesystem. ⏳ Reading Bundle meta file... ⏳ Downloading bundle... ✅ Successfully downloaded bundle. ⏳ Creating backup... ✅ Backed up. ⏳ Updating assets...

League\Flysystem\UnableToCheckDirectoryExistence

Unable to check existence for: lasso/global/history.json

at vendor/league/flysystem/src/UnableToCheckExistence.php:19 15▕ } 16▕ 17▕ public static function forLocation(string $path, Throwable $exception = null): static 18▕ { ➜ 19▕ return new static("Unable to check existence for: {$path}", 0, $exception); 20▕ } 21▕ 22▕ public function operation(): string 23▕ {

  +41 vendor frames

42 artisan:37 Illuminate\Foundation\Console\Kernel::handle(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))

[ahaneef29]

Any workaround?

[Sammyjo20]

Hi, thanks for the message - apologies for the late reply - I will take a look likely Sunday for you.

[ajuchacko]

@ahaneef29 I'd like to help you with this, Unfortunately I am not able to get digital ocean spaces. If you'd like to get me one test credentials or we could chat about this, shoot me an email.

[danmatthews]

@Sammyjo20 - hey Sam, i've just hit this issue with Lasso + S3, i was able to work around it by manually creating the history.json file on my S3 bucket, but i'm assuming it's something that it's something that Lasso should be creating when uploading the assets?

UPDATE 3

Tested all the way back to thephpleague/flysystem-aws-s3-v3 v3.0.0 and it's still busted.

Also confirmed still happens without --use-commit flag.

UPDATE 2

Looks like it's an issue with Flysystem:

https://github.com/laravel/framework/issues/45639

https://github.com/thephpleague/flysystem-aws-s3-v3/commit/ea100348d497585687e4ad487bf150b0d766b46d

UPDATE 1 First run of php artisan lasso:publish --use-commit creates the development folder, but no history.json visible in my S3 bucket:

I can then confirm this in Transmit:

Running php artisan lasso:pull --use-commit gives the error:

Now i know i can manually fix this by creatinga JSON file manually, so I do it in tinkerwell, note the empty JSON body:

Storage::disk('s3_assets')->put('/socialsync/development/history.json', '{}');

Checking both Transmit and S3 console now shows history.json:

pull now works, and if you check the history file after running pull, it has content.

Versions:

Laravel Version ........................................................................................................................... 9.52.5
PHP Version ............................................................................................................................... 8.1.16
Composer Version ........................................................................................................................... 2.5.4

Lasso v3.1.0

[ajuchacko]

Hey @danmatthews, Can you test this PR on your app, where history.json is not empty on s3 also on a new app where no history.json exists, to make sure it works as expected.

thanks

[Sammyjo20]

Hey @danmatthews sorry for the delay on this issue! Are you still having this problem?