This repository has been archived by the owner on Nov 15, 2024. It is now read-only.
vgrange/fix_vulnerabilities_signaled_by_github (again) #402
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
dejafait
changed the title
|
FTR https://valodata.slack.com/archives/C2RR5PZD3/p1567414270000500 OK en recette KO en production, toutes les pages donnent cette 404 :-(
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.
|
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
force-pushed
the
vgrange/fix_vulnerabilities_signaled_by_github
branch
from
341e38a
to
675b0b4
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
second attempt after 404 fiasco of first attempt #400