-
Notifications
You must be signed in to change notification settings - Fork 71
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
Help debugging mcrypt issue - $@ 150,000 #310
Comments
when running with both node versions mcrypt leaves a message:
in your log i see a permission denied, so try |
So I think instead we're trying to remove mcrypt and use cryptian instead w1ntermute is taking on the testing I'm not sure if you're in the developing on sphinx tribe that's where the discussion is happening latest changes are made to this lib https://github.com/evanfeenstra/JSCryptor to use cryptian |
yes im in there, i see its mac specific so that is why i didnt get the error (i use linux) |
I think I figured it out, npm .npmrc file was giving an explicit path for node-gyp which was wrong. I don't remember ever editing that file tho ¯_(ツ)_/¯ |
Trying to upgrade a node cluster from nodejs 12 -> 16 and I'm getting the mcrypt error again
|
with this exact node version (v16.17.1, and npm 8.15.0 that comes with it) i dont get this error when running |
yea I think the cluster is using this docker file https://github.com/stakwork/sphinx-relay/blob/master/Dockerfile.lndrelay which means its using golang:1.13-alpine I'm trying to update the containers in place because taking them down and bringing them back up changes the container id which we need. I'm using this script to update each container
let me know if there's anything you recommend me trying |
this answer i found on SO looks similar (i think bycrypt is similar to mcrypt) with the same error in this answer the problem would be solved by updating/installing dependencies with the following commands:
could you try running these in the update script? |
just curious, what depends on the container id staying the same? |
I'm getting this error when trying to add those dependencies
We have them in a spreadsheet linking to who's using which node for customer support and etc, if we lost whos node is connected to which container it would be hard to debug if we needed to know which node is mapped to which user |
Fyi the clusters I've been updating previously didn't have any issue just when I got to these two it started to give me this mcrypt error |
I'm not sure if this might be the issue in the docker file it seems we're installing is the build when doing |
We really should not have |
why is mcrypt installed then? is it also a dependency for a different package? i dont see it directly required in package.json |
@Evanfeenstra I see that you have mcrypt taken out on your own fork but are we still using the default JSCryptor I don't see it pointing to your fork in the package.json *nvm it is your fork didn't realize you're fognet* |
So I was able to make progress by removing mcrypt dependency from this PR chesstrian/JSCryptor#23 and then publishing to npm Able to run npm install and I'm going to test that images are still working as intended to but will post what exactly I'm doing when I test |
@Evanfeenstra you said jscryptor was only being used for paid meme images, from what I tested so far I was able to send a paid meme image and have it paid and decrypted. Both on different versions of jscryptor I can try the other way around too |
hmm seems like the new changes on jscryptor is breaking the image tests which is not good |
closing this issue as I think its resolved now, haven't seen in a while |
[Description]
Our team is having trouble getting debugging an mcrypt dependency issue when running
npm install
[Complexity] (1,2,3,5,7)
2
[To Reproduce]
Download the repo
run
npm install
it should fail and you should see the error below
[Acceptance Criteria]
Given
We have the repo downloaded cleanWhen
we run the codenpm install
Then
it should install properly with no mcrypt errorThe text was updated successfully, but these errors were encountered: