I am using cursor for a ruby on rails project. Rubocop is the ruby linter. Rubocop is very slow with cursor and always reports problems in files that do not exist. When I try to open the files my editor cannot and I get some text like
“The editor could not be opened due to an unexpected error: Unable to resolve resource aichat-code-block-anysphere://tqmxbhaoyr”
Attached is a screenshot of the problems and me trying to open one of these files. I initially thought it was due to rubocop interacting with another extension, but if I turn all my extensions off except rubocop the issue persists and the issue is not present at all in VSCode.
Could this be some issue to do with cached chat conversations?
Any help would be much appreciated as I have a suspicion these issues are slowing cursor down with rubocop.
The aichat-code-block-anysphere:// URI is used to reference code snippets from your files in the chat, so that you can jump back to the line and file the snippet is from by clicking it in the chat.
However, this shouldn’t be interfering with Rubocop at all.
Can you confirm, does this happen on a brand new project, or only in ones where you have used the chat before? It’s possible Rubocop tracks (and caches?) what files have been opened based on their URI, and is remembering our internal ones instead of the real file location.
I’ll raise this with the team to see if they have more info on this.
I’m seeing the same thing with RedHat’s YAML extension. I’m working with Ansible, and it appears to happen with ongoing chats/composer threads. I reloaded a window, didn’t have errors, loaded an ongoing composer thread, and it flagged a bunch of files.
