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
Trying to process more than one image: crypto HashUpdate fail #10
Comments
Alright, I just looked at MapSlicer.js. I removed line 15 ( |
Thank you for fixing it. It is a slightly weird way to create PR though the code landed in master and is published as 1.0.3 @ npm. Again thanks and best regards! |
No problem! It makes me happy to know I could finally help with something, even it being so simple, for the first time in my life. Sorry for the noobish questions, but I don't understand what you mean by "It is a slightly weird way to create PR". What is PR? Are you referring to the way it was before of after I changed the code? Best regards! |
A "PR" or "Pull Request" is the-github-way™ to collaborate. Github has a guide that explains it here |
Oh, of course. I thought it had something to do with mapslice itself. I should have thought a little more before asking. Thanks! Now, I promise this is the last question, but I really want to learn the right way to do this stuff. What was weird about the way I created the PR? I've already read the guide before, but I'm not sure. Is it because I opened an issue and linked it to the PR? If so, I apologize. I only thought about trying to fix the bug myself after opening the issue. |
I'm trying to implement a page with express and multer where uploaded images should be immediately processed by mapslice. It works fine with the first image, but fails for the second one, whether I try to upload both at the same time or sequentially:
In nodejs/node-v0.x-archive#1415 it is stated that "crypto instances are not reusable", so I guess the script is trying to reuse the same object for the second image. Is this a bug in mapslice or am I doing something wrong?
The following code reproduces the problem, although it's not exactly what I'm using:
The text was updated successfully, but these errors were encountered: