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

non-string marking causes import crash #1171

Open
wlhunt opened this issue May 6, 2024 · 1 comment
Open

non-string marking causes import crash #1171

wlhunt opened this issue May 6, 2024 · 1 comment
Assignees
Labels

Comments

@wlhunt
Copy link
Contributor

wlhunt commented May 6, 2024

What appears to be temporary or pre-initialization marking, that's stored in the db, causes the import process to fail.

Stored models with a marking set to an empty python string are not processable through the archive system. The import process crashes upon discovery of a marking stored as [].

Here's an example model:

{
"_id": "a05dba96ee324e5690a146bac03666ed",
"_rev": "2-6352825fa40d3d1825dae970198be0a6",
"bookmark": "none",
"type": "model",
"model-type": "timeseries",
"marking": [],
"project": "51186573a65bba04739b6956db001663",
"created": "2022-03-16T21:33:24.532602",
"creator": "barbie",
"name": "Lobotomy Study III",
"description": "partial frontal",
"artifact-types": {},
"input-artifacts": [],
"state": "waiting",
"result": null,
"started": null,
"finished": null,
"progress": null,
"message": null
}

@Mletter1
Copy link
Collaborator

looking into this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants