Conversation
|
Can you elaborate on " games sometimes hangs on my system"? Most of these seem straighforward issues related to changes in functions arguments. Some functions gained new arguments, some had arguments removed. For example, The reasons for each change should be clear from https://github.com/igraph/igraph/blob/develop/CHANGELOG.md — if not, we need to improve the changelog. |
This comment was marked as outdated.
This comment was marked as outdated.
|
|
For the top of the list,
|
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
I cleaned up the changelog significantly to make it more readable. My advice here is not to start with fixing tests. That is going to be frustrating and risks that things will be left broken. Instead, just read the changelog, and address each change one by one. A few may still remain, and only then would I start doing this in a test-driven way. The changelog of the C core is written manually, not automatically compiled from commits, so it should be relatively easy to follow. |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as outdated.
This comment was marked as outdated.
|
No, the changelog is here on the https://github.com/igraph/igraph/blob/develop/CHANGELOG.md Everything under the I am not saying NOT to look at tests, but that trying to do this in a test-driven way is a recipe for pain, frustration and maybe disaster. Not every change that is necessary will (or can) be caught by tests. I recommend using the changelog as the primary driver, and using tests to clean up what's left after. For example, if you rely on tests, you might notice strange behaviour from
|
Does this mean we should check the length of the unique values of the |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
It's the opposite: It means that this is no longer a concern. This is in the "Changed" section, which lists changes which are not really breaking. It's good to look at these, but the "Breaking changes" section is the more important one. I looked at the three bullet points under "Changed"—none of these need any adaptation from the R side. |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
|
When a function gained an argument in the C core, do we have to handle that or is there a default value anyway? |
|
I wonder whether we should also open "expose" issues for them to not forget. |
Absolutely. |
|
In many cases, the first and quickest step towards fixing things is to move functions to auto-generation. Kirill has done a lot of these already. That's why this branch even compiles. So, treat things from |
|
@krlmlr could you please remind me why we're keeping this PR open? |
This shows the result of updating snapshot tests for the
nextbranch. Also clearing the "embedding" and "games" tests.authority_score()workshub_score()workshits_score()works -- authorityhits_scores()works -- hubWe need to resolve this before vendoring on the
nextbranch can resume.@szhorvat: Can you please help?
Details