-
Notifications
You must be signed in to change notification settings - Fork 30
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
Error switching to different workflow from classification in progress #2809
Comments
Possible fix in progress - https://github.com/zooniverse/front-end-monorepo/compare/fix-2809?expand=1, will open PR asap |
@mcbouslog Snapshots can't contain models. They have to be pure snapshots. |
Hard to debug on the live site, but I'm seeing an error in a snapshot processor somewhere. https://www.zooniverse.org/projects/humphrydavy/davy-notebooks-project/classify/workflow/20178?demo=true |
It's hard to tell in the minified source, but this might be the line that's crashing, when the stored snapshot contains drawing marks (or is this specific to transcription tasks?) front-end-monorepo/packages/lib-classifier/src/plugins/drawingTools/models/marks/Mark/Mark.js Line 36 in 4027e64
EDIT: editing to add that drawing and transcription task annotations are stored as something like |
I can reproduce the bug live on Davy Notebooks, but not with the transcription task on my staging/testing project. 🤔 |
@mcbouslog I can recommend using #2793 for debugging. It adds better console log messages when the store hydrates from a snapshot. |
Fixed in #2813, I think. I'm not seeing this bug when I run Davy Notebooks locally on that branch. Weird that this bug is specific to Davy Notebooks. I wonder if it is triggered by using many workflows that are all clones of the same step and task structure? Drawing task annotations are stored in |
Following on from that comment, should we document the classifier store structure to help in debugging? |
Package
Describe the bug
Application error.
Appears to be per TasksConnector line 27.
Changing to
const latest = subject?.stepHistory?.latest
(adding optional chaining to stepHistory) appears to fix the issue.Not sure how/why subject is defined but stepHistory isn't, thereby creating the issue.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Loads different workflow.
Additional context
I'm only seeing the bug on Davy Notebooks, not seeing the bug on HMS NHS or Corresponding with Quakers
The text was updated successfully, but these errors were encountered: