Composefs --progress-fd bytes_total is broken

Open
#2,484 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
backend

Research direction

Start by tracing how the composefs backend emits progress-fd bytes and bytes_total, then compare that behavior with the ostree backend. Reproduce a parallel composefs layer download and verify that progress does not begin with 0 divided by 0 and that the reported byte information has parity with ostree output.

Written by the indexing model from the issue text.

Description

area/composefs triaged

Currently, for the ostree backend, we're able to track download progress by dividing bytes by bytes_total. This is useful for showing download progress in plymouth like so.

For composefs, it reports byte information before it even knows what it's downloading, meaning initially it's 0 bytes divided by 0 bytes_total. It also reports bytes separately for each layer being downloaded in parallel.

Composefs and ostree output should have parity with one another.

Dominant language
Rust
Stars
2.3k
Forks
230
Avg merge
2d 11h
Merged PRs (30d)
42

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bootc-dev/bootc

All issues in bootc-dev/bootc

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.