-
Notifications
You must be signed in to change notification settings - Fork 4
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
It's possible a promise in unzipCUB3ds.js gets rejected without logging #90
Comments
True. One my machine, it's about one minute per exported tile. (I'll change the doc right away) |
I'm running this on a Core 2 Quad @ 2.66Ghz with Ubuntu 14.04 x64. |
Something went wrong. It's possible a promise got rejected and we don't log its error. |
We're finishing a major refactoring, so it's possible things don't all go well, sorry about that. |
aaah, much better :D The extraction is quite fast (2~10 seconds/tile) |
what is much better? |
No, I just stopped the process (which had been eating 100% of a core doing nothing) and relaunched it without changing anything. The extraction process worked as expected. |
Ok. Closing then... |
Probably not worth opening a new issue: there's a missing 'run' between npm and 'start-dev'. |
Fixed. Thanks :-) |
I jsut stumbled upon the same issue node unzipCUB... |
Related from @iOiurson (french): Grosso modo, le problème n’apparaît que lors de l’unzip de gros fichiers .zip. En fait, le pb est dans unzipInTmpDirectory. Je me rappelle on avait discuté de ça fin décembre parce que j’arrivais pas à unzip une tile avec textures. Du coup, l’évènement « finish » se lance, mais pas l’évènement « close », ou se trouve le def.resolve. Pour fixer les idées, sur bordeaux centre, il y a une cinquante de fichiers zip à extraire, mais seulement 40 se retrouvent dans le tmp. |
Maybe duplicate of #76 |
indeed but let's close this one and see it fixes the other one |
The README estimates the extraction time to 5 minutes on "normal hardware"but I've launched the extraction procedure more than an hour ago and it's still working at it!
My guess is that the operation takes around 5 minutes per exported tile (I have exported something like 25 tiles), the docs should probably mention that.
The text was updated successfully, but these errors were encountered: