owls @owls@yshi.org

I didn't think that was right, so I dug into it a bit more and realized Laravel was setting that stream_reads setting to false.

I dug a bit more and realized exactly what that TEMP resource actually did.

It's something from Guzzle, presumably done to stop you shooting your feet off: it writes the data to disk to stop you going OOM.

https://docs.guzzlephp.org/en/stable/psr7.html#body

The behaviour I was seeing, despite using readStream(), was that for large files, I would get null instead of the resource.

If I examined the resource with stream_get_meta_data(), I saw it was a TEMP resource. The PHP docs don't really explain that much.

For a while, I assumed it was fine.

Then I ran it locally with a large file and my queue driver se to sync and noticed ... it took about 4 seconds to just read the file.

The default in Flysystem's driver is true:

https://github.com/thephpleague/flysystem-aws-s3-v3/blob/3.x/AwsS3V3Adapter.php#L127

this threw me off a bit, since I was looking at the driver on S3 and assumed the defaults.

And I was getting *a* resource, just not one that behaved in the way I assumed it would.

One more gotcha in #Laravel when working with S3.

Storage has a readStream() method, which returns a stream resource instead of trying to jam a heckin' 2GB zip into memory.

The method will always return a resource -- but out of the box, it won't be a resource to stream from S3.

For whatever reason, Laravel defaults the setting stream_reads to false:

https://github.com/laravel/framework/blob/c0f3ee8c8779d5cfb6bb3c37c93b84672e67f236/src/Illuminate/Filesystem/FilesystemManager.php#L241

Got burned by the #Laravel Storage interface today.

I'm using an S3 filesystem. After a user uploaded a (potentially large) file to S3 and their form request is validated/saved, I was moving the file from a `tmp/` spot in S3 to a permanent spot.

This was done using ->move(), which I assumed would be an instantaneous rename operation.

Not so. S3 doesn't seem to *have* a move operation -- only copy -- and Flysystem uses that plus delete for "moving" objects.

An incredible ending to the first story arc.

I'm so glad for the wheelbarrow community.

"Silence kills in the wheelbarrow industry."

Sir Michael has a podcast and it is everything we deserve

https://shows.acast.com/sturdywheelbarrows/episodes/a-small-horse-or-a-large-wheelbarrow

ended up getting this mostly done on Friday!

It needs some polish but there's time enough for that on Monday, probably.

SO INSTEAD I WILL WRITE SOME USER GUIDES BECAUSE I HATE FUN