Studio: failed to save commands
See original GitHub issueCurrent behavior
Test code to reproduce
I created a new repo, added cypress, did cypress open, deleted examples, created a new spec:
describe('soak test', () => {
it('logs in', () => {
cy.visit('internal url');
});
});
Then I opened studio, typed into an input and clicked save.
The page refreshes so I needed to use animation capture to see the error.
How can I provide more details on the exact error? I don’t see anything in the debug log but I will attach it here.
Versions
6.3.0 windows 10
Issue Analytics
- State:
- Created 3 years ago
- Comments:23 (14 by maintainers)
Top Results From Across the Web
save not doing anything - Visual Studio Feedback
There are no error message, no obvious issues, it simply just doesn't save. I tried clicking save, save all, CRTL + S and...
Read more >VS Code Will Not Save Changes - Mac - Stack Overflow
I have yet to find anything that affects the failed to save error, and if anyone has any suggestions, they would be greatly...
Read more >ERROR: "Failed to save. Insufficient permissions." When trying ...
It looks like you somehow changed file ownerships in your home directory. One way to correct this without endangering your system is
Read more >How to save files with Visual Studio Code? / Newbie Corner ...
When I try to save anything I've got this error: ... you have to change of ownership to program directory by command (as...
Read more >Fix 'Unable to write into user settings" | Visual Studio Code
Getting an annoying error whenever you're changing settings in Visual Studio Code (VS Code)? Well, this video shows you how things might be ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
My test case file was exactly as I put in the initial description and it was a brand new setup - all I did was enable studio.
We’ve just released copy to clipboard in v7.7.0 - check it out and let us know what you think!
We’re still working on a more dedicated fix to prevent this message from occurring in the first place but copy to clipboard should help out in the meantime.