dvandal / cryptonote-nodejs-pool

Mining pool for all CryptoNote based coins using Cryptonight, Cryptonight Light and Cryptonight Heavy algorithms
GNU General Public License v2.0
365 stars 611 forks source link

haven-nodejs-wrapper error #603

Closed Cideg closed 3 years ago

Cideg commented 3 years ago

make: Entering directory '/root/test/node_modules//build' CXX(target) Release/obj.target/havennodejswrapper/src/main.o ../src/main.cc:8:10: fatal error: cryptonote_basic/cryptonote_basic.h: No such file or directory

include "cryptonote_basic/cryptonote_basic.h"

      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

compilation terminated. havennodejswrapper.target.mk:124: recipe for target 'Release/obj.target/havennodejswrapper/src/main.o' failed make: *** [Release/obj.target/havennodejswrapper/src/main.o] Error 1 make: Leaving directory '/root/test/node_modules/haven-nodejs-wrapper/build' gyp ERR! build error gyp ERR! stack Error: make failed with exit code: 2 gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:191:23) gyp ERR! stack at ChildProcess.emit (events.js:198:13) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12) gyp ERR! System Linux 4.15.0-115-generic gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" gyp ERR! cwd /root/test/node_modules/haven-nodejs-wrapper gyp ERR! node -v v10.22.1 gyp ERR! node-gyp -v v5.1.0 gyp ERR! not ok npm WARN ws@7.3.1 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer dependencies yourself. npm WARN ws@7.3.1 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.

npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! haven-nodejs-wrapper@1.0.1 install: node-gyp rebuild npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the haven-nodejs-wrapper@1.0.1 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Swepool commented 3 years ago

Same issue but with 11.15

eheheeeeeee commented 3 years ago

yep, same issue with 11.15, tried to play with some haven wrappers forks, no luck :/

ghost commented 3 years ago

Maybe must people pay for it...? Is it a closed source...? Scientific studies are not the wisdom...! 💩

macroTbeast commented 3 years ago

@dvandal I am also getting this issue when running the npm update/install commands

Swepool commented 3 years ago

I removed the haven stuff and got it to work:)

Running two pools now

macroTbeast commented 3 years ago

I removed the haven stuff and got it to work:)

Running two pools now

I removed it and it installed but now it wont start.

2020-10-28 18:52:47 [master] Daemon died, spawning replacement... /root/pool/cryptonote-nodejs-pool/lib/utils.js:28 .toString()); ^

TypeError: Cannot read property 'toString' of undefined at Object. (/root/pool/cryptonote-nodejs-pool/lib/utils.js:28:2) at Module._compile (internal/modules/cjs/loader.js:816:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:827:10) at Module.load (internal/modules/cjs/loader.js:685:32) at Function.Module._load (internal/modules/cjs/loader.js:620:12) at Module.require (internal/modules/cjs/loader.js:723:19) at require (internal/modules/cjs/helpers.js:14:16) at Object. (/root/pool/cryptonote-nodejs-pool/lib/daemon.js:1:13) at Module._compile (internal/modules/cjs/loader.js:816:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:827:10) 2020-10-28 18:52:47 [master] Daemon died, spawning replacement... /root/pool/cryptonote-nodejs-pool/lib/utils.js:28 .toString());

Swepool commented 3 years ago

I removed the haven stuff and got it to work:) Running two pools now

I removed it and it installed but now it wont start.

2020-10-28 18:52:47 [master] Daemon died, spawning replacement... /root/pool/cryptonote-nodejs-pool/lib/utils.js:28 .toString()); ^

TypeError: Cannot read property 'toString' of undefined at Object. (/root/pool/cryptonote-nodejs-pool/lib/utils.js:28:2) at Module._compile (internal/modules/cjs/loader.js:816:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:827:10) at Module.load (internal/modules/cjs/loader.js:685:32) at Function.Module._load (internal/modules/cjs/loader.js:620:12) at Module.require (internal/modules/cjs/loader.js:723:19) at require (internal/modules/cjs/helpers.js:14:16) at Object. (/root/pool/cryptonote-nodejs-pool/lib/daemon.js:1:13) at Module._compile (internal/modules/cjs/loader.js:816:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:827:10) 2020-10-28 18:52:47 [master] Daemon died, spawning replacement... /root/pool/cryptonote-nodejs-pool/lib/utils.js:28 .toString());

Here https://github.com/Imlulle/cryptonote-nodejs-pool

macroTbeast commented 3 years ago

I tried to clone that, run npm update and then start it node init.js

I am getting the same error as before

2020-10-29 09:22:39 [master] Daemon died, spawning replacement... /root/cryptonote-nodejs-pool/lib/utils.js:28 .toString()); TypeError: Cannot read property 'toString' of undefined

I am on ubuntu 16.04 with node 11

git clone https://github.com/Imlulle/cryptonote-nodejs-pool.git pool cd pool

npm update node init.js

Swepool commented 3 years ago

Try rebuild?

I'm on Ubuntu 18.04

fm407 commented 3 years ago

is there a fix for this? removing "haven stuff" isnt really a fix

cryptomaxsun commented 3 years ago
compilation terminated.
havennodejswrapper.target.mk:122: recipe for target 'Release/obj.target/havennodejswrapper/src/main.o' failed
make: *** [Release/obj.target/havennodejswrapper/src/main.o] Error 1
make: Leaving directory '/home/max/p2/pool/node_modules/haven-nodejs-wrapper/build'
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/root/.nvm/versions/node/v11.15.0/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack     at ChildProcess.emit (events.js:193:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:255:12)
gyp ERR! System Linux 4.4.0-142-generic
gyp ERR! command "/root/.nvm/versions/node/v11.15.0/bin/node" "/root/.nvm/versions/node/v11.15.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/max/p2/pool/node_modules/haven-nodejs-wrapper
gyp ERR! node -v v11.15.0
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok 
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! haven-nodejs-wrapper@1.0.1 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the haven-nodejs-wrapper@1.0.1 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Nothing helped, how can this be fixed?

fm407 commented 3 years ago

Resolved here https://github.com/dvandal/cryptonote-nodejs-pool/issues/612

fabgat commented 3 years ago

Thanks, I solved just with:

"includeHeight": true,

into config.json

Now I receive the height.

:)

Cheers

Il giorno ven 1 gen 2021 alle ore 21:34 BerghemHack < notifications@github.com> ha scritto:

Try

"algo": null, "coin": null,

Or

Go to https://xmrig com/wizard

Inviato da ProtonMail mobile

-------- Messaggio originale -------- On 1 Gen 2021, 19:19, fabgat ha scritto:

Hi, I am on ubuntu 16.04 with node 11 and I'm using https://github.com/Imlulle/cryptonote-nodejs-pool.git

Monero is updated and wallet cli refreshed.

Using xmrig 6.7.0: "algo": "cn-heavy/xhv", "coin": "monero",

I always receive: new job from xxx.xxx.xxx.xxx diff 500054 algo rx/0 height 0

Where I'm wrong?

Thanks

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/dvandal/cryptonote-nodejs-pool/issues/603#issuecomment-753379228, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGKATTEX5XLQ2OLCVPR4HTLSXYWWNANCNFSM4SEIPERA .

-- .:Fabrizio Gatti:.

fabgat commented 3 years ago

This is the default configuration, isn't it? This has: "includeHeight": false,

with false, it does not send height to miners.

Il giorno sab 2 gen 2021 alle ore 16:29 BerghemHack < notifications@github.com> ha scritto:

Try this:


{ "poolHost": "YOUR POOL ADDRESS",

"coin": "monero", "symbol": "XMR", "coinUnits": 1000000000000, "coinDecimalPlaces": 4, "coinDifficultyTarget": 120, "blockchainExplorer": "https://xmrchain.net/block/{id}", "transactionExplorer": "https://xmrchain.net/tx/{id}", "daemonType": "default", "cnAlgorithm": "randomx", "cnVariant": 0, "cnBlobType": 0, "includeHeight": false, "isRandomX": true,

"logging": { "files": { "level": "info", "directory": "logs", "flushInterval": 5 }, "console": { "level": "info", "colors": true } }, "childPools": null, "poolServer": { "enabled": true, "mergedMining": false, "clusterForks": "auto", "poolAddress": "YOUR WALLET ADDRESS", "intAddressPrefix": 19, "blockRefreshInterval": 1000, "minerTimeout": 900, "sslCert": "./cert.pem", "sslKey": "./privkey.pem", "sslCA": "./chain.pem", "ports": [ { "port": 3333, "difficulty": 5000, "desc": "Low end hardware" }, { "port": 4444, "difficulty": 15000, "desc": "Mid range hardware" }, { "port": 5555, "difficulty": 25000, "desc": "High end hardware" }, { "port": 7777, "difficulty": 500000, "desc": "Cloud-mining / NiceHash" }, { "port": 8888, "difficulty": 25000, "desc": "Hidden port", "hidden": true }, { "port": 9999, "difficulty": 20000, "desc": "SSL connection", "ssl": false } ], "varDiff": { "minDiff": 100, "maxDiff": 100000000, "targetTime": 120, "retargetTime": 60, "variancePercent": 30, "maxJump": 100 }, "paymentId": { "addressSeparator": ".", "validation": false, "validations": ["1,16", "64"], "ban": true }, "fixedDiff": { "enabled": true, "addressSeparator": "." }, "shareTrust": { "enabled": true, "min": 10, "stepDown": 3, "threshold": 10, "penalty": 30 }, "banning": { "enabled": true, "time": 600, "invalidPercent": 25, "checkThreshold": 30 }, "slushMining": { "enabled": false, "weight": 300, "blockTime": 60, "lastBlockCheckRate": 1 } },

"payments": { "enabled": true, "interval": 1800, "maxAddresses": 50, "mixin": 7, "priority": 0, "transferFee": 14000000000, "dynamicTransferFee": true, "minerPayFee": true, "minPayment": 1000000000000, "maxPayment": null, "maxTransactionAmount": 0, "denomination": 100000000000 },

"blockUnlocker": { "enabled": true, "interval": 30, "depth": 60, "poolFee": 0.8, "devDonation": 0.0, "networkFee": 0.0 },

"api": { "enabled": true, "hashrateWindow": 600, "updateInterval": 5, "bindIp": "0.0.0.0", "port": 8117, "blocks": 30, "payments": 30, "password": "YOUR_PASSWORD", "ssl": false, "sslPort": 8119, "sslCert": "./cert.pem", "sslKey": "./privkey.pem", "sslCA": "./chain.pem", "trustProxyIP": true },

"daemon": { "host": "127.0.0.1", "port": 18081 },

"wallet": { "host": "127.0.0.1", "port": 18083 },

"redis": { "host": "127.0.0.1", "port": 6379, "auth": null, "db": 0, "cleanupInterval": 15 },

"notifications": { "emailTemplate": "email_templates/default.txt", "emailSubject": { "emailAdded": "Your email was registered", "workerConnected": "Worker %WORKER_NAME% connected", "workerTimeout": "Worker %WORKER_NAME% stopped hashing", "workerBanned": "Worker %WORKER_NAME% banned", "blockFound": "Block %HEIGHT% found !", "blockUnlocked": "Block %HEIGHT% unlocked !", "blockOrphaned": "Block %HEIGHT% orphaned !", "payment": "We sent you a payment !" }, "emailMessage": { "emailAdded": "Your email has been registered to receive pool notifications.", "workerConnected": "Your worker %WORKER_NAME% for address %MINER% is now connected from ip %IP%.", "workerTimeout": "Your worker %WORKER_NAME% for address %MINER% has stopped submitting hashes on %LAST_HASH%.", "workerBanned": "Your worker %WORKERNAME% for address %MINER% has been banned.", "blockFound": "Block found at height %HEIGHT% by miner %MINER% on %TIME%. Waiting maturity.", "blockUnlocked": "Block mined at height %HEIGHT% with %REWARD% and %EFFORT% effort on %TIME%.", "blockOrphaned": "Block orphaned at height %HEIGHT% :(", "payment": "A payment of %AMOUNT% has been sent to %ADDRESS% wallet." }, "telegramMessage": { "workerConnected": "Your worker %WORKERNAME% for address %MINER% is now connected from ip %IP%.", "workerTimeout": "Your worker _%WORKERNAME% for address %MINER% has stopped submitting hashes on _%LASTHASH%.", "workerBanned": "Your worker _%WORKERNAME% for address %MINER% has been banned.", "blockFound": "Block found at height %HEIGHT% by miner %MINER%! Waiting maturity.", "blockUnlocked": "Block mined at height %HEIGHT% with %REWARD% and %EFFORT% effort on %TIME%.", "blockOrphaned": "Block orphaned at height %HEIGHT% :(", "payment": "A payment of %AMOUNT% has been sent." } },

"email": { "enabled": false, "fromAddress": "your@email.com", "transport": "sendmail", "sendmail": { "path": "/usr/sbin/sendmail" }, "smtp": { "host": "smtp.example.com", "port": 587, "secure": false, "auth": { "user": "username", "pass": "password" }, "tls": { "rejectUnauthorized": false } }, "mailgun": { "key": "your-private-key", "domain": "mg.yourdomain" } },

"telegram": { "enabled": false, "botName": "", "token": "", "channel": "", "channelStats": { "enabled": false, "interval": 30 }, "botCommands": { "stats": "/stats", "report": "/report", "notify": "/notify", "blocks": "/blocks" } },

"monitoring": { "daemon": { "checkInterval": 60, "rpcMethod": "getblockcount" }, "wallet": { "checkInterval": 60, "rpcMethod": "getbalance" } },

"prices": { "source": "cryptonator", "currency": "USD" },

"charts": { "pool": { "hashrate": { "enabled": true, "updateInterval": 60, "stepInterval": 1800, "maximumPeriod": 86400 }, "miners": { "enabled": true, "updateInterval": 60, "stepInterval": 1800, "maximumPeriod": 86400 }, "workers": { "enabled": true, "updateInterval": 60, "stepInterval": 1800, "maximumPeriod": 86400 }, "difficulty": { "enabled": true, "updateInterval": 1800, "stepInterval": 10800, "maximumPeriod": 604800 }, "price": { "enabled": true, "updateInterval": 1800, "stepInterval": 10800, "maximumPeriod": 604800 }, "profit": { "enabled": true, "updateInterval": 1800, "stepInterval": 10800, "maximumPeriod": 604800 } }, "user": { "hashrate": { "enabled": true, "updateInterval": 180, "stepInterval": 1800, "maximumPeriod": 86400 }, "worker_hashrate": { "enabled": true, "updateInterval": 60, "stepInterval": 60, "maximumPeriod": 86400 }, "payments": { "enabled": true } }, "blocks": { "enabled": true, "days": 30 } } }


Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ Il sabato 2 gennaio 2021 13:14, fabgat notifications@github.com ha scritto:

Thanks, I solved just with:

"includeHeight": true,

into config.json

Now I receive the height.

:)

Cheers

Il giorno ven 1 gen 2021 alle ore 21:34 BerghemHack < notifications@github.com> ha scritto:

Try

"algo": null, "coin": null,

Or

Go to https://xmrig com/wizard

Inviato da ProtonMail mobile

-------- Messaggio originale -------- On 1 Gen 2021, 19:19, fabgat ha scritto:

Hi, I am on ubuntu 16.04 with node 11 and I'm using https://github.com/Imlulle/cryptonote-nodejs-pool.git

Monero is updated and wallet cli refreshed.

Using xmrig 6.7.0: "algo": "cn-heavy/xhv", "coin": "monero",

I always receive: new job from xxx.xxx.xxx.xxx diff 500054 algo rx/0 height 0

Where I'm wrong?

Thanks

— You are receiving this because you commented. Reply to this email directly, [view it on GitHub](

https://github.com/dvandal/cryptonote-nodejs-pool/issues/603#issuecomment-753360317 ), or [unsubscribe](

https://github.com/notifications/unsubscribe-auth/AR2DWX22DJ7W6NREB6GXC5LSXYG27ANCNFSM4SEIPERA ).

— You are receiving this because you commented. Reply to this email directly, view it on GitHub < https://github.com/dvandal/cryptonote-nodejs-pool/issues/603#issuecomment-753379228 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AGKATTEX5XLQ2OLCVPR4HTLSXYWWNANCNFSM4SEIPERA

.

-- .:Fabrizio Gatti:.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/dvandal/cryptonote-nodejs-pool/issues/603#issuecomment-753486872, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGKATTDZ7HZWXQJK6L5FDWLSX43WNANCNFSM4SEIPERA .

-- .:Fabrizio Gatti:.

muscleman commented 3 years ago

@fabgat maybe you should make a pull request with your working config.json????

fabgat commented 3 years ago

Hi, as wrote before, I solved just with:

"includeHeight": true,

into config.json

Now I receive the height.

Thanks

Il giorno dom 3 gen 2021 alle ore 01:01 muscleman notifications@github.com ha scritto:

@fabgat https://github.com/fabgat maybe you should make a pull request with your working config.json????

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/dvandal/cryptonote-nodejs-pool/issues/603#issuecomment-753545973, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGKATTGH35PO53MNY24BLMLSX6XUHANCNFSM4SEIPERA .

-- .:Fabrizio Gatti:.

fabgat commented 3 years ago

Now it seems to work fine. You can try it: https://moneropool.permitall.com/

Il giorno dom 3 gen 2021 alle ore 10:14 Fabrizio Gatti < fabrizio.gatti@gmail.com> ha scritto:

Hi, as wrote before, I solved just with:

"includeHeight": true,

into config.json

Now I receive the height.

Thanks

Il giorno dom 3 gen 2021 alle ore 01:01 muscleman < notifications@github.com> ha scritto:

@fabgat https://github.com/fabgat maybe you should make a pull request with your working config.json????

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/dvandal/cryptonote-nodejs-pool/issues/603#issuecomment-753545973, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGKATTGH35PO53MNY24BLMLSX6XUHANCNFSM4SEIPERA .

-- .:Fabrizio Gatti:.

-- .:Fabrizio Gatti:.

muscleman commented 3 years ago

you seem to be missing the point. if the existing config.json was incorrect for monero, why not submit a pull request so others can benefit from your findings?

fabgat commented 3 years ago

I don’t miss the point, because as told, I’ve just changed one parameter between false and true. Nothing else

Inviato da iPhone

Il giorno 3 gen 2021, alle ore 16:31, muscleman notifications@github.com ha scritto:

 you seem to be missing the point. if the existing config.json was incorrect for monero, why not submit a pull request so others can benefit from your findings?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

muscleman commented 3 years ago

so how does this help the next person that uses this software. do you think its fair to make someone search the pool issues, because your to lazy to submit a pull request to change the default config.json file.

fm407 commented 3 years ago

I don’t miss the point, because as told, I’ve just changed one parameter between false and true. Nothing else Inviato da iPhone Il giorno 3 gen 2021, alle ore 16:31, muscleman @.***> ha scritto:  you seem to be missing the point. if the existing config.json was incorrect for monero, why not submit a pull request so others can benefit from your findings? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

Charge him $200 for the new config 🤣

fabgat commented 3 years ago

I've just made a commit request. I'm not lazy, probably you are the most unfriendly person I ever met. Thanks for your work, but try to be more friendly.

Il giorno dom 3 gen 2021 alle ore 19:22 Francesco notifications@github.com ha scritto:

I don’t miss the point, because as told, I’ve just changed one parameter between false and true. Nothing else Inviato da iPhone … <#m-6714242241174341128> Il giorno 3 gen 2021, alle ore 16:31, muscleman @.***> ha scritto:  you seem to be missing the point. if the existing config.json was incorrect for monero, why not submit a pull request so others can benefit from your findings? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

Charge him $200 for the new config 🤣

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/dvandal/cryptonote-nodejs-pool/issues/603#issuecomment-753657030, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGKATTGO6XR45XTNFBSQ7RDSYCYXLANCNFSM4SEIPERA .

-- .:Fabrizio Gatti:.

fm407 commented 3 years ago

I've just made a commit request. I'm not lazy, probably you are the most unfriendly person I ever met. Thanks for your work, but try to be more friendly. Il giorno dom 3 gen 2021 alle ore 19:22 Francesco notifications@github.com ha scritto: I don’t miss the point, because as told, I’ve just changed one parameter between false and true. Nothing else Inviato da iPhone … <#m-6714242241174341128> Il giorno 3 gen 2021, alle ore 16:31, muscleman @.***> ha scritto:  you seem to be missing the point. if the existing config.json was incorrect for monero, why not submit a pull request so others can benefit from your findings? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Charge him $200 for the new config 🤣 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#603 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGKATTGO6XR45XTNFBSQ7RDSYCYXLANCNFSM4SEIPERA . -- .:Fabrizio Gatti:.

@fabgat Don't you worry, as we say in Italy, that is just "l'asino che chiama cornuto il bue" :)

muscleman commented 3 years ago

Yep.. I'm being harsh. With good reason though. You want free working software. Well it requires community input.

Get Outlook for Androidhttps://aka.ms/ghei36


From: Francesco notifications@github.com Sent: Sunday, January 3, 2021 12:35:04 PM To: dvandal/cryptonote-nodejs-pool cryptonote-nodejs-pool@noreply.github.com Cc: muscleman musclesonvacation@hotmail.com; Comment comment@noreply.github.com Subject: Re: [dvandal/cryptonote-nodejs-pool] haven-nodejs-wrapper error (#603)

I've just made a commit request. I'm not lazy, probably you are the most unfriendly person I ever met. Thanks for your work, but try to be more friendly. Il giorno dom 3 gen 2021 alle ore 19:22 Francesco notifications@github.commailto:notifications@github.com ha scritto: … I don’t miss the point, because as told, I’ve just changed one parameter between false and true. Nothing else Inviato da iPhone … <#m-6714242241174341128> Il giorno 3 gen 2021, alle ore 16:31, muscleman @.***> ha scritto:  you seem to be missing the point. if the existing config.json was incorrect for monero, why not submit a pull request so others can benefit from your findings? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Charge him $200 for the new config 🤣 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#603 (comment)https://github.com/dvandal/cryptonote-nodejs-pool/issues/603#issuecomment-753657030>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGKATTGO6XR45XTNFBSQ7RDSYCYXLANCNFSM4SEIPERA . -- .:Fabrizio Gatti:.

@fabgathttps://github.com/fabgat Don't you worry, as we say in Italy, that is just "l'asino che chiama cornuto il bue" :)

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/dvandal/cryptonote-nodejs-pool/issues/603#issuecomment-753658555, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABDK6E4RFTMIMUIYSQYDUHDSYC2FRANCNFSM4SEIPERA.

fabgat commented 3 years ago

Same target can be reached in many different ways.

Il giorno dom 3 gen 2021 alle ore 19:50 muscleman notifications@github.com ha scritto:

Yep.. I'm being harsh. With good reason though. You want free working software. Well it requires community input.

Get Outlook for Androidhttps://aka.ms/ghei36


From: Francesco notifications@github.com Sent: Sunday, January 3, 2021 12:35:04 PM To: dvandal/cryptonote-nodejs-pool < cryptonote-nodejs-pool@noreply.github.com> Cc: muscleman musclesonvacation@hotmail.com; Comment < comment@noreply.github.com> Subject: Re: [dvandal/cryptonote-nodejs-pool] haven-nodejs-wrapper error (#603)

I've just made a commit request. I'm not lazy, probably you are the most unfriendly person I ever met. Thanks for your work, but try to be more friendly. Il giorno dom 3 gen 2021 alle ore 19:22 Francesco notifications@github.commailto:notifications@github.com ha scritto: … I don’t miss the point, because as told, I’ve just changed one parameter between false and true. Nothing else Inviato da iPhone … <#m-6714242241174341128> Il giorno 3 gen 2021, alle ore 16:31, muscleman @.***> ha scritto:  you seem to be missing the point. if the existing config.json was incorrect for monero, why not submit a pull request so others can benefit from your findings? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Charge him $200 for the new config 🤣 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#603 (comment)< https://github.com/dvandal/cryptonote-nodejs-pool/issues/603#issuecomment-753657030>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGKATTGO6XR45XTNFBSQ7RDSYCYXLANCNFSM4SEIPERA . -- .:Fabrizio Gatti:.

@fabgathttps://github.com/fabgat Don't you worry, as we say in Italy, that is just "l'asino che chiama cornuto il bue" :)

— You are receiving this because you commented. Reply to this email directly, view it on GitHub< https://github.com/dvandal/cryptonote-nodejs-pool/issues/603#issuecomment-753658555>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/ABDK6E4RFTMIMUIYSQYDUHDSYC2FRANCNFSM4SEIPERA>.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/dvandal/cryptonote-nodejs-pool/issues/603#issuecomment-753660420, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGKATTCPXFQTQYPOLLQSA23SYC4AHANCNFSM4SEIPERA .

-- .:Fabrizio Gatti:.

xmrminers commented 3 years ago

i have submitted a PR reverting the haven stuff, should be fully functional now