View Issue Details

IDProjectCategoryView StatusLast Update
0017676MMW 5Tagging / organizing (properties / auto-tools)public2021-05-23 21:46
Reporterrusty Assigned To 
PriorityurgentSeveritymajorReproducibilitysometimes
Status closedResolutionfixed 
Product Version5.0 
Target Version5.0.1Fixed in Version5.0.1 
Summary0017676: Auto-tag: graceful handling of unavailable server(s) so that 'file 1 of y processing' doesn't endlessly display
DescriptionIn build 2325 auto-tag is failing. The status is stuck on 'File 1 of x processing...' endlessly (for Martin and I), or in other cases advances at a rate of about 1 minute per track (for Peke).

For the attached log, 10 files from different albums (all in a single directory) were selected to be auto-tagged.

I'm not sure what the cause is, but it appears to be either a regression (perhaps due to the change in networking API), or not dealing well with connection problems (or both). Note that Peke indicated that the problem did not occur when he performed smoke tests on build 2325 several days ago, which would imply that the issue is related to some change at external services e.g. acoustid/musicbrainz.

btw, even if the cause in this case is not due to a connection problem, can you confirm that MM deals with the following scenarios:
a) failed connection or hitting limits on acoustID (e.g. 10s timeout) --> Status bar should show:
File x of y procssing: (<path>) Status: Fingerprining - Cannot create connection
In such a case, the lookup should proceed without the fingerprinting step

b) failed connection or hitting limits on MusicBrainz
Additional InformationTicket 973 984
TagsNo tags attached.
Fixed in build2406

Activities

rusty

2021-03-17 16:26

administrator   ~0062480

rusty

2021-03-17 21:46

administrator   ~0062491

Given that this was fixed at the server side, it's no longer critical.

Please push to 5.0.1 if non-trivial to implement.

petr

2021-03-18 11:54

developer   ~0062500

Adding such a visual feedback will be more complex update so i prefer to postpone to 5.0.1 because it's high regression risk.

petr

2021-05-19 19:40

developer   ~0063289

Fixed

peke

2021-05-23 21:46

developer   ~0063405

Verified 2407

Correct toast message appears.