Hello,
Recently I realised that I do not managed anymore to open a session from a specific (old) commit (to come back from an earlier version of my Renku project).
When I check from which version I open the project, I can see in the session detail that the commit is the “old” one, but in the git history tab of the Jupyterlab interface, I see that the project is apparently to its lastest version. So it does not match.
Is there a reason why? Or how can I indeed get back to an earlier version of my project?
(I tested this on several of my Renku projects)
Thank you.
@colinem I think this may be a bug. I am looking into it.
For the time being you can always switch to any other git commit or branch in your session.
For example: git checkout another_branch will checkout another_branch if it exists otherwise error out.
If you want a specific commit on a specific branch (i.e. not the latest commit on a branch). Then you can run git checkout another_branch to get the latest commit of the branch that you want. And then run git reset --hard <commit-sha> to get to the specific commit. Please note that if you run the git reset --hard ... then you will lose all uncommitted changes and also any upushed commits that you have committed on the active branch.
@colinem yes this is a bug. But I can confirm that we are using the right image tied to the commit that you selected. The problem is that when we clone your repo we just go to the latest commit on the branch you have selected rather than the specific commit you wanted.
I have opened an issue here: Renku v1 cloning a repo always goes to the HEAD of the branch · Issue #619 · SwissDataScienceCenter/renku-data-services · GitHub to track this problem.
But as I mentioned before you can (for the time being) easily switch to whichever branch or commit you want. And the docker image for your session is the correct one for the commit you selected.
Ok thanks @tolevski for the quick answer and confirmation that the docker image should be the correct one associated with the selected commit.