Peut-être c’est dû au runtime non encore mis-à-jour; mais j’ai des logs qui se répètent pour le SMITH: Storage("CurrentPeriodIndex value not found")
duniter-v2s-gdev-validator | 2024-11-30 21:23:24 Storage("CurrentPeriodIndex value not found")
duniter-v2s-gdev-validator | 2024-11-30 21:23:24 🏆 Imported #4131320 (0x3780…ebb8 → 0x61f4…1ff6)
duniter-v2s-gdev-validator | 2024-11-30 21:23:24 🆕 Imported #4131320 (0x3780…ebb8 → 0x4527…ffbf)
duniter-v2s-gdev-validator | 2024-11-30 21:23:27 💤 Idle (16 peers), best: #4131320 (0x61f4…1ff6), finalized #4131318 (0x8f45…a91e), ⬇ 18.8kiB/s ⬆ 14.2kiB/s
duniter-v2s-gdev-validator | 2024-11-30 21:23:30 Storage("CurrentPeriodIndex value not found")
duniter-v2s-gdev-validator | 2024-11-30 21:23:30 🏆 Imported #4131321 (0x61f4…1ff6 → 0xde92…4bab)
duniter-v2s-gdev-validator | 2024-11-30 21:23:32 💤 Idle (16 peers), best: #4131321 (0xde92…4bab), finalized #4131319 (0x3780…ebb8), ⬇ 20.4kiB/s ⬆ 14.0kiB/s
duniter-v2s-gdev-validator | 2024-11-30 21:23:36 Storage("CurrentPeriodIndex value not found")
Et toujours des erreurs pour l’oracle toutes les 200 secondes:
distance-oracle | thread 'main' panicked at /root/distance-oracle/src/api.rs:50:10:
distance-oracle | Cannot fetch current pool index: Metadata(IncompatibleCodegen)
distance-oracle | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
distance-oracle | Waiting 200 seconds before next execution...