Repository navigation
telemetry(crash): name the step a crash happened in - #24
Merged
Merged
Conversation
pdf-lib's errors are all named plain "Error", so every PDF crash reported the same `crash: Error`, and telemetry couldn't say where it failed. processFile now tracks a step (read, strip, assemble) and any processor can refine it. stripPdf names the Info field, xmp, custom and save. Steps are fixed names from our own code, never text from the file.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Crash reasons now say where the crash happened.
stripPdfmarksinfo:<Key>for each Info field, thenxmp,customandsave. Other formats reportread,striporassembleuntil they mark their own.Steps are fixed strings from our code, so the reason still never carries text from the file.
Evidence
Monday, 5 Januarygivescrash: Error. That is the same reason as the production failures on 6 and 31 Oct.After: the same file gives
crash: Error at info:CreationDate.305 tests pass, typecheck and lint clean.
Merge Danger
Door: two-way
Blast Radius: telemetry
No user-facing change. The crash reason string changes, so queries matching exactly
crash: ErrorneedILIKE 'crash%'. The malformed date crash itself is not fixed here.