Skip to content

Conversation

@Abdkhan14
Copy link
Contributor

No description provided.

@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Dec 6, 2025
true
);
const startTimestamp = 'start_timestamp' in event ? event.start_timestamp : undefined;
// TODO Abdullah Khan: Clean this up once getRepresentativeTraceEvent is moved to the TraceTree class
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Addressed this here: #104503

@Abdkhan14 Abdkhan14 requested a review from gggritso December 9, 2025 01:33
@Abdkhan14 Abdkhan14 marked this pull request as ready for review December 9, 2025 01:33
'timestamp' in event
? event.timestamp
: 'event_timestamp' in event && typeof event.event_timestamp === 'number'
? event.event_timestamp
Copy link
Contributor

Choose a reason for hiding this comment

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

Bug: Wrong property name causes missing duration for EAP events

The code checks for event_timestamp but this property doesn't exist on any TraceTree.TraceEvent type. For EAPSpan and UptimeCheck events, the end time is stored in end_timestamp, not event_timestamp. This causes the duration calculation to fail for these event types, returning '\u2014' instead of the actual duration. The condition should check for 'end_timestamp' in event rather than 'event_timestamp' in event.

Fix in Cursor Fix in Web

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

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants