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

zetasql/2024.11.1 package update #34096

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

Conversation

octo-sts[bot]
Copy link
Contributor

@octo-sts octo-sts bot commented Nov 13, 2024

Signed-off-by: wolfi-bot <121097084+wolfi-bot@users.noreply.github.com>
@octo-sts octo-sts bot added request-version-update request for a newer version of a package automated pr labels Nov 13, 2024
Copy link
Contributor Author

octo-sts bot commented Nov 13, 2024

Gen AI suggestions to solve the build error:

Based on the error output, there are a few issues to address:

  1. Primary Issue - Patch Failure:
    The patch is failing because it can't find the file zetasql/jdk/BUILD to patch. This could be because:
  • The file path in the patch file doesn't match the actual repository structure
  • The repository structure has changed since the patch was created

Suggestions to fix:

  1. Verify the correct path in the repository:
# When in interactive mode
ls -R | grep BUILD  # List all BUILD files
  1. Update the patch file paths to match the actual repository structure
  • You might need to modify multi-arch-for-linux.patch to use the correct paths
  • If the file has moved, update the path in the patch file
  1. Secondary Consideration - Build Resources:
    The package requests significant resources:
resources:
    cpu: 33
    memory: 100Gi

These are quite high but might be necessary for Bazel builds.

  1. Authentication Error Note:
    There's an error about Google authentication, but it doesn't appear to be affecting the build:
Error: rpc error: code = NotFound desc = federate identity...

This can be ignored for now as it's not blocking the build process.

Next steps:

  1. Examine the repository structure to confirm the correct paths for the BUILD files
  2. Update the patch file to match the actual file locations
  3. If needed, recreate the patch file against the current version of the repository

To recreate the patch if needed:

git diff > new-multi-arch-for-linux.patch

Focus on fixing the patch file paths first, as this is the immediate cause of the build failure.

@hbh7
Copy link
Member

hbh7 commented Nov 14, 2024

Important previous context here: #26865

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants