feat: initial google calendar

[ntindle]

Using sync code in the async route often introduces a blocking
event-loop code that impacts stability.

The current RPC system only provides a synchronous client to call the
service endpoints.
The scope of this PR is to provide an entirely decoupled signature
between client and server, allowing the client can mix & match async &
sync options on the client code while not changing the async/sync nature
of the server.

Changes 🏗️

• Add support for flexible async/sync RPC client.
• Migrate scheduler client to all-async client.

Checklist 📋

For code changes:

• I have clearly listed my changes in the PR description
• I have made a test plan
• I have tested my changes according to the test plan:
  • Scheduler route test.
  • Modified service_test.py
  • Run normal agent executions

Changes 🏗️

Checklist 📋

For code changes:

• I have clearly listed my changes in the PR description
• I have made a test plan
• I have tested my changes according to the test plan:
  • ...

Example test plan

• Create from scratch and execute an agent with at least 3 blocks
• Import an agent from file upload, and confirm it executes correctly
• Upload agent to marketplace
• Import an agent from marketplace and confirm it executes correctly
• Edit an agent from monitor, and confirm it executes correctly

For configuration changes:

• .env.example is updated or already compatible with my changes
• docker-compose.yml is updated or already compatible with my changes
• I have included a list of my configuration changes in the PR description (under Changes)

Examples of configuration changes

• Changing ports
• Adding new services that need to communicate with each other
• Secrets or environment variable changes
• New or infrastructure changes such as databases

[netlify]

✅ Deploy Preview for auto-gpt-docs-dev canceled.

Name	Link
🔨 Latest commit	657299f
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs-dev/deploys/681d8dc67da3c40008142b6b

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 3 🔵🔵🔵⚪⚪

🧪 No relevant tests

🔒 Security concerns OAuth token handling: The code is handling sensitive OAuth tokens and credentials. While the implementation uses Secret types for tokens, there's no validation that the tokens are properly encrypted at rest or in transit. Additionally, the code directly accesses Settings().secrets which could potentially expose secrets if not properly secured throughout the application lifecycle.

⚡ Recommended focus areas for review Typo in Description The description for GoogleCalendarReadNextEventsBlock mentions Google Sheets instead of Google Calendar, which is incorrect and misleading. description="This block reads data from a Google Sheets spreadsheet.", categories={BlockCategory.DATA}, Typo in Parameter The description for the start_time parameter contains a typo "wehn to start" instead of "when to start". description="wehn to start, defaults to timezone utc now", default=datetime.now(tz=timezone.utc), Empty Test Mock The test_mock for _read_calendar returns an empty list with commented out example data, which may not provide adequate test coverage. "_read_calendar": lambda *args, **kwargs: [ # ["Name", "Score"], # ["Alice", "85"], ],

[deepsource-io]

Here's the code health analysis summary for commits 089e7aa..657299f. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
JavaScript	✅ Success		View Check ↗
Python	✅ Success	❗ 3 occurences introduced	View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[netlify]

✅ Deploy Preview for auto-gpt-docs canceled.

Name	Link
🔨 Latest commit	657299f
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs/deploys/681d8dc6237f460008b3f791

[ntindle]

updated to make a bit more sense

[ntindle]

Thanks for the review @kcze ! changes made