duniter issueshttps://git.duniter.org/nodes/typescript/duniter/-/issues2020-04-30T22:26:39+02:00https://git.duniter.org/nodes/typescript/duniter/-/issues/1332Ğ1-test stuck because of the size of the block2020-04-30T22:26:39+02:00MoulĞ1-test stuck because of the size of the blockcf https://forum.duniter.org/t/monnaie-bloquee-trop-de-transactions-dans-le-bloc-a-generer/5648/4cf https://forum.duniter.org/t/monnaie-bloquee-trop-de-transactions-dans-le-bloc-a-generer/5648/41.7https://git.duniter.org/nodes/typescript/duniter/-/issues/1286Crashing 1.6.21 / Debian stretch2020-04-30T22:11:21+02:00SachaCrashing 1.6.21 / Debian stretchOn Debian Stretch up to date, I just installed new version of Duniter 1.6.21
It's completely instable for me, here is a crash log:
``
2018-03-04T16:44:55+01:00 - error: Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed
at ChildProces...On Debian Stretch up to date, I just installed new version of Duniter 1.6.21
It's completely instable for me, here is a crash log:
``
2018-03-04T16:44:55+01:00 - error: Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed
at ChildProcess.target.send (internal/child_process.js:606:16)
at Worker.send (internal/cluster/worker.js:40:28)
at PowWorker.sendCancel (/opt/duniter/app/modules/prover/lib/PowWorker.js:76:27)
at slaves.forEach.s (/opt/duniter/app/modules/prover/lib/powCluster.js:116:22)
at Array.forEach (<anonymous>)
at Master.cancelWorkersWork (/opt/duniter/app/modules/prover/lib/powCluster.js:115:21)
at Master.cancelWork (/opt/duniter/app/modules/prover/lib/powCluster.js:125:14)
at PowEngine.cancel (/opt/duniter/app/modules/prover/lib/engine.js:43:29)
at WorkerFarm.stopPoW (/opt/duniter/app/modules/prover/lib/blockProver.js:70:53)
at BlockProver.cancel (/opt/duniter/app/modules/prover/lib/blockProver.js:122:24)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:160:7)
``1.7https://git.duniter.org/nodes/typescript/duniter/-/issues/1262PoW: migrate to shared memory feature of Node 9/Node 102020-05-01T13:21:06+02:00Cédric MoreauPoW: migrate to shared memory feature of Node 9/Node 10As explained in #689, and after the problems with #1234 and #1256, this is definitely our target.
Yet, this requires us to migrate to Node 9 or Node 10.As explained in #689, and after the problems with #1234 and #1256, this is definitely our target.
Yet, this requires us to migrate to Node 9 or Node 10.1.9Cédric MoreauCédric Moreauhttps://git.duniter.org/nodes/typescript/duniter/-/issues/1234Calculates proofs for many different and past blocks2018-01-27T18:54:52+01:00ÉloïsCalculates proofs for many different and past blockssince Saturday 9 December 1 am, 1 of my member node continues to calculate even when it is excluded, it tries to calculate proofs for a lot of past blocks ! And yet it is well synchronized with the rest of the network on block 76348. It'...since Saturday 9 December 1 am, 1 of my member node continues to calculate even when it is excluded, it tries to calculate proofs for a lot of past blocks ! And yet it is well synchronized with the rest of the network on block 76348. It's so weird !
```
2017-12-09T20:48:08+01:00 - info: POST Peer 2t6NP6Fvvu#76319 to 10 peers
2017-12-09T20:48:09+01:00 - info: Matched 3 zeros 000674C083277FC715D9D280CE17D7F7E4BC267A5A7996278BFA7E693C13203A with Nonce = 30400000020777 for block#76219 by D9D2za
2017-12-09T20:48:10+01:00 - info: ✔ PEER DfjVNNn7
2017-12-09T20:48:10+01:00 - info: POST Peer DfjVNNn7JW#76319 to 10 peers
2017-12-09T20:48:11+01:00 - warn: Could not reach duniter.floth.fr:80, reason: Unexpected token < in JSON at position 0
2017-12-09T20:48:11+01:00 - warn: Could not reach duniter.floth.fr:80, reason: Unexpected token < in JSON at position 0
2017-12-09T20:48:13+01:00 - info: Matched 3 zeros 0001882C0BBAB887823AB8E119C8EE8E272DBB61AFA318744EAC81AC6B2C19C1 with Nonce = 30100000234023 for block#76161 by D9D2za
2017-12-09T20:48:14+01:00 - warn: httpCode=400, ucode=1005, message=Document has unkown fields or wrong line ending format
2017-12-09T20:48:14+01:00 - info: Matched 3 zeros 000C970400951C1D631C3EFFCD79FD50CEAE7BEA53EF3CAF0608D0B3D10A264A with Nonce = 30100000234469 for block#76161 by D9D2za
2017-12-09T20:48:15+01:00 - info: Matched 3 zeros 0004907B9F9B19D88BA57A66CB6E99B4766ED9346F2F6D0000C7AADD6CD53F87 with Nonce = 30100000234579 for block#76161 by D9D2za
2017-12-09T20:48:15+01:00 - info: POST Peer Be1eVp7etV#76348 to 1 peers
2017-12-09T20:48:15+01:00 - info: ✔ PEER Be1eVp7e
2017-12-09T20:48:15+01:00 - info: POST Peer Be1eVp7etV#76348 to 10 peers
2017-12-09T20:48:19+01:00 - info: Matched 3 zeros 000AD639C259CC049C4C023AFD676DC4DF5D922B34A68F2144D90286B21FEB80 with Nonce = 30300003184833 for block#76157 by D9D2za
2017-12-09T20:48:19+01:00 - info: Matched 3 zeros 0005272B7B42765F75581E21F4E8FF40B46BEA538839BC44806E044942796DEE with Nonce = 30200000433995 for block#76156 by D9D2za
2017-12-09T20:48:23+01:00 - info: Matched 3 zeros 000A117999F8B3C8F345CEA2D8613434BF54C0F29E9FE566D8928AB234F2DCC1 with Nonce = 30300003186040 for block#76157 by D9D2za
2017-12-09T20:48:25+01:00 - warn: ETIMEDOUT
2017-12-09T20:48:25+01:00 - warn: ETIMEDOUT
2017-12-09T20:48:25+01:00 - info: Peer Be1eVp7etVfA7cT6er6dcJ9d5KxGJVY2tzCGGCAz3yG unreachable: now considered as DOWN.
2017-12-09T20:48:27+01:00 - info: Matched 3 zeros 000C27F8E97A77DDD1B944ED66BC7C2C03F466331EBCEB00FBF1B63E43F228D3 with Nonce = 30100000233011 for block#76163 by D9D2za
2017-12-09T20:48:28+01:00 - info: ✔ PEER 9zCYjVtP
2017-12-09T20:48:28+01:00 - info: POST Peer 9zCYjVtPFz#76318 to 10 peers
2017-12-09T20:48:28+01:00 - warn: Could not reach 167.114.232.189:10901, reason: Unknown reference block of peer
2017-12-09T20:48:31+01:00 - warn: Could not reach duniter.floth.fr:80, reason: Unexpected token < in JSON at position 0
2017-12-09T20:48:33+01:00 - info: ✔ PEER 4fHMTFBM
2017-12-09T20:48:33+01:00 - info: POST Peer 4fHMTFBMo5#76319 to 10 peers
2017-12-09T20:48:33+01:00 - warn: Could not reach 167.114.232.189:10901, reason: Unknown reference block of peer
2017-12-09T20:48:35+01:00 - info: Matched 3 zeros 000BC1DDE8F8F8018A102305BA290A1E283E8323A7525332A72AE4C7FCBB0053 with Nonce = 30400000020803 for block#76258 by D9D2za
2017-12-09T20:48:42+01:00 - info: Matched 3 zeros 0008D3706435B5A3A5274ABE0725D1712C694A5C659554D7B1F7D6D467098CAB with Nonce = 30300003191112 for block#76157 by D9D2za
2017-12-09T20:48:42+01:00 - info: Pulling blocks from the network...
2017-12-09T20:48:42+01:00 - info: Peer 48SLtTLL3CxAXUcmbKwp2PUg1hUvEh2s5EwEpRh8RaoR unreachable: now considered as DOWN.
2017-12-09T20:48:43+01:00 - info: Matched 3 zeros 00074786ECF9FDD67D0639CFEC68AE440C2C1D2DB0DF38B4177413549F5EC8FF with Nonce = 30300003191385 for block#76157 by D9D2za
2017-12-09T20:48:45+01:00 - info: ✔ PEER 38MEAZN6
2017-12-09T20:48:45+01:00 - info: POST Peer 38MEAZN68P#76319 to 10 peers
2017-12-09T20:48:45+01:00 - warn: Could not reach 167.114.232.189:10901, reason: Unknown reference block of peer
2017-12-09T20:48:46+01:00 - info: Matched 3 zeros 000B5705E7B03D3539DFD9902B8B187023209B37E70D8AE6B19B25443BD15313 with Nonce = 30400000020851 for block#76268 by D9D2za
2017-12-09T20:48:48+01:00 - warn: Could not reach duniter.floth.fr:80, reason: Unexpected token < in JSON at position 0
2017-12-09T20:48:49+01:00 - info: Matched 3 zeros 000854D6EDED4FD7D9EACF4C7B85339952947498CDC809AA0F30ABA00B5D9EEE with Nonce = 30100000234230 for block#76165 by D9D2za
2017-12-09T20:48:52+01:00 - info: Peer Com8rJukCozHZyFao6AheSsfDQdPApxQRnz7QYFf64mm unreachable: now considered as DOWN.
2017-12-09T20:48:52+01:00 - info: Matched 3 zeros 0009358457521339F8751B7763E5CF0F708F6F153890347EEAC33604F4AFC0C0 with Nonce = 30400000020868 for block#76274 by D9D2za
2017-12-09T20:48:52+01:00 - info: Block resolution: 0 potential blocks after current#76348...
2017-12-09T20:48:52+01:00 - info: Will pull blocks from the network in 9 min 59 sec
2017-12-09T20:48:52+01:00 - info: Matched 3 zeros 0007B694F567EF68BD70C00016B1384E0BF99E2C779E68405812923A21532531 with Nonce = 30100000232648 for block#76166 by D9D2za
2017-12-09T20:48:53+01:00 - info: Matched 3 zeros 000D8D22CA7396CBABC0F99E32D458E4F6DB7FCF155DE03BBBEF5C63E27EEB41 with Nonce = 30400000020983 for block#76274 by D9D2za
2017-12-09T20:48:56+01:00 - info: WS2P D9D2zaJoWYWveii1JRYLVK3J4Z7ZH3QczoKrnQeiM6mx: new incoming connection from 127.0.0.1:44909!
2017-12-09T20:48:57+01:00 - info: WS2P: established incoming connection from D9D2zaJo 127.0.0.1:44909
2017-12-09T20:48:58+01:00 - info: Matched 3 zeros 00014A7533480CF628902112B4D497A7BA09EA2041DE4FA004438A03ED21B3E0 with Nonce = 30300003195709 for block#76157 by D9D2za
2017-12-09T20:49:00+01:00 - info: Matched 3 zeros 0009E6BFAD920EB08C9ED861143CDEA3604D3A644150B92971AE5EDC209F6E25 with Nonce = 30200000431807 for block#76159 by D9D2za
2017-12-09T20:49:01+01:00 - info: worker 31956 died with code null and signal SIGINT
```1.6.0Cédric MoreauCédric Moreauhttps://git.duniter.org/nodes/typescript/duniter/-/issues/1232powCluster.js process still alive after Duniter stop2020-05-01T13:22:06+02:00Cédric MoreaupowCluster.js process still alive after Duniter stop@nanocryk already raised this issue, and I could also observe this behavior with the powCluster.ts unit test with the following code:
```js
"use strict";
const co = require('co');
const should = require('should');
const PowEngine = req...@nanocryk already raised this issue, and I could also observe this behavior with the powCluster.ts unit test with the following code:
```js
"use strict";
const co = require('co');
const should = require('should');
const PowEngine = require('../../../app/modules/prover/lib/engine').PowEngine
const logger = require('../../../app/lib/logger').NewLogger()
describe('PoW Engine', () => {
it('should be configurable', () => co(function*(){
const e1 = new PowEngine({ nbCores: 1 }, logger);
(yield e1.setConf({ cpu: 0.2, prefix: '34' })).should.deepEqual({ cpu: 0.2, prefix: '34' });
const e2 = new PowEngine({ nbCores: 1 }, logger);
yield e1.shutDown()
}));
it('should be able to make a proof', () => co(function*(){
const e1 = new PowEngine({ nbCores: 1 }, logger);
const block = { number: 35 };
const zeros = 2;
const highMark = 'A';
const pair = {
pub: 'HgTTJLAQ5sqfknMq7yLPZbehtuLSsKj9CxWN7k8QvYJd',
sec: '51w4fEShBk1jCMauWu4mLpmDVfHksKmWcygpxriqCEZizbtERA6de4STKRkQBpxmMUwsKXRjSzuQ8ECwmqN1u2DP'
};
const forcedTime = 1;
const medianTimeBlocks = 20;
const avgGenTime = 5 * 60;
const proof = yield e1.prove({
newPoW: {
block,
zeros,
highMark,
pair,
forcedTime,
conf: {
medianTimeBlocks,
avgGenTime
}
}
}
)
proof.should.deepEqual({
pow: {
block: {
number: 35,
time: 1,
inner_hash: '51937F1192447A96537D10968689F4F48859E2DD6F8F9E8DE1006C9697C6C940',
nonce: 212,
hash: '009A52E6E2E4EA7DE950A2DA673114FA55B070EBE350D75FF0C62C6AAE9A37E5',
signature: 'bkmLGX7LNVkuOUMc+/HT6fXJajQtR5uk87fetIntMbGRZjychzu0whl5+AOOGlf+ilp/ara5UK6ppxyPcJIJAg=='
},
testsCount: 211,
pow: '009A52E6E2E4EA7DE950A2DA673114FA55B070EBE350D75FF0C62C6AAE9A37E5'
}
});
yield e1.shutDown()
}));
it.only('should be able to stop a proof', () => co(function*(){
const e1 = new PowEngine({ nbCores: 1 }, logger);
// yield e1.forceInit()
const block = { number: 26 };
const zeros = 10; // Requires hundreds of thousands of tries probably
const highMark = 'A';
const pair = {
pub: 'HgTTJLAQ5sqfknMq7yLPZbehtuLSsKj9CxWN7k8QvYJd',
sec: '51w4fEShBk1jCMauWu4mLpmDVfHksKmWcygpxriqCEZizbtERA6de4STKRkQBpxmMUwsKXRjSzuQ8ECwmqN1u2DP'
};
const forcedTime = 1;
const medianTimeBlocks = 20;
const avgGenTime = 5 * 60;
const proofPromise = e1.prove({
newPoW: {
block,
zeros,
highMark,
pair,
forcedTime,
conf: {
medianTimeBlocks,
avgGenTime
}
}
}
)
// yield new Promise((res) => setTimeout(res, 10))
// yield e1.cancel()
// const proof = yield proofPromise;
// should.not.exist(proof);
yield e1.shutDown()
}));
});
```
Then if I launch the test:
yarn tsc && node --trace-warnings node_modules/mocha/bin/_mocha --grep "PoW Engine"
I can see in my console that, even if the test is done, I still get messages of another process:
(node:19136) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): undefined
at emitWarning (internal/process/promises.js:63:21)
at emitPendingUnhandledRejections (internal/process/promises.js:95:11)
at runMicrotasksCallback (internal/process/next_tick.js:124:9)
at _combinedTickCallback (internal/process/next_tick.js:131:7)
at process._tickCallback (internal/process/next_tick.js:180:9)
(node:19136) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
at emitWarning (internal/process/promises.js:78:15)
at emitPendingUnhandledRejections (internal/process/promises.js:95:11)
at runMicrotasksCallback (internal/process/next_tick.js:124:9)
at _combinedTickCallback (internal/process/next_tick.js:131:7)
at process._tickCallback (internal/process/next_tick.js:180:9)
(node:19136) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): undefined
at emitWarning (internal/process/promises.js:63:21)
at emitPendingUnhandledRejections (internal/process/promises.js:95:11)
at runMicrotasksCallback (internal/process/next_tick.js:124:9)
at _combinedTickCallback (internal/process/next_tick.js:131:7)
at process._tickCallback (internal/process/next_tick.js:180:9)
(node:19136) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 3): undefined
at emitWarning (internal/process/promises.js:63:21)
at emitPendingUnhandledRejections (internal/process/promises.js:95:11)
at runMicrotasksCallback (internal/process/next_tick.js:124:9)
at _combinedTickCallback (internal/process/next_tick.js:131:7)
at process._tickCallback (internal/process/next_tick.js:180:9)
(node:19136) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 4): undefined
at emitWarning (internal/process/promises.js:63:21)
at emitPendingUnhandledRejections (internal/process/promises.js:95:11)
at runMicrotasksCallback (internal/process/next_tick.js:124:9)
at _combinedTickCallback (internal/process/next_tick.js:131:7)
at process._tickCallback (internal/process/next_tick.js:180:9)
This is a problem: the sub-processes launched by Duniter (here, the tests) should be killed along with Duniter being stopped.1.9Cédric MoreauCédric Moreauhttps://git.duniter.org/nodes/typescript/duniter/-/issues/1197CPU: Intel Atom should follow the same rule as ARM2018-01-12T18:24:22+01:00Cédric MoreauCPU: Intel Atom should follow the same rule as ARMSee: https://forum.duniter.org/t/duniter-powcluster-js-utilise-mes-8-coeurs-a-100/3608/17
Indeed, we divide the CPU value by 2 for ARM (empiric rule): https://github.com/duniter/duniter/blob/da85e4c3ba8e18a66b0c216335454473e1c205ae/ap...See: https://forum.duniter.org/t/duniter-powcluster-js-utilise-mes-8-coeurs-a-100/3608/17
Indeed, we divide the CPU value by 2 for ARM (empiric rule): https://github.com/duniter/duniter/blob/da85e4c3ba8e18a66b0c216335454473e1c205ae/app/modules/prover/lib/engine.ts#L38-L40
It seems Atom CPU suffer the same problem, and needs to have the CPU% value divided by 2 as well.1.7ÉloïsÉloïshttps://git.duniter.org/nodes/typescript/duniter/-/issues/1190duniter-prover includes revoked identites?2017-12-03T00:43:43+01:00Cédric Moreauduniter-prover includes revoked identites?https://forum.duniter.org/t/comportement-bizarre-de-duniter-1-6-11/3592https://forum.duniter.org/t/comportement-bizarre-de-duniter-1-6-11/35921.6.0ÉloïsÉloïshttps://git.duniter.org/nodes/typescript/duniter/-/issues/1126Gérer le préfixe de pair manuellement dans la configuration du nœud2018-01-27T07:27:43+01:00ÉloïsGérer le préfixe de pair manuellement dans la configuration du nœudBMA gère le préfixe de pair (premier caractère du nonce) afin d'éviter que deux nœuds partageant la même clé ne calculent la même preuve. WS2P ne le gère pas encore.BMA gère le préfixe de pair (premier caractère du nonce) afin d'éviter que deux nœuds partageant la même clé ne calculent la même preuve. WS2P ne le gère pas encore.1.6.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1123PoW handler stuck in an infinite loop2018-01-27T07:27:43+01:00Cédric MoreauPoW handler stuck in an infinite loopThe message:
> The proof-of-work generation was canceled: Document already under treatment
is displayed continuously in a kind of infinite loop.The message:
> The proof-of-work generation was canceled: Document already under treatment
is displayed continuously in a kind of infinite loop.1.6.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1119PoW children process do not close when duniter closes on armhf2018-01-27T07:27:41+01:00Cédric MoreauPoW children process do not close when duniter closes on armhfSee this topic (french): https://forum.duniter.org/t/beta-test-duniter-1-6-ws2p/3247/50See this topic (french): https://forum.duniter.org/t/beta-test-duniter-1-6-ws2p/3247/501.6.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1098PoW issue2018-01-27T07:27:43+01:00Cédric MoreauPoW issue*Created by: M5oul*
With version 1.5.9:
```bash
2017-09-15T12:02:16+02:00 - warn: The proof-of-work generation was canceled: [object Object]
2017-09-15T12:02:16+02:00 - warn: The proof-of-work generation was canceled: [object Object]...*Created by: M5oul*
With version 1.5.9:
```bash
2017-09-15T12:02:16+02:00 - warn: The proof-of-work generation was canceled: [object Object]
2017-09-15T12:02:16+02:00 - warn: The proof-of-work generation was canceled: [object Object]
2017-09-15T12:02:16+02:00 - warn: The proof-of-work generation was canceled: [object Object]
2017-09-15T12:02:16+02:00 - warn: The proof-of-work generation was canceled: [object Object]
2017-09-15T12:02:16+02:00 - warn: The proof-of-work generation was canceled: [object Object]
2017-09-15T12:02:16+02:00 - warn: The proof-of-work generation was canceled: [object Object]
2017-09-15T12:02:16+02:00 - warn: The proof-of-work generation was canceled: [object Object]
2017-09-15T12:02:16+02:00 - warn: The proof-of-work generation was canceled: [object Object]
2017-09-15T12:02:16+02:00 - warn: The proof-of-work generation was canceled: [object Object]
2017-09-15T12:02:17+02:00 - warn: The proof-of-work generation was canceled: [object Object]
2017-09-15T12:02:17+02:00 - warn: The proof-of-work generation was canceled: [object Object]
2017-09-15T12:02:18+02:00 - warn: The proof-of-work generation was canceled: [object Object]
2017-09-15T12:02:18+02:00 - warn: The proof-of-work generation was canceled: [object Object]
2017-09-15T12:02:18+02:00 - warn: The proof-of-work generation was canceled: [object Object]
2017-09-15T12:02:18+02:00 - warn: The proof-of-work generation was canceled: [object Object]
2017-09-15T12:02:18+02:00 - warn: The proof-of-work generation was canceled: [object Object]
2017-09-15T12:02:19+02:00 - warn: The proof-of-work generation was canceled: [object Object]
2017-09-15T12:02:19+02:00 - info: Node 8KTEFQ (167.114.232.189:8999) is UP!
2017-09-15T12:02:19+02:00 - warn: The proof-of-work generation was canceled: [object Object]
2017-09-15T12:02:19+02:00 - warn: The proof-of-work generation was canceled: [object Object]
2017-09-15T12:02:19+02:00 - warn: The proof-of-work generation was canceled: [object Object]
```1.6.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1096Duniter Desktop starts looping for no reason on "The proof-of-work generation...2018-01-27T07:27:43+01:00Cédric MoreauDuniter Desktop starts looping for no reason on "The proof-of-work generation was canceled: [object Object]"*Created by: jytou*
For the second time in 3 days, my duniter desktop started looping on the following in the logs:
```
2017-09-10T19:09:25+02:00 - warn: The proof-of-work generation was canceled: [object Object]
2017-09-10T19:09:25+...*Created by: jytou*
For the second time in 3 days, my duniter desktop started looping on the following in the logs:
```
2017-09-10T19:09:25+02:00 - warn: The proof-of-work generation was canceled: [object Object]
2017-09-10T19:09:25+02:00 - trace: PoW loops = 143672
2017-09-10T19:09:25+02:00 - warn: The proof-of-work generation was canceled: [object Object]
2017-09-10T19:09:25+02:00 - trace: PoW loops = 143673
2017-09-10T19:09:25+02:00 - warn: The proof-of-work generation was canceled: [object Object]
2017-09-10T19:09:25+02:00 - trace: PoW loops = 143674
2017-09-10T19:09:25+02:00 - warn: The proof-of-work generation was canceled: [object Object]
2017-09-10T19:09:25+02:00 - trace: PoW loops = 143675
```
It gets stuck on an old block and doesn't go forward or calculate anything anymore.
When I try to restart it, it gives the following error:
```
2017-09-10T19:13:14+02:00 - error: TypeError: Cannot read property 'transactions' of null
at DuniterBlockchain.<anonymous> (/opt/duniter/app/lib/blockchain/DuniterBlockchain.js:443:36)
at next (<anonymous>)
at /opt/duniter/app/lib/blockchain/DuniterBlockchain.js:7:71
at __awaiter (/opt/duniter/app/lib/blockchain/DuniterBlockchain.js:3:12)
at DuniterBlockchain.undoDeleteTransactions (/opt/duniter/app/lib/blockchain/DuniterBlockchain.js:442:16)
at DuniterBlockchain.<anonymous> (/opt/duniter/app/lib/blockchain/DuniterBlockchain.js:406:24)
at next (<anonymous>)
at fulfilled (/opt/duniter/app/lib/blockchain/DuniterBlockchain.js:4:58)
```
And when I restart it again, I get a core dumped. Last time, it did restart correctly and after a sync it was back on track. Not this time. It took 4 restarts until it got back on track and it is now on the latest block.1.6.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1094Raspberry PI 3 does not find blocks2018-01-27T07:27:41+01:00Cédric MoreauRaspberry PI 3 does not find blocksApparently, a Raspberry PI 3 no more find any acceptable block since Duniter 1.4. It used to work with 1.3.
The computation is well started, but with a difficulty of 5 zeros and 90% CPU configured it seems not enough to find even just...Apparently, a Raspberry PI 3 no more find any acceptable block since Duniter 1.4. It used to work with 1.3.
The computation is well started, but with a difficulty of 5 zeros and 90% CPU configured it seems not enough to find even just a block per day.
IMO, this is a software issue with Duniter being too much asking to the PI, proof excluded.1.6.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1089PoW is computing wrong block in G1Test2018-01-27T07:27:42+01:00Cédric MoreauPoW is computing wrong block in G1TestA lot of fork block are present in the nodes, which makes them compute another block than HEAD+1 because this HEAD is being changed during fork resolution.
We need a semaphore on this.A lot of fork block are present in the nodes, which makes them compute another block than HEAD+1 because this HEAD is being changed during fork resolution.
We need a semaphore on this.1.5.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1030written.json is not a function2018-01-27T07:27:43+01:00Cédric Moreauwritten.json is not a function*Created by: M5oul*
```bash
2017-07-11T14:51:11+02:00 - info: Generating proof-of-work with 4 leading zeros followed by [0-4]... (CPU usage set to 90%) for block#34361 GfKERH
2017-07-11T14:51:11+02:00 - info: Stop proof-of-work worker...*Created by: M5oul*
```bash
2017-07-11T14:51:11+02:00 - info: Generating proof-of-work with 4 leading zeros followed by [0-4]... (CPU usage set to 90%) for block#34361 GfKERH
2017-07-11T14:51:11+02:00 - info: Stop proof-of-work worker #1
2017-07-11T14:51:11+02:00 - info: Stop proof-of-work worker #2
2017-07-11T14:51:13+02:00 - info: Block #34361 added to the blockchain in 39771 ms
2017-07-11T14:51:13+02:00 - info: Stop proof-of-work worker #1
2017-07-11T14:51:14+02:00 - info: Stop proof-of-work worker #2
2017-07-11T14:51:15+02:00 - info: POST Block block#34361
2017-07-11T14:51:16+02:00 - info: Stop proof-of-work worker #1
2017-07-11T14:51:16+02:00 - info: Stop proof-of-work worker #2
2017-07-11T14:51:16+02:00 - info: Block #34362 added to the blockchain in 2031 ms
2017-07-11T14:51:17+02:00 - error: Written: transactions=[], excluded=[], actives=[], leavers=[], revoked=[], identities=[], joiners=[], certifications=[], hash=00001EF886E5880BBBB41FB0FE6460C07F42CF6D0609CF4DF31EBC844F0C91B8, signature=ctkCTzcl1KVzLN/cCOEQv1pqOlokCQHAtLgvukuWDDg8i4Bx/VFVGBZuMOg4lA6qUofzwGjExhTFxYSJpiokCQ==, raw=Version: 10
Type: Block
Currency: g1
Number: 34362
PoWMin: 75
Time: 1499777411
MedianTime: 1499775920
UnitBase: 0
Issuer: FVUFRrk1K5TQGsY7PRLwqHgdHRoHrwb1hcucp4C2N5tD
IssuersFrame: 91
IssuersFrameVar: 0
DifferentIssuersCount: 18
PreviousHash: 000028D46557301EE81E789C5736792A7606D5E025FBE5D4959D0C511BA5156C
PreviousIssuer: 6fFt4zdvtNyVcfJn7Y41mKLmMDizyK3nVeNW3qdDXzpc
MembersCount: 185
Identities:
Joiners:
Actives:
Leavers:
Revoked:
Excluded:
Certifications:
Transactions:
InnerHash: 63B3A95C97401D04982169BEA079E35638A302ABEC38368AC41D680EFB9F5A56
Nonce: 10200000001413
, version=10, currency=g1, number=34362, powMin=75, time=1499777411, medianTime=1499775920, unitbase=0, issuer=FVUFRrk1K5TQGsY7PRLwqHgdHRoHrwb1hcucp4C2N5tD, issuersFrame=91, issuersFrameVar=0, issuersCount=18, previousHash=000028D46557301EE81E789C5736792A7606D5E025FBE5D4959D0C511BA5156C, previousIssuer=6fFt4zdvtNyVcfJn7Y41mKLmMDizyK3nVeNW3qdDXzpc, membersCount=185, inner_hash=63B3A95C97401D04982169BEA079E35638A302ABEC38368AC41D680EFB9F5A56, nonce=10200000001413, dividend=null, parameters=, monetaryMass=14182000
2017-07-11T14:51:17+02:00 - error: TypeError: written.json is not a function
at /opt/duniter/node_modules/duniter-bma/lib/controllers/abstract.js:15:22
at next (native)
at onFulfilled (/opt/duniter/node_modules/co/index.js:65:19)
at process._tickCallback (internal/process/next_tick.js:109:7)
2017-07-11T14:51:17+02:00 - error: TypeError: written.json is not a function
at /opt/duniter/node_modules/duniter-bma/lib/controllers/abstract.js:15:22
at next (native)
at onFulfilled (/opt/duniter/node_modules/co/index.js:65:19)
at process._tickCallback (internal/process/next_tick.js:109:7)
2017-07-11T14:51:17+02:00 - warn: written.json is not a function
2017-07-11T14:51:19+02:00 - info: Stop proof-of-work worker #1
2017-07-11T14:51:19+02:00 - info: Stop proof-of-work worker #2
2017-07-11T14:51:19+02:00 - info: GIVEN proof-of-work for block#34361 with 4 leading zeros followed by [0-4]! stop PoW for GfKERH
2017-07-11T14:51:19+02:00 - warn: The proof-of-work generation was canceled: Proof-of-work computation canceled because block received
2017-07-11T14:51:19+02:00 - info: POST Block block#34362
2017-07-11T14:51:19+02:00 - warn: connect ECONNREFUSED 78.227.107.45:10901
2017-07-11T14:51:22+02:00 - info: POST Peer 3QLkBNoCNJ#34329
```1.4.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1024PoW is not launched2018-01-27T07:27:43+01:00Cédric MoreauPoW is not launched*Created by: M5oul*
- Version: `dev@32a7b9058818e6179714fb5e697039943df49292`*Created by: M5oul*
- Version: `dev@32a7b9058818e6179714fb5e697039943df49292`1.4.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1021Strange Nonce happen sometime2018-01-27T07:27:43+01:00Cédric MoreauStrange Nonce happen sometime*Created by: M5oul*
```bash
2017-06-26T17:33:16+02:00 - info: Matched 3 zeros 0006F7F79BB665F1AB16F5EAAE6F0884C460833655E2C77A7DDDE272791C7CCE with Nonce = 1.00000000000002e+25 for block#30392 by GfKERH
2017-06-26T17:33:16+02:00 - inf...*Created by: M5oul*
```bash
2017-06-26T17:33:16+02:00 - info: Matched 3 zeros 0006F7F79BB665F1AB16F5EAAE6F0884C460833655E2C77A7DDDE272791C7CCE with Nonce = 1.00000000000002e+25 for block#30392 by GfKERH
2017-06-26T17:33:16+02:00 - info: Matched 3 zeros 0006F7F79BB665F1AB16F5EAAE6F0884C460833655E2C77A7DDDE272791C7CCE with Nonce = 1.00000000000002e+25 for block#30392 by GfKERH
2017-06-26T17:33:17+02:00 - info: Matched 3 zeros 0006F7F79BB665F1AB16F5EAAE6F0884C460833655E2C77A7DDDE272791C7CCE with Nonce = 1.00000000000002e+25 for block#30392 by GfKERH
2017-06-26T17:33:40+02:00 - info: Pulling blocks from the network...
2017-06-26T17:33:40+02:00 - info: Will pull blocks from the network in 1 min 58 sec
```1.4.0https://git.duniter.org/nodes/typescript/duniter/-/issues/974Proof-of-work is launched during initial sync2018-01-27T07:27:44+01:00Cédric MoreauProof-of-work is launched during initial syncIt's making the sync longer, it could even break the sync if a PoW is found.It's making the sync longer, it could even break the sync if a PoW is found.1.2.3https://git.duniter.org/nodes/typescript/duniter/-/issues/910Memory leaks on main process2018-01-27T07:27:45+01:00Cédric MoreauMemory leaks on main process*Created by: M5oul*
On my Internet Cube dedicated to Duniter node, there memory leaks as duniter process takes 750Mb. This process is running since five days at least.
This process takes almost 130Mb when turning-it on.
That could e...*Created by: M5oul*
On my Internet Cube dedicated to Duniter node, there memory leaks as duniter process takes 750Mb. This process is running since five days at least.
This process takes almost 130Mb when turning-it on.
That could explain why my not-dedicated ARM board was unrechable since there were no more memory available.
![capture du 2017-03-27 09-33-02](https://cloud.githubusercontent.com/assets/4758871/24345523/ee2b3116-12d0-11e7-8884-8374df348bb7.png)
Other: I don't know why there is so much processes.1.2.3https://git.duniter.org/nodes/typescript/duniter/-/issues/839CPU settings sometimes not taken into account2018-01-27T07:27:46+01:00Cédric MoreauCPU settings sometimes not taken into account*Created by: jytou*
I have duniter-desktop version 0.90.6 on Ubuntu 14, when I set the CPU settings to something lower than 100%, from time to time it will start mining at 100% anyhow (although the GUI settings still show the initial se...*Created by: jytou*
I have duniter-desktop version 0.90.6 on Ubuntu 14, when I set the CPU settings to something lower than 100%, from time to time it will start mining at 100% anyhow (although the GUI settings still show the initial setting < 100%). Clicking on the GUI with another setting correctly enforces it... for a while (and I believe at least until a new block is found).0.91.0