You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The top level symptom is a new normalisation spreadsheet has been uploaded, but the new data has not gone live, as something has gone wrong with euctr-tracker-code/deploy/loaddata-eutrialstracker_live.sh (run from crontab).
If we look at our production euctr-tracker-data repository, we can see that it is in an inconsistent state, possibly due to the weirdness about the earlier Aug tracker data:
server:/blah/euctr-tracker-data$ git status
On branch master
Your branch is behind 'origin/master' by 1 commit, and can be fast-forwarded.
(use "git pull" to update your local branch)
Changes to be committed:
(use "git reset HEAD <file>..." to unstage)
modified: new_trials.csv
new file: normalized_sponsor_names.xlsx
nb. repo is at 329efbd1730049067626ead07f5e17d7670a3f55 , which is behind upstream at c3ce0f81e4ac82c5a62fc3eb3e2576f9680e29cb
The text was updated successfully, but these errors were encountered:
I think this is because the normalisation file was incorrectly removed by this automatic commit ebmdatalab/euctr-tracker-data@329efbd - cleaned up the repo to what I think is the correct state, will manually run the loaddata step
appears to have worked - trials count has changed from 10028/13874 to 10396/14207. production git data repo now looks clean & git history is correct - hopefully will work automatically next time!!
This is similar but possibly different to #119
The top level symptom is a new normalisation spreadsheet has been uploaded, but the new data has not gone live, as something has gone wrong with
euctr-tracker-code/deploy/loaddata-eutrialstracker_live.sh
(run from crontab).If we look at our production euctr-tracker-data repository, we can see that it is in an inconsistent state, possibly due to the weirdness about the earlier Aug tracker data:
nb. repo is at 329efbd1730049067626ead07f5e17d7670a3f55 , which is behind upstream at c3ce0f81e4ac82c5a62fc3eb3e2576f9680e29cb
The text was updated successfully, but these errors were encountered: