Ryan Albrecht

> I don't think we need to do a snippet per say, rather we just fast forward the replay to (just as an example) 5 secs before the error. The...

I think this is a start/finish timestamp issue - The replay says: `finishedAt = "2022-08-18T14:54:58+00:00"` (note: 58th second) - The last segment has a timestamp of: `dateAdded: "2022-08-18T14:54:59.058074Z"` (note: 59th...

Related to https://github.com/getsentry/sentry-replay/issues/148

I think this is fixed now by https://github.com/getsentry/sentry/pull/40281 The improvement is inside of static/app/utils/replays/replayReader.tsx, the `finishedAt` timestamp usually has `ms` precision, and we're using that to re-calculate the `duration`. That...

There are three examples in the thread above that are still available, they're all working great now: - Example From Sept 1st (https://github.com/getsentry/sentry/issues/38000#issuecomment-1234378274) - Example From Sept 19 (https://github.com/getsentry/sentry/issues/38000#issuecomment-1251423672) -...

> when you click the link in the header, does it also filter the console by all errors? @Jesse-Box yes, right now it's filtering to show all errors because we've...

Found an issue with this: when there are no sentry errors clicking the link in the header will set the console filter, but 'error' isn't in the list, so it...

The part from the other ticket that needs to be included here are these query params: ``` t_main: 'console', f_c_logLevel: 'error', f_c_search: undefined, ``` they need to be passed over...

I wonder if this is related to the missing-segment issue, causing dropped frames, so we're unable to read the dom.

Ok, since this is missing some segments and that is a known problem I think this can be closed. Last segment is id=19, it's missing missing 8, 9, 11, 13,...