invana / invana-studio

Open source graph visualiser.
Apache License 2.0
174 stars 19 forks source link

TypeError: e.connector.requestBuilder is undefined (Uncaught exception) #79

Closed karsil closed 3 years ago

karsil commented 3 years ago

When accessing the graph explorer in Firefox (83.0) on Windows 10, the page remains black. The console log of the browser prints the following error:

11:53:01.118 connector constructor base.js:31:16
11:53:01.119 ======isLoading null spinner.js:23:16
11:53:01.123 gremlin-component componentDidMount graph-component.js:167:16
11:53:01.124 redirectToConnectIfNeeded utils.js:173:12
11:53:01.124 We will be using ws protocol graph-component.js:171:20
11:53:01.124 setupWebSocket triggered=========================== websocket.js:72:16
11:53:01.126 gremlin-component componentWillUnmount triggered graph-component.js:188:16
11:53:01.126 TypeError: e.connector.requestBuilder is undefined
    value home.js:15
    React 2
    unstable_runWithPriority scheduler.production.min.js:19
    React 9
    <anonymous> index.js:6
    l (index):1
    <anonymous> main.5110d596.chunk.js:1
    l (index):1
    t (index):1
    r (index):1
    <anonymous> main.5110d596.chunk.js:1
react-dom.production.min.js:209:194
    React 5
    unstable_runWithPriority scheduler.production.min.js:19
    React 4
    unstable_runWithPriority scheduler.production.min.js:19
    React 6
    <anonym> index.js:6
    l (index):1
    <anonym> main.5110d596.chunk.js:1
    l (index):1
    t (index):1
    r (index):1
    <anonym> main.5110d596.chunk.js:1
11:53:01.127 Uncaught TypeError: e.connector.requestBuilder is undefined
    value home.js:15
    React 2
    unstable_runWithPriority scheduler.production.min.js:19
    React 9
    <anonymous> index.js:6
    l (index):1
    <anonymous> main.5110d596.chunk.js:1
    l (index):1
    t (index):1
    r (index):1
    <anonymous> main.5110d596.chunk.js:1
home.js:15:8
11:53:01.141 connected websocket.js:34:16
11:53:01.141 received event 
Object { statusMessage: "Connected", isConnected: true }
graph-component.js:236:16
11:53:01.142 ===eventName statusMessage Connected graph-component.js:217:16
11:53:01.142 ===eventName isConnected true graph-component.js:217:16
11:53:01.142 setIsConnected2Gremlin true graph-component.js:161:16
rrmerugu commented 3 years ago

This is a migration issue(connection url), You can navigate to http://ip-address:graph-explorer-port/switch-server , this will sign out the previous cookie of the connection URL you might have saved. This will ask you for connection url, this time give the invana-engine url http://ip-address:invana-engine-port/graphql.

This is caused by the way I was handling connection url in the part. A fresh start will solve this issue, and you shall never face this issue again

karsil commented 3 years ago

Perfect, thank you very much, this solved the problem!