tests fail in 2032

Open Beginner friendly
#997 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
postgresql, python

Research direction

Start with tests/certs/client.cert.pem and run the test suite around the certificate-based tests. Check why the certificate expires on 2032-01-04 and update the test certificate or its test setup so the tests continue to pass after that date. Done means the affected tests pass with the future date.

Written by the indexing model from the issue text.

Description

  • asyncpg version: asyncpg-0.27.0
  • PostgreSQL version: N/A
  • Python version: 3.9++
  • Platform: openSUSE-Tumbleweed 20230126

While working on reproducible builds for openSUSE, I found that
our python-asyncpg package fails its tests after 2032-01-04 because tests/certs/client.cert.pem expired.

Background:
As part of my work on reproducible builds for openSUSE, I check that software still gives identical build results in the future.
The usual offset is +16 years, because that is how long I expect some software will be used in some places.
This showed up failing tests in our package build.
See https://reproducible-builds.org/ for why this matters.

Dominant language
Python
Stars
8.1k
Forks
469
Avg merge
4h 42m
Merged PRs (30d)
6

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MagicStack/asyncpg

All issues in MagicStack/asyncpg

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.