Repository navigation
v0.0.9: five stores, a platform registry, and CI
A worker crash could hang the whole run, --km-concurrency never reached the engine, and --no-title-dir let a sampler overwrite the volume it belongs to.
Fixed
- A crashed render worker hung the entire run. Both worker pools handed the next page to a worker that had already died, and
postMessageto a terminated worker is a silent no-op, so that page's promise never settled. Because the pool is closed in afinallythat runs after the downloads are awaited, one crash meant the CLI produced no output and never exited; aftersizecrashes every remaining page did the same. A dead worker is now dropped instead of reused, the pool refills itself, and anexitwithout amessagesettles the in-flight job rather than parking it forever. --km-concurrencydid nothing. It was declared, shown in--help, read by the driver and consumed by the k-manga adapter, butparseOptionsnever copied it into the config, so the documented default of 16 was really a hardcoded 8. The five per-store page counts are now followed from declaration through the parse to the store context in one test, so the next dead flag fails the suite rather than shipping.- A sampler overwrote its own volume under
--no-title-dir. A sampler and the full volume share one content id, so naming the folder after the id sent both to the same directory, where they overwrote each other page for page. CMOA, BookWalker and Kindle were affected; k-manga already carried the sample suffix. OnevolumeFolderhelper now decides this for every store. - A store-supplied title of
.or..wrote outside--out. The ebookjapan sanitiser stripped separators but not trailing dots, so the path resolved to the parent directory. It now uses the same sanitiser as every other store, which also removes a second, looser copy of the rule. - A re-run re-downloaded every descrambled ebookjapan page. The "is this page already on disk" check looked for WebP magic regardless of the format actually written, so with descrambling on -- where the pages are JPEG -- it never matched, and the whole volume was fetched and re-encoded again without
--force. - A page the descrambler could not rebuild was reported as a success. When the WASM glue used a canvas call outside the known set, the composition returned no plan and the raw scrambled bytes were written to a
.jpgpath and counted as downloaded. It is now a failed page. - One flaky probe aborted a whole CMOA scan. Probing deliberately rethrows anything that is not "this volume does not exist", so a single 429 or 500 while scanning killed the run even when every other URL was fine. A thrown probe now counts as a miss.
- A volume whose page uploads mostly failed was reported as a success. Upload failures were recorded but never affected
ok, so a 200-page volume with 199 bad pushes exited 0 with a.mokurobuilt from the one page that arrived. - A finalize stream that ended without a
doneframe counted as a success. The vendored BookWalker client throws on that input and the ebookjapan client did not, so the same truncated upload was judged two ways. --parallel Nran up to2Nvolumes. Each scheduling lane built its own pool ofparallelworkers, which contradicts both the help text and the number the summary reports. Both lanes now draw from one gate.<link rel="next">on a BookWalker series page is now resolved against the page URL; a relative href used to reach the fetcher as-is and fail to parse.- A series page fetch that answers non-200 now releases its socket instead of leaking one per page.
Changed
- The stores are a registry, not a set of branches. Each store owns a descriptor: the URLs it answers to, its progress label, the lane it runs on, how a title URL expands, its series walk, and its download.
run.jsdispatches through that registry, so adding a store is one descriptor rather than a new branch in the driver, a switch in the adapter, and an entry in three tables. - Folder naming, the volume marker and the shared scrapers moved out of the CMOA adapter, which every other adapter had been importing from.
- The ebookjapan viewer's WASM module and glue chunks are no longer vendored. They are ebookjapan's own proprietary build output and redistributing them under this project's MIT licence is not ours to do. They are now fetched from the store on first use and cached under
~/.bwdd-cli/ebookjapan-assets/(or$BWDD_EBOOKJAPAN_ASSETS);vendor/README.mdhas the refresh procedure.
Notes
- The tests that pinned the wiring by grepping the source have been replaced with behavioural ones. A check like "does
run.jscontain the textretries: config.retries" cannot tell a working build from a renamed variable, and it fails on any refactor; the same guarantee is now expressed by running the code.