Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cache, or increase TTL for cached versions of, stable build tools such as Python x.y to avoid remote breakage

See original GitHub issue

Description:

This feature request results from the suggestion under “Expected Behaviour” when reporting the failure of CI tests specifying PyPy 3.7.

2022-07-04T23:12:24.5261882Z ##[group]Run actions/setup-python@v2
2022-07-04T23:12:24.5262166Z with:
2022-07-04T23:12:24.5262474Z   python-version: pypy-3.7
2022-07-04T23:12:24.5262955Z   token: ***
2022-07-04T23:12:24.5263234Z ##[endgroup]
2022-07-04T22:52:51.6322476Z PyPy version 3.7 (x) was not found in the local cache
2022-07-04T22:52:52.1006041Z ##[error]
2022-07-04T22:52:52.1006041Z ##[error]
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html>
  <head>
    <title>503 certificate has expired</title>
  </head>
  <body>
    <h1>Error 503 certificate has expired</h1>
    <p>certificate has expired</p>
    <h3>Error 54113</h3>
    <p>Details: cache-iad-kiad7000098-IAD 1656975172 2426781050</p>
    <hr>
    <p>Varnish cache server</p>
  </body>
</html>

Action version: See log

Platform:

Ubuntu
macOS
Windows

Runner type:

Hosted
Self-hosted

Tools version:

PyPy 3.7

Repro steps:

https://github.com/ytdl-org/youtube-dl/runs/7187814676?check_suite_focus=true

Also, try https://downloads.python.org/pypy/

Expected behaviour:

Run test as specified with PyPy 3.7.

Even if the actual problem is with Python.org’s slack site admin, it would be better to set a long cache lifetime for mainline tools that are updated only infrequently, so that if something like this happens the cached version can be used and a warning flagged. The lifetime should be of the order of the time that it takes to resolve this sort of failure, ie days or weeks.

Actual behaviour:

See log.

Issue Analytics

State:
Created a year ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

mattipcommented, Jul 12, 2022

feature request related to caching

Perhaps then the title should be changed?

0reactions

IvanZosimovcommented, Jul 12, 2022

Hi, @mattip 👋 ! Thanks for the suggestion, but we will keep it open as a feature request related to caching PyPy versions as a backup in case of PyPy server outages. 💾

Top Results From Across the Web

cachetools — Extensible memoizing collections and ...

This module provides multiple cache classes based on different cache algorithms, as well as decorators for easily memoizing function and method calls. Cache...

Using Redis In-Memory Storage for your Python Applications

Leverage in-memory data storage to cache data, handle user sessions, and avoid database transactions to keep your Python app snappy.

Python in-memory cache with time to live - Stack Overflow

This solution is really elegant. It's just a pity that this method doesn't guarantee that each cached value expires exactly after the TTL...

Stack Overflow: How We Do App Caching - 2019 Edition

Like debating which cache server is best! We have a few Redis instances to separate concerns of apps (but on the same set...

Modules are cached - Python Morsels

When re-importing a module Python will use the cached version of your module (instead of reevaluating your code). To refresh a module while...