fix: avoid noisy error log on starting new sessions #269
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Summary
First-time visitors with no session replay metadata in local storage would
get an error log related to the session data not being valid (it would be an empty object).
How did you test this change?
CI
Are there any deployment considerations?
no
Note
Adjusts
pruneSessionDatato only act on entries withlastPushTimeand removes error logging for non-session data, preventing noisy logs for new sessions.sdk/highlight-run/src/client/utils/sessionStorage/highlightSession.ts):pruneSessionDatato only consider items withlastPushTimebefore pruning.lastPushTime; keep debug log when removing stale data.Written by Cursor Bugbot for commit 3cecc11. This will update automatically on new commits. Configure here.