hermit-os/uhyve

Make error handling's fataility of open/read/write a parameter

Open

#1,245 opened on Feb 6, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (35 forks)auto 404
enhancementfeature/file systemfeature/securitygood first issuelow priority

Repository metrics

Stars
 (293 stars)
PR merge metrics
 (PR metrics pending)

Description

See also: https://github.com/hermit-os/uhyve/pull/1219#discussion_r2774467127

Making it a parameter of uhyve if it should crash on write errors or not might be the most sensible option.

Imo read [and porbably also open] should be handled the same way (if isolation is concerned), particularly in regards to permission errors.

Contributor guide

Research direction
Examine the referenced discussion to understand the proposed parameterization of error handling fatality, then trace the current implementation of open, read, and write functions to identify where crashes occur and how to add a configurable parameter.
Tech stack
rust
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitRust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65