Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Supported by

Saving and publishing to JATOS gives Error: JZIPUploadError

Hi all,

Whenever I upload a task to JATOS for the first time, via the OSWeb and JATOS control panel I always get the message:

Error: JZIPUploadError

Unknown upload error (status code 201)

A JZIPUploadError is raised when an experiment could not be uploaded to a JATOS server. This may happen when the JATOS server or API token are incorrect. This may also happen when there is a problem with the internet connection.

Interestingly, the task is actually uploaded to JATOS without issue, and on subsequent saves (with the same UUID), the message does not appear.

I'm running:

Opensesame 4.1.6

JATOS v3.10.4

My colleagues have the exact same issue. While it's not a critical issue, as the task it actually uploaded despite the error message, it does lead to confusion and questions from our researchers.

Kind regards,

Kerwin

Comments

  • Hi Kerwin,

    is this something new that happened only after you updated JATOS or OpenSesame?

    Best,

    Kristian

  • Ah that's hard to say. I've encountered this issue for a while now, but we've only included this in our official acceptance test last round, so we hadn't properly documented the issue before. The only thing I can say is that we see this same issue on all our machines (and multiple accounts) running this version combination of Opensesame and JATOS.

  • My guess is that this is an issue with JATOS' API consolidation that happened with 3.10.x. The HTTP status codes returned by JATOS got in line with the standards. If the study does not exist yet in JATOS a 201 (created) is returned. A subsequent import of the same study (with the same UUID) leads to an overwrite and a 200 is returned. My guess is that OpenSesame only checks for a 200 and reports a 201 as a failure. But this should be confirmed by the OpenSesame people. I'll ask them.

  • Hi, I was just informed that this is already fixed in the newest version of OpenSesame and you just have to update. Best, Kristian

Sign In or Register to comment.