[fix] Optimize access to sources by pubkey, using specific index

[fix] Optimize access to sources by pubkey, using specific index for complex condition - Close #1438 (closed)

changed milestone to %1.9

requested review from @c-geek

added 1 commit

• 9c1aee50 - [fix] Delete or update 'indexOfComplexeConditionForPubkeys' when removing a block

Compare with previous version

added 1 commit

• 3479d265 - [fix] Remove debug logger in getAvailableSourcesByPubkey()

Compare with previous version

added 5 commits

• 3479d265...f12d6871 - 2 commits from branch dev
• 5ec7a750 - [fix] Optimize access to sources by pubkey, using specific index for complex...
• e7dbaebe - [fix] Delete or update 'indexOfComplexeConditionForPubkeys' when removing a block
• df403420 - [fix] Remove debug logger in getAvailableSourcesByPubkey()

Compare with previous version

added 5 commits

• 15f88fed - [fix] Optimize access to sources by pubkey, using specific index for complex...
• 9c1aee50 - [fix] Delete or update 'indexOfComplexeConditionForPubkeys' when removing a block
• 3479d265 - [fix] Remove debug logger in getAvailableSourcesByPubkey()
• 6dc02844 - Merge remote-tracking branch 'origin/fix/1438/optimize_sources_by_pubkey' into...
• 4148dfe2 - [fix] fix format using Prettier

Compare with previous version

added 7 commits

• 2e0fdded - [fix] Optimize access to sources by pubkey, using specific index for complex...
• f02367a6 - [fix] Delete or update 'indexOfComplexeConditionForPubkeys' when removing a block
• 0a7ac064 - [fix] Remove debug logger in getAvailableSourcesByPubkey()
• 8da8c7a7 - [fix] Optimize access to sources by pubkey, using specific index for complex...
• 42913bae - [fix] Delete or update 'indexOfComplexeConditionForPubkeys' when removing a block
• e11261d6 - [fix] fix format using Prettier
• e6611f3c - Merge remote-tracking branch 'origin/fix/1438/optimize_sources_by_pubkey' into...

Compare with previous version

Je viens de jeter un œil, pour l'instant je ne vois rien à redire, c'est très propre

Il me faudrait y regarder de plus près pour être vraiment convaincu, mais ce ne sera pas ce soir

Dans la mesure où il s'agit de code d'API, et non de protocole, il n'y a pas de risque de casser le protocole blockchain. Au pire, les clients ne pourront pas payer, c'est un problème à relativiser.

De plus les tests couvrent la plupart du code donc je suis confiant.

OK pour moi.

approved this merge request

merged

mentioned in commit 9a08389c

mentioned in issue clients/python/duniterpy#201 (closed)

mentioned in commit 5d59fe17

mentioned in merge request !1428 (merged)

mentioned in commit a6891711

mentioned in commit d6eb97ca

changed milestone to %1.8.7