-
Notifications
You must be signed in to change notification settings - Fork 1
bug(sentry): Flatten nested objects in backtrace frame arguments using dot notation #509
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Co-authored-by: neSpecc <3684889+neSpecc@users.noreply.github.com>
Co-authored-by: neSpecc <3684889+neSpecc@users.noreply.github.com>
neSpecc
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@copilot remove unrelated changes like listing of files that should not be affected by your solution
…tion Co-authored-by: neSpecc <3684889+neSpecc@users.noreply.github.com>
Removed unrelated files. Only the 3 Sentry worker files remain in the changeset (eb368a5). Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
…g dot notation (#509) (#510) * Initial plan * Implement dot notation for nested objects in backtrace frame arguments * Fix empty array handling to be consistent with empty objects * Remove unrelated file changes that should not be affected by the solution --------- Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com> Co-authored-by: neSpecc <3684889+neSpecc@users.noreply.github.com>
* bug(sentry): Flatten nested objects in backtrace frame arguments using dot notation (#509) * Initial plan * Implement dot notation for nested objects in backtrace frame arguments Co-authored-by: neSpecc <3684889+neSpecc@users.noreply.github.com> * Fix empty array handling to be consistent with empty objects Co-authored-by: neSpecc <3684889+neSpecc@users.noreply.github.com> * Remove unrelated file changes that should not be affected by the solution Co-authored-by: neSpecc <3684889+neSpecc@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: neSpecc <3684889+neSpecc@users.noreply.github.com> * chore(setup): migrate from node 16 to 24 (#512) * Upgrade to Node.js 24 and update TypeScript config Update all workflows, Dockerfiles, and .nvmrc to use Node.js 24 for consistency and latest features. Enable 'moduleResolution: node' and 'skipLibCheck' in tsconfig.json to improve TypeScript compatibility and speed up builds. * upd packages * Update jest.setup.redis-mock.js * Update jest.global-teardown.js * fix tests * Update jest.setup.redis-mock.js * disable redis tests * rm skip * Update jest.config.js * rm skips * lint code --------- Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com> Co-authored-by: neSpecc <3684889+neSpecc@users.noreply.github.com> Co-authored-by: Peter <specc.dev@gmail.com>
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.