Skip to content

fix: handle unset fee/reward change timestamps in orchestrator list#586

Merged
rickstaa merged 1 commit intomainfrom
fix/incorrect-fee-reward-change-value
Mar 9, 2026
Merged

fix: handle unset fee/reward change timestamps in orchestrator list#586
rickstaa merged 1 commit intomainfrom
fix/incorrect-fee-reward-change-value

Conversation

@rickstaa
Copy link
Member

@rickstaa rickstaa commented Mar 9, 2026

Summary

  • Fix orchestrators with unset fee/reward timestamps showing ~20521 days ago (days since Unix epoch) instead of "Never"
  • Use the latest non-zero timestamp between feeShareUpdateTimestamp and rewardCutUpdateTimestamp, treating 0 as unset
  • Display "Never" when neither timestamp has been set

Closes #585

Test plan

  • Verify orchestrators that have never changed params show "Never" for latest fee/reward change
  • Verify orchestrators that changed params today show "0 days ago" (not "Never")
  • Verify orchestrators with valid timestamps still show correct "X days ago" values

🤖 Generated with Claude Code

Use the latest of feeShareUpdateTimestamp and rewardCutUpdateTimestamp
(ignoring 0 values) and display "Never" when neither has been set,
instead of computing days since Unix epoch (~20521 days).

Closes #585

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings March 9, 2026 20:41
@rickstaa rickstaa requested a review from ECWireless as a code owner March 9, 2026 20:41
@vercel
Copy link
Contributor

vercel bot commented Mar 9, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
explorer-arbitrum-one Ready Ready Preview, Comment Mar 9, 2026 8:43pm

Request Review

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Fixes the orchestrator yield popover so “Latest fee/reward change” no longer shows an absurd “~20521 days ago” when the subgraph returns 0 for unset fee/reward update timestamps. The change treats 0 as “unset”, uses the latest non-zero timestamp across fee/reward updates, and displays “Never” when neither has been set.

Changes:

  • Compute a single latestChangeTimestamp as the max of feeShareUpdateTimestamp and rewardCutUpdateTimestamp, treating missing values as 0.
  • Render “Never” when the computed latest timestamp is unset (0), otherwise render “X days ago”.
  • Update mapped row fields to store null for “never updated” values rather than computing a diff from Unix epoch.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@rickstaa rickstaa merged commit 10b6950 into main Mar 9, 2026
12 checks passed
@rickstaa rickstaa deleted the fix/incorrect-fee-reward-change-value branch March 9, 2026 22:33
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.

Bug: 'Latest fee/reward change' shows ~20521 days ago for orchestrators with unset timestamps

2 participants