-
-
Notifications
You must be signed in to change notification settings - Fork 553
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
Immutable graph backend for Posets #15623
Comments
Commit: |
Branch: u/ncohen/15623 |
Last 10 new commits:
|
Work Issues: doctest error related with hash of mutable graphs |
comment:3
Merging all the dependencies (there are review commits that are not part of your branch), I get this error:
I am wondering: Shouldn't the error message say But in any case, this error needs fixing. I'll see what I can do about it. |
comment:4
Aha. This is about a function that returns
I suppose this should be
instead. The fact that the doctest is about hash shows that we want an immutable graph. |
Changed branch from u/ncohen/15623 to u/SimonKing/ticket/15623 |
comment:6
With the review commit I just added, all tests should pass. "Should". I'll hopefully finish review tomorrow. PS: Again I had to change the commit field manually. |
comment:7
Please resolve the conflict with your new commit in #15622. |
comment:8
Done ! Nathann |
Changed commit from |
Changed branch from u/SimonKing/ticket/15623 to public/15623 |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Commit: |
comment:10
I don't know how THIS could be read without the ticket numbers |
comment:11
The merge was successful (looking at the code), and all tests pass. |
Changed work issues from doctest error related with hash of mutable graphs to none |
comment:15
This doesn't merge with the latest |
Changed branch from public/15623 to u/SimonKing/ticket/15623 |
comment:17
I attempted to merge the develop branch into the ticket branch. Nathann, could you check whether you think the merge was successful? I am running tests now. If it works, then I think it can be back to positive review New commits:
|
comment:18
Arrgh. It seems I did wrong.
|
comment:19
There are more errors concerning the missing attribute 'vertex_ints'. Nathann, do you have an idea what went wrong? |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:22
Ahaaaa! It seems that I did wrong when merging! Namely, I have removed the vertex_ints attribute. In a second commit, I re-introduced it. Well, the joy of git. I don't dare to amend the merge commit and rather add an ugly second commit on top of a wrong first commit At least one of the failing doctests is now working. So, needs review again, and since I am the reviewer, I suppose I can revert to positive review as soon as |
comment:23
|
comment:24
Looks good to me, but I wasn't able to see directly from git how the conflicts were manually solved. So it works, but it's a bit scary that there does not seem to be a way to see that Thank you Simon for doing this ! I was away for 4 days, and rather unreachable in cold cold Hungary. I was there because I had promised a pretty girl a braid of dried chili, and a friend told me they had nice ones in Hungary Nathann |
At long, long last, it passes all tests
:-P
Thank you Simon for your help with all this !!!
Nathann
Depends on #15622
CC: @simon-king-jena
Component: combinatorics
Author: Nathann Cohen
Branch/Commit: u/SimonKing/ticket/15623 @
c5b6d59
Reviewer: Simon King
Issue created by migration from https://trac.sagemath.org/ticket/15623
The text was updated successfully, but these errors were encountered: