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
[bug] conan remote command fails if remotes.json doen't exist #3581
Comments
Hi @leha-bot Thanks for your report.
works fine. Can you please try the above commands? |
Oh, it seems that the simple deletion is not sufficient to reproduce, I had had some another remotes (excluding conancenter) in that |
I am afraid I can't reproduce with that info either. Trying to add, remove, etc, doesn't make it fail like that. I think the key is here: This only happens if the json file is corrupted and not valid json. Maybe your remotes.json was broken? Someone accidentally touched it? If not, can you please try to provide steps to reproduce the error? Thanks! |
Hi @leha-bot Any feedback here? Thanks! |
hello, sorry for late responce. It seems that the weird symbol was from PowerShell 'New-Item' (but I'm not sure). From my friends I heard that Powershell sometimes likes to add the Unicode BOM symbol in generated files (e.g., after pipelining like I think that if you have any resources, then it would be good to add the 'fool check' for weird BOM/file size (I saw some similar in YouCompleteMe Vim plugin for LSP: https://github.com/ycm-core/ycmd/pull/1680/files) |
No prob, thanks for following up :)
I see. In general this fie is managed with the
Seems a bit overkill at the moment, the check adds some complexity and cost too, I'll check with the team for more opinions. |
I have discussed with the team, and yes, it seems a bit overkill at the moment |
Environment details
Steps to reproduce
Logs
The text was updated successfully, but these errors were encountered: