-
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
iris Plan issue #644
Comments
@diegocepedaw any update what is causing this issue. |
@allwyn-pradip unfortunately I have not had much bandwidth recently to look at community issues lately. Do you remember which release version this issue was introduced in? I haven't encountered this issue myself, can you give me more details on your current Iris setup as well? |
@diegocepedaw I am at the latest version 1.36 testing it for python3 |
@allwyn-pradip what do you get if you run |
@diegocepedaw the output for the query is fine. Also facing the issue Error: Invalid plan - Target NOC-Team not found for step 1. |
Is the sync targets script running and correctly able to git oncall-api? |
@diegocepedaw what is the sync target script? |
@diegocepedaw i saw there is one sync_target.py code is available in srs/iris/bin. executed manually and getting below error. could you please help here. 2022-02-08 11:26:10,489 ERROR root Error syncing from oncall! |
@mohammad-sajid the sync_targets.py script is what syncs teams and users from oncall-api, you will need this running if you want to automatically have oncal-api teams become available as targets in Iris. If you are running it locally with the make file you should be able to run |
Thanks, @diegocepedaw . after verifying user_contact table now am able to sync between the iris and oncall app. Thanks for your support @diegocepedaw |
I still encounter the issues discussed above when testing with the master branch commit Version 500822a
sync_targets.py seems to be running fine:
target_type, target, and priority are not empty
|
I have also hit the same issue. Steps to reproduce:
@allwyn-pradip mentioned that this issue is fixed by #690. I ran those changes locally and found that the issue was fixed, but haven't yet figured out what particular change resolved the bug. Edit: turns out it was gevent's monkey patching! |
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
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
with the new images, new or existing plans do not get saved.
the error pops up as
Error: Invalid plan - Priority not found for step 1
even when the priority are setup
The text was updated successfully, but these errors were encountered: