You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems as though you're using sysreqs to get the system requirements for a container and it seems you always get the list of packages, either from the session info, description, etc.
Once you have the list of packages, you seem to loop through each package. This is not required as sysreqs can handle a character vector of packages, such as https://sysreqs.r-hub.io/pkg/containerit,igraph,xml2,magick. The issue here is that the looping, for a large number of dependencies essentially DDoS's the API and then you get some 400's. I propose to stop the looping in .find_system_dependencies.
So, both functions are actually calling the API and so I think overall containerit should simply call sysreqs::sysreqs rather than the 2 functions. If I'm missing something, then I'd be interested to see why the 2 methods were created.
muschellij2
added a commit
to muschellij2/containerit
that referenced
this issue
Nov 19, 2021
It seems as though you're using
sysreqs
to get the system requirements for a container and it seems you always get the list of packages, either from the session info, description, etc.Once you have the list of packages, you seem to loop through each package. This is not required as
sysreqs
can handle a character vector of packages, such ashttps://sysreqs.r-hub.io/pkg/containerit,igraph,xml2,magick
. The issue here is that the looping, for a large number of dependencies essentially DDoS's the API and then you get some 400's. I propose to stop the looping in.find_system_dependencies
.Created on 2021-11-19 by the reprex package (v2.0.0)
Session info
The text was updated successfully, but these errors were encountered: