Closed Alexander-Serov closed 1 year ago
@Alexander-Serov from a quick look it seems like:
ValueError
ValueError
but a new exception CassetteNotFoundError
, see #681 and https://vcrpy.readthedocs.io/en/latest/advanced.html#register-your-own-cassette-persisterWhat do you think?
@Alexander-Serov PS: If you could report this as a bug to pytest-recording at https://github.com/kiwicom/pytest-recording/issues that would be great. PPS: We also released VCR.py 4.4.0 yesterday, the planned last on the 4.x.x track. Downgrading to 4.4.0 is not a good long-term approach, but may help to put out the fire for the moment.
Hey @hartwork,
Thanks for the fast answer. Yes, this totally makes sense to me and you guessed it right, I am using vcrpy
through pytest-recording
. It didn't show up in the main error message, so I came here first, but yes, totally makes sense to file an issue on their side. Do you mind keeping this issue open here for the moment, in case it requires any interaction between the 2 issues (or as a landing zone for newcomers)?
And yes, we have temporarily downgraded on our side, but it should be properly fixed by pytest-recording
, I agree! Thanks for the suggestion!
@Alexander-Serov thanks for the update. I have labelled the issue as a question now. We can link to this issue open or closed, I can try if pinning it for a few days works even in closed state, will see.
I think we still need to agree on who does the reporting to pytest-recording. Could you take that over? You need the change in pytest-recording more than I do, since I use plain VCR.py myself.
@Alexander-Serov PS: Pinning in closed state seems to work fine:
@Alexander-Serov thanks for https://github.com/kiwicom/pytest-recording/issues/111 ! :+1:
@hartwork Great, thanks for the fast reaction!
// Suggested Solution: // 1. Check the release notes and changelog for version 5.0.0 to identify any relevant changes related to cassette management or configuration. // 2. Review the project's test and configuration files to ensure they align with the changes introduced in version 5.0.0. // 3. If necessary, adjust the cassette setup or configuration to address the "No cassettes found" issue. // Note: This issue might be specific to certain configurations or edge cases, so thorough testing and investigation are required to determine the root cause.
For some reason, after upgrading to vcrpy==5.0.0, the old cassettes on our working pipeline are not found anymore. Since there are no changes in code, something seems to have changed in
vcrpy
.I understand it's a major version release, so it is the right place to introduce new functionality and break the old one, but in this case, I would like to suggest a clearer message to the user on how to fix it. For the moment, it just says that the cassettes are not found, which is wrong. They are present at the same location they are found by v4.*.