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

Revert psycopg3 upgrade in postgres integration #15859

Merged
merged 24 commits into from
Sep 19, 2023

Conversation

alexandre-normand
Copy link
Contributor

@alexandre-normand alexandre-normand commented Sep 18, 2023

What does this PR do?

This PR reverts the upgrade of psycopg we made in #15411 in order to unblock internal production deploys of the agent. We believe this upgrade is causing blocking in the cluster worker, which is causing other checks to become blocked and not run properly.

Motivation

Additional Notes

Review checklist (to be filled by reviewers)

  • Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
  • Changelog entries must be created for modifications to shipped code
  • Add the qa/skip-qa label if the PR doesn't need to be tested during QA.

@github-actions
Copy link

The validations job has failed; please review the Files changed tab for possible suggestions to resolve.

@github-actions
Copy link

github-actions bot commented Sep 18, 2023

Test Results

     12 files       12 suites   16m 34s ⏱️
   227 tests    225 ✔️   2 💤 0
1 368 runs  1 320 ✔️ 48 💤 0

Results for commit 940ada8.

♻️ This comment has been updated with latest results.

* Add support for sending database_instance metadata

* Maybe fix test

* Add changelog

* Update CHANGELOG entry

* Update CHANGELOG entry using ddev tooling

* Fix some tests

* Set expected tags in test

* Fix sneaking typo

* Fix time package usage

* Proper fix for wrong time import

* Fix linting error
* Fix InstanceConfig loading error

* remove unnecessary ssl defaults

* Set log to be default value for ssl mode

* update changelog
* Return Azure AD auth token in correct format

* changelog
@github-actions
Copy link

The validations job has failed; please review the Files changed tab for possible suggestions to resolve.

@github-actions
Copy link

The validations job has failed; please review the Files changed tab for possible suggestions to resolve.

@jmeunier28 jmeunier28 changed the title Revert to last good commit Revert psycopg3 upgrade in postgres integration Sep 18, 2023
@github-actions
Copy link

The validations job has failed; please review the Files changed tab for possible suggestions to resolve.

@github-actions
Copy link

The validations job has failed; please review the Files changed tab for possible suggestions to resolve.

@github-actions
Copy link

The validations job has failed; please review the Files changed tab for possible suggestions to resolve.

@ghost ghost added the integration/mysql label Sep 18, 2023
@jmeunier28 jmeunier28 marked this pull request as ready for review September 18, 2023 21:16
@jmeunier28 jmeunier28 requested review from a team as code owners September 18, 2023 21:16
hestonhoffman
hestonhoffman previously approved these changes Sep 18, 2023
Copy link
Contributor

@jmeunier28 jmeunier28 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As a follow up, we should try to schema collection back in & survey anything else other than the upgrade to make sure all expected fixes still get into 7.48

@codecov
Copy link

codecov bot commented Sep 18, 2023

Codecov Report

Merging #15859 (940ada8) into master (e0aa0bd) will increase coverage by 0.09%.
The diff coverage is 92.15%.

Flag Coverage Δ
activemq ?
cassandra ?
hive ?
hivemq ?
hudi ?
ignite ?
jboss_wildfly ?
kafka ?
postgres 91.68% <92.15%> (-0.21%) ⬇️
presto ?
solr ?
tomcat ?
weblogic ?

Flags with carried forward coverage won't be shown. Click here to find out more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants