Skip to content
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.

Sign up for GitHub

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

Jump to bottom

2.7.3 possibly broke Activejob with Sidekiq #850

Closed
nateberkopec opened this issue Jun 20, 2018 · 2 comments
Closed

2.7.3 possibly broke Activejob with Sidekiq #850

nateberkopec opened this issue Jun 20, 2018 · 2 comments
Labels
needs-repro Type: Bug
Projects
3.x

Comments

@nateberkopec
Copy link
Contributor

No description provided.

@jacquescrocker
Copy link

Context: 2.7.3 is not sending ActiveJob parameters when reporting errors to Sentry. Testing on 2.7.2 to see if the issue persists there

@jacquescrocker
Copy link

Ok, I've confirmed version 2.7.2 of the gem does send the arguments correctly:

On 2.7.2 (arguments)
screen shot 2018-06-20 at 4 18 05 pm

On 2.7.3 (no arguments)
screen shot 2018-06-20 at 4 19 24 pm

@st0012 st0012 added this to Needs triage in 3.x Aug 28, 2020
@st0012 st0012 closed this as completed Dec 10, 2020
3.x automation moved this from Needs triage to Closed Dec 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
needs-repro Type: Bug
Projects
3.x
  
Closed
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jacquescrocker @nateberkopec @st0012