Open jmontleon opened 3 years ago
Thank you @jmontleon for your report. We actually have that in place already in our receiver code. See here but as you can see here it is currently disabled. We disabled it at some point because it was creating a bottleneck but maybe it's OK to bring it back… @kelson42 ?
Ultimate goal is to stop relying on this. Zims will only be published by the CMS (to come) if satisfying defined criteria (zimcheck status from the zimfarm being a source).
@rgaudin @jmontleon The whole problem is known indeed and the plan is clear: we will develop (actually it should already be online if we would not be late!). The CMS should check the zimcheck
json output (available in next release) and based on threshold decided to let go through the quarantine or not.
This issue has been automatically marked as stale because it has not had recent activity. It will be now be reviewed manually. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be now be reviewed manually. Thank you for your contributions.
Problem
The task generated a garbage zim file. The test results in the log backs this up, as does the size of ~1MB instead of the typical ~45MB. If the test failed it probably shouldn't be published/made available.
If I follow the link https://download.kiwix.org/zim/archlinux_en_all_maxi.zim this is what I get though. I guess kiwix is probably just looking at the latest available copy.
Reproducing steps
This zim has broken occasionally before but it seems like a transient issue that usually gets resolved on the next build.