NORA visualisation failing on 24.1

[hexylena]

Describe the bug

upon opening Nora I am greeted with Load function 'load' not found. and the message window.bundleEntries.chartUtilities is undefined in console.

Galaxy Version and/or server at which you observed the bug
Galaxy Version: 24.1.4.dev0
Commit: it's usegalaxy.org today

Browser and Operating System
Operating System: linux
Browser: Firefox

To Reproduce
Steps to reproduce the behavior:

1. Go to https://usegalaxy.org/u/helena-rasche/h/unnamed-history-2
2. import
3. open nora
4. it doesn't show a dataset selector, nor does it show nora's interface (unlike Nora Visualization could not load datasets #11468) it just immediately errors

Expected behavior

it should open my nii1 image that i found in the galaxy test cases (I'm trying to work on #18895)

[hexylena]

@dannon you're the visualisation person so, pinging you in case you have some ideas why this isn't working currently on .org/other servers.

[dannon]

'load not found' means the js 404'd usually due to the build failing when it was last deployed; generally due to system node/dependency issues, and then it gets stuck that way. We've been working around these using a new approach to pre-built viz. I'll check on nora.

[hexylena]

Ah interesting. Thanks @dannon I appreciate it

[guerler]

I can reproduce this locally for drawrna and nvd3 too.

[dannon]

@guerler Those are likely a different issue? I tracked down Nora's problem and it actually happened a long while back; I just didn't get around to pushing an update. It's already a viz we prebuild -- one of the first we did this for actually. I'll push that up after calls.

[guerler]

@dannon sounds good, can you also take a look at drawrna. Might be the last one we'd need to move to the script endpoint.

[dannon]

@guerler Sure, I can do that

[guerler]

I am seeing this for all nvd3 visualizations locally too, fyi. My assumption is that it works on deployed instances because it was build quite awhile ago but would not be able to rebuild again on new instances.

[dannon]

@guerler That's exactly right -- a failed rebuild doesn't overwrite the old successful (already staged) artifacts since the staging process doesn't run. I forgot about this over the holidays but I can push up my tweaks shortly.

[jdavcs]

Bumping to 25.0.