Error when launching job in new workspace

When launching a job and selecting “Run job in: new workspace”, an error message arises reading

'None Type' object is not superscriptable

The new workspace is created, and the job is copied into the new unnamed workspace. However, it also remains linked in the old workspace. The job is not launched.

I’ve observed this on a machine running CentOS 7 but I’m currently seeing it on Ubuntu server 20.04.2 as well. I’m running the latest patched version of cryoSPARC.

cryosparc@troll:~$ cryosparcm status
----------------------------------------------------------------------------
CryoSPARC System master node installed at
/troll/scratch/cryosparc/cryosparc_master
Current cryoSPARC version: v3.2.0
----------------------------------------------------------------------------

CryoSPARC process status:

app                              RUNNING   pid 32752, uptime 3 days, 17:23:13
app_dev                          STOPPED   Not started
command_core                     RUNNING   pid 32628, uptime 3 days, 17:23:22
command_rtp                      RUNNING   pid 32690, uptime 3 days, 17:23:19
command_vis                      RUNNING   pid 32664, uptime 3 days, 17:23:20
database                         RUNNING   pid 32517, uptime 3 days, 17:23:25
liveapp                          RUNNING   pid 32774, uptime 3 days, 17:23:11
liveapp_dev                      STOPPED   Not started
webapp                           RUNNING   pid 32724, uptime 3 days, 17:23:15
webapp_dev                       STOPPED   Not started

----------------------------------------------------------------------------

global config variables:

export CRYOSPARC_LICENSE_ID="***"
export CRYOSPARC_MASTER_HOSTNAME="troll"
export CRYOSPARC_DB_PATH="/troll/scratch/cryosparc/cryosparc_database"
export CRYOSPARC_BASE_PORT=39000
export CRYOSPARC_DEVELOP=false
export CRYOSPARC_INSECURE=false
export CRYOSPARC_CLICK_WRAP=true

Hi @posertinlab,

Thanks very much for your post - we’ve identified the bug. A fix will be available in the next cryoSPARC release!

- Suhail

Hi @posertinlab, this is now fixed in v3.3!

1 Like