org.hibernate.PropertyValueException importing an OSWeb study on jatos.mindprobe.eu

Wouter

Hiya,

I'm trying to upload an experiment onto jatos.mindprobe.eu ; the same study which worked fine on experiments.jatos.org last weekend. However, this time around some interesting stuff happens when I'm trying to use the 'import study' button.

First off, nothing gets visibly imported, but something clearly happened: when I retry, I get confronted with a message like :

You are about to import the study "pilot_imcat" and its directory "0aad6d916ddaf004cad39650f5e043c2". Unfortunately a directory with this name already exists. If you proceed the directory will be renamed to "0aad6d916ddaf004cad39650f5e043c2_2".

Once that screen passes, I get a red error message that reads:

org.hibernate.PropertyValueException: not-null property references a null or transient value : models.common.Component.uuid

No study entry gets created, so my homedir on the server is still completely empty.

The same behavior occurs with a MWE, [Opensesame default template immediately exported to a jatos zip, attached].

I have no clue where to move from here, so any help would be greatly appreciated!

I'm running OSWeb1.3.8.2 on OpenSesame 3.3.8b1, in case that helps.

testtest.osexp.zip

.

sebastiaan

Hi @Wouter ,

I get the same error, indeed simply when exporting the default template and then importing into the MindProbe JATOS. There's also an error in the browser console, so I posted a screenshot of that so that @kri can take a look at that.

As you know, MindProbe is in a testing phase now! Still a few kinks to be ironed out.

— Sebastiaan

kri

Thanks for reporting this. I will look into this asap and fix it before we go live on Monday.

kri

Hi guys! I just updated the MindProbe JATOS. It can deal with OSWeb studies again. Can you check and confirm?

Wouter

Hi @kri !

Thanks for fixing this. Both the mwe and my experiment now seem to upload just fine. (I still get the duplicate folder warning/renaming though, but by generating a new file with a new internal ID I should be able to prevent that.)

Thanks!

W

by generating a new file with a new internal ID I should be able to prevent that

Edit: yep. Uploading a newly generated jatos file works without any issues.