Getting Timeout Error during Execution #71
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: DGNum/uptime-kuma-api#71
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi,
While making API calls to Uptime Kuma, frequently getting this Timeout Exception.
File "/var/task/uptime_kuma_api/api.py", line 1346, in delete_monitor return self._call('deleteMonitor', id_) File "/var/task/uptime_kuma_api/api.py", line 547, in _call r = self.sio.call(event, data, timeout=self.timeout) File "/var/task/socketio/client.py", line 287, in call raise exceptions.TimeoutError()
when the calls are made from local it has no issue. But when made from a lambda or an EC2, it gets this problem. For Example , if I'm making a get_monitors() call first and if I try to delete few based on the response, It gets timedout there. Logically only one works fine.
Am I missing anything ? can someone help ! TIA
I am using the ansible collection that uses this api in azure and getting timeouts quite often myself.
Is this project actively maintained?
In the official documentation, you can define the timeout time as follows, api = UptimeKumaApi('http://localhost:3001', 100), with an example timeout time of 100 seconds.
Docs: https://uptime-kuma-api.readthedocs.io/en/latest/api.html#uptime_kuma_api.UptimeKumaApi.get_monitor
i also have the timeout error. Unfortunately, it's currently not working with my playbooks. @lucasheld it would be great of you can give us a sign if you are currently maintaining this project or not. Thanks!