-
Notifications
You must be signed in to change notification settings - Fork 40
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
ipfs-npm = registry-mirror.next() #43
Conversation
71ce99b
to
8348f69
Compare
* chore: upgrade dependencies * some cleanup and fixes * depend follow-registry fork for now * bring back tests * feat: use aegir * more options * fix: sequence parsing * refactor: replace ronin with yargs * feat: fail if no daemon is found * cleanup * feat: add registry ls * more commands and sha1 checks * fix downloading and registry settings, add sha check * fix: add missing dep * add debug info * improve error handling on writer * more debug logs * try to fix counter * try to fix the hangs * do sha check only after download to avoid reading the whole content again * fix err callback * fix: more error handling * correct host parsing * start increasing test coverage * more tests for verify * test: full coverage for verifier * moar tests * feat: update all dependencies
@dignifiedquire could you write a status update on what you found so far? |
Current findings: I came close twice to finish a full clone of the registry and ipfs blew up underneath me. The first time I hadn't flushed at all, the second time I did flush but still after the crash and restart |
feat: multi multi multi core
So with the latest multicore updates the cloning process was speed up nicely such that we have now a full clone inside IPFS. I just published it here: > ipfs name publish /ipfs/QmWtyxBrThZzZb5m9bdM9NN3WF6m4Vk85AukjzeQmhgnu6
Published to QmcmzV8FXsEfF5bQFf8vyJxhBZcV2SxTBApRcQbP5BQYGz: /ipfs/QmWtyxBrThZzZb5m9bdM9NN3WF6m4Vk85AukjzeQmhgnu6 The current repo size is about Pinning this root hash does destroy the daemon currently. |
|
@dignifiedquire what is the status on this? Last time I heard was that modules were not being properly stored anymore. I know you changed the cloner to a multicore one, might be because of that? |
The status is, I started to write a fully tested cloner here: https://github.com/dignifiedquire/registry-cloner but I will need some time to finish it. |
files mkdir
exhaustively ipfs/kubo#2918