-
Notifications
You must be signed in to change notification settings - Fork 2
set concurrency to 1 #3
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
base: master
Are you sure you want to change the base?
set concurrency to 1 #3
Conversation
avaer
left a comment
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.
This seems to regress the core parallel install functionality of this module. If we're going to add concurrency configuration, it should be taken in as an argument, not hard coded to 1. Otherwise a large part if the point of using archae in the first place is lost.
| /node_modules | ||
| /example/installed | ||
| /example/data | ||
| .idea/ No newline at end of file |
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.
This seemingly has nothing to do with setting concurrency to 1, so it shouldn't be in this PR right?
| const watchr = require('watchr'); | ||
| const cryptoutils = require('cryptoutils'); | ||
| const MultiMutex = require('multimutex'); | ||
| var bluebird = require('bluebird'); |
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.
Can we avoid this bluebird dependency? This seems a huge thing to use when the equivalent promise looper is probably 5 lines of code.
Also we have the multimutex module already included, which solves this exact concurrency problem.
| "repository": { | ||
| "type": "git", | ||
| "url": "https://github.com/modulesio/archae.git" | ||
| "url": "https://github.com/toomu/archae.git" |
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.
Was it deliberate to take over the repo in npm?
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.
I dont have permissions to write to https://github.com/modulesio/archae.git . Thought that implied I need to fork it to make the changes
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.
Yeah, but with this change the whole repo would point to toomu/archae from now on in npm. I'm really not sure what the point of that would be.
If this is for testing, it probably shouldn't be committed, or at least should not be part of a PR.
Though I'm not quite sure how this helps in testing in the first place...
| @@ -7,9 +7,10 @@ | |||
| }, | |||
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.
The npm version probably needs to change to please package manager and deployment systems.
No description provided.