Investigate errors in the rosetta log
@jbphet is already working on this.
Since Aug 2, 2023.
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
While looking into some issues related to starting to use CloudFlare as a CDN for our website, I noticed that there are a fair number of errors being logged in Rosetta's runtime log. Here are some examples:
Jul 27 03:30:43 phet-server2.int.colorado.edu rosetta[554564]: error: Cannot read properties of undefined (reading 'simSpecific')
.
.
.
Jul 27 13:18:28 phet-server2.int.colorado.edu rosetta[554564]: error: long-term storage of ki/wave-interference failed
.
.
.
Jul 28 09:29:33 phet-server2.int.colorado.edu rosetta[554564]: error: none of the scenarios for queryParametersWarningDialog.theSimulationWillStart were true; something has gone horribly wrong
These (meaning all errors in the log) should be investigated and separate child issues logged and addressed as appropriate. Ideally, during normal operation, we should not see any errors in this log.
I've attached a trimmed-down version of the current log that was small enough to be within the GitHub size limit. This can be used as a reference, but it probably makes the most sense when working on this to start with the most recent log.
Contributor guide
No contributing guide indexed for this repository
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.
Assessment
This issue has not been assessed yet.