View Issue Details

IDProjectCategoryView StatusLast Update
0004614mantisbtrelationshipspublic2007-10-04 01:37
Reportermasc Assigned Tovboctor  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
PlatformX86OSWindowsOS VersionWin2K
Product Versiongit trunk 
Fixed in Version1.1.0rc1 
Summary0004614: Relationship graph: sometimes arrows direction is not correct
Description

The bugs 506,507,508 are all child of 472. Looking at the attached images, the relationships graph associated with the 472 bug is different (arrows direction) from the one associated to the bug 507 (all the three arrows should point the 472).

TagsNo tags attached.
Attached Files
right.gif (2,376 bytes)   
right.gif (2,376 bytes)   
wrong.gif (2,577 bytes)   
wrong.gif (2,577 bytes)   
query.gif (9,590 bytes)   
query.gif (9,590 bytes)   
neato-test-2.vbs (577 bytes)

Activities

jferraz

jferraz

2004-09-26 14:09

reporter   ~0007755

Last edited: 2004-09-26 14:11

Hi masc,

This is strange, and I couldn't reproduce it here. Could you please return me the result of

SELECT * FROM mantis_bug_relationship_table
WHERE source_bug_id = 472 OR source_bug_id = 506 OR
source_bug_id = 507 OR source_bug_id = 508 OR
destination_bug_id = 472 OR destination_bug_id = 506 OR
destination_bug_id = 507 OR destination_bug_id = 508
?

Btw, send me a reminder when you find bugs related to the relationship graphs, please.

alterado em: 09-26-04 14:11

masc

masc

2004-09-26 15:27

reporter   ~0007756

Find attached an image with the query result from phpmyadmin.

jferraz

jferraz

2004-09-26 18:01

reporter   ~0007761

Still unsuccessful trying to reproduce this bug. I created bugs with the same numbering as yours, created the same relationships in the same order, and nothing, still perfect.

The problem you are reporting makes me think that some bits in relgraph_generate_rel_graph() got somehow swapped. On the latest CVS, on lines 76-77 and 91-92 there are:

76 $v_rel_list[$t_id][$t_dst] = BUG_DEPENDANT;
77 $v_rel_list[$t_dst][$t_id] = BUG_BLOCKS;
...
91 $v_rel_list[$t_id][$t_dst] = BUG_BLOCKS;
92 $v_rel_list[$t_dst][$t_id] = BUG_DEPENDANT;

What you are reporting suggests that both sections were like
   $v_rel_list[$t_id][$t_dst] = BUG_BLOCKS;
$v_rel_list[$t_dst][$t_id] = BUG_DEPENDANT;

Indeed, I managed to replicate this bug when I made this change, but this is not what was commited to CVS. Can you check this, please?

Another thing: are you using graphviz 1.10 or higher? Is it the Windows version? I just thought it could be a bug in graphviz handling back/forward arrows...

If you could reduce this to a minimum number of entries and export an SQL file with your database with just these issues and relations, I can check better if it is a bug.

masc

masc

2004-09-27 02:44

reporter   ~0007766

I checked the source code and it's as expected. I'm using WinGraphviz 1.02.25 (it was downloaded a couple of days ago, it should be lastest).
In my database I have a lot of bugs with three childs and the resulting graphs are all wrong (when you center the graph in one of the child).
It seems all the arrow are pointed in the direction of the centered bugs. When you change bugs, the directions change accordingly to the new centered bug.

In any case your work is great!

Marcello

jferraz

jferraz

2004-10-08 14:04

reporter   ~0007966

This is another WinGraphviz-specific bug. The attached script should produce a "src" node pointing to two "dst" nodes... WinGraphviz produces something like dst1-->src-->dst2.

I'll contact the author, just like 0004625. I don't know if there is a workaround for this bug... it seems that sometimes it choses random arrow directions, and it looks hard to predict to where they'll point to.

jferraz

jferraz

2004-10-12 12:23

reporter   ~0007994

Four days passed and I received no answer from the author. I'm afraid that he is not maintaining WinGraphviz anymore.

masc

masc

2004-10-20 01:40

reporter   ~0008112

Juliano,
I have discovered a very crazy behaviour in WinGraph.
You have two nodes A and B.
B has already some edges with other nodes.
You would like to add a new edge from A to B ( A->B ) and then set the attributes 'forward'.
It seems and this case (when the B nodes has already other edges) that the forward direction is from B to A ( B->A ). Then to have the right direction it's needed to set the attributes 'back'.
I tried this while developing the states automa graph (new feature) and it works.
Can you have a look to this strage workaround? Perhaps we can implement it just in case of WinGraph use.

player

player

2006-01-30 13:22

reporter   ~0012042

Even in 1.0.0rc5 I have such problem under Windows and WinGraphviz with edge orientation. But after inserting a string "ksort($v_bug_list);" in line 136 in "core/relation_graph_api.php" before cycle
" foreach ( $v_bug_list as $t_id => $t_bug ) {
$t_id_string = bug_format_id( $t_id );
"
all seems OK.

mkornatzki

mkornatzki

2007-09-18 14:50

reporter   ~0015660

thanks, this fix works perfectly

vboctor

vboctor

2007-09-20 02:02

manager   ~0015668

Applied the fix suggested by "player" and confirmed by "mkornatzki" for now. If this break something else then we will undo the change and re-open this issue.