All those repos are private, but since I can't access the interface I cannot make them public to help with debugging. :-/
This is not super urgent but I felt like I should report this in case others encounter a similar problem (and also possibly to be able to delete those "unused" repos).
A while back I renamed a repo to this:
- https://gin.g-node.org/RemiGau/layer_fmri_analysis_survey
I then wanted to update my datalad sibling config locally to keep track of the name change.
But after doing this I have been unable to access the repo via the web interface.
The webpage only displays this :
```
template: repo/view_list:9:72: executing "repo/view_list" at <.LatestCommit.Author.Email>: invalid value; expected string
```
---
I have just tried to create a new repo (https://gin.g-node.org/RemiGau/layer_analysis_many_pipelines) to push the data to it. But I did set it up with HTTPS and not SSH (my mistake). And I am still getting the same error.
Now trying to push onto a third repo set up with ssh and this seems to work: https://gin.g-node.org/RemiGau/layer_fmri_many_pipelines
---
All those repos are private, but since I can't access the interface I cannot make them public to help with debugging. :-/
---
This is not super urgent but I felt like I should report this in case others encounter a similar problem (and also possibly to be able to delete those "unused" repos).
Thanks a lot for reporting this issue! I will try to reproduce the problem on our dev machine to pinpoint and fix the issue.
If you remember, would you also be willing to post the datalad commands you ran before the issue occurred?
Hi Remi!
Thanks a lot for reporting this issue! I will try to reproduce the problem on our dev machine to pinpoint and fix the issue.
If you remember, would you also be willing to post the datalad commands you ran before the issue occurred?
The exact sequence of events I reported to the datalad team on their chat that led to this was:
rename GIN repo
do a datalad siblings configure to update the url locally
push
bug
I think some tried to reproduce the issue but did not manage.
Let me know if you need access to the repo where the data now lives to see if you can find anything.
pretty sure I ran this one
```
datalad siblings configure --name gin --url git@gin.g-node.org:/RemiGau/layer_fmri_analysis_survey.git
```
And then I pushed.
The exact sequence of events I reported to the datalad team on their chat that led to this was:
- rename GIN repo
- do a datalad siblings configure to update the url locally
- push
- bug
I think some tried to reproduce the issue but did not manage.
Let me know if you need access to the repo [where the data now lives](https://gin.g-node.org/RemiGau/layer_fmri_many_pipelines) to see if you can find anything.
A while back I renamed a repo to this:
I then wanted to update my datalad sibling config locally to keep track of the name change.
But after doing this I have been unable to access the repo via the web interface.
The webpage only displays this :
I have just tried to create a new repo (https://gin.g-node.org/RemiGau/layer_analysis_many_pipelines) to push the data to it. But I did set it up with HTTPS and not SSH (my mistake). And I am still getting the same error.
Now trying to push onto a third repo set up with ssh and this seems to work: https://gin.g-node.org/RemiGau/layer_fmri_many_pipelines
All those repos are private, but since I can't access the interface I cannot make them public to help with debugging. :-/
This is not super urgent but I felt like I should report this in case others encounter a similar problem (and also possibly to be able to delete those "unused" repos).
Hi Remi!
Thanks a lot for reporting this issue! I will try to reproduce the problem on our dev machine to pinpoint and fix the issue.
If you remember, would you also be willing to post the datalad commands you ran before the issue occurred?
pretty sure I ran this one
And then I pushed.
The exact sequence of events I reported to the datalad team on their chat that led to this was:
I think some tried to reproduce the issue but did not manage.
Let me know if you need access to the repo where the data now lives to see if you can find anything.
Great, thank you for the details!