calendar +agenda silently returns incomplete results

Open
#900 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@manrods is already working on this.

Since Aug 21, 2026.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
rust
Domain
api, cli

Research direction

Start in crates/google-workspace-cli/src/helpers/calendar.rs at the calendar list and event request code linked in the issue. Reproduce with more than 50 matching events and inspect how request, response, and JSON errors are handled. Done means pagination is followed and per-calendar failures are surfaced or explicitly reported as partial results, including any intentional truncation.

Written by the indexing model from the issue text.

Description

Summary

gws calendar +agenda says that it shows events across all calendars, but it can silently omit calendars and events.

At commit a3768d0e82ad83cca2da97724e46bea4ff0e6dbd:

This makes a partial result indistinguishable from a complete agenda with no events.

Reproduction

  1. Put more than 50 matching events in one calendar within the requested range.
  2. Run gws calendar +agenda for that range.
  3. The output contains at most 50 events from that calendar and reports no truncation.

A provider error for one secondary calendar also produces a successful result that omits that calendar.

Expected behavior

  • Follow nextPageToken for calendarList.list and every events.list request until it is absent.
  • Do not convert per-calendar failures into empty calendars. Return an error, or return an explicit partial-result status with the failed calendar and cause.
  • If the command has an intentional caller limit, expose the limit and report that the result is truncated.
Dominant language
Rust
Stars
32.3k
Forks
2k
Avg merge
16h 3m
Merged PRs (30d)
1

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from googleworkspace/cli

All issues in googleworkspace/cli

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.