-
Notifications
You must be signed in to change notification settings - Fork 48
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Several fixes for inline script attribution (#90)
* Fix stacktrace regex * Use CDP for analysing stack traces (mostly rollback of https://dub.duckduckgo.com/duckduckgo/tds-crawler/commit/ca83d0a05de5d4985769cd5cc83047a17e0629b4) * Fix collected arguments type * Use non-pausing breakpoints when possible * Ignore non-http attribution urls (e.g. webpack-internal://) * Resume all breakpoints, including those from debugger; statements * Clean up some duplicated code * Tweak stack trace parsing * Bump eslint * Add more tests for APICallCollector * optional chaining requires Node >= 14 * Use scriptParsed.embedderName as it contains the non-sourcemapped script url * Make runtime JS stacks more verbose for better API attribution * Do not use chalk inside APICallCollector * Revert "optional chaining requires Node >= 14" This reverts commit 1ce25fb. * Method cleanup * Shortcut url parsing with a labeled break * Resume debugger as soon as possible without waiting * Always collect cookie arguments in the breakpoint script, for consistent output format * Add an integration test for API attribution * Switch most attribution tests to 3rd-party * Add more descriptive comments about attribution failures * Move the breakpoint script to a separate file * add an attribution test case * Ignore TS errors in breakpoint template * More descriptive test errors * Add retries to CI tests
- Loading branch information
Showing
13 changed files
with
3,485 additions
and
979 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
Oops, something went wrong.