-
Notifications
You must be signed in to change notification settings - Fork 12
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
[Session, Test] Session rollover test #332
Conversation
Co-authored-by: Daniel Olshansky <[email protected]>
Co-authored-by: Daniel Olshansky <[email protected]>
Co-authored-by: Daniel Olshansky <[email protected]>
Co-authored-by: Daniel Olshansky <[email protected]>
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.
A couple minor NITS but shold be g2g right after.
@red-0ne Remember to update the base branch to main assuming you'll merge the other one in first. Please also trigger e2e tests after.
pkg/relayer/proxy/proxy_test.go
Outdated
"server1": { | ||
ProxyName: "server1", | ||
ProxyName: defaultServer, |
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.
This is an ultra NIT, but something I'm asking for just because I also always get confused between proxy/server/etc...
Do the key and proxyName
need to be the same or can they be different?
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.
You are right, it's confusing.
The key and ProxyName
have to be the same, as the config parser maps the proxy servers using their ProxyName
as keys.
I was uncomfortable having a variable as a key but afterthought, I believe it will add more clarity. Let's having as
defaultProxyServer: {
ProxyName: defaultProxyServer,
...
}
The CI will now also run the e2e tests on devnet, which increases the time it takes to complete all CI checks. If you just created a pull request, you might need to push another commit to produce a container image DevNet can utilize to spin up infrastructure. You can use |
Co-authored-by: Daniel Olshansky <[email protected]>
Summary
AI Summary
Summary generated by Reviewpad on 26 Jan 24 05:42 UTC
This pull request includes changes to the
relayerproxy.go
file in thetestproxy
package. It involves the following changes:The function
WithRelayerProxyDependencies
has been renamed toWithRelayerProxyDependenciesForBlockHeight
. It now takes an additional parameterblockHeight
, which represents the block height returned by the block client'sLastNBlock
method.A new function
WithSuccessiveSessions
has been introduced. This function creates sessions with session numbers ranging from 0 tosessionsCount-1
and adds them to the session map. These sessions are configured with the same service ID and application provided.There is a TODO_TECHDEBT comment pertaining to suggested changes for the
GetRelayResponseError
function.Issue
Type of change
Select one or more:
Testing
make go_develop_and_test
make test_e2e
devnet-test-e2e
label to the PR. This is VERY expensive, only do it after all the reviews are complete.Sanity Checklist