Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.
Data Sources Does Not Appear
-
Aha! Thanks for getting that information. This was caused by a very recent Chrome update that took issue with the code in one of the JavaScript libraries, xstyle. We've already found and fixed this in the upcoming release by updating the xstyle library, so that'll be core 3.4.3 which will probably occur today or tomorrow. You may be able to use Firefox or Edge in the interim.
-
For searchability:
Uncaught ReferenceError: normal is not defined -
@phildunlap said in Data Sources Does Not Appear:
Uncaught ReferenceError: normal is not defined
Also further references -
https://stackoverflow.com/questions/50672599/dojo-uncaught-referenceerror-normal-is-not-defined
https://github.com/kriszyp/xstyle/issues/44#issuecomment-76512785 -
Ah ok, thank you !! It worked, was testing on 2 different PCs and all 2 were with Google Chrome.
-
Guys that is wonderful news and I have updated the all our V3 servers. However this same chrome error exists on our 2.8.8 systems as well. Will you be updating the code for 2.8.8 to fix this ?
-
Here for the same problem.
EDIT - the update seems to have fixed it. Now to the next issue. Memory leak/cpu usage.
-
@ordosays said in Data Sources Does Not Appear:
Here for the same problem.
EDIT - the update seems to have fixed it. Now to the next issue. Memory leak/cpu usage.
Sounds like it would belong in its own thread if you want to ask us anything about what's going on.
-
@phillip-weeks said in Data Sources Does Not Appear:
Guys that is wonderful news and I have updated the all our V3 servers. However this same chrome error exists on our 2.8.8 systems as well. Will you be updating the code for 2.8.8 to fix this ?
Probably not. You can however easily fix it by downloading xstyle from here - https://github.com/kriszyp/xstyle/archive/master.zip
You will need to extract it to
${MA_HOME}/overrides/web/resources/xstyle -
@jared-wiltshire Thank-you millions Jared
-
Now I remember this fixed my other 2.8.8 systems. I couldn't find it for the life of me.
Comment for searchability for next time :-P
Cheers -
Had this come up again on an instance of v3.4.0
Found putting the xstyle into the /overrides/web/resources folder it didn't take it, so ended up replacing the xstyle folder in /web/resources folder -
@dan I have the same issue after updating Mango to the core v3.7.7
Chrome version is 92.0.4515.131 (Official Build) (64-bit)When I switch to the old interface and switch to the Datasources tab, the list of data sources does not appear, just the empty white space. The data point tab works well. In the new interface, everything is alright.
When checking the browser's console I found there a bunch of errors like this ones:
Note: The actual IP address is removed and changed with <IP_address> tag.
DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/layout/TabController.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/layout/StackController.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/Menu.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/DropDownMenu.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/_MenuBase.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/_KeyNavContainer.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/_KeyNavMixin.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/MenuItem.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/layout/ScrollingTabController.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/PopupMenuItem.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/_WidgetsInTemplateMixin.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/CheckedMenuItem.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/MenuSeparator.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE -
J Jared Wiltshire referenced this topic on
-
J Jared Wiltshire referenced this topic on
