codesandbox / codesandbox/codesandbox-client
Problem saving the code / Failed to save [file]: Unknown Save Error - Sentry exception
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13.6k
- Forks
- 2.4k
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 2
Description
🐛 bug report
Preflight Checklist
- I have read the
Contributing Guidelines
for this project. - I agree to follow the
Code of Conduct
that this project adheres to. - I have searched the issue tracker for an issue that matches the one I want
to file, without success.
Description of the problem
Upon saving a file, I get two notification on the bottom right:
There was a problem with saving the code, please try againFailed to save 'DialogueParser.js': Unknown Save Error
Seems to be a problem with sentry, the network tab shows a failed request to sentry.io on save, with the response carrying the exception "Non-Error exception captured with keys: reason"
On top of that, the developer console displays the following errors on attempting to save:
"The operation's base length must be equal to the string's length. String length: 0, base length: 1193"POST https://sentry.io/api/2071895/store/?sentry_key=f595bc90ce3646c4a9d76a8d3b84b403&sentry_version=7 net::ERR_BLOCKED_BY_CLIENT
This only happens in one file, the rest of the files in the sandbox work and save fine.
How has this issue affected you? What are you trying to accomplish?
The file is forever marked in an "unsaved" state. Worth mentioning that even with the errors above, the file seems to save fine for my user as opening the sandbox in a different browser / incognito mode shows the latest edits, however when accessing the sandbox via a public link the file appears empty.
To Reproduce
To be honest, I have no idea. it just started happening out of the blue, for just one file in one sandbox.
Your Environment
| Software | Name/Version |
|---|---|
| Сodesandbox | 76fd74d21 |
| Browser | Chrome Version 88.0.4324.190 (Official Build) (64-bit) / Firefox 86.0 (64-bit) |
| Operating System | Windows 10 |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report identifies DialogueParser.js and browser console/network errors, but no implementation file, test, or entry point. Start by reproducing the save failure and tracing the save request and Sentry exception; done means the file saves without remaining unsaved or appearing empty through a public link.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- full-stack
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100