duniter issueshttps://git.duniter.org/nodes/typescript/duniter/-/issues2020-04-30T22:31:41+02:00https://git.duniter.org/nodes/typescript/duniter/-/issues/1333Ğ1 node stuck2020-04-30T22:31:41+02:00MoulĞ1 node stuckI created a [dump by myself](https://moul.re/jirafeau/f.php?h=2khmsr-r&d=1).
The arguments of `duniter dump` is not explicit.I created a [dump by myself](https://moul.re/jirafeau/f.php?h=2khmsr-r&d=1).
The arguments of `duniter dump` is not explicit.1.10https://git.duniter.org/nodes/typescript/duniter/-/issues/1329WS2P sync does not work on nodes with a path in their WS2P endpoint2020-10-04T18:34:41+02:00Cédric MoreauWS2P sync does not work on nodes with a path in their WS2P endpointFor example with this endpoint:
WS2P 90e9b12 duniter.g1.1000i100.fr 443 /ws2p
Duniter will try to join `wss://duniter.g1.1000i100.fr /ws2p`. There is an extra space here which make the connection fail.For example with this endpoint:
WS2P 90e9b12 duniter.g1.1000i100.fr 443 /ws2p
Duniter will try to join `wss://duniter.g1.1000i100.fr /ws2p`. There is an extra space here which make the connection fail.1.10Cédric MoreauCédric Moreauhttps://git.duniter.org/nodes/typescript/duniter/-/issues/1328BMA: /blockchain/block transactions do no longer have the `hash` field2020-10-04T18:35:02+02:00Cédric MoreauBMA: /blockchain/block transactions do no longer have the `hash` fieldSee https://forum.duniter.org/t/api-bma-1-7-tx-hash/5567See https://forum.duniter.org/t/api-bma-1-7-tx-hash/55672.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1324Add "syc in RAM" option2020-10-04T19:14:29+02:00Cédric MoreauAdd "syc in RAM" optionNot really a priority, but it could be useful for some users.Not really a priority, but it could be useful for some users.2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1319Sync stuck in infinite loop...2020-10-04T18:35:40+02:00Vincent TexierSync stuck in infinite loop...Duniter desktop v1.7.8,
reset & sync on `g1-test.cgeek.fr` port `443`, at 01:00 am on december the 26th.
Milestones... (100%)
Download... (99%)
Apply... (98%)
Sandbox... (0%)
Peers... (0%)
Download stuck at 99%, with the logs scrolli...Duniter desktop v1.7.8,
reset & sync on `g1-test.cgeek.fr` port `443`, at 01:00 am on december the 26th.
Milestones... (100%)
Download... (99%)
Apply... (98%)
Sandbox... (0%)
Peers... (0%)
Download stuck at 99%, with the logs scrolling fast and cycling infinitely on this statements :
```javascript
at <anonymous>
2018-12-26T11:23:01+01:00 - warn: No node found to download chunk #1173.
2018-12-26T11:23:01+01:00 - error: Error: NO_NODE_FOUND_TO_DOWNLOAD_CHUNK
at fifoPromise.pushFIFOPromise (/mnt/data/Logiciels/duniter-desktop-v1.7.8-linux-x64/app/modules/crawler/lib/sync/P2PSyncDownloader.js:73:23)
at <anonymous>
2018-12-26T11:23:01+01:00 - warn: No node found to download chunk #1176.
2018-12-26T11:23:01+01:00 - error: Error: NO_NODE_FOUND_TO_DOWNLOAD_CHUNK
at fifoPromise.pushFIFOPromise (/mnt/data/Logiciels/duniter-desktop-v1.7.8-linux-x64/app/modules/crawler/lib/sync/P2PSyncDownloader.js:73:23)
at <anonymous>
2018-12-26T11:23:02+01:00 - warn: No node found to download chunk #1174.
2018-12-26T11:23:02+01:00 - error: Error: NO_NODE_FOUND_TO_DOWNLOAD_CHUNK
at fifoPromise.pushFIFOPromise (/mnt/data/Logiciels/duniter-desktop-v1.7.8-linux-x64/app/modules/crawler/lib/sync/P2PSyncDownloader.js:73:23)
at <anonymous>
2018-12-26T11:23:02+01:00 - warn: No node found to download chunk #1173.
2018-12-26T11:23:02+01:00 - error: Error: NO_NODE_FOUND_TO_DOWNLOAD_CHUNK
at fifoPromise.pushFIFOPromise (/mnt/data/Logiciels/duniter-desktop-v1.7.8-linux-x64/app/modules/crawler/lib/sync/P2PSyncDownloader.js:73:23)
at <anonymous>
```
Duniter should be able to find another node to finish the download, because I see many nodes in cesium g1-test.2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1318Sandboxes sync issues?2020-10-04T18:36:01+02:00MoulSandboxes sync issues?Strange, it seems the sandboxes synchronization didn’t happen in the initial step with Ğ1:
```bash
Milestones: [||||||||||||||||||||] 100 %
Download: [||||||||||||||||||||] 100 %
Apply: [||||||||||||||||||||] 100 %
Sandbox: ...Strange, it seems the sandboxes synchronization didn’t happen in the initial step with Ğ1:
```bash
Milestones: [||||||||||||||||||||] 100 %
Download: [||||||||||||||||||||] 100 %
Apply: [||||||||||||||||||||] 100 %
Sandbox: [ ] 0 %
Peers: [||||||||||||||||||||] 100 %
```
Thought, it happen later.
I didn’t encounter this issue with gtest.
May be a display issue.2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1314Zombies PoW processes2019-09-10T12:01:34+02:00MoulZombies PoW processesThere is many zombies PoW processes which are left running by duniter main process:
![Ekrankopio_de_2018-11-17_14-15-01](/uploads/33094dda63f49c9323f5160feaa89931/Ekrankopio_de_2018-11-17_14-15-01.png)
Sometimes, theses processes are ta...There is many zombies PoW processes which are left running by duniter main process:
![Ekrankopio_de_2018-11-17_14-15-01](/uploads/33094dda63f49c9323f5160feaa89931/Ekrankopio_de_2018-11-17_14-15-01.png)
Sometimes, theses processes are taking a bit of CPU, around 5%.2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1290Add the packaging metadata to build the duniter snap2018-03-07T22:06:06+01:00ÉloïsAdd the packaging metadata to build the duniter snap*Created by: elopio*
This package will let you publish the latest dunier in the Ubuntu store, and from there reach many users on all the supported Ubuntu versions, and more Linux distributions in progress.*Created by: elopio*
This package will let you publish the latest dunier in the Ubuntu store, and from there reach many users on all the supported Ubuntu versions, and more Linux distributions in progress.Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/1289On a new installation ws2p quota outgoing is 102020-10-04T18:36:17+02:00ÉloïsOn a new installation ws2p quota outgoing is 10On a new installation ws2p quota outgoing is 10 while it should be at 5On a new installation ws2p quota outgoing is 10 while it should be at 52.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1287NPM releases are not updated by GitLab2020-10-04T18:38:29+02:00Cédric MoreauNPM releases are not updated by GitLabI wanted to upgrade Remuniter to duniter@1.6.21, but the latest version is only 1.6.14. There is something broken somewhere.
![image](/uploads/5fa638b241b6a0ac8b50bf9080601aef/image.png)I wanted to upgrade Remuniter to duniter@1.6.21, but the latest version is only 1.6.14. There is something broken somewhere.
![image](/uploads/5fa638b241b6a0ac8b50bf9080601aef/image.png)1.10https://git.duniter.org/nodes/typescript/duniter/-/issues/1285Sync : check integrity of downloaded chunks2020-10-04T18:38:49+02:00ÉloïsSync : check integrity of downloaded chunkshttps://forum.duniter.org/t/ca-y-est-cest-lance-ou-presque-au-secours/4344/31?u=eloishttps://forum.duniter.org/t/ca-y-est-cest-lance-ou-presque-au-secours/4344/31?u=elois2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1284Node stopped2020-10-04T18:39:11+02:00MoulNode stopped1.6.21 stop:
```bash
2018-03-03T13:39:13+01:00 - warn: ESOCKETTIMEDOUT
2018-03-03T13:39:13+01:00 - info: Peer DJQjWdkUB9YWzGRPTjPCdGgC5pBx6CA24Dghu6NNvpuH unreachable: now considered as DOWN.
2018-03-03T13:39:15+01:00 - info: Pulling bl...1.6.21 stop:
```bash
2018-03-03T13:39:13+01:00 - warn: ESOCKETTIMEDOUT
2018-03-03T13:39:13+01:00 - info: Peer DJQjWdkUB9YWzGRPTjPCdGgC5pBx6CA24Dghu6NNvpuH unreachable: now considered as DOWN.
2018-03-03T13:39:15+01:00 - info: Pulling blocks from the network...
2018-03-03T13:39:16+01:00 - info: Node 5gJYnQ (g1.imirhil.fr:80) is UP!
2018-03-03T13:39:16+01:00 - info: Block resolution: 0 potential blocks after current#99603...
2018-03-03T13:39:16+01:00 - info: Will pull blocks from the network in 3 min 21 sec
2018-03-03T13:39:16+01:00 - info: Node FEkbc4 (me.jytou.fr:9007) is UP!
2018-03-03T13:39:20+01:00 - error: Error: read ETIMEDOUT
at _errnoException (util.js:1022:11)
at TCP.onread (net.js:615:25)
```2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1283build release for linux-x86 in docker2018-03-07T21:05:50+01:00Éloïsbuild release for linux-x86 in dockerHorizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/1281Improve block generation speed2020-10-04T18:41:55+02:00Cédric MoreauImprove block generation speedThe block generation is becoming slower and slower on Ğ1 due to the increasing activity on it, notably the WoT documents.
It is particularly handicaping for modest configurations like Raspberry PIs.The block generation is becoming slower and slower on Ğ1 due to the increasing activity on it, notably the WoT documents.
It is particularly handicaping for modest configurations like Raspberry PIs.2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1280sync: delete filesystem chunks that do not chains correctly2020-05-01T13:19:11+02:00Cédric Moreausync: delete filesystem chunks that do not chains correctlyhttps://forum.duniter.org/t/bug-de-synchro-sur-g1-test/4245/101?u=cgeekhttps://forum.duniter.org/t/bug-de-synchro-sur-g1-test/4245/101?u=cgeekHorizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/1279My node sends wrong blocks in a row2020-10-04T18:42:12+02:00insoMy node sends wrong blocks in a rowSee https://forum.duniter.org/t/bug-de-synchro-sur-g1-test/4245/42
.db and wotb.bin files : [inso.tar.gz](/uploads/2d06c4ac41a17ef7bcb207259a898424/inso.tar.gz)See https://forum.duniter.org/t/bug-de-synchro-sur-g1-test/4245/42
.db and wotb.bin files : [inso.tar.gz](/uploads/2d06c4ac41a17ef7bcb207259a898424/inso.tar.gz)2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1273Error: Request failed: 500 on requesting upnp server of the router2020-10-04T18:42:27+02:00Vincent TexierError: Request failed: 500 on requesting upnp server of the routerTesting Duniter Desktop 1.6.17 tar.gz archive.
Nodejs
But playing with upnp on/off on duniter desktop seems to wreck the upnp responses of my livebox.
```javascript
2018-02-03T16:50:14+01:00 - error: Error: Request failed: 500
at ...Testing Duniter Desktop 1.6.17 tar.gz archive.
Nodejs
But playing with upnp on/off on duniter desktop seems to wreck the upnp responses of my livebox.
```javascript
2018-02-03T16:50:14+01:00 - error: Error: Request failed: 500
at /mnt/data/Logiciels/duniter-desktop-v1.6.17-linux-x64/node_modules/nnupnp/lib/nat-upnp/device.js:151:27
at Parser.<anonymous> (/mnt/data/Logiciels/duniter-desktop-v1.6.17-linux-x64/node_modules/xml2js/lib/xml2js.js:199:18)
at emitOne (events.js:115:13)
at Parser.emit (events.js:210:7)
at SAXParser.saxParser.onclosetag (/mnt/data/Logiciels/duniter-desktop-v1.6.17-linux-x64/node_modules/xml2js/lib/xml2js.js:183:24)
at emit (/mnt/data/Logiciels/duniter-desktop-v1.6.17-linux-x64/node_modules/sax/lib/sax.js:624:35)
at emitNode (/mnt/data/Logiciels/duniter-desktop-v1.6.17-linux-x64/node_modules/sax/lib/sax.js:629:5)
at closeTag (/mnt/data/Logiciels/duniter-desktop-v1.6.17-linux-x64/node_modules/sax/lib/sax.js:889:7)
at SAXParser.write (/mnt/data/Logiciels/duniter-desktop-v1.6.17-linux-x64/node_modules/sax/lib/sax.js:1436:13)
at Parser.exports.Parser.Parser.parseString (/mnt/data/Logiciels/duniter-desktop-v1.6.17-linux-x64/node_modules/xml2js/lib/xml2js.js:211:31)
at Parser.parseString (/mnt/data/Logiciels/duniter-desktop-v1.6.17-linux-x64/node_modules/xml2js/lib/xml2js.js:6:61)
at Request._callback (/mnt/data/Logiciels/duniter-desktop-v1.6.17-linux-x64/node_modules/nnupnp/lib/nat-upnp/device.js:149:14)
at Request.self.callback (/mnt/data/Logiciels/duniter-desktop-v1.6.17-linux-x64/node_modules/nnupnp/node_modules/request/main.js:120:22)
at emitTwo (events.js:125:13)
at Request.emit (events.js:213:7)
at Request.<anonymous> (/mnt/data/Logiciels/duniter-desktop-v1.6.17-linux-x64/node_modules/nnupnp/node_modules/request/main.js:633:16)
at emitOne (events.js:115:13)
at Request.emit (events.js:210:7)
at IncomingMessage.<anonymous> (/mnt/data/Logiciels/duniter-desktop-v1.6.17-linux-x64/node_modules/nnupnp/node_modules/request/main.js:595:14)
at emitNone (events.js:110:20)
at IncomingMessage.emit (events.js:207:7)
at endReadableNT (_stream_readable.js:1059:12)
```
I have deleted .config/duniter, restarted a sync on gtest node, and get this error in the logs again...
Duniter should handle the response correctly without crashing the XML parser.2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1272Command yarn tscw fails2018-03-07T22:35:07+01:00swergasCommand yarn tscw failsHi, I'm following this tutorial page https://duniter.org/fr/wiki/duniter/tutoriel-dev/chapitre-4-demarrage/ , and when I run `yarn tsc` there is no problem, but when I run `yarn tscw` I get the following output:
```
$ yarn tscw
yarn run...Hi, I'm following this tutorial page https://duniter.org/fr/wiki/duniter/tutoriel-dev/chapitre-4-demarrage/ , and when I run `yarn tsc` there is no problem, but when I run `yarn tscw` I get the following output:
```
$ yarn tscw
yarn run v1.3.2
$ tsc -w
fs.js:1376
throw error;
^
Error: watch /home/quentin/prog/duniter/typescript/duniter EMFILE
at _errnoException (util.js:1024:11)
at FSWatcher.start (fs.js:1374:19)
at Object.fs.watch (fs.js:1400:11)
at watchPresentDirectory (/home/quentin/prog/duniter/typescript/duniter/node_modules/typescript/lib/tsc.js:2635:42)
at fsWatchDirectory (/home/quentin/prog/duniter/typescript/duniter/node_modules/typescript/lib/tsc.js:2620:21)
at Object.watchDirectory (/home/quentin/prog/duniter/typescript/duniter/node_modules/typescript/lib/tsc.js:2768:28)
at addDirectoryWatcher (/home/quentin/prog/duniter/typescript/duniter/node_modules/typescript/lib/tsc.js:56930:21)
at Object.watchDirectory (/home/quentin/prog/duniter/typescript/duniter/node_modules/typescript/lib/tsc.js:59955:20)
at createDirectoryWatcher (/home/quentin/prog/duniter/typescript/duniter/node_modules/typescript/lib/tsc.js:59381:35)
at watchFailedLookupLocationOfResolution (/home/quentin/prog/duniter/typescript/duniter/node_modules/typescript/lib/tsc.js:59348:81)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
```
And I can't find util.js and fs.js files that are mentioned in the error. Any idea?Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/1264Explicit SSL/TLS endpoints2020-10-04T18:40:29+02:00Kévin GuignardExplicit SSL/TLS endpointsPlease add explicit HTTPS endpoint for BMA (i.e. **BMAS**) and explicit WSS endpoint for WS2P (i.e. **WS2PS**).
I am NOT talking about handling SSL/TLS but how the nodes declare themselves on the network. By the way, a reverse-proxy (ngi...Please add explicit HTTPS endpoint for BMA (i.e. **BMAS**) and explicit WSS endpoint for WS2P (i.e. **WS2PS**).
I am NOT talking about handling SSL/TLS but how the nodes declare themselves on the network. By the way, a reverse-proxy (nginx, apache, stunnel, whatever) would still be required.2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1263Error: ruleIssuerIsMember at Function.checkBlock2018-03-07T22:37:43+01:00Vincent TexierError: ruleIssuerIsMember at Function.checkBlockJ’ai lancé la version desktop.tar.gz de la 1.6.17 en prerelease.
https://git.duniter.org/nodes/typescript/duniter/-/jobs/2031/artifacts/file/work/bin/duniter-desktop-v20180128.2213.27-linux-x64.tar.gz
Reset Data
Sync sur g1-test.dunite...J’ai lancé la version desktop.tar.gz de la 1.6.17 en prerelease.
https://git.duniter.org/nodes/typescript/duniter/-/jobs/2031/artifacts/file/work/bin/duniter-desktop-v20180128.2213.27-linux-x64.tar.gz
Reset Data
Sync sur g1-test.duniter.org 443.
Je reçois bien les blocs venant de g1-test.duniter.org 443.
Mais.
Le WS2P public est activé mais cesium me voit en noeud privé…
L’interface me dit qu’elle attend une meilleure difficulté pour calculer un bloc.
J’ai mis mes identifiants. La clef public est bonne.
J’ai cet inquiétant message d’erreur dans les logs :
2018-01-29T19:37:13+01:00 - error: Error: ruleIssuerIsMember
at Function.checkBlock (/mnt/data/Logiciels/duniter-desktop-v20180128.2213.27-linux-x64/app/lib/blockchain/DuniterBlockchain.js:53:19)
Ci-joint la database pour debug : [duniter_db_for_debug.db.tgz](/uploads/a18693f203e194a9b8dfd2e1c88b91ce/duniter_db_for_debug.db.tgz)Horizon