Closed peterk closed 5 years ago
I can replicate this but Squidwarc still seems to be installed. For some reason, even updating the node-warc dependencies in a variety of places in the project to 0.3.2, 0de56e6628d1e0e8d18cb9e772ae7871bd8cd926 is still used. I am not sure if rebasing the submodule onto the node-warc latest master would remedy the issue but it would be worth a try.
EDIT: I am using the latest master. @N0taN3rd looks to have done some work on the next
branch recently, so that will require further testing.
The next
branch appears to pull node-warc 48cd9aad8d41e04e879377e83a4265d77c0cb06d. The edit on this branch do not report the error you reported @peterk and appears to complete the default crawl successfully. @N0taN3rd Would it be worth it to merge the next
branch into master to facilitate the fix on tools that depend on Squidwarc?
@peterk apologies for the delay in closing this issue officially but this issue should be fixed
Are you submitting a bug report or a feature request?
Bug report.
What is the current behavior?
Installing as per the instructions gives the following error in the
bootstrap.sh
script (relating to the node-war submodule):What is the expected behavior?
Installation proceeds normally.