Cannot decode images from Structurizr AWS 2020 theme

[ad737079]

Currently if you try to use the AWS 2020 theme from https://docs.structurizr.com/ui/diagrams/themes every diagram that uses a AWS image generates incorrectly with the following error in place of each logo:

(Cannot decode: https://static.structurizr.com/themes/amazon-web-services-2020.04.30/AWS-Cloud_light-bg@4x.png)

This does not happen with the 2022 and 2023 themes, so I assume its something to do with the @ symbol thats been added to the image paths within the theme definition as this isn't present in the other themes.

Can reproduce by using any of the theme tags in a DSL and running generate-site, e.g.:

deploymentNode "AWS" { tags "Amazon Web Services - Cloud" }

[jenspav]

Do you have a minimal but complete model at hand which easily reproduces this issue?

[ad737079]

Yes, using the default Structurizr Example:

workspace "Test" "A test" {
    model {
        u = person "User"
        ss = softwareSystem "Software System" {
            wa = container "Web Application"
            db = container "Database Schema" {
                tags "Amazon Web Services - Cloud"
            }
        }
    }

    views {
        properties {
            "generatr.site.exporter" "structurizr"
        }

        container ss "Diagram2" {
            include *
            autolayout lr
        }

        themes default https://static.structurizr.com/themes/amazon-web-services-2020.04.30/theme.json
    }
}

Results in:

[jenspav]

Thanks for the example! Looks like the diagram generation itself went fine, the error is baked in into the svg/png. So it doesn't look like our issue. Running your example at https://structurizr.com/dsl , I can reproduce this there with the planuml and C4-plantuml export (I've added view property "c4plantuml.tags" "true" for that).

Could you please open an issue at https://github.com/structurizr/java/tree/master/structurizr-export and report it there as well?

[ad737079]

Done - structurizr/themes#17

[ad737079]

Now fixed upstream, closing this issue.

[jenspav]

Thanks for the heads-up!