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

Error loading simple_workflow sample data #438

Closed
chris-hailstorm opened this issue Jan 25, 2018 · 5 comments

Comments

@chris-hailstorm
Copy link

commented Jan 25, 2018

Using the Getting Started guide -- tried:

$ python manage.py loadworkflowsampledata simple_workflow/v1

Got this error:
An error occurred while loading sample data: 'NoneType' object is not callable

This worked fine:

$ python manage.py loadworkflowsampledata journalism/v1
@marcua

This comment has been minimized.

Copy link
Member

commented Jan 30, 2018

@chris-hailstorm Thank you for reporting. Do you happen to have a full stack trace? If not I can try to reproduce nonetheless.

@davidkrcil

This comment has been minimized.

Copy link

commented Apr 19, 2018

I have the some problem, please send what details you need

@adrianoadum

This comment has been minimized.

Copy link

commented Jan 16, 2019

Exact same issue here. journalism works fine, but simple_workflow fail.
As command return a single error line, I have no full stack trace to share. (tried --verbosity 3 but the output is the same)

@steve-bate

This comment has been minimized.

Copy link

commented Mar 13, 2019

I hit this issue too. It appears to be some bad data in simple_workflow/workflow.json #339. The path ends in 'name', but the actual load function in simple_workflow/load_sample_data.py #421 is called 'load'. Since the method 'name' can't be located in orchestra/management/commands/loadworkflowsampledata.py #421, it results in error message about the 'NoneType' object not being callable. The fix looks simple, but I don't have time at the moment to create and test a PR. While diagnosing the issue, I worked around it by loading and calling the load function manually in a Python shell. Hopefully, these details with give the developers enough info to fix the issue since this turns a 5 minute getting started activity into at least a several hour debugging session. ;-)

@marcua

This comment has been minimized.

Copy link
Member

commented May 16, 2019

Thanks everyone for reporting. We fixed this in PR #497! Hurray!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.