Cryptic not reproduceable error on `daily`

In one of my many test runs of incus-compose I have seen this incus error on daily:

    05:07 WRN Result with error action=ensure kind=network name=default incus_name=ic-gsobe3evwy created=false error="creating network \"default\": Failed to setup firewall: Failed adding network \"ic-gsobe3evwy\" to the managed bridges set: Failed apply nftables config: Failed to run: nft -f -: exit status 1 (/dev/stdin:4:9-9: Error: syntax error, unexpected <, expecting '{'\nchain in<no value>ic-gsobe3evwy {\n        ^\n/dev/stdin:5:2-5: Error: syntax error, unexpected type\n\ttype filter hook input priority 0; policy accept;\n\t^^^^\n/dev/stdin:5:37-42: Error: syntax error, unexpected policy\n\ttype filter hook input priority 0; policy accept;\n\t                                   ^^^^^^\n/dev/stdin:7:2-8: Error: syntax error, unexpected iifname\n\tiifname \"ic-gsobe3evwy\" tcp dport 53 accept\n\t^^^^^^^\n/dev/stdin:8:2-8: Error: syntax error, unexpected iifname\n\tiifname \"ic-gsobe3evwy\" udp dport 53 accept\n\t^^^^^^^\n/dev/stdin:13:10-10: Error: syntax error, unexpected <, expecting string or last\nchain out<no value>ic-gsobe3evwy {\n         ^\n/dev/stdin:14:2-5: Error: syntax error, unexpected type\n\ttype filter hook output priority 0; policy accept;\n\t^^^^\n/dev/stdin:14:38-43: Error: syntax error, unexpected policy\n\ttype filter hook output priority 0; policy accept;\n\t                                    ^^^^^^\n/dev/stdin:16:2-8: Error: syntax error, unexpected oifname\n\toifname \"ic-gsobe3evwy\" tcp sport 53 accept\n\t^^^^^^^\n/dev/stdin:17:2-8: Error: syntax error, unexpected oifname\n\toifname \"ic-gsobe3evwy\" udp sport 53 accept\n\t^^^^^^^)"
    05:07 ERR Ensuring resources project=teste2euprecreate incus_project=teste2euprecreate error="unknown: network(ic-gsobe3evwy): creating network \"default\": Failed to setup firewall: Failed adding network \"ic-gsobe3evwy\" to the managed bridges set: Failed apply nftables config: Failed to run: nft -f -: exit status 1 (/dev/stdin:4:9-9: Error: syntax error, unexpected <, expecting '{'\nchain in<no value>ic-gsobe3evwy {\n        ^\n/dev/stdin:5:2-5: Error: syntax error, unexpected type\n\ttype filter hook input priority 0; policy accept;\n\t^^^^\n/dev/stdin:5:37-42: Error: syntax error, unexpected policy\n\ttype filter hook input priority 0; policy accept;\n\t                                   ^^^^^^\n/dev/stdin:7:2-8: Error: syntax error, unexpected iifname\n\tiifname \"ic-gsobe3evwy\" tcp dport 53 accept\n\t^^^^^^^\n/dev/stdin:8:2-8: Error: syntax error, unexpected iifname\n\tiifname \"ic-gsobe3evwy\" udp dport 53 accept\n\t^^^^^^^\n/dev/stdin:13:10-10: Error: syntax error, unexpected <, expecting string or last\nchain out<no value>ic-gsobe3evwy {\n         ^\n/dev/stdin:14:2-5: Error: syntax error, unexpected type\n\ttype filter hook output priority 0; policy accept;\n\t^^^^\n/dev/stdin:14:38-43: Error: syntax error, unexpected policy\n\ttype filter hook output priority 0; policy accept;\n\t                                    ^^^^^^\n/dev/stdin:16:2-8: Error: syntax error, unexpected oifname\n\toifname \"ic-gsobe3evwy\" tcp sport 53 accept\n\t^^^^^^^\n/dev/stdin:17:2-8: Error: syntax error, unexpected oifname\n\toifname \"ic-gsobe3evwy\" udp sport 53 accept\n\t^^^^^^^)"
    main_test.go:205:
                Error Trace:    /home/runner/incus-compose/cmd/incus-compose/main_test.go:205
                Error:          Received unexpected error:
                                Logged error: unknown: network(ic-gsobe3evwy): creating network "default": Failed to setup firewall: Failed adding network "ic-gsobe3evwy" to the managed bridges set: Failed apply nftables config: Failed to run: nft -f -: exit status 1 (/dev/stdin:4:9-9: Error: syntax error, unexpected <, expecting '{'
                                chain in<no value>ic-gsobe3evwy {
                                        ^
                                /dev/stdin:5:2-5: Error: syntax error, unexpected type
                                        type filter hook input priority 0; policy accept;
                                        ^^^^
                                /dev/stdin:5:37-42: Error: syntax error, unexpected policy
                                        type filter hook input priority 0; policy accept;
                                                                           ^^^^^^
                                /dev/stdin:7:2-8: Error: syntax error, unexpected iifname
                                        iifname "ic-gsobe3evwy" tcp dport 53 accept
                                        ^^^^^^^
                                /dev/stdin:8:2-8: Error: syntax error, unexpected iifname
                                        iifname "ic-gsobe3evwy" udp dport 53 accept
                                        ^^^^^^^
                                /dev/stdin:13:10-10: Error: syntax error, unexpected <, expecting string or last
                                chain out<no value>ic-gsobe3evwy {
                                         ^
                                /dev/stdin:14:2-5: Error: syntax error, unexpected type
                                        type filter hook output priority 0; policy accept;
                                        ^^^^
                                /dev/stdin:14:38-43: Error: syntax error, unexpected policy
                                        type filter hook output priority 0; policy accept;
                                                                            ^^^^^^
                                /dev/stdin:16:2-8: Error: syntax error, unexpected oifname
                                        oifname "ic-gsobe3evwy" tcp sport 53 accept
                                        ^^^^^^^
                                /dev/stdin:17:2-8: Error: syntax error, unexpected oifname
                                        oifname "ic-gsobe3evwy" udp sport 53 accept
                                        ^^^^^^^)
                Test:           TestE2EUpRecreate/up_simple-nginx

I run tests so the CI’s CPU is at around 50% of all cores. Maybe @stgraber you have a clue and maybe it helps you something, if not ignore.

Looks like a failure, maybe a race around the new logic to allow for network to network traffic to not be NAT-ed.

This <no value> seems a go template thing?