You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Slack messages now split into daily and hourly notifications.
Hourly activates event reminder notifications which sends a reminder to teams 48, 24, and 1 hour before the event.
Notes
Any other notes go here
Test Cases
Postman test to make sure events only fire once on 48, 24 and 1 hour intervals
Tests to make sure teams are collected correctly
Checklist
It can be helpful to check the Checks and Files changed tabs.
Please review the contributor guide and reach out to your Tech Lead if anything is unclear.
Please request reviewers and ping on slack only after you've gone through this whole checklist.
All commits are tagged with the ticket number
No linting errors / newline at end of file warnings
All code follows repository-configured prettier formatting
No merge conflicts
All checks passing
Screenshots of UI changes (see Screenshots section)
Remove any non-applicable sections of this template
Assign the PR to yourself
No yarn.lock changes (unless dependencies have changed)
Request reviewers & ping on Slack
PR is linked to the ticket (fill in the closes line below)
The reason will be displayed to describe this comment to others. Learn more.
I think the root cause is GitHub scheduler. The new hourly workflow still uses GitHub's scheduler, so it'll be delayed too. Late runs won't send reminders after the meeting anymore, but they'll skip reminders: any 1-hour reminder whose run is more than about an hour late gets dropped. Can you look into other ways to do this? I'm thinking of triggering /notifications/hourly and /notifications/daily from AWS EventBridge Scheduler instead of GitHub cron, since the backend is already on AWS, but lmk if you find something different
This makes the seed helper silently fall back to the wall clock whenever a caller omits either bound. The seed-time contract explicitly says generation is anchored to SEED_REFERENCE_DATE and that only realNow() may use the real clock, so a future unbounded call would make CI data nondeterministic. Keep from and to required and pass them directly to Faker.
Plain curl exits successfully for HTTP 401/500 responses, so a failed daily notification request will be recorded as a successful workflow run and will not be surfaced for retry. Use the same fail-on-HTTP-error behavior as the hourly workflow.
Keep seed date bounds required for deterministic behavior
src/backend/src/prisma/dates.ts:10
This makes the seed date helper silently fall back to wall-clock time whenever a caller omits a bound, reintroducing the nondeterminism that seed-time.ts explicitly forbids. The previous signature required both dates, and all current callers already pass them; keep both parameters required instead of using Date.now().
The reason will be displayed to describe this comment to others. Learn more.
Since this schedule is back after the revert, once the bay container is live, won't every message will go out twice. Can we switch it to workflow_dispatch?
Also, should figure out if the bay compose file has restart: unless-stopped, and whether it come back up after a reboot, since it'll be the only thing sending notifications now
The reason will be displayed to describe this comment to others. Learn more.
The endpoint does all its Slack sends before it responds, and the default timeout is 60s. On a slow Slack day this logs FAILED even though the messages went out. Make it timeoutMs: 10 * 60_000?
This branch has not been deployed
No deployments
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
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.
Changes
Slack messages now split into daily and hourly notifications.
Hourly activates event reminder notifications which sends a reminder to teams 48, 24, and 1 hour before the event.
Notes
Any other notes go here
Test Cases
Checklist
It can be helpful to check the
ChecksandFiles changedtabs.Please review the contributor guide and reach out to your Tech Lead if anything is unclear.
Please request reviewers and ping on slack only after you've gone through this whole checklist.
yarn.lockchanges (unless dependencies have changed)Closes #4412 (issue #)