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

Add enable option for EVC, with default = false #626

Merged
merged 7 commits into from
Jul 29, 2021

Conversation

bouthilx
Copy link
Member

@bouthilx bouthilx commented Jul 23, 2021

[Fixes #547]

The EVC is a constant source of confusion for users. It should be
disabled by default with warning messages when different versions of
experiments are used. Users who wants using advanced features of the EVC
would still be able to use it by enabling it.

Making it false by default is a breaking change and may cause issues to
user currently using the EVC. Based on discussion with users there does
not seem to have much usage of the EVC so far so this breaking change
should be relatively harmless. Avoiding further confusion by making it
disabled by default is worth the breaking change.

@bouthilx bouthilx added the enhancement Improves a feature or non-functional aspects (e.g., optimization, prettify, technical debt) label Jul 23, 2021
@bouthilx bouthilx added this to the v0.1.16 milestone Jul 23, 2021
The tests for the different EVC options were all inter-dependent. This
commit makes them independent, all starting from the same DB state using
the same command. This makes it much easier to make modifications in
these tests without affecting all following tests.
The EVC is a constant source of confusion for users. It should be
disabled by default with warning messages when different versions of
experiments are used. Users who wants using advanced features of the EVC
would still be able to use it by enabling it.

Making it false by default is a breaking change and may cause issues to
user currently using the EVC. Based on discussion with users there does
not seem to have much usage of the EVC so far so this breaking change
should be relatively harmless. Avoiding further confusion by making it
disabled by default is worth the breaking change.
Why:

If the EVC is not enabled, the consumer should always ignore the code
changes. It would not make sense to raise an error between 2 trials
because user's script code changed while EVC is disabled.

How:

If EVC is disabled, force ignore_code_changes to True in Consumer.
@bouthilx bouthilx added this to Review in progress in Release v0.1.16 Jul 28, 2021
@bouthilx bouthilx merged commit 4d89c20 into Epistimio:develop Jul 29, 2021
Release v0.1.16 automation moved this from Review in progress to Done Jul 29, 2021
@bouthilx bouthilx deleted the feature/optional_evc branch July 29, 2021 16:23
@bouthilx bouthilx mentioned this pull request Aug 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improves a feature or non-functional aspects (e.g., optimization, prettify, technical debt)
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

Make it possible to enable/disable the EVC
1 participant