nodes issueshttps://git.duniter.org/groups/nodes/-/issues2017-11-28T16:49:16+01:00https://git.duniter.org/nodes/typescript/duniter/-/issues/1100Allow certification cancelling2017-11-28T16:49:16+01:00Cédric MoreauAllow certification cancellingThe discussion is here: https://forum.duniter.org/t/annulation-de-certification/3233
It is still being discussed.The discussion is here: https://forum.duniter.org/t/annulation-de-certification/3233
It is still being discussed.Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/1182Separate network key and block computing key2020-10-04T18:45:31+02:00ÉloïsSeparate network key and block computing keyTo allow anonymization of nodes on the network, a member should be able to use a non-member anonymous network key.
The key dedicated to signing the calculated blocks would never be shared on the network.
The blocks that the node will c...To allow anonymization of nodes on the network, a member should be able to use a non-member anonymous network key.
The key dedicated to signing the calculated blocks would never be shared on the network.
The blocks that the node will compute. It would submit them to the network via ws2p in the same way as it relays any other block received. For the nodes that receive its blocks, it would be impossible to know if they are blocks that he has calculated himself or that he simply relays.2.0https://git.duniter.org/nodes/typescript/modules/duniter-currency-monit/-/issues/69erreur sur page GaussianWotQuality2020-04-24T18:39:12+02:00ty kaynerreur sur page GaussianWotQualitysur la page http://localhost:10500/gaussianWotQuality?lg=fr
on trouve cette erreur sur la branche master:
TypeError: Cannot read property 'detailedDistance' of null
at membersQuality (/var/www/html/duniter-currency-monit/routes/tool...sur la page http://localhost:10500/gaussianWotQuality?lg=fr
on trouve cette erreur sur la branche master:
TypeError: Cannot read property 'detailedDistance' of null
at membersQuality (/var/www/html/duniter-currency-monit/routes/tools/membersQuality.js:36:31)
at module.exports (/var/www/html/duniter-currency-monit/routes/gaussianWotQuality2.js:69:51)
at
at process._tickCallback (internal/process/next_tick.js:182:7)https://git.duniter.org/nodes/typescript/duniter/-/issues/717PB Installation de duniter-desktop sous debian 64 virtualisé virtualbox sous ...2017-11-28T16:49:16+01:00Cédric MoreauPB Installation de duniter-desktop sous debian 64 virtualisé virtualbox sous windows*Created by: bou2fil*
Problème instal sur noeud duniter-desktop sur vm virtualbox debian jessie 64bit, machine hote : windows 10 64 bit
Après avoir installé le paquet Duniter 0.50.2 avec gdebi sous root, j'ai lancé en tapant : dunite...*Created by: bou2fil*
Problème instal sur noeud duniter-desktop sur vm virtualbox debian jessie 64bit, machine hote : windows 10 64 bit
Après avoir installé le paquet Duniter 0.50.2 avec gdebi sous root, j'ai lancé en tapant : duniter-desktop
, il y a la fenetre graphique qui bloque sur du noir et le terminal affiche des trucs ci-dessous :
[1739:1739:1117/171004:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
2016-11-17T17:10:04+01:00 - debug: Opening SQLite database "/home/fil/.config/duniter/duniter_default/duniter.db"...
[1739:1739:1117/171004:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171004:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171004:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171004:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
2016-11-17T17:10:05+01:00 - debug: Upgrade database...
Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/859Systematically error + dumped2017-11-28T16:49:16+01:00Cédric MoreauSystematically error + dumped*Created by: galuel*
J'ai toujours un plantage sous Ubuntu 64 bits, lors du premier lancement de duniter-desktop, depuis tout le temps je crois bien. J'y ai pas trop porté d'attention, car au deuxième lancement ça fonctionne généralemen...*Created by: galuel*
J'ai toujours un plantage sous Ubuntu 64 bits, lors du premier lancement de duniter-desktop, depuis tout le temps je crois bien. J'y ai pas trop porté d'attention, car au deuxième lancement ça fonctionne généralement...
$ duniter-desktop
2017-03-01T12:36:23+01:00 - debug: Plugging file system...
2017-03-01T12:36:23+01:00 - debug: Loading conf...
2017-03-01T12:36:24+01:00 - debug: Configuration saved.
2017-03-01T12:36:24+01:00 - debug: Opening SQLite database "/home/galuel/.config/duniter/duniter_default/duniter.db"...
2017-03-01T12:36:24+01:00 - debug: Upgrade database...
2017-03-01T12:36:24+01:00 - info: Duniter server listening on http://192.168.0.77:30118
2017-03-01T12:36:24+01:00 - info: UPnP: configuring...
2017-03-01T12:36:24+01:00 - trace: UPnP: mapping external port 30118 to local 30118...
2017-03-01T12:36:24+01:00 - info: Crawling the network...
2017-03-01T12:36:24+01:00 - info: Pulling blocks from the network...
2017-03-01T12:36:25+01:00 - trace: Checking if node DZRR5W is UP... (88.190.82.70:30118)
2017-03-01T12:36:25+01:00 - info: Sibling endpoints:
2017-03-01T12:36:25+01:00 - trace: Try with 90.9.227.204:8999 7iBkcy
2017-03-01T12:36:25+01:00 - info: Crawling done.
2017-03-01T12:36:25+01:00 - info: External access: 88.190.82.70:30118
2017-03-01T12:36:25+01:00 - debug: Generating server's peering entry based on block#8697...
2017-03-01T12:36:26+01:00 - error:
Abandon (core dumped)
- deuxième lancement :
$ duniter-desktop
2017-03-01T12:36:44+01:00 - debug: Plugging file system...
2017-03-01T12:36:45+01:00 - debug: Loading conf...
2017-03-01T12:36:45+01:00 - debug: Configuration saved.
2017-03-01T12:36:45+01:00 - debug: Opening SQLite database "/home/galuel/.config/duniter/duniter_default/duniter.db"...
2017-03-01T12:36:45+01:00 - debug: Upgrade database...
2017-03-01T12:36:45+01:00 - info: Duniter server listening on http://192.168.0.77:30118
2017-03-01T12:36:45+01:00 - info: UPnP: configuring...
2017-03-01T12:36:45+01:00 - trace: UPnP: mapping external port 30118 to local 30118...
2017-03-01T12:36:45+01:00 - info: Crawling the network...
2017-03-01T12:36:45+01:00 - info: Pulling blocks from the network...
2017-03-01T12:36:46+01:00 - info: Crawling done.
2017-03-01T12:36:46+01:00 - debug: Will check that node DZRR5W (88.190.82.70:30118) is UP in 1440 min...
2017-03-01T12:36:46+01:00 - info: Sibling endpoints:
2017-03-01T12:36:46+01:00 - trace: Try with 90.9.227.204:8999 7iBkcy
2017-03-01T12:36:46+01:00 - info: External access: 88.190.82.70:30118
2017-03-01T12:36:46+01:00 - debug: Generating server's peering entry based on block#8698...
2017-03-01T12:36:46+01:00 - info: Changing conf to: {"prefix":10} on engine#1
2017-03-01T12:36:46+01:00 - info: Changing conf to: {"prefix":10} on engine#2
2017-03-01T12:36:46+01:00 - info: Next peering signal in 10 min
2017-03-01T12:36:46+01:00 - warn: Waitinghttps://git.duniter.org/nodes/typescript/duniter/-/issues/928gtest and g1 nodes communicating2017-11-28T16:49:16+01:00insogtest and g1 nodes communicatingHello,
I just saw the following logs in sakia :
```
DEBUG:network:handle_new_node:Stacking new peer document : 77mfxsDcX8JZKHD9fBC9wNtM1R7Yj3WA27DsY7kyrePX
DEBUG:network:discovery_loop:New node found : 77mfx
DEBUG:network:disco...Hello,
I just saw the following logs in sakia :
```
DEBUG:network:handle_new_node:Stacking new peer document : 77mfxsDcX8JZKHD9fBC9wNtM1R7Yj3WA27DsY7kyrePX
DEBUG:network:discovery_loop:New node found : 77mfx
DEBUG:network:discovery_loop:Error : Node is working for gtest currency, but should be g1
```
What do you think about it ?https://git.duniter.org/nodes/typescript/duniter/-/issues/1012Remember installed modules and reinstall them on Duniter update2020-10-04T18:48:09+02:00Cédric MoreauRemember installed modules and reinstall them on Duniter updateToday modules are completely removed when Duniter gets upgraded, and need to be manually reinstalled if we want to keep them working.
We could remember these installed modules in the configuration file, and reinstall them on Duniter sta...Today modules are completely removed when Duniter gets upgraded, and need to be manually reinstalled if we want to keep them working.
We could remember these installed modules in the configuration file, and reinstall them on Duniter startup if they are not installed yet (i.e. present in the package.json file).
Also if a module gets removed, we would remove it from the configuration file.2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1179Create a synchronization mechanism via ws2p2020-10-04T18:45:53+02:00ÉloïsCreate a synchronization mechanism via ws2pThis requires creating a new type of WS2P connection specifically designed for sync, a kind of temporary websocket just the time to download chunk files.This requires creating a new type of WS2P connection specifically designed for sync, a kind of temporary websocket just the time to download chunk files.2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/926Prune sandboxes on incoming data2017-11-28T16:49:16+01:00Cédric MoreauPrune sandboxes on incoming dataSee https://forum.duniter.org/t/noeud-specialise-pour-visualiser-salle-dattente-des-futurs-membres-g1/2230/69See https://forum.duniter.org/t/noeud-specialise-pour-visualiser-salle-dattente-des-futurs-membres-g1/2230/69Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/1099Have a dynamic stock of certifications2017-11-28T16:49:16+01:00Cédric MoreauHave a dynamic stock of certificationsThe discussion is here: https://forum.duniter.org/t/stock-de-certifications-dynamique/3232
For now this is still an under discussion feature.The discussion is here: https://forum.duniter.org/t/stock-de-certifications-dynamique/3232
For now this is still an under discussion feature.Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/1180WS2P Optimization: do not attempt to connect to a node whose key has already ...2020-10-04T18:47:45+02:00ÉloïsWS2P Optimization: do not attempt to connect to a node whose key has already connected us.It seems that Private WS2P is trying to connect to keys that are already connected in public mode.
Provide an exception for oneself (for multi-node cases).It seems that Private WS2P is trying to connect to keys that are already connected in public mode.
Provide an exception for oneself (for multi-node cases).2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/857Sync may lead to empty BINDEX2017-11-28T16:49:16+01:00Cédric MoreauSync may lead to empty BINDEXUnder certain circumstances, after a full sync and then a start, the BINDEX is empty.
I suspect this has some link with the block number being a multiple of the chunk, or something related.Under certain circumstances, after a full sync and then a start, the BINDEX is empty.
I suspect this has some link with the block number being a multiple of the chunk, or something related.Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/921Fast sync restarting a node with too much blocks missing2017-11-28T16:49:16+01:00Cédric MoreauFast sync restarting a node with too much blocks missing*Created by: M5oul*
When a node have been stopped for a long time.
It would be great that a mechanism detects that the node have too much blocks late.
Instead of trying to sync slowly.
It would be great that the fast sync could be la...*Created by: M5oul*
When a node have been stopped for a long time.
It would be great that a mechanism detects that the node have too much blocks late.
Instead of trying to sync slowly.
It would be great that the fast sync could be launched from current local blockchain state.Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/1009Network & sync issues since 1.3.92017-11-28T16:49:16+01:00Cédric MoreauNetwork & sync issues since 1.3.9https://forum.duniter.org/t/duniter-version-1-3/2684/13
https://forum.duniter.org/t/duniter-version-1-3/2684/13
1.3.10https://git.duniter.org/nodes/typescript/duniter/-/issues/1101Difficulties not updated with HEAD2017-11-28T16:49:16+01:00Cédric MoreauDifficulties not updated with HEAD*Created by: M5oul*
I noticed that the ID of the HEAD block issued by this ID is not displayed on `/blockchain/difficulties` when this ID was not on the current window. *Created by: M5oul*
I noticed that the ID of the HEAD block issued by this ID is not displayed on `/blockchain/difficulties` when this ID was not on the current window. Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/764Create issues for covering the protocol global rules2018-03-07T22:18:30+01:00Cédric MoreauCreate issues for covering the protocol global rulesWe should aim at covering every single rule of the protocol, at least for the global scope rules.
The idea is to reproduce what has been done in 50886de5c5577f1470fd4e6d8a2931eeabe27ce6.
We should create an issue per rule, so anyon...We should aim at covering every single rule of the protocol, at least for the global scope rules.
The idea is to reproduce what has been done in 50886de5c5577f1470fd4e6d8a2931eeabe27ce6.
We should create an issue per rule, so anyone could take the issue and focus on it.
Eventually, we could go further and do the same (create an issue) for the computation rules (BR_G01 to BR_G48).Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/852Do not launch PoW engines if not a member2017-11-28T16:49:16+01:00Cédric MoreauDo not launch PoW engines if not a memberHorizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/907Prioritize transaction's integration2017-11-28T16:49:16+01:00Cédric MoreauPrioritize transaction's integration> (14:54:45) inso: du coup on a rien conclut pour le moment pour limiter les tx "spam" ? :)
(14:55:47) inso: Dans bitcoin on notera que les noeuds ont des règles anti spam : https://en.bitcoin.it/wiki/Spam_transactions
(15:03:47) Moul ...> (14:54:45) inso: du coup on a rien conclut pour le moment pour limiter les tx "spam" ? :)
(14:55:47) inso: Dans bitcoin on notera que les noeuds ont des règles anti spam : https://en.bitcoin.it/wiki/Spam_transactions
(15:03:47) Moul [moul@moul.re/cab338c8-e743-424c-a0d7-b8247b43dfb6] a rejoint le salon.
(15:05:39) mamygeek a quitté le salon (Disconnected: closed)
(15:10:59) inso: Un truc tout simple pour l'anti spam : "Specifically, it looks for the age of the transaction outputs that are being spent. If you are transferring coins that were previously transfered a short time before, the priority goes down,"
(15:11:35) mamygeek [mamygeek@im.apinc.org/Julie] a rejoint le salon.
(15:12:55) Tortue a quitté le salon (Disconnected: timeout during receiving)
(15:12:57) cgeek: inso: oui c'est une bonne idée ça
(15:13:10) inso: Et qui suffit à régler un grand nombre de cas (quelqu'un qui chercherait à spammer le réseau pourrait consommer tout ses outputs, puis ça s'arrêterait puisque ses nouveaux outputs seraient trop récents)
(15:14:28) inso: Ce qui est intéressant c'est que des tx sans fees sont faisable dans bitcoin si elles respectent des conditions assez proche de ce qu'on fait dans DUniter :) http://bitcoin.stackexchange.com/a/37233
(15:14:39) inso: It is smaller than 1,000 bytes.
All outputs are 0.01 BTC or larger.
Its priority is large enough
(15:15:42) inso: Un petit point auquel je pense avec le problème de l'age des outputs - le chaining de transactions ne serait plus possible (ou apparaitre comme du spam)
(15:15:48) inso: Il faudrait l'implémenter différement
(15:25:09) inso: en fait non, les tx de change n'apparaitraient pas comme du spam
(15:25:19) inso: car on passerait de 44 inputs à 1 output
(15:25:33) inso: donc on détruit des outputs -> cette transaction est raisonnable
(15:25:57) inso: donc la priorité serait un facteur de l'age de l'output mais aussi de son origine (le nombre d'input détruit pour créé cette output)
(15:27:04) cgeek: oui d'accord, privilégier d'abord celles qui diminuent les outputs, puis celle à nombre égal priorisées par age, puis celles qui augmentent le nombre triées par augmentation et age
(15:28:46) inso: ca me parait correct :)https://git.duniter.org/nodes/typescript/duniter/-/issues/1095UPnP ports are opened during automated tests2017-11-28T16:49:16+01:00Cédric MoreauUPnP ports are opened during automated testsI could see several ports opened during unit tests using UPnP.
That should not occur, it is a bug in the tests.I could see several ports opened during unit tests using UPnP.
That should not occur, it is a bug in the tests.https://git.duniter.org/nodes/typescript/duniter/-/issues/1176resolv why test ws2p server limitations needs to establish a oneself ws2p con...2020-10-04T18:46:39+02:00Éloïsresolv why test ws2p server limitations needs to establish a oneself ws2p connectionthis test does not pass any more when we warn oneself ws2p connection :
So in the meantime we're applying an exception on the 11111111 uuid : https://github.com/duniter/duniter/commit/9fe597ee15631ff924addcb8a41a40577c211c93this test does not pass any more when we warn oneself ws2p connection :
So in the meantime we're applying an exception on the 11111111 uuid : https://github.com/duniter/duniter/commit/9fe597ee15631ff924addcb8a41a40577c211c932.0