Crashplan Docker container can't connect to server (Synology Firewall issue)

Current Behavior
I've set up the docker container with the image from the registry. When I go to the correct url and port, I'm asked for my email (no where to enter a password). I enter my email and click Continue. Nothing happens. Then after awhile, I get an error:
Unable to sign in. Can't connect to server.
I have my Synology firewall enabled and rules set up for ports 5800, 5900 as well as the associated local ports.
I turned off the firewall and everything works as advertised. So there is something in the container or the firewall rules that is preventing the container from being able to connect with the Crashplan servers.
Does anyone have any ideas about what I may be missing?
Expected Behavior
No response
Steps To Reproduce
No response
Environment
Synology NAS DS918+
DSM7.1.1
Tried multiple browsers
No reverse proxy
Container creation
Installed via image from registry.
Container log
╭――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╮
    │                                                                      │
    │ Application:           CrashPlan for Small Business                  │
    │ Application Version:   11.0.1                                        │
    │ Docker Image Version:  23.04.2                                       │
    │ Docker Image Platform: linux/amd64                                   │
    │                                                                      │
    ╰――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╯
[cont-init   ] 89-info.sh: terminated successfully.
[cont-init   ] all container initialization scripts executed.
[init        ] giving control to process supervisor.
[supervisor  ] loading services...
[supervisor  ] loading service 'default'...
[supervisor  ] loading service 'app'...
[supervisor  ] loading service 'gui'...
[supervisor  ] loading service 'certsmonitor'...
[supervisor  ] service 'certsmonitor' is disabled.
[supervisor  ] loading service 'nginx'...
[supervisor  ] loading service 'xvnc'...
[supervisor  ] loading service 'openbox'...
[supervisor  ] loading service 'CrashPlanEngine'...
[supervisor  ] loading service 'logmonitor'...
[supervisor  ] loading service 'logrotate'...
[supervisor  ] all services loaded.
[supervisor     ] starting services...
[supervisor     ] starting service 'xvnc'...
[xvnc           ] Xvnc TigerVNC 1.13.1 - built Apr 16 2023 17:12:53
[xvnc           ] Copyright (C) 1999-2022 TigerVNC Team and many others (see README.rst)
[xvnc           ] See https://www.tigervnc.org for information on TigerVNC.
[xvnc           ] Underlying X server release 12013000
[xvnc           ] Mon May 29 00:51:08 2023
[xvnc           ]  vncext:      VNC extension running!
[xvnc           ]  vncext:      Listening for VNC connections on /tmp/vnc.sock (mode 0660)
[xvnc           ]  vncext:      Listening for VNC connections on all interface(s), port 5900
[xvnc           ]  vncext:      created VNC server for screen 0
[supervisor     ] starting service 'nginx'...
[nginx          ] Listening for HTTP connections on port 5800.
[supervisor     ] starting service 'openbox'...
[supervisor     ] starting service 'CrashPlanEngine'...
[xvnc           ] Mon May 29 00:51:18 2023
[xvnc           ]  Connections: accepted: /tmp/vnc.sock
[xvnc           ]  SConnection: Client needs protocol version 3.8
[xvnc           ]  SConnection: Client requests security type None(1)
[xvnc           ]  VNCSConnST:  Server default pixel format depth 24 (32bpp) little-endian rgb888
[xvnc           ]  VNCSConnST:  Client pixel format depth 24 (32bpp) little-endian bgr888
[supervisor     ] ERROR: service 'CrashPlanEngine' failed to be started: not ready after 30000 msec, giving up.
[supervisor     ] starting service 'app'...
[supervisor     ] starting service 'logmonitor'...
[logmonitor     ] Monitoring log file: /config/log/service.log.0
[logmonitor     ] Monitoring status file: /config/log/app.log
[supervisor     ] all services started.
[xvnc           ] Mon May 29 16:30:31 2023
[xvnc           ]  VNCSConnST:  closing /tmp/vnc.sock: Clean disconnection
[xvnc           ]  EncodeManager: Framebuffer updates: 527
[xvnc           ]  EncodeManager:   Tight:
[xvnc           ]  EncodeManager:     Solid: 110 rects, 6.91665 Mpixels
[xvnc           ]  EncodeManager:            1.71875 KiB (1:15720.4 ratio)
[xvnc           ]  EncodeManager:     Bitmap RLE: 36 rects, 13.423 kpixels
[xvnc           ]  EncodeManager:                 1.12793 KiB (1:46.8606 ratio)
[xvnc           ]  EncodeManager:     Indexed RLE: 538 rects, 472.31 kpixels
[xvnc           ]  EncodeManager:                  100.129 KiB (1:18.4888 ratio)
[xvnc           ]  EncodeManager:   Tight (JPEG):
[xvnc           ]  EncodeManager:     Full Colour: 250 rects, 741.132 kpixels
[xvnc           ]  EncodeManager:                  382.221 KiB (1:7.58195 ratio)
[xvnc           ]  EncodeManager:   Total: 934 rects, 8.14351 Mpixels
[xvnc           ]  EncodeManager:          485.196 KiB (1:65.5849 ratio)
[xvnc           ]  Connections: closed: /tmp/vnc.sock
[xvnc           ]  ComparingUpdateTracker: 42.0744 Mpixels in / 5.95396 Mpixels out
[xvnc           ]  ComparingUpdateTracker: (1:7.06662 ratio)
[supervisor     ] SIGTERM received, shutting down...
[supervisor     ] stopping service 'logmonitor'...
[supervisor     ] service 'logmonitor' exited (got signal SIGTERM).
[supervisor     ] stopping service 'app'...
[supervisor     ] stopping service 'CrashPlanEngine'...
[supervisor     ] stopping service 'openbox'...
[supervisor     ] service 'openbox' exited (with status 0).
[supervisor     ] stopping service 'nginx'...
[supervisor     ] service 'nginx' exited (with status 0).
[supervisor     ] stopping service 'xvnc'...
[xvnc           ] Sat Jun  3 16:49:16 2023
[xvnc           ]  ComparingUpdateTracker: 0 pixels in / 0 pixels out
[xvnc           ]  ComparingUpdateTracker: (1:-nan ratio)
[supervisor     ] service 'xvnc' exited (with status 0).
[supervisor     ] sending SIGTERM to all processes...
[supervisor     ] service 'app' exited (with status 143).
[supervisor     ] sending SIGKILL to all processes...
[supervisor     ] service 'CrashPlanEngine' exited (got signal SIGKILL).
[finish      ] executing container finish scripts...
[finish      ] all container finish scripts executed.
[init        ] container is starting...
[cont-env    ] loading container environment variables...
[cont-env    ] APP_NAME: loading...
[cont-env    ] APP_VERSION: loading...
[cont-env    ] DISPLAY: executing...
[cont-env    ] DISPLAY: terminated successfully.
[cont-env    ] DISPLAY: loading...
[cont-env    ] DOCKER_IMAGE_PLATFORM: loading...
[cont-env    ] DOCKER_IMAGE_VERSION: loading...
[cont-env    ] GTK2_RC_FILES: executing...
[cont-env    ] GTK2_RC_FILES: terminated successfully.
[cont-env    ] GTK2_RC_FILES: loading...
[cont-env    ] GTK_THEME: executing...
[cont-env    ] GTK_THEME: terminated successfully.
[cont-env    ] GTK_THEME: loading...
[cont-env    ] HOME: loading...
[cont-env    ] QT_STYLE_OVERRIDE: executing...
[cont-env    ] QT_STYLE_OVERRIDE: terminated successfully.
[cont-env    ] QT_STYLE_OVERRIDE: loading...
[cont-env    ] TAKE_CONFIG_OWNERSHIP: loading...
[cont-env    ] XDG_CACHE_HOME: loading...
[cont-env    ] XDG_CONFIG_HOME: loading...
[cont-env    ] XDG_DATA_HOME: loading...
[cont-env    ] XDG_RUNTIME_DIR: loading...
[cont-env    ] XDG_STATE_HOME: loading...
[cont-env    ] container environment variables initialized.
[cont-secrets] loading container secrets...
[cont-secrets] container secrets loaded.
[cont-init   ] executing container initialization scripts...
[cont-init   ] 10-certs.sh: executing...
[cont-init   ] 10-certs.sh: terminated successfully.
[cont-init   ] 10-check-app-niceness.sh: executing...
[cont-init   ] 10-check-app-niceness.sh: terminated successfully.
[cont-init   ] 10-cjk-font.sh: executing...
[cont-init   ] 10-cjk-font.sh: terminated successfully.
[cont-init   ] 10-clean-logmonitor-states.sh: executing...
[cont-init   ] 10-clean-logmonitor-states.sh: terminated successfully.
[cont-init   ] 10-clean-tmp-dir.sh: executing...
[cont-init   ] 10-clean-tmp-dir.sh: terminated successfully.
[cont-init   ] 10-fontconfig-cache-dir.sh: executing...
[cont-init   ] 10-fontconfig-cache-dir.sh: terminated successfully.
[cont-init   ] 10-init-users.sh: executing...
[cont-init   ] 10-init-users.sh: terminated successfully.
[cont-init   ] 10-nginx.sh: executing...
[cont-init   ] 10-nginx.sh: terminated successfully.
[cont-init   ] 10-openbox.sh: executing...
[cont-init   ] 10-openbox.sh: terminated successfully.
[cont-init   ] 10-set-tmp-dir-perms.sh: executing...
[cont-init   ] 10-set-tmp-dir-perms.sh: terminated successfully.
[cont-init   ] 10-vnc-password.sh: executing...
[cont-init   ] 10-vnc-password.sh: terminated successfully.
[cont-init   ] 10-web-data.sh: executing...
[cont-init   ] 10-web-data.sh: terminated successfully.
[cont-init   ] 10-x11-unix.sh: executing...
[cont-init   ] 10-x11-unix.sh: terminated successfully.
[cont-init   ] 10-xdg-runtime-dir.sh: executing...
[cont-init   ] 10-xdg-runtime-dir.sh: terminated successfully.
[cont-init   ] 15-install-pkgs.sh: executing...
[cont-init   ] 15-install-pkgs.sh: terminated successfully.
[cont-init   ] 55-crashplan-pro.sh: executing...
[cont-init   ] 55-crashplan-pro.sh: setting CrashPlan Engine maximum memory to 1024M
[cont-init   ] 55-crashplan-pro.sh: terminated successfully.
[cont-init   ] 55-validate_max_mem.sh: executing...
[cont-init   ] 55-validate_max_mem.sh: terminated successfully.
[cont-init   ] 85-take-config-ownership.sh: executing...
[cont-init   ] 85-take-config-ownership.sh: terminated successfully.
[cont-init   ] 89-info.sh: executing...
    ╭――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╮
    │                                                                      │
    │ Application:           CrashPlan for Small Business                  │
    │ Application Version:   11.0.1                                        │
    │ Docker Image Version:  23.04.2                                       │
    │ Docker Image Platform: linux/amd64                                   │
    │                                                                      │
    ╰――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╯
[cont-init   ] 89-info.sh: terminated successfully.
[cont-init   ] all container initialization scripts executed.
[init        ] giving control to process supervisor.
[supervisor  ] loading services...
[supervisor  ] loading service 'default'...
[supervisor  ] loading service 'app'...
[supervisor  ] loading service 'gui'...
[supervisor  ] loading service 'certsmonitor'...
[supervisor  ] service 'certsmonitor' is disabled.
[supervisor  ] loading service 'nginx'...
[supervisor  ] loading service 'xvnc'...
[supervisor  ] loading service 'openbox'...
[supervisor  ] loading service 'CrashPlanEngine'...
[supervisor  ] loading service 'logmonitor'...
[supervisor  ] loading service 'logrotate'...
[supervisor  ] all services loaded.
[supervisor     ] starting services...
[supervisor     ] starting service 'xvnc'...
[xvnc           ] Xvnc TigerVNC 1.13.1 - built Apr 16 2023 17:12:53
[xvnc           ] Copyright (C) 1999-2022 TigerVNC Team and many others (see README.rst)
[xvnc           ] See https://www.tigervnc.org for information on TigerVNC.
[xvnc           ] Underlying X server release 12013000
[xvnc           ] Sat Jun  3 16:54:56 2023
[xvnc           ]  vncext:      VNC extension running!
[xvnc           ] Sat Jun  3 16:54:57 2023
[xvnc           ]  vncext:      Listening for VNC connections on /tmp/vnc.sock (mode 0660)
[xvnc           ]  vncext:      Listening for VNC connections on all interface(s), port 5900
[xvnc           ]  vncext:      created VNC server for screen 0
[supervisor     ] starting service 'nginx'...
[nginx          ] Listening for HTTP connections on port 5800.
[supervisor     ] starting service 'openbox'...
[supervisor     ] starting service 'CrashPlanEngine'...
[supervisor     ] ERROR: service 'CrashPlanEngine' failed to be started: not ready after 30000 msec, giving up.
[supervisor     ] starting service 'app'...
[supervisor     ] starting service 'logmonitor'...
[logmonitor     ] Monitoring log file: /config/log/service.log.0
[logmonitor     ] Monitoring status file: /config/log/app.log
[supervisor     ] all services started.
[xvnc           ] Sun Jun  4 14:43:57 2023
[xvnc           ]  Connections: accepted: /tmp/vnc.sock
[xvnc           ]  SConnection: Client needs protocol version 3.8
[xvnc           ]  SConnection: Client requests security type None(1)
[xvnc           ]  VNCSConnST:  Server default pixel format depth 24 (32bpp) little-endian rgb888
[xvnc           ] Sun Jun  4 14:43:58 2023
[xvnc           ]  VNCSConnST:  Client pixel format depth 24 (32bpp) little-endian bgr888
[xvnc           ] Sun Jun  4 14:51:20 2023
[xvnc           ]  Connections: accepted: /tmp/vnc.sock
[xvnc           ] Sun Jun  4 14:51:21 2023
[xvnc           ]  SConnection: Client needs protocol version 3.8
[xvnc           ] Sun Jun  4 14:51:22 2023
[xvnc           ]  SConnection: Client requests security type None(1)
[xvnc           ]  VNCSConnST:  Server default pixel format depth 24 (32bpp) little-endian rgb888
[xvnc           ]  VNCSConnST:  Client pixel format depth 24 (32bpp) little-endian bgr888
[xvnc           ] Sun Jun  4 14:51:27 2023
[xvnc           ]  VNCSConnST:  closing /tmp/vnc.sock: Clean disconnection
[xvnc           ]  EncodeManager: Framebuffer updates: 88
[xvnc           ]  EncodeManager:   Tight:
[xvnc           ]  EncodeManager:     Solid: 30 rects, 1.97493 Mpixels
[xvnc           ]  EncodeManager:            480 B (1:16458.5 ratio)
[xvnc           ]  EncodeManager:     Indexed RLE: 85 rects, 46.909 kpixels
[xvnc           ]  EncodeManager:                  13.0811 KiB (1:14.0841 ratio)
[xvnc           ]  EncodeManager:   Tight (JPEG):
[xvnc           ]  EncodeManager:     Full Colour: 25 rects, 113.767 kpixels
[xvnc           ]  EncodeManager:                  48.668 KiB (1:9.13733 ratio)
[xvnc           ]  EncodeManager:   Total: 140 rects, 2.13561 Mpixels
[xvnc           ]  EncodeManager:          62.2178 KiB (1:134.107 ratio)
[xvnc           ]  Connections: closed: /tmp/vnc.sock
[xvnc           ]  ComparingUpdateTracker: 2.74529 Mpixels in / 580.394 kpixels out
[xvnc           ]  ComparingUpdateTracker: (1:4.73005 ratio)

Container inspect
[
    {
        "Id": "254e6fe9bcf046db086004f32388b4b39cfaf12f5380cf8645c5a78bf12008fd",
        "Created": "2023-05-28T18:58:29.908264969Z",
        "Path": "/init",
        "Args": [],
        "State": {
            "Status": "running",
            "Running": true,
            "Paused": false,
            "Restarting": false,
            "OOMKilled": false,
            "Dead": false,
            "Pid": 20284,
            "ExitCode": 0,
            "Error": "",
            "StartedAt": "2023-06-03T16:54:55.54725301Z",
            "FinishedAt": "2023-06-03T16:49:21.92156088Z",
            "StartedTs":<PHONE_NUMBER>,
            "FinishedTs":<PHONE_NUMBER>
        },
        "Image": "sha256:60f73e389d640c8cde1610a40be00e97690550f8ce23af6680c9f85bc37bb4dd",
        "ResolvConfPath"<EMAIL_ADDRESS>        "HostnamePath": "/volume1/@docker/containers/254e6fe9bcf046db086004f32388b4b39cfaf12f5380cf8645c5a78bf12008fd/hostname",
        "HostsPath": "/volume1/@docker/containers/254e6fe9bcf046db086004f32388b4b39cfaf12f5380cf8645c5a78bf12008fd/hosts",
        "LogPath"<EMAIL_ADDRESS>        "Name": "/crashplan",
        "RestartCount": 0,
        "Driver": "btrfs",
        "Platform": "linux",
        "MountLabel": "",
        "ProcessLabel": "",
        "AppArmorProfile": "docker-unconfined",
        "ExecIDs": null,
        "HostConfig": {
            "Binds": [
                "/volume1/homes:/storage:rw",
                "/volume1/docker/crashplan-pro:/config:rw"
            ],
            "ContainerIDFile": "",
            "LogConfig": {
                "Type": "db",
                "Config": {}
            },
            "NetworkMode": "bridge",
            "PortBindings": {
                "5800/tcp": [
                    {
                        "HostIp": "",
                        "HostPort": "49160"
                    }
                ],
                "5900/tcp": [
                    {
                        "HostIp": "",
                        "HostPort": "49161"
                    }
                ]
            },
            "RestartPolicy": {
                "Name": "always",
                "MaximumRetryCount": 0
            },
            "AutoRemove": false,
            "VolumeDriver": "",
            "VolumesFrom": null,
            "CapAdd": [],
            "CapDrop": [],
            "CgroupnsMode": "host",
            "Dns": [],
            "DnsOptions": [],
            "DnsSearch": [],
            "ExtraHosts": null,
            "GroupAdd": null,
            "IpcMode": "private",
            "Cgroup": "",
            "Links": null,
            "OomScoreAdj": 0,
            "PidMode": "",
            "Privileged": true,
            "PublishAllPorts": false,
            "ReadonlyRootfs": false,
            "SecurityOpt": [
                "label=disable"
            ],
            "UTSMode": "",
            "UsernsMode": "",
            "ShmSize": 67108864,
            "Runtime": "runc",
            "Env": [
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/base/sbin:/opt/base/bin",
                "ENV=/root/.docker_rc",
                "USER_ID=1030",
                "GROUP_ID=100",
                "SUP_GROUP_IDS=",
                "UMASK=0022",
                "LANG=en_US.UTF-8",
                "TZ=Etc/UTC",
                "KEEP_APP_RUNNING=0",
                "APP_NICENESS=0",
                "INSTALL_PACKAGES=",
                "CONTAINER_DEBUG=0",
                "DISPLAY_WIDTH=1920",
                "DISPLAY_HEIGHT=1080",
                "DARK_MODE=0",
                "SECURE_CONNECTION=0",
                "SECURE_CONNECTION_VNC_METHOD=SSL",
                "SECURE_CONNECTION_CERTS_CHECK_INTERVAL=60",
                "WEB_LISTENING_PORT=5800",
                "VNC_LISTENING_PORT=5900",
                "VNC_PASSWORD=",
                "ENABLE_CJK_FONT=0",
                "CRASHPLAN_SRV_MAX_MEM=1024M"
            ],
            "ConsoleSize": [
                0,
                0
            ],
            "Isolation": "",
            "CpuShares": 50,
            "Memory": 0,
            "NanoCpus": 0,
            "CgroupParent": "",
            "BlkioWeight": 0,
            "BlkioWeightDevice": null,
            "BlkioDeviceReadBps": null,
            "BlkioDeviceWriteBps": null,
            "BlkioDeviceReadIOps": null,
            "BlkioDeviceWriteIOps": null,
            "CpuPeriod": 0,
            "CpuQuota": 0,
            "CpuRealtimePeriod": 0,
            "CpuRealtimeRuntime": 0,
            "CpusetCpus": "",
            "CpusetMems": "",
            "Devices": null,
            "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": null,
            "ReadonlyPaths": null
        },
        "GraphDriver": {
            "Data": null,
            "Name": "btrfs"
        },
        "Mounts": [
            {
                "Type": "bind",
                "Source": "/volume1/docker/crashplan-pro",
                "Destination": "/config",
                "Mode": "rw",
                "RW": true,
                "Propagation": "rprivate"
            },
            {
                "Type": "bind",
                "Source": "/volume1/homes",
                "Destination": "/storage",
                "Mode": "rw",
                "RW": true,
                "Propagation": "rprivate"
            }
        ],
        "Config": {
            "Hostname": "crashplan",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": false,
            "AttachStderr": false,
            "ExposedPorts": {
                "5800/tcp": {},
                "5900/tcp": {}
            },
            "Tty": true,
            "OpenStdin": true,
            "StdinOnce": false,
            "Env": [
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/base/sbin:/opt/base/bin",
                "ENV=/root/.docker_rc",
                "USER_ID=1030",
                "GROUP_ID=100",
                "SUP_GROUP_IDS=",
                "UMASK=0022",
                "LANG=en_US.UTF-8",
                "TZ=Etc/UTC",
                "KEEP_APP_RUNNING=0",
                "APP_NICENESS=0",
                "INSTALL_PACKAGES=",
                "CONTAINER_DEBUG=0",
                "DISPLAY_WIDTH=1920",
                "DISPLAY_HEIGHT=1080",
                "DARK_MODE=0",
                "SECURE_CONNECTION=0",
                "SECURE_CONNECTION_VNC_METHOD=SSL",
                "SECURE_CONNECTION_CERTS_CHECK_INTERVAL=60",
                "WEB_LISTENING_PORT=5800",
                "VNC_LISTENING_PORT=5900",
                "VNC_PASSWORD=",
                "ENABLE_CJK_FONT=0",
                "CRASHPLAN_SRV_MAX_MEM=1024M"
            ],
            "Cmd": [
                "/init"
            ],
            "Image": "jlesage/crashplan-pro:latest",
            "Volumes": {
                "/config": {},
                "/storage": {}
            },
            "WorkingDir": "/tmp",
            "Entrypoint": null,
            "OnBuild": null,
            "Labels": {
                "org.label-schema.description": "Docker container for CrashPlan PRO",
                "org.label-schema.name": "crashplan-pro",
                "org.label-schema.schema-version": "1.0",
                "org.label-schema.vcs-url": "https://github.com/jlesage/docker-crashplan-pro",
                "org.label-schema.version": "23.04.2"
            },
            "DDSM": false
        },
        "NetworkSettings": {
            "Bridge": "",
            "SandboxID": "61d010bd7fe2702fd926d2ca379fb70375b04d43c38f9373775980a59dfed38e",
            "HairpinMode": false,
            "LinkLocalIPv6Address": "",
            "LinkLocalIPv6PrefixLen": 0,
            "Ports": {
                "5800/tcp": [
                    {
                        "HostIp": "<IP_ADDRESS>",
                        "HostPort": "49160"
                    }
                ],
                "5900/tcp": [
                    {
                        "HostIp": "<IP_ADDRESS>",
                        "HostPort": "49161"
                    }
                ]
            },
            "SandboxKey": "/var/run/docker/netns/61d010bd7fe2",
            "SecondaryIPAddresses": null,
            "SecondaryIPv6Addresses": null,
            "EndpointID": "6253d0146e80acafdb5b2b63f8dffa8dfb787da5cd79db9979f33d4b8ee10b76",
            "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": "5f54f4fd9ebbf175cea30bcfc2800ff83be0fc75258fc45a222bb2ee8b27ae37",
                    "EndpointID": "6253d0146e80acafdb5b2b63f8dffa8dfb787da5cd79db9979f33d4b8ee10b76",
                    "Gateway": "<IP_ADDRESS>",
                    "IPAddress": "<IP_ADDRESS>",
                    "IPPrefixLen": 16,
                    "IPv6Gateway": "",
                    "GlobalIPv6Address": "",
                    "GlobalIPv6PrefixLen": 0,
                    "MacAddress": "02:42:ac:11:00:02",
                    "DriverOpts": null
                }
            }
        }
    }
]

Anything else?
No response

Is the firewall blocking connections to the Internet ?

Do you have a rule that denies everything (globally or per interface) ?  What is the default action if no rule is matched ?
Is it working when you have the firewall enabled, without any rule defined ?

Great that you figured it out.
For reference, ports used by CrashPlan are documented here: https://support.crashplan.com/hc/en-us/articles/9020789462669-IP-addresses-and-ports-used-by-CrashPlan

Do you still have problems with the firewall ?  If yes, I suggest that you share the whole firewall configuration, for all interfaces.  It would also be useful if you could share what you are trying to achieve when enabling the firewall.  Finally, you might also seek help with Synology about how to use the firewall.  The problem doesn't seem to be with the container, but really with the setup of the firewall.


[BUG] RKE2 System Images Are Not Pulled From Cluster Level Registry

Rancher Server Setup

Rancher version: 2.6.5 and up
Installation option (Docker install/Helm Chart):

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): n/a

Proxy/Cert Details: n/a

Information about the Cluster

Kubernetes version: any
Cluster Type (Local/Downstream):

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): RKE2/K3s

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)

If custom, define the set of permissions: admin

Describe the bug

When provisioning an RKE2 cluster configured with a cluster level registry, while also having a global level registry defined in the Rancher global settings, not all system images are pulled from the cluster level registry.
To Reproduce

Create 1 unauthenticated and 1 authenticated registry containing all system images for a released version of Rancher (2.6.7 for example)
1a. The unauthenticated registry will act as your global level registry
1b. The authenticated registry will act as your cluster level registry
Change the global system-default-registry in the Rancher global settings to point to your unauthenticated registry
Begin to create an RKE2 cluster, ensuring you chose the correct version of k8's for the images loaded into your registries
In the Cluster Configuration section, select Registries
The Pull images for Rancher from a private registry option should already be selected, and the value should default to your global level registry. Change the value to point to your cluster level registry.
For Authentication select Create a basic HTTP Auth Secret and pass in the username and password of your authenticated registry
Create the cluster

Result
Navigate to the cluster explorer, and view all pods within all namespaces. Observe that a majority of the images pulled are from the global level registry, and not he cluster level registry.
Expected Result

All images should be pulled from the cluster level registry if one is defined.
Additional context
This change will require a release note, as it will impact existing clusters which may or may not have the cluster level registry configured correctly. Additional documentation should also be added to denote this change in behavior.

This issue is related to https://github.com/rancher/rancher/issues/35189

This work will be included in 2.7.0-rc1
Root cause
Rancher was passing the --system-default-registry flag to RKE2 even in situations where a cluster level registry was defined, causing images to be pulled from the wrong registry.
What was fixed, or what changes have occurred
If a cluster level private registry is defined in the UI, this flag will not be passed. System images will be pulled from the correct registry defined in registries.yaml.
Areas or cases that should be tested

Create 1 unauthenticated and 1 authenticated registry containing all system images for a released version of Rancher (Images for registries are generated with reach release and RC, and can be located in the rancher-images.txt file.)
1a. The unauthenticated registry will act as your global level registry
1b. The authenticated registry will act as your cluster level registry
Change the global system-default-registry in the Rancher global settings to point to your unauthenticated registry
Begin to create an RKE2/K3s cluster, ensuring you chose the correct version of k8's for the images loaded into your registries
In the Cluster Configuration section, select Registries
The Pull images for Rancher from a private registry option should already be selected, and the value should default to your global level registry. Change the value to point to your cluster level registry.
For Authentication select Create a basic HTTP Auth Secret and pass in the username and password of your authenticated registry
Create the cluster and wait for it to become available
Navigate to the Cluster Explorer
In the top right corner, select all namespaces
Navigate to the pods section of the explorer so that all pods are visible
Check that all images pulled by default (system-default-images) are pulled from the cluster level registry and not the global level registry.
It is expected that the fleet-agent image is not pulled from the cluster level registry, this is a known issue that was intentionally not resolved in this PR

The above steps should be repeated for K3s clusters, as they both share the same logic
What areas could experience regressions?
situations where only the global system-default-registry has been defined, however I have done manual testing of this and have seen no issues.

/backport v2.6.9

Ticket #38890 - Test Results - WIP
With HA Helm:
To be verified on rancher v2.7-head:

Scenario 1 -

Test: Provision a downstream AWS Node driver RKE2 cluster, w/ authenticated registry configured
Result:

Scenario 2 - Provision a downstream AWS Node driver K3s cluster, w/ authenticated registry configured

Test:
Result:

Scenario 3 - Provision downstream AWS Node driver RKE2 + K3s clusters, w/ global (un-auth'd) registry configured

Test:
Result:

Reproduced - ✅ - Friday September 23, 2022
On rancher v2.6.8:

Create 2 private registries - [1 authenticated + 1 un-authenticated]
Fresh install of rancher v2.6.8
From Global Settings > system-default-registry, update field to point to un-authenticated registry created in step 1
As admin, provision a downstream AWS Node driver RKE2 cluster, w/ authenticated registry configured
Reproduced - Images are primarily pulled from global registry, not cluster registry

Screenshot:

Scenario 1:
Validation Not Yet Started

Can we validate with a cluster registry with and without authentication?

@deniseschannon yes, Scenario 3 was specifically for that use case

Test cases to be included

Cluster Type
Cluster Level Registry
Global Level registry
Status

RKE2
Yes; Authenticated
Yes; Not Authenticated

RKE2
Yes; Authenticated
Not Set

RKE2
Yes; Not Authenticated
Yes; Not Authenticated

RKE2
Yes; Not Authenticated
Not Set

K3s
Yes; Authenticated
Yes; Not Authenticated

K3s
Yes; Authenticated
Not Set

K3s
Yes; Not Authenticated
Yes; Not Authenticated

K3s
Yes; Not Authenticated
Not Set

RKE2
Not Set
Yes; Not Authenticated

k3s
Not Set
Yes; Not Authenticated

Awaiting rancher v2.7.0-rc2 to resume testing

Awaiting test results from https://github.com/rancher/rancher/issues/39104;
Will request RC for v2.7 to resume testing once that has been validated + closed

#39104 - ✅
Requested v2.7.0-rc3
Will resume testing when RC is published

Ticket #38890 - Test Results
Reproduction on v2.6.8 found here
Verified on rancher v2.7.0-rc3 w/ k8s v1.24.4+rke2r1 || v1.24.6+k3s1

Cluster Type
Cluster Level Registry
Global Level registry
Status

RKE2
Yes; Authenticated
Yes; Not Authenticated
✅

RKE2
Yes; Not Authenticated
Yes; Not Authenticated
✅

K3s
Yes; Authenticated
Yes; Not Authenticated
✅

K3s
Yes; Not Authenticated
Yes; Not Authenticated
✅


Adding a -y flag to an apt-get install command

I aborted the tests b/c none of this runs this code anyway

Looks like 9.1 is not ready in CI yet. I will just leave this here until later

These changes will be incorporated somewhere else


Syntax for specifying missing columns

Currently, a type specification of Optional[int] means that a column must be of integer type but may contain nulls.
We currently don't support a syntax to specify that it is allowed that a column is missing.
One current workaround is to specify Foo.validate(df, allow_missing_columns=True), where allow_missing_columns is passed on to _find_errors as a kwarg (we should add this as an explicit parameter).
The following example contains a suggestion for how we could allow missing columns (see c). It is one that @JakobGM came up with last year.
import patito as pt
from typing import Optional

class Foo(pt.Model):
    a: int # only ints
    b: Optional[int] # mix ints and nulls
    c: int = None # column may be missing, but if it's there it must be an int - but this fails a type check
    d: Optional[int] = None # column may be missing, but if it's there it must be an int

An alternative would be to use pt.Field / ColumnInfo, and do something like the following, which I might like better, just because it will pass type checks.
class Foo(pt.Model):
    c: int = pt.Field(allow_missing=True)

I am very open to ideas here. Does anyone have a suggestion? Tagging a few possibly-interested parties, @brendancooley, @dsgibbons, @ion-elgreco

Hey @thomasaarholt, I would prefer pt.Field(allow_missing=True) because if you say c: int = None it's not entirely clear what is happening and also how can one still add a pt.Field with specific settings on a field.
A kwarg in pt.Field seems most clear and flexible to me.
And also I like the idea of allowing specific columns to be missing! :)

+1 for pt.Field(allow_missing=True)

+1 for allow_missing. A related feature to consider is validation on derived_from and constraints column dependencies. We can inspect which columns are required to compute a derivation or constraint using expr.meta.root_names() and check

that the column is present on the model and
that allow_missing is False

Perhaps we could insert these checks into the Model.validate_schema method.

I may be interested in giving this a go - are we happy to pursue pt.Field(allow_missing=True)?

@dsgibbons yeah I think there is a consensus on allow_missing! Go ahead : )


Include navbar dropdown event handler in Angular2_CLI_Starter

Awesome template, thanks for sharing!
While using the Angular2_CLI_Starter project to create my admin panel, I noticed that the dropdown event handler on full-layout.component.ts for the navbar was missing. Using the full project as an example, I ported the event handler code over to the starter project.
I'm not sure if you left this out intentionally or if it was just overlooked. Feel free to merge if you see fit.

I see that you've added the changes. I'll close this pull request.


Stack overflow problem for small ROM

I've implemented a ROM as proposed by https://github.com/freechipsproject/chisel3/wiki/Memories but when I try to run the tests, it stack-overflows:
[info] [0.003] Elaborating design... [info] [0.202] Done elaborating. [info] [0.000] Elaborating design... [info] [0.078] Done elaborating. End of dependency graph Circuit state created *** RUN ABORTED ***   java.lang.StackOverflowError:   at firrtl_interpreter.LoFirrtlExpressionEvaluator.evaluate(LoFirrtlExpressionEvaluator.scala:263)   at firrtl_interpreter.LoFirrtlExpressionEvaluator.binaryBitWise(LoFirrtlExpressionEvaluator.scala:241)   at firrtl_interpreter.LoFirrtlExpressionEvaluator.evaluate(LoFirrtlExpressionEvaluator.scala:355)   at firrtl_interpreter.LoFirrtlExpressionEvaluator.evaluate(LoFirrtlExpressionEvaluator.scala:290)   at firrtl_interpreter.LoFirrtlExpressionEvaluator$$anonfun$5.apply(LoFirrtlExpressionEvaluator.scala:453)   at firrtl_interpreter.LoFirrtlExpressionEvaluator$$anonfun$5.apply(LoFirrtlExpressionEvaluator.scala:445)   at firrtl_interpreter.Timer.apply(Timer.scala:40)   at firrtl_interpreter.LoFirrtlExpressionEvaluator.firrtl_interpreter$LoFirrtlExpressionEvaluator$$resolveDependency(LoFirrtlExpressionEvaluator.scala:444)   at firrtl_interpreter.LoFirrtlExpressionEvaluator.getValue(LoFirrtlExpressionEvaluator.scala:81)   at firrtl_interpreter.LoFirrtlExpressionEvaluator.evaluate(LoFirrtlExpressionEvaluator.scala:304)   ...

console.zip

I cannot reproduce the problem.  This runs for me with both the firrtl and verilator backends.  The only changes I made were

Comment out //import util.control.Breaks._
Change the third expect to expect(c.io.character, c.helloWorldString(i % l).toInt)

I tried fiddling with memory parameters, the following:
export SBT_OPTS='-Xmx64M -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -Xss2M  -Duser.timezone=GMT'

could cause some error. But didn't seem to be related to yours.  I usually use -Xmx2G in SBT_OPTS
@jackkoenig can you answer the strange verilog question

When it fails depends on the JVM settings as you point out, so that would
explain why I would see it and you wouldn't.
The length of "val helloWorldString" is what seems to trigger it.
Can you try to make it e.g. 64kBytes?
Perhaps the recursive algorithm is explained by the funny Verilog it
produces?
On Thu, Jul 6, 2017 at 12:34 AM, Chick Markley<EMAIL_ADDRESS>wrote:

I cannot reproduce the problem. This runs for me with both the firrtl
and verilator backends. The only changes I made were

Comment out //import util.control.Breaks._
Change the third expect to expect(c.io.character,
c.helloWorldString(i % l).toInt)

I tried fiddling with memory parameters, the following:
export SBT_OPTS='-Xmx64M -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -Xss2M  -Duser.timezone=GMT'
could cause some error. But didn't seem to be related to yours. I usually
use -Xmx2G in SBT_OPTS
@jackkoenig https://github.com/jackkoenig can you answer the strange
verilog question
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/freechipsproject/chisel3/issues/642#issuecomment-313245398,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACq05i-KASgIQRYLxknCCC7Tj49NuWaHks5sLA9mgaJpZM4OOP84
.

--
Øyvind Harboe, General Manager, Zylin AS, +47 917 86 146

@oharboe Per the "strange" Verilog: synthesis tools do in fact infer this correctly. We emit Verilog like this because it's easier to implement and still handled well by existing CAD tools. We would like to emit more traditional Verilog vectors but there are many technical hurdles to overcome before then so it will be a while.
@chick Long dependency chains could definitely cause a stack overflow error. We should make evaluate algorithm tail recursive or use an explicit stack.

Is this still a problem?

Yes.
Updated test files here: console2.zip
[info] [0.002] Elaborating design... [info] [0.138] Done elaborating. Total FIRRTL Compile Time: 1409.1 ms Total FIRRTL Compile Time: 256.3 ms End of dependency graph Circuit state created *** RUN ABORTED ***   java.lang.StackOverflowError:   at scala.math.BigInt$.int2bigInt(BigInt.scala:97)   at firrtl_interpreter.ConcreteUInt.<init>(Concrete.scala:332)   at firrtl_interpreter.Concrete$.apply(Concrete.scala:292)   at firrtl_interpreter.LoFirrtlExpressionEvaluator.evaluate(LoFirrtlExpressionEvaluator.scala:374)   at firrtl_interpreter.LoFirrtlExpressionEvaluator.comparisonOp(LoFirrtlExpressionEvaluator.scala:179)   at firrtl_interpreter.LoFirrtlExpressionEvaluator.evaluate(LoFirrtlExpressionEvaluator.scala:332)   at firrtl_interpreter.LoFirrtlExpressionEvaluator.binaryBitWise(LoFirrtlExpressionEvaluator.scala:242)   at firrtl_interpreter.LoFirrtlExpressionEvaluator.evaluate(LoFirrtlExpressionEvaluator.scala:355)   at firrtl_interpreter.LoFirrtlExpressionEvaluator.evaluate(LoFirrtlExpressionEvaluator.scala:290)   at firrtl_interpreter.LoFirrtlExpressionEvaluator$$anonfun$5.apply(LoFirrtlExpressionEvaluator.scala:453)   ...

I am not sure how I missed this one.  It's a bit strange.
I get the same stack overflow if I run this from chisel, but if I take either the fir or lo.fir file I can read it into the interpreter repl without a problem.  I'll try and figure it out tomorrow

Would it make sense to add this code to the automated regression test suite
in git?
On Fri, Oct 20, 2017 at 9:54 AM, Chick Markley<EMAIL_ADDRESS>wrote:

I am not sure how I missed this one. It's a bit strange.
I get the same stack overflow if I run this from chisel, but if I take
either the fir or lo.fir file I can read it into the interpreter repl
without a problem. I'll try and figure it out tomorrow
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/freechipsproject/chisel3/issues/642#issuecomment-338133990,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACq05l2J8_HbNgz6V4XCXg2WLVI5kWJ8ks5suFG3gaJpZM4OOP84
.

--
Øyvind Harboe, General Manager, Zylin AS, +47 917 86 146

This appears to be a straight up legitimate stack overflow.  The interpreter is not elegant in it's dependency resolution, the dependency depth here was just too big for it.  I was able to run using
export SBT_OPTS="-Xmx2G -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:MaxPermSize=2G -Xss2M  -Duser.timezone=GMT"

sbt `testOnly examples.ConsoleTester`

I think this is a fair amount of work to fix properly, but alternatively I am in development of a next generation interpreter that has a fairly different (and hopefully quite a bit faster) execution engine that will not have this kind of dependency depth.
When that is done (pretty soon) we should include this in the regression.

makes sense. thanks!

okt. 2017 19.11 skrev "Chick Markley"<EMAIL_ADDRESS>

This appears to be a straight up legitimate stack overflow. The
interpreter is not elegant in it's dependency resolution, the dependency
depth here was just too big for it. I was able to run using
export SBT_OPTS="-Xmx2G -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:MaxPermSize=2G -Xss2M  -Duser.timezone=GMT"
sbt testOnly examples.ConsoleTester
I think this is a fair amount of work to fix properly, but alternatively I
am in development of a next generation interpreter that has a fairly
different (and hopefully quite a bit faster) execution engine that will not
have this kind of dependency depth.
When that is done (pretty soon) we should include this in the regression.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/freechipsproject/chisel3/issues/642#issuecomment-338266868,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACq05i0Mdq4uUITlS0r121qjb85irxNwks5suNQlgaJpZM4OOP84
.

fast-interpreter is still  a ways away, but I have incorporated this test into it's test suite and it passes with new scheme.

thanks!

nov. 2017 19.26 skrev "Chick Markley"<EMAIL_ADDRESS>

fast-interpreter is still a ways away, but I have incorporated this test
into it's test suite and it passes with new scheme.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/freechipsproject/chisel3/issues/642#issuecomment-342240053,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACq05q0_IVwTvWDIgrxyXU0l_-B3JzDBks5sz082gaJpZM4OOP84
.


Validation to be able to get a certificate

How do I get a certificate with the common name "myclustername.southcentralus.cloudapp.azure.com"? Generally, you can prove control over a domain name either by creating a DNS record or performing HTTP validation. For "cloudapp.azure.com" the second option is the only possibility (unless you are Microsoft). However, this creates a chicken and egg problem. I need to deploy a cluster (that exposes a web server) to be able to perform HTTP validation to get the certificate but to deploy the cluster I need the certificate. Is the only option to create a temporary cluster just to get the certificate with the common name and then replace this temporary cluster with the real cluster using the same name? In that case I think that should be included in the documentation.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e302570c-50f7-af0d-ab7c-62845ecd35cb
Version Independent ID: 679e51cc-2123-adb8-abe2-1c8bbacf46c3
Content: Create an Azure Service Fabric cluster using certificate common name
Content Source: articles/service-fabric/service-fabric-create-cluster-using-cert-cn.md
Service: service-fabric
GitHub Login: @rwike77
Microsoft Alias: ryanwi

Thanks for the question! We are investigating and will update you shortly.

@Liversage whenever you create a SF cluster in Azure the naming convention for connecting is ClusterName.Location.cloudapp.azure.com
When you get a cert from a certificate authority you will request that the certificate has the same name schema as ClusterName.Location.cloudapp.azure.com
Once you have certificate you would upload to the keyvault and follow the rest of this doc.
So I suppose in the case of making sure the name is available you might want to create a temp cluster first and then get the cert from a CA with the same name. Then delete the cluster and deploy the prod cluster under that same name. But getting the cert from the CA does not have anything to do with the SF being in place first. This is a separate process.

@MicahMcKittrick-MSFT I can't speak on behalf of DigiCert but I'm pretty sure that while you are able to order the certificate you will not actually get it. Or perhaps you will because you are an Microsoft employee which I'm not but that's not really my point.
To get a certificate with a common name that is a domain name you need to validate that you "own" the domain name. This domain validation is performed after you have placed the order so placing an order is not proving that you can buy a random domain name. In fact, the whole business of certificates and EV certificates is about having a trusted authority (in this case DigiCert) validating the organization buying the certificate. For instance, I can't buy a certificate for customersupport.microsoft.com which otherwise could be useful if my main line of business was phishing.
There is an SSL Certificate Validation Process from DigiCert page and under the label Domain Validation they write:

The aim of our domain validation process is to ensure that the individual requesting a certificate does, in fact, have authority to request a certificate for the domain in question.

Again, without knowing the specifics of how DigiCert conducts business I would expect that if you did in fact purchase the certificate you would then be presented with several options to prove that you control the domain name in the certificate, one of them being that you put up a web page on the domain with specific content that DigiCert provides you with (some random code). This allows them to verify that you control the domain name.
Since this issue has evolved into a discussion of the feasibility of being able to buy a certificate for a domain name I don't control I would like to point to a question about this with some answers: What prevents me from buying a SSL certificate for a domain I don't control?.

@dkkapur and @masnider if they are able to comment further.

@Liversage I did some additional digging but I found no issue with you actually requesting a cert from a CA for a domain that has the name "Azure" in it.
When you create any service in Azure that uses a DNS name it has Azure in the name. Unless you use a custom domain that is. Regardless, you are considered to own that domain and can prove it in any case. So in terms of getting the cert from the CA there should be no issues with getting it. Assuming you are not trying to get one for Azure.Com of course :)

@Liversage
This sounds like LetsEncrypt.
Where they ask you to host a web server, that serves a unique String, and if their issuer server can resolve that server and read that unique string; it will issue you a cert.
First. LetsEncrypt is not an integrated KV Trusted Root CA, and it NOT advised for Enterprise use.
Second, the process to get a certificate from non trusted and non integrated CA's is up to that CA; SF doesn't care where you get certificates from, the process to provision them, or installing them to your hosts.
I.E. Our VMSS extension ACL's the declared cert to SF cluster process, and our Runtime will only used installed accessible certs (it doesn't fetch them yet); we only care that its a valid accessible x509 certificate that the user explicitly trusts by declaring its Common Name and issuer thumbprint.
In Azure the prescriptive process that works, for provisioning a couple hundred dollar a year cert, and installing them on your hosts is:

Use Keyvault to provide credentials for an integrated CA (Digit Cert or Global Sign), and it will issue you a certificate for a domain you own; I.E. it can't be already owned by someone else, or you credentials authorize you to request a certificate for domains that already exist; further Trusted CA's are Audited to ensure they do not issue certs to unauthorized users.
Use VMSS.osProfile.secrets.vaultCertificates.certificateUrl to install a versioned certificate from Keyvault, using your VMSS's identity to authenticate to KV.
Use VMSS SF Extension to ACL the Cert to SF runtime
SF Cluster resource will declare what cert to use for the cluster.

For 3rd Party CA's who desire to be a Trusted Root CA, Microsoft's Trusted Root Certificate Program Requirements:
https://docs.microsoft.com/en-us/previous-versions//cc751157(v=technet.10)
@MicahMcKittrick-MSFT
Close this.

I don't think you really get what the original creator of the issue meant. What are the complete steps to create a working and supported cluster using a certificate that uses common name?
As far as I know I will not be able to obtain the certificate TheClusterIWantToCreate.Location.cloudapp.azure.com because I can't prove to the CA (digicert) that I control that domain. And I absolutely don't control that domain before I have created the cluster. And I cannot create a working cluster before I have obtained the certificate?
This documentation is about creating a cluster with certificate using common name. And I feel it's incomplete if not totally impossible to achieve this with the help of this article.
Some vital information is missing here.
The article guides:
"First, get a certificate from a certificate authority (CA). The common name of the certificate should be the host name of the cluster. For example, "myclustername.southcentralus.cloudapp.azure.com"."
Which should be impossible because CAs work in a way that one just cannot get the certificate without some kind of validation. The validation is not really possible because I haven't created the cluster reserved the domain name yet. Even if I had already created the cluster and reserved the domain name the service fabric doesn't provide any proof to the CA. So are we supposed to install a web server to the service fabric cluster (that doesn't yet exists) to provide a web server validation.
Other common ways of validation are absolutely unobtainable:

Email validation (no we cannot receive email at @Location.cloudapp.azure.com)
DNS (TXT record) validation (no we cannot change dns settings for azure.com or any of its subdomains)

Please show this issue to someone who has actually worked with these things.


Fix Sheridan's ID to be the sonatype ID 'scr14'.

@bivas - I was unable to deploy - I think because the id that I specified in developers section was not my sonatype id; can you please take a look & merge this?

/cc @daozheng @ynagasaki


Subtree acls

These patches add preliminary support for subtree-* ACL variants to allow simpler management of project trees and other data sharing where many resources will share the same policies. Additional test cases need to be written before we merge this, but I am starting the pull request to make it easier to review and discuss, since we may decide to abandon this approach and try something different...
These changes also raise several questions:

Should we really have separate ACL tables linked to the resources, since ACLs may become quite sparse when using tree-level policies?  The current denormalized arrays seem pretty ugly.
When creating new resources, should we still always set the owner ACL to the client identity, even if the client is already present in the subtree-owner ACL of an ancestor resource?  Skipping this might streamline some bulk workloads, but of course the ancestor ACLs could change in the future, orphaning such resources that lack their own owner.

I think this could be reviewed and merged now. At least now there are some tests of the new subtree ACLs and they pass too. :-)

Looks good to me. I'll merge this. Regarding your comments:

I agree we probably want a more normalized storage structure for the ACLs. I think you are right that they will likely be sparse.
I think it would make sense to set the owner on every object. But you're right we'll need to consider the performance implications for bulk workloads. It just makes sense though that every object would have its own owner that we can track for basic provenance.


Support shell commands

Allow users to do embed shell commands like this:
> "Authorization:Basic `cat ~/.apiauths | grep JIRA`"

Releated: #13

Done in PR #61.


[Bug report] No new photos available with v3.1.0

Version
3.1.0
Platforms
iOS
Device Model
iPhone 14 Pro
flutter info
[✓] Flutter (Channel stable, 3.19.6, on macOS 14.4.1 23E224 darwin-arm64, locale en-US)
    • Flutter version 3.19.6 on channel stable at /Users/mn/fvm/versions/3.19.6
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 54e66469a9 (3 weeks ago), 2024-04-17 13:08:03 -0700
    • Engine revision c4cd48e186
    • Dart version 3.3.4
    • DevTools version 2.31.1

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/mn/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/mn/Library/Android/sdk
    • ANDROID_SDK_ROOT = /Users/mn/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.10+0-17.0.10b1087.21-11572160)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15E204a
    • CocoaPods version 1.15.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2023.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.10+0-17.0.10b1087.21-11572160)

[✓] VS Code (version 1.89.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.86.0

[✓] Connected device (3 available)
    • Fred (2) (mobile) • 00008120-001A70290CC0C01E • ios            • iOS 17.4.1 21E236
    • macOS (desktop)   • macos                     • darwin-arm64   • macOS 14.4.1 23E224 darwin-arm64
    • Chrome (web)      • chrome                    • web-javascript • Google Chrome 124.0.6367.119

[✓] Network resources
    • All expected network resources are available.

• No issues found!

How to reproduce?
After updating to v3.1.0, only photos from prior to the update are available for selection when using AssetPicker.pickAssets. No photos made afterwards are visible at all. New screenshots made in the meantime are visible, however.
Reverting to v3.0.0 fixes the issue, after downgrading, everything works as expected again.
Logs
No response
Example code (optional)
No response
Contact
No response

Follow the migration guide might be helpful.

@AlexV525 thanks 🙏  I'm actually not using photo_manager directly at all, only (flutter_wechat_assets_picker)[https://github.com/fluttercandies/flutter_wechat_assets_picker] but I must have at some point added the dependency separately and then updated. After removing photo_manager from pub spec.yaml, 3.0.0 is picked correctly.
Closing this issue as it's working again. I guess the migration is then something to consider in flutter_wechat_assets_picker at some point.

Actually no, maybe I closed this too soon. flutter pub upgrade will update to 3.1.0 and then break the photo picker. But it's mostly an issue with flutter_wechat_assets_picker not pinning the version, so I'll raise the issue there, for anyone who runs into the same issue.


Font size not maintained after links

Text entered immediately after a link with a non-default font size reverts to the default font size. In order to give our users the most flexibility possible, we cannot use block scoped font sizing.
Steps for Reproduction

Visit this playground with font size and links.
Change the text size to small or large
Enter a bunch of text
Convert that text into a link
Enter text after the link noting that it is at normal font size

Expected behavior:
The text entered after the link should be small
Actual behavior:
The text entered after the link is normal size.
Platforms:
Chrome Version 130.0.6723.92 (Official Build) (arm64)
Version:
2.0.2

It's also when creating a new line or pressing enter


[PLC] [AST] [Builtin] Extensible builtins

It's a draft, no point to review yet.

Closed in favor of #1956.


[Expansion Panel] Shadow rendered incorrectly in Microsoft Edge

In Microsoft Edge the shadow around an expansion panel is not shown correctly (the shadow on the top and left are missing).

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
The shadow on the top and left is not rendered.

Expected Behavior 🤔
It should be rendered like Chrome/Firefox is doing.

Steps to Reproduce 🕹
Steps:

Open https://peepl.csb.app/

Your Environment 🌎

Tech
Version

Material-UI
v4.5.0

React
v16.10

Browser
Microsoft Edge

If it's okay, can I pick this ticket up? @oliviertassinari

@adeelibr Did you found a workaround? If it's easy to solve, sure! :)

Doing some research I found this helpful
https://stackoverflow.com/questions/22517621/css-box-shadow-around-entire-div-in-ie-11#comment34262865_22517621
Basically apply different styles for box-shadow on IE using media query which would only effect IE browser, the solution would be to increase the box-shadow more so it's more visible on IE.
your thoughts?


Newly installed instance could use incorrect "utf8" charset for MySQL

A default install could produce such app.ini:
APP_NAME=Gitea: Git with a cup of tea
RUN_USER=xiaoguang
RUN_MODE=prod

[database]
DB_TYPE=mysql
HOST=<IP_ADDRESS>:3306
NAME=gitea
USER=gitea
PASSWD=gitea
SCHEMA=
SSL_MODE=disable

CHARSET=utf8     !!!!!!!!!!!! wrong here

PATH=/Users/xiaoguang/work/gitea/data/gitea.db
LOG_SQL=false

"utf8mb4" is required for MySQL to work with emoji.

Keep it open for 1.20 .... it's a serious problem now ....

Could you backport #25413 ?

There is a separate PR #25432 for 1.20, while I do not understand why there was objection for backporting #25413 or what's the difference between them.

There is a separate PR #25432 for 1.20, while I do not understand why there was objection for backporting #25413 or what's the difference between them.

Now I can understand backporting #25413 will not break too much.


Navmesh mount dir

So it doesn't need to be included in the original tf2 files.

Implemented in dd84eacdec85259ec9c5f0a61ceddc55f18363e6, and I forgot to include the magic words in the commit message...


Add ducking, now playing display, multi-device control

Server minor and larger changes:

Add awareness of Spotify Connect playing on other devices
Transfer playback to local device before attempting playback
Add 5 second "auto ducking" when wakeword is heard
Add display of current track artist and title
Add support for simple 'Play Spotify' command

A bunch of tiny things but over all feels much better. Merging now.


Assignment Completion

braily pushed and submitted 1st, i struggled with the merge conflict but i think i fixed it, however im worried that my "push" overwrited braileys since i didnt get to pull his work before he pushed to github. please let me know if theres anything me or braily we need to do.


IndexConfig's factory 'create' method's supposed to be static?

Hi, good evening.
I'm revisiting issue #33 and I noticed that the create factory method of org.tinspin.index.IndexConfig is no static.
Could you please clarify if this change is intentional?

No, this is not intentional. It it actually quite embarrassing, it just goes to show that even seemingly simple changes deserve a unit test.
I already made a new release but it may take a day or so until it is indexed in the major maven search sites.
Thanks a lot for reporting!


[CONTRACT] add lock duration logic to the escrow

The lock function of the escrow should take as a parameter a minimum lock duration expressed in seconds.
The verification of compliance with this duration will be implemented later in a hook.

This way, a user who locks an amount in USDC must wait for a certain period before being able to withdraw their funds if no one has agreed to the exchange. However, a user who provides proof of an off-chain transfer can withdraw the funds without waiting.

I


add python-tk to Wily/Xenial

Links:

http://packages.ubuntu.com/xenial/python-tk
http://packages.ubuntu.com/xenial/python3-tk

Sorry, that was originally submitted as pyside stuff.


Shapely wheel link path for homebrew libgeos on OS X

I tried installing pip3 install shapely using the wheel for OS X 10.11 and found that the shared libraries were linked to a specified libgeos:
yesimon@oxygen /u/l/l/p/s/s/speedups> otool -L _speedups.cpython-35m-darwin.so
_speedups.cpython-35m-darwin.so:
        @loader_path/../.dylibs/libgeos-3.4.2.dylib (compatibility version 0.0.0, current version 0.0.0)
        @loader_path/../.dylibs/libgeos_c.1.dylib (compatibility version 10.0.0, current version 10.2.0)
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1197.1.1)

This results in the same error as SciTools/cartopy#738 when actually running.
I was able to get it to work by doing pip3 install --no-use-wheel shapely, which results in a different link:
yesimon@oxygen /u/l/l/p/s/s/speedups> otool -L _speedups.cpython-35m-darwin.so
_speedups.cpython-35m-darwin.so:
        /usr/local/opt/geos/lib/libgeos_c.1.dylib (compatibility version 11.0.0, current version 11.0.0)
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1226.10.1)

Perhaps adding the /usr/local/opt/geos is a reasonable during the link or maybe this should be included as a formula in Homebrew/homebrew-python.

@yesimon This is a packaging problem that will be fixed in 1.5.16 (#387).

@yesimon could you do me a big favor and test the new wheel I've just uploaded to Dropbox?
https://www.dropbox.com/s/jpvvxwc69xgqpzq/Shapely-1.5.15-cp35-cp35m-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl?dl=0
I've compiled the _vectorized and _speedups modules more carefully, linking only libgeos_c. It's looking good on my computer but I don't have a setup that will let me reproduce your problem with cartopy.

@sgillies It seems to work installing the latest version 1.5.16 from pypi. Thanks!

🎉 Thanks for your patience and thanks for following up!


ConcurrentModificationException when importing macros in nested parallels blocks

The fix for #159 just passes down the importedTemplates list to the embedded EvaluationContext. This fixes the problem that parallel blocks don't have access to macros imported into the outer context however, now we get a problem in the case where one is importing macros inside the parallels block. This is concurrently modifying the list of importedTemplates (and technically, is leaking inner macros to the outer context).

I can basically think of two easy ways to fix this. I created a pull request for each. Furthermore, they contain a test for this issue that does repeatable fail for me (depending on your hardware ymmv).
The difference between the two is that one (the "snapshot") makes it so that the macros included in an inner context are not "leaked" to its outer context while the other (the "copyonwrite") does still "leak".  Personally, I think the "leaking" is not what i would expect so I'd go with the "snapshot" patch but I don't feel very strongly either way.
Finally, the reason the test is writing in a bit of a roundabout way is that in case of a parallel tag, exceptions during the evaluation just bubble up to the Thread of the Executor (where they get swallowed) -- hence, from the outside (the template.eval) it looks like everything went ok while in reality a swallowed exception might have messed the result up. I think this is a bug in its own right which probably should be addressed in a separate issue/patch.

Good catch, thanks for both the test and the proposed solutions. I went with the "snapshot" technique but I adjusted where the list is copied so that it only occurs when using the "parallel" tag.


Model Previews No Longer Showing After Update

They worked up until about two-three days ago.
There are no errors in the log. Simply - no lora previews anymore. I'm not sure what is going on?
File "C:\Users\jlynn\AppData\Local\Programs\Python\Python311\Lib\site-packages\aiohttp\web_protocol.py", line 462, in _handle_request
resp = await request_handler(request)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\jlynn\AppData\Local\Programs\Python\Python311\Lib\site-packages\aiohttp\web_app.py", line 537, in _handle
resp = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\jlynn\AppData\Local\Programs\Python\Python311\Lib\site-packages\aiohttp\web_middlewares.py", line 114, in impl
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "D:\AI\ComfyUI\server.py", line 61, in cache_control
response: web.Response = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "D:\AI\ComfyUI\server.py", line 109, in origin_only_middleware
response = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "D:\AI\ComfyUI\server.py", line 73, in cors_middleware
response = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "D:\AI\ComfyUI\custom_nodes\ComfyUI-Custom-Scripts\py\better_combos.py", line 58, in get_examples
pos = name.index("/")
^^^^^^^^^^^^^^^
ValueError: substring not found
Error handling request
Traceback (most recent call last):
File "C:\Users\jlynn\AppData\Local\Programs\Python\Python311\Lib\site-packages\aiohttp\web_protocol.py", line 462, in _handle_request
resp = await request_handler(request)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\jlynn\AppData\Local\Programs\Python\Python311\Lib\site-packages\aiohttp\web_app.py", line 537, in _handle
resp = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\jlynn\AppData\Local\Programs\Python\Python311\Lib\site-packages\aiohttp\web_middlewares.py", line 114, in impl
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "D:\AI\ComfyUI\server.py", line 61, in cache_control
response: web.Response = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "D:\AI\ComfyUI\server.py", line 109, in origin_only_middleware
response = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "D:\AI\ComfyUI\server.py", line 73, in cors_middleware
response = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "D:\AI\ComfyUI\custom_nodes\ComfyUI-Custom-Scripts\py\better_combos.py", line 58, in get_examples
pos = name.index("/")
^^^^^^^^^^^^^^^
ValueError: substring not found
Error handling request
Traceback (most recent call last):
File "C:\Users\jlynn\AppData\Local\Programs\Python\Python311\Lib\site-packages\aiohttp\web_protocol.py", line 462, in _handle_request
resp = await request_handler(request)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\jlynn\AppData\Local\Programs\Python\Python311\Lib\site-packages\aiohttp\web_app.py", line 537, in _handle
resp = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\jlynn\AppData\Local\Programs\Python\Python311\Lib\site-packages\aiohttp\web_middlewares.py", line 114, in impl
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "D:\AI\ComfyUI\server.py", line 61, in cache_control
response: web.Response = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "D:\AI\ComfyUI\server.py", line 109, in origin_only_middleware
response = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "D:\AI\ComfyUI\server.py", line 73, in cors_middleware
response = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "D:\AI\ComfyUI\custom_nodes\ComfyUI-Custom-Scripts\py\better_combos.py", line 58, in get_examples
pos = name.index("/")
^^^^^^^^^^^^^^^
ValueError: substring not found
Error handling request
Traceback (most recent call last):
File "C:\Users\jlynn\AppData\Local\Programs\Python\Python311\Lib\site-packages\aiohttp\web_protocol.py", line 462, in _handle_request
resp = await request_handler(request)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\jlynn\AppData\Local\Programs\Python\Python311\Lib\site-packages\aiohttp\web_app.py", line 537, in _handle
resp = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\jlynn\AppData\Local\Programs\Python\Python311\Lib\site-packages\aiohttp\web_middlewares.py", line 114, in impl
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "D:\AI\ComfyUI\server.py", line 61, in cache_control
response: web.Response = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "D:\AI\ComfyUI\server.py", line 109, in origin_only_middleware
response = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "D:\AI\ComfyUI\server.py", line 73, in cors_middleware
response = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "D:\AI\ComfyUI\custom_nodes\ComfyUI-Custom-Scripts\py\better_combos.py", line 58, in get_examples
pos = name.index("/")
^^^^^^^^^^^^^^^

Harley NO the<PHONE_NUMBER>99000
On Mon, Sep 9, 2024 at 5:57 PM Evilander @.***> wrote:

They worked up until about two-three days ago.
There are no errors in the log. Simply - no lora previews anymore. I'm not
sure what is going on?
—
Reply to this email directly, view it on GitHub
https://github.com/pythongosssss/ComfyUI-Custom-Scripts/issues/344, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BE7VXHOVYT4OYFSKX7RSAGLZVYKTZAVCNFSM6AAAAABN5N7T32VHI2DSMVQWIX3LMV43ASLTON2WKOZSGUYTIOJZGY4DGOA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

😃
Cody Reichenbach reacted via Gmail
https://www.google.com/gmail/about/?utm_source=gmail-in-product&utm_medium=et&utm_campaign=emojireactionemail#app
On Tue, Sep 10, 2024 at 9:23 PM Cody Reichenbach @.***>
wrote:

Harley NO the<PHONE_NUMBER>99000
On Mon, Sep 9, 2024 at 5:57 PM Evilander @.***> wrote:

They worked up until about two-three days ago.
There are no errors in the log. Simply - no lora previews anymore. I'm
not sure what is going on?
—
Reply to this email directly, view it on GitHub
https://github.com/pythongosssss/ComfyUI-Custom-Scripts/issues/344, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BE7VXHOVYT4OYFSKX7RSAGLZVYKTZAVCNFSM6AAAAABN5N7T32VHI2DSMVQWIX3LMV43ASLTON2WKOZSGUYTIOJZGY4DGOA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

🧑🎄
Cody Reichenbach reacted via Gmail
https://www.google.com/gmail/about/?utm_source=gmail-in-product&utm_medium=et&utm_campaign=emojireactionemail#app
On Tue, Sep 10, 2024 at 9:23 PM Cody Reichenbach @.***>
wrote:

Harley NO the<PHONE_NUMBER>99000
On Mon, Sep 9, 2024 at 5:57 PM Evilander @.***> wrote:

They worked up until about two-three days ago.
There are no errors in the log. Simply - no lora previews anymore. I'm
not sure what is going on?
—
Reply to this email directly, view it on GitHub
https://github.com/pythongosssss/ComfyUI-Custom-Scripts/issues/344, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BE7VXHOVYT4OYFSKX7RSAGLZVYKTZAVCNFSM6AAAAABN5N7T32VHI2DSMVQWIX3LMV43ASLTON2WKOZSGUYTIOJZGY4DGOA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Sorry - confused.

How do you resolve this bug?
i am still having this problem.Loras and CheckPoints are not loading for me.

Confirm. Lora/Checkpoint info is not working after the update.


Add more type hints to make mypy lint more

I've just learned about python/mypy#4409 and in general, mypy doesn't type check a function if it has no annotations, so you need to often include an explicit return type to do so.
I also forgot that dict and list are type-checked starting from Python 3.9, so I removed the use of Dict and List.

Sounds great, thank you!


Provide the implementation as a custom io.Writer

Hi,
Is there a possibility or a plan to provide the Logrus implementation as a custom io.Writer that can be used in conjonction with the standard library logger ?
https://godoc.org/github.com/Sirupsen/logrus#StdLogger is nice but it still makes the package depend on Logrus, only to get the interface.
I'm discussing the issue here: https://github.com/ant0ine/go-json-rest/issues/62
Thanks,
Antoine

I'm in favor of logrus implementing the io.Writer interface. The reason for this is that many libraries use the default logger (e.g. log.Println("foo")). By allowing us to set the default logger to send to logrus, we can take advantage of logrus's hooks. This can be very important if the we are using the hooks to send to multiple destinations.

#103 implemented this!
Thanks @phemmer :heart:


Generating walls

Hold off on reviewing this until MCS-33 has been merged into master. I think I'm going to have to do a touch of refactoring then

Maybe it would be better to merge master into this branch and resolve conflicts here?

Maybe it would be better to merge master into this branch and resolve conflicts here?

I plan on doing that- but I want your merges into master first. Which is why I requested a delay

Oh, right, MCS-33. Sorry, failure to read.

@ThomasSchellenbergNextCentury @rartiss55 @brianpippin  Why don't we go ahead and review this? Its been waiting long enough

Sorry Billy, I thought we were waiting to merge Chris's PR first.  I'll take a look at it now.

@chrislong Can you review this? I was seeing errors with Goal Generation using this code.

@wagnerwj Sure, I'll take a look

Good for me as well unless Chris has anything.


*: remove last remainers of non-second metrics

:+1:

Travis seems to have file system issues for go 1.5.4 builds – other one passing though.


Removing dead code in RecoveryTarget.

This code in RecoveryTarget is not invoked, all of these methods are implemented by the parent ReplicationTarget with the same behavior.
Signed-off-by: Marc Handalian<EMAIL_ADDRESS>Description
[Describe what this change achieves]
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Gradle Check (Jenkins) Run Completed with:

RESULT:  ❌
URL: https://build.ci.opensearch.org/job/gradle-check/2035/
CommitID: 574122e

> Task :libs:opensearch-grok:compileTestJava
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.

File system event consumer thread stopped due to exception
java.lang.NullPointerException: Cannot invoke "Object.hashCode()" because "key" is null
	at java.****/java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:936)
	at org.gradle.internal.watch.registry.impl.DefaultFileWatcherProbeRegistry.triggerWatchProbe(DefaultFileWatcherProbeRegistry.java:93)
	at org.gradle.internal.watch.registry.impl.AbstractFileWatcherUpdater.triggerWatchProbe(AbstractFileWatcherUpdater.java:118)
	at org.gradle.internal.watch.registry.impl.DefaultFileWatcherRegistry$1.handleChangeEvent(DefaultFileWatcherRegistry.java:88)
	at net.rubygrapefruit.platform.internal.jni.AbstractFileEventFunctions$ChangeEvent.handleEvent(AbstractFileEventFunctions.java:266)
	at org.gradle.internal.watch.registry.impl.DefaultFileWatcherRegistry.lambda$createAndStartEventConsumerThread$0(DefaultFileWatcherRegistry.java:84)
	at java.****/java.lang.Thread.run(Thread.java:833)
Exception in thread "Thread-1500" java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
	at net.rubygrapefruit.platform.internal.jni.AbstractFileEventFunctions$NativeFileWatcher.executeRunLoop0(Native Method)
	at net.rubygrapefruit.platform.internal.jni.AbstractFileEventFunctions$NativeFileWatcher.access$100(AbstractFileEventFunctions.java:159)
	at net.rubygrapefruit.platform.internal.jni.AbstractFileEventFunctions$NativeFileWatcher$1.run(AbstractFileEventFunctions.java:173)

Codecov Report

Merging #4278 (574122e) into main (5327767) will increase coverage by 0.14%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##               main    #4278      +/-   ##
============================================
+ Coverage     70.63%   70.78%   +0.14%
- Complexity    57168    57281     +113
============================================
  Files          4610     4610
  Lines        275118   275105      -13
  Branches      40284    40283       -1
============================================
+ Hits         194339   194723     +384
+ Misses        64431    64080     -351
+ Partials      16348    16302      -46

Impacted Files
Coverage Δ

...rg/opensearch/indices/recovery/RecoveryTarget.java
72.90% <ø> (+0.87%)
:arrow_up:

.../indices/replication/common/ReplicationTarget.java
80.00% <100.00%> (ø)

...pensearch/action/ingest/DeletePipelineRequest.java
31.25% <0.00%> (-37.50%)
:arrow_down:

...n/decider/SnapshotInProgressAllocationDecider.java
34.78% <0.00%> (-34.79%)
:arrow_down:

...ensearch/client/indices/DetailAnalyzeResponse.java
20.54% <0.00%> (-34.25%)
:arrow_down:

...nsearch/index/shard/IndexShardClosedException.java
66.66% <0.00%> (-33.34%)
:arrow_down:

...ava/org/opensearch/threadpool/ThreadPoolStats.java
52.00% <0.00%> (-29.34%)
:arrow_down:

.../java/org/opensearch/index/reindex/RemoteInfo.java
51.37% <0.00%> (-28.45%)
:arrow_down:

...va/org/opensearch/monitor/process/ProcessInfo.java
68.00% <0.00%> (-24.00%)
:arrow_down:

...a/org/opensearch/search/profile/ProfileResult.java
69.23% <0.00%> (-23.08%)
:arrow_down:

... and 499 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


[Enhancement] Avoid global namespace pollution

The saved variables names selected are too generic.
MiniMapDB
KeyboardPosition
MousePosition
ShowEmptyBinds
ShowInterfaceBinds
KeyBindSettings
KeyBindSettingsMouse
MouseKeyEditLayouts
KeyboardEditLayouts
CurrentLayoutMouse
CurrentLayoutKeyboard
tutorialCompleted
These are all put in the global namespace after ADDON_LOADED fires for KeyUI.
That means they can overwrite or get overwritten by other addons leading to really hard to debug issues.
I'm not mentioning the KeyUI_Settings variable because that one is actually properly named <addonname>_suffix is a good naming scheme because the addonname is always unique for a specific player's installation (you cannot have 2 folders with the same name in \AddOns).
The solution to this problem can be one of

Prefix the existing variables with KeyUI_
Tuck them inside the KeyUI_Settings variable (I would go with this)
The second one will also make the variables migration quite easy.

So they would be
KeyUI_Settings.MinimapDB
KeyUI_Settings.KeyboardPosition
..
etc.

“Thank you for your advice! This is my first coding project, so I’m still learning as I go. I really appreciate your feedback and am open to any suggestions you may have!

It's a well made addon, especially for a first project 😄
Code is fairly clean and for the most part well encapsulated, you're using the ... vararg passed in by the client to namespace your functions etc.
So lots of things already done well.
The saved variables thing catches a lot of people out in their first projects, because it's natural to assume they are something unique to your addon.
Unfortunately they are not they are just Lua arrays / tables no different to any other array / table.
You can do /dump MiniMapDB in-game and it will print that array contents to chat.
You can do /run MiniMapDB={} and it will reset it.
Other addons can accidentally do that if they are leaking a MiniMapDB variable or using it as a name for their own minimap settings.
In the latter case, if two addons are using the same name to reference their minimap settings, the one that loads last (alphabetic order) will overwrite the first one, or more likely try to use the other addon's settings
So like you do in your actual code trying to encapsulate variables and functions and keep them local to your addon the same applies to saved variable table names.

I'll try send a pull request so you can see it in practice.

That's a hard one but i am mostly done.

Something I would like to point out if it helps.
You are already using this facility but not fully 😺
The wow client passes into every Lua file referenced in the .toc of an addon a vararg ...
First argument is the addon folder name and second argument is a Lua array that is shared between all the addon files without being global
It is a - particular to WoW - "my addon scope".
local addonName, addon = ...

on top of your Lua files lets you pass around variables (including methods, other tables etc) without having to put them in the global namespace.
So let's say you have an inCombat boolean that you want to use in two of your addon files but does not need to persist in saved variables.
addon.inCombat = true

in file1.lua is perfectly accessible in file2.lua so long as it also has assigned the local addonName, addon = ... at the top.

I’m grateful for your input and have now implemented almost everything. There are still a few variables I’m not fully satisfied with, but I’m working on them.
Would you be interested in taking a quick look?

Looks good 👍🏻


Google Calendar integration

FullCalendar.io allows for users to call from the Google Calendar API and renders the data in a way that it can be displayed on the calendar. I'm currently building this capability with react-big-calendar on a client project and could create a branch for this if you want.

That's really cool! Generally we don't want that sort of thing built into the library but I think we already provide all the API's necessary for it to be a standalone addon or wrapper over the core Calendar component. I'd be happy to promote or bump such a project in the docs as a good companion to RBC if you build it!

Sounds good. Getting the events is easy....now to writing the recursion logic.

+1 for the Google Calendar integration

@simondegheselle I'm starting to built a function to handle it if you want to try it out and test its capabilities.

I built an implementation for Google, which is basically just using a handful of functions to display events from Google calendars in react-big-calendar.


Travis CI can't run Flow

Since about 2019-07-16, last week, all builds in Travis CI have been failing in Flow. The error looks like:
Running flow...
/home/travis/build/zulip/zulip-mobile/node_modules/flow-bin/flow-linux64-v0.78.0/flow: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.17' not found (required by /home/travis/build/zulip/zulip-mobile/node_modules/flow-bin/flow-linux64-v0.78.0/flow)

In other words, the glibc on the system isn't new enough!?
The first failure on master was https://travis-ci.org/zulip/zulip-mobile/builds/559639646 . The last success on master was https://travis-ci.org/zulip/zulip-mobile/builds/559192039 . (I'm getting the sequence from this history page.)
We haven't changed Flow versions, or any Travis configuration that could possibly affect this. In particular, the difference between the commits at that last success and first failure is:
$ git diff --stat 2407f3f9c..ce4ed6ab2
 src/webview/js/generatedEs3.js      | Bin 15766 -> 15823 bytes
 src/webview/js/js.js                |   3 +++
 src/webview/webViewHandleUpdates.js |  17 +++++++++--------
 3 files changed, 12 insertions(+), 8 deletions(-)

Looking at the Worker information and Build system information at the top of the logs, there are interesting differences. Here's the last success:
Worker information
hostname<EMAIL_ADDRESS>version: v6.2.0 https://github.com/travis-ci/worker/tree/5e5476e01646095f48eec13196fdb3faf8f5cbf7
instance: travis-job-b8f5e50c-4675-4230-9739-77d8d7683428 travis-ci-cookiecat-trusty-1503974222 (via amqp)
startup: 6.386011955s
system_info

Build system information
Build language: android
Build group: stable
Build dist: trusty
Build id: 559192039
Job id: 559192040
Runtime kernel version: 4.4.0-93-generic
travis-build version: e88137ff9
Build image provisioning date and time
Tue Aug 29 03:00:05 UTC 2017
Operating System Details
Distributor ID:	Ubuntu
Description:	Ubuntu 14.04.5 LTS
Release:	14.04
Codename:	trusty

And the first failure:
Worker information
hostname<EMAIL_ADDRESS>version: v6.2.0 https://github.com/travis-ci/worker/tree/5e5476e01646095f48eec13196fdb3faf8f5cbf7
instance: travis-job-0e355844-d892-46eb-b4ef-60702acd2233 precise-android-stable-alternative (via amqp)
startup: 6.533831823s
system_info

Build system information
Build language: android
Build group: stable
Build dist: xenial
Build id: 559639646
Job id: 559639647
Runtime kernel version: 3.13.0-100-generic
travis-build version: a82bb1cfc
Build image provisioning date and time
Thu Nov 10 02:43:40 UTC 2016
Operating System Details
Distributor ID:	Ubuntu
Description:	Ubuntu 12.04.5 LTS
Release:	12.04
Codename:	precise

In other words, we were on Ubuntu 14.04 trusty -- as seen in the instance name, "Build dist", and "Operating System Details". Then "Build dist" changed to refer to the newer Ubuntu 16.04 xenial... but the instance name and the "Operating System Details" indicate a downgrade, to Ubuntu 12.04 precise.
Looking at a few other recent failing builds, they have the same pattern of xenial-but-precise.
Trusty is now several months past EOL, so it's more than reasonable for Travis to move to Xenial. But by the same token, moving to Precise, two years older, is completely broken... and it looks like that's what they've actually done for us.
I first noticed this on PR #3561: https://github.com/zulip/zulip-mobile/pull/3561#issuecomment-513405783 but because that PR upgraded Flow, I assumed it was Flow that had changed and not Travis.
More investigation required.

OK:

This support-forum thread is helpful: https://travis-ci.community/t/travis-builds-failing-due-to-discrepancy-between-worker-instance-and-dist-version/3693/5
Indeed, adding dist: trusty fixes it -- it seems to restore the status quo.
I also posted https://travis-ci.community/t/android-builds-default-to-precise-which-is-2-years-eol/4352 to pose the bug more precisely (ha) and request they actually fix it.

I'll push the dist: trusty fix shortly.


videojs cant't  catch ended event when player seek forward until ending

I'll try to implement a PR for this, but a solution I got working is below:
var seekStep = 5; //how many seconds to seek with arrow keys
player.hotkeys({
    seekStep: 0, //manually handle this below
    rewindKey: function(event, player) {
	    event.preventDefault();

	    var time = player.currentTime();
	    if (event.which == 37) { //left arrow
		    player.currentTime(time-seekStep);
	    }
	    return false;
    },
    forwardKey: function(event, player) {
	    event.preventDefault();

	    var time = player.currentTime();
	    if (event.which == 39 && time+seekStep <= duration) { //right arrow
		    player.currentTime(time+seekStep);
	    } else if (event.which == 39) {
		    player.currentTime(duration);
	    }
	    return false;
    }
});


io.rancher.scheduler.require_any label is case sensitive.

Rancher Versions: Build from master
Steps to reproduce the problem:
Host has label hello=test and io.rancher.scheduler.require_any=test1=value3
Create a service with label ``test1=VALUE3and host affinity to hello=test```.
Containers are not able to get deployed in this host.

Tested with latest build from master, rancher/scheduler:v0.7.1 and rancher/network-manager:v0.4.6 .
io.rancher.scheduler.require_any label is case insensitive.
Tested with having - io.rancher.scheduler.require_any=MYKEY1=VALUE1 set of host.
Containers with following labels get scheduled on this host:
MYKEY1=value1
mykey1=VALUE1
mykey1=value1


add --filter option to ciao-cli

while the go template support makes scripting more useful for people who know golang, it would be nice to provide an option for people who want to script without golang or to just reduce the amount of output. Implement a --filter option to filter on a struct field.

I noticed recently that we do have some filter ability tied to the pager interface, but not all output goes through the pager.  Could we move the filtering up out of the pager?  I was thinking an extended variant of ctl.ds.GetWorkload() such as "GetFilteredWorkload()" or extending GetAllInstances()/GetAllInstancesFromTenant() into a GetAllInstancesFiltered().  Beyond tenant and the pager's filter on flavor there are a variety of useful filter options such as image, name, status, ip, and "tags".  Filtering at the highest level would be best for performance, as subsequent operations should have less through which to iterate.

this request is not for filtering at the api, but at the cli level.

Filtering at the API level would be filtering on data contents.  The request here is for filtering to only display the data of certain data fields by name.

This is now possible for one field at a time using a template, e.g.,
$ ciao-cli workload list -f '{{select . "Name"}}'
Fedora 24 Cloud
Clear Cloud
Docker Debian latest
Docker Iperf

select can be combined with filter to actually filter.  For example,
# ciao-cli workload list -f '{{select (filter . "Disk" "") "Name"}}'
Fedora 24 Cloud
Clear Cloud

Displays the names of the workloads that have no image associated with them, i.e., the VM images.
Do filter and select cover the issues raised by this bug? If so I'll add some examples to the README.md and we can close.

@kaccardi I think we should close this.  It's much easier to filter by template than it was when we first entered this bug.


new issue

test
test
test
test
test

Hi, I have some suggestions to help solving this issue!
Here is a list of similar issues:

1. [new issue](https://github.com/fjsj/python-social-auth/issues/39)

2. [new issue](https://github.com/fjsj/python-social-auth/issues/39)

3. [new issue](https://github.com/fjsj/python-social-auth/issues/39)

4. [new issue](https://github.com/fjsj/python-social-auth/issues/39)

5. [new issue](https://github.com/fjsj/python-social-auth/issues/39)

Hope this is useful!
Cheers,
Cinnabot.


feat(locker): Track the liquidity locked by token address

Resolves #106
Covered all the description and have done the changes

Some stuff missing

Documentation not updated / not accurate
The token_locks list is never appended to
remove_user_lock function name and documentation not updated to reflect the new behavior
Once a token is fully unlocked, it's not removed from the token_locks list

Thank you @enitrat , I have addressed all these in the new commit.


Attempt to use Servers->Databases. Error: "Object Exporer task didn't complete within 45 seconds"

Issue Type: Bug

Connected to a Server
Trying to use Servers > Databases
Getting error "Object Explorer task didn't complete within 45 seconds"

It does not seem that listing the DBs should take any significant amount of time unless it also attempts to run some metadata queries on each DB.
Azure Data Studio version: Azure Data Studio 1.6.0 (eb35dae1d1238e03f1cab3bd45e151f381b22aef, 2019-04-17T06:14:17.039Z)
OS version: Darwin x64 18.5.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz (8 x 2200)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: enabledrasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 2

Memory (System)
16.00GB (10.68GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions: none

@mayurrumal1 are there any relevant details regarding the server you're connecting to?  e.g. is it a Azure SQL DB with low DTU, is the server generally responsive otherwise, etc?.

@mayurrumal1 are there any relevant details regarding the server you're connecting to? e.g. is it a Azure SQL DB with low DTU, is the server generally responsive otherwise, etc?.

I am getting this issue as well. And it's not just on small databases and elastic pools, but even ones with 20 vcores, and pretty much zero traffic going to them.
This looks like a bug within the application

I have had this issue for a few days now (on Azure Data Studio v.1.32.0).  It's an odd error - it looks like the server is connected (green icon), no connection errors - but the same message as above.
I managed to resolve it by:

Re-opening Azure Data Studio
Reconnect user (go through authentication)

Reconnect to the server

Still having this issue in 2022...

Kindly update your Azure data studio. Fixed the issue on my end.

I’m only happy that my response has helped someone. 😊 With love from Uganda 🇺🇬 .

@cmorris98 What type of server (Azure/On-Prem) are you trying to connect to?

So this is an on-prem server. But turns out I am now suspecting a slow corporate vpn that I am using to access it. For smaller databases it works no problem. But for our larger one it will timeout. And yesterday it magically worked on the larger DB. I have noticed over the last few weeks that our corporate VPN has become painfully slow. Is there a config option we can use to set the timeout period?

This is still happening to Version 1.39.1

Same error: "Object Exporer task didn't complete within 45 seconds"
Version: 1.39.1 (system setup)
Commit: 7553f799e175f471b7590302dd65c997b838b29b
Date: 2022-08-30T01:11:13.047Z
VS Code: 1.62.0
Electron: 13.6.6
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.19043

version 1.39.1
... error still present.

Same problem here!

Same problem here, very annoying. I really want to keep using azure data studio, but this makes it really difficult :(

Still having this issue on 1.39.1

It'd be nice if I'm able to configure this timeout but since it is hardcoded somewhere, it basically prevents from using it :-(

I'm copying my post over from #20321 as it was deemed a duplicate and closed.
Issue Type: Bug
I've successfully connected to a SQL Server that has 3 databases on it. I only have access to 2 of those databases (i.e. I have a SQL Login for the SQL Server, but I only have a SQL User for 2 out of those 3 databases).
The object explorer fails to load. I've faced a similar issue in the past and i've fixed it by creating a SQL User for my SQL Login for all of the databases on the server.
The problem is in this case I can't create a SQL User for myself because my organization (reasonably) doesn't want to give me access to databases I don't need access to simply because my RDBMS client has a glitch.
This is on Azure Data Studio for Mac. I've connected to the same server using SQL Server Management Studio on a windows machine and the object explorer works fine.
The SQL Server I'm connecting to is hosted on Azure, and the databases are Azure SQL databases, if that makes any difference.
I've attached the log files and system info below
console.log
20221116T184908.zip
Azure Data Studio Version Info:
Version: 1.40.0
Commit: https://github.com/microsoft/azuredatastudio/commit/3fbaa3de931ef433090fe3deb8c89cba99d7952b
Date: 2022-11-11T22:47:49.772Z
VS Code: 1.67.0
Electron: 17.4.11
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 22.1.0
System Information:
CPUs	Apple M1 (8 x 24)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled metal: disabled_off multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_renderer: enabled_on video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled
Load (avg)	2, 2, 2
Memory (System)	8.00GB (0.04GB free)
Process Argv
Screen Reader	no
VM	0%
Enabled extensions:
Extension	Author (truncated)	Version
admin-pack	Mic	0.0.2
agent	Mic	0.49.0
azuredatastudio-postgresql	Mic	0.2.7
dacpac	Mic	1.11.0
import	Mic	1.5.3
profiler	Mic	0.11.0
Please let me know if you need any more info. Thanks,
Zach