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

mzcompose,feature-benchmark: Ensure --dev option is in effect when ne… #10527

Merged

Conversation

philip-stoev
Copy link
Contributor

…eded

In order to avoid user frustration, the feature benchmark should run even
if the environment has not been primed with bin/pyactivate --dev in advance.

  • Enable --dev if ./mzcompose from the feature directory is called
  • Enable --dev if bin/mzcompose --dev is used
  • Remove the documentation step where bin/pyactivate --dev was mentioned

Motivation

  • This PR fixes a previously unreported bug.
    The feature benchmark would only run on environments that were primed with bin/pyactivate --dev in advance. If that step was not executed, a cryptic error would occur which would lead to user frustration.

…eded

In order to avoid user frustration, the feature benchmark should run even
if the environment has not been primed with bin/pyactivate --dev in advance.

* Enable --dev if ./mzcompose from the feature directory is called
* Enable --dev if bin/mzcompose --dev is used
* Remove the documentation step where bin/pyactivate --dev was mentioned
Copy link
Member

@benesch benesch left a comment

Choose a reason for hiding this comment

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

LGTM, though heads up that I will be entirely removing the split between dev and non-dev requirements as soon as #10054 is fixed!

@philip-stoev philip-stoev merged commit 6fa9b3d into MaterializeInc:main Feb 10, 2022
@philip-stoev philip-stoev deleted the feature-benchmark-ensure-dev branch February 10, 2022 10:51
benesch added a commit to benesch/materialize that referenced this pull request Feb 14, 2022
It turns out MaterializeInc#10527 broke use of the `--dev` option to `mzcompose` to
mean "build in dev mode rather than release mode". Revert that part of
the commit. Instead, teach `bin/mzcompose` to always install dev deps
when invoked from the root. We don't tell users about `bin/mzcompose`,
so they'll continue to get the reduced set of deps when running
mzcompose from a directory locally.
wangandi pushed a commit to wangandi/materialize that referenced this pull request Apr 11, 2022
It turns out MaterializeInc#10527 broke use of the `--dev` option to `mzcompose` to
mean "build in dev mode rather than release mode". Revert that part of
the commit. Instead, teach `bin/mzcompose` to always install dev deps
when invoked from the root. We don't tell users about `bin/mzcompose`,
so they'll continue to get the reduced set of deps when running
mzcompose from a directory locally.
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.

None yet

2 participants