-
Notifications
You must be signed in to change notification settings - Fork 81
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
Error: socket hang up #73
Comments
As a hacky workaround, I've broken it up into smaller sets of files on each task. That seems to solve the problem. function makeSubTasks(dir) {
grunt.file.expand(path.join(dir, '*')).forEach(function(dir) {
grunt.config('s3.' + dir + '.upload', uploadsOfDir(dir));
});
}
makeSubTasks(devRoot);
// it's kinda shitty to have to do this on grunt.initConfig(), because
// scanning all the files is slow and putting it there means that
// we will do it every time the user types `grunt`
function uploadsOfDir(dir) {
var files = grunt.file.expand(path.join(dir, '**', '*.*'));
return files.map(function(file) {
return {
src: file,
dest: path.sep + file.split(path.sep).slice(1).join(path.sep)
}
});
} |
Yeah, I've witnessed this too. I imagine it's just s3 being finicky. I've considered adding automatic retry to everything. |
Interesting. Is it possibly related to knox? s3 is supposed to be able to handle huge uploads, right? How can it be failing for < 500 files? Automatic retrying sounds reasonable. |
hmm, good point about knox. There is this issue: Automattic/knox#116 Have you tried |
I have been using that version of grunt-s3, and I'm still getting the same issue. |
I think that this problem exists for node |
I can repeat the problem with |
This issue is happening constantly for me as well with a large amount of files. |
+1 Had not seen this error before a month ago, now it's happening on every upload. |
+1 happens intermittently but frequently with |
I think (theoretically) this is due to not calling .end() on the knox calls. I'm playing with fixing this too. |
Any updates/fixes for this one? It's happening consistently on uploading to S3 for me. |
+1 same problem. only uploading a couple dozen files |
+1 this intermittent error happens with node |
+1 still happening |
+1 |
8 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
I sometimes get socket errors when trying to push content to s3:
Why does this happen? It seems to be non-deterministic.
The text was updated successfully, but these errors were encountered: