Skip to content
This repository was archived by the owner on Nov 15, 2024. It is now read-only.

Conversation

@dejafait
Copy link
Contributor

@dejafait dejafait commented Sep 2, 2019

second attempt after 404 fiasco of first attempt #400

@dejafait dejafait changed the title vgrange/fix_vulnerabilities_signaled_by_github vgrange/fix_vulnerabilities_signaled_by_github (again) Sep 2, 2019
@dejafait
Copy link
Contributor Author

dejafait commented Sep 2, 2019

FTR

https://valodata.slack.com/archives/C2RR5PZD3/p1567414270000500

OK en recette

KO en production, toutes les pages donnent cette 404 :-(

image

Pourtant en fin de deploy du frontal 1, les URLs frontend ont été testées et renvoyaient bien une 200! o_O Normalement le deploy aurait du casser à cette étape, ainsi le frontal 1 reste HS tandis que le frontal 2 non mis à jour continue de servir 100% du traffic.

image

@dejafait
Copy link
Contributor Author

dejafait commented Sep 2, 2019

@dejafait dejafait self-assigned this Sep 13, 2019
Mainly upgrade Flask to 1.1.1
logging.DEBUG_LOG_FORMAT no longer exists, I dropped it as it is
only used in development and I have no idea why we needed it.
@dejafait dejafait force-pushed the vgrange/fix_vulnerabilities_signaled_by_github branch from 341e38a to 675b0b4 Compare January 3, 2020 10:01
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants