The commit history in this PR is misleading. It contains some of my older commits unrelated to this PR. Any ideas how to fix it?

@atulep For future reference, you can rebase your branch against main (e.g., git rebase main) to clean up the previous history.

In addition to my comments inline, two things:

• These are unit tests, not system tests (they don't exercise actual over-the-wire API calls).
• They belong in python-api-core, not in this repository.

@tseaver
Tests send API requests to showcase server and assert errors returned from real server response.

We want gapic clients to have access to error.details, so we should test it here. Additionally,python-api-core doesn't have any existing infrastructure for system tests, which suggested to me it's not a suitable place.

@atulep I apologize -- I somehow missed seeing that these tests use the echo fixture.

Please do rebase your branch against the current main and force push, e.g.:

$ git fetch --all --prune
$ git checkout main
$ git checkout error_details
$ git rebase main
$ git push -f origin error_details

I would also avoid re-using a branch after merging its PR.

@tseaver, I followed your script, but it gave me:

$ git rebase master
Current branch error_details is up to date.

Maybe it's easier to start a fresh PR with correct history.