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

Passing userdata to the sub behavior does not work properly on the develop branch #129

Closed
fgrcar opened this issue Jul 27, 2020 · 2 comments
Labels
resolved on develop Resolved on the development branch, no further work expected.

Comments

@fgrcar
Copy link

fgrcar commented Jul 27, 2020

Hi,

I tried the develop branch of this repository because of this and I found a bug regarding passing the userdata to the sub behavior.

So, I created a following behavior:
image
image
This behavior just takes an input userdata key and prints it out.

Then I created another behavior which uses the first one.
image
image
This behavior just prints out the key which is then passed into the sub behavior.

If I use the develop branch of this repository, the printed logs of the main behavior are:
image
That means that the key was not passed properly, because the default was used.
If I run the same behavior on the master, I get the desired logs:
image

I am not sure if I am missing something but it looks like that the passing of the userdata does not work properly on the develop branch.

Best regards, F

@cjue
Copy link
Contributor

cjue commented Sep 18, 2020

There are multiple commits related to userdata on develop:

I also noticed another bug on develop, where userdata is not passed along between states when the behavior does not define any default userdata values (in the State Machine Userdata dashboard section).

My guess would be the bug is related to the new distinction between "_userdata" and "_own_userdata".

@pschillinger
Copy link
Member

Sorry for my delay in addressing this, but both issues should be fixed now by the above commit. Please let me know if you still observe any unexpected behavior.

@pschillinger pschillinger added the resolved on develop Resolved on the development branch, no further work expected. label Nov 9, 2020
@fgrcar fgrcar closed this as completed Nov 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
resolved on develop Resolved on the development branch, no further work expected.
Projects
None yet
Development

No branches or pull requests

3 participants