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
I have come across a few occasions where I want to download files over again or want to download datasets with new versions and am unable to do so due to the "<QUERY_ID> is already up-to-date" response. Would it be possible to add a '-f' or '--force' option to ignore the database and download the files anyway, regardless if the file ID's are already allocated? Thanks.
The text was updated successfully, but these errors were encountered:
@meteorologist15 maybe this is a workaround in the meantime, but you could change your db file to a temporary/alternative db file in order to force the download. If you're 100% there are no newer filers to be replicated there should be no lost in sync with between db and filesystem either.
I have come across a few occasions where I want to download files over again or want to download datasets with new versions and am unable to do so due to the "<QUERY_ID> is already up-to-date" response. Would it be possible to add a '-f' or '--force' option to ignore the database and download the files anyway, regardless if the file ID's are already allocated? Thanks.
The text was updated successfully, but these errors were encountered: