Data were not synced from my local repos to amazon #24
Comments
|
With only one file (easier to debug), and git remote at the end: @kousu in case you see this... help needed 🙏 |
|
On my local laptop (the one I pushed the data from), I get this: So, for some reasons, the data were not pushed to amazon. I don't know why, and I don't know how to fix this. |
|
Hum, my local repos on the laptop might have a problem. When I do this: Whereas on compute canada, i get that: |
jcohenadad
changed the title
|
The labels that were supposed to be added in #15 are needed ASAP for further experiments, so I will try to retrieve them and push them to the main git-annex repos. starting directly from @lrouhier branch: |
|
@lrouhier i'll try to copy the labels on my local station and re-upload to amazon. Are the labels still there? |
|
Assuming the answer to #24 (comment) is yes, i went ahead and tried syncing one label: Now, going to Github to see if I can open a PR, I don't see my branch 😭 (usually, three PR choices appear, now there are only two): |
|
The answer is yes the data are there. |
|
Maybe there is something wrong with my local repos, so trying to create a new one from scratch: Hum... the message cat .git/config gives me: which seems to be missing the following piece (present in my other local repos): |
|
Maybe the problem is because i cloned via https instead of ssh. So, trying again with ssh: Now trying the init again: interestingly, the error message is slightly different than previously #24 (comment). cat .git/config (still no remote "amazon") |
|
It's normal to see this message, because the |
|
Thank you for the quick reply @Drulex. However, it seems that something got "broken", because I don't seem to be able to retrieve the data from amazon anymore using the commands which used to work previously. If you have any clue, that would be hugely appreciated. |
|
Indeed I can see that some files can't be retrieved.. I will try to take a look later tonight, it's definitely related to recent commits. Perhaps not all branch were merged as supposed to (although it's hard to say because there isn't a whole lot of documentation on |
|
thanks. If it could be of any help, it is definitely possible for me to re-do the latest commits (and do a "hard reset" to a point where things are working). |
|
It looks like files stopped resolving at commit 2598880. In the snippet below I reset the branch to that specific commit and try to download on of the files that was committed. So it appears that the files exist on @jcohenadad's filesystem, but weren't synced to It looks like you synced the metadata without actually uploading the files? |
|
Ok I just read the issue description (sorry I hadn't) and yes indeed you did not upload the files to amazon. Relevant: #18 (comment) |
|
I've got a patch for this ready: Homebrew/homebrew-core#60667 I'm just testing it now. It should be published by the end of the week and then we can put this behind us. |
Context
I have cloned the git-annex repos on my laptop, and use it to push on amazon s3. So far, everything was working fine.
Recently, I made some changes on my local repos, and synced it (or I thought I did) to Amazon, by doing the following procedure:
Note: I wanted to do
git annex sync --content amazonafter the commit, according to our procedure, but it failed (see #18).So I went ahead, and opened the PRs on Github, and then rebased+merged them on master.
After merging, I went back to another local copy of the repos (on compute canada cluster), and did the following:
And ran into a failure:
Full details
The text was updated successfully, but these errors were encountered: