search

microsoft / showwhy

MIT License
200 stars 28 forks source link

Frontend Error when trying to run Causal Discovery or Event Analysis #435

Closed MikeScavell closed 5 months ago

MikeScavell commented 8 months ago

I have built the Frontend application using the latest commit hash. I have ran the Docker compose command and it states that the webpack has compiled successfully. I am able to access the webpack on localhost:3000, load example data, and then view all of the data.

However, when I click on Causal Discovery or Event Analysis, I am presented with the error below.

Error: Snapshot has already been released.

err webpack://.yarn/virtual/recoil-virtual-1a48bd9ed0/0/cache/recoil-npm-0.7.6-6f8de04e3d-2b31dd29a7.zip/node_modules/recoil/es/index.js:16 retain webpack://.yarn/virtual/recoil-virtual-1a48bd9ed0/0/cache/recoil-npm-0.7.6-6f8de04e3d-2b31dd29a7.zip/node_modules/recoil/es/index.js:3803 useRecoilSnapshot webpack://.yarn/virtual/recoil-virtual-1a48bd9ed0/0/cache/recoil-npm-0.7.6-6f8de04e3d-2b31dd29a7.zip/node_modules/recoil/es/index.js:5735 HostInner webpack://.yarn/virtual/@datashaper-app-framework-virtual-76174ef016/0/cache/@datashaper-app-framework-npm-0.4.1-71cc242619-afdfdfb214.zip/node_modules/@datashaper/app-framework/dist/components/client/RecoilBasedProfileHost/RecoilBasedProfileHost.js:25 renderWithHooks webpack://.yarn/virtual/react-dom-virtual-a157c21d32/0/cache/react-dom-npm-18.2.0-dd675bca1c-7d323310be.zip/node_modules/react-dom/cjs/react-dom.development.js:16305 updateFunctionComponent webpack://.yarn/virtual/react-dom-virtual-a157c21d32/0/cache/react-dom-npm-18.2.0-dd675bca1c-7d323310be.zip/node_modules/react-dom/cjs/react-dom.development.js:19588 updateSimpleMemoComponent webpack://.yarn/virtual/react-dom-virtual-a157c21d32/0/cache/react-dom-npm-18.2.0-dd675bca1c-7d323310be.zip/node_modules/react-dom/cjs/react-dom.development.js:19425 beginWork webpack://.yarn/virtual/react-dom-virtual-a157c21d32/0/cache/react-dom-npm-18.2.0-dd675bca1c-7d323310be.zip/node_modules/react-dom/cjs/react-dom.development.js:21678 beginWork$1 webpack://.yarn/virtual/react-dom-virtual-a157c21d32/0/cache/react-dom-npm-18.2.0-dd675bca1c-7d323310be.zip/node_modules/react-dom/cjs/react-dom.development.js:27426 performUnitOfWork webpack://.yarn/virtual/react-dom-virtual-a157c21d32/0/cache/react-dom-npm-18.2.0-dd675bca1c-7d323310be.zip/node_modules/react-dom/cjs/react-dom.development.js:26560 workLoopSync webpack://.yarn/virtual/react-dom-virtual-a157c21d32/0/cache/react-dom-npm-18.2.0-dd675bca1c-7d323310be.zip/node_modules/react-dom/cjs/react-dom.development.js:26466 renderRootSync webpack://.yarn/virtual/react-dom-virtual-a157c21d32/0/cache/react-dom-npm-18.2.0-dd675bca1c-7d323310be.zip/node_modules/react-dom/cjs/react-dom.development.js:26434 recoverFromConcurrentError webpack://.yarn/virtual/react-dom-virtual-a157c21d32/0/cache/react-dom-npm-18.2.0-dd675bca1c-7d323310be.zip/node_modules/react-dom/cjs/react-dom.development.js:25850 performConcurrentWorkOnRoot webpack://.yarn/virtual/react-dom-virtual-a157c21d32/0/cache/react-dom-npm-18.2.0-dd675bca1c-7d323310be.zip/node_modules/react-dom/cjs/react-dom.development.js:25750 workLoop webpack://.yarn/cache/scheduler-npm-0.23.0-a379a6bc3b-d79192eeaa.zip/node_modules/scheduler/cjs/scheduler.development.js:266 flushWork webpack://.yarn/cache/scheduler-npm-0.23.0-a379a6bc3b-d79192eeaa.zip/node_modules/scheduler/cjs/scheduler.development.js:239 performWorkUntilDeadline webpack://.yarn/cache/scheduler-npm-0.23.0-a379a6bc3b-d79192eeaa.zip/node_modules/scheduler/cjs/scheduler.development.js:533

Am I doing something obviously wrong here, or are other people encountering this issue? Thanks!

MikeScavell commented 7 months ago

An update on this issue is that the Frontend application does not have this issue when I build from the v2.0.0 tag. My gut feel is there are some changes that have been made to the code somewhere that are causing this issue. I have not tracked the exact issue yet, but if anyone finds it please let me know!

MikeScavell commented 5 months ago

After coming back to this after a little while, I had an idea to try a different browser. Looks like the issue was with Firefox rather than the code itself. Once I accessed ShowWhy with Chrome instead the issue went away.

For anyone getting this issue, make sure you use ShowWhy through Chrome rather than Firefox.