-
Notifications
You must be signed in to change notification settings - Fork 322
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
fix: router destinationsMap access #2582
Conversation
Codecov ReportBase: 43.97% // Head: 43.95% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #2582 +/- ##
==========================================
- Coverage 43.97% 43.95% -0.02%
==========================================
Files 187 187
Lines 39082 39082
==========================================
- Hits 17185 17180 -5
- Misses 20817 20823 +6
+ Partials 1080 1079 -1
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
@Sidddddarth we may need to fail events for which no configuration can be found instead of aborting them. A test scenario for this would be desirable too. |
02090f6
to
fd0aeb3
Compare
worker.rt.configSubscriberLock.RUnlock() | ||
if !ok { | ||
status := jobsdb.JobStatusT{ | ||
JobID: job.JobID, | ||
AttemptNum: job.LastJobStatus.AttemptNum, | ||
JobState: jobsdb.Aborted.State, | ||
JobState: jobsdb.Failed.State, |
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.
@Sidddddarth we need to update the status of the job in the barrier, since failed jobs are notified early, at this stage
Description
Accessing
destination
without checking for its existence first. Fixes that.Notion Ticket
fix: router destination map access
Security