Skip to content

Conversation

@willpote
Copy link
Contributor

@willpote willpote commented Nov 14, 2025

Support FallbackLayer in boundless SDK and in broker. This allows configuring multiple RPCs and trying all of them.

Enables it for one of the two single instance provers we operate, so we can monitor and compare perf to the other one

@github-actions github-actions bot changed the title Add support for FallbackLayer to boundless sdk BM-1908: Add support for FallbackLayer to boundless sdk Nov 14, 2025
@willpote willpote marked this pull request as ready for review November 18, 2025 00:36
Comment on lines +141 to +142
let active_count =
std::num::NonZeroUsize::new(transports.len()).unwrap_or(std::num::NonZeroUsize::MIN);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we should just ignore the case of no transports being selected? This feels like we would be opening up to issues where there are 0 transports, but the fallback layer assumes there is one? Given that we are only calling this if there are values, should this not just pass back an error in this case?

Comment on lines +124 to +132
// Add the primary RPC URL if set
if let Some(ref rpc_url) = self.rpc_url {
all_urls.push(rpc_url.clone());
}

// Add any additional URLs from rpc_urls
all_urls.extend(self.rpc_urls.clone());

Ok(all_urls)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like erroring if all_urls is empty here might be helpful with a message that indicates you need to set either or both variables?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants