File not found error surfaces local path instead of cloud path

I was loading a file from s3 and mistyped the file location. The error I got showed me the local tmp path, which was misleading. I think this should be the standard error you get when you try to do a cloud operation on a file that doesn't exist (something like "head object does not exist") or at least something that includes the cloud path instead of the local path.

DATA_DIR here is an S3Path.