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

grpc/1.67.0 package update #30328

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

octo-sts[bot]
Copy link
Contributor

@octo-sts octo-sts bot commented Oct 8, 2024

@octo-sts octo-sts bot added request-version-update request for a newer version of a package automated pr labels Oct 8, 2024
Copy link
Contributor Author

octo-sts bot commented Oct 8, 2024

Open AI suggestions to solve the build error:

The log file at `/tmp/script2608912943` does not contain any error messages. If you have another file or need further assistance, please provide more details.

@octo-sts octo-sts bot added the bincapz/blocking Bincapz (aka malcontent) scan results detected CRITICALs on the packages. label Oct 8, 2024
Copy link
Contributor Author

octo-sts bot commented Oct 8, 2024

malcontent detected files with a risk score equal or higher than 'CRITICAL': Click to expand/collapse

/tmp/malcontent2120662378/packages/x86_64/py3-grpcio-1.67.0-r0.apk/usr/lib/python3.12/site-packages/grpc/_cython/cygrpc.cpython-312-x86_64-linux-gnu.so [🚨 CRITICAL]

RISK KEY DESCRIPTION EVIDENCE
CRITICAL 3P/JPCERT/plugx/config detect PlugX in memory, by JPCERT/CC Incident Response Group $v2b
$v2f
$v2g
$v2h
�3333
�3333
�DDDD
�3333
�DDDD
�3333

@egibs egibs added the malcontent/reviewed The malcontent findings in this PR have been manually reviewed by security. label Oct 8, 2024
Copy link
Contributor Author

octo-sts bot commented Oct 9, 2024

Open AI suggestions to solve the build error:

The error message indicates a failure in building the package due to an issue in running the package falco pipeline, resulting in an exit status 2. Here are some steps you can take to resolve the issue:

1. **Check Logs**: Look into the logs located in the workspace directory `/temp/melange-workspace-880838871` and the guest directory `/temp/melange-guest-2213661612` for more detailed information about the error.

2. **Dependencies**: Ensure that all necessary dependencies for the build are installed and correctly configured.

3. **Build Scripts and Configurations**: Verify that the build scripts and configurations are correct and up-to-date.

4. **Increased Verbosity**: Re-run the build process with increased verbosity to gain more insights into what might be causing the failure.

Copy link
Contributor Author

octo-sts bot commented Oct 9, 2024

Open AI suggestions to solve the build error:

The error message in the log is: 

"WARN /home/build/src/php/ext/grpc/call_credentials.c:168:3: error: implicit declaration of function 'gpr_log'; did you mean 'gpr_now'? [-Wimplicit-function-declaration]"

To fix this error:
1. Ensure the header file declaring `gpr_log` is included in `call_credentials.c`.
2. Check if `gpr_log` is correctly defined in the gRPC library.
3. If `gpr_log` is deprecated, replace it with `gpr_now` or the appropriate function.
4. Rebuild the project after making changes.

wolfi-bot and others added 2 commits October 10, 2024 01:20
…-dev. The grpc package update has failing ABI compat checks

Signed-off-by: Mark McCormick <[email protected]>
@xnox xnox force-pushed the wolfictl-1953b58c-46dd-4515-8d95-2058c67fc264 branch from 5067c7f to bedafe7 Compare October 10, 2024 00:21
Copy link
Contributor Author

octo-sts bot commented Oct 10, 2024

Open AI suggestions to solve the build error:

The error log indicates a problem with the `plugin_get_metadata` function in the `call_credentials.c` file, specifically an implicit declaration of the `gpr_log` function. It suggests that you might have meant `gpr_now`. The build process failed with an exit code 2. Here are some steps to resolve the issue:

1. Ensure that the correct header file for `gpr_log` is included in your source code.
2. Verify that the gRPC library is properly installed and accessible.
3. Clean your build environment and attempt to rebuild the project.
4. Check for any updates or patches for the gRPC library that might address this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automated pr bincapz/blocking Bincapz (aka malcontent) scan results detected CRITICALs on the packages. malcontent/reviewed The malcontent findings in this PR have been manually reviewed by security. request-version-update request for a newer version of a package
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants