I am running an experiment and want to change one small thing in a setting. Since the experiment was originally uploaded on different desktop, I had to clone the experiment (through GitHub) and I changed the issue and wanted to upload it back. While Github is able to push everything to the Gitlab repository and I can see the uploaded files, I cannot synchronize the project in PsychoPy, as I get following error:
File “C:\Users\Sarka Kadava\AppData\Local\Programs\PsychoPy\lib\site-packages\git\cmd.py”, line 983, in execute
raise GitCommandError(redacted_command, status, stderr_value, stdout_value)
git.exc.GitCommandError: Cmd(‘C:\Users\Sarka Kadava\AppData\Local\Programs\PsychoPy\MinGit\cmd\git.exe’) failed due to: exit code(1)
cmdline: C:\Users\Sarka Kadava\AppData\Local\Programs\PsychoPy\MinGit\cmd\git.exe pull Wim Pouw / FLESH_EXP_1A · GitLab master
stderr: ‘fatal: Couldn’t find remote ref master
warning: redirecting to Wim Pouw / FLESH_EXP_1A · GitLab’
Whether the sync in PsychoPy is necessary or not, I cannot see the change of my experiment when running it on Pavlovia. I don’t know whether that is because of the common problem with cache (?) or because of this error.
Thanks for any suggestions for solution
my procedure to get a deployed experiment for a new computer is different. I start PsychoPy on the new computer, select Find existing study (at pavlovia.org), select Me in the Search for projects online, and sync/create the experiment I want to copy to the new machine. Then I make the edits and sync them back to Pavlovia.
The problem you are facing is that there is no branch called master in your forked project, see here github - git pull master with error: fatal: couldn't find remote ref master - Stack Overflow
Best wishes Jens
I do the same. An important point is to sync before making changes when you have local copies in more than one location.
I do it as you write but I get the same error when cloning/syncing. Then I see that the pulling was actually succesfull and I have the experiment in new folder - but when I open it and sync it, it agains throws the error. Besides that - the thing I want to change is a presentation limit (for presentation cap in shelf) but when I check the settings at this new cloned file, the change is already there. So I guess there is also some problem with Pavlovia noticing this change, because the presentation limit is still set on the old number when I run it
An update: I created branch ‘master’ in my gitlab repository - now everything worked, I cloned, changed, synced, then within gitlab made a merge request and comitted changes from master branch to main. All good, but Pavlovia still doesn’t see the change in my presentation limit
If the change is visible in GitLab then try using an incognito tab or Ctrl-Shift-R to flush the cache.
Haha, yes, that worked! Thank you