duniter issueshttps://git.duniter.org/nodes/typescript/duniter/-/issues2020-10-04T18:31:02+02:00https://git.duniter.org/nodes/typescript/duniter/-/issues/1381/node/sandboxes does not display certifications sandboxes2020-10-04T18:31:02+02:00Moul/node/sandboxes does not display certifications sandboxes```json
/node/sandboxes
{
"identities": {
"size": 5000,
"free": 4866
},
"memberships": {
"size": 5000,
"free": 4001
},
"transactions": {
"size": 200,
"free": 179
}
}
``````json
/node/sandboxes
{
"identities": {
"size": 5000,
"free": 4866
},
"memberships": {
"size": 5000,
"free": 4001
},
"transactions": {
"size": 200,
"free": 179
}
}
```2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1380[mempool] expired memberships are accepted2019-06-02T12:11:11+02:00Cédric Moreau[mempool] expired memberships are acceptedSame as #1379.Same as #1379.1.7Cédric MoreauCédric Moreauhttps://git.duniter.org/nodes/typescript/duniter/-/issues/1379[mempool] expired certifications are accepted2019-06-02T12:10:56+02:00Cédric Moreau[mempool] expired certifications are acceptedWhile tracing accepted certifications by a node, I noticed that already written certifications still are in the mempool and gets replicated on the network.
It seems Duniter lacks a control on expiry date for mempool acceptance.While tracing accepted certifications by a node, I noticed that already written certifications still are in the mempool and gets replicated on the network.
It seems Duniter lacks a control on expiry date for mempool acceptance.1.7Cédric MoreauCédric Moreauhttps://git.duniter.org/nodes/typescript/duniter/-/issues/1237Resync g1.duniter.org cause : memberhips & certifications loss2018-03-07T21:06:56+01:00Benoit LavenierResync g1.duniter.org cause : memberhips & certifications lossDepuis la migration du noeud g1.duniter.org, plusieurs utilisateurs ont perdu leur dossier d'adhésion :
- CamilleL (attention elle avait envoyé plusieurs demandes, avec la même clef) : elle avait 5 certifications !
- Jean-Marie Toupin...Depuis la migration du noeud g1.duniter.org, plusieurs utilisateurs ont perdu leur dossier d'adhésion :
- CamilleL (attention elle avait envoyé plusieurs demandes, avec la même clef) : elle avait 5 certifications !
- Jean-Marie Toupin : il est retombé à 1 certification, alors qu'il en avait 4.
Est-il possible de restaurer ces dossiers ?
Merci pour euxHorizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/1152Change tx sandbox size2020-10-04T18:47:27+02:00ÉloïsChange tx sandbox sizehttps://forum.duniter.org/t/gbot-feeback-on-g1-test/3400/5?u=eloishttps://forum.duniter.org/t/gbot-feeback-on-g1-test/3400/5?u=elois1.10https://git.duniter.org/nodes/typescript/duniter/-/issues/1064Make sandbox pulling more frequent2018-01-27T07:27:42+01:00Cédric MoreauMake sandbox pulling more frequentLet's try 1 time every 4 hour now.Let's try 1 time every 4 hour now.1.4.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1053Duniter et le choix du contenu des blocs2018-01-27T07:27:43+01:00Cédric MoreauDuniter et le choix du contenu des blocs*Created by: gerard94*
Reference : [forum.duniter.org](https://forum.duniter.org/t/duniter-et-le-choix-du-contenu-des-blocs/2968)
As the peer to peer network brings already a bit of randomness in the choice of blocks contents, It could...*Created by: gerard94*
Reference : [forum.duniter.org](https://forum.duniter.org/t/duniter-et-le-choix-du-contenu-des-blocs/2968)
As the peer to peer network brings already a bit of randomness in the choice of blocks contents, It could be easier and more uniform to go on this way and randomize the whole contents as soon as concurrency is concerned.1.4.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1051Integrate valid TX when received invalid block2017-11-28T16:49:17+01:00Benoit LavenierIntegrate valid TX when received invalid blockVoici mon cas :
> - je viens de brancher Cesium sur mon noeud (duniter.fr)
> - j'ai passé 2 TX de paiement.
> - Aussitot les TX ont été inscrits dans un nouveau bloc par mon noeud, qu'il a ensuite émis.
> - mais un fork réseau s'e...Voici mon cas :
> - je viens de brancher Cesium sur mon noeud (duniter.fr)
> - j'ai passé 2 TX de paiement.
> - Aussitot les TX ont été inscrits dans un nouveau bloc par mon noeud, qu'il a ensuite émis.
> - mais un fork réseau s'est créé (les autre snoeuds ont rejetté mon bloc)
> Du coup, mes 2 TX, pourtant valides également pour la branche principale, restent bloqués... et ne sont pas visibles ailleurs que sur mon noeud.
Lorsque mon noeud sera à nouveau synchro, il ne va pas rediffuser les TX aux autres noeuds.
Bref, ne serait-ce pas une bonne idée de décapsuler les blocs invalides (redirigés vers la piscine, je crois), pour en prendre les TX, qui elles peuvent etre valides ?
En d'autres terme, un blocs invalid pourrait etre le véhicule de TX valides...https://git.duniter.org/nodes/typescript/duniter/-/issues/1036Sandboxes sync for non 24/7 nodes2018-01-27T07:27:42+01:00Cédric MoreauSandboxes sync for non 24/7 nodes*Created by: M5oul*
When are retrieve sandboxes informations for a diurnal node?
A node running 7/24 will sync his sandboxes every days.
For a diurnal one, will it happen? I am asking that as my node's sandboxes don't seems complete.
...*Created by: M5oul*
When are retrieve sandboxes informations for a diurnal node?
A node running 7/24 will sync his sandboxes every days.
For a diurnal one, will it happen? I am asking that as my node's sandboxes don't seems complete.
The best would be to sync sandboxes when restarting.
Not just when restarting as it could be annoying if restarting many times the node.
Sandboxes' sync could start ten minutes after the restart.1.4.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1027sandbox empty after reset data and sync2018-01-27T07:27:43+01:00Éloïssandbox empty after reset data and syncI apply `reset data` and `sync` command to my node `g1-monit.elois.org` and just after sync database sandbox is empty : https://librelois.fr/public/duniter-g1-33426.g1-monit.elois.org.db
I observe exactly the same behavior on my class...I apply `reset data` and `sync` command to my node `g1-monit.elois.org` and just after sync database sandbox is empty : https://librelois.fr/public/duniter-g1-33426.g1-monit.elois.org.db
I observe exactly the same behavior on my classic node `g1.elois.org`, so this behavior has no relationship with my module.1.4.0https://git.duniter.org/nodes/typescript/duniter/-/issues/994Sandbox pulling is too much frequent2018-01-27T07:27:44+01:00Cédric MoreauSandbox pulling is too much frequentAs said in #968. We could have only 1 sync / day, because the push mechanism should be enough. Also each time a node successfully pulls a new document, it shares it again through the push mechanism.
So 1 per day should really be enough.As said in #968. We could have only 1 sync / day, because the push mechanism should be enough. Also each time a node successfully pulls a new document, it shares it again through the push mechanism.
So 1 per day should really be enough.1.3.0https://git.duniter.org/nodes/typescript/duniter/-/issues/988Sync: also sync the sandboxes2018-01-27T07:27:44+01:00Cédric MoreauSync: also sync the sandboxesWe can trigger a sandbox pulling at the end of the sync, just after the peers for example.We can trigger a sandbox pulling at the end of the sync, just after the peers for example.1.3.0https://git.duniter.org/nodes/typescript/duniter/-/issues/932Have bigger identities + membership sandboxes2018-01-27T07:27:45+01:00Cédric MoreauHave bigger identities + membership sandboxesSee https://forum.duniter.org/t/piscines-pleines-problemes-et-solutions/2344See https://forum.duniter.org/t/piscines-pleines-problemes-et-solutions/23441.2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/931Always accept the identity of a valid stored certification2018-01-27T07:27:44+01:00Cédric MoreauAlways accept the identity of a valid stored certificationWhen a new certification is coming, if it has be checked to be valid and will be added to the certifications' sandbox of its issuer, then accept the certified identity.
In other words: bypass the identity sandbox restriction during th...When a new certification is coming, if it has be checked to be valid and will be added to the certifications' sandbox of its issuer, then accept the certified identity.
In other words: bypass the identity sandbox restriction during the acceptance of a certification.1.2.0Cédric MoreauCédric Moreauhttps://git.duniter.org/nodes/typescript/duniter/-/issues/930Only members should be able to send certifications2018-01-27T07:27:45+01:00Cédric MoreauOnly members should be able to send certificationsIt is already true in the blockchain, but let's apply this also to sandboxes.It is already true in the blockchain, but let's apply this also to sandboxes.1.2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/927Have a per member sandbox for certifications2018-01-27T07:27:44+01:00Cédric MoreauHave a per member sandbox for certificationsWe could imagine the sandbox of certifications to be per member.
Because as we know we have max sigWindow/sigDelay = 60 days / 5 days = 12 pending certifications issued per member, then `cert_sandbox_room = 12` would give us an absolu...We could imagine the sandbox of certifications to be per member.
Because as we know we have max sigWindow/sigDelay = 60 days / 5 days = 12 pending certifications issued per member, then `cert_sandbox_room = 12` would give us an absolute room size just depending on N.
So any certification would pass for any member as long as he limits himself to 12 concurrent certs, and be refused from non-members of course.1.2.0Cédric MoreauCédric Moreauhttps://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/69Horizon