Closed jernestmyers closed 1 year ago
Not sure if this should be a separate ticket, but sometimes it looks like the config selectors changing makes the visualization try to update. So below, i made a new ranked abundance box, selected my app config, then got this screen
Sometimes this happens if i have already made a plot, and then go change config values. So here i had a fully working plot with Data: Phylum. I changed to this metagenomic parameter, and saw the following.
I switched the param back to Phylum, all works. I go back again to that metagenomic one, and now the job is complete and i can use the plot!
So i think what's happening is the config changing is autostarting a job, and the viz is looking for that data. If i go back again to that config, the compute job has finished so it's all there!
I'd guess for sake of storage space we wouldn't want to autostart a job when the config changes.
Anyways, might be a separate issue but logging it here to start!
Ah, yes. That's a problem. Thanks for detailed examples and steps to re-create. I'll dig into it now.
Removing this logic and conditional rendering for job status appeared to be the culprit.
I've more or less reverted back to where we use plot SVGs based on the job status.
Resolves https://github.com/VEuPathDB/web-eda/issues/1559