question-mark
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.

GitHub CIs no longer work with v0.7.0

See original GitHub issue

GitHub CIs are still using Python 3.8, which results in incompatibility with v0.7.0. It seems to have been missed by Poxy CI since it never ran Poxy itself - the tests are never used.

Traceback (most recent call last):
  File "/usr/local/bin/poxy", line 5, in <module>
    from poxy.main import main
  File "/usr/local/lib/python3.8/dist-packages/poxy/main.py", line 1[7](https://github.com/wroyca/rune/runs/8239827362?check_suite_focus=true#step:4:8), in <module>
    from . import css
  File "/usr/local/lib/python3.[8](https://github.com/wroyca/rune/runs/8239827362?check_suite_focus=true#step:4:9)/dist-packages/poxy/css.py", line 28, in <module>
    def resolve_imports(text, cwd=None, mcss_dir = None) -> tuple[str, bool]:
TypeError: 'type' object is not subscriptable

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:11 (11 by maintainers)

github_iconTop GitHub Comments

1reaction
wroycacommented, Sep 8, 2022

~Yeah I think the discriminator here is that in my toml++ CI i’m explicitly invoking apt get install python3 so it’s probably updating it post-3.8. I’ll push a poxy update to fix that type annotation so that isn’t necessary.~ Oh, so are you. I have no idea then.

Poxy CI since it never ran Poxy itself - the tests are never used.

Heh, yeah. There’s no tests currently; I set up some CI to blast out different versions of Doxygen and started writing a framework for diffing poxy outputs, but ran out of steam. Definitely need to square that circle at some point.

Had a quick look, you re-synchronize the package index files from their sources and then install python which now fetch most likely 3.9~3.10. Mine doesn’t re-synchronize the index and instead use it as it is with the image by default, therefore pulling 3.8. I can fix that on my end 😃

1reaction
marzercommented, Sep 8, 2022

Ah, it’s likely because I’m doing this:

    container:
      image: debian:testing

That was necessary for something in toml++'s CI (linux shenanigans, I dunno), and I suppose I’ve unthinkingly copied it into the GH pages workflow 😅

Read more comments on GitHub >

github_iconTop Results From Across the Web

v0.7.0 Milestone - GitHub
Checks whether Kubernetes is deployed according to security best practices as defined in the CIS Kubernetes Benchmark - v0.7.0 Milestone ...
Read more >
On 2022-04-05, the default branch will be renamed ... - GitHub
On 2022-04-05, we are going to rename the branch from "master" to "main". At that point, we can no longer provide an informative...
Read more >
CIS Kubernetes V1.20 Benchmark v1.0.0 · Issue #897 - GitHub
New CIS Kubernetes V1.20 Benchmark v1.0.0 was published 2 weeks ago on May 19th 2021 And we should add support for it.
Read more >
CIS benchmark rke2 hardened fails in 5.3.1 with cilium as CNI
Just updated to rancher 2.6.5 and deployed cis benchmark 2.0.4. scanned the downstream cluster and got an error for 5.3.1 (cni does not...
Read more >
What k8s versions are supported? · Discussion #908 - GitHub
I see that you have merged the "CIS Kubernetes V1.20 Benchmark v1.0.0" PR. ... Do you know when v0.7.0 will be available?
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found