Open Bug 1447804 Opened 7 years ago Updated 2 years ago

Normandy client should handle IO errors when reading telemetry pings

Categories

(Firefox :: Normandy Client, defect)

defect

Tracking

()

Tracking Status
firefox61 --- affected

People

(Reporter: mythmon, Unassigned)

References

()

Details

(Whiteboard: [nightly-js-sentry:3319576])

This bug was automatically filed from Sentry: https://sentry.prod.mozaws.net/operations/nightly-js-errors/issues/3319576/ It seems that when loading telemetry pings for the filter expression context, we don't handle errors while reading pings. Error: 1521592533158 app.normandy.recipe-runner ERROR Error checking filter for "Pref Flip - Search Composition new users in Release 57 - Bug 1413565". Filter: [( [normandy.userId]|bucketSample(10, 990, 1000) && normandy.channel == 'release' && normandy.version >= '57.0' && ((!normandy.telemetry.main.environment.profile.creationDate && normandy.isFirstRun) || normandy.telemetry.main.environment.profile.creationDate > 17483) && 'browser.search.widget.inNavBar'|preferenceValue == false )]. Error: "PingReadError: uncaught exception: Buffer is too short (no header) - Data: <redacte profile path>/datareporting/archived/2018-03/<redacted>.saved-session.jsonlz4" at App_append(undefined:797:9) at log(undefined:435:7) at error(undefined:443:5) at checkFilter(undefined:342:7) at throw(undefined:1230:9)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.