Merged
Conversation
* feat: prefix support for drep / CIP-0129 * feat: fix logic / failed tests * feat: spotless * feat: add tests for drep prefix * feat: move drep id prefix code to ProcessContructions * feat: new tests for vote delegation / fail by error code * feat: fix pom conflict * feat: unused imports * refactor: use either instead of throwing exception within a code block. --------- Co-authored-by: Mateusz Czeladka <mateusz.czeladka@cardanofoundation.org>
* feat: SPO / dReps governance actions voting support * chore: postman collection fix. --------- Co-authored-by: Mateusz Czeladka <mateusz.czeladka@cardanofoundation.org>
Co-authored-by: Mateusz Czeladka <mateusz.czeladka@cardanofoundation.org>
Co-authored-by: Mateusz Czeladka <mateusz.czeladka@cardanofoundation.org>
Co-authored-by: Mateusz Czeladka <mateusz.czeladka@cardanofoundation.org>
matiwinnetou
force-pushed
the
develop
branch
2 times, most recently
from
27d4d41 to
a4c60eb
Compare
* chore: bump mithril version * chore: mithril bump
matiwinnetou
force-pushed
the
develop
branch
4 times, most recently
from
95ea302 to
05867d8
Compare
…+index concatenated.
…ntinue-on-parse-error in case there is a problem processing a block (#502) Co-authored-by: Mateusz Czeladka <mateusz.czeladka@cardanofoundation.org>
**Context**
When using Mithril on mainnet and the node is fully synced, batches of
~200 blocks are written efficiently.
When the node is syncing without mithril, yaci-store processes blocks
sequentially, reducing sync performance.
In docker-compose setup, Yaci Store currently starts before the Cardano
node has fully synced to the tip. This can lead to sync inefficiencies
or unpredictable behaviour.
The unpredictable behavior is not related to data consistency, as long
as blocks already synced by the indexer are not reprocessed. However,
during node sync, the chain tip keeps moving, causing yaci-store to
switch between sequential and parallel modes, resulting in inconsistent
performance.
**Tests to Do**
- [ ] 1. sync test wtih SYNC=true, MITHRIL=true
***Expected behaviour***
- [ ] Indexer should fully sync without being stuck
- [ ] DB, indexer and API should should start once the node is at the
tip
- [ ] 2. sync test with SYNC=true, MITHRIL=false
***Expected behaviour***
- [ ] Indexer should fully sync without being stuck
- [ ] DB, indexer and API should should start once the node is at the
tip
- [ ] 3. sync test with SYNC=false, MITHRIL=true
***Expected behaviour***
- [ ] Indexer should fully sync without being stuck
- [ ] DB, indexer and API should would start together
- [ ] 4. sync test with SYNC=false, MITHRIL=false
***Expected behaviour***
- [ ] Indexer should be stuck
- [ ] DB, indexer and API should would start together
- [ ] Also test the offline mode set SYNC to false
…o new governance_action_hash param - Updated key governance_action (`71676f7665726e616e63655f616374696f6e`) to governance_action_hash (`76676f7665726e616e63655f616374696f6e5f68617368`) - Updated governance_action_hash from value map(2) (`a26574785f696478403430633261343266653332343735396136343064636664646263363965663265336237666535613939386166386436363630333539373732626634346339646365696e64657800`) to text(66) (`7842343063326134326665333234373539613634306463666464626336396566326533623766653561393938616638643636363033353937373262663434633964633030`)
matiwinnetou
force-pushed
the
develop
branch
3 times, most recently
from
6960401 to
c7376ee
Compare
|
…nfig path for single docker (#545)
matiwinnetou
force-pushed
the
develop
branch
4 times, most recently
from
e17d197 to
1913a95
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.