Skip to content
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

Closed
wants to merge 15 commits into from
Closed

ipfs-npm = registry-mirror.next() #43

wants to merge 15 commits into from

Conversation

daviddias
Copy link
Member

@daviddias daviddias commented Jun 28, 2016

WIP

* 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
@daviddias
Copy link
Member Author

@dignifiedquire could you write a status update on what you found so far?

@dignifiedquire
Copy link
Member

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 files ls / was returning nothingness. I am currently waiting for @whyrusleeping to investigate what the failure was.

@dignifiedquire
Copy link
Member

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 1.7T but the actual size is probably lower, given that there are things from previous attempts in there.

Pinning this root hash does destroy the daemon currently.

@dignifiedquire
Copy link
Member

> ipfs files ls /npm-registry |wc -l
208677

@daviddias
Copy link
Member Author

@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?

@dignifiedquire
Copy link
Member

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.

@daviddias daviddias closed this Aug 15, 2018
@daviddias daviddias deleted the ipfs-npm branch August 15, 2018 09:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants