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
refactor: Remove client.Reset usage #1762
Conversation
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.
LGTM
Signed-off-by: Will Beason <willbeason@google.com>
Codecov Report
@@ Coverage Diff @@
## master #1762 +/- ##
==========================================
- Coverage 52.35% 52.26% -0.10%
==========================================
Files 98 98
Lines 8781 8781
==========================================
- Hits 4597 4589 -8
- Misses 3824 3830 +6
- Partials 360 362 +2
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
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.
LGTM
Right now
client.Reset
complicates the ability to shard template compilation and running as it means it's very easy to accidentally forget to completely reset state. We're going to be making a lot of changes relatively quickly tolocal.Driver
andclient.Client
, so we may miss things. We could try to maintain this behavior, but it'll be a lot of trouble (both to implement + test).Further, it means that we can't initialize modules as part of Client/Driver initialization since these are immediately deleted per the call to
client.Reset
after Client is instantiated.This PR removes calls to
client.Reset
. A PR inframeworks
will remove this function fromClient
's interface.We originally added
client.Reset
to prepare for the possibility of a remote driver inframeworks
. For now we don't have plans to complete that, so it seems safe to remove usage here. There are tests which made usage of this functionality - I've modified them so each case instantiates a new Client. This should have no effect on benchmarks as this setup does not happen within the call tob.Run()
.This does not change the preexisting issue of broken benchmarks.
Signed-off-by: Will Beason willbeason@google.com