398 improve db task executions traces #399
Merged
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
rv2931
force-pushed
the
398_improve_db_task_executions_traces
branch
from
84f5f38 to
b37b24e
Compare
marthevienne
approved these changes
Jan 7, 2025
…, only one working for each pooling period
rv2931
force-pushed
the
398_improve_db_task_executions_traces
branch
from
973ac15 to
f0c09de
Compare
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.
Fix #398
Ajout des colonnes duration et position_count à la table task_executions et adaptation des tâches load_spire_data_from_api, clean_positions et create_update_excursions_segments
On obtient des choses comme ça
Le déploiement des cette évolutions est bloqué actuellement par l'issue #349 qui déclenche une erreur sur la tâche create_update_excursions_segments
C'est potentiellement possible d'appliquer cette évolution à partit du commit actuel en production, cela permettra d'attendre de résoudre le #349
Ajout d'un mécanisme de syncrhonisation en cas de lancement de plusieurs load_spire_data_from_api en paralèlle sur plusieurs machines pour fiabiliser l'aquisition #404