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

AIFlow support python3.6 #364

Open
jiangxin369 opened this issue Jul 25, 2022 · 0 comments
Open

AIFlow support python3.6 #364

jiangxin369 opened this issue Jul 25, 2022 · 0 comments

Comments

@jiangxin369
Copy link
Contributor

Describe the feature

AIFlow support python3.6

Describe the solution you'd like

Describe alternatives you've considered

Additional context

When run aiflow with python3.6, notification server blocks wich following logs:

[2022-07-25 14:07:07,682 - server.py:68 [MainThread] - INFO: Notification server started.
[2022-07-25 14:07:18,780 - server.py:189 [Thread-1] - ERROR: Lock is not acquired.
Traceback (most recent call last):
  File "/root/venv_for_aiflow/lib64/python3.6/site-packages/notification_service/server.py", line 185, in _call_behavior_async
    return await behavior(argument, context), True
  File "/usr/lib64/python3.6/asyncio/coroutines.py", line 225, in coro
    res = yield from await_meth()
  File "/root/venv_for_aiflow/lib64/python3.6/site-packages/notification_service/service.py", line 221, in _list_all_events
    pass
  File "/usr/lib64/python3.6/asyncio/coroutines.py", line 212, in coro
    res = func(*args, **kw)
  File "/usr/lib64/python3.6/asyncio/locks.py", line 86, in __aexit__
    self.release()
  File "/usr/lib64/python3.6/asyncio/locks.py", line 207, in release
    raise RuntimeError('Lock is not acquired.')
RuntimeError: Lock is not acquired.
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

No branches or pull requests

1 participant