damondouglas opened a new issue, #33333:
URL: https://github.com/apache/beam/issues/33333

   ### What happened?
   
   # Situation
   
   Release Nightly Snapshot failing from timeouts with HTTP requests to 
https://repository.apache.org.
   
   # Background
   
   Some details of the HTTP request failures are shown in the following.
   
   <details>
   
   <summary>Could not resolve all files for configuration 
':sdks:java:extensions:sql:jdbc:shadowTestRuntimeClasspath'</summary>
   
   ```
   Build file 
'/runner/_work/beam/beam/sdks/java/extensions/sql/jdbc/build.gradle' line: 70
   Could not resolve all files for configuration 
':sdks:java:extensions:sql:jdbc:shadowTestRuntimeClasspath'.
   > Could not resolve io.confluent:kafka-avro-serializer:7.6.0.
     Required by:
         project :sdks:java:extensions:sql:jdbc > project 
:sdks:java:extensions:sql > project :sdks:java:io:kafka
     > Could not resolve io.confluent:kafka-avro-serializer:7.6.0.
       > Could not get resource 
'https://repository.apache.org/snapshots/io/confluent/kafka-avro-serializer/7.6.0/kafka-avro-serializer-7.6.0.pom'.
         > Could not GET 
'https://repository.apache.org/snapshots/io/confluent/kafka-avro-serializer/7.6.0/kafka-avro-serializer-7.6.0.pom'.
           > Connect to repository.apache.org:443 
[repository.apache.org/65.109.119.155] failed: connect timed out
             > connect timed out
   > Could not resolve io.confluent:kafka-schema-registry-client:7.6.0.
     Required by:
         project :sdks:java:extensions:sql:jdbc > project 
:sdks:java:extensions:sql > project :sdks:java:io:kafka
     > Could not resolve io.confluent:kafka-schema-registry-client:7.6.0.
       > Could not get resource 
'https://repository.apache.org/snapshots/io/confluent/kafka-schema-registry-client/7.6.0/kafka-schema-registry-client-7.6.0.pom'.
         > Could not GET 
'https://repository.apache.org/snapshots/io/confluent/kafka-schema-registry-client/7.6.0/kafka-schema-registry-client-7.6.0.pom'.
           > Connect to repository.apache.org:443 
[repository.apache.org/65.109.119.155] failed: connect timed out
             > connect timed out
   > Could not resolve net.minidev:json-smart:[1.3.1,2.3].
     Required by:
         project :sdks:java:extensions:sql:jdbc > project 
:sdks:java:extensions:sql > project :sdks:java:io:parquet > 
org.apache.hadoop:hadoop-common:2.10.2 > org.apache.hadoop:hadoop-auth:2.10.2 > 
com.nimbusds:nimbus-jose-jwt:7.9
     > Skipped due to earlier error
     > Failed to list versions for net.minidev:json-smart.
       > Unable to load Maven meta-data from 
https://repository.apache.org/content/repositories/releases/net/minidev/json-smart/maven-metadata.xml.
         > Could not GET 
'https://repository.apache.org/content/repositories/releases/net/minidev/json-smart/maven-metadata.xml'.
           > Connect to repository.apache.org:443 
[repository.apache.org/65.109.119.155] failed: connect timed out
             > connect timed out
   ```
   
   </details>
   
   <details>
   <summary>Failed to publish publication 'mavenJava' to repository 
'apache.snapshots.https'</summary>
   
   ```
   Failed to publish publication 'mavenJava' to repository 
'apache.snapshots.https'
   > Could not GET 
'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-transform-service/2.62.0-SNAPSHOT/maven-metadata.xml'.
     > Connect to repository.apache.org:443 
[repository.apache.org/65.109.119.155] failed: connect timed out
       > connect timed out
   ```
   
   </details>
   
   Repeated failures are list in the following:
   - https://github.com/apache/beam/actions/runs/12235613311
   - https://github.com/apache/beam/actions/runs/12221763267
   - https://github.com/apache/beam/actions/runs/12212854096
   - https://github.com/apache/beam/actions/runs/12207225029
   - https://github.com/apache/beam/actions/runs/12198768313
   
   The last known successful run is 
https://github.com/apache/beam/actions/runs/12179715616 at 
d24d838bd838427a545592ad21d9623fb1272fb0. The first known failure run is 
https://github.com/apache/beam/actions/runs/12198768313 at 
d379968e7ee8a108b2f019702ffb4525f153e070 with commits listed in the following:
   
   - 68e3c0de9c570ea8e137e1c4f1a2296397ad855e
   - 2344fdc4cb8608fad8bb42d2ce5b2e910e6c8098
   - e509e703a504d74da778ce16541d3ee6f918a646
   - 7df49a520b5660aadfe8ee6edfa26076277cb072
   
   # Assessment
   
   There seems to be a global failure across Beam with these failing HTTP 
requests. Nor is there any commit involving a change in the Gradle 
configurations. Most likely there's a configuration change to the credentials 
of the GitHub repository.
   
   # Recommendation
   
   Assess whether there have been any recent https://repository.apache.org 
credential changes.
   
   
   ### Issue Priority
   
   Priority: 2 (default / most bugs should be filed as P2)
   
   ### Issue Components
   
   - [ ] Component: Python SDK
   - [ ] Component: Java SDK
   - [ ] Component: Go SDK
   - [ ] Component: Typescript SDK
   - [ ] Component: IO connector
   - [ ] Component: Beam YAML
   - [ ] Component: Beam examples
   - [ ] Component: Beam playground
   - [ ] Component: Beam katas
   - [ ] Component: Website
   - [ ] Component: Infrastructure
   - [ ] Component: Spark Runner
   - [ ] Component: Flink Runner
   - [ ] Component: Samza Runner
   - [ ] Component: Twister2 Runner
   - [ ] Component: Hazelcast Jet Runner
   - [ ] Component: Google Cloud Dataflow Runner


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to