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

fix: fill in the required args for Api::Impl #14554

Merged
merged 2 commits into from
Jan 10, 2021
Merged

fix: fill in the required args for Api::Impl #14554

merged 2 commits into from
Jan 10, 2021

Conversation

ynqa
Copy link
Contributor

@ynqa ynqa commented Jan 3, 2021

Commit Message: Add Random::RandomGenerator& as an argument which is required by Api::Impl.
Risk Level: Low

@repokitteh-read-only
Copy link

Hi @ynqa, welcome and thank you for your contribution.

We will try to review your Pull Request as quickly as possible.

In the meantime, please take a look at the contribution guidelines if you have not done so already.

🐱

Caused by: #14554 was opened by ynqa.

see: more, trace.

@ynqa ynqa changed the title fix: fill in the required args for Api::Impl. fix: fill in the required args for Api::Impl Jan 3, 2021
@rojkov
Copy link
Member

rojkov commented Jan 4, 2021

Thanks! Could you please amend the commit message to include a Signed-Off-By field? Otherwise the DCO check is bound to fail.

Also run ./tools/code_format/check_format.py fix to fix formatting errors.

Signed-off-by: Makoto Ito <un.pensiero.vano@gmail.com>
Envoy::Api::Impl api(platform_impl_.threadFactory(), stats_store, time_system,
platform_impl_.fileSystem());
platform_impl_.fileSystem(), rand);
Copy link
Contributor

Choose a reason for hiding this comment

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

cc @akonradi @lizan @htuch

I wonder if it would be possible to have a basic test the exercises this tool and catches compile breakages like this one.

Copy link
Contributor

Choose a reason for hiding this comment

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

The compilation breakage should have been caught by the existing build rule. Do we not try to build everything under //tools somewhere in CI?

Copy link
Member

Choose a reason for hiding this comment

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

We must not which seems broken. Can you add this somewhere here? https://github.com/envoyproxy/envoy/blob/master/ci/do_ci.sh

/wait

Copy link
Contributor

Choose a reason for hiding this comment

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

My understanding is that bazel test does not build binaries that are not required to run tests. In order to verify compilation of a binary, you need a test that depends on it.

Copy link
Member

Choose a reason for hiding this comment

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

bazel build //tools/... should suffice.

Copy link
Member

Choose a reason for hiding this comment

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

Yeah ^

Copy link
Contributor

@antoniovicente antoniovicente Jan 8, 2021

Choose a reason for hiding this comment

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

I think that the way to do this would be to change the following line in ci/build_setup.sh to also cover //tools/...
I can offer to send that as a separate change if we prefer just getting this build fix in and address the CI coverage issue separately.

[ -z "${ENVOY_BUILD_TARGET}" ] && export ENVOY_BUILD_TARGET=//source/exe:envoy-static //tools/...

Copy link
Contributor

Choose a reason for hiding this comment

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

There are other build breakages under //tools/... like:

ERROR: tools/testdata/protoxform/envoy/v2/BUILD:23:14: //tools/testdata/protoxform/envoy/v2:freeze_protos: missing input file '//tools/testdata/protoxform/envoy/v2:active_non_terminal.proto'
ERROR: tools/testdata/protoxform/envoy/v2/BUILD:23:14 3 input file(s) do not exist

I'm looking into them.

Signed-off-by: Makoto Ito <un.pensiero.vano@gmail.com>
@ynqa ynqa marked this pull request as ready for review January 6, 2021 17:42
Envoy::Api::Impl api(platform_impl_.threadFactory(), stats_store, time_system,
platform_impl_.fileSystem());
platform_impl_.fileSystem(), rand);
Copy link
Contributor

@antoniovicente antoniovicente Jan 8, 2021

Choose a reason for hiding this comment

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

I think that the way to do this would be to change the following line in ci/build_setup.sh to also cover //tools/...
I can offer to send that as a separate change if we prefer just getting this build fix in and address the CI coverage issue separately.

[ -z "${ENVOY_BUILD_TARGET}" ] && export ENVOY_BUILD_TARGET=//source/exe:envoy-static //tools/...

antoniovicente added a commit to antoniovicente/envoy that referenced this pull request Jan 9, 2021
Signed-off-by: Antonio Vicente <avd@google.com>
Copy link
Member

@mattklein123 mattklein123 left a comment

Choose a reason for hiding this comment

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

As long as @antoniovicente (or someone) is working on testing tools in CI I'm fine to merge this as is. Thank you!

@mattklein123 mattklein123 merged commit abf8cd8 into envoyproxy:master Jan 10, 2021
@antoniovicente
Copy link
Contributor

As long as @antoniovicente (or someone) is working on testing tools in CI I'm fine to merge this as is. Thank you!

Yes, I'm looking into it in #14615

Thanks for the fix!

mpuncel added a commit to mpuncel/envoy that referenced this pull request Jan 12, 2021
* master:
  http: support creating filters with match tree (envoyproxy#14430)
  [tls] Expose ServerContextImpl::selectTlsContext (envoyproxy#14592)
  docs: update ext_proc docs to reflect implementation status (envoyproxy#14636)
  filter manager: drop assert (envoyproxy#14633)
  kick off v1.18.0 (envoyproxy#14637)
  1.17.0 release (envoyproxy#14624)
  Implement request header processing in ext_proc (envoyproxy#14385)
  http: expose encoded headers/trailers via callbacks (envoyproxy#14544)
  [fuzz] fix minor fuzz bugs (envoyproxy#14593)
  rate limit: add computed descriptors (envoyproxy#14448)
  tools: fill in the required args for Api::Impl (envoyproxy#14554)
  Bump envoy-build to current images (envoyproxy#14608)

Signed-off-by: Michael Puncel <mpuncel@squareup.com>
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.

6 participants