Users from the meteo swiss cluster reported seeing this when trying to launch a session on a public project, with a public github repository.
It seems that this can happen when we cannot reach github to get additional information about the repository. But the error message should be more descriptive, not just metadata_unknown. Even I had to dig through the code to see what this means. It seems that there is a an enum in the code that contains different erorr cases and conditions that in some cases gets piped straight into the error message without any disambiguation.
Seen on renku 2.17.1.
It may be that this is worse or more common when the repo is saved with the url pointing to the ui page only. I.e. like https://github.com/MeteoSwiss/opendata-nwp-demos rather than https://github.com/MeteoSwiss/opendata-nwp-demos.git. But I have not been able to reproduce this even when the repo url is not in the optimal form.
Users from the meteo swiss cluster reported seeing this when trying to launch a session on a public project, with a public github repository.
It seems that this can happen when we cannot reach github to get additional information about the repository. But the error message should be more descriptive, not just
metadata_unknown. Even I had to dig through the code to see what this means. It seems that there is a an enum in the code that contains different erorr cases and conditions that in some cases gets piped straight into the error message without any disambiguation.Seen on renku 2.17.1.
It may be that this is worse or more common when the repo is saved with the url pointing to the ui page only. I.e. like
https://github.com/MeteoSwiss/opendata-nwp-demosrather thanhttps://github.com/MeteoSwiss/opendata-nwp-demos.git. But I have not been able to reproduce this even when the repo url is not in the optimal form.