Billy Vong

~~I was able to install the plugin using nvim v0.2.2 via homebrew HEAD. If it installs successfully you should see:~~ ``` remote/host: node host registered plugins ['nvim-parinfer.js', 'jest'] ``` ~~Try...

@ryan953 Here's one where it looks like finishedAt == last segment but it's overflowing: https://sentry.io/organizations/sentry-emerging-tech/replays/billy-test:a059b6139367467aab10579061436c47/ Maybe because we lose precision with the `duration` from the replay record? `duration` is 5,...

This should be fixed by https://github.com/getsentry/sentry-replay/pull/169

Going to see if the cause for duplicate segment ids has also fixed this -- I believe there were still instances where this was overflowing.

https://sentry.io/organizations/sentry/replays/javascript:952bb398d92242afa05a3676afb08443/?referrer=%2Forganizations%2F%3AorgId%2Freplays%2F&t_main=network

https://sentry.io/organizations/sentry/replays/javascript:4f3fdfe947b1497cb0ce98710bcf5e26/?referrer=%2Forganizations%2F%3AorgId%2Freplays%2F

This is an issue where the backend is storing the start/finish + duration in seconds (and losing the ms precision), but our UI uses the difference of "min_timestamp(replay_events)" and "max_timestamp(replay_events)"...

I think @ryan953 is going to change the frontend behavior to not use the timestamps that lack ms precision.

@chemzqm It's in `.yarn/sdks/eslint/bin/eslint.js` and in my `.vim/coc-settings.json` I have this config: `"eslint.nodePath": ".yarn/sdks"`. (This was done by the `pnpify` package). I've also tried the full path and it does...

Also odd, my TSC works fine: