Skip to content

Conversation

jfrain99
Copy link
Contributor

@jfrain99 jfrain99 commented Jan 7, 2025

Before, the CU was searching for old evaluations (findEvaluation) through processId, timestamp, ordinate, cron. Now, only search by processId and messageId to find duplicate assignments.

Closes #1091

@jfrain99 jfrain99 force-pushed the jfrain99/check-assignments-by-message-id-cu branch from 51012d6 to b572f49 Compare January 7, 2025 20:58
@jfrain99 jfrain99 force-pushed the jfrain99/check-assignments-by-message-id-cu branch from b572f49 to 4d3e8bf Compare January 7, 2025 21:09
@jfrain99 jfrain99 requested review from TillaTheHun0 and removed request for TillaTheHun0 January 8, 2025 15:44
Comment on lines 22 to +24
return findEvaluation({
processId: ctx.id,
to: ctx.to,
ordinate: ctx.ordinate,
cron: ctx.cron
messageId: ctx.messageId
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are cases where messageId will be undefined, like the case of requests to /cron and /dry-run.

Perhaps this should attempt to call findEvaluation iff messageId is provided?

@jfrain99 jfrain99 added the hold label Jan 16, 2025
@TillaTheHun0
Copy link
Collaborator

Please continue to hold on this change, as it seems the ecosystem has coded to the existing behavior, and so we might need to keep it around.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix(cu): return previous assignment evaluation on duplicate

2 participants