Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TypeError can't convert BigInt to number after upgrade to version 2.4.3 #805

Closed
sirko-schroeder opened this issue Mar 1, 2024 · 6 comments · Fixed by #810
Closed

TypeError can't convert BigInt to number after upgrade to version 2.4.3 #805

sirko-schroeder opened this issue Mar 1, 2024 · 6 comments · Fixed by #810
Assignees
Labels
bug Something isn't working

Comments

@sirko-schroeder
Copy link

Some of the graph reports like the one below that are working fine in 2.4.2:
image

Are not working any longer in 2.4.3

This this is the error message that is displayed instead now:

An unexpected error occurred. Try refreshing the component. 

paintNodes/<@webpack-internal:///./node_modules/force-graph/dist/force-graph.mjs:616:34
paintNodes@webpack-internal:///./node_modules/force-graph/dist/force-graph.mjs:604:22
tickFrame@webpack-internal:///./node_modules/force-graph/dist/force-graph.mjs:577:7
index/</</comp[methodName]@webpack-internal:///./node_modules/force-graph/node_modules/kapsule/dist/kapsule.mjs:194:65
init/refreshShadowCanvas<@webpack-internal:///./node_modules/force-graph/dist/force-graph.mjs:1641:42
invokeFunc@webpack-internal:///./node_modules/lodash.throttle/index.js:160:19
leadingEdge@webpack-internal:///./node_modules/lodash.throttle/index.js:170:22
debounced@webpack-internal:///./node_modules/lodash.throttle/index.js:235:16
animate@webpack-internal:///./node_modules/force-graph/dist/force-graph.mjs:1677:21
init@webpack-internal:///./node_modules/force-graph/dist/force-graph.mjs:1692:7
initStatic@webpack-internal:///./node_modules/force-graph/node_modules/kapsule/dist/kapsule.mjs:145:14
comp@webpack-internal:///./node_modules/force-graph/node_modules/kapsule/dist/kapsule.mjs:140:17
index/</<@webpack-internal:///./node_modules/react-kapsule/dist/react-kapsule.mjs:120:11
useEffectOnce/<@webpack-internal:///./node_modules/react-kapsule/dist/react-kapsule.mjs:179:29
commitHookEffectListMount@webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:20568:26
commitLifeCycles@webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:20629:36
commitLayoutEffects@webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:23421:23
callCallback@webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:3945:14
invokeGuardedCallbackDev@webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:3994:16
invokeGuardedCallback@webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:4056:31
commitRootImpl@webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:23146:30
unstable_runWithPriority@webpack-internal:///./node_modules/scheduler/cjs/scheduler.development.js:468:12
runWithPriority$1@webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:11276:10
commitRoot@webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:22985:20
performSyncWorkOnRoot@webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:22324:13
flushSyncCallbackQueueImpl/<@webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:11327:26
unstable_runWithPriority@webpack-internal:///./node_modules/scheduler/cjs/scheduler.development.js:468:12
runWithPriority$1@webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:11276:10
flushSyncCallbackQueueImpl@webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:11322:26
flushSyncCallbackQueue@webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:11309:3
scheduleUpdateOnFiber@webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:21888:9
dispatchAction@webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:16139:26
useDimensions/</observerRef.current</raf<@webpack-internal:///./node_modules/react-cool-dimensions/dist/index.esm.js:153:17

If I run the dashborad via

yarn run dev

I also see this error messsage:

image

This is the query :

match (co:Corporation) where co.name in $neodash_company
optional match (co)-[co_c:HAS_ADDRESS]->(c:Community)
optional match (co)-[co_g:REPORTED]->(g:General_Report)
optional match (co)-[co_cat:IN_CATEGORY]->(cat:CorpCat)
return co_c,c,g,co_g,co

Kind Regards,
Sirko

@sirko-schroeder sirko-schroeder added the bug Something isn't working label Mar 1, 2024
@gcthys
Copy link

gcthys commented Mar 1, 2024

Hello Sirko,
Have you noticed there is a typo in your WHERE statement? Should be WHERE co.name IS (not "in").
Guido

@sirko-schroeder
Copy link
Author

Hi Guido,

the "in" is correct as $neodash_company is the result of a multiselect from a table and contains a list of names. e.g. ['foo','bar'].
Cheers,
Sirko

@BennuFire
Copy link
Collaborator

Hello @sirko-schroeder !

We are aware of a breaking change introduced during a driver update on 2.4.3. We are working on bringing a patch ASAP

@BennuFire BennuFire self-assigned this Mar 1, 2024
@BennuFire BennuFire linked a pull request Mar 1, 2024 that will close this issue
@BennuFire BennuFire removed a link to a pull request Mar 1, 2024
@BennuFire BennuFire linked a pull request Mar 1, 2024 that will close this issue
@BennuFire
Copy link
Collaborator

Hello @sirko-schroeder ,

In the meantime, if you remove the NodeSizeRelationship from the configuration of your Chart, it should work as before (but without variable node Size).

@sirko-schroeder
Copy link
Author

Hi @BennuFire,

In the meantime, if you remove the NodeSizeRelationship from the configuration of your Chart, it should work as before (but without variable node Size).

Thank you for the workaround disabling the node resizing leads to the graph being displayed but some nodes don't get their shape rendered only their label is shown:

image

And the Report Actions seem only to fire on nodes that have a shape e.g. the community nodes above.

Thank you again for looking into this.
Kind Regards,
Sirko

@sirko-schroeder
Copy link
Author

2.4.4 fixes all the problems. :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants