Skip to content
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

Update api requesting issue catching #275

Merged
merged 7 commits into from Oct 22, 2019
Merged

Update api requesting issue catching #275

merged 7 commits into from Oct 22, 2019

Conversation

SimonSAMPERE
Copy link
Collaborator

@SimonSAMPERE SimonSAMPERE commented Oct 17, 2019

As part of the #266 bug investigation.

In case of a problem with the response of the Isogeo API, the error code Qt and the status code http are written in the logs. The objective is to identify more different causes of error.

Bonus : close #273 by replacing types with datatype

catch other error codes
better error catcher
@SimonSAMPERE SimonSAMPERE added bug Problème par rapport au fonctionenment attendu enhancement Amélioration du fonctionnement existant labels Oct 17, 2019
@SimonSAMPERE SimonSAMPERE added this to the version 2.0.0-beta5 milestone Oct 17, 2019
@SimonSAMPERE SimonSAMPERE self-assigned this Oct 17, 2019
@SimonSAMPERE SimonSAMPERE changed the title Update authentication issue catching Update api requesting issue catching Oct 17, 2019
Comment on lines -75 to +76
if len(words) == 1 and len(words[0]) > 33:
final_text = "\n" + words[0][:30] + "..."
if len(words) == 1 and len(words[0]) > 22:
final_text = "\n" + words[0][:19] + "..."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

à quel ticket cette modif est-elle liée ?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

" in 'Preferences/Options/Network'.",
context=__class__.__name__,
),
)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Plusieurs choses :

  • l'alerte est contraire à ce qui est indiqué dans la docstring. Déclenche t'on une erreur s'il y a un proxy sur l'OS mais dans QGIS ? ou l'inverse ? ou les deux ?
  • seul HTTP est testé alors que l'API fonctionne essentiellement en HTTPS. Certes, les proxy gèrent cependant souvent les 2 protocoles sur la même URL mais pourquoi ne pas tester ?
  • de plus comme indiqué sur Slack, cela ne teste que la case cochée ou pas. Or, dans QGIS, la case peut être cochée (donc test=True) mais indiquer d'utiliser le proxy OS (DefaultProxy) https://docs.qgis.org/testing/en/docs/user_manual/introduction/qgis_configuration.html#network-settings

@SimonSAMPERE SimonSAMPERE merged commit f856098 into master Oct 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Problème par rapport au fonctionenment attendu enhancement Amélioration du fonctionnement existant
Projects
None yet
Development

Successfully merging this pull request may close these issues.

corriger le fichier quicksearches.json
2 participants