[Graphs] Bug in directed edge-connectivity algorithm
Dear all, my name is Michele Borassi, and I am a user of Boost Graph library, version 1.58.0. I have found a problem in the edge connectivity algorithm: if the input is a directed path with 3 vertices (0, 1, 2) and 2 edges ((0,1), (1,2)), the output is 1 (while it should be 0, since the graph is not strongly connected). However, if edge (1,0) is added, the output becomes (correctly) 0. A minimal working example that shows this issue is attached; my output is: Path of 3 vertices and 2 edges. The edge connectivity is 1. Added edge (1,0): now there are 3 edges. The edge connectivity becomes 0. Could you also explain me which is the best way to report a bug? I have checked your web page http://www.boost.org/development/bugs.html, but all links seem to be broken. Waiting for your answer, I thank you in advance, Michele Borassi
On 6/15/2015 5:40 AM, Michele Borassi wrote:
Dear all, my name is Michele Borassi, and I am a user of Boost Graph library, version 1.58.0.
I have found a problem in the edge connectivity algorithm: if the input is a directed path with 3 vertices (0, 1, 2) and 2 edges ((0,1), (1,2)), the output is 1 (while it should be 0, since the graph is not strongly connected). However, if edge (1,0) is added, the output becomes (correctly) 0. A minimal working example that shows this issue is attached; my output is:
Path of 3 vertices and 2 edges. The edge connectivity is 1. Added edge (1,0): now there are 3 edges. The edge connectivity becomes 0.
Could you also explain me which is the best way to report a bug? I have checked your web page http://www.boost.org/development/bugs.html, but all links seem to be broken.
None of the links are broken when I try them. Try 4) or 5) to report a bug in the Trac system.
Waiting for your answer, I thank you in advance, Michele Borassi
On 15 Jun 2015 at 8:44, Edward Diener wrote:
Could you also explain me which is the best way to report a bug? I have checked your web page http://www.boost.org/development/bugs.html, but all links seem to be broken.
None of the links are broken when I try them.
Try 4) or 5) to report a bug in the Trac system.
I would assume the OP thinks the three month old SSL cert expiry warnings means broken links. I can see the point. I tried reminding boost-steering about this again recently, still no movement unfortunately. It could be the case that nobody knows any longer who can get into root on the main Boost web server, as I have been asking to try upgrading the Trac install on boost-steering for some weeks now to no avail. Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/
On 06/15/2015 08:20 AM, Niall Douglas wrote:
On 15 Jun 2015 at 8:44, Edward Diener wrote:
Could you also explain me which is the best way to report a bug? I have checked your web page http://www.boost.org/development/bugs.html, but all links seem to be broken.
None of the links are broken when I try them.
Try 4) or 5) to report a bug in the Trac system.
I would assume the OP thinks the three month old SSL cert expiry warnings means broken links. I can see the point. I tried reminding boost-steering about this again recently, still no movement
I understand your frustration with this. I'm equally frustrated. I sent another slew of emails last week. We don't control that server and so at the moment all we can keep doing is ask politely. michael -- Michael Caisse ciere consulting ciere.com
On 15 Jun 2015 at 8:21, Michael Caisse wrote:
I would assume the OP thinks the three month old SSL cert expiry warnings means broken links. I can see the point. I tried reminding boost-steering about this again recently, still no movement
I understand your frustration with this. I'm equally frustrated. I sent another slew of emails last week. We don't control that server and so at the moment all we can keep doing is ask politely.
So I was semi-right that nobody has access to root anymore. Wow. Thanks for telling us Michael. None of us knew what was going on other than "it's being handled" which tells us nothing about the delay. Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/
On 06/15/2015 08:27 AM, Niall Douglas wrote:
On 15 Jun 2015 at 8:21, Michael Caisse wrote:
I would assume the OP thinks the three month old SSL cert expiry warnings means broken links. I can see the point. I tried reminding boost-steering about this again recently, still no movement
I understand your frustration with this. I'm equally frustrated. I sent another slew of emails last week. We don't control that server and so at the moment all we can keep doing is ask politely.
So I was semi-right that nobody has access to root anymore. Wow.
Thanks for telling us Michael. None of us knew what was going on other than "it's being handled" which tells us nothing about the delay.
Niall
Actually, I'm not sure about that. It might be behind a load-balancer as far as I know (though I doubt it). I simply know that the administrator needs to install the certs. With some luck, this wont be a problem (one way or another) for much longer. -- Michael Caisse ciere consulting ciere.com
participants (4)
-
Edward Diener -
Michael Caisse -
Michele Borassi -
Niall Douglas