fix: débogage API Python + client Node - Aicha#10
Open
elouadiaicha wants to merge 11 commits into
Open
Conversation
elouadiaicha
changed the title
elouadiaicha
changed the title
elouadiaicha
changed the title
elouadiaicha
changed the title
This file contains hidden or 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
1 participant
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.
Plusieurs bugs empêchaient la communication entre l’API Python Flask et le client Node.js.
Les corrections ont porté sur des variables non définies, un mauvais port Flask, un chemin de fichier incorrect, une dépendance axios invalide ainsi qu’une mauvaise propriété utilisée dans la réponse Axios.
Après correction, le client Node.js récupère correctement les données de l’API Python et affiche le rapport des logs Azure.