Open abulte opened 4 years ago
About community resources, this was caused by transport's script which forced the URL to a previous when doing the PUT
to update metadata. It's been fixed but there's still 87 dangling resources https://gist.github.com/abulte/f283a2c2e3dc9102d8f767f0c908637e#file-cr-unsynced-fs-filename-v2-csv. They can be removed.
Going further: we probably should not allow setting the URL from the API when a resource is of type file
(ie not remote
). This would have prevented this whole mess.
Keeping this open since this one is stil unexplained:
5448d3e0c751df01f85d0572 50625621-18bd-43cb-8fde-6b8c24bdabb3 https://static.data.gouv.fr/resources/fichier-consolide-des-bornes-de-recharge-pour-vehicules-electriques/20200920-224338/bornes-irve-20200920.csv fichier-consolide-des-bornes-de-recharge-pour-vehicules-electriques/20200820-224444/bornes-irve-20200820.csv
and #2542 must be fixed too.
Sometimes, especially on community resources from transport.data.gouv.fr, our
fs_filename
is not synced withurl
. After our cleanup, it lead topurge-datasets
failing because it tries to remove a not existing file.Tests done so far
On demo.data.gouv.fr:
CommunityResources
300+ occurrences, cf complete list https://gist.github.com/abulte/f283a2c2e3dc9102d8f767f0c908637e.
It happened again this morning, cf
Resources
Cf #2542 for
catalogue-des-donnees-de-data-gouv-fr
. No idea why it failed forfichier-consolide-des-bornes-de-recharge-pour-vehicules-electriques
, this is a pretty standard API upload.