Nodejs v12 has been released / Toward Nodejs v10 usage

Merci ! Ça m’a l’air beaucoup mieux tout ça, la compil passe, le .deb fait une taille correcte par rapport aux versions précédentes et duniter se lance une fois installé. Que demande le peuple ?

3 J'aimes

Je viens de réussir une synchronisation avec Nodejs 10.
Ça a également bien démarré.

2019-05-11T13:55:57+02:00 - info: NodeJS version: v10.15.3
2019-05-11T13:55:57+02:00 - info: Node version: 1.7.18

Voyons voir sur le long terme.

J’ai :

(node:25362) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.

Et il s’est bizarement mis à écrire des blocs :
Sinon, ça va depuis, il se comporte normalement.

2019-05-11T13:50:36+02:00 - info: Generating proof-of-work with 0 leading zeros followed by [0-9A-F]... (CPU usage set to NaN%) for block#0 HgTTJL
2019-05-11T13:50:36+02:00 - info: Creating worker c#0#w#1
2019-05-11T13:50:36+02:00 - info: [online] worker c#0#w#0
2019-05-11T13:50:37+02:00 - info: ENGINE c#0#0 HAS FOUND A PROOF #CABAC5250522AB98A4345DEF5BAEB9AD8E8511FBBD27C084E864EEE39E426D6A
2019-05-11T13:50:37+02:00 - info: [done] worker c#0#w#0
2019-05-11T13:50:37+02:00 - info: ENGINE c#0#0 HAS FOUND A PROOF #CABAC5250522AB98A4345DEF5BAEB9AD8E8511FBBD27C084E864EEE39E426D6A
2019-05-11T13:50:37+02:00 - info: Done: #0, CABAC5250522AB98A4345DEF5BAEB9AD8E8511FBBD27C084E864EEE39E426D6A in 1.45s (~0 tests, ~0.00 tests/s, using 1 cores, CPU NaN%)
2019-05-11T13:50:37+02:00 - info: FOUND proof-of-work with 0 leading zeros followed by [0-9A-F]!
2019-05-11T13:50:37+02:00 - info: SIDE Block #0-CABAC525 added to the blockchain in 1 ms
2019-05-11T13:50:37+02:00 - info: Block resolution: 1 potential blocks for root block...
2019-05-11T13:50:37+02:00 - info: Block #0 added to the blockchain in 37 ms
2019-05-11T13:50:37+02:00 - info: Block resolution: 0 potential blocks after current#0...
2019-05-11T13:50:37+02:00 - info: Generating proof-of-work with 0 leading zeros followed by [0-9A-B]... (CPU usage set to NaN%) for block#1 HgTTJL
2019-05-11T13:50:37+02:00 - info: ENGINE c#0#0 HAS FOUND A PROOF #68C553BD7DB8DE607B7CB1E52166D1F7148B70128EDE0AF9EA417A8F2F5686A7
2019-05-11T13:50:37+02:00 - info: [done] worker c#0#w#0
2019-05-11T13:50:37+02:00 - info: ENGINE c#0#0 HAS FOUND A PROOF #68C553BD7DB8DE607B7CB1E52166D1F7148B70128EDE0AF9EA417A8F2F5686A7
2019-05-11T13:50:37+02:00 - info: Done: #1, 68C553BD7DB8DE607B7CB1E52166D1F7148B70128EDE0AF9EA417A8F2F5686A7 in 0.01s (~0 tests, ~0.00 tests/s, using 1 cores, CPU NaN%)
2019-05-11T13:50:37+02:00 - info: FOUND proof-of-work with 0 leading zeros followed by [0-9A-B]!
2019-05-11T13:50:37+02:00 - info: SIDE Block #1-68C553BD added to the blockchain in 1 ms
2019-05-11T13:50:37+02:00 - info: Block resolution: 1 potential blocks after current#0...
2019-05-11T13:50:37+02:00 - info: Block #1 added to the blockchain in 7 ms
2019-05-11T13:50:37+02:00 - info: Block resolution: 0 potential blocks after current#1...
2019-05-11T13:50:37+02:00 - info: Generating proof-of-work with 0 leading zeros followed by [0-9A]... (CPU usage set to NaN%) for block#2 HgTTJL
2019-05-11T13:50:37+02:00 - info: ENGINE c#0#0 HAS FOUND A PROOF #621B39CB48D6A23AE45D47DB743CC7FE202B7F4E0FD40CF5CDA98AF017AFA0CC
2019-05-11T13:50:37+02:00 - info: [done] worker c#0#w#0
2019-05-11T13:50:37+02:00 - info: ENGINE c#0#0 HAS FOUND A PROOF #621B39CB48D6A23AE45D47DB743CC7FE202B7F4E0FD40CF5CDA98AF017AFA0CC
2019-05-11T13:50:37+02:00 - info: Done: #2, 621B39CB48D6A23AE45D47DB743CC7FE202B7F4E0FD40CF5CDA98AF017AFA0CC in 0.01s (~0 tests, ~0.00 tests/s, using 1 cores, CPU NaN%)
2019-05-11T13:50:37+02:00 - info: FOUND proof-of-work with 0 leading zeros followed by [0-9A]!
2019-05-11T13:50:37+02:00 - info: SIDE Block #2-621B39CB added to the blockchain in 1 ms
2019-05-11T13:50:37+02:00 - info: Block resolution: 1 potential blocks after current#1...
2019-05-11T13:50:37+02:00 - info: Block #2 added to the blockchain in 2 ms
2019-05-11T13:50:37+02:00 - info: Block resolution: 0 potential blocks after current#2...
2019-05-11T13:50:37+02:00 - info: Generating proof-of-work with 0 leading zeros followed by [0-9A-C]... (CPU usage set to NaN%) for block#3 HgTTJL
2019-05-11T13:50:37+02:00 - info: ENGINE c#0#0 HAS FOUND A PROOF #01735F851F1EC1F99D7F246A7A7F8794ACE94F2F875C90F218A72813044834F2
2019-05-11T13:50:37+02:00 - info: [done] worker c#0#w#0
2019-05-11T13:50:37+02:00 - info: ENGINE c#0#0 HAS FOUND A PROOF #01735F851F1EC1F99D7F246A7A7F8794ACE94F2F875C90F218A72813044834F2
2019-05-11T13:50:37+02:00 - info: Done: #3, 01735F851F1EC1F99D7F246A7A7F8794ACE94F2F875C90F218A72813044834F2 in 0.03s (~1 tests, ~32.26 tests/s, using 1 cores, CPU NaN%)
2019-05-11T13:50:37+02:00 - info: FOUND proof-of-work with 0 leading zeros followed by [0-9A-C]!
2019-05-11T13:50:37+02:00 - info: SIDE Block #3-01735F85 added to the blockchain in 1 ms
2019-05-11T13:50:37+02:00 - info: Block resolution: 1 potential blocks after current#2...
2019-05-11T13:50:37+02:00 - info: Block #3 added to the blockchain in 6 ms
2019-05-11T13:50:37+02:00 - info: Block resolution: 0 potential blocks after current#3...
2019-05-11T13:50:37+02:00 - info: Generating proof-of-work with 0 leading zeros followed by [0-9A-C]... (CPU usage set to NaN%) for block#4 HgTTJL
2019-05-11T13:50:37+02:00 - info: ENGINE c#0#0 HAS FOUND A PROOF #210B3B2ABA628A61AA747F7A875277099BAE6165B84AE51BCE531664F1AEACE1
2019-05-11T13:50:37+02:00 - info: [done] worker c#0#w#0
2019-05-11T13:50:37+02:00 - info: ENGINE c#0#0 HAS FOUND A PROOF #210B3B2ABA628A61AA747F7A875277099BAE6165B84AE51BCE531664F1AEACE1
2019-05-11T13:50:37+02:00 - info: Done: #4, 210B3B2ABA628A61AA747F7A875277099BAE6165B84AE51BCE531664F1AEACE1 in 0.01s (~0 tests, ~0.00 tests/s, using 1 cores, CPU NaN%)
2019-05-11T13:50:37+02:00 - info: FOUND proof-of-work with 0 leading zeros followed by [0-9A-C]!
2019-05-11T13:50:37+02:00 - info: SIDE Block #4-210B3B2A added to the blockchain in 1 ms
2019-05-11T13:50:37+02:00 - info: Block resolution: 1 potential blocks after current#3...
2019-05-11T13:50:37+02:00 - info: Block #4 added to the blockchain in 3 ms
2019-05-11T13:50:37+02:00 - info: Block resolution: 0 potential blocks after current#4...
2019-05-11T13:50:37+02:00 - info: Generating proof-of-work with 0 leading zeros followed by [0-9A-C]... (CPU usage set to NaN%) for block#5 HgTTJL
2019-05-11T13:50:37+02:00 - info: ENGINE c#0#0 HAS FOUND A PROOF #40C9A581B85657CCC3ACB3068FD5C4475BCA4C22E91F6BD1F585A7FF0F092A8B
2019-05-11T13:50:37+02:00 - info: [done] worker c#0#w#0
2019-05-11T13:50:37+02:00 - info: ENGINE c#0#0 HAS FOUND A PROOF #40C9A581B85657CCC3ACB3068FD5C4475BCA4C22E91F6BD1F585A7FF0F092A8B
2019-05-11T13:50:37+02:00 - info: Done: #5, 40C9A581B85657CCC3ACB3068FD5C4475BCA4C22E91F6BD1F585A7FF0F092A8B in 0.01s (~0 tests, ~0.00 tests/s, using 1 cores, CPU NaN%)
2019-05-11T13:50:37+02:00 - info: FOUND proof-of-work with 0 leading zeros followed by [0-9A-C]!
2019-05-11T13:50:37+02:00 - info: SIDE Block #5-40C9A581 added to the blockchain in 0 ms
2019-05-11T13:50:37+02:00 - info: Block resolution: 1 potential blocks after current#4...
2019-05-11T13:50:37+02:00 - info: Block #5 added to the blockchain in 6 ms
2019-05-11T13:50:37+02:00 - info: Block resolution: 0 potential blocks after current#5...
2019-05-11T13:50:37+02:00 - info: Generating proof-of-work with 0 leading zeros followed by [0-9A-B]... (CPU usage set to NaN%) for block#6 HgTTJL
2019-05-11T13:50:37+02:00 - info: ENGINE c#0#0 HAS FOUND A PROOF #6FE0E716B0D3A08C6D548A9C86D0B8AE32C83528C0E4FCE74A3E0DBCDF9C5301
2019-05-11T13:50:37+02:00 - info: [done] worker c#0#w#0
2019-05-11T13:50:37+02:00 - info: ENGINE c#0#0 HAS FOUND A PROOF #6FE0E716B0D3A08C6D548A9C86D0B8AE32C83528C0E4FCE74A3E0DBCDF9C5301
2019-05-11T13:50:37+02:00 - info: Done: #6, 6FE0E716B0D3A08C6D548A9C86D0B8AE32C83528C0E4FCE74A3E0DBCDF9C5301 in 0.01s (~0 tests, ~0.00 tests/s, using 1 cores, CPU NaN%)
2019-05-11T13:50:37+02:00 - info: FOUND proof-of-work with 0 leading zeros followed by [0-9A-B]!
2019-05-11T13:50:37+02:00 - info: SIDE Block #6-6FE0E716 added to the blockchain in 0 ms
2019-05-11T13:50:37+02:00 - info: Block resolution: 1 potential blocks after current#5...
2019-05-11T13:50:37+02:00 - info: Block #6 added to the blockchain in 3 ms
2019-05-11T13:50:37+02:00 - info: Block resolution: 0 potential blocks after current#6...
2019-05-11T13:50:37+02:00 - info: Generating proof-of-work with 0 leading zeros followed by [0-9A-C]... (CPU usage set to NaN%) for block#7 HgTTJL
2019-05-11T13:50:37+02:00 - info: ENGINE c#0#0 HAS FOUND A PROOF #8B9D1C6BCF941D89CA2A8E2EC403B258075149060FDA85195672B91062BA1962
2019-05-11T13:50:37+02:00 - info: [done] worker c#0#w#0
2019-05-11T13:50:37+02:00 - info: ENGINE c#0#0 HAS FOUND A PROOF #8B9D1C6BCF941D89CA2A8E2EC403B258075149060FDA85195672B91062BA1962
2019-05-11T13:50:37+02:00 - info: Done: #7, 8B9D1C6BCF941D89CA2A8E2EC403B258075149060FDA85195672B91062BA1962 in 0.01s (~0 tests, ~0.00 tests/s, using 1 cores, CPU NaN%)
2019-05-11T13:50:37+02:00 - info: FOUND proof-of-work with 0 leading zeros followed by [0-9A-C]!
2019-05-11T13:50:37+02:00 - info: SIDE Block #7-8B9D1C6B added to the blockchain in 0 ms
2019-05-11T13:50:37+02:00 - info: Block resolution: 1 potential blocks after current#6...
2019-05-11T13:50:37+02:00 - info: Block #7 added to the blockchain in 6 ms
2019-05-11T13:50:37+02:00 - info: Block resolution: 0 potential blocks after current#7...
2019-05-11T13:50:37+02:00 - info: Generating proof-of-work with 0 leading zeros followed by [0-9A-B]... (CPU usage set to NaN%) for block#8 HgTTJL
2019-05-11T13:50:37+02:00 - info: ENGINE c#0#0 HAS FOUND A PROOF #748882F672238CFC86B94C42B1DE89A88CDAC40C8573B9B176DB0EAE78AF4D09
2019-05-11T13:50:37+02:00 - info: [done] worker c#0#w#0
2019-05-11T13:50:37+02:00 - info: ENGINE c#0#0 HAS FOUND A PROOF #748882F672238CFC86B94C42B1DE89A88CDAC40C8573B9B176DB0EAE78AF4D09
2019-05-11T13:50:37+02:00 - info: Done: #8, 748882F672238CFC86B94C42B1DE89A88CDAC40C8573B9B176DB0EAE78AF4D09 in 0.01s (~0 tests, ~0.00 tests/s, using 1 cores, CPU NaN%)
2019-05-11T13:50:37+02:00 - info: FOUND proof-of-work with 0 leading zeros followed by [0-9A-B]!
2019-05-11T13:50:37+02:00 - info: SIDE Block #8-748882F6 added to the blockchain in 0 ms
2019-05-11T13:50:37+02:00 - info: Block resolution: 1 potential blocks after current#7...
2019-05-11T13:50:38+02:00 - info: Block #8 added to the blockchain in 6 ms
2019-05-11T13:50:38+02:00 - info: Block resolution: 0 potential blocks after current#8...
2019-05-11T13:50:38+02:00 - info: Generating proof-of-work with 0 leading zeros followed by [0-9A-B]... (CPU usage set to NaN%) for block#9 HgTTJL
2019-05-11T13:50:38+02:00 - info: ENGINE c#0#0 HAS FOUND A PROOF #5C83BB161FC24783C44655CF546AAE1D025E8DAC4DB5D30464F4171D5A35430D
2019-05-11T13:50:38+02:00 - info: [done] worker c#0#w#0
2019-05-11T13:50:38+02:00 - info: ENGINE c#0#0 HAS FOUND A PROOF #5C83BB161FC24783C44655CF546AAE1D025E8DAC4DB5D30464F4171D5A35430D
2019-05-11T13:50:38+02:00 - info: Done: #9, 5C83BB161FC24783C44655CF546AAE1D025E8DAC4DB5D30464F4171D5A35430D in 0.03s (~1 tests, ~34.48 tests/s, using 1 cores, CPU NaN%)
2019-05-11T13:50:38+02:00 - info: FOUND proof-of-work with 0 leading zeros followed by [0-9A-B]!
2019-05-11T13:50:38+02:00 - info: SIDE Block #9-5C83BB16 added to the blockchain in 0 ms
2019-05-11T13:50:38+02:00 - info: Block resolution: 1 potential blocks after current#8...
2019-05-11T13:50:38+02:00 - info: Block #9 added to the blockchain in 3 ms
2019-05-11T13:50:38+02:00 - info: Block resolution: 0 potential blocks after current#9...
2019-05-11T13:50:38+02:00 - info: Generating proof-of-work with 0 leading zeros followed by [0-9A]... (CPU usage set to NaN%) for block#10 HgTTJL
2019-05-11T13:50:38+02:00 - info: ENGINE c#0#0 HAS FOUND A PROOF #6E407270235F9B655DBF8734A1835C29E201138CC3C68FEC9F5925BCF87C265E
2019-05-11T13:50:38+02:00 - info: [done] worker c#0#w#0
2019-05-11T13:50:38+02:00 - info: ENGINE c#0#0 HAS FOUND A PROOF #6E407270235F9B655DBF8734A1835C29E201138CC3C68FEC9F5925BCF87C265E
2019-05-11T13:50:38+02:00 - info: Done: #10, 6E407270235F9B655DBF8734A1835C29E201138CC3C68FEC9F5925BCF87C265E in 0.03s (~1 tests, ~40.00 tests/s, using 1 cores, CPU NaN%)
2019-05-11T13:50:38+02:00 - info: FOUND proof-of-work with 0 leading zeros followed by [0-9A]!
2019-05-11T13:50:38+02:00 - info: SIDE Block #10-6E407270 added to the blockchain in 5 ms
2019-05-11T13:50:38+02:00 - info: Block resolution: 1 potential blocks after current#9...
2019-05-11T13:50:38+02:00 - info: Block #10 added to the blockchain in 3 ms
2019-05-11T13:50:38+02:00 - info: Block resolution: 0 potential blocks after current#10...
2019-05-11T13:50:38+02:00 - info: Generating proof-of-work with 0 leading zeros followed by [0-9A]... (CPU usage set to NaN%) for block#11 HgTTJL
2019-05-11T13:50:38+02:00 - info: ENGINE c#0#0 HAS FOUND A PROOF #7DE6F0A1221EB69E6236FBB3B5FB6E6BC26D16536E209EF3F6F9B6B5D489BD49
2019-05-11T13:50:38+02:00 - info: [done] worker c#0#w#0
2019-05-11T13:50:38+02:00 - info: ENGINE c#0#0 HAS FOUND A PROOF #7DE6F0A1221EB69E6236FBB3B5FB6E6BC26D16536E209EF3F6F9B6B5D489BD49
2019-05-11T13:50:38+02:00 - info: Done: #11, 7DE6F0A1221EB69E6236FBB3B5FB6E6BC26D16536E209EF3F6F9B6B5D489BD49 in 0.01s (~0 tests, ~0.00 tests/s, using 1 cores, CPU NaN%)

Je lance les tests pour voir.
Voici le résultat des tests :

  716 passing (4m)
  2 failing

  1) WS2P docpool pulling should be able to pull the docpool:
     Error: the string "WS2P connection timeout" was thrown, throw an Error :)
      at Runner.fail (/mnt/444cee27-ed7e-476e-b2e9-c3ad0d73938e/duniter/node_modules/mocha/lib/runner.js:233:11)
      at /mnt/444cee27-ed7e-476e-b2e9-c3ad0d73938e/duniter/node_modules/mocha/lib/runner.js:565:18
      at done (/mnt/444cee27-ed7e-476e-b2e9-c3ad0d73938e/duniter/node_modules/mocha/lib/runnable.js:295:5)
      at /mnt/444cee27-ed7e-476e-b2e9-c3ad0d73938e/duniter/node_modules/mocha/lib/runnable.js:359:11

  2) WS2P docpool pulling "after all" hook:
     TypeError: Cannot read property 'close' of undefined
      at Context.after (/mnt/444cee27-ed7e-476e-b2e9-c3ad0d73938e/duniter/test/integration/ws2p/ws2p_docpool.ts:64:19)
      at callFn (/mnt/444cee27-ed7e-476e-b2e9-c3ad0d73938e/duniter/node_modules/mocha/lib/runnable.js:348:21)
      at Hook.Runnable.run (/mnt/444cee27-ed7e-476e-b2e9-c3ad0d73938e/duniter/node_modules/mocha/lib/runnable.js:340:7)
      at next (/mnt/444cee27-ed7e-476e-b2e9-c3ad0d73938e/duniter/node_modules/mocha/lib/runner.js:309:10)
      at Immediate._onImmediate (/mnt/444cee27-ed7e-476e-b2e9-c3ad0d73938e/duniter/node_modules/mocha/lib/runner.js:339:5)
      at runCallback (timers.js:705:18)
      at tryOnImmediate (timers.js:676:5)
      at processImmediate (timers.js:658:5)



error Command failed with exit code 2.

Une affirmation qui paraît un peu rapide, vu les résultats sur le GitLab :

1 J'aime

Surement un problème de websocket rencontré localement.

Ok, trouvé, mon système viens avec une version plus à jour de nodejs-ws dont la compatibilité n’est pas maintenue avec la v1.

Étrange que ça n’utilise pas la version 1.1.5 présente dans node_modules.

Hop, j’ai passé mes nœuds de prod Ğ1 et Ğ1-test sous Nodejs v10 !
Je n’ai pas rencontré le problème ci-dessus.

À noter qu’il faut resynchroniser son nœud pour que /blockchain/with/* fonctionne de nouveau.

1 J'aime

Depuis, mes nœuds tournent bien avec Node.js v10 !