-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support websocket URLs #21
Conversation
tested in a notebook with today's gateway build. |
i also tested using R and I could connect to idr-next too |
Sorry @jburel , I pretty much overhauled the ServerInformation class again, would have to test again. So basically there are now two methods: The previous |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One minor comment, but based on testing ome/omero-insight#66 this works well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two minor comments that can easily be handled in a follow-up. They are more general guidelines that we could apply to all Java classes. Otherwise, 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like the final
-related issues I saw previously have been taken care of.
One thing outwith this PR to discuss: the addition of methods would suggest this be released as 5.6, for example, if someone has previously subclassed.
I'm not sure what that means with respect to merging the PR: Can't be merged until we plan to release a 5.6 version? |
I vote for getting this in, I've tested the merge build in a Docker container on mybinder.org and it's worked! |
I'd put it the other way around. I don't see anything blocking the release of this PR, but we should discuss the version number. |
Noticed an issue on Linux when no preferences are set:
|
Thanks, good point, I never tested this case. Rather refers to ome/omero-insight#66 I think. |
Sorry, had to add one more commit to bump the blitz version to 5.5.4 so that ome/omero-blitz#66 is included. On that occassion also rebased to latest master branch. |
this.uri = new URI(null,null, hostname, | ||
port, null, null, null); | ||
} | ||
} catch (URISyntaxException e) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you want to log the error?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thought about it. But at that point I don't have any reference to the Gateway, which has the Logger.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok understood
Websocket connection works in principle, but at the moment you'll get a "Failed to get inet address...." warning when the gateway tries to get the IP of the server. This PR just fixes the issue.
Test with something like this, e.g. against idr next ( this would implicitly also test ome/omero-blitz#66 ):
Then also test the 'normal' login via hostname only, and hostname + port.