Description of the problem:
I cannot upload an experiment to Pavlovia. I tried to open PsychoPy several times, created a new folder, logged out and logged in to Pavlovia. I get the following error message:
Traceback (most recent call last):
File “C:.….…\AppData\Local\Programs\PsychoPy\lib\site-packages\psychopy\app\pavlovia_ui\sync.py”, line 162, in submit
self.project.refresh()
File “C:.….…\AppData\Local\Programs\PsychoPy\lib\site-packages\psychopy\projects\pavlovia.py”, line 636, in refresh
raise ValueError(f"Could not find project with id {self.id} on Pavlovia: {requestVal}")
ValueError: Could not find project with id 345526 on Pavlovia: {‘origin’: ‘https://pavlovia.org/api/v2/experiments/345526’, ‘context’: …
I am getting the same error message. See below At one point, I think I saw that there was some maintenance being done to Pavlovia today and that the ability to add new users might be impacted. Is the same true for new experiments? I have tested this with 3 different .psyexp files etc. and get the same error.
Traceback (most recent call last):
File “/Applications/PsychoPy.app/Contents/Resources/lib/python3.8/psychopy/app/pavlovia_ui/sync.py”, line 162, in submit
File “/Applications/PsychoPy.app/Contents/Resources/lib/python3.8/psychopy/projects/pavlovia.py”, line 657, in refresh
ValueError: Could not find project with id 345537 on Pavlovia: {‘origin’: ‘https://pavlovia.org/api/v2/experiments/345537’,…
Here is relevant text from the server maintenance information (full link below). It seems likely this is the issue.
Similarly, some of you may notice that a newly created experiment is not appearing on their dashboard on pavlovia.org : it will also have appeared by Friday, at which point it will be possible to pilot it.
This is indeed a temporary, regrettably unintended, side-effect of today’s maintenance.
Your experiment has been created on our GitLab server but it is not available just yet on the pavlovia server, which is confusing the PsychoPy Builder.
I am on it and hope to have this sorted in a few hours, and certainly by tomorrow (Friday).
With my apologies for the glitch!