-
-
Notifications
You must be signed in to change notification settings - Fork 84
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
Extension not asking for new credentials #401
Comments
Hello, first, update the issue with template: https://github.com/JohnstonCode/svn-scm/blob/master/.github/ISSUE_TEMPLATE/bug_report.md |
I have updated the issue details. |
edgardmessias
added a commit
that referenced
this issue
Nov 16, 2018
🎉 This issue has been resolved in version 1.45.4 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
VSCode Version: 1.29.0 (user setup)
OS Version: 1709
OS Build: 16299.726
Extension Version: v1.45.2
System Language: English(India)
SVN Version: TortoiseSVN 1.10.28176
Issue
If I use tortoise SVN in file explorer, it is prompting for the new password when the password for SVN changes remotely. But this SVN extension does not show any error or prompt for the new password in the same case. Besides that, the extension says, Updated as status in the Status bar. But when I try to updating manually, it just displays a message showing unable to update. After this manual update also, the status does not change. So, how can I know if there are any pending updates from the repository?
Steps to Reproduce
Solution expected:
Display proper message which shows " there is some authentication error or Password expired." And prompt for the new password.
If I close and re-open the VS code and SVN extension are working as expected. But I want to resume the work VScode as I use any other app.
The alternative solution I have used
Initially, I have no idea why it's not working, So I used Tortoise SVN in system file explorer. After many occurences of same case I undersood the issue.
The text was updated successfully, but these errors were encountered: