Cardinal/Songbird CORS error

General information

SDK version: 3.85.3
Environment: Sandbox
Browser and OS MacOS 11.4 Chrome 102.0.5005.61

Issue description
Cardinal is throwing CORS errors. This is irrespective of site environment - happens locally as well as on server environments.
We have made no changes to config/code recently so the error seems pretty random.
Really unsure how to even begin to resolve this.
ccess to XMLHttpRequest at 'https://centinelapistag.cardinalcommerce.com/V1/Order/JWT/Init' from origin 'http://localhost:3001' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
next-dev.js?6283:25 Base.GeneralUtility: unexpected Exception: "Connectivity Error"
window.console.error @ next-dev.js?6283:25
overrideMethod @ react_devtools_backend.js:4026
n.cerror @ 5.a960453caa80548c4a43.songbird.js:1
n.sendLogItemsConsole @ 5.a960453caa80548c4a43.songbird.js:1
i.sendBatch @ 5.a960453caa80548c4a43.songbird.js:1
i.log @ 5.a960453caa80548c4a43.songbird.js:1
t.log @ 5.a960453caa80548c4a43.songbird.js:1
t.error @ 5.a960453caa80548c4a43.songbird.js:1
logRouter @ 5.a960453caa80548c4a43.songbird.js:1
h @ 5.a960453caa80548c4a43.songbird.js:1
handleError @ 5.a960453caa80548c4a43.songbird.js:7
(anonymous) @ 10.a960453caa80548c4a43.songbird.js:1
M @ 5.a960453caa80548c4a43.songbird.js:7
k @ 5.a960453caa80548c4a43.songbird.js:7
L @ 5.a960453caa80548c4a43.songbird.js:7
_ @ 5.a960453caa80548c4a43.songbird.js:7
Z @ 5.a960453caa80548c4a43.songbird.js:7
characterData (async)
(anonymous) @ 5.a960453caa80548c4a43.songbird.js:7
W @ 5.a960453caa80548c4a43.songbird.js:7
N @ 5.a960453caa80548c4a43.songbird.js:7
(anonymous) @ 5.a960453caa80548c4a43.songbird.js:7
handleError @ 5.a960453caa80548c4a43.songbird.js:12
s.xhr.s.xhr.onerror @ 5.a960453caa80548c4a43.songbird.js:12
error (async)
sendRequest @ 5.a960453caa80548c4a43.songbird.js:12
i @ 5.a960453caa80548c4a43.songbird.js:1
s @ 5.a960453caa80548c4a43.songbird.js:1
process @ 10.a960453caa80548c4a43.songbird.js:1
(anonymous) @ 5.a960453caa80548c4a43.songbird.js:54
window.songbirdLoader @ songbird.js:1
(anonymous) @ 10.a960453caa80548c4a43.songbird.js:1
5.a960453caa80548c4a43.songbird.js:12          POST https://centinelapistag.cardinalcommerce.com/V1/Order/JWT/Init net::ERR_FAILED

I can confirm we see the same error for the last couple of hours.

We are also facing the same issue.

Facing the same issue with our sandbox environment. With drop-in UI for card verification.

Blocked on testing a few use cases and release due to this issue. Please fix this on priority.

Same issue, it looks like this is due https://centinelapistag.cardinalcommerce.com/V1/Order/JWT/Init responding HTTP 520, so it might be up to CardinalCommerce to fix whatever breakage/outage they are having.

$ curl -I https://centinelapistag.cardinalcommerce.com/V1/Order/JWT/Init
HTTP/2 520
date: Fri, 17 Jun 2022 12:25:04 GMT
content-length: 0
cache-control: no-store, no-cache
cf-cache-status: DYNAMIC
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=%2Fuxl0wyGXdiySD5klbBuMK3y%2FRKMscFqNNAji1HdcaBJMYCwdQAxL%2FcynihoV%2F13MDbpHEtXBIA0nwQRccQB6ex9AqHJ2%2BPpdH6OosCDVPF8G8Q85SLUL0IQ2rw4ajSMfTr9DQJ0pdicqcwqsB5ONqU15xfU9w%3D%3D"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
server: cloudflare
cf-ray: 71cbc40c196741b6-AMS

Closing due to inactivity and because it seems related specifically to CardinalCommerce.


Scroll-able volume rocker

Is your feature request related to a problem? Please describe.
I always need to drag the volume bar, which takes time and is imprecise if I want to be fast (loud song, etc.)

Describe the solution you'd like
It would be great if that music bar would be scroll-able.
Scrolling up is volume up, scrolling down is volume down.
This should only work when hovering over the volume rocker (the current "hit-box").
Additional context
Something handy would also be that you'd be able to set (in the settings) how big the interval is of each scroll.

That is a great idea.
I also found it annoying to always drag the slider whenever I wanted to change the volume of the app.
I recently added a keyboard shortcut to overcome this issue and this option will also help.
I will also be adding this feature in a future release.

Confirmed


upgrade ovn database schema

Closes USHIFT-153
Signed-off-by: Zenghui Shi<EMAIL_ADDRESS>

closing in favor of https://github.com/openshift/microshift/pull/821


Add Flathub/Flatpak method of installation

It may sound like a strange request, but ncspot already has a package on Flathub, and it is a good way for installing it in immutable distros like openSUSE MicroOS and Fedora Silverblue.

Hi, I don't maintain the installation packages, but hopefully someone can take a look and add one.

@aome510
I'm doing a Flatpak myself and while I still can't make it work (it runs, but it still breaks somehow).
What about an icon? I did this https://files.catbox.moe/wfhy7i.svg

I still can't make it work (it runs, but it still breaks somehow).

Can you elaborate how it breaks?

What about an icon? I did this https://files.catbox.moe/wfhy7i.svg

Looks good. ty

Why make a Flatpak for a TUI application?

Close this issue as the project doesn't provide support for maintaining build file for installing from external package managers. Feel free to make a PR to update the README if the support is added.


Caddy ignoring mounted Caddyfile - falling back to default

Hi there. I am running into an issue where caddy-docker is ignoring the Caddyfile I have mounted at /etc/Caddyfile, and instead serving the welcome page over port 2015.
I have verified this by:

docker exec'ing into the container
catting /etc/Caddyfile and verifying that it matches the file I am trying to mount
curling localhost:2015 and seeing the welcome message

Version: 1.0.3
Host OS: Ubuntu Server 18
Logs:
Sep 15 05:58:06 casa systemd[1]: Started Caddy static site and reverse proxy.
Sep 15 05:58:08 casa caddy[4748]: Activating privacy features... done.
Sep 15 05:58:08 casa caddy[4748]: Serving HTTP on port 2015
Sep 15 05:58:08 casa caddy[4748]: http://:2015

I have tried this with a number of different Caddyfiles, including examples from Caddy documentation, so I don't believe it's an issue with any particular caddyfile

Did you check to see if your configured page was reachable on another port?  Not sure why, but my config works in addition to the default page.  I just don't really allow any traffic to hit that port, and I'm good.

Did you check to see if your configured page was reachable on another port? Not sure why, but my config works in addition to the default page. I just don't really allow any traffic to hit that port, and I'm good.

Sorry for the delay, yes, I'm certain that it is only serving traffic on port 2015.

Can you run "docker inspect <YOUR_CADDY_CONTAINER_ID>" and post the results?

[
    {
        "Id": "18216d5cc478496f8cc87cdeaeba28fd1b161b3d37c2504026693a8c27f871ff",
        "Created": "2019-10-08T04:40:32.818267264Z",
        "Path": "/bin/parent",
        "Args": [
            "caddy",
            "-ca",
            "https://acme-staging-v02.api.letsencrypt.org/directory"
        ],
        "State": {
            "Status": "running",
            "Running": true,
            "Paused": false,
            "Restarting": false,
            "OOMKilled": false,
            "Dead": false,
            "Pid": 6859,
            "ExitCode": 0,
            "Error": "",
            "StartedAt": "2019-10-08T04:40:34.386296443Z",
            "FinishedAt": "0001-01-01T00:00:00Z"
        },
        "Image": "sha256:7b7636ac875d205d9b30b52a0eb9f8db65998524b393338786f27d9f33766e41",
        "ResolvConfPath": "/var/lib/docker/containers/18216d5cc478496f8cc87cdeaeba28fd1b161b3d37c2504026693a8c27f871ff/resolv.conf",
        "HostnamePath": "/var/lib/docker/containers/18216d5cc478496f8cc87cdeaeba28fd1b161b3d37c2504026693a8c27f871ff/hostname",
        "HostsPath": "/var/lib/docker/containers/18216d5cc478496f8cc87cdeaeba28fd1b161b3d37c2504026693a8c27f871ff/hosts",
        "LogPath": "",
        "Name": "/caddy",
        "RestartCount": 0,
        "Driver": "overlay2",
        "Platform": "linux",
        "MountLabel": "",
        "ProcessLabel": "",
        "AppArmorProfile": "docker-default",
        "ExecIDs": null,
        "HostConfig": {
            "Binds": [
                "/home/web/config/Caddyfile:/etc/Caddyfile",
                "/home/web/ssl:/root/.caddy:rw",
                "/home/web/static:/www:ro"
            ],
            "ContainerIDFile": "",
            "LogConfig": {
                "Type": "none",
                "Config": {}
            },
            "NetworkMode": "default",
            "PortBindings": {
                "443/tcp": [
                    {
                        "HostIp": "",
                        "HostPort": "8443"
                    }
                ],
                "80/tcp": [
                    {
                        "HostIp": "",
                        "HostPort": "8080"
                    }
                ]
            },
            "RestartPolicy": {
                "Name": "no",
                "MaximumRetryCount": 0
            },
            "AutoRemove": true,
            "VolumeDriver": "",
            "VolumesFrom": null,
            "CapAdd": null,
            "CapDrop": null,
            "Capabilities": null,
            "Dns": [],
            "DnsOptions": [],
            "DnsSearch": [],
            "ExtraHosts": null,
            "GroupAdd": null,
            "IpcMode": "private",
            "Cgroup": "",
            "Links": null,
            "OomScoreAdj": 0,
            "PidMode": "",
            "Privileged": false,
            "PublishAllPorts": false,
            "ReadonlyRootfs": false,
            "SecurityOpt": null,
            "UTSMode": "",
            "UsernsMode": "",
            "ShmSize": 67108864,
            "Runtime": "runc",
            "ConsoleSize": [
                0,
                0
            ],
            "Isolation": "",
            "CpuShares": 0,
            "Memory": 0,
            "NanoCpus": 0,
            "CgroupParent": "",
            "BlkioWeight": 0,
            "BlkioWeightDevice": [],
            "BlkioDeviceReadBps": null,
            "BlkioDeviceWriteBps": null,
            "BlkioDeviceReadIOps": null,
            "BlkioDeviceWriteIOps": null,
            "CpuPeriod": 0,
            "CpuQuota": 0,
            "CpuRealtimePeriod": 0,
            "CpuRealtimeRuntime": 0,
            "CpusetCpus": "",
            "CpusetMems": "",
            "Devices": [],
            "DeviceCgroupRules": null,
            "DeviceRequests": null,
            "KernelMemory": 0,
            "KernelMemoryTCP": 0,
            "MemoryReservation": 0,
            "MemorySwap": 0,
            "MemorySwappiness": null,
            "OomKillDisable": false,
            "PidsLimit": null,
            "Ulimits": null,
            "CpuCount": 0,
            "CpuPercent": 0,
            "IOMaximumIOps": 0,
            "IOMaximumBandwidth": 0,
            "MaskedPaths": [
                "/proc/asound",
                "/proc/acpi",
                "/proc/kcore",
                "/proc/keys",
                "/proc/latency_stats",
                "/proc/timer_list",
                "/proc/timer_stats",
                "/proc/sched_debug",
                "/proc/scsi",
                "/sys/firmware"
            ],
            "ReadonlyPaths": [
                "/proc/bus",
                "/proc/fs",
                "/proc/irq",
                "/proc/sys",
                "/proc/sysrq-trigger"
            ]
        },
        "GraphDriver": {
            "Data": {
                "LowerDir": "/var/lib/docker/overlay2/c5f3ed1394a4bfe48c73158a08ff2c781aa012c9468aaf7b0b4bc4d62f95132f-init/diff:/var/lib/docker/overlay2/4c51bdf03ef34902ec15d5872e84b1de8552cf122bfcbd3498e69af8736f57b2/diff:/var/lib/docker/overlay2/ae9bc8dd773bf03ed6103955054f528aeb05f24733f4c3ce6ec974d569bfbeeb/diff:/var/lib/docker/overlay2/0af867539402602da3747dbcd206b48e4d607879171727950fad5600ffd0f56c/diff:/var/lib/docker/overlay2/df0a6eb2708f662c74fb78776c321f8b8a20abe0e5f126575b1e9e985677386a/diff:/var/lib/docker/overlay2/eee6392fd2f5b66aea396e5fceb413f519e9630034be003c7247dd452feb8837/diff:/var/lib/docker/overlay2/5b0b806f83372daf0fb9193947db13f446c3c3d284d42771dd331f22902a0e1a/diff:/var/lib/docker/overlay2/a562e47c54dae6b75b81a2d6246953c458a5f3d80ef445f07e05045b32071a99/diff",
                "MergedDir": "/var/lib/docker/overlay2/c5f3ed1394a4bfe48c73158a08ff2c781aa012c9468aaf7b0b4bc4d62f95132f/merged",
                "UpperDir": "/var/lib/docker/overlay2/c5f3ed1394a4bfe48c73158a08ff2c781aa012c9468aaf7b0b4bc4d62f95132f/diff",
                "WorkDir": "/var/lib/docker/overlay2/c5f3ed1394a4bfe48c73158a08ff2c781aa012c9468aaf7b0b4bc4d62f95132f/work"
            },
            "Name": "overlay2"
        },
        "Mounts": [
            {
                "Type": "volume",
                "Name": "a02e2e9baab7154c0d0c253f8f3216d1b2b456dd1f6c19a59507d7ef80c4018f",
                "Source": "/var/lib/docker/volumes/a02e2e9baab7154c0d0c253f8f3216d1b2b456dd1f6c19a59507d7ef80c4018f/_data",
                "Destination": "/srv",
                "Driver": "local",
                "Mode": "",
                "RW": true,
                "Propagation": ""
            },
            {
                "Type": "bind",
                "Source": "/home/web/config/Caddyfile",
                "Destination": "/etc/Caddyfile",
                "Mode": "",
                "RW": true,
                "Propagation": "rprivate"
            },
            {
                "Type": "bind",
                "Source": "/home/web/ssl",
                "Destination": "/root/.caddy",
                "Mode": "rw",
                "RW": true,
                "Propagation": "rprivate"
            },
            {
                "Type": "bind",
                "Source": "/home/web/static",
                "Destination": "/www",
                "Mode": "ro",
                "RW": false,
                "Propagation": "rprivate"
            }
        ],
        "Config": {
            "Hostname": "18216d5cc478",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": true,
            "AttachStderr": true,
            "ExposedPorts": {
                "2015/tcp": {},
                "443/tcp": {},
                "80/tcp": {}
            },
            "Tty": false,
            "OpenStdin": false,
            "StdinOnce": false,
            "Env": [
                "ACME_AGREE=true",
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
                "ENABLE_TELEMETRY="
            ],
            "Cmd": [
                "-ca",
                "https://acme-staging-v02.api.letsencrypt.org/directory"
            ],
            "Image": "abiosoft/caddy:1.0.3",
            "Volumes": {
                "/root/.caddy": {},
                "/srv": {}
            },
            "WorkingDir": "/srv",
            "Entrypoint": [
                "/bin/parent",
                "caddy"
            ],
            "OnBuild": null,
            "Labels": {
                "caddy_version": "1.0.3",
                "maintainer": "Abiola Ibrahim<EMAIL_ADDRESS>            }
        },
        "NetworkSettings": {
            "Bridge": "",
            "SandboxID": "3c3e2518f9e74fe94fda809af8f07735dcf2611974bc868a99e8a0fc37c04bd3",
            "HairpinMode": false,
            "LinkLocalIPv6Address": "",
            "LinkLocalIPv6PrefixLen": 0,
            "Ports": {
                "2015/tcp": null,
                "443/tcp": [
                    {
                        "HostIp": "<IP_ADDRESS>",
                        "HostPort": "8443"
                    }
                ],
                "80/tcp": [
                    {
                        "HostIp": "<IP_ADDRESS>",
                        "HostPort": "8080"
                    }
                ]
            },
            "SandboxKey": "/var/run/docker/netns/3c3e2518f9e7",
            "SecondaryIPAddresses": null,
            "SecondaryIPv6Addresses": null,
            "EndpointID": "b9b1f2537a03957bd171d949ef7bc894c20db2ac5708fb30a4a2571e52be7fad",
            "Gateway": "<IP_ADDRESS>",
            "GlobalIPv6Address": "",
            "GlobalIPv6PrefixLen": 0,
            "IPAddress": "<IP_ADDRESS>",
            "IPPrefixLen": 16,
            "IPv6Gateway": "",
            "MacAddress": "02:42:ac:11:00:02",
            "Networks": {
                "bridge": {
                    "IPAMConfig": null,
                    "Links": null,
                    "Aliases": null,
                    "NetworkID": "7d470b673e2fee46657c5cdd53b493e00d966eae0797d44615383ae7d41ed8e0",
                    "EndpointID": "b9b1f2537a03957bd171d949ef7bc894c20db2ac5708fb30a4a2571e52be7fad",
                    "Gateway": "<IP_ADDRESS>",
                    "IPAddress": "<IP_ADDRESS>",
                    "IPPrefixLen": 16,
                    "IPv6Gateway": "",
                    "GlobalIPv6Address": "",
                    "GlobalIPv6PrefixLen": 0,
                    "MacAddress": "02:42:ac:11:00:02",
                    "DriverOpts": null
                }
            }
        }
    }
]

Can we see a Caddyfile you’re trying to use? Everything looks good there, especially since you said the Caddyfile inside the container is readable, and matches what’s on the host.
Did you try curl-ing localhost on https/8443, and http/8080?  Looks like that’s where you have 80, and 443 mapped.

Yep, I'm curling 8443 and 8080.
Current Caddyfile (though I've tried with other, simpler caddyfiles as well):
(common) {
    tls<EMAIL_ADDRESS>    gzip
}

typokign.com {
    import common
    redir https://www.typokign.com{uri}
}

www.typokign.com {
    import common
    root /www
}

matrix.typokign.com {
    import common
    proxy / localhost:10080
}

riot.typokign.com {
    import common
    proxy / localhost:10080
}

mail.typokign.com {
    import common
    proxy / localhost:11080
}

Okay, I think I see the problem now. Have you tried curl-ing and setting
the Host header?  Like this:
curl http://localhost:2015 -H “Host: www.typokign.com”

Everything might be on 2015 right now because you didn’t specify a port in
your Caddyfile.  Consequently, without specifying the host header, you get
the default Caddy page.  Explicitly add the port you want each directive to
serve, and add the host header, and you should be good.
On Fri, Oct 11, 2019 at 21:31 David Cruz<EMAIL_ADDRESS>wrote:

Yep, I'm curling 8443 and 8080.
Current Caddyfile (though I've tried with other, simpler caddyfiles as
well):
(common) {
tls<EMAIL_ADDRESS>gzip
}
typokign.com {
import common
redir https://www.typokign.com{uri}
}
www.typokign.com {
import common
root /www
}
matrix.typokign.com {
import common
proxy / localhost:10080
}
riot.typokign.com {
import common
proxy / localhost:10080
}
mail.typokign.com {
import common
proxy / localhost:11080
}
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/abiosoft/caddy-docker/issues/218?email_source=notifications&email_token=ACDPSB5OKS567FROMDYJPETQOESFZA5CNFSM4IWZKVU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBBR33Y#issuecomment-541269487,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACDPSB4RW5SQYUXJ433RQMDQOESFZANCNFSM4IWZKVUQ
.

Okay, I think I see the problem now. Have you tried curl-ing and setting
the Host header?  Like this:
curl http://localhost:2015 -H “Host: www.typokign.com”

Everything might be on 2015 right now because you didn’t specify a port in
your Caddyfile.  Consequently, without specifying the host header, you get
the default Caddy page.  Explicitly add the port you want each directive to
serve, and add the host header, and you should be good.

Thanks, I've added the ports but I am still only serving the default page on port 2015:
(common) {
    tls<EMAIL_ADDRESS>    gzip
}

:8080 {
    redir https://{host}{uri}:8443
}

https://typokign.com:8443 {
    import common
    redir https://www.typokign.com:8443{uri}
}

https://www.typokign.com:8443 {
    import common
    root /www
}

https://matrix.typokign.com:8443 {
    import common
    proxy / localhost:10080
}

https://riot.typokign.com:8443 {
    import common
    proxy / localhost:10080
}

https://mail.typokign.com:8443 {
    import common
    proxy / localhost:11080
}

The only thing that could explain that is that there's an error in your Caddyfile and Caddy just quits reading after it sees it (which seems unlikely given you've tried simpler Caddyfiles, and that's not Caddy's style), or the Caddyfile you've defined isn't actually mounted, and readable inside your container.  I wish I could say this was something Caddy was messing up, but I've deployed this container inside three production networks and I've never had Caddy ignore my Caddyfile.
Just to clarify, here's how I'd troubleshoot (run these inside the Caddy container):

ls -al /etc/Caddyfile: should show that the file is readable at least by the user that Caddy is running as ( rw-r--r-- or something similar)
cat /etc/Caddyfile: should show the same Caddyfile as outside the container.

Making sure that every time you make a change how you're configuring your container, you check those two things.  You can't change the config and then restart Caddy inside the container (unless you use some sort of non-standard entry point).  The container's life depends on Caddy running.  If Caddy is restarted, the container goes away.
How are you deploying the container?  Just locally? Swarm? Compose?  Can we see how you're starting the container?

Commands in container:
~ # ls -al /etc/Caddyfile
-r--------    1 root     root           504 Oct 14 23:57 /etc/Caddyfile
~ # whoami
root
~ # cat /etc/Caddyfile
(common) {
    tls<EMAIL_ADDRESS>    gzip
}

:8080 {
    redir https://{host}{uri}:8443
}

https://typokign.com:8443 {
    import common
    redir https://www.typokign.com:8443{uri}
}

https://www.typokign.com:8443 {
    import common
    root /www
}

https://matrix.typokign.com:8443 {
    import common
    proxy / localhost:10080
}

https://riot.typokign.com:8443 {
    import common
    proxy / localhost:10080
}

https://mail.typokign.com:8443 {
    import common
    proxy / localhost:11080
}
~ #

I am deploying the container with a systemd unit that simply docker runs the container.

Also, it might be a bit late for this, but a single node swarm is probably a much more canonical way to get this going.  Then you could declare your Caddyfile as a config, and use a named volume for your certs.
docker swarm init
docker service create caddy ... (see service command help for all the details)

Systemd doesn’t care if your container dies, swarm does.

Logs get piped straight to journald. This is kind of an old box with a lot of non-dockerized services managed by systemd so I'd like to keep things consistent.

Hmm, well, the only other thing that I could think of is that Caddy is not running as root. Sure you exec into the container as root, but that doesn’t necessarily mean caddy ran as root. Can you do a ps -ef inside the container?

It could also be some weird cgroup permission thing since you’re actually running the container from the system slice. Perhaps, since you exec in from the user slice, you’re able to read the Caddyfile, but otherwise the “service” doesn’t have access? It’s a bit of a reach, but docker does it’s own cgroup isolation that is maybe interfering with what the system is also doing.
If you’re super against swarm, you could always use —restart=aways in your Docker run command.  That will take care of reboots, and service failures.  Then, caddy will go up/down along with docker. It would then eliminate any potential issues with cgroup permissions.

/srv # ps -ef
PID   USER     TIME  COMMAND
    1 root      0:00 /bin/parent caddy -ca https://acme-staging-v02.api.letsencrypt.org/directory
   13 root      0:00 /usr/bin/caddy -ca https://acme-staging-v02.api.letsencrypt.org/directory
   31 root      0:00 /bin/sh
   36 root      0:00 ps -ef

Adding --restart=always to the run command and removing --rm didn't work.

Wasn’t suggesting that would fix it exactly. Was suggesting that perhaps the fact that it’s kicked off in a service slice might be making things weird.
If you stop the caddy “service”, and run the container manually, does that work?

Ah ha! I've made an important discovery. Launching the container with the -ca flag, either as a user or from systemd, causes Caddy to fall back to the default Caddyfile. Omitting it causes Caddy to correctly parse the Caddyfile! :tada:
However, looking in journald I am now hanging on this line:
2019/10/16 05:58:41 [INFO][typokign.com] Obtain certificate

Caddy is unresponsive on all ports. I've modified my Caddyfile to run on standard ports 80/443:
(common) {
    tls<EMAIL_ADDRESS>    gzip
}

:80 {
    redir https://{host}{uri}:443
}

https://typokign.com {
    import common
    redir https://www.typokign.com{uri}
}

https://www.typokign.com {
    import common
    root /www
}

https://matrix.typokign.com {
    import common
    proxy / localhost:10080
}

https://matrix.typokign.com:8448 {
    import common
    proxy / localhost:10448
}

https://riot.typokign.com {
    import common
    proxy / localhost:10080
}

https://mail.typokign.com {
    import common
    proxy / localhost:11080
}

And I've modified the docker run args to reflect the new ports. Any idea why Caddy would be hanging on obtaining a cert?
Thank you!

Nevermind, not sure what broke but I just removed the lock file and everything seems to be working. Thanks for all of your help @paullj1 . Thread closed.


[dynamic-dns] Cloudflare Invalid TTL when updating DNS

Describe the bug
Performing a force-update on my Cloudflare DNS domains gives the following errors:
opnsense: /services_dyndns_edit.php: Dynamic DNS (example.com): PAYLOAD: { "result": null, "success": false, "errors": [ { "code": 9021, "message": "Invalid TTL. Must be between 120 and 2,147,483,647 seconds, or 1 for automatic" } ], "messages": [] }

Expected behavior
Domains to be updated with new IP address
Environment
OPNsense 19.7.9

I have updated the dyndns plugin to use the (not so) new token based authentification and to set TTL.
#1726

Done.


support either tx hashes or full details; output tx input data in various formats

This PR adds a -tx flag to the block command, and an -input flag to the block and tx commands.
OPTIONS:
   --tx value     Transaction format: count/hash/detail (default: "count")
   --input value  Transaction input data format: len/hex/utf8 (default: "len")

Before this change, only transaction hashes were fetched with blocks, only the count was displayed in the human readable output, and input data was always left out. Now the user may choose whether to display block transactions as count, hash, or detail - the default is count (the pre-existing behavior). For hash and detail, each tx is printed on a line following its index in the block (detail works with -format json as well). Users may also choose whether to display tx input data as len, hex, or utf8 - the default is len.
Definitely open to name and/or format suggestions. The hash output is nice and clean:
...
MixDigest: 0x0000000000000000000000000000000000000000000000000000000000000000
Signer: 0x1d6dd30512ca935f36273c39fcdaa196fbe3d303ddb2f37ecf780f8fde8b69c13bbbe23c84d42fad47e90ef1429e4753bc96555d7c84791b466660a6d17a001800
Transaction Hashes:
	0	0x1055efe6b8e4c6c085914ff5986f5cef8973d814b0a895c1ff4afbe309a66028
	1	0x5e69f2e0510a11d039a9b022ee166b6459589bb39cdc033e9f7909d432f29307
	2	0x1f843b26d4457efab7c4ae2afc52b6000d4f934995369fcf22411c7745e09542
	3	0xfed8884a3f5ae311a4734409fea2ae387a6d18e73012764096abf6b44d36a72e
...

But the detail output is sort of dense (worse when it wraps):
...
Signer: 0xbf071fedb259bef7901004f66a2b7823bbe4c618d0028409c8d350cb4b90c5d631f46e84ba75e2863a81c8ea78dcdde3bf712f8f0728de01b6adae7ebda0259f00
Transaction Details:
	0	Hash: 0x1528e6509469b0abaef9351379cadb86e7fbf277ee58ba48e5534934daae9bd9 From: 0xF320A60c650Ce54697B4D6a232B31358bb7Dd427 To: 0xa23f8A7cEDd53Ee90460baa7d4654Dc9457DB505 Value: 0.000000000000000017GO Nonce: 92181 Gas Limit: 201734 Gas Price: 3.581222517 gwei Input: 0x
	1	Hash: 0xb6255abd8c96d69ec96dae7ed696887f2c92627cfc558145b04ddea50adb1704 From: 0xdfc947AB6E5aed846c8b71C9EE327fc30f6008d6 To: 0xE0D92301d90B9D1BBED7FEe2660Ca57536cE1c52 Value: 0.000000000000000010GO Nonce: 9092 Gas Limit: 308845 Gas Price: 3.350911431 gwei Input: 0x
	2	Hash: 0x16fa5b613146531a85003ab02ef417d6396692593ed76346e340e376bd031f96 From: 0xdfc947AB6E5aed846c8b71C9EE327fc30f6008d6 To: 0x18b7f4fE91dd484B53392236b3376696eF057Af0 Value: 0.000000000000000019GO Nonce: 9093 Gas Limit: 203146 Gas Price: 3.873731163 gwei Input: 0x
	3	Hash: 0x88aac9b2239a20f0c9ccab2c756c423a32cb692a241cf684b9193364fda729ae From: 0xdfc947AB6E5aed846c8b71C9EE327fc30f6008d6 To: 0xF6522549115D74453B8C751238E56B34c62af54f Value: 0.000000000000000014GO Nonce: 9094 Gas Limit: 293005 Gas Price: 3.567985475 gwei Input: 0x
...

it looks better than it was


TypeLoadException could not find type in dll file

Hi, I have this error while generating the OpenAPI documentation for my project in Azure Devops pipeline.
Since the Domain.TrackerVersion is located in another project in the same solution, how can I add it to myproject.dll so that it won't complain about not finding the object in the XML?
Thanks
This is the exception I got :
POST /api/tracker/updateorcreate || ExceptionType: TypeLoadException || Message: Type "Domain.TrackerVersion" could not be found. Ensure that it exists in one of the following assemblies: myproject.dll Newtonsoft.Json.dll

Please raise tooling-related issues on the relevant repository. This repository is for the OpenAPI specification itself. You may also receive more answers on a general support forum such as StackOverflow. Thanks.


bump node to v20

fix deprecation message
via: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions uses Node.js version which is deprecated and will be forced to run on node20<EMAIL_ADDRESS>
For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

/cc @DaAnda97 @lmoesle @alex-praschek @dominikhorn93

thank you!


chore: fixed typos and updated README to use proper function arguments

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[ ] It's really useful if your PR references an issue where it is discussed ahead of time.
[X] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[X] Run the tests with npm run test and lint the project with npm run lint and npm run prettier

@Secreto31126 I'll sign the commits and create separate PR in some time.
Thanks!

Don't worry about the signatures, it's a me thing.
Thanks for opening the PR!


Response to #80

Since you keep closing the conversation i have to reopen new issues once again. I would have preferred a single issue to discuss arguments. Anyway, feel free to block everybody who has some contra arguments, if this is your way of handling things.

Answer on #80:
I am sorry, i have to disagree. I a spinner does not indicate progress. It only indicates activity. Hence it is name ActivityIndicator, e.g. in Apple's UIKit. The is no way of telling or guess how much progress in made from a simple spinning view. Nor is it a bar either.
Have a good one.

  This is my project.  These are my opinions.    I've reported you to GitHub and blocked you completely.  The time you spent worried about this issue you could actually have made some meaningful contributions to open source.


Move compiler error (usually SyntaxError) error message handling to error augmentation

Before the change compiler errors (usually SyntaxError) had their message modified in the compiler, with the line number added to the error message. The compiler would do this by catching the error, modifying it, and rethrowing it. The downside of this is that a debugger Throw notify won't see the line number in the error message because the message hasn't been modified on the first throw.
This pull request change the message modification to happen in ordinary error augmentation. This is a slight change in behavior if error augmentation is disabled, because compiler error messages won't then have a line number.

Is there a reason the line number isn't just added at the original throw site in the compiler?

While it'd be possible to change all the call sites in the compiler, note that the line number is added to any error thrown during compilation. That means the call site can be e.g. in a duk_require_hstring() called by the compiler, or anywhere else inside Duktape.


Shall we skip Python 2.7 support?

Description
Supporting only Python 3.x makes the code easier to maintain. In OWSLib we have already done this step.
What is your opinion?

I agree. Python 2.7 is now being dropped from most Linux distributions, pretty soon no one will use it any more.
Let us keep the discussion open for now and have a PSC vote later in the month. Hopefully there will be quorum during FOSS4G.

Motion: get rid of Python 2 support for PyWPS 4.3 (future 4.4) branch

[ ] @cehbrecht
[ ] @jachym
[ ] @ldesousa
[ ] @tomkralidis
[ ] @jonas-eberle
[ ] @jorgejesus

done, thank you all


A document must not include more than one “meta” element with a “charset” attribute.

Versions

nuxt: "nuxt": "2.14.12", => problem
node: v12.20.0 -->

"nuxt": "2.14.5", => no problem
Reproduction
I think the minimum scenario to reproduce is:

use last version of nuxt
nuxt generate (reproduced in static generated app)
inspect  they should be 2 of them.

it's needed, my repo: https://github.com/trollepierre/recontact_travel_blog/tree/dev/front
https://github.com/trollepierre/recontact_travel_blog/blob/dev/front/nuxt.config.js
Steps to reproduce
I think the minimum scenario to reproduce is:

use last version of nuxt
nuxt (reproduce in yarn dev, and in static generated app)
inspect  they should be 2 of them.

What is Expected?
I expect to see only one meta charset and no html5-validator error
What is actually happening?
there are 2 meta charset div in my html
this one needs to be removed:

ok! thanks you solved my issue!

Rather than creating a new bug report, in Nuxt3 I am experiencing similarly two instances of meta charset appearing in ./pages/index.vue
See discord server message starting at https://discord.com/channels/473401852243869706/897487139888062506/955710568453521428
In Nuxt3's nuxt.config.ts, with contents:
import { defineNuxtConfig } from 'nuxt3';

export default defineNuxtConfig({
  meta: {
    meta: [
      { charset: 'latin-1' } // not utf-8, but better shows which one is added from the script
    ]
  },
})

then the html source appears as:
<meta charset="utf-8"><meta charset="latin-1">

apparently Nuxt3 is injecting utf-8 always from somewhere else.

Oh, I just noticed this report is closed, and I can't find a way to open it. Oh well.

@jasonkhanlar Issues for Nuxt 3 should be raised at https://github.com/nuxt/framework.
This particular issue comes from upstream: see https://github.com/vueuse/head/issues/32.


Using Redis Stack and Pool Feature

Hi, I was facing some trouble using Redis Stack and the pool features provided by this package. Is there any example or sample code where I can learn how to use those features of this package?
Thank you.

Hi @tehsunnliu,
The pool documentation is here with an example
https://docs.rs/rustis/latest/rustis/client/index.html#the-pooled-client-manager
About RedisStack, like any other high level commands, it is available in the commands module where commands are gathered in differents traits implemented by the Client struct:
https://docs.rs/rustis/latest/rustis/commands
You will find RedisStack documentation on the different specific traits, for instance JsonCommands for RedisJson
Examples can be found in the test suite:
https://github.com/dahomey-technologies/rustis/blob/main/src/tests.
Each specific command trait should be tested here.
Which part of RedisStack do you want to use ?
I may help you on specific questions

Consider also using the multiplexed client instead of the pool.

Thank you so much @mcatanzariti for your reply and the sources you have provided. It's really helpful.
I'm trying to add the Redis Stack feature to the rocket_auth crate which currently supports MySQL, PostgreSQL, and SQLite. And uses Redis only for caching. Since I, recently came to know that Redis also supports Permanent data storage so I thought it will be a good time to learn Redis Stack and also implement this feature on the rocket_auth crate.

Don't hesitate if I can help you further


Building and training  a RoutingTransformerEncDec from pre-trained RoutingTransformerLMs

I am trying to build and train an encoder-decoder from pretrained routing transformer LMs. The way I approached it was to replace the encoder and decoder in a RoutingTransformerEncDec with the pre-trained RoutingTransformerLMs as follows:
enc_dec.enc=pretrained_lm
enc_dec.dec=AutoregressiveWrapper(pretrained_lm)

and then try to train the enc_dec as normal when I get the following error:
RuntimeError                              Traceback (most recent call last)
<ipython-input-9-681d3315d6dc> in <module>
    147         grad_accum_steps=1,
    148         temperature=1,
--> 149         model_suffix=''
    150
    151     )

~/projects/trlabs_routing_transformer/routing_sum/train_and_eval.py in train_routing_single(epoch, model, tokenizer, train_chunk_bucket, val_data_bucket, model_dir, optimizer, lr, max_seq_len, pred_target_len, src_pad_len, tgt_pad_len, max_src_len, max_tgt_len, log_interval, eval_interval, save_interval, train_logger, global_step, grad_accum_steps, temperature, model_suffix)
    469         train_seq_out = padded_target[:, :max_seq_len].to(device)
    470         loss, aux_loss = model(train_seq_in, train_seq_out, return_loss=True)
--> 471         loss.backward()
    472         aux_loss.backward()
    473         train_loss += loss.item()

~/anaconda3/envs/routing/lib/python3.6/site-packages/torch/tensor.py in backward(self, gradient, retain_graph, create_graph)
    196                 products. Defaults to ``False``.
    197         """
--> 198         torch.autograd.backward(self, gradient, retain_graph, create_graph)
    199
    200     def register_hook(self, hook):

~/anaconda3/envs/routing/lib/python3.6/site-packages/torch/autograd/__init__.py in backward(tensors, grad_tensors, retain_graph, create_graph, grad_variables)
     98     Variable._execution_engine.run_backward(
     99         tensors, grad_tensors, retain_graph, create_graph,
--> 100         allow_unreachable=True)  # allow_unreachable flag
    101
    102

RuntimeError: new kmeans has not been supplied

I would appreciate any feedback on what may be the problem or what is the best way to build an enc_dec from pretrained LM checkpoints.

@AliOskooeiTR Hi Ali, it is tricky because in the encoder / decoder setting, the hook for updating the kmeans must be moved from the individual transformers to the EncDec class, as shown https://github.com/lucidrains/routing-transformer/blob/master/routing_transformer/encoder_decoder.py#L78 Let me work on this later this weekend and see if there is a clean way to do this

@AliOskooeiTR also, as shown https://github.com/lucidrains/routing-transformer/blob/master/routing_transformer/encoder_decoder.py#L59

@AliOskooeiTR if you want to try version 1.4.3, this should fix it
enc.cancel_kmeans_update()  # cancel kmeans update for enc and dec
dec.cancel_kmeans_update()

encdec.enc = enc
encdec.dec = dec

encdec.register_kmeans_update() # reregister kmeans

@lucidrains  I tried this:
`pretrained_lm.cancel_kmeans_update()  # cancel kmeans update for enc and dec
enc_dec.enc = pretrained_lm
enc_dec.dec = AutoregressiveWrapper(pretrained_lm)
enc_dec.register_kmeans_update() # reregister kmeans`
And unfortunately I still get the same error:
RuntimeError: new kmeans has not been supplied

@AliOskooeiTR ohh, I see the problem, I don't think you can use the same pretrained LM for both encoder and decoder. Instead of doing it that way, why not do something like
enc_dec.enc.load_state_dict(pretrained_lm.state_dict())
enc_dec.dec.load_state_dict(pretrained_lm.state_dict())

@lucidrains Thanks for the suggestion. I tried this:
enc_dec.enc.load_state_dict(pretrained_lm.state_dict())
enc_dec.dec.load_state_dict(pretrained_lm.state_dict())

It would give me missing key error as the state dict keys for enc_dec.enc and pretrained_lm were different. Surprisingly even the number of keys were quite different. I did not understand how this could be since enc_dec.enc and pretrained_lm are both RoutingTransformerLMs.
I then replaced encdec state dicts entirely just to see what happens:
pretrained_lm.cancel_kmeans_update()
pretrained_dec = AutoregressiveWrapper(pretrained_lm)
enc_dec.enc.state_dict=pretrained_lm.state_dict
enc_dec.dec.state_dict=pretrained_dec.state_dict
enc_dec.register_kmeans_update()

This gave me the same kmeans error:
RuntimeError: new kmeans has not been supplied

Just closing this issue as I have sorted out why it wasn't possible to use the same LM for both the encoder and the decoder. The decoder LM must receive context and be causal. This results in the encoder having a different architecture and state dictionary and not exchangeable with the encoder LM.


get_grandpa_justification is returning None

Hey,
get_grandpa_justification method provided by the client is returning None api.get_grandpa_justification(signed_block.block.header.number). Though I can access it using polkadot.js

Just to make sure: The block you're accessing via api.get_grandpa_justification(signed_block.block.header.number) does contain a grandpa justification? Depending on your substrate node settings, only every xth block contains a justification.
Example of a block with a justification:

(Rococo Block Nr 1,313,373:
https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frococo-rpc.polkadot.io#/explorer/query/0x0e37ea669c7f20b7d989532220da5ce2fc762c9a888f6104bee9972420deb54d)

@zktony is this still a problem?

Closing this as answered for now. Please reopen if it's still a problem.


Adding npx commands for testing

Adding npx commands for CDK operations to prevent breaking the service during testing.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.pclata seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


attempt to solve problem with video list ids being out of sync

when stored as a widget and accessed at a later date
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] I have read the CONTRIBUTING document.

All Submissions:

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Changes to Core Features:

[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you successfully ran tests with your changes locally?

@asciidisco  Sorry the second commit was not meant to come into this PR. It adds a retry decorator which I used to fix: https://github.com/asciidisco/plugin.video.netflix/issues/196
I hope that does not cause too much issues and they can be reviewed together.

@hawkeyexp - If you get a chance please try and review this PR. Cheers :)

I'm trying out now :-) But i noticed we will get a merge conflict if gtechalpha's pr will me merged.

@hawkeyexp Please do not merge it now.

Thanks, yeah that was my fear when left for too long a period...the changes are not too complicated though so should be easy enough to merge or I can resubmit based on gtechalpha's PR once completed

@asciidisco merging is your part of work lol - i will only merge small things/fixes -no big code related stuff :-)

Thanks @hawkeyexp it’s my most used feature as I like to have my next up list on the home screen. @asciidisco if you want to merge the conflicts that’s fine or let me know if you’d like me to resubmit after you pull in the other PR. Cheers

@im85288 I´m going to merge some big chunk of refactored code most probably on Sunday, going to merge your PR during that merge session as well. Sorry for the delay.

Thanks @asciidisco - hopefully it should be straight forward but let me know if there’s anything confusing

@asciidisco - I attempted to merge these changes with master but now it does not seem to work. Has there been changes with regards caching the List ID used? Is this something I should try on the refactor branch instead as something has definitely changed. Thanks

It turns out this was down to it picking out the incorrect user when auto login is enabled (my last test was with only one user). The above change assures the profile is set at the start for all routing calls and prevents it from being called each time the addon is opened to show the user list/genres etc

@asciidisco - what's happening with this PR?

This can be closed, as it has been implemented in #300

Has been implemented in #300


Failed to serialize the input pipeline graph: PyFunc is stateful. [Op:DatasetToGraphV2]

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
OS Platform and Distribution (e.g., Linux Ubuntu 20.04):
TensorFlow installed from (source or binary): binary build from branch 2.3.0
TensorFlow version (use command below): 2.3.0
Python version: 3.8.5
Bazel version (if compiling from source): 3.1.0
CUDA/cuDNN version: 11.1, 8.0.4
GPU model and memory: Nvidia GeForce 1060 6Gb

Describe the current behavior
I am using a custom model that inherits from tf.Module. Also for some logic I am using tf-addons==0.11.2
Everything trains ok, without problem, however when I am using tf.saved_model.save(custom_model, path) I get the error below in logs section.
I found this issue after tensorflow update 2.1.0 source to 2.3.0 binary.
Standalone code to reproduce the issue
Below is my train code:
import tensorflow as tf
import tensorflow_addons as tfa

class NERTrainer(tf.Module):
    ..........
    def _helpers_(self):
        pass
    ..........
    def train(self):
        ix = 0
        for words, chars, labels, sentence_lengths in self._training_dataset:
            with tf.GradientTape() as tape:
                embeddings = self._add_embeddings_transformations(words, chars, ix)
                logits = self._add_logits(embeddings, ix)
                labels = tf.cast(labels, tf.int32)
                sentence_lengths = tf.cast(sentence_lengths, tf.int32)

                log_likelihood, transition_parameters = tfa.text.crf_log_likelihood(
                    logits, labels, sentence_lengths
                )
                log_likelihood = tf.reduce_mean(-log_likelihood)
            gradients = tape.gradient(log_likelihood, self._trainables)
            self.optimizer.apply_gradients(zip(gradients, self._trainables))
            ix += 1

        self._transition_parameters = tf.constant(transition_parameters.numpy())
        scores = self._run_evaluation(train_dataset=False)
        return {'avg_f1': np.mean(scores['f1'])}

if '__name__' == '__main__':
    nn_trainer = NERTrainer()
    num_epochs = 10
    for ix in range(num_epochs):
            print('Epoch #{}'.format(ix))
            logger.info('Epoch #{}'.format(ix))

            nn_trainer.train()
            nn_trainer.lr *= nn_trainer.lr_decay

            tf.saved_model.save(nn_trainer, target_save_path)

Other info / logs Include any logs or source code that would be helpful to
All logs while training:
2020-11-11 14:21:33.948277: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcuda.so.1
2020-11-11 14:21:33.948441: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-11-11 14:21:33.948969: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1716] Found device 0 with properties:
pciBusID: 0000:0a:00.0 name: GeForce GTX 1060 6GB computeCapability: 6.1
coreClock: 1.8095GHz coreCount: 10 deviceMemorySize: 5,93GiB deviceMemoryBandwidth: 178,99GiB/s
2020-11-11 14:21:33.948983: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudart.so.11.1
2020-11-11 14:21:33.950141: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcublas.so.11
2020-11-11 14:21:33.950597: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcufft.so.10
2020-11-11 14:21:33.950717: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcurand.so.10
2020-11-11 14:21:33.951851: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcusolver.so.11
2020-11-11 14:21:33.952087: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcusparse.so.11
2020-11-11 14:21:33.952157: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudnn.so.8
2020-11-11 14:21:33.952243: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-11-11 14:21:33.952820: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-11-11 14:21:33.953190: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1858] Adding visible gpu devices: 0
2020-11-11 14:21:33.953398: I tensorflow/core/platform/cpu_feature_guard.cc:142] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN)to use the following CPU instructions in performance-critical operations:  SSE3 SSE4.1 SSE4.2 AVX AVX2 FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2020-11-11 14:21:33.980819: I tensorflow/core/platform/profile_utils/cpu_utils.cc:104] CPU Frequency:<PHONE_NUMBER> Hz
2020-11-11 14:21:33.981555: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x791e0e0 initialized for platform Host (this does not guarantee that XLA will be used). Devices:
2020-11-11 14:21:33.981578: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): Host, Default Version
2020-11-11 14:21:34.038911: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-11-11 14:21:34.039310: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x78fa260 initialized for platform CUDA (this does not guarantee that XLA will be used). Devices:
2020-11-11 14:21:34.039330: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): GeForce GTX 1060 6GB, Compute Capability 6.1
2020-11-11 14:21:34.039561: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-11-11 14:21:34.040024: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1716] Found device 0 with properties:
pciBusID: 0000:0a:00.0 name: GeForce GTX 1060 6GB computeCapability: 6.1
coreClock: 1.8095GHz coreCount: 10 deviceMemorySize: 5,93GiB deviceMemoryBandwidth: 178,99GiB/s
2020-11-11 14:21:34.040053: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudart.so.11.1
2020-11-11 14:21:34.040099: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcublas.so.11
2020-11-11 14:21:34.040122: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcufft.so.10
2020-11-11 14:21:34.040141: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcurand.so.10
2020-11-11 14:21:34.040160: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcusolver.so.11
2020-11-11 14:21:34.040178: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcusparse.so.11
2020-11-11 14:21:34.040196: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudnn.so.8
2020-11-11 14:21:34.040286: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-11-11 14:21:34.040790: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-11-11 14:21:34.041208: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1858] Adding visible gpu devices: 0
2020-11-11 14:21:34.041240: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudart.so.11.1
2020-11-11 14:21:34.268942: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1257] Device interconnect StreamExecutor with strength 1 edge matrix:
2020-11-11 14:21:34.268983: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1263]      0
2020-11-11 14:21:34.268992: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1276] 0:   N
2020-11-11 14:21:34.269251: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-11-11 14:21:34.269571: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-11-11 14:21:34.269829: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1402] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 5006 MB memory) -> physical GPU (device: 0, name: GeForce GTX 1060 6GB, pci bus id: 0000:0a:00.0, compute capability: 6.1)
Epoch #0
2020-11-11 14:21:34.496695: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudnn.so.8
2020-11-11 14:21:34.824964: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcublas.so.11
2020-11-11 14:22:03.651363: W tensorflow/python/util/util.cc:348] Sets are not currently considered sequences, but this may change in the future, so consider avoiding using them.
Traceback (most recent call last):
  File "ner.py", line 358, in <module>
    tf.saved_model.save(nn_trainer, target_save_path)
  File "/home/kirill/.local/lib/python3.8/site-packages/tensorflow/python/saved_model/save.py", line 975, in save
    _, exported_graph, object_saver, asset_info = _build_meta_graph(
  File "/home/kirill/.local/lib/python3.8/site-packages/tensorflow/python/saved_model/save.py", line 1061, in _build_meta_graph
    _ = _SaveableView(checkpoint_graph_view)
  File "/home/kirill/.local/lib/python3.8/site-packages/tensorflow/python/saved_model/save.py", line 216, in __init__
    function._list_all_concrete_functions_for_serialization())  # pylint: disable=protected-access
  File "/home/kirill/.local/lib/python3.8/site-packages/tensorflow/python/eager/def_function.py", line 1030, in _list_all_concrete_functions_for_serialization
    concrete_functions = self._list_all_concrete_functions()
  File "/home/kirill/.local/lib/python3.8/site-packages/tensorflow/python/eager/def_function.py", line 1012, in _list_all_concrete_functions
    self.get_concrete_function()
  File "/home/kirill/.local/lib/python3.8/site-packages/tensorflow/python/eager/def_function.py", line 1167, in get_concrete_function
    concrete = self._get_concrete_function_garbage_collected(*args, **kwargs)
  File "/home/kirill/.local/lib/python3.8/site-packages/tensorflow/python/eager/def_function.py", line 1073, in _get_concrete_function_garbage_collected
    self._initialize(args, kwargs, add_initializers_to=initializers)
  File "/home/kirill/.local/lib/python3.8/site-packages/tensorflow/python/eager/def_function.py", line 696, in _initialize
    self._stateful_fn._get_concrete_function_internal_garbage_collected(  # pylint: disable=protected-access
  File "/home/kirill/.local/lib/python3.8/site-packages/tensorflow/python/eager/function.py", line 2855, in _get_concrete_function_internal_garbage_collected
    graph_function, _, _ = self._maybe_define_function(args, kwargs)
  File "/home/kirill/.local/lib/python3.8/site-packages/tensorflow/python/eager/function.py", line 3213, in _maybe_define_function
    graph_function = self._create_graph_function(args, kwargs)
  File "/home/kirill/.local/lib/python3.8/site-packages/tensorflow/python/eager/function.py", line 3065, in _create_graph_function
    func_graph_module.func_graph_from_py_func(
  File "/home/kirill/.local/lib/python3.8/site-packages/tensorflow/python/framework/func_graph.py", line 986, in func_graph_from_py_func
    func_outputs = python_func(*func_args, **func_kwargs)
  File "/home/kirill/.local/lib/python3.8/site-packages/tensorflow/python/eager/def_function.py", line 600, in wrapped_fn
    return weak_wrapped_fn().__wrapped__(*args, **kwds)
  File "/home/kirill/.local/lib/python3.8/site-packages/tensorflow/python/training/tracking/tracking.py", line 262, in _creator
    resource = self._create_resource()
  File "/home/kirill/.local/lib/python3.8/site-packages/tensorflow/python/data/ops/dataset_ops.py", line 205, in <lambda>
    lambda: weak_self._trace_variant_creation()()),  # pylint: disable=unnecessary-lambda,protected-access
  File "/home/kirill/.local/lib/python3.8/site-packages/tensorflow/python/data/ops/dataset_ops.py", line 277, in _trace_variant_creation
    self._as_serialized_graph(external_state_policy=distribute_options
  File "/home/kirill/.local/lib/python3.8/site-packages/tensorflow/python/util/deprecation.py", line 507, in new_func
    return func(*args, **kwargs)
  File "/home/kirill/.local/lib/python3.8/site-packages/tensorflow/python/data/ops/dataset_ops.py", line 248, in _as_serialized_graph
    return gen_dataset_ops.dataset_to_graph_v2(
  File "/home/kirill/.local/lib/python3.8/site-packages/tensorflow/python/ops/gen_dataset_ops.py", line 1122, in dataset_to_graph_v2
    _ops.raise_from_not_ok_status(e, name)
  File "/home/kirill/.local/lib/python3.8/site-packages/tensorflow/python/framework/ops.py", line 6843, in raise_from_not_ok_status
    six.raise_from(core._status_to_exception(e.code, message), None)
  File "<string>", line 3, in raise_from
tensorflow.python.framework.errors_impl.FailedPreconditionError: Failed to serialize the input pipeline graph: PyFunc is stateful. [Op:DatasetToGraphV2]

I see this error the first time. Didn't find something similar.
Could you help me with this issue please?

@Ecclesiast
I ran the code shared it has syntax errors and is not indented, please find the gist here. could you please share indented code such that we could replicate the issue or is possible share a colab gist with the error.


chore: add askpt to org

@askpt has helped with numerous .NET issues. They:

removed the Moq lib: (here and here)
added the readme to the nuget package here.
deprecated the OTel hook, and implemented the metrics hook.

@askpt please comment-on or :+1: this PR to signal your interest!

Thank you for the invitation @toddbaert 😄

Welcome aboard @askpt


Error: The specified module could not be found.

Tried running the control-gallery example on OS X which works without issues, but attempting to run it on Windows 7 results in an error:
module.js:568
  return process.dlopen(module, path._makeLong(filename));
                 ^

Error: The specified module could not be found.
\\?\node_modules\libui-node\build\Release\nbind.node
    at Error (native)
    at Object.Module._extensions..node (module.js:568:18)
    at Module.load (module.js:458:32)
    at tryModuleLoad (module.js:417:12)
    at Function.Module._load (module.js:409:3)
    at Module.require (module.js:468:17)
    at require (internal/module.js:20:19)
    at initNode (node_modules\libui-node\node_modules\nind\dist\nbind.js:162:15)
    at node_modules\libui-node\node_modules\nbind\dist\bind.js:130:13
    at findCompiledModule (node_modules\libui-node\nodemodules\nbind\dist\nbind.js:94:13)

EDIT: Found the problem. It's having issues finding libui.dll and copying the file from node_modules/libui-node to the root of the script fixed it and it now works fine. Don't know if there's any better solution to this...

Hi @KraXarN, thank you for the report.
You got some kind of error during the copy process of the dll?
Where exactly did you place the dll to make it work?
It should work from node_modules/libui-node, if it doesn't it means there is some problem on the loading phase on Windows.

Hello. Sorry for the long delay, forgot to reply. :/
Here's the full log of the install. I can't find any information of it copying the dll file, so maybe that's the issue.
If the folder where the script is I'm trying to run, containing my code is the root, the dll was placed in /node_modules/libui-node/libui.dll and I had to copy it to /libui.dll for it to work. If the dll isn't in that location and in the node_modules folder, that errors pops up upon starting my script.

I had this exact problem as well. Windows 10 Pro v1607. Node v6.6.0. Npm v 3.10.8
I was banging my head against this for a while until I found this issue. Any ideas why this is happening?

Just go with my solution for now :p

Same here, Windows 8.1. The copy dll did the trick, thanks @KraXarN !

I have the same issue :( . What I did:

clone repo
run npm -S i
npm start

...
module.js:598
  return process.dlopen(module, path._makeLong(filename));
                 ^

Error: The specified module could not be found.
\\?\C:\cygwin64\home\user\libui-node\nbind.node
    at Object.Module._extensions..node (module.js:598:18)
    at Module.load (module.js:488:32)
  ...

But in my case there are both nbind.node and libui.dll in cwd.

Windows 8.1
node 7.5.0
npm 4.1.2

Could you upload somewhere prebuilt demo that can be run out of the box.

Same here
nbind.node isn't copied to node_modules/libui-node/

Next version (that will be coming next weeks) will solve the problem.
In the meanwhile, @kusti8 solve it to use it in proton-native here: https://github.com/kusti8/libui-node/blob/master/copy_node.js

nbind.node isn't copied to node_modules/libui-node/

now it is (#62)

When installing libui-node on Mac OS there was an error.
Error: Could not locate the bindings file. Tried:
/usr/local/bin/libui-node/nbind.node
solution
sudo cp /usr/local/bin/node_modules/libui-node/nbind.node /usr/local/bin/libui-node/nbind.node
Now you can run the examples in examples
$ node /examples/grid.js
Simon


Tag/release a new version

There have been lots of changes since 0.7.2

+1. I need parsers to be exported.

0.7.3 published. :) Sorry about that.

:+1:

Is there a new version ready for release? It seems there have been a few changes since 0.7.3, and the source in my node_modules is quite different from the Github repo.
For example, I've noticed that #117 was fixed, the middleware patterns may have changed (resulting in my confusion in #119), and the README was also changed, as a result.


How to put initial value on page load?

you can put them in the state and initialize them in the constructor

Can I see your sample code for it? There's no sample in the readme file. Thank you.

go check the example folder, I don't think you read all the readme and missed the last sentence but we all do that ¯_(ツ)_/¯

TypeError: statRef.select is not a function. (In 'statRef.select(0)', 'statRef.select' is undefined)

`
useEffect(() => {
if (isVisible) {
console.log(statRef.select(0));
}
}, [isVisible]);
<TagGroup
ref={statRef}
source={[
"All",
"Created",
"Processing",
"Reassigned",
"Resolved",
]}
onSelectedTagChange={(selected) => {
//console.log(statRef);
setSearchStatus(selected);
}}
singleChoiceMode={true}
tagStyle={{
height: 35,
borderWidth: 1,
borderColor: CONSTANTS.TEXT_COLOR,
}}
textStyle={{
alignItems: "center",
alignContent: "center",
padding: 4,
}}
activeTagStyle={{
borderColor: CONSTANTS.PRIMARY_COLOR,
backgroundColor: CONSTANTS.PRIMARY_COLOR,
}}
activeTextStyle={{ color: "white" }}
/>`

if you want to create refs of a component do it like this ref={component => this.refName = component}, I'd recommend you to read the react doc

Thank you for your help. For future reference, here's how I solved it.


Is MouseEvent's button() broken?

I have been trying to handle right click on a canvas but right click doesn't seem to be triggered for some reason! The code below works for left click only.

let cl = Closure::wrap(Box::new(move |e: Event|{
  let btn = e.dyn_into::<MouseEvent>().unwrap().button();
  log!("{}", btn);
  if btn == 0 {
     log!("Left Click");
  } else if btn == 2 {
    log!("Right Click");
  }
}) as Box<dyn FnMut(_)>);
element.add_event_listener_with_callback(
    "click",
    cl.as_ref().unchecked_ref(),
)
.unwrap();
cl.forget();

Similarly I can't disable context menu using rust
let cl = Closure::wrap(Box::new(move |e: Event|{
    e.prevent_default();

}) as Box<dyn FnMut(_)>);
element.add_event_listener_with_callback(
    "contextmenu",
    cl.as_ref().unchecked_ref(),
)
.unwrap();
cl.forget();

I am resorting to embedding javascript in the html attribute
canvas.set_attribute("oncontextmenu", "event.preventDefault();").unwrap();

This isn't a bug with wasm-bindgen, it's just how browsers work (the same thing happens in JavaScript):
// Doesn't fire for right click
addEventListener("click", function (e) {
    console.log(e.button);
});

The only way to detect right click is with the mousedown, mouseup, or contextmenu events.
As for prevent_default, have you tried setting the contextmenu event on the window?
window().unwrap().add_event_listener_with_callback(
    "contextmenu",
    cl.as_ref().unchecked_ref(),
)
.unwrap();

If that doesn't work, then it's definitely a bug in wasm-bindgen.

Sorry I meant mousedown. My code has mousedown.
I was using a function to add event listener easily without having to type : Closure::wrap(Box::new(move  everytime I add a event listener. My function was internally bound to "click" event when I meant to pass in the event type as a parameter.
 Thanks for your clarification though!
pub fn add_event<H>(el: &HtmlElement, event_type: &str, event_listener: H)
where H: 'static + FnMut(Event) {
    let cl = Closure::wrap(Box::new(event_listener) as Box<dyn FnMut(_)>);
    el.add_event_listener_with_callback("click", cl.as_ref().unchecked_ref())
        .unwrap();
    cl.forget();
}

and I was calling it with "mousedown" which obviously wouldn't work: add_event(&canvas, "mousedown", move |_|{...});

Glad you got it fixed. You should also take a look at gloo, which has an EventListener helper type:
EventListener::new(&canvas, "mousedown", move |_| { ... })

It also handles things like deregistering the event listener when it's no longer needed.
It isn't released yet, but it will be released soon.


Portfolio website has been committed

I have added my portfolio website codes to this repo.
Language used: HTML and CSS

Please merge

Good work. I am merging your PR.
Do give us a star by hitting the star button of this repo!

Thanks a lot


Feature: Make defaults and overrides a first class feature

Until now, defaults were handled during Email construction, assuming defaults values where found in (system) properties (files). This approach worked fine for a long time, but had two disadvantages:

You can only control defaults on a global level, while defaults could be different between multiple Mailer instances, for example because their respective SMTP server had different policies for headers, from address, DKIM domain keys etc.
Programmatic defaults were only possible by managing the ConfigLoader properties directly. A separate step before using Email/Mailer builder API. It works and is relatively easy to do, but doesn't conform to Simple Java Mail's mission statement for a super simple and clean API.
You couldn't make exceptions on a field by field basis. Either you applied all defaults or you ignored them all using emailBuiler.ignoringDefaults().
Some operations were expensive and prohibitive for large scale operations. For example reading and processing a PKCS12 truststore for signing emails with S/MIME.

And of course, there was no capability for defining overrides. Defaults are for missing values, while overrides take precedence in any case.
A recent change alleviated some of these issues, but this this had a focus on performance, which meant only some properties were moved to the Mailer level (specifically S/MIME). That too with dedicated methods on the MailerBuilder, which wouldn't scale well if we were going to have all properties configurable that way. An even more recent change added defaults email instances and even overrides on the Mailer level, but this was a flawed implementation, as the properties from system/files/ConfigLoader were still applied during Email construction and then whatever was programmatically added as default on the Mailer was set during sending.
This issue aims to move all defaults/overrides to the Mailer level, via the existing EmailGovernance object. We're not having a single setXyzByDefault() for every property on the Mailer, but we simply set Email instances as defaults/overrides references on the governance object. If no defaults email is provided, a blank one will be created and populated from the system/files/ConfigLoader sources. This means that all expensive operations are executed only once and all properties are now evaluated only when sending emails. This also means that emails you create initially have no defaults applied and might look empty. You will have more control to have an Email created regularly, or create it with defaults/overrides applied right away (in case if you don't want to send an email, but still want a fully populated email, for example to use as a defaults email reference, or if you just want to use a helper method). And also you will be able to exclude specific properties from being defaulted or overridden. You can model advanced scenarios this way, allowing exceptions on exceptions on exceptions (define property file defaults, overwrite with programmatic defaults, have a specific email ignore a specific default altogether, but then an override can be enabled but also ignored the same way).

Release in 8.0.0. I'm still updating the documentation on simplejavamail.org

Defaults and overrides are now only applied when sending mail, logging mail or delegating mail to a CustomMailer.
This means emailBuilder().build() might not be as populated as you expect. If you need a fully populated email for your own purposes, such as logging, handling or using one of Simple Java Mail's helper methods -but not sending-, you can use emailBuilder.buildEmailCompletedWithDefaultsAndOverrides()
You can set Email instances as defaults or overrides reference using mailerBuilder.withEmailDefaults(Email) or mailerBuilder.withEmailOverrides(Email). All fields can be used.
On Email level, you can set certain fields to be exempt completely from default values or overriding values, using emailBuilder.dontApplyDefaultValueFor(EmailProperty...) or emailBuilder.dontApplyOverrideValueFor(EmailProperty...).
To complete innoculate your Email instance from having defaults or overrides set, use emailBuilder.ignoringDefaults(true) or ignoringOverrides(true), or when you start an email with EmailBuilder.ignoringDefaults() and EmailBuilder.ignoringOverrides().

You can create a new EmailGovernance using new EmailGovernanceImpl(...), but that's unintended. There is a builder missing to this neatly. This will come in 8.0.1.


⚠ Bofrost.be has degraded performance

In 36d4f83, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1097 ms

Resolved: Bofrost.be performance has improved in f202b43 after 1 hour, 16 minutes.


Portfolio Balance updates

I'm deciding to go with a portfolio total function that you can use any base as the total.
As the earlier implementation did, I overall just had a lot of bugs, so I'm refactoring most, but the classes will stay the same.
It will use the total balance of each active pair that doesnt have a balance of 0.0, in whatever base of users choosing.
An example: hedging into different assets for accumulation of said chosen base.

Adding Orderbook options to calculate portfolio total

Ready for unit test @davidagustin


Another video that does not display - not ASLLVD

Here the problem cannot be the lack of an original video...
Results from videos/Tyler-ASLLVD-DOUBT.mp4

But the video is indeed missing on the DAI:

Another one:  WLASL-A-CABBAGE-08535.mp4

This video is also missing in the DAI.

The video for DOUBT-1p  and COOPERATE/UNITE_2 are still missing.

See #399 .  That will fix this.

This is complete on dev1


Reset the whole view of interactive app

While exploring my ABMs, I often find myself updating parameters and resetting the model over and over again. Because of this, I'd like an ability to reset the whole view of the interactive app, i.e. having completely "blank" plots and a fresh view of the space and so on.
This could be done either via a new clear button or by extending the functionality of the existing reset button. Currently reset resets the underlying model to its initial state and draws a red vertical line in the plots after which the new series are drawn. Was this just a temporary workaround or was it a deliberate design decision to never completely clear the plots? Which option would you prefer - a new button or changing how the existing one works? Would love to hear your thoughts on this.

Pretty sure George was thinking that the restart line shows a discontinuation in an effectively infinite exploration. What that doesn't cover in my view, are models that have a clear temporal start and end. I think this is what you're hitting here as well.
I like the red lines for continuous resets, and I think your additional behaviour is welcomed. Best of both worlds makes adding a new button the clear winner.

yeah adding a new clear button is the way to go and thankfully quite simple given the current code. just copy the reset button and make it also make the plotted curves to be  = Point2f0[].


Upgrade k8s libraries to 1.13.0-rc.1

Usually there aren't significantly differences between RCs in k8s so it's better to update the libraries so we can catch possible bugs earlier.
Add support for Kubernetes 1.13

This change is

test-me-please

Coverage decreased (-0.07%) to 43.474% when pulling 1ef421e2e092e86c95ada37fb4051e6655f65fda on pr/upgrade-k8s-1.13 into 38e678d7555f2bc6256803471fef194ca34b66b2 on master.

test-missed-k8s

test-missed-k8s

test-missed-k8s


Appstudio update test-custom-default-branch-fyao

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-opmr-on-pull-request-
creating pipelinerun test-annotations-opmr-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-htcz-on-pull-request-
creating pipelinerun test-annotations-htcz-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-gsnx-on-pull-request-
creating pipelinerun test-simple-build-gsnx-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-ckox-on-pull-request-
creating pipelinerun test-simple-build-ckox-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-andp-on-pull-request-
creating pipelinerun test-annotations-andp-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-nqsa-on-pull-request-
creating pipelinerun test-annotations-nqsa-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-gqbk-on-pull-request-
creating pipelinerun test-annotations-gqbk-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-cvzf-on-pull-request-
creating pipelinerun test-simple-build-cvzf-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-vmcc-on-pull-request-
creating pipelinerun test-annotations-vmcc-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-pcyu-on-pull-request-
creating pipelinerun test-annotations-pcyu-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-qvet-on-pull-request-
creating pipelinerun test-annotations-qvet-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-uwwa-on-pull-request-
creating pipelinerun test-annotations-uwwa-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-kpke-on-pull-request-
creating pipelinerun test-annotations-kpke-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-plnr-on-pull-request-
creating pipelinerun test-annotations-plnr-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-xlnr-on-pull-request-
creating pipelinerun test-annotations-xlnr-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-llgt-on-pull-request-
creating pipelinerun test-annotations-llgt-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-clyb-on-pull-request-
creating pipelinerun test-annotations-clyb-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-lbhf-on-pull-request-
creating pipelinerun test-annotations-lbhf-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-xtci-on-pull-request-
creating pipelinerun test-annotations-xtci-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-taux-on-pull-request-
creating pipelinerun test-simple-build-taux-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-bkgt-on-pull-request-
creating pipelinerun test-annotations-bkgt-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-qlwi-on-pull-request-
creating pipelinerun test-annotations-qlwi-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-bycd-on-pull-request-
creating pipelinerun test-annotations-bycd-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-eukh-on-pull-request-
creating pipelinerun test-annotations-eukh-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-evsa-on-pull-request-
creating pipelinerun test-annotations-evsa-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-onzg-on-pull-request-
creating pipelinerun test-simple-build-onzg-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-izai-on-pull-request-
creating pipelinerun test-annotations-izai-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-pzcq-on-pull-request-
creating pipelinerun test-annotations-pzcq-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-pjiw-on-pull-request-
creating pipelinerun test-annotations-pjiw-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-ylok-on-pull-request-
creating pipelinerun test-simple-build-ylok-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-arvj-on-pull-request-
creating pipelinerun test-simple-build-arvj-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-nycf-on-pull-request-
creating pipelinerun test-simple-build-nycf-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-efea-on-pull-request-
creating pipelinerun test-simple-build-efea-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-jgvv-on-pull-request-
creating pipelinerun test-annotations-jgvv-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-fuha-on-pull-request-
creating pipelinerun test-simple-build-fuha-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-gjnx-on-pull-request-
creating pipelinerun test-annotations-gjnx-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-xtgf-on-pull-request-
creating pipelinerun test-annotations-xtgf-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-yoht-on-pull-request-
creating pipelinerun test-annotations-yoht-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-fohw-on-pull-request-
creating pipelinerun test-annotations-fohw-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-umup-on-pull-request-
creating pipelinerun test-annotations-umup-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-pyqq-on-pull-request-
creating pipelinerun test-annotations-pyqq-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-yjrl-on-pull-request-
creating pipelinerun test-annotations-yjrl-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-xosv-on-pull-request-
creating pipelinerun test-simple-build-xosv-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-mgqw-on-pull-request-
creating pipelinerun test-annotations-mgqw-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-jihl-on-pull-request-
creating pipelinerun test-simple-build-jihl-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-irii-on-pull-request-
creating pipelinerun test-simple-build-irii-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-knyw-on-pull-request-
creating pipelinerun test-simple-build-knyw-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-mbrb-on-pull-request-
creating pipelinerun test-simple-build-mbrb-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-kvjs-on-pull-request-
creating pipelinerun test-simple-build-kvjs-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-ygyv-on-pull-request-
creating pipelinerun test-simple-build-ygyv-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-pmki-on-pull-request-
creating pipelinerun test-simple-build-pmki-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-wfdk-on-pull-request-
creating pipelinerun test-simple-build-wfdk-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-kzfl-on-pull-request-
creating pipelinerun test-simple-build-kzfl-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-kgek-on-pull-request-
creating pipelinerun test-simple-build-kgek-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-acga-on-pull-request-
creating pipelinerun test-annotations-acga-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-phhr-on-pull-request-
creating pipelinerun test-simple-build-phhr-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-wznz-on-pull-request-
creating pipelinerun test-simple-build-wznz-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-gvay-on-pull-request-
creating pipelinerun test-simple-build-gvay-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-izee-on-pull-request-
creating pipelinerun test-simple-build-izee-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-qezd-on-pull-request-
creating pipelinerun test-simple-build-qezd-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-igaw-on-pull-request-
creating pipelinerun test-simple-build-igaw-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-owhs-on-pull-request-
creating pipelinerun test-simple-build-owhs-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-smhg-on-pull-request-
creating pipelinerun test-simple-build-smhg-on-pull-request- in namespace build-e2e-uxve-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request