Bug(Sprint Poker): Error in ParabolScopingSearchResultItem

[Dschoordsch]

https://parabol.sentry.io/issues/3402262694/?referrer=github_plugin

TypeError: Cannot destructure property 'id' of 'u' as it is undefined.
  at Ft (./packages/client/components/ParabolScopingSearchResultItem.tsx:78:14)
  at Set.forEach (<anonymous>)
...
(31 additional frame(s) were not displayed)

How to reproduce

• Create a Sprint Poker meeting
• add parabol tasks
• advance the meeting
• delete one of the tasks (the task itself from the task dashboard by removing its content)
• go back to the sprint meeting scoping session
• press the new task button

[Dschoordsch]

2.2k events, 355 users, thus this should be a p1

[Dschoordsch]

Sentry issue: ACTION-PRODUCTION-E0T

[Dschoordsch]

Sentry issue: ACTION-PRODUCTION-DWZ

[Dschoordsch]

Sentry issue: ACTION-PRODUCTION-DWY

[Dschoordsch]

Linked additional issues which have different backtrace but appear in the same area and timespan thus probably have the same root cause.

[igorlesnenko]

Just clicking New Task in the Parabol tab straight from the beginning does not work too

[Dschoordsch]

Yes. I discussed this yesterday with Matt. It's an issue resulting from adding the optimistic task to the edges of the task search result. Omitting the optimistic task would work, but Matt also suggested rearranging the GraphQL fragments, because James recently found out that something similar happened because of @plural items nested in a fragment.

[gcrickman]

A user 🔒 writes:

I'm unable to create a parabol task from a sprint poker meeting. I got this error:

TypeError: Cannot read properties of undefined (reading 'node')
at ParabolScopingSelectAllTasks.tsx:44:52
at Array.map (<anonymous>)
at Lt (ParabolScopingSelectAllTasks.tsx:44:25)
at aa (react-dom.production.min.js:157:137)
at Za (react-dom.production.min.js:180:154)
at Ws (react-dom.production.min.js:269:343)
at kl (react-dom.production.min.js:250:347)
at xl (react-dom.production.min.js:250:278)
at wl (react-dom.production.min.js:250:138)
at yl (react-dom.production.min.js:243:163)
at react-dom.production.min.js:123:115
at t.unstable_runWithPriority (scheduler.production.min.js:18:343)
at Bi (react-dom.production.min.js:122:325)
at Wi (react-dom.production.min.js:123:61)
at Ki (react-dom.production.min.js:122:428)
at hl (react-dom.production.min.js:237:203)
at ka (react-dom.production.min.js:170:408)
at v (useFragmentNode.js:62:5)
at FragmentResource.js:498:9
at t._updateSubscription (RelayStoreSubscriptions.js:172:7)
at RelayStoreSubscriptions.js:114:26
at Set.forEach (<anonymous>)
at t.updateSubscriptions (RelayStoreSubscriptions.js:113:25)
at t.notify (RelayModernStore.js:300:30)
at t.run (RelayPublishQueue.js:217:24)
at t._runPublishQueue (OperationExecutor.js:1388:61)
at t._handleNext (OperationExecutor.js:521:30)
at OperationExecutor.js:341:16
at e.exports (withDuration.js:26:16)
at OperationExecutor.js:340:28
at t._schedule (OperationExecutor.js:298:7)
at t._next (OperationExecutor.js:339:10)
at Object.next (OperationExecutor.js:156:17)
at Object.next (RelayObservable.js:534:20)
at t.default.dispatch (GQLTrebuchetClient.js:50:26)
at a.<anonymous> (GQLTrebuchetClient.js:11:18)
at s.emit (index.js:202:33)
at ws.onmessage (SocketTrebuchet.js:113:26)

[lilicaruso]

Enterprise User 🔒 followed up on resolution of this one.

[Dschoordsch]

The workaround should be released by the end of this week.

[Dschoordsch]

Just removed the p1 label to not convey unnecessary urgency since the workaround solves it for now.

[jmtaber129]

@Dschoordsch @BartoszJarocki can this be closed in favor of a task for the actual fix since the bandaid fix is merged?

[Dschoordsch]

Sentry issue: ACTION-PRODUCTION-EWT

[Dschoordsch]

Sentry issue: ACTION-PRODUCTION-EWS

[Dschoordsch]

Reappeared due to a partial revert of the fix in #8472