Project

General

Profile

Actions
Copy link

Bug #5896

open

[FUSE] Ensure all I/O errors properly distinguish "not found" and other API errors

Added by Brett Smith over 9 years ago. Updated over 3 years ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
FUSE
Target version:
-
Start date:
05/04/2015
Due date:
% Done:

0%

Estimated time:
Story points:
-

Description

A user is trying to work with a collection so large that, as of now, the API server can't return it—nginx returns a 504 timeout to the client. They tried to enter this collection's by_id subdirectory. FUSE reported "No such file or directory," but that's not actually true. The Collection does exist; arv-mount just couldn't fetch it. arv-mount should only return ENOENT when it gets an express 403 or 404 from the API server, and return a more generic I/O error for all other problems.

Actions
Copy link

Also available in: Atom PDF