#6 Check availability of git-annex content

Ditutup
dibuka 3 tahun lalu oleh sprenger · 7 komentar

It seems the content of some files is not available any more since 534ceaaec4

Using earlier commits should still allow to access the content.

It seems the content of some files is not available any more since https://gin.g-node.org/INT/multielectrode_grasp/commit/534ceaaec49784f182cec22111ca29cd70cead25 Using earlier commits should still allow to access the content.
Michael Denker komentar 3 tahun lalu
Pemilik

So, you mean, the actual data (nev, nsx, etc) files are not available via git-annex or gin? I just tried using web-download, there I couldn't find files that don't download...

So, you mean, the actual data (nev, nsx, etc) files are not available via `git-annex` or `gin`? I just tried using web-download, there I couldn't find files that don't download...
sprenger komentar 3 tahun lalu
Kolaborator

@stellalessandra pointed out that she experienced issues when using gin get and gin get-content.

@stellalessandra pointed out that she experienced issues when using `gin get` and `gin get-content`.
Michael Denker komentar 3 tahun lalu
Pemilik

Indeed, getting the latest lilou files leads to wrong files being downloaded by the client. From the web interface downloading the same file works as a workaround.

Indeed, getting the latest lilou files leads to wrong files being downloaded by the client. From the web interface downloading the same file works as a workaround.
Michael Denker komentar 3 tahun lalu
Pemilik

Indeed, the previous commit still works for me. Any idea what the latest commit 534c actually did? I assume there was not change to the data itself... Maybe the best would be do revert to :3266 and make a new commit.

Indeed, the previous commit still works for me. Any idea what the latest commit `534c` actually did? I assume there was not change to the data itself... Maybe the best would be do revert to `:3266` and make a new commit.
sprenger komentar 3 tahun lalu
Kolaborator

I reverted the last commit and it seems to work again. My feeling is that 534c was not intended for this remote / branch, but a side effect of working on #5. Sorry for that.

I reverted the last commit and it seems to work again. My feeling is that `534c` was not intended for this remote / branch, but a side effect of working on #5. Sorry for that.
sprenger komentar 3 tahun lalu
Kolaborator

@stellalessandra, can you confirm it is working for you again?

@stellalessandra, can you confirm it is working for you again?
Michael Denker komentar 3 tahun lalu
Pemilik

I can confirm it works again for me -- thanks for the reversion!

I can confirm it works again for me -- thanks for the reversion!
Masuk untuk bergabung dalam percakapan ini.
Tidak ada tonggak
Tidak ada penerima
2 Peserta
Memuat...
Batal
Simpan
Belum ada konten.