-
Notifications
You must be signed in to change notification settings - Fork 13
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
Always get TimeoutError while invoking place_order in Google Cloud Functions #149
Comments
BTW, it works fine in my local development laptop, I just simply deploy it to Google Cloud and the region of the cloud instance is asia-east1 which is supposed to be located in Changhua. |
@AugThWu
|
Hi @Pofatoezil If I remember correctly, I got TimeoutError while invoking place_order thus hadn't invoked logout yet, so I have no idea if logout has the same problem. I could paste the call stack here as well if necessary :) |
Hi @AugThWu 最近我為了將TradingView 交易策略的webhook alerts 串接到自動下單,所以研究將shioaji api放到google cloud function中
但仍然有許多狀況:
希望以上資訊能幫助你排除狀況 |
Any follow up on this issue? I am using shioaji==1.2.2 and I have TimeoutError occasionally when calling api.login function on GCP Cloud Functions. I have no issue on my laptop. |
I got the same issue, any update on it? |
我的狀況是在 login 就出現這樣的問題。 |
想請問有解決方法了嗎?因為 gcp serveless 服務沒辦法修改系統時間,python 使用 pytz 改時區也沒辦法解決 |
@jasonlin0189impv 選擇台灣區域的Server (Asia east 1)來部屬,但不是每次都可以的 |
shioaji version: 1.1.11
Hi there, I found that I always get TimeoutError while invoking place_order() in Google Cloud Functions, after checking the logs, looks like it dues to the timezone in the cloud instance is UTC, which is 8 hours later than Taipei (CST timezone), I guess this is the reason of TimeoutError.
Since I didn't find an easy way to change the time zone of the cloud instance, guessing the simplest fix is to always convert the time with the CST timezone before sending the request, could you please take a look at this issue?
Your API is such a great work, it would be better if it works fine in the cloud :)
The text was updated successfully, but these errors were encountered: