Keeping the right tokens for every websocket connection #225
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Plus de 401 pour les ws.
J’ai été un peu brutal sur le refresh_ws de api.py , sinon ça tentait de refresh le deuxième ws avec le endpoint du premier. Je pense que faire une liste ou un dict serait peut être plus simple ensuite mais ça demande quand même un peu de refactor.
Pour ce qui bloquait, il me semble que chaque ws a besoin de son propre token, le shared_token c’est probablement ce qui bloque, j’ai donc modifié pour que les deux soit bien avec leur propre token (facile avec la conf), et je récupère bien l’url.