Skip to content

Update module github.com/aws/aws-sdk-go-v2/service/s3 to v1.97.3 [SECURITY] - autoclosed#4230

Closed
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/go-github.com-aws-aws-sdk-go-v2-service-s3-vulnerability
Closed

Update module github.com/aws/aws-sdk-go-v2/service/s3 to v1.97.3 [SECURITY] - autoclosed#4230
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/go-github.com-aws-aws-sdk-go-v2-service-s3-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Apr 23, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
github.com/aws/aws-sdk-go-v2/service/s3 v1.95.1v1.97.3 age confidence

Denial of Service due to Panic in AWS SDK for Go v2 SDK EventStream Decoder

GHSA-xmrv-pmrh-hhx2

More information

Details

CVSSv3.1 Rating: [Medium]
CVSSv3.1 Score: [5.9]
CVSSv3.1 Vector String: [CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H]

Summary and Impact

An issue exists in the the EventStream header decoder in AWS SDK for Go v2 in versions predating 2026-03-23. An actor can send a malformed EventStream response frame containing a crafted header value type byte outside the valid range, which can cause the host process to terminate.

Impacted versions: < 2026-03-23

Patches

This issue has been addressed in versions 2026-03-23 and above. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.

Workarounds

Not Applicable

References

If you have any questions or comments about this advisory, we ask that you contact [AWS/Amazon] Security via our vulnerability reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue.

Severity

  • CVSS Score: 5.9 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

aws/aws-sdk-go-v2 (github.com/aws/aws-sdk-go-v2/service/s3)

v1.97.3

General Highlights

  • Dependency Update: Updated to the latest SDK module versions

Module Highlights

  • github.com/aws/aws-sdk-go-v2: v1.41.5
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/accessanalyzer: v1.45.12
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/account: v1.30.5
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/acm: v1.37.23
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/acmpca: v1.46.12
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/aiops: v1.6.21
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/amp: v1.42.9
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/amplify: v1.38.14
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/amplifybackend: v1.32.20
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/amplifyuibuilder: v1.28.20
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/apigateway: v1.39.1
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/apigatewaymanagementapi: v1.29.14
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/apigatewayv2: v1.34.1
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/appconfig: v1.43.13
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/appconfigdata: v1.23.22
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/appfabric: v1.16.21
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/appflow: v1.51.12
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/appintegrations: v1.37.7
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/applicationautoscaling: v1.41.14
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/applicationcostprofiler: v1.27.12
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/applicationdiscoveryservice: v1.35.13
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/applicationinsights: v1.34.20
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/applicationsignals: v1.19.1
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/appmesh: v1.35.12
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/apprunner: v1.39.14
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/appstream: v1.54.4
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/appsync: v1.53.5
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/arcregionswitch: v1.6.3
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/arczonalshift: v1.22.23
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/artifact: v1.15.5
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/athena: v1.57.4
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/auditmanager: v1.46.12
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/autoscaling: v1.64.4
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/autoscalingplans: v1.30.14
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/b2bi: v1.0.0-preview.100
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/backup: v1.54.11
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/backupgateway: v1.26.3
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/backupsearch: v1.6.23
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/batch: v1.63.2
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/bcmdashboards: v1.1.4
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/bcmdataexports: v1.14.0
    • Feature: With this release we are providing an option to accounts to have their export delivered to an S3 bucket that is not owned by the account.
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/bcmpricingcalculator: v1.10.9
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/bcmrecommendedactions: v1.1.5
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/bedrock: v1.57.1
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/bedrockagent: v1.52.7
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/bedrockagentcore: v1.15.2
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/bedrockagentcorecontrol: v1.25.1
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/bedrockagentruntime: v1.51.8
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/bedrockdataautomation: v1.13.5
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/bedrockdataautomationruntime: v1.10.4
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/bedrockruntime: v1.50.4
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/billing: v1.10.4
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/billingconductor: v1.28.5
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/braket: v1.39.8
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/budgets: v1.43.4
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/chatbot: v1.14.21
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/chime: v1.41.12
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/chimesdkidentity: v1.27.20
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/chimesdkmediapipelines: v1.26.21
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/chimesdkmeetings: v1.33.15
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/chimesdkmessaging: v1.32.17
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/chimesdkvoice: v1.28.13
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/cleanrooms: v1.42.4
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/cleanroomsml: v1.22.5
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/cloud9: v1.33.20
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/cloudcontrol: v1.29.13
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/clouddirectory: v1.30.12
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/cloudformation: v1.71.9
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/cloudfront: v1.60.4
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/cloudfrontkeyvaluestore: v1.12.24
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/cloudhsm: v1.29.21
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/cloudhsmv2: v1.34.21
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/cloudsearch: v1.32.12
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/cloudsearchdomain: v1.28.20
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/cloudtrail: v1.55.9
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/cloudtraildata: v1.17.13
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/cloudwatch: v1.55.3
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/cloudwatchevents: v1.32.23
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/cloudwatchlogs: v1.65.0
    • Feature: This release adds parameter support to saved queries in CloudWatch Logs Insights. Define reusable query templates with named placeholders, invoke them using start query. Available in Console, CLI and SDK
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/codeartifact: v1.38.21
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/codebuild: v1.68.13
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/codecatalyst: v1.21.12
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/codecommit: v1.33.12
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/codeconnections: v1.10.20
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/codedeploy: v1.35.13
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/codeguruprofiler: v1.29.20
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/codegurureviewer: v1.34.20
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/codegurusecurity: v1.16.24
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/codepipeline: v1.46.21
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/codestarconnections: v1.35.13
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/codestarnotifications: v1.31.21
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/cognitoidentity: v1.33.22
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/cognitoidentityprovider: v1.59.3
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/cognitosync: v1.29.12
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/comprehend: v1.40.21
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/comprehendmedical: v1.31.21
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/computeoptimizer: v1.49.8
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/computeoptimizerautomation: v1.0.8
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/configservice: v1.62.1
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/connect: v1.166.1
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/connectcampaigns: v1.20.20
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/connectcampaignsv2: v1.11.4
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/connectcases: v1.39.1
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/connectcontactlens: v1.33.13
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/connecthealth: v1.0.3
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/connectparticipant: v1.36.7
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/controlcatalog: v1.14.9
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/controltower: v1.28.9
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/costandusagereportservice: v1.34.13
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/costexplorer: v1.63.6
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/costoptimizationhub: v1.22.8
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/customerprofiles: v1.57.2
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/databasemigrationservice: v1.61.10
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/databrew: v1.39.14
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/dataexchange: v1.40.14
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/datapipeline: v1.30.20
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/datasync: v1.58.2
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/datazone: v1.54.2
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/dax: v1.29.16
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/deadline: v1.26.2
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/detective: v1.38.13
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/devicefarm: v1.38.8
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/devopsguru: v1.40.12
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/directconnect: v1.38.15
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/directoryservice: v1.38.16
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/directoryservicedata: v1.7.21
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/dlm: v1.35.16
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/docdb: v1.48.13
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/docdbelastic: v1.20.13
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/drs: v1.36.13
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/dsql: v1.12.8
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/dynamodb: v1.57.1
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/dynamodbstreams: v1.32.14
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/ebs: v1.33.14
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/ec2: v1.296.1
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/ec2instanceconnect: v1.32.20
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/ecr: v1.56.2
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/ecrpublic: v1.38.13
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/ecs: v1.74.1
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/efs: v1.41.14
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/eks: v1.81.2
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/eksauth: v1.12.13
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/elasticache: v1.51.13
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/elasticbeanstalk: v1.34.2
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/elasticloadbalancing: v1.33.23
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/elasticloadbalancingv2: v1.54.10
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/elasticsearchservice: v1.39.2
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/elementalinference: v1.0.3
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/emr: v1.59.0
    • Feature: Add StepExecutionRoleArn to RunJobFlow API
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/emrcontainers: v1.40.17
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/emrserverless: v1.39.6
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/entityresolution: v1.26.5
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/eventbridge: v1.45.23
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/evs: v1.6.4
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/finspace: v1.33.21
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/finspacedata: v1.33.21
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/firehose: v1.42.13
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/fis: v1.37.20
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/fms: v1.44.22
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/forecast: v1.41.21
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/forecastquery: v1.29.21
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/frauddetector: v1.41.12
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/freetier: v1.13.14
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/fsx: v1.65.7
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/gamelift: v1.51.3
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/gameliftstreams: v1.11.1
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/geomaps: v1.9.4
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/geoplaces: v1.8.5
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/georoutes: v1.7.14
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/glacier: v1.32.6
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/globalaccelerator: v1.35.15
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/glue: v1.139.1
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/grafana: v1.33.4
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/greengrass: v1.32.21
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/greengrassv2: v1.42.12
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/groundstation: v1.40.4
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/guardduty: v1.74.2
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/health: v1.37.4
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/healthlake: v1.36.13
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/iam: v1.53.7
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/identitystore: v1.36.5
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/imagebuilder: v1.51.4
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/inspector: v1.30.20
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/inspector2: v1.47.4
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/inspectorscan: v1.13.5
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/internetmonitor: v1.26.14
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/invoicing: v1.9.8
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/iot: v1.72.5
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/iotdataplane: v1.32.21
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/iotdeviceadvisor: v1.36.21
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/iotevents: v1.33.13
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/ioteventsdata: v1.30.12
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/iotfleetwise: v1.31.20
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/iotjobsdataplane: v1.30.13
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/iotmanagedintegrations: v1.8.4
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/iotsecuretunneling: v1.33.21
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/iotsitewise: v1.52.19
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/iotthingsgraph: v1.30.21
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/iottwinmaker: v1.29.21
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/iotwireless: v1.54.9
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/ivs: v1.48.14
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/ivschat: v1.21.20
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/ivsrealtime: v1.33.1
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/kafka: v1.49.2
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/kafkaconnect: v1.30.4
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/kendra: v1.60.21
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/kendraranking: v1.15.25
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
  • github.com/aws/aws-sdk-go-v2/service/keyspaces: v1.25.4
    • Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the cli

Configuration

📅 Schedule: (in timezone Etc/UTC)

  • Branch creation
    • ""
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the security label Apr 23, 2026
@renovate renovate Bot enabled auto-merge (squash) April 23, 2026 23:27
@renovate

renovate Bot commented Apr 23, 2026

Copy link
Copy Markdown
Contributor Author

ℹ️ Artifact update notice

File name: e2e_cleanup/go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 10 additional dependencies were updated

Details:

Package Change
github.com/aws/aws-sdk-go-v2 v1.41.1 -> v1.41.5
github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream v1.7.4 -> v1.7.8
github.com/aws/aws-sdk-go-v2/internal/configsources v1.4.17 -> v1.4.21
github.com/aws/aws-sdk-go-v2/internal/endpoints/v2 v2.7.17 -> v2.7.21
github.com/aws/aws-sdk-go-v2/internal/v4a v1.4.17 -> v1.4.22
github.com/aws/aws-sdk-go-v2/service/internal/accept-encoding v1.13.4 -> v1.13.7
github.com/aws/aws-sdk-go-v2/service/internal/checksum v1.9.8 -> v1.9.13
github.com/aws/aws-sdk-go-v2/service/internal/presigned-url v1.13.17 -> v1.13.21
github.com/aws/aws-sdk-go-v2/service/internal/s3shared v1.19.17 -> v1.19.21
github.com/aws/smithy-go v1.24.0 -> v1.24.2

@renovate renovate Bot force-pushed the renovate/go-github.com-aws-aws-sdk-go-v2-service-s3-vulnerability branch 2 times, most recently from b99cffc to f7ca6cc Compare April 25, 2026 16:30
@codecov

codecov Bot commented Apr 25, 2026

Copy link
Copy Markdown

❌ 2 Tests Failed:

Tests completed Failed Passed Skipped
2226 2 2224 203
View the top 3 failed test(s) by shortest run time
github.com/PeerDB-io/peerdb/flow/e2e::TestApiMy
Stack Traces | 0.01s run time
=== RUN   TestApiMy
=== PAUSE TestApiMy
=== CONT  TestApiMy
--- FAIL: TestApiMy (0.01s)
2026/04/28 01:38:26 INFO Received AWS credentials from peer for connector: ci x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
2026/04/28 01:38:26 INFO Received AWS credentials from peer for connector: clickhouse x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
github.com/PeerDB-io/peerdb/flow/e2e::TestApiPg
Stack Traces | 0.01s run time
=== RUN   TestApiPg
=== PAUSE TestApiPg
=== CONT  TestApiPg
--- FAIL: TestApiPg (0.01s)
github.com/PeerDB-io/peerdb/flow/e2e::TestPeerFlowE2ETestSuitePG_CH
Stack Traces | 0.01s run time
=== RUN   TestPeerFlowE2ETestSuitePG_CH
=== PAUSE TestPeerFlowE2ETestSuitePG_CH
=== CONT  TestPeerFlowE2ETestSuitePG_CH
--- FAIL: TestPeerFlowE2ETestSuitePG_CH (0.01s)
github.com/PeerDB-io/peerdb/flow/e2e::TestPeerFlowE2ETestSuitePG_CH_Cluster
Stack Traces | 0.01s run time
=== RUN   TestPeerFlowE2ETestSuitePG_CH_Cluster
=== PAUSE TestPeerFlowE2ETestSuitePG_CH_Cluster
=== CONT  TestPeerFlowE2ETestSuitePG_CH_Cluster
--- FAIL: TestPeerFlowE2ETestSuitePG_CH_Cluster (0.01s)
github.com/PeerDB-io/peerdb/flow/e2e::TestApiPg/TestTableAdditionWithoutInitialLoad
Stack Traces | 6.19s run time
=== RUN   TestApiPg/TestTableAdditionWithoutInitialLoad
=== PAUSE TestApiPg/TestTableAdditionWithoutInitialLoad
=== CONT  TestApiPg/TestTableAdditionWithoutInitialLoad
2026/04/25 17:10:01 INFO Received AWS credentials from peer for connector: ci x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
2026/04/25 17:10:01 INFO Received AWS credentials from peer for connector: clickhouse x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
    api_test.go:2500: WaitFor wait for initial load to finish 2026-04-25 17:10:06.032274942 +0000 UTC m=+409.776118810
2026/04/25 17:10:06 INFO Executing and processing query x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,val FROM e2e_test_api_c6ihdlsb.\"original\" ORDER BY id"
2026/04/25 17:10:06 INFO Executing and processing query stream x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,val FROM e2e_test_api_c6ihdlsb.\"original\" ORDER BY id"
2026/04/25 17:10:06 INFO [pg_query_executor] declared cursor x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursorQuery="DECLARE peerdb_cursor_10673785967633837282 CURSOR FOR SELECT id,val FROM e2e_test_api_c6ihdlsb.\"original\" ORDER BY id" args=[]
2026/04/25 17:10:06 INFO [pg_query_executor] fetching rows start x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,val FROM e2e_test_api_c6ihdlsb.\"original\" ORDER BY id" channelLen=0
2026/04/25 17:10:06 INFO [pg_query_executor] fetching from cursor x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursor=peerdb_cursor_10673785967633837282
2026/04/25 17:10:06 INFO processed row stream x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursor=peerdb_cursor_10673785967633837282 records=1 bytes=9 channelLen=0
2026/04/25 17:10:06 INFO [pg_query_executor] fetched rows x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,val FROM e2e_test_api_c6ihdlsb.\"original\" ORDER BY id" rows=1 bytes=9 channelLen=0
2026/04/25 17:10:06 INFO [pg_query_executor] fetching from cursor x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursor=peerdb_cursor_10673785967633837282
2026/04/25 17:10:06 INFO processed row stream x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursor=peerdb_cursor_10673785967633837282 records=0 bytes=0 channelLen=0
2026/04/25 17:10:06 INFO [pg_query_executor] fetched rows x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,val FROM e2e_test_api_c6ihdlsb.\"original\" ORDER BY id" rows=0 bytes=0 channelLen=0
2026/04/25 17:10:06 INFO [pg_query_executor] committing transaction x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart
2026/04/25 17:10:06 INFO [pg_query_executor] committed transaction for query x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,val FROM e2e_test_api_c6ihdlsb.\"original\" ORDER BY id" rows=1 bytes=9 channelLen=0
    api_test.go:2510: WaitFor wait for pause for add table 2026-04-25 17:10:06.064087451 +0000 UTC m=+409.807931340
    api_test.go:2511: UNEXPECTED ERROR unable to establish connection with catalog: FATAL: terminating connection due to administrator command (SQLSTATE 57P01)
    api_test.go:49: begin tearing down postgres schema api_c6ihdlsb
--- FAIL: TestApiPg/TestTableAdditionWithoutInitialLoad (6.19s)
github.com/PeerDB-io/peerdb/flow/e2e::TestApiMy/TestEditTablesBeforeResync
Stack Traces | 18.1s run time
=== RUN   TestApiMy/TestEditTablesBeforeResync
=== PAUSE TestApiMy/TestEditTablesBeforeResync
=== CONT  TestApiMy/TestEditTablesBeforeResync
2026/04/28 01:36:43 INFO Received AWS credentials from peer for connector: ci x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
2026/04/28 01:36:43 INFO Received AWS credentials from peer for connector: clickhouse x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
2026/04/28 01:36:43 INFO fetched schema x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} table=e2e_test_mych_is4n73ks.test_update_pkey_chunking_initial_load_enabled
    api_test.go:1884: WaitFor wait for initial load to finish 2026-04-28 01:36:47.505613672 +0000 UTC m=+510.288938596
2026/04/28 01:36:47 INFO fetched schema x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} table=e2e_test_api_zwpcmhvc.original
    api_test.go:1895: WaitFor wait for pause for add table 2026-04-28 01:36:47.519766621 +0000 UTC m=+510.303091555
2026/04/28 01:36:47 INFO fetched schema x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} table=e2e_test_mych_is4n73ks.test_update_pkey_chunking_initial_load_enabled
    api_test.go:1896: UNEXPECTED ERROR unable to establish connection with catalog: FATAL: terminating connection due to administrator command (SQLSTATE 57P01)
    api_test.go:49: begin tearing down postgres schema api_zwpcmhvc
--- FAIL: TestApiMy/TestEditTablesBeforeResync (18.11s)
github.com/PeerDB-io/peerdb/flow/e2e::TestPeerFlowE2ETestSuitePG_CH_Cluster/Test_Binary_Format_Base64
Stack Traces | 140s run time
=== RUN   TestPeerFlowE2ETestSuitePG_CH_Cluster/Test_Binary_Format_Base64
=== PAUSE TestPeerFlowE2ETestSuitePG_CH_Cluster/Test_Binary_Format_Base64
=== CONT  TestPeerFlowE2ETestSuitePG_CH_Cluster/Test_Binary_Format_Base64
2026/04/25 16:56:24 INFO Received AWS credentials from peer for connector: ci x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
2026/04/25 16:56:25 INFO Received AWS credentials from peer for connector: clickhouse x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
2026/04/25 16:56:25 INFO Executing and processing query x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,\"key\" FROM e2e_test_pgchcl_jt0yb2xv.\"test_update_pkey_chunking_initial_load_enabled\" ORDER BY id"
2026/04/25 16:56:25 INFO Executing and processing query stream x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,\"key\" FROM e2e_test_pgchcl_jt0yb2xv.\"test_update_pkey_chunking_initial_load_enabled\" ORDER BY id"
2026/04/25 16:56:25 INFO [pg_query_executor] declared cursor x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursorQuery="DECLARE peerdb_cursor_11365496741520331361 CURSOR FOR SELECT id,\"key\" FROM e2e_test_pgchcl_jt0yb2xv.\"test_update_pkey_chunking_initial_load_enabled\" ORDER BY id" args=[]
2026/04/25 16:56:25 INFO [pg_query_executor] fetching rows start x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,\"key\" FROM e2e_test_pgchcl_jt0yb2xv.\"test_update_pkey_chunking_initial_load_enabled\" ORDER BY id" channelLen=0
2026/04/25 16:56:25 INFO [pg_query_executor] fetching from cursor x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursor=peerdb_cursor_11365496741520331361
2026/04/25 16:56:25 INFO processed row stream x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursor=peerdb_cursor_11365496741520331361 records=4 bytes=40 channelLen=3
2026/04/25 16:56:25 INFO [pg_query_executor] fetched rows x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,\"key\" FROM e2e_test_pgchcl_jt0yb2xv.\"test_update_pkey_chunking_initial_load_enabled\" ORDER BY id" rows=4 bytes=40 channelLen=3
2026/04/25 16:56:25 INFO [pg_query_executor] fetching from cursor x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursor=peerdb_cursor_11365496741520331361
2026/04/25 16:56:25 INFO processed row stream x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursor=peerdb_cursor_11365496741520331361 records=0 bytes=0 channelLen=0
2026/04/25 16:56:25 INFO [pg_query_executor] fetched rows x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,\"key\" FROM e2e_test_pgchcl_jt0yb2xv.\"test_update_pkey_chunking_initial_load_enabled\" ORDER BY id" rows=0 bytes=0 channelLen=0
2026/04/25 16:56:25 INFO [pg_query_executor] committing transaction x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart
2026/04/25 16:56:25 INFO [pg_query_executor] committed transaction for query x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,\"key\" FROM e2e_test_pgchcl_jt0yb2xv.\"test_update_pkey_chunking_initial_load_enabled\" ORDER BY id" rows=4 bytes=40 channelLen=0
    clickhouse_test.go:1064: WaitFor waiting for CDC count 2026-04-25 16:56:30.116751734 +0000 UTC m=+671.312588591
    clickhouse_test.go:1068: WaitFor waiting for CDC count 2026-04-25 16:56:30.125983137 +0000 UTC m=+671.321819994
    clickhouse.go:76: 
        	Error Trace:	.../flow/e2e/congen.go:44
        	            				.../flow/e2e/clickhouse.go:76
        	            				.../flow/e2e/clickhouse.go:154
        	            				.../flow/e2e/test_utils.go:240
        	            				.../flow/e2e/test_utils.go:852
        	            				.../flow/e2e/test_utils.go:237
        	            				.../flow/e2e/clickhouse_test.go:1068
        	            				.../flow/e2e/clickhouse_test.go:1091
        	Error:      	Received unexpected error:
        	            	unable to establish connection with catalog: FATAL: terminating connection due to administrator command (SQLSTATE 57P01)
        	Test:       	TestPeerFlowE2ETestSuitePG_CH_Cluster/Test_Binary_Format_Base64
    clickhouse.go:107: begin tearing down postgres schema pgchcl_9sey4d7u
2026/04/25 16:56:44 INFO Executing and processing query x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,val FROM e2e_test_api_qsj6l2dw.\"table1\" ORDER BY id"
2026/04/25 16:56:44 INFO Executing and processing query stream x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,val FROM e2e_test_api_qsj6l2dw.\"table1\" ORDER BY id"
2026/04/25 16:56:44 INFO [pg_query_executor] declared cursor x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursorQuery="DECLARE peerdb_cursor_6641370244377917162 CURSOR FOR SELECT id,val FROM e2e_test_api_qsj6l2dw.\"table1\" ORDER BY id" args=[]
2026/04/25 16:56:44 INFO [pg_query_executor] fetching rows start x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,val FROM e2e_test_api_qsj6l2dw.\"table1\" ORDER BY id" channelLen=0
2026/04/25 16:56:44 INFO [pg_query_executor] fetching from cursor x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursor=peerdb_cursor_6641370244377917162
2026/04/25 16:56:44 INFO processed row stream x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursor=peerdb_cursor_6641370244377917162 records=2 bytes=19 channelLen=1
2026/04/25 16:56:44 INFO [pg_query_executor] fetched rows x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,val FROM e2e_test_api_qsj6l2dw.\"table1\" ORDER BY id" rows=2 bytes=19 channelLen=1
2026/04/25 16:56:44 INFO [pg_query_executor] fetching from cursor x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursor=peerdb_cursor_6641370244377917162
2026/04/25 16:56:44 INFO processed row stream x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursor=peerdb_cursor_6641370244377917162 records=0 bytes=0 channelLen=0
2026/04/25 16:56:44 INFO [pg_query_executor] fetched rows x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,val FROM e2e_test_api_qsj6l2dw.\"table1\" ORDER BY id" rows=0 bytes=0 channelLen=0
2026/04/25 16:56:44 INFO [pg_query_executor] committing transaction x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart
2026/04/25 16:56:44 INFO [pg_query_executor] committed transaction for query x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,val FROM e2e_test_api_qsj6l2dw.\"table1\" ORDER BY id" rows=2 bytes=19 channelLen=0
    clickhouse.go:107: 
        	Error Trace:	.../flow/e2e/pg.go:147
        	            				.../flow/e2e/clickhouse.go:107
        	            				.../flow/e2eshared/e2eshared.go:38
        	            				.../hostedtoolcache/go/1.26.2.../src/testing/testing.go:1317
        	            				.../hostedtoolcache/go/1.26.2.../src/testing/testing.go:1667
        	            				.../hostedtoolcache/go/1.26.2.../src/testing/testing.go:2030
        	            				.../hostedtoolcache/go/1.26.2.../src/runtime/panic.go:694
        	            				.../hostedtoolcache/go/1.26.2.../src/testing/testing.go:1022
        	            				.../flow/e2e/congen.go:44
        	            				.../flow/e2e/clickhouse.go:76
        	            				.../flow/e2e/clickhouse.go:154
        	            				.../flow/e2e/test_utils.go:240
        	            				.../flow/e2e/test_utils.go:852
        	            				.../flow/e2e/test_utils.go:237
        	            				.../flow/e2e/clickhouse_test.go:1068
        	            				.../flow/e2e/clickhouse_test.go:1091
        	            				.../hostedtoolcache/go/1.26.2.../src/reflect/value.go:586
        	            				.../hostedtoolcache/go/1.26.2.../src/reflect/value.go:369
        	            				.../flow/e2eshared/e2eshared.go:40
        	Error:      	failed to teardown postgres schema
        	Test:       	TestPeerFlowE2ETestSuitePG_CH_Cluster/Test_Binary_Format_Base64
        	Messages:   	pgchcl_9sey4d7u: failed to drop replication slots: ERROR: replication slot "peerflow_slot_ch_binary_format_base64_pgchcl_9sey4d7u" is active for PID 37069 (SQLSTATE 55006)
--- FAIL: TestPeerFlowE2ETestSuitePG_CH_Cluster/Test_Binary_Format_Base64 (139.50s)
github.com/PeerDB-io/peerdb/flow/e2e::TestPeerFlowE2ETestSuitePG_CH/Test_Normalize_Metadata_With_Retry
Stack Traces | 181s run time
=== RUN   TestPeerFlowE2ETestSuitePG_CH/Test_Normalize_Metadata_With_Retry
=== PAUSE TestPeerFlowE2ETestSuitePG_CH/Test_Normalize_Metadata_With_Retry
=== CONT  TestPeerFlowE2ETestSuitePG_CH/Test_Normalize_Metadata_With_Retry
2026/04/25 16:53:17 INFO Received AWS credentials from peer for connector: ci x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
2026/04/25 16:53:17 INFO Received AWS credentials from peer for connector: clickhouse x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
    clickhouse_test.go:2208: WaitFor waiting on initial 2026-04-25 16:53:23.145650819 +0000 UTC m=+433.120215155
2026/04/25 16:53:23 INFO Executing and processing query x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,\"key\" FROM e2e_test_pgch_mknqb5ih.\"test_normalize_metadata_with_retry_1\" ORDER BY id"
2026/04/25 16:53:23 INFO Executing and processing query stream x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,\"key\" FROM e2e_test_pgch_mknqb5ih.\"test_normalize_metadata_with_retry_1\" ORDER BY id"
2026/04/25 16:53:23 INFO [pg_query_executor] declared cursor x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursorQuery="DECLARE peerdb_cursor_6408396196381215105 CURSOR FOR SELECT id,\"key\" FROM e2e_test_pgch_mknqb5ih.\"test_normalize_metadata_with_retry_1\" ORDER BY id" args=[]
2026/04/25 16:53:23 INFO [pg_query_executor] fetching rows start x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,\"key\" FROM e2e_test_pgch_mknqb5ih.\"test_normalize_metadata_with_retry_1\" ORDER BY id" channelLen=0
2026/04/25 16:53:23 INFO [pg_query_executor] fetching from cursor x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursor=peerdb_cursor_6408396196381215105
2026/04/25 16:53:23 INFO processed row stream x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursor=peerdb_cursor_6408396196381215105 records=4 bytes=29 channelLen=3
2026/04/25 16:53:23 INFO [pg_query_executor] fetched rows x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,\"key\" FROM e2e_test_pgch_mknqb5ih.\"test_normalize_metadata_with_retry_1\" ORDER BY id" rows=4 bytes=29 channelLen=3
2026/04/25 16:53:23 INFO [pg_query_executor] fetching from cursor x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursor=peerdb_cursor_6408396196381215105
2026/04/25 16:53:23 INFO processed row stream x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursor=peerdb_cursor_6408396196381215105 records=0 bytes=0 channelLen=0
2026/04/25 16:53:23 INFO [pg_query_executor] fetched rows x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,\"key\" FROM e2e_test_pgch_mknqb5ih.\"test_normalize_metadata_with_retry_1\" ORDER BY id" rows=0 bytes=0 channelLen=0
2026/04/25 16:53:23 INFO [pg_query_executor] committing transaction x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart
2026/04/25 16:53:23 INFO [pg_query_executor] committed transaction for query x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,\"key\" FROM e2e_test_pgch_mknqb5ih.\"test_normalize_metadata_with_retry_1\" ORDER BY id" rows=4 bytes=29 channelLen=0
    clickhouse_test.go:2222: WaitFor waiting for first sync to complete 2026-04-25 16:53:23.162458515 +0000 UTC m=+433.137022860
    clickhouse_test.go:2233: WaitFor waiting for raw table push to complete 2026-04-25 16:53:39.175460652 +0000 UTC m=+449.150024997
    clickhouse_test.go:2246: WaitFor waiting for normalize error 2026-04-25 16:53:39.178790882 +0000 UTC m=+449.153355207
    clickhouse_test.go:2259: WaitFor waiting for second sync to complete 2026-04-25 16:53:39.185910843 +0000 UTC m=+449.160475178
2026/04/25 16:53:39 INFO Executing and processing query x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,\"key\" FROM e2e_test_pgch_yj1tjsou.\"test_extra_ch_cols\" ORDER BY id"
2026/04/25 16:53:39 INFO Executing and processing query stream x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,\"key\" FROM e2e_test_pgch_yj1tjsou.\"test_extra_ch_cols\" ORDER BY id"
2026/04/25 16:53:39 INFO [pg_query_executor] declared cursor x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursorQuery="DECLARE peerdb_cursor_2887103178364364298 CURSOR FOR SELECT id,\"key\" FROM e2e_test_pgch_yj1tjsou.\"test_extra_ch_cols\" ORDER BY id" args=[]
2026/04/25 16:53:39 INFO [pg_query_executor] fetching rows start x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,\"key\" FROM e2e_test_pgch_yj1tjsou.\"test_extra_ch_cols\" ORDER BY id" channelLen=0
2026/04/25 16:53:39 INFO [pg_query_executor] fetching from cursor x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursor=peerdb_cursor_2887103178364364298
2026/04/25 16:53:39 INFO processed row stream x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursor=peerdb_cursor_2887103178364364298 records=2 bytes=15 channelLen=1
2026/04/25 16:53:39 INFO [pg_query_executor] fetched rows x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,\"key\" FROM e2e_test_pgch_yj1tjsou.\"test_extra_ch_cols\" ORDER BY id" rows=2 bytes=15 channelLen=1
2026/04/25 16:53:39 INFO [pg_query_executor] fetching from cursor x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursor=peerdb_cursor_2887103178364364298
2026/04/25 16:53:39 INFO processed row stream x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursor=peerdb_cursor_2887103178364364298 records=0 bytes=0 channelLen=0
2026/04/25 16:53:39 INFO [pg_query_executor] fetched rows x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,\"key\" FROM e2e_test_pgch_yj1tjsou.\"test_extra_ch_cols\" ORDER BY id" rows=0 bytes=0 channelLen=0
2026/04/25 16:53:39 INFO [pg_query_executor] committing transaction x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart
2026/04/25 16:53:39 INFO [pg_query_executor] committed transaction for query x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,\"key\" FROM e2e_test_pgch_yj1tjsou.\"test_extra_ch_cols\" ORDER BY id" rows=2 bytes=15 channelLen=0
    clickhouse_test.go:2270: WaitFor waiting for second raw table push to complete 2026-04-25 16:53:54.19907277 +0000 UTC m=+464.173637095
    clickhouse.go:97: 
        	Error Trace:	.../flow/e2e/congen.go:44
        	            				.../flow/e2e/clickhouse.go:97
        	            				.../flow/e2e/clickhouse.go:79
        	            				.../flow/e2e/clickhouse.go:154
        	            				.../flow/e2e/clickhouse_test.go:2271
        	            				.../flow/e2e/test_utils.go:852
        	            				.../flow/e2e/clickhouse_test.go:2270
        	Error:      	Received unexpected error:
        	            	unable to establish connection with catalog: FATAL: terminating connection due to administrator command (SQLSTATE 57P01)
        	Test:       	TestPeerFlowE2ETestSuitePG_CH/Test_Normalize_Metadata_With_Retry
    clickhouse.go:107: begin tearing down postgres schema pgch_mknqb5ih
2026/04/25 16:54:18 INFO Executing and processing query x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,val FROM e2e_test_api_oj1cinkj.\"table1\" ORDER BY id"
2026/04/25 16:54:18 INFO Executing and processing query stream x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,val FROM e2e_test_api_oj1cinkj.\"table1\" ORDER BY id"
2026/04/25 16:54:18 INFO [pg_query_executor] declared cursor x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursorQuery="DECLARE peerdb_cursor_11470598014849711466 CURSOR FOR SELECT id,val FROM e2e_test_api_oj1cinkj.\"table1\" ORDER BY id" args=[]
2026/04/25 16:54:18 INFO [pg_query_executor] fetching rows start x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,val FROM e2e_test_api_oj1cinkj.\"table1\" ORDER BY id" channelLen=0
2026/04/25 16:54:18 INFO [pg_query_executor] fetching from cursor x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursor=peerdb_cursor_11470598014849711466
2026/04/25 16:54:18 INFO processed row stream x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursor=peerdb_cursor_11470598014849711466 records=2 bytes=19 channelLen=1
2026/04/25 16:54:18 INFO [pg_query_executor] fetched rows x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,val FROM e2e_test_api_oj1cinkj.\"table1\" ORDER BY id" rows=2 bytes=19 channelLen=1
2026/04/25 16:54:18 INFO [pg_query_executor] fetching from cursor x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursor=peerdb_cursor_11470598014849711466
2026/04/25 16:54:18 INFO processed row stream x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart cursor=peerdb_cursor_11470598014849711466 records=0 bytes=0 channelLen=0
2026/04/25 16:54:18 INFO [pg_query_executor] fetched rows x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,val FROM e2e_test_api_oj1cinkj.\"table1\" ORDER BY id" rows=0 bytes=0 channelLen=0
2026/04/25 16:54:18 INFO [pg_query_executor] committing transaction x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart
2026/04/25 16:54:18 INFO [pg_query_executor] committed transaction for query x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} partitionId=testpart query="SELECT id,val FROM e2e_test_api_oj1cinkj.\"table1\" ORDER BY id" rows=2 bytes=19 channelLen=0
    clickhouse.go:107: 
        	Error Trace:	.../flow/e2e/pg.go:147
        	            				.../flow/e2e/clickhouse.go:107
        	            				.../flow/e2eshared/e2eshared.go:38
        	            				.../hostedtoolcache/go/1.26.2.../src/testing/testing.go:1317
        	            				.../hostedtoolcache/go/1.26.2.../src/testing/testing.go:1667
        	            				.../hostedtoolcache/go/1.26.2.../src/testing/testing.go:2030
        	            				.../hostedtoolcache/go/1.26.2.../src/runtime/panic.go:694
        	            				.../hostedtoolcache/go/1.26.2.../src/testing/testing.go:1022
        	            				.../flow/e2e/congen.go:44
        	            				.../flow/e2e/clickhouse.go:97
        	            				.../flow/e2e/clickhouse.go:79
        	            				.../flow/e2e/clickhouse.go:154
        	            				.../flow/e2e/clickhouse_test.go:2271
        	            				.../flow/e2e/test_utils.go:852
        	            				.../flow/e2e/clickhouse_test.go:2270
        	            				.../hostedtoolcache/go/1.26.2.../src/reflect/value.go:369
        	            				.../flow/e2eshared/e2eshared.go:40
        	Error:      	failed to teardown postgres schema
        	Test:       	TestPeerFlowE2ETestSuitePG_CH/Test_Normalize_Metadata_With_Retry
        	Messages:   	pgch_mknqb5ih: failed to drop replication slots: ERROR: replication slot "peerflow_slot_test_normalize_metadata_with_retry_pgch_mknqb5ih" is active for PID 17812 (SQLSTATE 55006)
--- FAIL: TestPeerFlowE2ETestSuitePG_CH/Test_Normalize_Metadata_With_Retry (181.48s)

To view more test analytics, go to the Test Analytics Dashboard
📋 Got 3 mins? Take this short survey to help us improve Test Analytics.

@github-actions

Copy link
Copy Markdown
Contributor

🔄 Flaky Test Detected

Analysis: Two different e2e tests failed across different matrix configurations with the same "failed to teardown postgres schema" teardown error, indicating CI environment timing/resource stress rather than a code regression.
Confidence: 0.8

✅ Automatically retrying the workflow

View workflow run

@github-actions

Copy link
Copy Markdown
Contributor

🔄 Flaky Test Detected

Analysis: TestApiPg/TestTableAdditionWithoutInitialLoad failed due to PostgreSQL SQLSTATE 57P01 (connection terminated by administrator command), a transient infrastructure error caused by the CI environment terminating a catalog connection — not a code regression.
Confidence: 0.95

✅ Automatically retrying the workflow

View workflow run

@renovate renovate Bot changed the title Update module github.com/aws/aws-sdk-go-v2/service/s3 to v1.97.3 [SECURITY] Update module github.com/aws/aws-sdk-go-v2/service/s3 to v1.97.3 [SECURITY] - autoclosed Apr 27, 2026
@renovate renovate Bot closed this Apr 27, 2026
auto-merge was automatically disabled April 27, 2026 17:49

Pull request was closed

@renovate renovate Bot deleted the renovate/go-github.com-aws-aws-sdk-go-v2-service-s3-vulnerability branch April 27, 2026 17:49
@renovate renovate Bot changed the title Update module github.com/aws/aws-sdk-go-v2/service/s3 to v1.97.3 [SECURITY] - autoclosed Update module github.com/aws/aws-sdk-go-v2/service/s3 to v1.97.3 [SECURITY] Apr 28, 2026
@renovate renovate Bot reopened this Apr 28, 2026
@renovate renovate Bot force-pushed the renovate/go-github.com-aws-aws-sdk-go-v2-service-s3-vulnerability branch 2 times, most recently from f7ca6cc to 0cabbb9 Compare April 28, 2026 00:10
@github-actions

Copy link
Copy Markdown
Contributor

🔄 Flaky Test Detected

Analysis: The test TestApiMy/TestEditTablesBeforeResync failed due to a PostgreSQL catalog connection being terminated by the server (SQLSTATE 57P01: terminating connection due to administrator command), which is a transient infrastructure error unrelated to the code under test.
Confidence: 0.92

✅ Automatically retrying the workflow

View workflow run

@github-actions

Copy link
Copy Markdown
Contributor

🔄 Flaky Test Detected

Analysis: The e2e test TestPeerFlowE2ETestSuitePG_CH_Cluster/Test_Binary_Format_Hex failed due to a PostgreSQL catalog connection being forcibly terminated (SQLSTATE 57P01: admin_shutdown), a transient CI infrastructure error rather than a test logic failure.
Confidence: 0.92

✅ Automatically retrying the workflow

View workflow run

@github-actions

Copy link
Copy Markdown
Contributor

🔄 Flaky Test Detected

Analysis: The failure is a transient PostgreSQL catalog connection drop (SQLSTATE 57P01 — "terminating connection due to administrator command") caused by cross-test interference in the 32-way parallel e2e test run, not a bug in the test logic.
Confidence: 0.92

✅ Automatically retrying the workflow

View workflow run

@renovate renovate Bot changed the title Update module github.com/aws/aws-sdk-go-v2/service/s3 to v1.97.3 [SECURITY] Update module github.com/aws/aws-sdk-go-v2/service/s3 to v1.97.3 [SECURITY] - autoclosed Apr 28, 2026
@renovate renovate Bot closed this Apr 28, 2026
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.

0 participants