400 Bad Request on all gws calendar +insert commands

Open
#912 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
rust
Domain
api, cli

Research direction

Start by reproducing the failure with the gws calendar +insert command and compare it with a previously working invocation. Check the Calendar API request path and authentication behavior, using the reported 400 Bad Request response as the initial symptom. Done means the command succeeds again or the server-side cause is documented with a clear workaround.

Written by the indexing model from the issue text.

Description

Quite suddenly I was unable to use the gws calendar +insert command. It has worked reliably for months but today it suddenly stopped working and I constantly get:

{
  "error": {
    "code": 400,
    "message": "Bad Request",
    "reason": "badRequest"
  }
}
error[api]: Bad Request

I have tried re-authenticating, fresh install, but it seems the problem is server-side?

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.