Activity
-
-
-
19bab0ed · feat: increase COUNT_INTERVAL to 20
-
-
-
pushed new branch duniter-v2s-issue-123-industrialize-releases at nodes / rust / modules / duniter-gva
-
commented on merge request !5 "feat(bma) add `get_written_transactions_for_bma()` and `get_pending_transactions_for_bma()` - close #1" at nodes / rust / modules / duniter-gva
À noter qu'il existait une anomalie similaire corrigée dans
async-graphql
en version4.0.0
.... -
commented on merge request !5 "feat(bma) add `get_written_transactions_for_bma()` and `get_pending_transactions_for_bma()` - close #1" at nodes / rust / modules / duniter-gva
Regarde bien les erreurs dans la CI : ce sont plutôt des soucis GraphQL j'ai l'impression (lors des tests exécutés via
cargo test --all --all-features
... -
-
563c843b · feat: update Cargo.lock
-
-
-
-
1938afc4 · fix: run `cargo clippy --fix` and `cargo update`
-
-
-
14730fae · Drop redshift tag
-
-
-
3999f353 · cargo update -p duniter-core
- ... and 1 more commit. Compare 68218021...3999f353
-
-
-
68218021 · Bump dependencies
-
-
-
d2dc354e · Downgrade async-bincode to v0.6.1
-
-
-
551dace3 ·
-
-
-
46c18030 · cargo update -p async-bincode
-
-
-
551dace3 · fix(1): Revert cargo.lock, and update it manually
-
-
commented on merge request !5 "feat(bma) add `get_written_transactions_for_bma()` and `get_pending_transactions_for_bma()` - close #1" at nodes / rust / modules / duniter-gva
Je suis toujours bloqué......
-
-
9f293035 · fix(1): upgrade async-bincode to 0.7.1
-
-
-
2660d326 · fix(1): run cargo update
-
-
commented on merge request !5 "feat(bma) add `get_written_transactions_for_bma()` and `get_pending_transactions_for_bma()` - close #1" at nodes / rust / modules / duniter-gva
cargo update
puis commiter le Cargo.lock qui va pointer sur le bon hash de commit présent sur la branche master de duniter-core.