Bioconductor enumeration code is fault-intolerant

[andrewpollock]

Describe the bug Bioconductor ecosystem test failures (due to the code under test being brittle) blocked unrelated PRs

Expected behaviour A degree of intermittent non-200 responses shouldn't cause immediate enumeration failure

https://requests.readthedocs.io/en/latest/user/advanced/#example-automatic-retries

Additionally, during periods of external infrastructure failure, the tests could fail open.

[github-actions[bot]]

This issue has not had any activity for 60 days and will be automatically closed in two weeks

[andrewpollock]

/cc @tylfin FYI

We authored

• https://github.com/google/osv.dev/blob/master/osv/ecosystems/bioconductor.py
• https://github.com/google/osv.dev/blob/master/osv/ecosystems/bioconductor_test.py

and haven't gotten around to addressing this yet. I wanted to ensure you were aware of this in case you/anyone else from the R Consortium have time and interest in assisting with addressing it before we get around to it.

[github-actions[bot]]

This issue has not had any activity for 60 days and will be automatically closed in two weeks

See https://github.com/google/osv.dev/blob/master/CONTRIBUTING.md for how to contribute a PR if you're interested in helping out.

[andrewpollock]

@hogo6002 can the work you did on enumeration make this code obsolete?

[hogo6002]

@hogo6002 can the work you did on enumeration make this code obsolete?

I haven't replaced the API query for Bioconductor from the enumeration method to affected range comparison. If it consistently fails to enumerate versions for this ecosystem, I think we can switch to version range comparison very easily. Then, we probably won't need the enumeration code for this ecosystem.

[andrewpollock]

we probably won't need the enumeration code for this ecosystem

Less (fault-intolerant, in particular) code SGTM 😺