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

datawire-envoy-1.31.yaml: Add openssf-options #32254

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

justinvreeland
Copy link
Member

No description provided.

@justinvreeland justinvreeland added automated pr openssf-compiler-options Track adding openssf-compiler-options labels Oct 29, 2024
@justinvreeland justinvreeland self-assigned this Oct 29, 2024
@xnox xnox added the approved-to-run A repo member has approved this external contribution label Nov 12, 2024
Copy link
Contributor

octo-sts bot commented Nov 12, 2024

Gen AI suggestions to solve the build error:

Based on the error message, the issue appears to be related to a checksum mismatch when Bazel is trying to download a dependency (com_googlesource_googleurl). Here are some steps to debug and fix the issue:

  1. The specific error shows a checksum mismatch:
Checksum was fc694942e8a7491dcc1dde1bddf48a31370a1f46fef862bc17acf07c34dc6325 
but wanted 59f14d4fb373083b9dc8d389f16bbb817b5f936d1d436aa67e16eb6936028a51
  1. This typically happens when:
  • The dependency's content has changed at the source
  • The hash in the Bazel configuration is outdated
  • The source URL is no longer available or has been modified

To fix this, you can try:

  1. Update the WORKSPACE file:
  • Look for the com_googlesource_googleurl repository definition
  • Update the SHA256 hash to match the new value
  • You might find this in either the main WORKSPACE file or in bazel/repositories.bzl
  1. Alternative approach - use --override_repository:
    Add this to your build command:
bazel build --override_repository=com_googlesource_googleurl=/path/to/local/copy envoy
  1. If building interactively, you can:
cd envoy
bazel clean --expunge  # Clear bazel cache
# Then retry the build with verbose output
bazel build -s --verbose_failures envoy

Given this is a Datawire fork of Envoy, you might want to:

  1. Check the Datawire repository for any recent changes to the dependency definitions
  2. Verify if the specific version (1.31.2) has any known build issues
  3. Consider updating the dependency hash in your repository configuration

The most direct fix would be to update the checksum in the build configuration to match the new value: fc694942e8a7491dcc1dde1bddf48a31370a1f46fef862bc17acf07c34dc6325

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved-to-run A repo member has approved this external contribution automated pr openssf-compiler-options Track adding openssf-compiler-options
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants