-
-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do not copy entry in 'W' namespace when recreating zim file. #452
Conversation
Codecov ReportAttention: Patch coverage is
❌ Your patch status has failed because the patch coverage (0.00%) is below the target coverage (80.00%). You can increase the patch coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## main #452 +/- ##
=======================================
Coverage 27.70% 27.70%
=======================================
Files 26 26
Lines 2534 2534
Branches 1363 1363
=======================================
Hits 702 702
Misses 1325 1325
Partials 507 507 ☔ View full report in Codecov by Sentry. |
Generated files are using the commands: ``` mkdir data/nov0 scripts/create_test_zimfiles --all src/small_zimfile_data/ data/nov0 zimrecreate data/withns/wikipedia_en_climate_change_mini_2024-06.zim data/nov0/wikipedia_en_climate_change_mini_2024-06.zim zimrecreate data/withns/wikibooks_be_all_nopic_2017-02.zim data/nov0/wikibooks_be_all_nopic_2017-02.zim zimsplit data/nov0/wikibooks_be_all_nopic_2017-02.zim --prefix data/nov0/wikibooks_be_all_nopic_2017-02_splitted.zim --size 51200 ``` `zimwriterfs`, `zimrecreate`, `zimsplit` are localy build using - commit b5127fc9 of libzim (commit in PR openzim/libzim#949) - commit 482a6708 of zimtools (head of PR openzim/zim-tools#452) Using non released version of libzim was necessary as we need test files to test the PR and without the PR merged, we cannot release a libzim generating such kind of files.
482a670
to
677cb58
Compare
Entries in 'W' namespace are automatically created by libzim creator. This is especially important as we will "lost" the namespace and so we would add the entry as an user entry.
677cb58
to
90a44a5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Frankly, I don't remember what purpose the W
namespace serves, however I can't raise any objections against its addition to the list of other internal namespaces.
Generated files are using the commands: ``` mkdir data/noTitleListingV0 scripts/create_test_zimfiles --all src/small_zimfile_data/ data/noTitleListingV0 zimrecreate data/withns/wikipedia_en_climate_change_mini_2024-06.zim data/noTitleListingV0/wikipedia_en_climate_change_mini_2024-06.zim zimrecreate data/withns/wikibooks_be_all_nopic_2017-02.zim data/noTitleListingV0/wikibooks_be_all_nopic_2017-02.zim zimsplit data/noTitleListingV0/wikibooks_be_all_nopic_2017-02.zim --prefix data/noTitleListingV0/wikibooks_be_all_nopic_2017-02_splitted.zim --size 51200 ``` `zimwriterfs`, `zimrecreate`, `zimsplit` are localy build using - commit b5127fc9 of libzim (commit in PR openzim/libzim#949) - commit 482a6708 of zimtools (head of PR openzim/zim-tools#452) Using non released version of libzim was necessary as we need test files to test the PR and without the PR merged, we cannot release a libzim generating such kind of files.
Entries in 'W' namespace are automatically created by libzim creator. This is especially important as we will "lost" the namespace and so we would add the entry as an user entry.