Opened 7 years ago
Closed 7 years ago
#15622 closed defect (fixed)
Immutable graphs must not be relabeled
Reported by:  ncohen  Owned by:  

Priority:  major  Milestone:  sage6.1 
Component:  graph theory  Keywords:  
Cc:  SimonKing  Merged in:  
Authors:  Nathann Cohen  Reviewers:  Simon King 
Report Upstream:  N/A  Work issues:  
Branch:  u/ncohen/15622 (Commits, GitHub, GitLab)  Commit:  6398780eca28da56527b3360d5fd597308517db9 
Dependencies:  #15619  Stopgaps: 
Description
Now
sage: Graph(graphs.PetersenGraph(), immutable=True).relabel({}) ... ValueError: Thou shalt not relabel an immutable graph
Before, the following happened
sage: Graph(graphs.PetersenGraph(), data_structure="static_sparse").relabel({}) ... AttributeError: 'StaticSparseBackend' object has no attribute 'vertex_ints'
This is actually another bug, as there should be a vertex_ints
variable in static sparse graphs. But that's another problem to be addressed in another ticket :P
Nathann
Change History (28)
comment:1 Changed 7 years ago by
 Branch set to u/ncohen/15622
 Status changed from new to needs_review
comment:2 Changed 7 years ago by
 Dependencies changed from #15603 to #15619
comment:3 Changed 7 years ago by
 Commit set to 0f578050749912c5f5c66824cf50475aa74c0f23
comment:4 Changed 7 years ago by
The code looks good. Perhaps the error message should hint at how to create a mutable copy?
comment:5 Changed 7 years ago by
OKayyyyyyyy.. What about this ?
Nathann
comment:6 Changed 7 years ago by
 Commit changed from 0f578050749912c5f5c66824cf50475aa74c0f23 to 529f7850c111c19522a8f18f9ce829e1e3a5b769
Branch pushed to git repo; I updated commit sha1. New commits:
529f785  trac #15622: More informative exception message

comment:7 Changed 7 years ago by
 Status changed from needs_review to needs_work
Oops:
sage t long src/sage/graphs/base/static_sparse_backend.pyx ********************************************************************** File "src/sage/graphs/base/static_sparse_backend.pyx", line 422, in sage.graphs.base.static_sparse_backend.StaticSparseBackend.relabel Failed example: g.relabel([],True) Expected: Traceback (most recent call last): ... ValueError: Thou shalt not remove a vertex from an immutable graph Got: <BLANKLINE> Traceback (most recent call last): File "/home/king/Sage/git/sage/local/lib/python2.7/sitepackages/sage/doctest/forker.py", line 480, in _run self.execute(example, compiled, test.globs) File "/home/king/Sage/git/sage/local/lib/python2.7/sitepackages/sage/doctest/forker.py", line 839, in execute exec compiled in globs File "<doctest sage.graphs.base.static_sparse_backend.StaticSparseBackend.relabel[2]>", line 1, in <module> g.relabel([],True) AttributeError: 'sage.graphs.base.static_sparse_backend.StaticSpars' object has no attribute 'relabel'
That is the only error, and I'll probably fix it in a review commit.
comment:8 Changed 7 years ago by
WTF??????
When I do the obvious and change StaticSparseCGraph
into StaticSparseBackend
, I get
Failed example: g.relabel([],True) Expected: Traceback (most recent call last): ... ValueError: Thou shalt not remove a vertex from an immutable graph Got: <BLANKLINE> Traceback (most recent call last): File "/home/king/Sage/git/sage/local/lib/python2.7/sitepackages/sage/doctest/forker.py", line 480, in _run self.execute(example, compiled, test.globs) File "/home/king/Sage/git/sage/local/lib/python2.7/sitepackages/sage/doctest/forker.py", line 839, in execute exec compiled in globs File "<doctest sage.graphs.base.static_sparse_backend.StaticSparseBackend.relabel[2]>", line 1, in <module> g.relabel([],True) File "static_sparse_backend.pyx", line 428, in sage.graphs.base.static_sparse_backend.StaticSparseBackend.relabel (sage/graphs/base/static_sparse_backend.c:4740) ValueError: Thou shalt not relabel an immutable graph
Where does the blankline come from? And why is there no blankline when doing the test interactively?
comment:9 Changed 7 years ago by
Ahaaa! You had a wrong class and a wrong error message in your test ("remove a vertex" versus "relabel").
comment:10 followup: ↓ 11 Changed 7 years ago by
I don't get what the "obvious change from StaticSparseCGraph
into StaticSparseBackend
" could be O_o
Nathann
comment:11 in reply to: ↑ 10 Changed 7 years ago by
Replying to ncohen:
I don't get what the "obvious change from
StaticSparseCGraph
intoStaticSparseBackend
" could beO_o

src/sage/graphs/base/static_sparse_backend.pyx
diff git a/src/sage/graphs/base/static_sparse_backend.pyx b/src/sage/graphs/base/static_sparse_backend.pyx index 9b5a8fe..e5b889e 100644
a b class StaticSparseBackend(CGraphBackend): 417 417 418 418 TEST:: 419 419 420 sage: from sage.graphs.base.static_sparse_backend import StaticSparse CGraph421 sage: g = StaticSparse CGraph(graphs.PetersenGraph())420 sage: from sage.graphs.base.static_sparse_backend import StaticSparseBackend 421 sage: g = StaticSparseBackend(graphs.PetersenGraph()) 422 422 sage: g.relabel([],True) 423 423 Traceback (most recent call last): 424 424 ... 425 ValueError: Thou shalt not re move a vertex froman immutable graph425 ValueError: Thou shalt not relabel an immutable graph 426 426 427 427 """ 428 428 raise ValueError("Thou shalt not relabel an immutable graph")
StaticSparceCGraph
simply is the wrong class.
comment:12 Changed 7 years ago by
For the record: It already takes 5 minutes to push my review commit.
comment:13 Changed 7 years ago by
 Branch changed from u/ncohen/15622 to u/SimonKing/ticket/15622
 Created changed from 01/02/14 21:20:19 to 01/02/14 21:20:19
 Modified changed from 01/03/14 13:20:36 to 01/03/14 13:20:36
comment:14 Changed 7 years ago by
 Branch changed from u/SimonKing/ticket/15622 to u/ncohen/15622
Oh. Ahem. Right O_O;;;;;;
Sorryyyyyyyyyyyyyyyyyyyyyyyyyyy O_O;;;;;
Nathann
Review commit : I often Ctrl+C it before it ends. Trac sends the mails almost instantaneously, the trac ticket is updated at the same time. I just have no idea what it does afterwards.
comment:15 Changed 7 years ago by
 Branch changed from u/ncohen/15622 to u/SimonKing/ticket/15622
 Commit changed from 529f7850c111c19522a8f18f9ce829e1e3a5b769 to 2245c020cd80a1d248cf0a453270f4dbd9d12f36
 Status changed from needs_work to positive_review
It seems that once more I have to manually upload the commit.
comment:16 Changed 7 years ago by
I think it's because you should set the branch name *before* pushing the commit. Otherwise nothing is triggered on the trac server's side.
Nathann
comment:17 Changed 7 years ago by
Okay. We are now in the VolkerFeared situation of a ticket which has a positive review, with a dependency which is still in needs_review
:P
Thanks for this commit !
Nathann
comment:18 Changed 7 years ago by
By the way, isn't the trac server 99999x times faster than yesterday ? Andrew said he would do something about it and it looks like he did O_O
Nathann
comment:19 Changed 7 years ago by
 Milestone changed from sage6.1 to sagepending
comment:20 Changed 7 years ago by
 Milestone changed from sagepending to sage6.1
comment:21 Changed 7 years ago by
 Reviewers set to Simon King
comment:22 followup: ↓ 26 Changed 7 years ago by
 Status changed from positive_review to needs_work
Various doctests fail (see also patchbot)
comment:23 Changed 7 years ago by
Gloops. Right.
comment:24 Changed 7 years ago by
 Branch changed from u/SimonKing/ticket/15622 to u/ncohen/15622
 Commit changed from 2245c020cd80a1d248cf0a453270f4dbd9d12f36 to 529f7850c111c19522a8f18f9ce829e1e3a5b769
 Status changed from needs_work to needs_review
That's the only way I found to make this work before #15623 is merged T_T
Nathann
comment:25 Changed 7 years ago by
 Commit changed from 529f7850c111c19522a8f18f9ce829e1e3a5b769 to 6398780eca28da56527b3360d5fd597308517db9
Okay, it looks like the automatic message does not work, but the branch is updated !
Nathann
comment:26 in reply to: ↑ 22 Changed 7 years ago by
Replying to vbraun:
Various doctests fail (see also patchbot)
WTF? When I reviewed it, things worked. Or did I accidentally merge other tickets that aren't dependencies for this?
comment:27 Changed 7 years ago by
 Status changed from needs_review to positive_review
Hooray. After pulling from the ticket branch and merging with the current develop branch, make ptest
results in
All tests passed!  Total time for all tests: 3791.7 seconds cpu time: 6340.1 seconds cumulative wall time: 7304.6 seconds
Nathann's last commit looks like the right thing to do. Hence, I hope this time my positive review will persist...
comment:28 Changed 7 years ago by
 Resolution set to fixed
 Status changed from positive_review to closed
Branch pushed to git repo; I updated commit sha1. Last 10 new commits:
trac #15622: Immutable graphs must not be relabeled
trac #15619: bug in the former definition; exception to avoid it in the future
trac #15619: Pickling of immutable graphs
trac #15603: "immutable=True" for Graph/Digraph __init__ and copy()
Trac 15278: Fix syntax error in doc test
Trac 15278: Only graphs that use the static backend are identical with their copy
Merge branch 'develop' into ticket/15278
Trac 15278: Error messages explain how to create (im)mutable graph copy
Make digraphs using the static backend immutable and hashable
Merge branch 'u/ncohen/15491' of git://trac.sagemath.org/sage into ticket/15278