Exposure analysis: Missing the subject identifier when loading project generates “Error: Invalid column reference: d[’index’]”

[jprussoibanez]

Context

Reproducing the DoWhy bank churners use case with exposure analysis through ShowWhy user interface.

Issue description

When I save and load the project, the subject identifier is missing in the data binding process for exposure analysis. This missing information seems to crash the estimate effects page with the following error on the user interface.

Error: Invalid column reference: "d["index"]"
__WEBPACK_DEFAULT_EXPORT__
webpack://.yarn/cache/arquero-npm-5.1.0-441d7e4e6f-491560706c.zip/node_modules/arquero/src/util/error.js:2
Object.error
webpack://.yarn/cache/arquero-npm-5.1.0-441d7e4e6f-491560706c.zip/node_modules/arquero/src/expression/parse.js:63
checkColumn
webpack://.yarn/cache/arquero-npm-5.1.0-441d7e4e6f-491560706c.zip/node_modules/arquero/src/expression/parse-expression.js:339
spliceMember
webpack://.yarn/cache/arquero-npm-5.1.0-441d7e4e6f-491560706c.zip/node_modules/arquero/src/expression/parse-expression.js:210
MemberExpression
webpack://.yarn/cache/arquero-npm-5.1.0-441d7e4e6f-491560706c.zip/node_modules/arquero/src/expression/parse-expression.js:182
walk
webpack://.yarn/cache/arquero-npm-5.1.0-441d7e4e6f-491560706c.zip/node_modules/arquero/src/expression/ast/walk.js:3
http://localhost:3000/main.493d57c909fd98bd8035.js:203142:60
parseOperator
webpack://.yarn/cache/arquero-npm-5.1.0-441d7e4e6f-491560706c.zip/node_modules/arquero/src/expression/parse-expression.js:280
CallExpression
webpack://.yarn/cache/arquero-npm-5.1.0-441d7e4e6f-491560706c.zip/node_modules/arquero/src/expression/parse-expression.js:149
walk
webpack://.yarn/cache/arquero-npm-5.1.0-441d7e4e6f-491560706c.zip/node_modules/arquero/src/expression/ast/walk.js:3
parseExpression
webpack://.yarn/cache/arquero-npm-5.1.0-441d7e4e6f-491560706c.zip/node_modules/arquero/src/expression/parse-expression.js:86
__WEBPACK_DEFAULT_EXPORT__
webpack://.yarn/cache/arquero-npm-5.1.0-441d7e4e6f-491560706c.zip/node_modules/arquero/src/expression/parse.js:76
ColumnTable.__WEBPACK_DEFAULT_EXPORT__
webpack://.yarn/cache/arquero-npm-5.1.0-441d7e4e6f-491560706c.zip/node_modules/arquero/src/verbs/rollup.js:5
ColumnTable.rollup
webpack://.yarn/cache/arquero-npm-5.1.0-441d7e4e6f-491560706c.zip/node_modules/arquero/src/table/transformable.js:207
agg
webpack://.yarn/cache/arquero-npm-5.1.0-441d7e4e6f-491560706c.zip/node_modules/arquero/src/verbs/helpers/agg.js:15
http://localhost:3000/main.493d57c909fd98bd8035.js:140738:68
updateMemo
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:17246
Object.useMemo
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:17886
useMemo
webpack://.yarn/cache/react-npm-18.2.0-1eae08fee2-88e38092da.zip/node_modules/react/cjs/react.development.js:1650
useIsMicrodata
webpack://@showwhy/app-model-exposure/src/hooks/estimate/useIsMicrodata.ts:11
useDataErrors
webpack://@showwhy/app-model-exposure/src/hooks/estimate/useDataErrors.ts:30
AnalyzeTestPageEffects
webpack://@showwhy/app-model-exposure/src/pages/AnalyzeTestPageEffects.tsx:53
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
MessagePort.performWorkUntilDeadline
webpack://.yarn/cache/scheduler-npm-0.23.0-a379a6bc3b-d79192eeaa.zip/node_modules/scheduler/cjs/scheduler.development.js:533

Note: Setting the subject identifier explicitly after loading the project, everything works ok, so seems to be a problem with the metadata saved on the project zip file.

Steps to reproduce the issue:

1. Load the following project zip.

2. Navigate directly to 4. Estimate effects on exposure analysis.

3. Page crashes even though backend API responds correctly.

Version information

• DoWhy version is the latest on the main branch.
• Running dockers locally on a Mac M1, so needed to adjust some of the library's dependencies to make it work within Tensorflow docker restrictions. Here is a more detailed explanation of the configuration used.

[xtshanlei]

Got the same issue. Hope someone can help

[amanrai2508]

Having the same issue.