Skip to content

Conversation

@MSzalowski
Copy link
Contributor

@MSzalowski MSzalowski commented Mar 4, 2025

List of changes

  • This might break the tests.
    Confirmation of the transaction now happens once the metadata are existing on chain (it increases drastically time of the transaction to be confirmed (~2m diff between existing transaction in db sync and metadata for that transaction)

Checklist

  • related issue
  • My changes generate no new warnings
  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the changelog
  • I have added tests that prove my fix is effective or that my feature works

@github-actions
Copy link
Contributor

github-actions bot commented Mar 4, 2025

✅ All checks succeeded

2 similar comments
@github-actions
Copy link
Contributor

github-actions bot commented Mar 4, 2025

✅ All checks succeeded

@github-actions
Copy link
Contributor

github-actions bot commented Mar 4, 2025

✅ All checks succeeded

@MSzalowski MSzalowski requested a review from placek March 5, 2025 09:35
@MSzalowski MSzalowski force-pushed the fix/3080-drep-re-registration-always-shows-the-previous-metadata-not-the-new-one branch from f3a00f4 to 888fa7a Compare March 5, 2025 10:14
@github-actions
Copy link
Contributor

github-actions bot commented Mar 5, 2025

❌ Docker Image Scan (Dockle) failed

No output

@github-actions
Copy link
Contributor

github-actions bot commented Mar 5, 2025

✅ All checks succeeded

1 similar comment
@github-actions
Copy link
Contributor

github-actions bot commented Mar 5, 2025

✅ All checks succeeded

@MSzalowski MSzalowski force-pushed the fix/3080-drep-re-registration-always-shows-the-previous-metadata-not-the-new-one branch from 888fa7a to b0bc417 Compare March 7, 2025 07:09
@github-actions
Copy link
Contributor

github-actions bot commented Mar 7, 2025

✅ All checks succeeded

2 similar comments
@github-actions
Copy link
Contributor

github-actions bot commented Mar 7, 2025

✅ All checks succeeded

@github-actions
Copy link
Contributor

github-actions bot commented Mar 7, 2025

✅ All checks succeeded

@MSzalowski MSzalowski force-pushed the fix/3080-drep-re-registration-always-shows-the-previous-metadata-not-the-new-one branch from b0bc417 to d656284 Compare March 14, 2025 13:00
@github-actions
Copy link
Contributor

✅ All checks succeeded

2 similar comments
@github-actions
Copy link
Contributor

✅ All checks succeeded

@github-actions
Copy link
Contributor

✅ All checks succeeded

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

🐛 DRep re-registration always shows the previous metadata, not the new one 🐛 Delay in Reflecting dRep Metadata Updates

3 participants