After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 740276 - clarify fetch progress is not known until all metadata is fetched
clarify fetch progress is not known until all metadata is fetched
Status: RESOLVED FIXED
Product: ostree
Classification: Infrastructure
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: OSTree maintainer(s)
OSTree maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-11-17 16:54 UTC by Colin Walters
Modified: 2015-01-13 01:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Colin Walters 2014-11-17 16:54:44 UTC 
1) Change the text to Retrieving Metadata Objects: XXX/(Estimating)
2) Prioritize metadata fetches to achieve known status earlier
3) Include sufficient metadata in commit objects to more precisely estimate completion (see the object sizes work)
Comment 2 Colin Walters 2015-01-07 15:26:45 UTC 
for #2, I think it'd be a matter of changing the current GQueue in OstreeFetcher into a priority queue, where we have exactly two priorities (metadata, content).  Then once all metadata is fetched, we know exactly how many objects are left.
Comment 3 Matthew Barnes 2015-01-12 12:53:50 UTC 
Split this into a series of micro-commits, so I'm going the pull-request route.

https://github.com/GNOME/ostree/pull/40
Comment 4 Matthew Barnes 2015-01-12 16:29:33 UTC 
Pull request merged.  Does that fully cover what you had in mind or is there still outstanding work for item (3)?
Comment 5 Colin Walters 2015-01-13 01:08:05 UTC 
I think so for this bug.  Any real improvements here I think are probably best addressed via deltas.  Then the loose fetch becomes a developer only case.