Skip to content

Conversation

@michelle0927
Copy link
Collaborator

@michelle0927 michelle0927 commented Feb 25, 2025

Resolves #15720

Summary by CodeRabbit

  • Chores
    • Updated version numbers across calendar integration modules and the package.
  • New Features
    • Introduced enhanced subscription timer settings for optimized renewal intervals.
  • Refactor
    • Improved error handling during deactivation processes to boost overall stability.

@vercel
Copy link

vercel bot commented Feb 25, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

3 Skipped Deployments
Name Status Preview Comments Updated (UTC)
docs-v2 ⬜️ Ignored (Inspect) Feb 25, 2025 7:31pm
pipedream-docs ⬜️ Ignored (Inspect) Feb 25, 2025 7:31pm
pipedream-docs-redirect-do-not-edit ⬜️ Ignored (Inspect) Feb 25, 2025 7:31pm

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 25, 2025

Walkthrough

This pull request primarily updates version numbers across multiple Google Calendar modules and the package file. In addition, a new constant for webhook subscription renewal has been added to the constants file. One source file ("new-or-updated-event-instant.mjs") also includes modifications to its constant import and enhanced error handling in its deactivate method. No changes affect core functionality beyond version tracking and minor control flow improvements.

Changes

File(s) Change Summary
components/google_calendar/actions/... Updated version numbers:
• add-attendees-to-event: 0.0.2 → 0.0.3
• create-event: 0.2.4 → 0.2.5
• delete-event: 0.1.6 → 0.1.7
• get-calendar: 0.1.7 → 0.1.8
• get-event: 0.1.7 → 0.1.8
• list-calendars: 0.1.7 → 0.1.8
• list-events: 0.0.7 → 0.0.8
• query-free-busy-calendars: 0.1.7 → 0.1.8
• quick-add-event: 0.1.6 → 0.1.7
• update-event: 0.0.9 → 0.0.10
components/google_calendar/common/constants.mjs Added new constants for webhook subscription:
WEBHOOK_SUBSCRIPTION_EXPIRATION_TIME_MILLISECONDS (24 hours) and WEBHOOK_SUBSCRIPTION_RENEWAL_SECONDS (95% of expiration time, in seconds)
components/google_calendar/package.json Package version updated from 0.5.7 to 0.5.8
components/google_calendar/sources/{event-cancelled, event-ended, new-calendar, new-event-search}/*.mjs Version updated from 0.1.10 → 0.1.11
components/google_calendar/sources/new-or-updated-event-instant/new-or-updated-event-instant.mjs Version updated from 0.1.14 → 0.1.15; replaced constant import with WEBHOOK_SUBSCRIPTION_RENEWAL_SECONDS and enhanced error handling in the deactivate method
components/google_calendar/sources/upcoming-event-alert/upcoming-event-alert.mjs Version updated from 0.0.9 → 0.0.10

Sequence Diagram(s)

sequenceDiagram
    participant Caller as Deactivate Caller
    participant Module as new-or-updated-event-instant
    participant StopWatch as stopWatchRequest
    participant Logger as Error Logger

    Caller->>Module: Calls deactivate()
    Module->>StopWatch: Invokes stopWatchRequest()
    alt Successful Execution
        StopWatch-->>Module: Returns success
    else Error Occurs
        StopWatch-->>Module: Throws error
        Module->>Logger: Logs error message
    end
Loading

Possibly related PRs

Suggested labels

bug

Suggested reviewers

  • jcortes

Poem

I'm a bunny with a code-filled heart,
Hopping through versions, making my mark.
With constants added and errors caught,
My little paws fix what others sought.
In fields of code, I joyfully prance—
A rabbit in code, in a happy dance!
🐇💻

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

components/google_calendar/actions/add-attendees-to-event/add-attendees-to-event.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at packageResolve (node:internal/modules/esm/resolve:839:9)
at moduleResolve (node:internal/modules/esm/resolve:908:18)
at defaultResolve (node:internal/modules/esm/resolve:1038:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:557:12)
at ModuleLoader.resolve (node:internal/modules/esm/loader:525:25)
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:246:38)
at ModuleJob._link (node:internal/modules/esm/module_job:126:49)

components/google_calendar/actions/get-event/get-event.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at packageResolve (node:internal/modules/esm/resolve:839:9)
at moduleResolve (node:internal/modules/esm/resolve:908:18)
at defaultResolve (node:internal/modules/esm/resolve:1038:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:557:12)
at ModuleLoader.resolve (node:internal/modules/esm/loader:525:25)
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:246:38)
at ModuleJob._link (node:internal/modules/esm/module_job:126:49)

components/google_calendar/actions/create-event/create-event.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at packageResolve (node:internal/modules/esm/resolve:839:9)
at moduleResolve (node:internal/modules/esm/resolve:908:18)
at defaultResolve (node:internal/modules/esm/resolve:1038:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:557:12)
at ModuleLoader.resolve (node:internal/modules/esm/loader:525:25)
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:246:38)
at ModuleJob._link (node:internal/modules/esm/module_job:126:49)

  • 14 others
✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@michelle0927 michelle0927 marked this pull request as ready for review February 25, 2025 19:32
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
components/google_calendar/sources/new-or-updated-event-instant/new-or-updated-event-instant.mjs (1)

69-73: Improved error handling in the deactivate method.

Adding a try-catch block is an important improvement that prevents errors during webhook deactivation from causing issues with the deactivation process. This helps with graceful shutdown even when the webhook deactivation fails.

Consider enhancing the error logging to include more context about what caused the failure:

-        console.log(`Error deactivating webhook. ${e}`);
+        console.log(`Error deactivating webhook for Google Calendar source. Details: ${e.message || e}`);
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7b0490b and 759a569.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (18)
  • components/google_calendar/actions/add-attendees-to-event/add-attendees-to-event.mjs (1 hunks)
  • components/google_calendar/actions/create-event/create-event.mjs (1 hunks)
  • components/google_calendar/actions/delete-event/delete-event.mjs (1 hunks)
  • components/google_calendar/actions/get-calendar/get-calendar.mjs (1 hunks)
  • components/google_calendar/actions/get-event/get-event.mjs (1 hunks)
  • components/google_calendar/actions/list-calendars/list-calendars.mjs (1 hunks)
  • components/google_calendar/actions/list-events/list-events.mjs (1 hunks)
  • components/google_calendar/actions/query-free-busy-calendars/query-free-busy-calendars.mjs (1 hunks)
  • components/google_calendar/actions/quick-add-event/quick-add-event.mjs (1 hunks)
  • components/google_calendar/actions/update-event/update-event.mjs (1 hunks)
  • components/google_calendar/common/constants.mjs (1 hunks)
  • components/google_calendar/package.json (1 hunks)
  • components/google_calendar/sources/event-cancelled/event-cancelled.mjs (1 hunks)
  • components/google_calendar/sources/event-ended/event-ended.mjs (1 hunks)
  • components/google_calendar/sources/new-calendar/new-calendar.mjs (1 hunks)
  • components/google_calendar/sources/new-event-search/new-event-search.mjs (1 hunks)
  • components/google_calendar/sources/new-or-updated-event-instant/new-or-updated-event-instant.mjs (3 hunks)
  • components/google_calendar/sources/upcoming-event-alert/upcoming-event-alert.mjs (1 hunks)
✅ Files skipped from review due to trivial changes (16)
  • components/google_calendar/actions/list-events/list-events.mjs
  • components/google_calendar/package.json
  • components/google_calendar/sources/event-cancelled/event-cancelled.mjs
  • components/google_calendar/actions/update-event/update-event.mjs
  • components/google_calendar/actions/create-event/create-event.mjs
  • components/google_calendar/actions/query-free-busy-calendars/query-free-busy-calendars.mjs
  • components/google_calendar/sources/new-calendar/new-calendar.mjs
  • components/google_calendar/actions/add-attendees-to-event/add-attendees-to-event.mjs
  • components/google_calendar/sources/event-ended/event-ended.mjs
  • components/google_calendar/sources/new-event-search/new-event-search.mjs
  • components/google_calendar/actions/quick-add-event/quick-add-event.mjs
  • components/google_calendar/actions/get-calendar/get-calendar.mjs
  • components/google_calendar/actions/list-calendars/list-calendars.mjs
  • components/google_calendar/actions/delete-event/delete-event.mjs
  • components/google_calendar/actions/get-event/get-event.mjs
  • components/google_calendar/sources/upcoming-event-alert/upcoming-event-alert.mjs
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: pnpm publish
  • GitHub Check: Verify TypeScript components
  • GitHub Check: Publish TypeScript components
🔇 Additional comments (5)
components/google_calendar/common/constants.mjs (2)

88-90: Good addition of webhook renewal constants.

Adding these constants that define webhook subscription expiration time and renewal timing is a good practice. Setting the renewal to 95% of the expiration time provides a proper buffer to ensure subscriptions are renewed before they expire.


95-95: LGTM on exporting the renewal constant.

Properly exporting the constant so it can be used in other modules.

components/google_calendar/sources/new-or-updated-event-instant/new-or-updated-event-instant.mjs (3)

4-4: Appropriate import of constants module.

Importing the constants module instead of using hardcoded values is a good practice for maintainability.


11-11: Version bump is appropriate.

The version increment from 0.1.14 to 0.1.15 is appropriate for this bug fix.


41-41: Good use of the central constant for timer interval.

Using the centrally defined constant WEBHOOK_SUBSCRIPTION_RENEWAL_SECONDS instead of a hardcoded value makes the code more maintainable.

Copy link
Collaborator

@GTFalcao GTFalcao left a comment

Choose a reason for hiding this comment

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

LGTM!

@michelle0927 michelle0927 merged commit 1571a72 into master Feb 26, 2025
11 checks passed
@michelle0927 michelle0927 deleted the issue-15720 branch February 26, 2025 15:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] Google Calendar webhook

3 participants