reporting a bug (named container)

0 votes
asked Apr 2, 2016 in Bug by anonymous
I didn't know how to report a bug.

The following work fine for me

@startuml
component   {
[script1]
[script2]
}
@enduml
but if you name the component it fails

i.e.

@startuml
component test  {
[script1]
[script2]
}
@enduml
 

results in

Exception java.lang.IllegalStateException: Cannot find color #000005
net.sourceforge.plantuml.cucadiagram.UnparsableGraphvizException: java.lang.IllegalStateException: Cannot find color #000005
    at net.sourceforge.plantuml.svek.CucaDiagramFileMakerSvek2.createFile(CucaDiagramFileMakerSvek2.java:237)
    at net.sourceforge.plantuml.svek.CucaDiagramFileMakerSvek.createFileInternal(CucaDiagramFileMakerSvek.java:108)
    at net.sourceforge.plantuml.svek.CucaDiagramFileMakerSvek.createFile(CucaDiagramFileMakerSvek.java:81)
    at net.sourceforge.plantuml.cucadiagram.CucaDiagram.exportDiagramInternal(CucaDiagram.java:318)
    at net.sourceforge.plantuml.UmlDiagram.exportDiagram(UmlDiagram.java:229)
    at net.sourceforge.plantuml.PSystemUtils.exportDiagramsCuca(PSystemUtils.java:206)
    at net.sourceforge.plantuml.PSystemUtils.exportDiagrams(PSystemUtils.java:69)
    at net.sourceforge.plantuml.SourceFileReader.getGeneratedImages(SourceFileReader.java:210)
    at net.sourceforge.plantuml.Run.manageFileInternal(Run.java:394)
    at net.sourceforge.plantuml.Run.processArgs(Run.java:316)
    at net.sourceforge.plantuml.Run.manageAllFiles(Run.java:291)
    at net.sourceforge.plantuml.Run.main(Run.java:135)
Caused by: java.lang.IllegalStateException: Cannot find color #000005
    at net.sourceforge.plantuml.svek.DotStringFactory.getClusterIndex(DotStringFactory.java:417)
    at net.sourceforge.plantuml.svek.DotStringFactory.solve(DotStringFactory.java:389)
    at net.sourceforge.plantuml.svek.CucaDiagramFileMakerSvek2.createFile(CucaDiagramFileMakerSvek2.java:226)
    ... 11 more
 

The same problem occurs with package, cloud or other containers

1 Answer

0 votes
answered Apr 2, 2016 by plantuml (295,000 points)

Hi,

Thanks for the report.

This is usually due to some Graphviz issue.

Which version are you using ?

You can test it like this:

@startuml
testdot
@enduml

More info on http://plantuml.com/graphvizdot.html

Regards,

commented Apr 2, 2016 by anonymous
it is not that simple.  As I mentioned the first example worked fine.
The "testdot" resulted in a png with statement where I set GRAPVIZ_DOT to [path]/bin/dot
Dot executable same as above
The graphvis version 2.38.0 (20140413.2041)
Installation seems OK file generation OK
I built graphvis from source.
I downloaded plantum.jar as well as built from source (623 trunk)
Both see to have the same problem.
commented Apr 2, 2016 by plantuml (295,000 points)
If you build graphviz yourself, please make sure that you have built it with libexpat library. This is usually the cause of "Cannot find color" issue.

And this will explain why your first diagram is working, and not the second : PlantUML is using HTML label for the second diagram (the "test" label), and GraphViz needs libexpat to parse this HTML label.

Hopes this help!
...