duniter issueshttps://git.duniter.org/nodes/typescript/duniter/-/issues2019-04-17T13:39:00+02:00https://git.duniter.org/nodes/typescript/duniter/-/issues/1365New versions are not published on NPM2019-04-17T13:39:00+02:00Cédric MoreauNew versions are not published on NPMVersions with pattern 1.x.y should be published on NPM, so that softwares relying on it can upgrade.Versions with pattern 1.x.y should be published on NPM, so that softwares relying on it can upgrade.https://git.duniter.org/nodes/typescript/duniter/-/issues/1363JSON blockchain archives are duplicated2020-10-04T18:31:40+02:00Pascal EngélibertJSON blockchain archives are duplicatedBoth `archives` and `g1` folders contain exactly the same data (excepted the `fork` value), so 260 MB could be saved by removing one of them.Both `archives` and `g1` folders contain exactly the same data (excepted the `fork` value), so 260 MB could be saved by removing one of them.2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1357[AT] `OUT` membership must not be included in a block if issued by a non-member2019-04-07T13:58:06+02:00Cédric Moreau[AT] `OUT` membership must not be included in a block if issued by a non-memberSee https://forum.duniter.org/t/bug-a-l-ajout-d-une-certification-d-un-non-membre-dans-le-bloc-a-calculer-v1-7-16/5952/13See https://forum.duniter.org/t/bug-a-l-ajout-d-une-certification-d-un-non-membre-dans-le-bloc-a-calculer-v1-7-16/5952/13https://git.duniter.org/nodes/typescript/duniter/-/issues/1354Add an automated test for dal.isMember()2022-07-07T10:45:00+02:00Cédric MoreauAdd an automated test for dal.isMember()See https://forum.duniter.org/t/bug-a-l-ajout-d-une-certification-d-un-non-membre-dans-le-bloc-a-calculer-v1-7-16/5952
`isMember()` should work: return true when and identity is member, false when it’s not
Tests to lock this feature fi...See https://forum.duniter.org/t/bug-a-l-ajout-d-une-certification-d-un-non-membre-dans-le-bloc-a-calculer-v1-7-16/5952
`isMember()` should work: return true when and identity is member, false when it’s not
Tests to lock this feature fixed in https://git.duniter.org/nodes/typescript/duniter/commit/f9778328c483f7a5a0b565f0f9d539fb175bec551.10https://git.duniter.org/nodes/typescript/duniter/-/issues/1353An identity with its membership which just expires proceed block calculation2020-10-04T18:34:17+02:00MoulAn identity with its membership which just expires proceed block calculation> Cf: https://forum.duniter.org/t/g1-test-dans-les-choux/4192/316?u=moul
It is not happening when launching pow with an already expired membership identity.
But, it happen, when an member identity is calculating, then loose its members...> Cf: https://forum.duniter.org/t/g1-test-dans-les-choux/4192/316?u=moul
It is not happening when launching pow with an already expired membership identity.
But, it happen, when an member identity is calculating, then loose its membership and keep calculate.
There is no further check at each block if the identity is still member. A mechanism should handle that.2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1349Deno instead of Nodejs?2020-05-10T18:15:04+02:00MoulDeno instead of Nodejs?- [Deno website](https://deno.land/)
- [Deno repository](https://github.com/denoland/deno)
> A secure JavaScript/TypeScript runtime built with V8, Rust, and Tokio.
Deno would be able to interpret TypeScript directly.
No need for transp...- [Deno website](https://deno.land/)
- [Deno repository](https://github.com/denoland/deno)
> A secure JavaScript/TypeScript runtime built with V8, Rust, and Tokio.
Deno would be able to interpret TypeScript directly.
No need for transpilation to JavaScript.
This is the project from the same author of Node.js.
The project is still in early stage. But, it worth having a look.Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/1347Node try to connect to previous currency peers after switch to another currency2019-03-27T10:30:56+01:00Vincent TexierNode try to connect to previous currency peers after switch to another currencyDuniter desktop 1.7.11 on Ubuntu 14.04. All actions made on the GUI.
* Running as g1-test node since installation.
* Full data reset on a g1 node to help in the forks.
* Few syncs later, and few hours later, the logs says that **the nod...Duniter desktop 1.7.11 on Ubuntu 14.04. All actions made on the GUI.
* Running as g1-test node since installation.
* Full data reset on a g1 node to help in the forks.
* Few syncs later, and few hours later, the logs says that **the node try to contact g1-test and g1 peers as well** !
```javascript
2019-03-27T10:16:06+01:00 - info: WS2P: Could not connect to peer 85W4GAHQ using `WS2P g1test.nordstrom.duniter.org 443: WS2P connection timeout`
2019-03-27T10:16:06+01:00 - debug: WS2P: init: failed connection
2019-03-27T10:16:06+01:00 - info: WS2P: Could not connect to peer 7GG6nP4T using `WS2P legacy.g1test.nordstrom.duniter.org 443: WS2P connection timeout`
2019-03-27T10:16:06+01:00 - info: WS2P: Could not connect to peer JyTqcD4Q using `WS2P gtest.jytou.fr 443: WS2P connection timeout`
2019-03-27T10:16:06+01:00 - debug: WS2P: init: failed connection
2019-03-27T10:16:06+01:00 - debug: WS2P: init: failed connection
2019-03-27T10:16:06+01:00 - info: WS2P: Could not connect to peer Do99s6wQ using `WS2P duniter-g1.p2p.legal 443: WS2P connection timeout`
2019-03-27T10:16:06+01:00 - info: WS2P: Could not connect to peer E7KeCdDS using `WS2P 93.20.61.189 20900: WS2P connection timeout`
```https://git.duniter.org/nodes/typescript/duniter/-/issues/1339In a quick sync on a currency with changed UnitBase, generated b_index may no...2019-02-03T12:24:04+01:00Cédric MoreauIn a quick sync on a currency with changed UnitBase, generated b_index may not be correct about UDhttps://git.duniter.org/nodes/typescript/duniter/-/issues/1338Quick sync and normal sync do not lead to the same b_index2020-04-30T22:29:29+02:00Cédric MoreauQuick sync and normal sync do not lead to the same b_indexSee https://forum.duniter.org/t/g1-test-bloquee-bloc-genere-mais-refuse-de-part-sa-taille/5648/47See https://forum.duniter.org/t/g1-test-bloquee-bloc-genere-mais-refuse-de-part-sa-taille/5648/471.10https://git.duniter.org/nodes/typescript/duniter/-/issues/1335Have command specific options2019-01-29T12:17:41+01:00MoulHave command specific optionscf https://www.npmjs.com/package/commander#command-specific-options
This is really annoying to find which option apply to which command.
There is some specifics option only for `sync` command for instance.
They should only be accessib...cf https://www.npmjs.com/package/commander#command-specific-options
This is really annoying to find which option apply to which command.
There is some specifics option only for `sync` command for instance.
They should only be accessible via `duniter sync -h` and not via `duniter -h`.
General options which can apply to many commands should stay at the root of the help.2.0https://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/1327Error ESOCKETTIMEDOUT at the end of the sync2019-01-05T19:34:35+01:00Cédric MoreauError ESOCKETTIMEDOUT at the end of the syncAn orange message can occur at the end of a synchronization:
ESOCKETTIMEDOUT
This is a failure of sandboxes' sync, it is not critical at all. The sandboxes will be synced later when the node will be running as well.
But it should ...An orange message can occur at the end of a synchronization:
ESOCKETTIMEDOUT
This is a failure of sandboxes' sync, it is not critical at all. The sandboxes will be synced later when the node will be running as well.
But it should not be blocking.https://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/1309/wot/certified-by/ => Error "Cannot read property 'pub' of null"2019-04-01T10:44:28+02:00Benoit Lavenier/wot/certified-by/ => Error "Cannot read property 'pub' of null"Sur G1-test, je constate une erreur lors de l'appel de `/wot/certified-by/` sur une clef non membre : (exemple [ici](http://88.174.120.187:10900/wot/certified-by/9N8tk7oz7sFXbZij3AFRM2HupDJCRcpsfN99tpXeo2wE))
```json
{
"ucode": 1002,
...Sur G1-test, je constate une erreur lors de l'appel de `/wot/certified-by/` sur une clef non membre : (exemple [ici](http://88.174.120.187:10900/wot/certified-by/9N8tk7oz7sFXbZij3AFRM2HupDJCRcpsfN99tpXeo2wE))
```json
{
"ucode": 1002,
"message": "Cannot read property 'pub' of null"
}
```
Auparavant (et sur G1 cela semble fonctionner ainsi), cela renvoyait un code 2004 : (exemple [ici](https://g1.duniter.fr/wot/certified-by/9N8tk7oz7sFXbZij3AFRM2HupDJCRcpsfN99tpXeo2wE))
```json
{
"ucode": 2004,
"message": "No member matching this pubkey or uid"
}
```
Cela fait planter Cesium, qui ne sait pas comment gérer cette erreur.
Je peux évidemment ajouter un cas pour dire que le compte n'est sans doute pas certifié, mais je voudrais etre sur que je loupe pas quelque chose de plus grave...
Merci !!https://git.duniter.org/nodes/typescript/duniter/-/issues/1305During the sync, propagate a new peer document and start listening to the net...2018-06-20T20:18:21+02:00Cédric MoreauDuring the sync, propagate a new peer document and start listening to the networkWe can listen to the network even if we don't have a blockchain: using WS2P private for example.
This way even if the sync takes a lot of time, we can keep up with the network's HEAD by receiving the new incoming blocks. Also, we would ...We can listen to the network even if we don't have a blockchain: using WS2P private for example.
This way even if the sync takes a lot of time, we can keep up with the network's HEAD by receiving the new incoming blocks. Also, we would get notified of each node's HEAD packet and display a view of the network during the synchronization.
This could help the user to understand what is the final state to reach. For example we could say "the node will reach this consensus".