A custom JavaScript error caused an issue loading your dashboard. See the developer console for more details.
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start with the Module-02_SetupPage tutorial and reproduce the dashboard setup on Splunk Enterprise 9.0.4.1. Use the developer console to inspect the 404s for react.production.min.js and react-dom.production.min.js and the related RequireJS errors in common.js. Done means the dashboard loads without the custom JavaScript error.
Written by the indexing model from the issue text.
Description
I'm trying to follow this tutorial (https://github.com/splunk/splunk-app-examples/tree/master/tutorials/Module-02_SetupPage/devtutorial) to set up password for my GeneratingCommand, but getting the error "A custom JavaScript error caused an issue loading your dashboard. See the developer console for more details.". Is there a way to fix it?
react.production.min.js:1
Failed to load resource: the server responded with a status of 404 (Not Found)Understand this errorAI
common.js:1514 Error: Script error for: react
http://requirejs.org/docs/errors.html#scripterror
at makeError (eval at e.exports (common.js:561:219217), <anonymous>:166:17)
at HTMLScriptElement.onScriptError (eval at e.exports (common.js:561:219217), <anonymous>:1689:36)
d.onError @ common.js:1514Understand this errorAI
react-dom.production.min.js:1
Failed to load resource: the server responded with a status of 404 (Not Found)Understand this errorAI
common.js:1514 Error: Script error for: ReactDOM
http://requirejs.org/docs/errors.html#scripterror
at makeError (eval at e.exports (common.js:561:219217), <anonymous>:166:17)
at HTMLScriptElement.onScriptError (eval at e.exports (common.js:561:219217), <anonymous>:1689:36)
Splunk Enterprise
Version: 9.0.4.1
Build: 419ad9369127
- Dominant language
- JavaScript
- Stars
- 155
- Forks
- 84
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing 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.
More from splunk/splunk-app-examples
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
splunk/splunk-app-examples#67 · 1 comment · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
splunk/splunk-app-examples#65 · 1 comment · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 32/100
splunk/splunk-app-examples#48 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
All issues in splunk/splunk-app-examples
Similar issues
-
area: bazaar bug complexity: medium
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
accensa/x402-facilitator-stellar#779 ·
Maintainers usually reply within 1 day
-
could-have reliability
Difficulty 1/5 Under an hour Newbie friendliness 88/100