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

Older PG compat #1306

Merged
merged 5 commits into from
Jan 28, 2025
Merged

Older PG compat #1306

merged 5 commits into from
Jan 28, 2025

Conversation

Xowap
Copy link
Contributor

@Xowap Xowap commented Jan 27, 2025

Closes #1305

Successful PR Checklist:

  • Tests
    • (not applicable?)
  • Documentation
    • (not applicable?)

PR label(s):

@Xowap Xowap requested a review from a team as a code owner January 27, 2025 10:02
@github-actions github-actions bot added the PR type: bugfix 🕵️ Contains bug fix label Jan 27, 2025
Copy link

Coverage report

This PR does not seem to contain any modification to coverable code.

@medihack
Copy link
Member

Hi @Xowap. Thanks a lot for fixing this! We should also test older Postgresql versions during CI. I already added a PR draft for that (#1307). If you like, add the changes in the ci.yml to your PR and extend the supported versions of PostgreSQL (matrix.postgresql-version). We can try everything >= 13 (https://www.postgresql.org/support/versioning/).

@Xowap
Copy link
Contributor Author

Xowap commented Jan 27, 2025

Makes much sense, adding it

@medihack
Copy link
Member

LGTM. @ewjoachim Ok for you, too?
I will add a note about the supported PostgreSQL versions to the documentation. I have to adjust the supported Python versions there anyway.

@@ -61,6 +61,46 @@ jobs:
path: .coverage.${{ matrix.python-version }}
include-hidden-files: true

older-db-versions:
Copy link
Member

Choose a reason for hiding this comment

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

I'm a bit weary of adding so many tests. What about changing the existing python matrix so that at the same time as we test old python versions, we test old postgres too ?

Copy link
Member

@medihack medihack Jan 27, 2025

Choose a reason for hiding this comment

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

My first version exactly did this, but I did not like it. I don't want to run coverage or upload artifacts. Of course, one can do this conditionally, but the job becomes more complicated. Also, the matrix itself becomes more complex as we want to test every Python version, but not every Python version against every database version. So, overall, I find a separate job more clear.
But I can implement it in my other PR (#1307) how it would look like.

Copy link
Member

Choose a reason for hiding this comment

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

So it would look something like this then. Do you think it's better? Or do you have something else in mind?
The --cov quite matters (running the whole test suite on my Laptop 47s vs 55s).

Copy link
Member

Choose a reason for hiding this comment

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

@Xowap I understood ewjoachim wrong, but his suggestion makes total sense now. Would you mind adapting the CI code to something like this: https://github.com/procrastinate-org/procrastinate/pull/1307/files
Sorry for the extra work and that I didn't think of it myself 🤦.

Copy link
Member

Choose a reason for hiding this comment

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

@Xowap I had some time left and quickly changed it 🙂.

@medihack medihack merged commit 4f63ae3 into procrastinate-org:main Jan 28, 2025
13 checks passed
@medihack
Copy link
Member

@Xowap Thanks a lot for the contribution! I will create a new fix release later.

@Xowap
Copy link
Contributor Author

Xowap commented Jan 28, 2025

Thanks for making contributing a nice experience!

Waiting eagerly to revert my pyproject.toml back to sanity 🤓

@ewjoachim
Copy link
Member

It was a pleasure to welcome your first Procrastinate contribution :) See you around !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR type: bugfix 🕵️ Contains bug fix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Migration syntax error
3 participants