-
Notifications
You must be signed in to change notification settings - Fork 139
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
Create Plan Fail #699
Comments
Probably a duplicate of #686 |
bilbof
added a commit
to bilbof/iris
that referenced
this issue
Apr 11, 2022
The api makes use of [gevent], a coroutine based networking library which relies heavily on monkey patching the stdlib. From the [gevent.monkey] docs: > Warning Patching too late can lead to unreliable behaviour > (for example, some modules may still use blocking sockets) or even errors. This appears to have happened here. Thanks to @allwyn-pradip for pointing me at the right file in PR linkedin#690. Resolves linkedin#686, linkedin#699, linkedin#644. Blog on gevent: https://eng.lyft.com/what-the-heck-is-gevent-4e87db98a8 > In the case of gevent — monkey patching has to be the absolute first thing a process does [gevent]: https://www.gevent.org/index.html [gevent.monkey]: https://www.gevent.org/api/gevent.monkey.html
diegocepedaw
pushed a commit
that referenced
this issue
Apr 11, 2022
The api makes use of [gevent], a coroutine based networking library which relies heavily on monkey patching the stdlib. From the [gevent.monkey] docs: > Warning Patching too late can lead to unreliable behaviour > (for example, some modules may still use blocking sockets) or even errors. This appears to have happened here. Thanks to @allwyn-pradip for pointing me at the right file in PR #690. Resolves #686, #699, #644. Blog on gevent: https://eng.lyft.com/what-the-heck-is-gevent-4e87db98a8 > In the case of gevent — monkey patching has to be the absolute first thing a process does [gevent]: https://www.gevent.org/index.html [gevent.monkey]: https://www.gevent.org/api/gevent.monkey.html
@bla-ckbox This should be fixed now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I still encounter issues below when testing with the master branch commit 500822a
Error: Invalid plan - Priority not found for step 1
when saving planTarget type user not found
on /v0/targets/usersync_targets.py seems to be running fine:
target_type, target, and priority are not empty
The problem also appears with the default dataset.
Originally posted by @bla-ckbox in #644 (comment)
The text was updated successfully, but these errors were encountered: