Consider moving to upstream vcrpy once the upstream async httpx issues are resolved

konveyor-ecosystem / kai

Konveyor AI - static code analysis driven migration to new targets via Generative AI

Apache License 2.0

8 stars 10 forks source link

Consider moving to upstream vcrpy once the upstream async httpx issues are resolved #207

Open jwmatthews opened 4 days ago

jwmatthews commented 4 days ago

Reminder we are using a fork of vcrpy as we wait for a fix to be merged in their upstream

https://github.com/konveyor-ecosystem/kai/blob/main/requirements.txt#L195C1-L196C75

# My fork has changes that fix some async issues in the real vcrpy that are yet to be accepted
git+https://github.com/fabianvf/vcrpy.git@httpx-async-threadpool#egg=vcrpy

See @fabianvf's fix at: https://github.com/kevin1024/vcrpy/pull/833