400 Errors From Girder Notification Stream

[wphicks]

When I create a Girder Session with enableSSE set to true, I'm seeing a bunch of 400s for "GET /api/v1/notification?since=2018-08-17T20:20:53.691Z HTTP/1.1" and similar calls. All other axios requests against my Girder instance seem to be going through fine. This is Girder 2.5.0 with Resonant:Geo 1.12. I see the errors when accessing my app from both Firefox and Chromium on Ubuntu. The notification stream for the Girder instance seems to be working properly from the usual Girder web interface.

[jbeezley]

I'm guessing you are using a version Girder that includes girder/girder#2768 but not girder/girder#2769. If you were on the Girder 2.5 release, you would be getting a 404. Could you verify the Girder commit you are using?

[wphicks]

I'm not sure that's it. I'm on 79fbbb51e69ac22a7ce0168a9539c3ba66955e34, which looks like it's before either of those MRs, unless I'm mistaken? It's definitely a 400, as you can see from the logs here:

girder_1     | 172.20.0.1 - - [20/Aug/2018:12:50:23] "GET /api/v1/notification?since=2018-08-20T12:50:00.664Z HTTP/1.1" 400 61 "http://localhost:8081/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/68.0.3440.106 Chrome/68.0.3440.106 Safari/537.36"

It sounds like this almost certainly an issue with my version of Girder one way or another, though. If folks aren't seeing this on the latest master, feel free to close it out. We can bump our Girder version for our next release and not worry about it for this one.

[jbeezley]

Thanks, I'll give that version a try and see if I can improve the fallback detection.