Skip to content

Fix the JSON conversion of operation errors - #284

Merged
5cript merged 1 commit into
mainfrom
fix/operation-error-descriptions
Oct 28, 2026
Merged

5cript merged 1 commit into
mainfrom
fix/operation-error-descriptions

Conversation

@5cript

@5cript 5cript commented Oct 28, 2026 •

Copy link
Copy Markdown
Owner

Operation errors now reach the frontend complete, and SFTP status codes above 8 get a readable name.

  • Converting an SFTP error with the InvalidPath wrapper error to JSON no longer throws; the value was missing from the WrapperErrors description.
  • OperationError::extraInfo is sent to the frontend, so operation cards show the detail the backend adds, such as "no free name is left".
  • sftpErrorToComprehensible names the status codes 9 to 31 of draft-ietf-secsh-filexfer-13 instead of reporting them as unknown.

…des 9 to 31

- Converting an SFTP error with the InvalidPath wrapper error to json threw, the value was missing from the description
- OperationError sent no extraInfo, so operation cards lost the detail the backend added to an error
- sftpErrorToComprehensible names the status codes of SFTP versions 4 to 6 (draft-ietf-secsh-filexfer-13)
@5cript 5cript changed the title Described InvalidPath and extraInfo for json and named SFTP status codes 9 to 31 Describe InvalidPath and extraInfo for json Oct 28, 2026
@5cript 5cript changed the title Describe InvalidPath and extraInfo for json Fix the JSON conversion of operation errors Oct 28, 2026
@5cript
5cript enabled auto-merge (rebase) October 28, 2026 21:33
@5cript
5cript merged commit 8420b1c into main Oct 28, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant