Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[FEATURE REQ][Thin client]Request error handling and retry #42893

Open
xinlian12 opened this issue Nov 11, 2024 · 0 comments
Open

[FEATURE REQ][Thin client]Request error handling and retry #42893

xinlian12 opened this issue Nov 11, 2024 · 0 comments
Labels
Client This issue points to a problem in the data-plane of the library. cosmos:v4-item Indicates this feature will be shipped as part of V4 release train Cosmos cosmos-java-ecosystem-se-planning

Comments

@xinlian12
Copy link
Member

xinlian12 commented Nov 11, 2024 •
edited
Loading

  • Session token retry handling

  • marking region unavailable logic re-check
@github-actions github-actions bot added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Nov 11, 2024
@xinlian12 xinlian12 changed the title [FEATURE REQ]Thin client request error handling and retry [FEATURE REQ][Thin client]Request error handling and retry Nov 11, 2024
@xinlian12 xinlian12 added Cosmos cosmos:v4-item Indicates this feature will be shipped as part of V4 release train cosmos-java-ecosystem-se-planning Client This issue points to a problem in the data-plane of the library. and removed needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. labels Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Client This issue points to a problem in the data-plane of the library. cosmos:v4-item Indicates this feature will be shipped as part of V4 release train Cosmos cosmos-java-ecosystem-se-planning
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@xinlian12