Skip to content
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

Realtime connection does not use fallback hosts in custom environment #2009

Open
lawrence-forooghian opened this issue Jan 9, 2025 · 0 comments
Labels
bug Something isn't working. It's clear that this does need to be fixed.

Comments

@lawrence-forooghian
Copy link
Collaborator

lawrence-forooghian commented Jan 9, 2025

For example, change the test test__091__Connection__Host_Fallback__every_connection_is_first_attempted_to_the_primary_host_realtime_ably_io so that it uses the sandbox environment (i.e. write options.environment = "sandbox"). You will see that the client does not attempt to connect to any fallback hosts. I think that, per RTN17c and RSC15g2, it should do.

Fallback hosts do seem to be working correctly for custom environments for REST connections; see the tests for RSC15g2.

(Note that I'm referring to the pre-1ef8d1a version of the spec, which deprecated the spec points I'm referring to and introduced the endpoint client option, which we haven't implemented yet.)

┆Issue is synchronized with this Jira Task by Unito

@lawrence-forooghian lawrence-forooghian added the bug Something isn't working. It's clear that this does need to be fixed. label Jan 9, 2025
lawrence-forooghian added a commit that referenced this issue Jan 9, 2025
I considered switching the test to instead use sandbox, but discovered
that fallback hosts for realtime connections with custom environments
are not working; see #2009.

Resolves #2008.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working. It's clear that this does need to be fixed.
Development

No branches or pull requests

1 participant