Project

General

Profile

Actions
Copy link

Bug #19897

open

FUSE should return a different error when attempting to create a file in a project

Added by Peter Amstutz over 1 year ago. Updated over 1 year ago.

Status:
New
Priority:
Normal
Assigned To:
Brett Smith
Category:
-
Target version:
2023-02-01 sprint
Start date:
Due date:
% Done:

0%

Estimated time:
(Total: 0.00 h)
Story points:
0.5

Description

You cannot create a bare file in a Project in the FUSE mount (only in Collections). If you try, you will get I/O error. This is disorienting because I/O error usually means something very bad happened. This should be something else like:

EPERM "Operation not permitted"
ENOSYS "Function not implemented"

Internally it is actually throwing NoImplementedError so catching that exception generally and turning it into ENOSYS would make sense. However the particular function that tries to create a file in a project could throw EPERM since it is more precise semantics.

From discussion: let's go with ENOTSUP "Operation not supported (POSIX.1-2001)."

Subtasks 1 (1 open — 0 closed)

Task #19950: ReviewNewPeter Amstutz

Actions
Actions
Copy link
 #1

Updated by Peter Amstutz over 1 year ago

  • Status changed from New to In Progress
Actions
Copy link
 #2

Updated by Peter Amstutz over 1 year ago

  • Description updated (diff)
Actions
Copy link
 #3

Updated by Peter Amstutz over 1 year ago

  • Status changed from In Progress to New
Actions
Copy link
 #4

Updated by Peter Amstutz over 1 year ago

  • Target version changed from 2023-02-01 sprint to To be groomed
Actions
Copy link
 #5

Updated by Peter Amstutz over 1 year ago

  • Assigned To set to Peter Amstutz
Actions
Copy link
 #6

Updated by Peter Amstutz over 1 year ago

  • Story points set to 0.5
Actions
Copy link
 #7

Updated by Peter Amstutz over 1 year ago

  • Assigned To deleted (Peter Amstutz)
  • Target version deleted (To be groomed)
  • Release set to 59
Actions
Copy link
 #8

Updated by Peter Amstutz over 1 year ago

  • Description updated (diff)
Actions
Copy link
 #9

Updated by Peter Amstutz over 1 year ago

  • Target version set to To be scheduled
Actions
Copy link
 #10

Updated by Brett Smith over 1 year ago

Before we put this on a sprint I feel like we should really pick which error we're going with.

Personally I would vote for ENOSYS since I think "the system doesn't support this" more accurately describes the problem than "you don't have permission to do this."

Actions
Copy link
 #11

Updated by Peter Amstutz over 1 year ago

  • Target version changed from To be scheduled to To be groomed
Actions
Copy link
 #12

Updated by Peter Amstutz over 1 year ago

  • Description updated (diff)
Actions
Copy link
 #13

Updated by Peter Amstutz over 1 year ago

  • Target version changed from To be groomed to To be scheduled
Actions
Copy link
 #14

Updated by Peter Amstutz over 1 year ago

  • Target version changed from To be scheduled to 2023-02-01 sprint
Actions
Copy link
 #15

Updated by Peter Amstutz over 1 year ago

  • Assigned To set to Brett Smith
Actions
Copy link
 #16

Updated by Peter Amstutz over 1 year ago 

      ENOTSUP         Operation not supported (POSIX.1-2001).

      EOPNOTSUPP      Operation not supported on socket (POSIX.1-2001).

                       (ENOTSUP and EOPNOTSUPP have the same value on Linux, but according to POSIX.1 these error values should be distinct.)

The thing that actually matters is what error message is printed by other programs, e.g. the shell, when you try to do something. Which probably comes from strerror(3)

Actions
Copy link

Also available in: Atom PDF