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.

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: single rejection caused cache cron to fail #18239

Merged
merged 1 commit into from
Dec 18, 2024
Merged

Conversation

zomars
Copy link
Member

@zomars zomars commented Dec 18, 2024

What does this PR do?

follow up to #18237 #18224

This pull request includes changes to improve the handling of calendar subscriptions and simplify the repository code. The most important changes include modifying the way promises are handled in the handleCalendarsToWatch function, removing unnecessary feature repository checks, and updating the SelectedCalendarRepository class.

Improvements to calendar subscription handling:

  • packages/features/calendar-cache/api/cron.ts: Changed from using Promise.all to Promise.allSettled for handling calendar watch and unwatch operations, and simplified the response object by removing detailed success/failure counts.

Codebase simplification:

  • Fixes #XXXX (GitHub issue number)
  • Fixes CAL-XXXX (Linear issue number - should be visible at the bottom of the GitHub issue description)

Mandatory Tasks (DO NOT REMOVE)

  • I have self-reviewed the code (A decent size PR without self-review might be rejected).
  • I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. If N/A, write N/A here and check the checkbox.
  • I confirm automated tests are in place that prove my fix is effective or that my feature works.

How should this be tested?

  • Are there environment variables that should be set?
  • What are the minimal test data to have?
  • What is expected (happy path) to have (input and output)?
  • Any other important info that could help to test that PR

Checklist

  • I haven't read the contributing guide
  • My code doesn't follow the style guidelines of this project
  • I haven't commented my code, particularly in hard-to-understand areas
  • I haven't checked if my changes generate no new warnings

@graphite-app graphite-app bot requested a review from a team December 18, 2024 03:35
@dosubot dosubot bot added the 🐛 bug Something isn't working label Dec 18, 2024
@keithwillcode keithwillcode added core area: core, team members only foundation labels Dec 18, 2024
Copy link

graphite-app bot commented Dec 18, 2024

Graphite Automations

"Add foundation team as reviewer" took an action on this PR • (12/18/24)

1 reviewer was added to this PR based on Keith Williams's automation.

Copy link
Contributor

E2E results are ready!

@zomars zomars merged commit 4d192ee into main Dec 18, 2024
41 of 81 checks passed
@zomars zomars deleted the fix/calendar-cache-cron branch December 18, 2024 04:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Something isn't working core area: core, team members only foundation ready-for-e2e
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants