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 data into an asynchronous function #628

Closed
Tofull opened this issue Jul 6, 2017 · 1 comment · Fixed by #648
Closed

passing data into an asynchronous function #628

Tofull opened this issue Jul 6, 2017 · 1 comment · Fixed by #648
Assignees

Comments

@Tofull
Copy link

Tofull commented Jul 6, 2017

Hi,

I am very interested in asynchronous functions as I am working on deep learning for image processing.

IronFunctions seems to not pass data when the functions are type: async.
In the async section of the readme, the route is requested with { "name":"Johnny" } data and the queued function returns Hello World! instead of Hello Johnny! as sync-version does the stuff.

This issue first appeared to me when I was trying an asynchronous hello world in python, taking a json file as the sync-version of python hello world does and the queued function returns:

INFO[9116] Pushed to MQ
INFO[9116] Added new task to queue
INFO[9116] Reserved
INFO[9116]
INFO[9116]
INFO[9116] Deleted
INFO[9116] Task complete
INFO[9116] Traceback (most recent call last):
INFO[9116] File "hello.py", line 9, in
INFO[9116] obj = json.loads(sys.stdin.read())
INFO[9116] File "/usr/lib/python2.7/json/init.py", line 339, in loads
INFO[9116] return _default_decoder.decode(s)
INFO[9116] File "/usr/lib/python2.7/json/decoder.py", line 364, in decode
INFO[9116] obj, end = self.raw_decode(s, idx=_w(s, 0).end())
INFO[9116] File "/usr/lib/python2.7/json/decoder.py", line 382, in raw_decode
INFO[9116] raise ValueError("No JSON object could be decoded")
INFO[9116] ValueError: No JSON object could be decoded
INFO[9116] container status

Thanks

@c0ze
Copy link
Contributor

c0ze commented Sep 22, 2017

@Tofull we have a new release 0.2.65 which should fix this issue ! Please let us know if this works for you !

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

Successfully merging a pull request may close this issue.

2 participants