-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
api.py or Meteor Server 2 minutes timeout while cloning board #5371
Comments
If there is requirement to clone board immediately, that requires: a) Different database, that has feature of immediate branching like |
I looked at it more this morning. I thought the emails I received where linked with cards I did subscribe in my main board, but in fact it's just emails with card creation webhook messages. Maybe it's this webhook ongoing process that doesn't manage to finish fast enough. By the way, {{{wekan-username}}} is always "undefined" in the massage describe on wekan/docs/wekan.wiki/Webhook-data.md Line 17 in 09f6dcb
Could those webhooks be disable while cloning or using API? Does it give any ideas of what is going on? There is no need for immediate board cloning. Looking at it, I've got the feeling everything is well clone on my board (but my thumb card information). |
Sorry to come back on it, but I tried to read the documentation regarding webhook and I don't find anywhere to go to modify configuration or wekan to avoid this behaviour. I've been to global configuration: no webhook But all administrators receive emails (one by list of the original board), with the messages described in wekan/docs/wekan.wiki/Webhook-data.md, one message for each card created during the duplication. It doesn't happen when cloning through the GUI, only through API. I try to find what trigger this. |
1. It takes too long while server stops after 2 minutes (wekan#5371). 2. It is useless, because when you copy a board, most of the time your users don't want to be notified of every copied cards.
Issue
Server Setup Information
Problem description
Times shows that it stop exactly after 120s. python request http used in api.py is known to wait forever, so I would blame meteor.
This board is not so big, but get cards that send email each time they are cloned (maybe one of the reason).
Maybe there is already an option to rise this limit.
Logs
Nothing in the log around those times.
The text was updated successfully, but these errors were encountered: