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

chore(redshift): retry schema does not exist errors in list schemas #208

Merged
merged 1 commit into from
Nov 1, 2024

Conversation

atzoum
Copy link
Collaborator

@atzoum atzoum commented Oct 4, 2024

Description

If the list schemas query is executed while a schema is being deleted, the query can fail with a schema does not exist error. This is happening for instance while multiple pull request tests are running. Therefore, we are now retrying such errors.

Security

  • The code changed/added as part of this pull request won't create any security issues with how the software is being used.

Copy link

codecov bot commented Oct 4, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.04%. Comparing base (f11118d) to head (e1c74a3).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #208      +/-   ##
==========================================
+ Coverage   87.00%   87.04%   +0.03%     
==========================================
  Files          87       88       +1     
  Lines        3872     3882      +10     
==========================================
+ Hits         3369     3379      +10     
  Misses        347      347              
  Partials      156      156              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@atzoum atzoum force-pushed the fix.flakyTest branch 4 times, most recently from 6da1c4d to 42586f1 Compare October 11, 2024 13:33
@atzoum atzoum changed the title [WIP] chore: debug statement mismatch chore(redshift): retry schema does not exist errors in list schemas Oct 11, 2024
Copy link

github-actions bot commented Nov 1, 2024

This PR is considered to be stale. It has been open 20 days with no further activity thus it is going to be closed in 5 days. To avoid such a case please consider removing the stale label manually or add a comment to the PR.

@github-actions github-actions bot added the Stale label Nov 1, 2024
@atzoum atzoum merged commit 78a6d0a into main Nov 1, 2024
20 checks passed
@atzoum atzoum deleted the fix.flakyTest branch November 1, 2024 09:28
atzoum pushed a commit that referenced this pull request Nov 1, 2024
🤖 I have created a release *beep* *boop*
---


##
[1.13.0](v1.12.0...v1.13.0)
(2024-11-01)


### Features

* **redshift:** bump github.com/aws/aws-sdk-go-v2/service/redshiftdata
from 1.29.4 to 1.30.1
([#216](#216))
([efefea6](efefea6))
* **trino:** bump github.com/trinodb/trino-go-client from 0.316.0 to
0.317.0 ([#214](#214))
([f11118d](f11118d))


### Miscellaneous

* **deps:** bump cloud.google.com/go from 0.115.1 to 0.116.0
([#222](#222))
([c5c3025](c5c3025))
* **deps:** bump github.com/aws/aws-sdk-go-v2/config from 1.27.40 to
1.27.41 ([#211](#211))
([1a35100](1a35100))
* **deps:** bump github.com/aws/aws-sdk-go-v2/config from 1.27.41 to
1.28.1 ([#227](#227))
([9f34b6f](9f34b6f))
* **deps:** bump github.com/rudderlabs/rudder-go-kit from 0.42.0 to
0.43.0 ([#213](#213))
([1bfe41d](1bfe41d))
* **deps:** bump google.golang.org/api from 0.199.0 to 0.204.0
([#226](#226))
([c7e8b62](c7e8b62))
* **deps:** bump rudderlabs/pr-description-enforcer from 1.0.0 to 1.1.0
([#209](#209))
([4349e7f](4349e7f))
* **redshift:** retry schema does not exist errors in list schemas
([#208](#208))
([78a6d0a](78a6d0a))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
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.

1 participant