Maven Azure Web App Plugin Endgame 1.4.1

Build

[x] 10/8 - Build and push jar files to stage repository @SummerSun

Test

[ ] 10/9 - Run Test Plan @bsaby

The {id} is commicrosoftazure-2640

Release

[ ] Add 1.4.1 tag for web app @SummerSun
[ ] Add 1.2.1 tag for library module @SummerSun
[ ] Release to maven central @SummerSun

Run Test Plan
Build:1.4.1
No new issue found
Test results:

Case
Details
Issue

Can deploy to Web App on windows
Pass

Can Auto detect deployment type
Pass

Can deploy to Deployment Slot on Windows
Pass

Can deploy to Web App on Linux
Pass

Can deploy to Deployment Slot on Linux
Pass

Can deploy to Web App on Linux with public Docker Hub container image
Pass

Can deploy to Deployment Slot on Linux with public DockerHub container image
Pass

Can deploy to Web App on Linux with private Docker Hub container image
Pass

Can deploy to Deployment Slot on Linux with private DockerHub container image
Pass

Can deploy to Web App on Linux with Docker container image in private container registry
Pass

Can deploy to Deployment Slot on Linux with docker container image in private container registry
Pass

Can deploy Web App to existing App Service Plan
Pass

Released to maven central:

https://repo.maven.apache.org/maven2/com/microsoft/azure/azure-webapp-maven-plugin/1.4.1
https://repo.maven.apache.org/maven2/com/microsoft/azure/azure-maven-plugin-lib/1.2.1/


list of api commands in wiki

Where are you using pytradfri
standalone
Version of pytradfri
current sync version
Expected behaviour
Actual behaviour
Can't there be a list of api commands added to the wiki or docs included in the package.
I am trying to simply switch on and off sockets from my pi though can't find the commands to do so.
Using the sync version

No reply for a long while, closing issue.


Duplicate occurrences in DWCA export

There are around a million duplicate occurrences in the exported DWCA:
$ grep '67484466' observations.csv

67484466,https://www.inaturalist.org/observations/67484466,HumanObservation,2021-01-06T10:40:51Z,iNaturalist,Observations,iNaturalist research-grade observations,,67484466,https://www.inaturalist.org/observations/67484466,,Patrick HAFFNER,,Patrick HAFFNER,,wild,2018-06-10T14:00:00+02:00,12:00:00Z,2018/06/10 2:00 PM CEST,"45290 Nogent-sur-Vernisson, France",47.8494966667,2.7463083333,,EPSG:4326,FR,Centre,148829729,2021-01-02T23:38:24Z,"",61532,Propylea
quatuordecimpunctata,species,Animalia,Arthropoda,Insecta,Coleoptera,Coccinellidae,Propylea,http://creativecommons.org/licenses/by-nc/4.0/,Patrick HAFFNER,patrickhaffner,,,,""

67484466,https://www.inaturalist.org/observations/67484466,HumanObservation,2021-01-06T10:40:51Z,iNaturalist,Observations,iNaturalist research-grade observations,,67484466,https://www.inaturalist.org/observations/67484466,,Patrick HAFFNER,,Patrick HAFFNER,,wild,2018-06-10T14:00:00+02:00,12:00:00Z,2018/06/10 2:00 PM CEST,"45290 Nogent-sur-Vernisson, France",47.8494966667,2.7463083333,,EPSG:4326,FR,Centre,148829729,2021-01-02T23:38:24Z,"",61532,Propylea quatuordecimpunctata,species,Animalia,Arthropoda,Insecta,Coleoptera,Coccinellidae,Propylea,http://creativecommons.org/licenses/by-nc/4.0/,Patrick HAFFNER,patrickhaffner,,,,""

We can handle some situations with duplicate rows in DWCAs, but not where there are extensions.
The current archive generated on 18 May is affected. I think the last one without these duplicates was 30 March (see https://registry.gbif.org/dataset/50c9509d-22c7-4a22-a47d-8c48425ef4a7/ingestion-history and compare the count for DWCA_TO_VERBATIM with VERBATIM_TO_INTERPRETED).
CC @muttcg, @CecSve, https://github.com/gbif/portal-feedback/issues/4094

This should be fixed now. That last several weekly exports haven't had duplicate occurrences, and hopefully that remains the case going forward


Set crop parameter default to False

Proposed changes
Include a brief description of the changes being proposed, and why they are necessary.
Checklist (replace [ ] with [x] to check off)

[ ] Remove any unused Python packages from Load packages
[ ] Remove any unused/empty code cells
[ ] Remove any guidance cells (e.g. General advice)
[ ] Ensure that all code cells follow the PEP8 standard for code. The jupyterlab_code_formatter tool can be used to format code cells to a consistent style: select each code cell, then click Edit and then one of the Apply X Formatter options (YAPF or Black are recommended)
[ ] Include relevant tags in the first notebook cell and re-use tags if possible
[ ] Ensure appropriate colour schemes  have been used to maximise accessibility for vision impairment. Test your images or learn more with Coblis or TPGI
[ ] Clear all outputs, run notebook from start to finish, and save the notebook in the state where all cells have been sequentially evaluated

Closes issues (optional)

Closes Issue #000

Hey @vikineema! Any chance you could provide some extra info on this change, e.g. reasons for turning it off by default? I'd love to know if you've had any bad experiences with this functionality or any feedback that I could use to improve it (it should make larger analyses a lot quicker).

Neat, thankyou! Will investigate 🙂


Describe the bug
Steps to reproduce the behavior:
When the main program of the Palworld server is running, the Docker log will keep prompting crazily: (Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING: Destination buffer appears to be in uncached or write-combined memory! This is extremely slow. See "How do I decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.) And the characters will be very laggy after entering the server.
OS information (IMPORTANT)

OS:  Ubuntu 24.04 LTS (GNU/Linux 6.8.0-51-generic x86_64)
Palworld Version:  <IP_ADDRESS>723
Docker Image Version:  Ubuntu Core 22 - 27.2.0 - 1.46

Hardware information (IMPORTANT)

CPU:  Intel Xeon E5 2699V4
Memory: 256GB REG ECC

docker-compose.yml contents (IMPORTANT)

docker-compose.yml
# [
    {
        "Id": "47004ef44ce2e4b593b1745c76f38178f3fa3461c3f48b5a394109b1b10ff879",
        "Created": "2024-12-27T00:01:42.644425291Z",
        "Path": "/home/steam/server/init.sh",
        "Args": [],
        "State": {
            "Status": "running",
            "Running": true,
            "Paused": false,
            "Restarting": false,
            "OOMKilled": false,
            "Dead": false,
            "Pid": 26763,
            "ExitCode": 0,
            "Error": "",
            "StartedAt": "2024-12-27T00:01:42.852265153Z",
            "FinishedAt": "0001-01-01T00:00:00Z",
            "Health": {
                "Status": "healthy",
                "FailingStreak": 0,
                "Log": [
                    {
                        "Start": "2024-12-27T00:06:18.964547354Z",
                        "End": "2024-12-27T00:06:19.562756133Z",
                        "ExitCode": 0,
                        "Output": ""
                    },
                    {
                        "Start": "2024-12-27T00:06:49.564363608Z",
                        "End": "2024-12-27T00:06:50.177718892Z",
                        "ExitCode": 0,
                        "Output": ""
                    },
                    {
                        "Start": "2024-12-27T00:07:20.179058067Z",
                        "End": "2024-12-27T00:07:20.79118215Z",
                        "ExitCode": 0,
                        "Output": ""
                    },
                    {
                        "Start": "2024-12-27T00:07:50.793039025Z",
                        "End": "2024-12-27T00:07:51.401569107Z",
                        "ExitCode": 0,
                        "Output": ""
                    },
                    {
                        "Start": "2024-12-27T00:08:21.406230683Z",
                        "End": "2024-12-27T00:08:22.03092027Z",
                        "ExitCode": 0,
                        "Output": ""
                    }
                ]
            }
        },
        "Image": "sha256:332d5ea24c4b1f8a33a2024ba64111ff7a60e453236adc7c05d570d91b06efc7",
        "ResolvConfPath": "/var/snap/docker/common/var-lib-docker/containers/47004ef44ce2e4b593b1745c76f38178f3fa3461c3f48b5a394109b1b10ff879/resolv.conf",
        "HostnamePath": "/var/snap/docker/common/var-lib-docker/containers/47004ef44ce2e4b593b1745c76f38178f3fa3461c3f48b5a394109b1b10ff879/hostname",
        "HostsPath": "/var/snap/docker/common/var-lib-docker/containers/47004ef44ce2e4b593b1745c76f38178f3fa3461c3f48b5a394109b1b10ff879/hosts",
        "LogPath": "/var/snap/docker/common/var-lib-docker/containers/47004ef44ce2e4b593b1745c76f38178f3fa3461c3f48b5a394109b1b10ff879/47004ef44ce2e4b593b1745c76f38178f3fa3461c3f48b5a394109b1b10ff879-json.log",
        "Name": "/palworld",
        "RestartCount": 0,
        "Driver": "overlay2",
        "Platform": "linux",
        "MountLabel": "",
        "ProcessLabel": "",
        "AppArmorProfile": "unconfined",
        "ExecIDs": null,
        "HostConfig": {
            "Binds": [
                "/home/yaya/palworld:/palworld:rw"
            ],
            "ContainerIDFile": "",
            "LogConfig": {
                "Type": "json-file",
                "Config": {}
            },
            "NetworkMode": "host",
            "PortBindings": {},
            "RestartPolicy": {
                "Name": "on-failure",
                "MaximumRetryCount": 0
            },
            "AutoRemove": false,
            "VolumeDriver": "",
            "VolumesFrom": null,
            "ConsoleSize": [
                0,
                0
            ],
            "CapAdd": null,
            "CapDrop": null,
            "CgroupnsMode": "private",
            "Dns": null,
            "DnsOptions": null,
            "DnsSearch": null,
            "ExtraHosts": null,
            "GroupAdd": null,
            "IpcMode": "private",
            "Cgroup": "",
            "Links": null,
            "OomScoreAdj": 0,
            "PidMode": "host",
            "Privileged": true,
            "PublishAllPorts": false,
            "ReadonlyRootfs": false,
            "SecurityOpt": [
                "label=disable"
            ],
            "UTSMode": "",
            "UsernsMode": "",
            "ShmSize": 67108864,
            "Runtime": "runc",
            "Isolation": "",
            "CpuShares": 0,
            "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,
            "MemoryReservation": 0,
            "MemorySwap": 0,
            "MemorySwappiness": null,
            "OomKillDisable": null,
            "PidsLimit": null,
            "Ulimits": null,
            "CpuCount": 0,
            "CpuPercent": 0,
            "IOMaximumIOps": 0,
            "IOMaximumBandwidth": 0,
            "MaskedPaths": null,
            "ReadonlyPaths": null
        },
        "GraphDriver": {
            "Data": {
                "LowerDir": "/var/snap/docker/common/var-lib-docker/overlay2/6685bf4a3b3cf023160495949bb9f94939e37dbfae4911aff9f819ba0fa0766e-init/diff:/var/snap/docker/common/var-lib-docker/overlay2/d7abce5ec8e4fa07504febaf79a59e646922e0ee6c5a32c464eebdc0b79bec98/diff:/var/snap/docker/common/var-lib-docker/overlay2/c4a19a3cd688a29fbc8622465885a8ffecadca0b71607e3b68c91c09b2a6495e/diff:/var/snap/docker/common/var-lib-docker/overlay2/08306657bbeb12c4f5e111e716ca47377c77bd3431dcde89230cf0acc2637518/diff:/var/snap/docker/common/var-lib-docker/overlay2/1f8c87e30b48e8b822342620c01613e06ccef0e7aa3ea2d0ddd0c8ba9b6ca131/diff:/var/snap/docker/common/var-lib-docker/overlay2/5245c6d6c94c8d1dca780c5062a158afcb442d2cf431b7d872957a56a6c5cd66/diff:/var/snap/docker/common/var-lib-docker/overlay2/31e23f1712ba871d0a2092688b839226710d92b1e636c5b0859205d4ea49c920/diff:/var/snap/docker/common/var-lib-docker/overlay2/5172da5dbe7f997044e9a20a66aa823d8ccdd44f831803ea51b5cfa5b58aedd6/diff:/var/snap/docker/common/var-lib-docker/overlay2/016fb89e2f84f7ce977b5e40071413c5f6ac405d2b0cf1419859b01d0587dfb4/diff:/var/snap/docker/common/var-lib-docker/overlay2/bd9bba3e54aaba25e66d7368193c9e9343929c02b49f29812ce992d39588ad40/diff:/var/snap/docker/common/var-lib-docker/overlay2/69a23b12a0340238f1badb355d48a09bccd893a5d0bf5c8dca0af42ed846d268/diff:/var/snap/docker/common/var-lib-docker/overlay2/6e55d7de6472e0d41bffc71c4430b0ffb720af5e1083eac0ad5ea6888eba15cd/diff:/var/snap/docker/common/var-lib-docker/overlay2/c0e4a046339e9be6d90e9b03631179d71d3f31b7b33597c4736e1187110d8b95/diff",
                "MergedDir": "/var/snap/docker/common/var-lib-docker/overlay2/6685bf4a3b3cf023160495949bb9f94939e37dbfae4911aff9f819ba0fa0766e/merged",
                "UpperDir": "/var/snap/docker/common/var-lib-docker/overlay2/6685bf4a3b3cf023160495949bb9f94939e37dbfae4911aff9f819ba0fa0766e/diff",
                "WorkDir": "/var/snap/docker/common/var-lib-docker/overlay2/6685bf4a3b3cf023160495949bb9f94939e37dbfae4911aff9f819ba0fa0766e/work"
            },
            "Name": "overlay2"
        },
        "Mounts": [
            {
                "Type": "bind",
                "Source": "/home/yaya/palworld",
                "Destination": "/palworld",
                "Mode": "rw",
                "RW": true,
                "Propagation": "rprivate"
            }
        ],
        "Config": {
            "Hostname": "palworld.pod.dpanel.local",
            "Domainname": "",
            "User": "",
            "AttachStdin": true,
            "AttachStdout": true,
            "AttachStderr": true,
            "ExposedPorts": {
                "25575/tcp": {}
            },
            "Tty": true,
            "OpenStdin": false,
            "StdinOnce": false,
            "Env": [
                "ADMIN_PASSWORD=!yaya-server",
                "ALLOW_CONNECT_PLATFORM=Steam",
                "ARM64_DEVICE=generic",
                "AUTO_REBOOT_CRON_EXPRESSION=0 0 * * *",
                "AUTO_REBOOT_ENABLED=False",
                "AUTO_REBOOT_EVEN_IF_PLAYERS_ONLINE=False",
                "AUTO_REBOOT_WARN_MINUTES=5",
                "AUTO_UPDATE_CRON_EXPRESSION=0 * * * *",
                "AUTO_UPDATE_ENABLED=False",
                "AUTO_UPDATE_WARN_MINUTES=30",
                "BACKUP_CRON_EXPRESSION=0 0 * * *",
                "BACKUP_ENABLED=true",
                "BOX64_DYNAREC_BIGBLOCK=1",
                "BOX64_DYNAREC_FASTNAN=1",
                "BOX64_DYNAREC_FASTROUND=1",
                "BOX64_DYNAREC_SAFEFLAGS=1",
                "BOX64_DYNAREC_STRONGMEM=1",
                "BOX64_DYNAREC_X87DOUBLE=0",
                "COMMUNITY=False",
                "DELETE_OLD_BACKUPS=False",
                "DISABLE_GENERATE_ENGINE=false",
                "DISCORD_CONNECT_TIMEOUT=30",
                "DISCORD_ERR_BACKUP_DELETE_MESSAGE=Unable to delete old backups, OLD_BACKUP_DAYS is not an integer. OLD_BACKUP_DAYS=old_backup_days",
                "DISCORD_ERR_BACKUP_DELETE_MESSAGE_ENABLED=true",
                "DISCORD_ERR_BACKUP_DELETE_MESSAGE_URL=",
                "DISCORD_MAX_TIMEOUT=30",
                "DISCORD_PLAYER_JOIN_MESSAGE=player_name has joined Palworld!",
                "DISCORD_PLAYER_JOIN_MESSAGE_ENABLED=true",
                "DISCORD_PLAYER_JOIN_MESSAGE_URL=",
                "DISCORD_PLAYER_LEAVE_MESSAGE=player_name has left Palworld.",
                "DISCORD_PLAYER_LEAVE_MESSAGE_ENABLED=true",
                "DISCORD_PLAYER_LEAVE_MESSAGE_URL=",
                "DISCORD_POST_BACKUP_DELETE_MESSAGE=Removed backups older than old_backup_days days",
                "DISCORD_POST_BACKUP_DELETE_MESSAGE_ENABLED=true",
                "DISCORD_POST_BACKUP_DELETE_MESSAGE_URL=",
                "DISCORD_POST_BACKUP_MESSAGE=Backup created at file_path",
                "DISCORD_POST_BACKUP_MESSAGE_ENABLED=true",
                "DISCORD_POST_BACKUP_MESSAGE_URL=",
                "DISCORD_POST_SHUTDOWN_MESSAGE=Server has been stopped!",
                "DISCORD_POST_SHUTDOWN_MESSAGE_ENABLED=true",
                "DISCORD_POST_SHUTDOWN_MESSAGE_URL=",
                "DISCORD_POST_UPDATE_BOOT_MESSAGE=Server update complete!",
                "DISCORD_POST_UPDATE_BOOT_MESSAGE_ENABLED=true",
                "DISCORD_POST_UPDATE_BOOT_MESSAGE_URL=",
                "DISCORD_PRE_BACKUP_DELETE_MESSAGE=Removing backups older than old_backup_days days",
                "DISCORD_PRE_BACKUP_DELETE_MESSAGE_ENABLED=true",
                "DISCORD_PRE_BACKUP_DELETE_MESSAGE_URL=",
                "DISCORD_PRE_BACKUP_MESSAGE=Creating backup...",
                "DISCORD_PRE_BACKUP_MESSAGE_ENABLED=true",
                "DISCORD_PRE_BACKUP_MESSAGE_URL=",
                "DISCORD_PRE_SHUTDOWN_MESSAGE=Server is shutting down...",
                "DISCORD_PRE_SHUTDOWN_MESSAGE_ENABLED=true",
                "DISCORD_PRE_SHUTDOWN_MESSAGE_URL=",
                "DISCORD_PRE_START_MESSAGE=Server has been started!",
                "DISCORD_PRE_START_MESSAGE_ENABLED=true",
                "DISCORD_PRE_START_MESSAGE_URL=",
                "DISCORD_PRE_UPDATE_BOOT_MESSAGE=Server is updating...",
                "DISCORD_PRE_UPDATE_BOOT_MESSAGE_ENABLED=true",
                "DISCORD_PRE_UPDATE_BOOT_MESSAGE_URL=",
                "DISCORD_SUPPRESS_NOTIFICATIONS=",
                "DISCORD_WEBHOOK_URL=",
                "ENABLE_PLAYER_LOGGING=true",
                "HOME=/home/steam",
                "HOMEDIR=/home/steam",
                "INSTALL_BETA_INSIDER=False",
                "MULTITHREADING=False",
                "OLD_BACKUP_DAYS=30",
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
                "PGID=1000",
                "PLAYERS=5000",
                "PLAYER_LOGGING_POLL_PERIOD=5",
                "PORT=8211",
                "PUBLIC_IP=",
                "PUBLIC_PORT=",
                "PUID=1000",
                "QUERY_PORT=27015",
                "RCON_ENABLED=true",
                "RCON_PORT=25575",
                "REST_API_PORT=8212",
                "REST_API_ENABLED=true",
                "SERVER_DESCRIPTION=",
                "SERVER_NAME=yaya-X99-SERVER",
                "SERVER_PASSWORD=114514",
                "STEAMCMDDIR=/home/steam/steamcmd",
                "TZ=Asia/Shanghai",
                "UPDATE_ON_BOOT=true",
                "USER=steam",
                "USE_DEPOT_DOWNLOADER=False",
                "DIFFICULTY=Normal",
                "DAYTIME_SPEEDRATE=0.500000",
                "NIGHTTIME_SPEEDRATE=0.500000",
                "EXP_RATE=2.000000",
                "PAL_CAPTURE_RATE=2.000000",
                "PLAYER_STOMACH_DECREASE_RATE=0.500000",
                "PLAYER_STAMINA_DECREASE_RATE=1.000000",
                "PLAYER_AUTO_HP_REGEN_RATE=1.000000",
                "PLAYER_AUTO_HP_REGEN_RATE_IN_SLEEP=2.000000",
                "PAL_STOMACH_DECREASE_RATE=0.250000",
                "PAL_STAMINA_DECREASE_RATE=0.250000",
                "PAL_AUTO_HP_REGEN_RATE=2.000000",
                "PAL_AUTO_HP_REGEN_RATE_IN_SLEEP=2.000000",
                "BUILD_OBJECT_HP_RATE=2.000000",
                "BUILD_OBJECT_DAMAGE_RATE=0.100000",
                "BUILD_OBJECT_DETERIORATION_DAMAGE_RATE=0.000000",
                "ENEMY_DROP_ITEM_RATE=1.500000",
                "DEATH_PENALTY=None",
                "ENABLE_PLAYER_TO_PLAYER_DAMAGE=False",
                "ENABLE_FRIENDLY_FIRE=False",
                "BASE_CAMP_MAX_NUM=60",
                "BASE_CAMP_WORKER_MAX_NUM=30",
                "DROP_ITEM_ALIVE_MAX_HOURS=3.000000",
                "BASE_CAMP_MAX_NUM_IN_GUILD=6",
                "PAL_EGG_DEFAULT_HATCHING_TIME=12.000000",
                "WORK_SPEED_RATE=1.000000",
                "AUTO_SAVE_SPAN=30.000000",
                "IS_MULTIPLAY=True",
                "IS_PVP=False",
                "ENABLE_NON_LOGIN_PENALTY=False",
                "EXIST_PLAYER_AFTER_LOGOUT=True",
                "ITEM_WEIGHT_RATE=0.500000",
                "COOP_PLAYER_MAX_NUM=6",
                "CHAT_POST_LIMIT_PER_MINUTE=100",
                "SUPPLY_DROP_SPAN=360",
                "USE_FIXED_FRAME_RATE=false",
                "SMOOTH_FRAME_RATE=true",
                "FIXED_FRAME_RATE=999.000000",
                "MIN_DESIRED_FRAME_RATE=80.000000",
                "NET_CLIENT_TICKS_PER_SECOND=120",
                "LAN_SERVER_MAX_TICK_RATE=999.000000"
            ],
            "Cmd": null,
            "Healthcheck": {
                "Test": [
                    "CMD-SHELL",
                    "pgrep \"PalServer-Linux\" > /dev/null || exit 1"
                ],
                "StartPeriod":<PHONE_NUMBER>00
            },
            "Image": "thijsvanloef/palworld-server-docker:latest",
            "Volumes": null,
            "WorkingDir": "/home/steam/server",
            "Entrypoint": [
                "/home/steam/server/init.sh"
            ],
            "OnBuild": null,
            "Labels": {
                "com.dpanel.description": "DPanel is a docker web management panel",
                "com.dpanel.website": "https://dpanel.cc",
                "dockerhub": "https://hub.docker.com/r/thijsvanloef/palworld-server-docker",
                "github": "https://github.com/thijsvanloef/palworld-server-docker",
                "maintainer": "DPanel",
                "name": "thijsvanloef/palworld-server-docker",
                "org.opencontainers.image.authors": "Thijs van Loef",
                "org.opencontainers.image.source": "https://github.com/thijsvanloef/palworld-server-docker"
            }
        },
        "NetworkSettings": {
            "Bridge": "",
            "SandboxID": "7d98f033f575030a6c0cc7a23b530c2510e5c67f14aa3178c9a00e892ece4a06",
            "SandboxKey": "/run/snap.docker/netns/default",
            "Ports": {},
            "HairpinMode": false,
            "LinkLocalIPv6Address": "",
            "LinkLocalIPv6PrefixLen": 0,
            "SecondaryIPAddresses": null,
            "SecondaryIPv6Addresses": null,
            "EndpointID": "",
            "Gateway": "",
            "GlobalIPv6Address": "",
            "GlobalIPv6PrefixLen": 0,
            "IPAddress": "",
            "IPPrefixLen": 0,
            "IPv6Gateway": "",
            "MacAddress": "",
            "Networks": {
                "host": {
                    "IPAMConfig": null,
                    "Links": null,
                    "Aliases": null,
                    "MacAddress": "",
                    "DriverOpts": null,
                    "NetworkID": "ab2c8c878c19c9c5e8372fedf8186bdfb20ea24cd12b7f542f8726f22fe6d759",
                    "EndpointID": "79a60d2920df40756d9179807a12fc7333b6b918c1a698b770f5561309d27e70",
                    "Gateway": "",
                    "IPAddress": "",
                    "IPPrefixLen": 0,
                    "IPv6Gateway": "",
                    "GlobalIPv6Address": "",
                    "GlobalIPv6PrefixLen": 0,
                    "DNSNames": null
                }
            }
        }
    }
]

Container/Host Logs (IMPORTANT)

Logs
****EXECUTING USERMOD****
usermod: no changes
Redirecting stderr to '/home/steam/Steam/logs/stderr.txt'
Logging directory: '/home/steam/Steam/logs'
[  0%] Checking for available updates...
[----] Verifying installation...
[  0%] Downloading update...
[  0%] Checking for available updates...
[----] Download complete.
[----] Extracting package...
[----] Extracting package...
[----] Extracting package...
[----] Extracting package...
[----] Installing update...
[----] Installing update...
[----] Installing update...
[----] Installing update...
[----] Installing update...
[----] Installing update...
[----] Installing update...
[----] Installing update...
[----] Installing update...
[----] Cleaning up...
[----] Update complete, launching Steamcmd...
UpdateUI: skip show logosteamcmd.sh[26813]: Restarting steamcmd by request...
Redirecting stderr to '/home/steam/Steam/logs/stderr.txt'
Logging directory: '/home/steam/Steam/logs'
[  0%] Checking for available updates...
[----] Verifying installation...
UpdateUI: skip show logoSteam Console Client (c) Valve Corporation - version<PHONE_NUMBER>
-- type 'quit' to exit --
Loading Steam API...IPC function call IClientUtils::GetSteamRealm took too long: 456 msec
OK
"@sSteamCmdForcePlatformType" = "linux"
"@sSteamCmdForcePlatformBitness" = "64"

Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
 Update state (0x3) reconfiguring, progress: 0.00 (0 / 0)
IPC function call IClientAppManager::GetUpdateInfo took too long: 396 msec
 Update state (0x3) reconfiguring, progress: 0.00 (0 / 0)
 Update state (0x5) verifying install, progress: 5.42 (195346364 /<PHONE_NUMBER>)
 Update state (0x5) verifying install, progress: 17.81 (642257286 /<PHONE_NUMBER>)
 Update state (0x5) verifying install, progress: 30.35<PHONE_NUMBER> /<PHONE_NUMBER>)
 Update state (0x5) verifying install, progress: 42.62<PHONE_NUMBER> /<PHONE_NUMBER>)
 Update state (0x5) verifying install, progress: 55.39<PHONE_NUMBER> /<PHONE_NUMBER>)
 Update state (0x5) verifying install, progress: 67.81<PHONE_NUMBER> /<PHONE_NUMBER>)
 Update state (0x5) verifying install, progress: 80.42<PHONE_NUMBER> /<PHONE_NUMBER>)
 Update state (0x5) verifying install, progress: 92.79<PHONE_NUMBER> /<PHONE_NUMBER>)
 Update state (0x81) verifying update, progress: 4.33 (156094838 /<PHONE_NUMBER>)
 Update state (0x81) verifying update, progress: 16.97 (611848582 /<PHONE_NUMBER>)
 Update state (0x81) verifying update, progress: 29.60<PHONE_NUMBER> /<PHONE_NUMBER>)
 Update state (0x81) verifying update, progress: 42.13<PHONE_NUMBER> /<PHONE_NUMBER>)
 Update state (0x81) verifying update, progress: 54.75<PHONE_NUMBER> /<PHONE_NUMBER>)
Success! App '2394010' fully installed.
****Checking for available container updates****
The container is up to date!
****GENERATING CONFIG****
Using Env vars to create PalWorldSettings.ini
****Compiling PalWorldSettings.ini****
Compiling PalWorldSettings.ini done!
****Compiling Engine.ini****
Compiling Engine.ini done!
****GENERATING CRONTAB****
BACKUP_ENABLED=true
Adding cronjob for auto backups
WARN[2024-12-27T08:02:43+08:00] process reaping disabled, not pid 1
Cronjobs started
****Starting Server****
./PalServer.sh -port=8211 -queryport=27015
WARN[2024-12-27T08:02:43+08:00] process reaping disabled, not pid 1
INFO[2024-12-27T08:02:43+08:00] read crontab: /home/steam/server/crontab
The file already exists: /palworld/Pal/Binaries/Linux/steamclient.so
Shutdown handler: initalize.
5.1.1-0+++UE5+Release-5.1 1008 0
Disabling core dumps.
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
(Usage warnings can be disabled via Oodle_SetUsageWarnings.)
OODLE USAGE WARNING : Destination buffer appears to be in uncached
or write-combined memory! This is extremely slow. See "How do I
decompress to graphics memory quickly?" in the Oodle FAQ.
[S_API FAIL] Tried to access Steam interface SteamNetworkingUtils004 before SteamAPI_Init succeeded.
[2024-12-27 08:06:09] [LOG] REST accessed endpoint /v1/api/players OK
[2024-12-27 08:06:14] [LOG] REST accessed endpoint /v1/api/players OK
[2024-12-27 08:06:20] [LOG] REST accessed endpoint /v1/api/players OK
[2024-12-27 08:06:25] [LOG] REST accessed endpoint /v1/api/players OK

Bug Report Checklist

[X] I searched for my issue on the Known issues page
[X] I searched for my issue in the Closed issues
[X] I have included all relevant information required above.
[ ] I am willing to fix this bug

Hi @mmyo456 Is this on a new server, or a preexisting server?


calc_hemi_seaice missing latitude

I was using the index instead of the actual latitude here so fixing this and also the boolean logic for the area.

Latitude in ancillary files uses nx, ny as dimensions and the model output uses ni, nj so have to take this into account too and rename latitude dimension accordingly. Also switching to where() instead of sel as we're not using a dimension but a separate variable to select the latitude.


Javascript syntax highlight breaks in function definitions inside objects

Issue Type: Bug
Syntax highlighting breaks when the following criteria are met:

The is an object who's values are functions
The object is surrounded by ( )
There is at least one newline between the opending ( and opening {
See below for an example:

const foo = (
    {
        // async, const and return not highlighted below
        bar: async () => {
            const baz = 2;
            return baz;
        }
    }
)

const foo = ({
    // same function, properly highlighted
    bar: async () => {
        const baz = 2;
        return baz;
    }
});

VS Code version: Code - Insiders 1.47.0-insider (b9d7ec9ff367a8e59fe4cc2abee605a55be180e8, 2020-06-20T00:08:33.687Z)
OS version: Windows_NT x64 10.0.18362

System Info

Item
Value

CPUs
AMD Ryzen 5 2600 Six-Core Processor             (12 x 3394)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.93GB (8.84GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions: none

Confirmed with the latest grammar versions

This is limitation of text mate grammar which doesnt allow lookup beyond single line. Because On first line we cant tell if its arrow or just parenthesized expression. We have tailored it to think it as arrow since thats the most common case and hence the issue.


Support FlexVolume in Alicloud for etcd

What this PR does / why we need it:
We are encountering an issue in gardener setup on Alicloud. It is related to the change on this part code https://github.com/gardener/gardener/blob/master/pkg/operation/cloudbotanist/alicloudbotanist/controlplane.go#L134-L142. In order to setup garden, seed clusters on Alicloud, we leverage the k8s cluster provided by Alicloud. However, k8s provided by Alicloud container service doesn't support csi and only supports flexvolume. We cannot bind this pvc when create main-etcd when create the first shoot (as seed for further shoot) in the soil cluster

@jia-jerry I suppose this is a duplicate of #1024 ?

@jia-jerry I suppose this is a duplicate of #1024 ?

Yes. #1024 is for hotfix. This is a critical fix.


Docs hard to comprehend

Provide your feedback here.
We're currently trying to build Select/MultiSelect components (which I guess you would call "TagField", when it's finally it's turn to be implemented?). React-Aria seems like the best choice feature-wise, but comprehension has been a struggle. I think I grasped the part that at the core, I just need to manage and pass around a Collection and SelectionManager, however the details are elusive.
For example: ListBox is a critical part of any such component, and is mentioned in most of relevant docs. Moreover, it's mentioned with the idea that we can build it once and just reuse. However usage examples are different in different pages:

Example in the useListBox itself puts useListState inside the ListBox component
Example in the useSelect instead passes state from useSelectState as a prop
We would like to allow booleans and null as possible values to be selected in the components. Seems like useListData is made for building a collection where keys need to be massaged a bit to be useable, however in that example ListBox accepts items and selectedKeys, not state.

Then, the docs menu is sorted... A bit weird? There's useSingleSelectListState at the top, but it's really just a building block for useSelectState that's at the bottom of the list?
I'm at a loss as to what pattern is suggested. Also, the types are all referencing each other. I've been staring at words List Select Props Options and State in, it seems, all possible combinations, for the last 3 days, and am feeling quite exhausted.

We definitely agree that combining the hooks can be cumbersome, and that is one of the reasons we created React Aria Components. We're hoping these unstyled components can be an easier way to get started, and they can choose to drop down to hooks if they need something more custom.

Then, the docs menu is sorted... A bit weird? There's useSingleSelectListState at the top, but it's really just a building block for useSelectState that's at the bottom of the list?

These are categorized, where the categorizes are sorted alphabetically, so there isn't necessarily a relationship between order and dependency in the menu.

I'm at a loss as to what pattern is suggested.

Beyond the examples in the docs, we recommend looking at the source code of individual React Spectrum components to get more ideas for implementation.
Hopefully that helps, and again, we're hoping that developer experience is improved by using the unstyled components as a starting point. Feel free to create a Discussion or Issue for specific ideas or recommendations.

So, I've thought about possible solutions, and here are some, in no particular order:

There needs to be a "Reference implementation" of "common" components. E.g, when ListBox is referred from useSelect or useListData, it must be the same ListBox. It's simply confusing otherwise. It can either be the main "Example" on the component's (ListBox's) page, or a special section "Reference implementation" that will be linked to.
Explicit compatibility notes on hooks. Ideally, each hook would have sections for:

This hook accepts output from these other hooks as it's 1st argument (repeat for as many arguments as there are):
The props this hooks accepts are the same as these other hooks:
The output of this hook can be consumed by the following hooks:
The following hooks are built using this one, you probably don't need both at the same time:

Be better at linking: currently, useSelect page doesn't have a link to useSelectState, only definition popups.
Maybe a tag system for different kind of groupings? I'm really missing a way to see related elements of the system. I sort of get how the current categories came to be, but I wish for more.

Wholeheartedly agree with all the points you've brought up @Faithfinder 💯
I've implemented a Select component using useSelect hook and the provided examples - and while that was still a bit hard to grok, the Codesandbox examples helped a great deal.
I'm now looking to extend this component to support multiple selection, and I'm simply at a loss as to how to do it. There are no such examples in the docs, and mentions of multiple selection seem to be scattered across several doc pages. It's pretty confusing. Digging through source code of React Spectrum isn't exactly great DX - it would be super helpful to have more examples of these fairly common use cases.

Multiple selection is not supported by Select, which is why you are not finding it. You could use ListBox with a popover to implement that though.

Ah, I see. Thanks for the clarification @devongovett. The State Management section in the useSelect docs makes it sound like it is.

I was also looking for a way to implement multiple selection with Select, and the documentation somewhat suggests that it's possible, especially since it lists the props for ListBox within the Select documentation. This is a bit confusing, I tried modifying the ListBox props to allow multiple selections, and it works, but only when it's not used inside a Select. Otherwise, the SelectionMode prop of ListBox seems to be ignored if it's used within a Select.

I was also looking for a way to implement multiple selection with Select, and the documentation somewhat suggests that it's possible, especially since it lists the props for ListBox within the Select documentation. This is a bit confusing, I tried modifying the ListBox props to allow multiple selections, and it works, but only when it's not used inside a Select. Otherwise, the SelectionMode prop of ListBox seems to be ignored if it's used within a Select.

Definitely agree with this. I guess this is a downside of the heavy use of composition in this library, or maybe just in the docs. If the ListBox selectionMode prop does nothing when inside a Select, I'd expect it to not be listed on the page as something you can change. There is a generic note above it that says "Within a , most  props are set automatically", but that doesn't imply that you can't set them yourself.

Multiple selection is not supported by Select, which is why you are not finding it. You could use ListBox with a popover to implement that though.

Reading https://github.com/adobe/react-spectrum/issues/2140, it seems like this may or may not come to the Select component. Until then, what would be a "recipe" for implementing it be?
<DialogTrigger>
  // "All Selected" | "None Selected" | "N Selected" | "Some option label" (if exactly 1 selected)
  <Button>2 items selected</Button>
  <Popover>
    <Dialog>
      <ListBox>
         <ListBoxItem />
      </ListBox>
    </Dialog>
  </Popover>
</DialogTrigger>

What about something like this? Where I don't need a type-able combobox or de-selectable tag pills, I just want a button trigger with a concatenated label and a popover.


chore: fix compile issue

What this PR changes/adds
Fix compile issue on AzureStorageDataSource and AzureDataFactoryTransferService
Why it does that
not compiling

Codecov Report
Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (ca5bc68) 71.36% compared to head (24777dc) 71.13%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #70      +/-   ##
==========================================
- Coverage   71.36%   71.13%   -0.23%
==========================================
  Files          25       25
  Lines         625      627       +2
  Branches       20       20
==========================================
  Hits          446      446
- Misses        176      178       +2
  Partials        3        3

Files
Coverage Δ

...e/datafactory/AzureDataFactoryTransferService.java
87.50% <0.00%> (-12.50%)
:arrow_down:

...azure/storage/pipeline/AzureStorageDataSource.java
95.12% <0.00%> (-2.38%)
:arrow_down:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Feature Request: Create separate entities for configuration/Replace some services with switches, buttons and selects.

Is your feature request related to a problem? Please describe.
This is less of a feature request and more of a suggestion.
Recently I've used a camera from another manufacturer and noticed there were a lot of entities in the device, which are great for controlling through the UI:

Describe the solution you'd like
Currently a lot of the camera controls are only accessible through service calls, which is fine for automations but makes it harder to change settings on the fly or see which setting is on at the time.
Some services could be replaced by switches:

tapo_control.set_privacy_mode
tapo_control.set_alarm
tapo_control.set_led_mode
tapo_control.set_auto_track_mode
tapo_control.set_alarm_mode

Some could be a button:

tapo_control.format
tapo_control.reboot
tapo_control.synchronize_time

These a select:

tapo_control.set_motion_detection_mode
tapo_control.set_day_night_mode

Describe alternatives you've considered
Usually I check the dev tools to see all atributes easily and then do the service calls or just go straight to the app.

Additional context
I used "replace" a lot, but there's no reason for removing services and turning this into a breaking change.

If we would be doing this i would prefer a breaking change since it will be less code to maintain and cleaner.
That being said, I was thinking of this in the past and doing this introduces more code and more possible bugs. Most if not all these entities can be created by users using template and we could add more examples into the readme.
That also being said, I am not against it and if someone wants to refactor the code, implement this and open PR I will accept it. It is ultimately a lot more user and beginner friendly. It's just not a priority for me right now as it can be fairly easily achieved. It would be a nice to have for a future.

@JurajNyiri i'm working on this at the moment, i think you will get a PR very soon :wink: :grin:

it escalated a little bit :see_no_evil:

@JurajNyiri tell me if I have such a structure in my yaml file
    script:
        tapo_camera_3_otvernis:
          alias: Камера гостиная Отвернись
          sequence:
          - service: tapo_control.ptz
            data:
              entity_id: camera.tapo_camera_3_sd
              preset: 1

Do I understand correctly that these services will not work?

Yes you do. You need to replace this with the switch.turn_off and switch.turn_on services with the related entity for privacy.


initialize:function() {}

Would be nice to have an "initialize function" to modify the first section upon loading, the same way you might modify other section with the before:function().

How would this differ from the afterRender function?


Caller does not have storage.buckets.get access

gcloud auth activate-service-account --key-file "service-account.json"
gsutil ls gs://some-bucket ### this works fine!

via ruby it doesn't work using the same service-account.json! why?!
storage = Google::Cloud::Storage.new(
      project: 'someproject', keyfile: 'service-account.json')
storage.bucket('some-bucket').files ...

...
forbidden: Caller does not have storage.buckets.get access to bucket 'some-bucket'

I don't need to list buckets! I just want to list all files in a bucket that service account has access to!

Unfortunately, it is not possible to list files without access to the bucket that contains them. This is due to the current design of the library, which requires that the bucket is loaded before listing its files.

why?!

I believe one of the founding goals of this project was a "clean, OOP-inspired design", which comes at some cost to flexibility. For more flexibility, the google-api-client/Google/Apis/StorageV1/StorageService offers a "flatter" API, although authentication is a bit more involved.

I've managed to list bucket files/dirs (using the same service account) using the code bellow:
storage.service.list_files( ...

Please note that calling storage.service.list_files( ... as suggested above is NOT RECOMMENDED as it uses undocumented access to storage.service to use the underlying google-api-client implementation. This implementation is subject to change at any time without warning, and has in fact been changed in many of the other packages in google-cloud-ruby. Should it change in the future for google-cloud-storage, the above code will no longer work.

I can think of two possible solutions for this issue:

Expose Objects.list as a top-level method (Project#files) that accepts the bucket name.
Add a mode (option) to Project#bucket to return a stub containing the given bucket name without retrieving the bucket metadata. This stub could then be used to call Bucket#files without permissions to the bucket.

@remi This issue raises a tension that I think is shared by #1596, which is that between granular access control and the hierarchical access of an OOP-inspired design. We would love to get your input on this issue as well.

Add a mode (option) to Project#bucket to return a stub containing the given bucket name without retrieving the bucket metadata

There's an existing idiom in the client libraries for doing this, eg.
require "google/cloud/pubsub"

pubsub = Google::Cloud::Pubsub.new
topic  = pubsub.topic "my-topic", skip_lookup: true

The Pub/Sub skip_lookup option is documented as such:

Optionally create a Topic object without verifying the topic resource exists on the Pub/Sub service. Calls made on this object will raise errors if the topic resource does not exist. Default is false.

This issue is one of the trade-offs/cons of the approach that these Ruby Google Cloud libraries take.  One of the benefits is that my code raises an exception when I call bucket.storage "bucket-that-doesn't exit" rather than raising an exception later on, which may be more challenging to debug.
For this specific case... storage.bucket "bucket", skip_lookup: true would follow an existing library idiom with precedent and fix the issue.

@quartzmo ^ this has the benefits of being an additive change to the library (which is GA). A more significant change, such as storage.bucket (and other such actions) not kicking off an API request would be a substantially bigger conversation.
*Note: this has come up a few times for performance because a user may only want to download a file (1 API request needed) but storage.bucket("dogs").file("dog.png").download "dog.png" kicks off 3 API requests. This is out of scope of this issue, just FYI

Thank you @remi.
@blowmage What is your opinion on adding skip_lookup behavior similar to that in Pub/Sub to all relevant methods in Storage? Do you have any reservations about having taken this approach with Pub/Sub?

I worry about unforeseen complications adding skip_lookup to libraries not originally designed for it. I sat on this question overnight and while I still have my concerns, I don't think they should stop progress and granting users additional control over the API calls made (or not made).

Ping: @blowmage I'm working on a sample where I could really find this feature request very useful. Do you have an ETA?

@frankyn Hoping to have something up for review by the end of the week.

Awesome! No rush, I'm excited for this feature. Thank you!

Hey @blowmage (follow-up).
Adding more rationale for this enhancement.
Turns out to use requester pays to download files with the client library this is a necessary enhancement. For a user to download a file using requester pays with the Ruby client, they need to provide permission to storage.buckets.get, storage.objects.list, and storage.objects.get to allUsers (public bucket/objects for this example) and this is only possible by assigning roles roles/storage.objectViewer and (roles/storage.legacyBucketReader or roles/storage.admin). roles/storage.admin is not a way a user should access a storage.buckets.get so a user has to use the legacy role roles/storage.legacyBucketReader.
This enhancement will allow users to not depend on a legacy role when using the Ruby client to access files from a public bucket.
Thanks!

We have added the ability to create Bucket and File objects without first accessing the Storage API by using skip_lookup in the 1.4.0 release.
This means that you should be able to accomplish this using the following code:
require "google/cloud/storage"

storage = Google::Cloud::Storage.new

bucket = storage.bucket "some-bucket", skip_lookup: true
files = bucket.files

Does OOP say everything have to be instantiated and self-inspected? I don't think so. It is about how we write code, not how it is being executed.
It is lazyness and Ruby is fine with it.

One of the benefits is that my code raises an exception when I call bucket.storage "bucket-that-doesn't exit" rather than raising an exception later on, which may be more challenging to debug.

I won't say it's challenging. Just put it in documentation that this stuff is lazy and if you really want to fail immediately do some intermediate check. I would love skip_lookup to see true by default and stating true would be that check.


Allow development of VS Code-themed webviews using UI toolkit and React framework

What this is for
To start addressing the following areas for improvement with Webviews:

They are cumbersome to develop, involving substantial boilerplate and message plumbing
It is hard to theme them consistently, both with each other and with the VS Code host environment
They don't react to theme changes in the host (e.g. switching between dark and light modes)
We have a lot of work to do to improve accessibility in our Webviews
It takes a long time to make code changes and see them reflected in the Webviews, making it hard to iterate
They use our own unique rendering approach and Handlebars helpers which make it harder to port views that we might want to create our own VSCode-themed versions of (e.g. Inspektor Gadget React components in Headlamp)

How it helps
This introduces a sub-project that allows development of Webviews as components in a React application. The application can be run in a development web server with continuous update and debugging in a browser, with browser-based mocking of the VS Code backend for message passing.
Some features of this are:

Reduced boilerplate: not creating an entire HTML document for each Webview, and extracting generic message-passing logic to shared utility types.
Strong typing of the 'contract' between VS Code and the Webviews, by leaning heavily on TypeScript to check the types of data passed both ways.
Use of CSS variables to match VS Code theme colours, allowing instantaneous reflection of colour scheme changes.
Use of the VS Code Webview UI Toolkit to display themed and accessible components.
Near real-time update of rendered views during development.
Easy creation of manual test scenarios, allowing views to reflect states that might be harder to achieve using a real VS Code backend (e.g. error scenarios).
A more 'standard' Framework for web UI development, making it easier to port other React components or try out new ideas quickly.

What is actually changed
There are a lot of existing Webviews in the extension. As an initial exercise to prove the utility of these changes, this PR includes the conversion one of the more complex ones to use the web application; that is the Periscope deployment result Webview.
This previously rendered something like this:

It is now showing like this (with theme switching between dark and light modes):

There is also a TestStyleViewer component, which is not displayed from any VS Code command, but is used in a VS Code test to extract the VS Code CSS variables and default Webview styling so that they can be used to style the React application so that it's consistent with VS Code.

👍 /hallway pass for the CHAT-Gpt stuff B-) because of its token number bug, nothing to do with the PR.


Copilot integration broken

hello,
i'm seeing an error with copilot integration after recent changes. when i try to use avante for anything i see the following
Received error from Copilot API: Bad Request

when i checkout commit hash 07af0a91f29584cdabf440dd3d4a0ed677ecf63e then the error goes away and functionality is restored
# this fixes it
cd ~/.local/share/nvim/lazy/avante.nvim
git checkout 07af0a91f29584cdabf440dd3d4a0ed677ecf63e
<restart nvim>

This has to do with the recent integrations from support pasting from clipboard. Copilot currently doesn't support image, so the text message is supposedly to be string instead of a list of message

when i update and retry, i now see
Received error from Copilot API: bad request: unknown Editor-Version header for IDE auth

Strange. When I replace Editor-Version by vscode/1.70.2 inside the plugin's code, it all work great.

sorry, I was having lunch, but https://github.com/yetone/avante.nvim/pull/287 should fix this now. Thanks for all the feedback


Add option for limiting rows of retrieved of results

I found the pandas-gbq interface easy to use and wanted to also use it for creating tables in BigQuery, not just downloading all the results at once. The existing capabilities of read_gbq() is actually already sufficient to do this, because you can just set query.destinationTable in the job configuration. However, I would like to limit the number of retrieved rows to a small sample of the whole table that was created instead of downloading the many thousands of rows that were created.
I've already played with making the changes myself in a project I'm working on:
http://nbviewer.jupyter.org/github/bburky/subredditgenderratios/blob/master/Subreddit Gender Ratios.ipynb
In the current code for run_query(), you read all rows from the table by converting the iterator into a list. Instead, you could pass the iterator to itertools.islice() first to limit it to a configurable limit. You can look at my code to see how it could be done.
Also, if you're interested I could contribute the IPython %%bigquery cell magic I am using in that project. It should be a very simple wrapper around read_gbq().

Adding the %%bigquery magic would be interesting. How similar is that to the magic in google's datalab?

Oh, I didn't know about datalab. My %%bigquery magic is basically a thin wrapper around read_gbq(). I can't quite tell how datalab's %%bq magic works, it may do something similar around their own APIs. They also have a --name argument for reusing results, but I can't tell if it saves tables, or just lets you save the output to a variable for reuse.
Would work on an IPython magic be done in this repository, or a separate standalone one? It would introduce a dependency on IPython.

Would work on an IPython magic be done in this repository, or a separate standalone one? It would introduce a dependency on IPython.

I'm not sure actually (it could be an optional dependency though). @jreback @tswast ?

you can do it in this repo; it a separate piece so the dep is fine (and only impacts the magic piece)

Follow-up for magics, the google-cloud-bigquery library is adding a BigQuery magic in https://github.com/GoogleCloudPlatform/google-cloud-python/pull/4983

Re limiting rows - that's very easy to do with a LIMIT clause

The issue was opened with the thought that you could do a query with a lot of results and write to a destination table, but only want to sample the results.

However, I would like to limit the number of retrieved rows to a small sample of the whole table that was created instead of downloading the many thousands of rows that were created.

Limiting the maximum results via pandas-gbq probably doesn't make the most sense if you want a representative sample. For that you'd want to add a little randomness and select from the destination table.
Or @bburky did you not want a representative sample, more just a preview?

Ah, preview makes sense. Sorry for being overzealous.

Yes. I was running a query that returned many many results and saving the
results with query.destinationTable. To sanity check the query I ran, I
wanted to see a 100 row preview or so.
A possible implementation is just itertools.islice() of the query
results. I don't mind if this isn't completely built into pandas-gbq, but
there wasn't any way for me to hook or modify anything except copy pasting
and modifying run_query().


Followup: we should not be making manual Run() calls in tests: those just cover up bugs with Run() scheduling.  We should be doing DrainAndServiceIO.

Followup: we should not be making manual Run() calls in tests: those just cover up bugs with Run() scheduling.  We should be doing DrainAndServiceIO.
Originally posted by @bzbarsky-apple in https://github.com/project-chip/connectedhomeip/pull/14805#discussion_r811578098

In particular:

The tests should be using an async loopback, not a sync one.
We should remove the Run calls.

Relevant tests:
src/app/tests/TestReadInteraction.cpp
src/controller/tests/TestReadChunking.cpp


Personal Safety (non disease), ... stay out of the hospital

Possible content to be added in the "Do's" section?
Everyone is naturally mentally distracted in this pandemic.    Please stay focused on your high risk activities, particularly driving.   Getting through your day safely so you don't require emergency services or hospitalization means those limited resources can attend to COVID-19 patients.
Now, especially,  is the time to silence your cell phone when you get behind the steering wheel.
Be safe.

Yes, same goes for any activity which is high risk but new to you. Here's a good resource from Stanford Childrens Hospital  outlining risks by activity.

And don't stress infrastructure unnecessarily either. eg. this guy destroyed his neighborhood sewage system with expanding hygroscopic beads. This is the very worst time to do so.


Move server files to the src folder

So that we have a single logical place to import them in the CLI and also to export them as library. This also colocates them more with related files and harmonizes the location of worker entrypoints

Merging this as it's just moving files around and I'd like to start building on top of it.


bump python multipart to 0.0.18

Bumping multipart dependency to resolve feature request #1561

Why this consistently fails is beyond me...

Superseded by #1570

Yes it does! The failing tests are weird. I only updated the pyproject.toml file and later just ran poetry lock and checked in both the pyproject.toml and poetry.lock file. I think the locking process caused Python to automatically update the rest of the dependencies which caused the tests to fail.
Thanks @dokterbob!


Add listeningInterface in broker.conf,Use Network Interface instead of IP

Fixes #9508

The pr had no activity for 30 days, mark with Stale label.


[WIP] Basic Dapr HTTP Client for Actors.

Description
Please explain the changes you've made
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #[issue number]
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[ ] Created/updated tests
[ ] Extended the documentation

Moved to this PR instead: dapr/java-sdk#39


updating cpanminus version

Signed-off-by: Swati Keshari<EMAIL_ADDRESS>Description
[Please describe what this change achieves]
Issues Resolved
[List any existing issues this PR resolves, or any Discourse or
StackOverflow discussions that are relevant]
Check List

[ ] New functionality includes tests
[ ] All buildkite tests pass
[ ] Full omnibus build and tests in buildkite pass
[ ] All commits have been signed-off for the Developer Certificate of Origin. See https://github.com/chef/chef/blob/master/CONTRIBUTING.md#developer-certification-of-origin-dco
[ ] PR title is a worthy inclusion in the CHANGELOG

This will need to wait until after the postgresql upgrade release

Acceptance Criteria: sqitch schema migration still works.

https://buildkite.com/chef/chef-chef-server-master-omnibus-adhoc/builds/2984#


Respect Android battery saver

Flutter should respect the Android battery saver.
Ideas:

Skip animations
???

API 21+ has an API to check:
https://developer.android.com/reference/android/os/PowerManager.html#isPowerSaveMode()

"Skipping animations" may also be started by https://github.com/flutter/flutter/issues/4827 for iOS Accessibility.

On the framework side we should make the SchedulerBinding expose a flag and then we should make AnimationController honour it.

The framework side of this will probably be subsumed by #4827.

Looks like on iOS one is even supposed to lower frame rates:
https://developer.apple.com/library/content/documentation/Performance/Conceptual/EnergyGuide-iOS/LowPowerMode.html

Seems like the flag has been implemented (animationBehavior property), what more is to be done here?


Issue with PSO and small population size

Hi,
Through a typo, I stumbled onto an issue where running PSO with a population size of 2 runs into a ValueError: unsupported format character '-' (0x2d) at index 2.
MWE:
from pymoo.core.problem import ElementwiseProblem
from pymoo.optimize import minimize
from pymoo.algorithms.soo.nonconvex.pso import PSO

class MyProblem(ElementwiseProblem):

    def __init__(self, **kwargs):
        super().__init__(n_var=10, n_obj=1, n_ieq_constr=0, xl=-5, xu=5, **kwargs)

    def _evaluate(self, x, out, *args, **kwargs):
         out["F"] = (x ** 2).sum()

problem = MyProblem()

res = minimize(problem, PSO(pop_size=2), termination=("n_gen", 10), seed=1, save_history=False, verbose=True,)

The problem seems to originate from the _adapt method when calculating the new inertia weight yields an overflow error, which then creates an issue with the display output. Running with either adaptive=False , verbose=False, or a population size >= 3 fixes the issue. It also only appears with PSO, other algorithms like GA, ES, etc. work fine with such a small population size.
Arguably, running with such small population sizes is more of a user mistake than anything but maybe a warning could be issued if an algorithm is initialized with nonsensical values.
Otherwise, great package, works like a charm, and the documentation is really nice ( and improved with the latest release).

Thank yo @mihofer for a workaround. Pop > 2 really allows to move on. I wouldn't describe pop == 2 as a mistake – a good size for testing code.
Here is an actual traceback:
File "pymoo/optimize.py", line 67, in minimize
    res = algorithm.run()
  File "pymoo/core/algorithm.py", line 141, in run
    self.next()
  File "pymoo/core/algorithm.py", line 162, in next
    self.advance(infills=infills)
  File "pymoo/core/algorithm.py", line 232, in advance
    self._post_advance()
  File "pymoo/core/algorithm.py", line 312, in _post_advance
    self.display(self)
  File "pymoo/core/callback.py", line 27, in __call__
    self.update(algorithm)
  File "pymoo/util/display/display.py", line 23, in update
    text += output.text()
  File "pymoo/util/display/output.py", line 53, in text
    return regex.format(*[col.text() for col in self.columns])
  File "pymoo/util/display/output.py", line 53, in <listcomp>
    return regex.format(*[col.text() for col in self.columns])
  File "pymoo/util/display/column.py", line 26, in text
    return format_text(value, self.width, self.truncate)
  File "pymoo/util/display/column.py", line 43, in format_text
    text = number_to_text(value, width)
  File "pymoo/util/display/column.py", line 34, in number_to_text
    return f"%.{width - 7}E" % number
ValueError: unsupported format character '-' (0x2d) at index 2

Thank you for pointing this out! It was just a printing issue in PSO.


Add webdam resource to webguide

Let me know if anything is amiss.
refs #165

Hi I have removed the spirious directions.
We should tell larger student facing services about the UCSBnetID convention -- like I dunno GOLD login prompts:
https://www.google.com/search?newwindow=1&site=&source=hp&q="UCSBNetID"&oq="UCSBNetID"&gs_l=hp.3..0l2j0i10i30l2j0i5i30.1179.4942.0.59<IP_ADDRESS>.<IP_ADDRESS>.1152.4j7.11.0....0...1c.1.64.hp..1.9.951.0..0i10j0i5i10i30.mj1CeFKK7Ow

@tenken I just go by the source, which is UCSB Identity Services http://www.identity.ucsb.edu/ and they do UCSBnetID. If other choose to not be precise, well that is on them. But I now see an error on one of the pages I control from your google search. I will need to fix it.


mix deps.compile failing on Phoenix 1.3

I've tried to add ex_admin package from the github master branch in my Phoenix 1.3 project.
My app name is Quest. In the installation docs, it is mentioned to config module as Quest.Web, which is something that doesn't exist(Is it supposed to be QuestWeb?).
When I try to do mix do deps.get, deps.compile, It fails with a message:
warning: the dependency :phoenix_html is duplicated at the top level, please remove one of them
mix admin.install also fails, with the following error:
** (Mix) Can't find brunch-config.js
Please help.

Use Phoenix1.2 or wait the author to upgrade this project.
ex_admin-0.8 is incompatible with Phoenix1.3 cause the Phoenix1.3 changed the directory structure a lot, like spliting web/* into /assets and lib/app_web, so the ./brunch-config.js has been moved to ./assets/find brunch-config.js.

I thought the master branch was updated for Phoenix 1.3

I don't think so, this line of code still try to find the ./brunch-config.js instead of ./assets/find brunch-config.js.

Closing this since phx-1.3 branch works


prevent update of min max for autoscaling groups

:tada: This PR is included in version 0.2.14 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 0.2.14 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 0.2.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Upload presentation file

Add an additional endpoint for uploading ppt or PDF files to the API. Provide download link for presentation file in track.html. Add option within PP add-in to allow-disallow upload of whole presentation.

DONE!


verdaccio is requesting packages that are only hosted locally from the upstream registry.

verdaccio is requesting packages that are only hosted locally from the upstream registry.
Here's a relevant snippet/example from my verdaccio.log file:
{"name":"verdaccio","hostname":"verdaccio1","pid":3474,"sub":"in","level":30,"req":{"method":"GET","url":"/@artsman%2freact-router-nav","headers":{"origin":"https://verdaccio.artsman.com","connection":"keep-alive","host":"verdaccio.artsman.com","x-real-ip":"<IP_ADDRESS>","x-forwarded-for":"<IP_ADDRESS>","x-forwarded-proto":"https","user-agent":"yarn/1.7.0 npm/? node/v10.3.0 darwin x64","accept":"application/vnd.npm.install-v1+json; q=1.0, application/json; q=0.8, */*","authorization":"<Classified>","accept-encoding":"gzip, deflate"},"remoteAddress":"<IP_ADDRESS>","remotePort":48902},"ip":"<IP_ADDRESS>","msg":"@{ip} requested<EMAIL_ADDRESS>@{req.url}'","time":"2018-06-06T16:49:51.928Z","v":0}
{"name":"verdaccio","hostname":"verdaccio1","pid":3474,"sub":"out","level":30,"method":"GET","headers":{"Accept":"application/json;","Accept-Encoding":"gzip","User-Agent":"npm (verdaccio/3.0.0)","Via":"1.1 00bcb945d706 (Verdaccio)"},"uri":"https://registry.npmjs.org/@artsman%2Freact-router-nav","msg":"making request: '@{method} @{uri}'","time":"2018-06-06T16:49:51.938Z","v":0}
{"name":"verdaccio","hostname":"verdaccio1","pid":3474,"sub":"out","level":35,"request":{"method":"GET","url":"https://registry.npmjs.org/@artsman%2Freact-router-nav"},"status":404,"msg":"@{!status}, req<EMAIL_ADDRESS>@{request.url}' (streaming)","time":"2018-06-06T16:49:52.071Z","v":0}
{"name":"verdaccio","hostname":"verdaccio1","pid":3474,"sub":"out","level":35,"err":null,"request":{"method":"GET","url":"https://registry.npmjs.org/@artsman%2Freact-router-nav"},"status":404,"bytes":{"in":0,"out":21},"msg":"@{!status}, req<EMAIL_ADDRESS>@{request.url}', bytes: @{bytes.in}/@{bytes.out}","time":"2018-06-06T16:49:52.071Z","v":0}
{"name":"verdaccio","hostname":"verdaccio1","pid":3474,"sub":"in","level":35,"request":{"method":"GET","url":"/@artsman%2freact-router-nav"},"user":"jharris","remoteIP":"<IP_ADDRESS> via <IP_ADDRESS>","status":200,"bytes":{"in":0,"out":2053},"msg":"@{status}, user: @{user}(@{remoteIP}), req<EMAIL_ADDRESS>@{request.url}', bytes: @{bytes.in}/@{bytes.out}","time":"2018-06-06T16:49:52.073Z","v":0}
{"name":"verdaccio","hostname":"verdaccio1","pid":3474,"sub":"in","level":35,"request":{"method":"GET","url":"/@artsman%2freact-router-nav"},"user":"jharris","remoteIP":"<IP_ADDRESS> via <IP_ADDRESS>","status":200,"bytes":{"in":0,"out":2053},"msg":"@{status}, user: @{user}(@{remoteIP}), req<EMAIL_ADDRESS>@{request.url}', bytes: @{bytes.in}/@{bytes.out}","time":"2018-06-06T16:49:52.073Z","v":0}

And here's my config.yaml:
listen: http://<IP_ADDRESS>:4873

storage: ./storage

auth:
  ldap:
    type: ldap
    groupNameAttribute: 'cn'
    client_options:
      url: "ldap://the-domain.com"
      adminDn: "uid=verdaccio,cn=sysaccounts,cn=etc,dc=the-domain,dc=com"
      adminPassword: "the-password"
      searchBase: "cn=users,cn=accounts,dc=the-domain,dc=com"
      searchFilter: "(uid={{username}})"
      cache: False
      searchAttributes:
        - "*"
        - memberOf
      tlsOptions:
        rejectUnauthorized: False

uplinks:
  npmjs:
    url: https://registry.npmjs.org/

packages:
  '@*/*':
    access: verdaccio
    publish: verdaccio
    proxy: npmjs

  '**':
    access: verdaccio
    publish: verdaccio
    proxy: npmjs

logs:
  - {type: stdout, format: pretty, level: http}
  - {type: file, path: verdaccio.log, level: info}

I suspect that I should be changing the above config to NOT proxy packages that are in the @my-private-scope/* scope somehow?
If that's the case, I could use some help with the correct config file syntax for that! thanks.

Remove proxy: npmjs section for those package sections you do not want are being resolved for any uplink.

@juanpicado thanks, just reviewing the docs and it seems like I want to replace this:
'@*/*':
    access: verdaccio
    publish: verdaccio
    proxy: npmjs

with this:
'@my-scope-goes-here/*':
    access: verdaccio
    publish: verdaccio

I'll give that a shot and close the issue when I get it working :-)

If you think is unclear in the docs, please feel free to add a section on docs :-) for better understanding.

The docs are pretty good, but there isn't a specific example like the one I included in my last message.
If you think the example I gave is correct then I could make a PR.
The example is intended to NOT proxy ANY packages that are in the @my-scope-goes-here scope. So like @my-scope-goes-here/any-package
Does that sound correct?

Yes 👍 it is correct !

Closing, and PR submitted in #742

Thanks!!! Merged already


[BUG] Wrong bar number in DynamicBar

Bug Description
Whatever value you set for the barNumber, you get (actual bar number - 1). So when there is only one bar, it simply dissapear.
set barNumber to 10:

but you get 9 bars:

Well, 这是个原生bug, 尝试了官方sandbox示例也是如此😂：

Since anichart.js was removed from hypercrx, so this issue does not matter anymore. Close it.


Define capabilities and API for sl-date-range-picker

This issue is where discussion about all of the things we want to change about the sl-date-range-picker component should occur and the final definition of its capabilities and API are defined.  As these items are discussed and vetted, issues will be created to work any individual tasks, with this issue serving as the overall source of progress.
To indicate that a capability of the component needs to be verified, add a comment with **VERIFY** as the first line.
To propose a change to the component, add a comment with **PROPOSAL** as the first line.
To indicate that something needs to be researched, add a comment with **RESEARCH** as the first line.
As you are leaving comments regarding any of these VERIFY, PROPOSAL, or RESEARCH comments, link back to the comments link in your own so that the conversation can be more easily followed (in absence of threaded conversation support in Github).  This should be done on the first line of the comment via **RE: <url>**
Capabilities and API

[ ] ARIA support
[ ] ...

Tasks
Adding them here until issues are created

Update documentation for each change
Complete review of documentation against capabilities

Issues tracking these efforts
https://github.com/softlayer/sl-ember-components/issues?q=is%3Aopen+is%3Aissue+milestone%3A"v0.13.0+(Final+push+for+a+1.0.0+release)"+label%3Asl-date-range-picker

PROPOSAL
Make use of sl-calendar inside of a twbs popover instead of the jq datepicker plugin.
Support individual input labels.
Support "form-inline" class as an option or allow the user to wrap the component with it instead of forcing 2-column layout with class='row' and class='col-md-6'.  This approach is locking the user into specific grid setups/resolutions.