-
Notifications
You must be signed in to change notification settings - Fork 41
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
PUT
request for changing a task's text do not save on the backend
#2212
Comments
Just noting this bug was previously discussed on Slack but none of us actually opened an issue for it. Example with the python client: >>> w.tasks['T0']['question']
u'que?'
>>> w.tasks['T0']['question'] = 'huh?'
>>> w.save()
>>> w.tasks['T0']['question']
u'que?'
>>> w.first_task
u'T0'
>>> w.first_task = 'T1'
>>> w.save()
>>> w.first_task
u'T1'
>>> w.tasks['T0']['question']
u'huh?' |
@zwolf you got time to have look at this? |
Just noting that i think this is caused by the resource not having it's updated at changed and the serializer response is cached for based on tihs. The data is all being set ok the backend but we'er serializing old data. You can check this by making your workflow active / inactive to force the updated_at timestamp to be changed. I've got a reverted PR that broke other things that should fix this issue on it's own #2169 |
When changing just the text for a task the changes don't save on the backend (e.g. refreshing the pages causes the changes to go away).
Example request made by the lab when changing a task's main text from
test 2
totest
(everything looks normal to me):And when refreshing the lab page the following request is made:
Note that the
Response
for TaskT0
squestion
key is not the same between thePUT
andGET
requests.If more things change on the workflows besides the task text (e.g. adding a new task) the changes save as expected. This same behavior is see when updating a workflow's task text with the python-client as well.
The text was updated successfully, but these errors were encountered: