-
Notifications
You must be signed in to change notification settings - Fork 6
fix(cron): auto-disable cron jobs whose target channel is unreachable #211
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
Open
LIU9293
wants to merge
7
commits into
main
Choose a base branch
from
fix/cron-auto-disable-channel-not-found-04526a90
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
b66828f
fix(cron): auto-disable jobs whose target channel is unreachable
4decf95
fix(cron): bypass channel revalidation when auto-disabling
abc106f
fix(discord): forward DiscordAPIError code through resolveTextChannel…
e1a33ea
fix(delivery): handle Lark 'chat does not exist' and Discord mixed-bo…
1820940
fix(discord): require every fetch attempt to be permanent
1fdf52b
fix(cron): treat Lark's undefined-send as a permanent delivery failure
a831e9d
fix(discord): suppress permanent code on wrapper for mixed Discord fa…
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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 hidden or 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 hidden or 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.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
When a Lark cron job's channel/workspace credentials have been removed,
sendLarkChannelMessagereturnsundefinedinstead of throwing (packages/ims/lark/client.ts:383-384), so this await falls through the new permanent-error handling and the run is later marked completed while the job remains enabled and undelivered. Fresh evidence after the stale-channel fix is that the direct-SQL disable helper is never reached for this no-credentials Lark path because no error is raised.Useful? React with 👍 / 👎.
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.
Addressed in 1fdf52b.
sendResultToChannelnow checks the Lark return value and throwsLark send returned no message id for channel <id> (chat_not_found or credentials missing)whensendLarkChannelMessagereturnsundefined(the missing-credentials path atpackages/ims/lark/client.ts:383-384). The wrapper text embedschat_not_found, so the existingisPermanentChannelErrorcheck in therunCronJobcatch branch classifies it as permanent anddisableCronJobForPermanentChannelErrordisables the job — same terminal behavior as an explicitchat_not_foundAPI response, no more silent completed-but-undelivered runs.Also added a test in
permanent-error.test.ts(matches the synthetic 'Lark send returned no message id' wrapper) that pins the exact wrapper string to the classifier, so a future rewording of the wrapper cannot silently regress the auto-disable path. Full suite: 437 pass, 1 skip, 0 fail.