Skip to content

[PECO-1687] Fixed the issue of infinite blocking in case of invalid credentials #399

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.

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

Closed

Conversation

jprakash-db
Copy link
Contributor

@jprakash-db jprakash-db commented Jun 17, 2024

  • Added the error handling for the Invalid Credentials error, that caused the connection retry to be stuck in an infinite loop

Copy link
Contributor

@kravets-levko kravets-levko left a comment

Choose a reason for hiding this comment

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

Hi @jprakash-db! Thank you for your effort on fixing this issue! Changes look good, but please do few things before we can merge this:

  • remove .idea folder
  • use existing NonRecoverableNetworkError instead of AuthenticationFailureError

@jprakash-db
Copy link
Contributor Author

@kravets-levko Sure, I will make those changes

@kravets-levko
Copy link
Contributor

@jprakash-db please also remove the .idea folder from this PR

@jprakash-db
Copy link
Contributor Author

@jprakash-db please also remove the .idea folder from this PR

Removed it @kravets-levko

@kravets-levko
Copy link
Contributor

@jprakash-db Can you please resolve conflicts, so I can merge this PR? Thanks!

@jprakash-db
Copy link
Contributor Author

@kravets-levko Resolved the merge conflicts

@kravets-levko
Copy link
Contributor

@jprakash-db when you resolved conflicts, I got confused, because I clearly remember that your PR definitely contained a code for handing 401 status. And then, I realized that recently we merged #408 🤦‍♂️ Sorry for asking you to do the job which is no longer needed. Fortunately, such overlaps don't happen often

@jprakash-db
Copy link
Contributor Author

@kravets-levko Ya, while merging I too saw, that someone had already fixed it 😅

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