Skip to content

docs(user-guide): how to examine error details#1685

Merged
coryan merged 3 commits intogoogleapis:mainfrom
coryan:docs-user-guide-examine-service-error-details
Apr 2, 2025
Merged

docs(user-guide): how to examine error details#1685
coryan merged 3 commits intogoogleapis:mainfrom
coryan:docs-user-guide-examine-service-error-details

Conversation

@coryan
Copy link
Collaborator

@coryan coryan commented Apr 1, 2025

Part of the work for #574

@codecov
Copy link

codecov bot commented Apr 1, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.94%. Comparing base (ae12873) to head (816f9ba).
Report is 5 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1685   +/-   ##
=======================================
  Coverage   95.94%   95.94%           
=======================================
  Files          47       47           
  Lines        1850     1850           
=======================================
  Hits         1775     1775           
  Misses         75       75           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@coryan coryan marked this pull request as ready for review April 1, 2025 23:03
@coryan coryan requested review from codyoss and dbolduc April 1, 2025 23:03
{{#include ../samples/src/examine_error_details.rs:examine-error-details-service-error}}
```

The client libraries return a the [`StatusDetails`] enum with the different
Copy link
Member

Choose a reason for hiding this comment

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

s/a the/a/

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Done.

`StatusDetails`, such as [`QuotaFailure`] may be useful at runtime to throttle
an application.

### Expected Output
Copy link
Member

Choose a reason for hiding this comment

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

nit: s/O/o/

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Done.

Typically the output from the error details will look like so:

```text
status.code=400, status.message=One of content, or gcs_content_uri must be set., status.status=Some("INVALID_ARGUMENT")
Copy link
Member

Choose a reason for hiding this comment

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

comment: if we normalize the status codes, we will need to update this text

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Ack.

- [How to initialize a client](initialize_a_client.md)
- [Configuring retry policies](configuring_retry_policies.md)
- [Error handling](error_handling.md)
- [Examine error details](examine_error_details.md)
Copy link
Member

Choose a reason for hiding this comment

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

comment: we might want to organize these into sections, but let's defer that until we have more guides

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Ack

@coryan coryan enabled auto-merge (squash) April 2, 2025 15:33
@coryan coryan merged commit 290ce52 into googleapis:main Apr 2, 2025
20 checks passed
@coryan coryan deleted the docs-user-guide-examine-service-error-details branch April 2, 2025 16:06
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.

2 participants