codesandbox / codesandbox/codesandbox-client
"We were not able to compare the content with the source, please refresh or report the issue."
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
My project is linked to a Github repo. After the previous commit, I could not load github tab at all.
The error message is "We were not able to compare the content with the source, please refresh or report the issue."

There seems to be 2 related issues:
- https://github.com/codesandbox/codesandbox-client/issues/4751
- https://github.com/codesandbox/codesandbox-client/discussions/4430
How has this issue affected you? What are you trying to accomplish?
Commit
To Reproduce
I donno. Quick commit and close the tab?
Link to sandbox: link
Your Environment
| Software | Name/Version |
|---|---|
| Сodesandbox | 7baad8a9c |
| Browser | Version 103.0.5060.114 (Official Build) (x86_64) |
| Operating System | macOS Bug Sur 11.6.7 |
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
Start by reproducing the failure in the linked sandbox: make a quick commit, close the tab, and reopen the GitHub tab. Read the related issue and discussion for existing context. Done means the GitHub tab loads after the commit without showing the comparison error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript
- Domain
- developer-experience, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100