-
-
Notifications
You must be signed in to change notification settings - Fork 90
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
Unable to commit #515
Comments
svn extension version: 1.47.5 I have a related problem. I noticed a couple of days ago I was able to commit, however, after the commit, its message remains in the input, as if the input was waiting to be "noticed" about the operation. |
Can you copy the svn output when you try and commit please |
I'm sorry, I can't find how to see the svn output in vscode, could you provide me any info? |
"SHOW > OUTPUT" and select SVN dropdown |
[myProject]$ svn commit src\components\dashboard\x.vue src\components\dashboard\y.vue -m '~ fix last todos' --depth empty After clicking "Commit" the message "~ fix last todos" remains in the vscode's input |
Nice @IperStan, some message are shown after commit? @JohnstonCode, line to refer svn-scm/src/commands/commit.ts Line 64 in 8471670
|
@edgardmessias The above-mentioned log is exactly what was shown after I clicked "Commit", nothing more. |
Sorry, I meant if it shows a popup. Before commit, you can go to "HELP > Toggle developers tools", and make the commit, and check some error message |
Big thanks @IperStan , now I will try reproduce here |
The problem is caused by 17c5438, has removed default encoding. |
🎉 This issue has been resolved in version 1.47.6 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
svn extension version: 1.47.5
vscode version: 1.32.3
os: Linux x64 4.4.175-89-default
Issue
since a few updates the svn extension for Visual Studio Code seems to be broken. At least I cannot commit the changes, however committing in the terminal with svn commands is working without issues.
SVN Output
The text was updated successfully, but these errors were encountered: