Skip to content

fix(fortuna): set last_updated_at correctly, use ms precision #2937

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 7, 2025

Conversation

tejasbadadare
Copy link
Contributor

Summary

  • Update timestamp precision to milliseconds
  • Set last_updated_at after we get back the tx receipt (or lack thereof)
    • I would've liked to add an assertion for this but this business logic doesn't have tests

Rationale

How has this been tested?

  • Current tests cover my changes
  • Added new tests
  • Manually tested the code

Copy link

vercel bot commented Aug 7, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
api-reference ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 7, 2025 9:19pm
component-library ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 7, 2025 9:19pm
developer-hub ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 7, 2025 9:19pm
entropy-debugger ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 7, 2025 9:19pm
entropy-explorer ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 7, 2025 9:19pm
insights ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 7, 2025 9:19pm
proposals ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 7, 2025 9:19pm
staking ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 7, 2025 9:19pm

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.

2 participants