-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Verify Compatibility with network 1.19.0 #10
Comments
Is this against the CRAN version or the https://github.com/EpiModel/networkLite version? |
This is against the CRAN version of networkLite. I just tried testing the github version, but it requires a statnet.common version that is greater than the version that is on CRAN. (Probably best not to put hard dependencies on packages that are not available, since no one can then use this package. I try to avoid version constraints unless absolutely necessary.) |
OK, I manually updated statnet.commons to the latest github version, and installed the github version of networkLite. With network 1.19, running local tests gives me the following:
I can't run it against the old network version, since it depends on 1.19, so there's no way to know if these are existing issues. But the warnings seem likely to set off CRAN. Anyway, the real question is whether this needs to be fixed right away, or whether I can tell CRAN that this is being worked on and will be corrected imminently. Since this version of networkLite is presumably waiting on the network release, I would presume that it's mostly ready to go? Just need to make sure I'm not creating more problems than I'm solving! |
This is for the |
These warnings are internal to |
…d be eliminated for consistency with 'network' (or added to 'network'). references #10
Not sure. FWIW, I also tightened up some code (in both the R and the C side) that could in theory cause issues if abusive calls were made. (One of these was previously protected, but a change associated with the switch to generic functions exposed it.) Depending on what the weird inputs are, that could be pertinent. To meet the deadline, I've pushed the current version of network to CRAN, but we'll see if it makes it past the gauntlet. |
OK, I had an exciting issue with some code that caused massive issues with some packages (and that was not caught by |
Hi, folks. I'm about to push network 1.19.0 (see the current github for the latest version), and revdep check suggests that there could be an issue with networkLite. The issues seem to arise in test-all.R, calling test-networkLite.R. It looks to be arising from the tibble-based methods. The output is such:
We need to push
network
in the next three days, so it would be great if you could check this - don't want to cause issues when we push! Thanks!!The text was updated successfully, but these errors were encountered: