Long running Jobs give connectionError when signing in
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 45/100
Direzione di ricerca
Start at the server.auth.sign_in entry point and inspect how its HTTP connection or session behaves after a 10-minute-to-4-hour delay. Reproduce the reported ConnectionError with the stated Python and TSC versions; done means long-running jobs can sign in reliably without caller retry loops, with regression coverage if the project has a relevant test location.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Describe the bug
I have a package where I standardize the way we're authenticating. So the server and tableau_auth are initialized on import of my package. Then downstream there are jobs that run anywhere from 10 minutes to 4 hours. But if they use
with server.auth.sign_in(tableau_auth):
print("do_anything")
It fails. Funnily enough, after it runs I can run the same function and it runs fine.
I can get around it by just trying multiple times for the sign in.
def sign_in():
for i in range(5):
try:
cxn = server.auth.sign_in(tableau_auth)
return cxn
except requests.exceptions.ConnectionError as e:
continue
except:
raise
if i == 5:
raise ConnectionError("Failed to connect after 5 attempts")
# and doing
with sign_in():
print("do_anything")
Versions
Details of your environment, including:
- tableau online
- Python version 3.9.12
- TSC library version =0.18.0
Results
ConnectionError: ('Connection aborted.', ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None))
Other Info
I tried to sign in multiple times because of this SO post
NOTE: Be careful not to post user names, passwords, auth tokens or any other private or sensitive information.
- Lingua principale
- Python
- Stelle
- 716
- Fork
- 446
- Merge medio
- 8g 8h
- PR unite (30g)
- 2
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di tableau/server-client-python
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
tableau/server-client-python#1865 ·
-
in-progress
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
tableau/server-client-python#1829 · 1 commento ·
-
enhancement gap needs investigation
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
tableau/server-client-python#1322 · 1 commento ·
-
[Type2] Allow Incremental Refresh type schedules to be added via `server.schedules.add_to_schedule` Apertahelp wanted Server-Side Enhancement ui-exists
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
tableau/server-client-python#1101 · 3 commenti ·
-
enhancement good first issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
tableau/server-client-python#783 · 5 commenti ·
Tutte le issue di tableau/server-client-python
Issue simili
-
essnmx good first issue
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 95/100
-
[Feature] 奇物选择添加优先级 Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
Giskard-AI/giskard-oss#2840 · 1 commento ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Apertaarea: repo bug perceived difficulty: 2
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
yeti-platform/yeti#1380 ·