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

Jump to bottom

Add options to control number of Storage API connections when using multiplexing #31721

Merged

ahmedabu98 merged 10 commits into apache:master from ahmedabu98:set_num_connections

Jul 12, 2024

Merged

Add options to control number of Storage API connections when using multiplexing #31721

add details

Annotations

7 warnings

Unhandled error in Gradle post-action - job will continue: Error: Cache upload failed because file read failed with EBADF: bad file descriptor, read

Failed to save cache entry with path '/home/runner/.gradle/caches,/home/runner/.gradle/notifications,/home/runner/.gradle/.gradle-build-action,zstd-without-long,1.0' and key: v8-gradle|Linux|precommit whitespace-beam_PreCommit_Whitespace[103967d2b7c0b52ee6c4bd7584ad78e0]-50a3403a4742e1c9e264f57f4411969daeff4642: Error: Cache service responded with 429 during upload chunk.

Unhandled error in Gradle post-action - job will continue: Error: Cache upload failed because file read failed with EBADF: bad file descriptor, read

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-python@v4, actions/setup-java@v3, gradle/gradle-build-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add options to control number of Storage API connections when using multiplexing #31721

Add options to control number of Storage API connections when using multiplexing #31721

Annotations

This job succeeded

Re-running jobs...