Skip to content

Conversation

@k-fish
Copy link
Member

@k-fish k-fish commented Nov 19, 2025

On issues details, this will add the error event into the logs list to give context as to where the error happened in time.

On issues details, this will add the error event into the logs list to give context as to where the error happened in time.
@k-fish k-fish requested a review from a team as a code owner November 19, 2025 16:15
@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Nov 19, 2025
__isPseudoRow: true,
__originalEvent: event,
} as PseudoLogResponseItem;
}
Copy link
Contributor

Choose a reason for hiding this comment

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

Bug: Missing ORGANIZATION_ID in pseudo log response item

The PseudoLogResponseItem interface requires ORGANIZATION_ID as a mandatory number field, but the createPseudoLogResponseItem function doesn't provide this field when creating the object. This could cause runtime issues where code expects the field to exist but finds it missing. The function should either accept an organizationId parameter or extract it from the event object.

Fix in Cursor Fix in Web

Comment on lines +99 to +102
const eventMoment = moment(eventTimestamp);
const start = getUtcDateString(eventMoment.clone().subtract(1, 'day'));
const end = getUtcDateString(eventMoment.clone().add(1, 'day'));
const environment = getEventEnvironment(event);
Copy link
Member

Choose a reason for hiding this comment

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

Could this create an end timestamp in the future? Does the time selector handle that gracefully?

Copy link
Member Author

Choose a reason for hiding this comment

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

It does create an end?

Comment on lines 185 to 188
const timestamps = data
.filter((row): row is OurLogsResponseItem => isRegularLogResponseItem(row))
.map(row => getLogRowTimestampMillis(row))
.filter(Boolean);
Copy link
Member

Choose a reason for hiding this comment

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

Can this just map over baseData?

@k-fish k-fish enabled auto-merge (squash) November 19, 2025 16:56
return -1;
}
const event = additionalData.event;
const eventTimestamp = new Date(event.dateCreated || new Date()).getTime();
Copy link
Contributor

Choose a reason for hiding this comment

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

Bug: Pseudo row positioned incorrectly if event lacks dateCreated

When calculating where to insert the pseudo row, the code falls back to the current time (new Date()) if event.dateCreated is missing. This means events without a dateCreated will always appear at or near the end of the log list, regardless of their actual timestamp. The code should use event.dateReceived as a fallback like the drawer does, or handle missing timestamps more gracefully.

Fix in Cursor Fix in Web

@k-fish k-fish merged commit b2a8586 into master Nov 19, 2025
47 checks passed
@k-fish k-fish deleted the fix/ourlogs/highlight-error-event branch November 19, 2025 17:07
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