Operation not permitted on deploy

Description of problem
Since upgrading to dokku 0.34.1, both my static sites deploy fail with the same error:
=====> Start of  container output (.)
       chown: changing ownership of '/app/.basher': Operation not permitted
       chown: changing ownership of '/app/.basher/bash': Operation not permitted
       chown: changing ownership of '/app/.basher': Operation not permitted
       chown: changing ownership of '/app/.basher/bash': Operation not permitted
       chown: changing ownership of '/app/.basher': Operation not permitted
       chown: changing ownership of '/app/.basher/bash': Operation not permitted
       chown: changing ownership of '/app/.basher': Operation not permitted
       chown: changing ownership of '/app/.basher/bash': Operation not permitted
       chown: changing ownership of '/app/.basher': Operation not permitted
       chown: changing ownership of '/app/.basher/bash': Operation not permitted
       chown: changing ownership of '/app/.basher': Operation not permitted
       chown: changing ownership of '/app/.basher/bash': Operation not permitted
       chown: changing ownership of '/app/.basher': Operation not permitted
       chown: changing ownership of '/app/.basher/bash': Operation not permitted
=====> End of  container output (.)

How reproducible
Reproduced on two static sites.
Steps to Reproduce

Add index.html and .static to a repo
Push to deploy
See fail

Actual Results
Deploy fails
Expected Results
Deploy successful
Environment Information
dokku report APP_NAME output
-----> uname: Linux app 5.10.0-20-amd64 #1 SMP Debian 5.10.158-2 (2022-12-13) x86_64 GNU/Linux
-----> memory:
                      total        used        free      shared  buff/cache   available
       Mem:           32011        5937        6402         309       19672       25312
       Swap:           1535          79        1456
-----> disk utilization:
       Filesystem      Size  Used Avail Use% Mounted on
       /dev/md1        1.8T  136G  1.6T   8% /
-----> disk inode utilization:
       Filesystem     Inodes IUsed IFree IUse% Mounted on
       /dev/md1         117M  1.9M  115M    2% /
-----> docker version:
       Client: Docker Engine - Community
        Version:           24.0.5
        API version:       1.43
        Go version:        go1.20.6
        Git commit:        ced0996
        Built:             Fri Jul 21 20:35:45 2023
        OS/Arch:           linux/amd64
        Context:           default

       Server: Docker Engine - Community
        Engine:
         Version:          24.0.5
         API version:      1.43 (minimum version 1.12)
         Go version:       go1.20.6
         Git commit:       a61e2b4
         Built:            Fri Jul 21 20:35:45 2023
         OS/Arch:          linux/amd64
         Experimental:     false
        containerd:
         Version:          1.6.22
         GitCommit:        8165feabfdfe38c65b599c4993d227328c231fca
        runc:
         Version:          1.1.8
         GitCommit:        v1.1.8-0-g82f18fe
        docker-init:
         Version:          0.19.0
         GitCommit:        de40ad0
-----> docker daemon info:
       Client: Docker Engine - Community
        Version:    24.0.5
        Context:    default
        Debug Mode: true
        Plugins:
         buildx: Docker Buildx (Docker Inc.)
           Version:  v0.11.2
           Path:     /usr/libexec/docker/cli-plugins/docker-buildx
         compose: Docker Compose (Docker Inc.)
           Version:  v2.20.2
           Path:     /usr/libexec/docker/cli-plugins/docker-compose
         scan: Docker Scan (Docker Inc.)
           Version:  v0.23.0
           Path:     /usr/libexec/docker/cli-plugins/docker-scan

       Server:
        Containers: 18
         Running: 17
         Paused: 0
         Stopped: 1
        Images: 66
        Server Version: 24.0.5
        Storage Driver: overlay2
         Backing Filesystem: extfs
         Supports d_type: true
         Using metacopy: false
         Native Overlay Diff: true
         userxattr: false
        Logging Driver: json-file
        Cgroup Driver: systemd
        Cgroup Version: 2
        Plugins:
         Volume: local
         Network: bridge host ipvlan macvlan null overlay
         Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
        Swarm: inactive
        Runtimes: io.containerd.runc.v2 runc
        Default Runtime: runc
        Init Binary: docker-init
        containerd version: 8165feabfdfe38c65b599c4993d227328c231fca
        runc version: v1.1.8-0-g82f18fe
        init version: de40ad0
        Security Options:
         apparmor
         seccomp
          Profile: builtin
         cgroupns
        Kernel Version: 5.10.0-20-amd64
        Operating System: Debian GNU/Linux 11 (bullseye)
        OSType: linux
        Architecture: x86_64
        CPUs: 8
        Total Memory: 31.26GiB
        Name: app
        ID: EYLH:6RE3:JP7B:Y2KD:VSCG:JM27:QG6J:BJUB:G3Z2:RYQ2:LHJO:TDS3
        Docker Root Dir: /var/lib/docker
        Debug Mode: false
         File Descriptors: 124
         Goroutines: 101
         System Time: 2024-03-29T09:41:25.016609434Z
         EventsListeners: 0
        Experimental: false
        Insecure Registries:
         <IP_ADDRESS>/8
        Live Restore Enabled: false

-----> herokuish version:
       herokuish: v0.8.0
       buildpacks:
         heroku-buildpack-multi     v1.2.0
         heroku-buildpack-ruby      v267
         heroku-buildpack-nodejs    v240
         heroku-buildpack-clojure   v91
         heroku-buildpack-python    v246
         heroku-buildpack-java      v73
         heroku-buildpack-gradle    v39
         heroku-buildpack-scala     v98
         heroku-buildpack-play      v26
         heroku-buildpack-php       v247
         heroku-buildpack-go        v189
         heroku-buildpack-nginx     v25
         buildpack-null             v3
-----> dokku version: dokku version 0.34.1
-----> dokku-event-listener version: 0.15.0build+5268732
-----> dokku-update version: dokku-update 0.7.2
-----> docker-container-healthchecker version: 0.9.0
-----> docker-image-labeler version: 0.6.1build+c6e15a9
-----> git version: git version 2.30.2
-----> lambda-builder version:        0.6.0
-----> netrc version: 0.8.0build+0751c1b
 !     pack binary is not available
-----> plugn version: plugn: 0.13.0build+fd5297a
-----> sigil version: 0.10.1build+e443be0
-----> sshcommand version: sshcommand 0.17.1
-----> dokku plugins:
         00_dokku-standard    0.34.1 enabled    dokku core standard plugin
         20_events            0.34.1 enabled    dokku core events logging plugin
         app-json             0.34.1 enabled    dokku core app-json plugin
         apps                 0.34.1 enabled    dokku core apps plugin
         builder              0.34.1 enabled    dokku core builder plugin
         builder-dockerfile   0.34.1 enabled    dokku core builder-dockerfile plugin
         builder-herokuish    0.34.1 enabled    dokku core builder-herokuish plugin
         builder-lambda       0.34.1 enabled    dokku core builder-lambda plugin
         builder-nixpacks     0.34.1 enabled    dokku core builder-nixpacks plugin
         builder-null         0.34.1 enabled    dokku core builder-null plugin
         builder-pack         0.34.1 enabled    dokku core builder-pack plugin
         buildpacks           0.34.1 enabled    dokku core buildpacks plugin
         caddy-vhosts         0.34.1 enabled    dokku core caddy-vhosts plugin
         certs                0.34.1 enabled    dokku core certificate management plugin
         checks               0.34.1 enabled    dokku core checks plugin
         common               0.34.1 enabled    dokku core common plugin
         config               0.34.1 enabled    dokku core config plugin
         cron                 0.34.1 enabled    dokku core cron plugin
         docker-options       0.34.1 enabled    dokku core docker-options plugin
         domains              0.34.1 enabled    dokku core domains plugin
         enter                0.34.1 enabled    dokku core enter plugin
         git                  0.34.1 enabled    dokku core git plugin
         haproxy-vhosts       0.34.1 enabled    dokku core haproxy-vhosts plugin
         letsencrypt          0.20.3 enabled    Automated installation of let's encrypt TLS certificates
         logs                 0.34.1 enabled    dokku core logs plugin
         network              0.34.1 enabled    dokku core network plugin
         nginx-vhosts         0.34.1 enabled    dokku core nginx-vhosts plugin
         openresty-vhosts     0.34.1 enabled    dokku core openresty-vhosts plugin
         plugin               0.34.1 enabled    dokku core plugin plugin
         ports                0.34.1 enabled    dokku core ports plugin
         postgres             1.36.4 enabled    dokku postgres service plugin
         proxy                0.34.1 enabled    dokku core proxy plugin
         ps                   0.34.1 enabled    dokku core ps plugin
         redirect             0.9.1 enabled    Plugin for managing application redirects
         registry             0.34.1 enabled    dokku core registry plugin
         repo                 0.34.1 enabled    dokku core repo plugin
         resource             0.34.1 enabled    dokku core resource plugin
         run                  0.34.1 enabled    dokku core run plugin
         scheduler            0.34.1 enabled    dokku core scheduler plugin
         scheduler-docker-local 0.34.1 enabled    dokku core scheduler-docker-local plugin
         scheduler-k3s        0.34.1 enabled    dokku core scheduler-k3s plugin
         scheduler-null       0.34.1 enabled    dokku core scheduler-null plugin
         shell                0.34.1 enabled    dokku core shell plugin
         ssh-keys             0.34.1 enabled    dokku core ssh-keys plugin
         storage              0.34.1 enabled    dokku core storage plugin
         trace                0.34.1 enabled    dokku core trace plugin
         traefik-vhosts       0.34.1 enabled    dokku core traefik-vhosts plugin
=====> www app-json information
       App json computed selected:    app.json
       App json global selected:      app.json
       App json selected:
=====> www app information
       App created at:<PHONE_NUMBER>
       App deploy source:
       App deploy source metadata:
       App dir:                       /home/dokku/www
       App locked:                    false
=====> www builder information
       Builder build dir:
       Builder computed build dir:
       Builder computed selected:
       Builder global build dir:
       Builder global selected:
       Builder selected:
=====> www builder-dockerfile information
       Builder dockerfile computed dockerfile path: Dockerfile
       Builder dockerfile global dockerfile path: Dockerfile
       Builder dockerfile dockerfile path:
=====> www builder-herokuish information
       Builder herokuish computed allowed: true
       Builder herokuish global allowed: true
       Builder herokuish allowed:
=====> www builder-lambda information
       Builder lambda computed lambdayml path: lambda.yml
       Builder lambda global lambdayml path: lambda.yml
       Builder lambda lambdayml path:
=====> www builder-nixpacks information
       Builder nixpacks computed nixpackstoml path: nixpacks.toml
       Builder nixpacks global nixpackstoml path: nixpacks.toml
       Builder nixpacks nixpackstoml path:
       Builder nixpacks computed no cache: false
       Builder nixpacks global no cache: false
       Builder nixpacks no cache:
=====> www builder-pack information
       Builder pack computed projecttoml path: project.toml
       Builder pack global projecttoml path: project.toml
       Builder pack projecttoml path:
=====> www buildpacks information
       Buildpacks computed stack:     gliderlabs/herokuish:latest-22
       Buildpacks global stack:
       Buildpacks list:
       Buildpacks stack:
=====> www caddy information
       Caddy image:                   lucaslorentz/caddy-docker-proxy:2.8
       Caddy letsencrypt email:
       Caddy letsencrypt server:      https://acme-v02.api.letsencrypt.org/directory
       Caddy log level:               ERROR
       Caddy polling interval:        5s
       Caddy tls internal:            false
=====> www ssl information
       Ssl dir:                       /home/dokku/www/tls
       Ssl enabled:                   false
       Ssl hostnames:
       Ssl expires at:
       Ssl issuer:
       Ssl starts at:
       Ssl subject:
       Ssl verified:
=====> www checks information
       Checks disabled list:          none
       Checks skipped list:           none
       Checks computed wait to retire: 60
       Checks global wait to retire:  60
       Checks wait to retire:
=====> www docker options information
       Docker options build:
       Docker options deploy:         --restart=on-failure:10
       Docker options run:
=====> www domains information
       Domains app enabled:           true
       Domains app vhosts:            www.app.france.sh
       Domains global enabled:        true
       Domains global vhosts:         app.france.sh
=====> www git information
       Git deploy branch:             main
       Git global deploy branch:      master
       Git keep git dir:              false
       Git rev env var:               GIT_REV
       Git sha:
       Git source image:
       Git last updated at:
=====> www haproxy information
       Haproxy image:                 byjg/easy-haproxy:4.4.0
       Haproxy letsencrypt email:
       Haproxy letsencrypt server:    https://acme-v02.api.letsencrypt.org/directory
       Haproxy log level:             ERROR
Can't open /home/dokku/www/tls/server.crt for reading, No such file or directory
140325042730304:error:02001002:system library:fopen:No such file or directory:../crypto/bio/bss_file.c:69:fopen('/home/dokku/www/tls/server.crt','r')
140325042730304:error:2006D080:BIO routines:BIO_new_file:no such file:../crypto/bio/bss_file.c:76:
unable to load certificate
=====> www letsencrypt information
       Letsencrypt active:            false
       Letsencrypt autorenew:         true
       Letsencrypt computed dns provider:
       Letsencrypt global dns provider:
       Letsencrypt dns provider:
       Letsencrypt computed email<EMAIL_ADDRESS>
       Letsencrypt global email<EMAIL_ADDRESS>
       Letsencrypt email:
       Letsencrypt expiration:<PHONE_NUMBER>
       Letsencrypt computed graceperiod: 2592000
       Letsencrypt global graceperiod:
       Letsencrypt graceperiod:
       Letsencrypt computed lego docker args:
       Letsencrypt global lego docker args:
       Letsencrypt lego docker args:
       Letsencrypt computed server:   https://acme-v02.api.letsencrypt.org/directory
       Letsencrypt global server:
       Letsencrypt server:
=====> www logs information
       Logs computed max size:        10m
       Logs global max size:          10m
       Logs global vector sink:
       Logs max size:
       Logs vector global image:      timberio/vector:0.36.1-debian
       Logs vector sink:
=====> www network information
       Network attach post create:
       Network attach post deploy:
       Network bind all interfaces:          false
       Network computed attach post create:
       Network computed attach post deploy:
       Network computed bind all interfaces: false
       Network computed initial network:
       Network computed tld:
       Network global attach post create:
       Network global attach post deploy:
       Network global bind all interfaces:   false
       Network global initial network:
       Network global tld:
       Network initial network:
       Network static web listener:
       Network tld:
       Network web listeners:
=====> www nginx information
       Nginx access log format:
       Nginx computed access log format:
       Nginx global access log format:
       Nginx access log path:
       Nginx computed access log path: /var/log/nginx/www-access.log
       Nginx global access log path:  /var/log/nginx/www-access.log
       Nginx bind address ipv4:
       Nginx computed bind address ipv4:
       Nginx global bind address ipv4:
       Nginx bind address ipv6:
       Nginx computed bind address ipv6: ::
       Nginx global bind address ipv6: ::
       Nginx client max body size:
       Nginx computed client max body size: 1m
       Nginx global client max body size: 1m
       Nginx disable custom config:
       Nginx computed disable custom config: false
       Nginx global disable custom config: false
       Nginx error log path:
       Nginx computed error log path: /var/log/nginx/www-error.log
       Nginx global error log path:   /var/log/nginx/www-error.log
       Nginx hsts include subdomains:
       Nginx computed hsts include subdomains: true
       Nginx global hsts include subdomains: true
       Nginx hsts max age:
       Nginx computed hsts max age:   15724800
       Nginx global hsts max age:     15724800
       Nginx hsts preload:
       Nginx computed hsts preload:   false
       Nginx global hsts preload:     false
       Nginx hsts:
       Nginx computed hsts:           true
       Nginx global hsts:             true
       Nginx last visited at:
       Nginx nginx conf sigil path:
       Nginx computed nginx conf sigil path: nginx.conf.sigil
       Nginx global nginx conf sigil path: nginx.conf.sigil
       Nginx proxy buffer size:
       Nginx computed proxy buffer size: 4k
       Nginx global proxy buffer size: 4k
       Nginx proxy buffering:
       Nginx computed proxy buffering: on
       Nginx global proxy buffering:  on
       Nginx proxy buffers:
       Nginx computed proxy buffers:  8 4k
       Nginx global proxy buffers:    8 4k
       Nginx proxy busy buffers size:
       Nginx computed proxy busy buffers size: 8k
       Nginx global proxy busy buffers size: 8k
       Nginx proxy read timeout:
       Nginx computed proxy read timeout: 60s
       Nginx global proxy read timeout: 60s
       Nginx underscore in headers:
       Nginx computed underscore in headers: off
       Nginx global underscore in headers: off
       Nginx x forwarded for value:
       Nginx computed x forwarded for value: $remote_addr
       Nginx global x forwarded for value: $remote_addr
       Nginx x forwarded port value:
       Nginx computed x forwarded port value: $server_port
       Nginx global x forwarded port value: $server_port
       Nginx x forwarded proto value:
       Nginx computed x forwarded proto value: $scheme
       Nginx global x forwarded proto value: $scheme
       Nginx x forwarded ssl:
       Nginx computed x forwarded ssl:
       Nginx global x forwarded ssl:
/var/lib/dokku/plugins/available/openresty-vhosts/command-functions: line 64: fn-openresty-allowed-letsencrypt-domains-func-base64: command not found
=====> www openresty information
       Openresty access log format:
       Openresty access log path:     /var/log/nginx/www-access.log
       Openresty allowed letsencrypt domains func base64:
       Openresty bind address ipv4:
       Openresty bind address ipv6:   ::
       Openresty client max body size:
       Openresty error log path:      /var/log/nginx/www-error.log
       Openresty global hsts:         true
       Openresty computed hsts:       true
       Openresty hsts:
       Openresty hsts include subdomains: true
       Openresty hsts max age:        15724800
       Openresty hsts preload:        false
       Openresty image:               dokku/openresty-docker-proxy:0.7.0
       Openresty letsencrypt email:
       Openresty letsencrypt server:  https://acme-v02.api.letsencrypt.org/directory
       Openresty proxy buffer size:   4k
       Openresty proxy buffering:     on
       Openresty proxy buffers:       8 4k
       Openresty proxy busy buffers size: 8k
       Openresty proxy read timeout:  60s
       Openresty underscore in headers: off
       Openresty x forwarded for value: $remote_addr
       Openresty x forwarded port value: $server_port
       Openresty x forwarded proto value: $scheme
       Openresty x forwarded ssl:
=====> www ports information
       Ports map:
       Ports map detected:            http:80:5000
=====> www proxy information
       Proxy computed type:           nginx
       Proxy enabled:                 true
       Proxy global type:             nginx
       Proxy type:
=====> www ps information
       Deployed:                      false
       Processes:                     0
       Ps can scale:                  true
       Ps computed procfile path:     Procfile
       Ps global procfile path:       Procfile
       Ps procfile path:
       Ps restart policy:             on-failure:10
       Restore:                       true
       Running:                       false
=====> www registry information
       Registry computed image repo:        dokku/www
       Registry computed push on release:   false
       Registry computed server:
       Registry global image repo template:
       Registry global push on release:
       Registry global server:
       Registry image repo:
       Registry push extra tags:
       Registry push on release:
       Registry server:
       Registry tag version:
=====> www resource information
=====> www scheduler information
       Scheduler computed selected:   docker-local
       Scheduler global selected:     docker-local
       Scheduler selected:
=====> www scheduler-docker-local information
       Scheduler docker local init process: true
       Scheduler docker local parallel schedule count:
=====> www scheduler-k3s information
       Scheduler k3s computed deploy timeout:       300s
       Scheduler k3s computed image pull secrets:
       Scheduler k3s computed letsencrypt server:   prod
       Scheduler k3s computed namespace:            default
       Scheduler k3s computed rollback on failure:  false
       Scheduler k3s deploy timeout:
       Scheduler k3s global deploy timeout:         300s
       Scheduler k3s global image pull secrets:
       Scheduler k3s global ingress class:          nginx
       Scheduler k3s global kube context:
       Scheduler k3s global kubeconfig path:        /etc/rancher/k3s/k3s.yaml
       Scheduler k3s global letsencrypt email prod:
       Scheduler k3s global letsencrypt email stag:
       Scheduler k3s global letsencrypt server:     prod
       Scheduler k3s global namespace:              default
       Scheduler k3s global network interface:      eth0
       Scheduler k3s global rollback on failure:    false
       Scheduler k3s image pull secrets:
       Scheduler k3s letsencrypt server:
       Scheduler k3s namespace:
       Scheduler k3s rollback on failure:
=====> www storage information
       Storage build mounts:
       Storage deploy mounts:
       Storage run mounts:
=====> www traefik information
       Traefik api enabled:           false
       Traefik api vhost:             traefik.dokku.me
       Traefik basic auth password:
       Traefik basic auth username:
       Traefik dashboard enabled:     false
       Traefik image:                 traefik:2.11.0
       Traefik letsencrypt email:
       Traefik letsencrypt server:    https://acme-v02.api.letsencrypt.org/directory
       Traefik log level:             ERROR

How (deb/make) and where (AWS, VirtualBox, physical, etc.) was Dokku installed?:
Physical server on Debian with bootstrap script, upgraded via dokku-update
Additional information

I tried to destroy one app and recreate it, same effect
Full deploy log with trace on https://gist.github.com/abulte/72b132fd5b161085c197aedfc52f6b16

Chiming in I have the same issue after just updating dokku

Thanks for reporting! Mind adding trace output for the deploy? I'll take a look at this tonight as well.

The docs site seems to work with the latest releases of Dokku and Herokuish (though not latest of this buildpack). Retrying with an updated buildpack version:
# dokku ps:rebuild docs
-----> Cleaning up...
-----> Building docs from herokuish
-----> Adding BUILD_ENV to build environment...
       BUILD_ENV added successfully
-----> Warning: Multiple default buildpacks reported the ability to handle this app. The first buildpack in the list below will be used.
       Detected buildpacks: multi static
-----> Multipack app detected
=====> Downloading Buildpack: https://github.com/dokku/buildpack-nginx.git#v23@v23
=====> Detected Framework: .static
-----> Copy static files to www
-----> Reusing nginx binary from cache
-----> Using user provided app-nginx.conf.sigil
-----> Using default mime.types
       Using release configuration from last framework (.static).
-----> Discovering process types
       Default types for  -> web
-----> Releasing docs...
-----> Checking for predeploy task
       No predeploy task found, skipping
-----> Checking for release task
       No release task found, skipping
=====> Processing deployment checks
       No web healthchecks found in app.json. Simple container checks will be performed.
       For more efficient zero downtime deployments, add healthchecks to your app.json. See https://dokku.com/docs/deployment/zero-downtime-deploys/ for examples
 !     No healthchecks found in app.json for web process type
-----> Deploying docs via the docker-local scheduler...
-----> Deploying web (count=3)
       Attempting pre-flight checks (web.1)
-----> Executing 2 healthchecks
       Running healthcheck name='port listening check' attempts=3 port=5000 retries=2 timeout=5 type='listening' wait=5
       Running healthcheck name='default' type='uptime' uptime=10
       Healthcheck succeeded name='port listening check'
       Healthcheck succeeded name='default'
       All checks successful (web.1)
=====> Start of docs container output (web.1)
=====> End of docs container output (web.1)
       Scheduling old container shutdown in 60 seconds (web.1)
       Attempting pre-flight checks (web.2)
-----> Executing 2 healthchecks
       Running healthcheck name='default' type='uptime' uptime=10
       Running healthcheck name='port listening check' attempts=3 port=5000 retries=2 timeout=5 type='listening' wait=5
       Healthcheck succeeded name='port listening check'
       Healthcheck succeeded name='default'
       All checks successful (web.2)
=====> Start of docs container output (web.2)
=====> End of docs container output (web.2)
       Scheduling old container shutdown in 60 seconds (web.2)
       Attempting pre-flight checks (web.3)
-----> Executing 2 healthchecks
       Running healthcheck name='default' type='uptime' uptime=10
       Running healthcheck name='port listening check' attempts=3 port=5000 retries=2 timeout=5 type='listening' wait=5
       Healthcheck succeeded name='port listening check'
       Healthcheck succeeded name='default'
       All checks successful (web.3)
=====> Start of docs container output (web.3)
=====> End of docs container output (web.3)
       Scheduling old container shutdown in 60 seconds (web.3)
=====> Triggering early nginx proxy rebuild
-----> Ensuring network configuration is in sync for docs
-----> Configuring dokku.com...(using built-in template)
-----> Creating https nginx.conf
       Enabling HSTS
       Reloading nginx
-----> Running post-deploy
-----> Ensuring network configuration is in sync for docs
-----> Configuring dokku.com...(using built-in template)
-----> Creating https nginx.conf
       Enabling HSTS
       Reloading nginx
-----> Renaming containers
       Found previous container(s) (d821f3deacb3) named docs.web.1
       Renaming container (d821f3deacb3) docs.web.1 to docs.web.1.1711853022
       Renaming container docs.web.1.upcoming-9891 (2bc0770a1a05) to docs.web.1
       Found previous container(s) (06b2aa98f8dc) named docs.web.2
       Renaming container (06b2aa98f8dc) docs.web.2 to docs.web.2.1711853022
       Renaming container docs.web.2.upcoming-16040 (f2d63d5f45d5) to docs.web.2
       Found previous container(s) (f4f2617ff4c5) named docs.web.3
       Renaming container (f4f2617ff4c5) docs.web.3 to docs.web.3.1711853023
       Renaming container docs.web.3.upcoming-9201 (82f74e1d2e96) to docs.web.3
-----> Checking for postdeploy task
       No postdeploy task found, skipping
-----> Updated schedule file
-----> Shutting down old containers in 60 seconds
=====> Application deployed:
       http://dokku.com
       https://dokku.com

Yeah seems to still work as expected: https://github.com/dokku/docs/actions/runs/8495245348/job/23271311774
If anyone can provide me a way to duplicate the issue, that would be awesome.

Hi @josegonzalez, thanks for looking into this!
Trace output for the deploy is here https://gist.github.com/abulte/72b132fd5b161085c197aedfc52f6b16.
I just ran dokku-update run again this morning, but my static deploy still fails with the same error.

This seems like an issue where bash is extracted by the herokuish binary through the use of go-basher. We can probably avoid this by just using system-bash, which will be exactly what one would expect from heroku (they also use system bash).

I think this will help: https://github.com/gliderlabs/herokuish/pull/1179

dokku-update run will pull the latest herokuish version, which fixes the problem. Thanks @josegonzalez!

Thank you very much, @josegonzalez - fixed here as well.

@josegonzalez that fixed mine too! Thank you!


SQLx transaction and context error

Hello.
This issue could be related to #467 but in another way.
While the transaction rollback on context cancelled is legit and should be done, we would expect any call to DB methods after a context cancel to throw an error witch could/should be context.Canceled.
For now, after a context cancel, I can still go through all the process only having a Transaction already rollbacked or already commited only on Commit.

Seems to be related to SQL main package and not just SQLx.


Update dry-configurable

I've noticed this repo is failing with tdlib-schema <IP_ADDRESS> from 2021, suggesting it should be requiring a newer version only available through git.
Do you need help maintaining?

Applied in v3.1.0


Getting X-MBX-USED-WEIGHT value after every request.

Hi,
Does the api able to return me this header for every request call? This is the current weight limit given back from Binance server. Has this been implemented yet or its in the pipeline ?
Regards,
mishari

Hei! Does this help you?
 fetch(
        "https://www.binance.com/api/v1/depth?symbol=TRXETH")
        .then(res => {
          console.log(res.status);
          console.log(
            "x-mbx-used-weight",
            res.headers.get("x-mbx-used-weight")
          );
        })
        .catch(err => {
          console.log(`${coinType1[i]}${coinType2[j]}`.red);
        });
    }


Dropped cell false positive?

I have a public HS where I ran vanguards for testing. There is really no chance someone is gonna do a targetted attack on it because it's just a test HS.
I recently got:
WARNING[Fri Feb 15 13:48:21 2019]: Possible attack! Got a dropped cell on circ 969.
NOTICE[Fri Feb 15 13:48:21 2019]: We force-closed circuit 969
WARNING[Sat Feb 16 04:52:22 2019]: Possible attack! Got a dropped cell on circ 1292.
NOTICE[Sat Feb 16 04:52:22 2019]: We force-closed circuit 1292

What could be happening here?

What Tor version was this attached to? And what vanguards commit?

Oh and how are you exercising it? Does it just sit idle? Can you run with --loglevel DEBUG or is that too much log output?

NOTICE[Wed Feb 13 13:16:24 2019]: Vanguards 0.3.0 connected to Tor <IP_ADDRESS>-alpha-dev (git-320c52e89d0d950) using stem 1.7.1`
The HS sits idle but gets visitors from people crawling the web (its address is public on the net).
Since then I've got this a few more times:
WARNING[Fri Feb 15 13:48:21 2019]: Possible attack! Got a dropped cell on circ 969.
NOTICE[Fri Feb 15 13:48:21 2019]: We force-closed circuit 969
WARNING[Sat Feb 16 04:52:22 2019]: Possible attack! Got a dropped cell on circ 1292.
NOTICE[Sat Feb 16 04:52:22 2019]: We force-closed circuit 1292
WARNING[Sun Feb 17 02:15:26 2019]: Possible attack! Got a dropped cell on circ 1806.
NOTICE[Sun Feb 17 02:15:26 2019]: We force-closed circuit 1806
WARNING[Sun Feb 17 12:46:24 2019]: Possible attack! Got a dropped cell on circ 2037.
NOTICE[Sun Feb 17 12:46:24 2019]: We force-closed circuit 2037
WARNING[Mon Feb 18 03:17:25 2019]: Possible attack! Got a dropped cell on circ 2358.
NOTICE[Mon Feb 18 03:17:25 2019]: We force-closed circuit 2358
WARNING[Mon Feb 18 11:31:25 2019]: Possible attack! Got a dropped cell on circ 2490.
NOTICE[Mon Feb 18 11:31:25 2019]: We force-closed circuit 2490
WARNING[Tue Feb 19 11:29:27 2019]: Possible attack! Got a dropped cell on circ 2989.
NOTICE[Tue Feb 19 11:29:27 2019]: We force-closed circuit 2989
WARNING[Tue Feb 19 14:05:27 2019]: Possible attack! Got a dropped cell on circ 3047.
NOTICE[Tue Feb 19 14:05:27 2019]: We force-closed circuit 3047
WARNING[Thu Feb 21 08:46:30 2019]: Possible attack! Got a dropped cell on circ 4077.
NOTICE[Thu Feb 21 08:46:30 2019]: We force-closed circuit 4077
WARNING[Thu Feb 21 14:39:30 2019]: Possible attack! Got a dropped cell on circ 4187.
NOTICE[Thu Feb 21 14:39:30 2019]: We force-closed circuit 4187
WARNING[Fri Feb 22 06:08:31 2019]: Possible attack! Got a dropped cell on circ 4611.
NOTICE[Fri Feb 22 06:08:31 2019]: We force-closed circuit 4611

I now switched to debug logging.

Can you also enable info logs in the tor side? We may have to match them together to guess what cells are causing this.

I have been unable to reproduce this with a simple wget while loop running for several hours now. vangaurds 0.3.0 was attached to Tor <IP_ADDRESS> running a v3 onion service. The client was not using vanguards.
Is your service side v2 or v3? And how complex is the page that is likely being fetched to trigger this? A single plain html page, or lots of javascript/images/css resources? Is it possibly caused by some kind of browser navigation through the page?

Ok I switched the script to get a page that did not exist and I managed to trigger some of these.. Most seem to be cannibalized HS_VANGUARDS circuits that become service side rends. Will try to gather some more instances where the circuit is not closed right away (to see if it is just one cell or a bunch) and then dig in.

Ok, I have collected a bunch of these. A few have been HS intro circuits that were in state HSSI_CONNECTING and then changed to PATH_BIAS_TESTING.. So the dropped cell may have been either the path bias cell, or (more likely) the introduce response coming after the path bias test probe.
But four of them corresponded to these logs in tor:
{{{
Mar 08 10:22:18.000 [warn] Possible replay detected! An INTRODUCE2 cell with thesame ENCRYPTED section was seen 2 seconds ago. Dropping cell.
Mar 08 12:05:58.000 [warn] Possible replay detected! An INTRODUCE2 cell with thesame ENCRYPTED section was seen 0 seconds ago. Dropping cell.
Mar 08 14:17:21.000 [warn] Possible replay detected! An INTRODUCE2 cell with thesame ENCRYPTED section was seen 59 seconds ago. Dropping cell.
}}}

Ok I have filed https://trac.torproject.org/projects/tor/ticket/29786 for 1, https://trac.torproject.org/projects/tor/ticket/29699 for 2, and https://trac.torproject.org/projects/tor/ticket/29700 for 3.
There may be more cases of buggy "normal" client behavior than the ones I have found.
In the meantime, I think the best we can do is demote this log to notice, and maybe give select path bias circuits a free dropped cell (so we don't close them early and influence path bias counts).

Ok asn, others: That commit has workarounds for the found cases so far. Can you please pull master and look for more WARNs? Those will be new instances.

OK done. Will let you know of results.

Ok there are a 4th class of these: mystery client-side ones that do not cause Tor to emit any log lines, even at debug level. I have filed https://trac.torproject.org/projects/tor/ticket/29927 for them. Committing workarounds shortly.

Just FTR with vanguards ad3f5163ce629fbef04ea37d2d5203649eb441e5 I still got a:
NOTICE[Fri Mar 22 06:35:38 2019]: Tor bug #29699: Got a dropped cell on circ 962. (in states HS_SERVICE_INTRO HSSI_ESTABLISHED HS_SERVICE_INTRO HSSI_CONNECTING)
NOTICE[Fri Mar 22 06:35:38 2019]: We force-closed circuit 962

Just FTR with vanguards ad3f5163ce629fbef04ea37d2d5203649eb441e5 I still got a:
NOTICE[Fri Mar 22 06:35:38 2019]: Tor bug #29699: Got a dropped cell on circ 962. (in states HS_SERVICE_INTRO HSSI_ESTABLISHED HS_SERVICE_INTRO HSSI_CONNECTING)
NOTICE[Fri Mar 22 06:35:38 2019]: We force-closed circuit 962

Yes, this is intentional. In this case, I chose to close the circuit since these happen infrequently, but I did not want to allow an adversary to send a lot of them down the same path. Because of both of these, I put the log message at NOTICE level, which we define in our README as being the level for "False positives that we know about."
If you think this is still too scary, I'm open to suggestions.

Got another instance of case 4. It turns out any circuit can get a dropped cell during construction, and then fail with END_CIRC_REASON_TORPRORTOCOL. There is also no log message for this. Possible ntor handshake failure, similar to the rend case? Not sure tho. Workaround coming

Fixed in vanguards 0.3.1 that was released today.


Feature/aql blocks by line

We have all internally agreed that this is now ready to merge.
All above requested changes have been implemented by someone.
Every other part has been reviewed before it got into this branch.


Eng 944 update discoverroute to show only base

Before, the Discover route (and Integration Details Page) shows all tables in the integration. Now, it only shows the base tables--user-created tables (loadspec) are filtered out.

New:
Only CSV-uploaded & existing base tables.

Old:
The above plus the data tables saved by the user via (table_artifact).save


Triggered Webjobs Deployment

The doc states "If you want the job to respond to an event-driven trigger, you should configure it as Run continuously. The script or program is stored in the folder named site/wwwroot/app_data/jobs/continuous."
Is this correct? When I used the portal to create a Triggered type WebJob with a manual trigger it was placed in site/wwwroot/app_data/jobs/triggered

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

ID: 50a65e47-b024-0c7c-0ee9-21ff095abafd
Version Independent ID: a764689a-168d-dcef-a297-c47f84ea2d12
Content: Background jobs guidance - Best practices for cloud applications
Content Source: docs/best-practices/background-jobs.md
Service: architecture-center
Sub-service: cloud-fundamentals
GitHub Login: @dragon119
Microsoft Alias: pnp

@dalejmarshall Thanks for reaching out! We will investigate on this issue and get back to you soon.

@dalejmarshall Folow this doc for types of Webjobs.
Following are the location for the triggered and continous web job mentioned in the doc as well .
For triggered execution: site/wwwroot/app_data/jobs/triggered/{job name}
For continuous execution: site/wwwroot/app_data/jobs/continuous/{job name}

@dalejmarshall For now I will proceed with closure of this and If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Add Forest Admin

Fix https://github.com/GetBlimp/built-with-ember/issues/154

@didiertho thanks and congrats on your first contribution 🎉 We'll need a screenshot of 1000×800 pixels. This one is currently 998x578 pixels.

@jpadilla PR replaced by https://github.com/GetBlimp/built-with-ember/pull/157/files made by @SeyZ


⚠ Bofrost.de has degraded performance

In f23ad87, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1001 ms

Resolved: Bofrost.de performance has improved in a4441ee after 1 minute.


WIP: Refactor types

Refactor OSQP types related to sparse matrices. These will carry both copies of CSC and CSR matrices to speedup computations and parallelization.
To complete:

[ ] Write new types in both CSC and CSR
[ ] Adapt internal functions to new types
[ ] Adapt interface functions to the new types
[ ] Change all the external interfaces

Coverage remained the same at 86.114% when pulling 8b04e671842db0942c43196e885c4620761c799c on refactor_types into b6aef9082c4deb5e336257cd82257441d332dc85 on 0.4.0.

I think this PR would definitely help in that respect. It will be very easy to add functions to retrieve the sparsity pattern depending on the CSC or CSR representation.
I did not have time to work seriously on this but the current plan is to

fix the internal representation with this PR
implement the new ldl solver (we have a prototype working!)
implement the indirect solver and parallelizations


Module 1.1 Assignment

Given what you have learned about Git, why would you want to use Git in your classroom?

👋 Hi @misto ! Would you mind responding to the question 😅

Oh :-D I was so eager to get going, I didn't read the whole assignment :-) We're an university of applied sciences, so this means that we teach what's used  in the industry or what we believe will soon be used (sometimes industry is a bit behind). That's why we switched to teaching git (we used CVS and Subversion before) many years ago. I've also been a GitHub for many years (I'm user #2111!).


[generic] labels invalid when using tag with sha

Hey, thank you for the generic Helm chart.
since the image tag is added as value to the default labels it is not longer possible to use a sha for the image, e.g.
    image:
      tag: latest@sha256:6703475278611b5a8871769095cb1b5c624ab4d2d9d3874d81afdbe1cb4b8cce

Error message: [metadata.labels: Invalid value: "latest@sha256:6703475278611b5a8871769095cb1b5c624ab4d2d9d3874d81afdbe1cb4b8cce": must be no more than 63 characters, metadata.labels: Invalid value: "latest@sha256:6703475278611b5a8871769095cb1b5c624ab4d2d9d3874d81afdbe1cb4b8cce": a valid label must be an empty string or consist of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyValue',  or 'my_value',  or '12345', regex used for validation is '(([A-Za │ │ z0-9[][-A-Za-z0-9_.]*)?[A-Za-z0-9])?')]

@morremeyer can you please have a look

Oh, that’s unfortunate. Sorry for breaking this, I’ll take a look later!

The simplest would be undoing your change I linked. Otherwise some replace and trim magic could also work

I decided to go with some filtering magic, since that allows us to have the label with a meaningful content.
For SHA256 versions, it will now just be the hash, for others it will be filtered to only contain valid characters and truncated to 63 characters.
Once #262 is merged, you should be good to go again.
Thanks for the report!


Fix for #1607

[ ] Added or updated tests
[ ] Documented user facing changes

Changes
Implements the fix mentioned in my comment on #1607. Tested it with a fresh Laravel app and the following controller
<?php

namespace App\Http\Controllers;

class NonExistingViewController
{
    public function __invoke(): \Illuminate\View\View
    {
        return \view('non-existing');
    }
}

and now phpstan properly complains about it:
phpstan --no-progress
Note: Using configuration file /private/tmp/laravel/larastan-routes-test/phpstan.neon.dist.
 ------ -----------------------------------------------------------------------------
  Line   Http/Controllers/NonExistingViewController.php
 ------ -----------------------------------------------------------------------------
  9      Parameter #1 $view of function view expects view-string|null, string given.
 ------ -----------------------------------------------------------------------------

 [ERROR] Found 1 error

If desired, I could also implement a test similar to the one in #1734, since the current one does not seem to catch all types of issues.
Breaking changes

Could you add one test that fails without this PR?
https://github.com/nunomaduro/larastan/blob/master/tests/Type/data/view-exists.php

Hi,
Thank you for the PR. As @szepeviktor a test would be nice for this change.

We've closed the master branch. Please open a new pull request and target the 2.x branch if you wish to re-open this pull request.


PMID:25665008

increased cellular proline level
increased cellular tryptophan level
increased cellular tyrosine level
decreased cellular tryptophan level
decreased cellular tyrosine level
increased cell population growth on glutamine nitrogen source
increased cell population growth on arabinose carbon source
increased cell population growth on melibiose carbon source
decreased cell population growth on glutamine nitrogen source
decreased cell population growth on arabinose carbon source
decreased cell population growth on melibiose carbon source
resistant to tellurite
resistant to caesium
sensitive to caesium
sensitive to tellurite CHEBI:30477

increased cellular proline level FYPO:0005237
increased cellular tryptophan level FYPO:0005238
increased cellular tyrosine level FYPO:0005239
decreased cellular tryptophan level FYPO:0005240
decreased cellular tyrosine level FYPO:0005241
decreased cell population growth on glutamine nitrogen source FYPO:0005242
increased cell population growth on glutamine nitrogen source FYPO:0005243
decreased cell population growth on arabinose carbon source FYPO:0005244
increased cell population growth on arabinose carbon source FYPO:0005245
decreased cell population growth on melibiose carbon source FYPO:0005246
increased cell population growth on melibiose carbon source FYPO:0005247
resistance to tellurite FYPO:0005248
resistance to caesium FYPO:0005249
sensitive to caesium FYPO:0005250
sensitive to tellurite FYPO:0005251

edit file: 245cc5e9bac91981cfa01a2e702333db2eae4f12
release: fac9f9f87d3b8884f99eb5614ae1338d20e8f50b


PHP 7.1 FIX: FUNCTION MCYRPT_XXX IS DEPRECATED

FIXED: FUNCTION MCYRPT_XXX IS DEPRECATED with PHP 7.1-RC in MAC OSX
check line 75,76,77 and 86

This is not a fix, this is a bunch of suppression operators that will still trigger issues depending on which framework you use. As the extension will be permanently removed in PHP 7.2 what we really need is to patch the library into not selecting the Mcrypt mixer on PHP 7.1 and above.


Add cuda 12.2

Adds cuda 12.2 to the build matrix.

continued in #438 to get the actions to actually run


correction saml2 bearer documentation

SAML2 bearer flow is often used from our side and therefore many people check the documentation on CF side , so that should be consistent with behaviour.
First version used always token endpoint but later it was refactored with behaviour of saml validation, therefore different endpoint

@strehle Thank for bringing this to our attention.  Added this to the team's backlog for review and merge.

The documentation change went out as a part of 74.16.0.  Thank you!


NullPointerException on DefaultPaginator.next() due to Null Thumbnail Value

When trying to get a paginator that contains a post with a null thumbnail, an npe will be thrown
Error message: https://pastebin.com/jijruUhv

Is there any suggested workaround for this yet? I can't load the Front Page at all anymore, due to "Null Type Value."

Just like to add that my frontpage, and anything else using DefaultPaginator is currently broken. Trying to do a workaround with BarebonesPaginator, which seems to be fine

I'm having the same problem with the same stack trace as @JoeCourtneyW. Any progress on this?

What sorting are you using? I can't reproduce:
redditClient.subreddit("all").posts()
    .sorting(SubredditSort.NEW)
    .limit(100)
    .build()
    .accumulate(maxPages = 10)

@mattbdean I can't seem to reproduce the error myself, I believe it occured on subreddits that contained deleted posts. The deleted posts would then have a null thumbnail and throw the npe. I'm not sure though.

I've made getThumbnail() nullable. I've also added Submission#hasThumbnail() for convenience.


Use the ParDo Application to Cache DoFns

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[x] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[x] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[x] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[x] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

A DoFn application is the scope of reuse.

R: @kennknowles

Conceptually LGTM. An important fix.


Stop adding custom properties to ApplicationInsights internal traces

#181

thanks, :shipit: . Can you also mark these traces with "SyntheticSource=SDKTelemetry"


WIP: add ability to pass additional info to layout items

Add ability to provide addinional information to LayoutItem #665

currently doesn't work with data-grid attribute, so WIP

nvm
i was wrong. it actually does work with both data-grid attribute and layout prop


Backup trying to operate on renamed folders

If you:

go through imap-backup setup, nominating specific folders
rename the folders on the email service (eg Gmail)
attempt to update the folder selection through imap-backup setup

the new named folder is available for selection (defaulting to not being selected) but the old named folder is not available for de-selection.
Then, running imap-backup will try and fetch from the (now non-existent) folder, resulting in an error like:
$ imap-backup
Traceback (most recent call last):
	20: from /Users/tom/.rbenv/versions/2.5.5/bin/imap-backup:23:in `<main>'
	19: from /Users/tom/.rbenv/versions/2.5.5/bin/imap-backup:23:in `load'
	18: from /Users/tom/.rbenv/versions/2.5.5/lib/ruby/gems/2.5.0/gems/imap-backup-2.0.0/bin/imap-backup:75:in `<top (required)>'
	17: from /Users/tom/.rbenv/versions/2.5.5/lib/ruby/gems/2.5.0/gems/imap-backup-2.0.0/lib/imap/backup/configuration/list.rb:17:in `each_connection'
	16: from /Users/tom/.rbenv/versions/2.5.5/lib/ruby/gems/2.5.0/gems/imap-backup-2.0.0/lib/imap/backup/configuration/list.rb:17:in `each'
	15: from /Users/tom/.rbenv/versions/2.5.5/lib/ruby/gems/2.5.0/gems/imap-backup-2.0.0/lib/imap/backup/configuration/list.rb:19:in `block in each_connection'
	14: from /Users/tom/.rbenv/versions/2.5.5/lib/ruby/gems/2.5.0/gems/imap-backup-2.0.0/bin/imap-backup:76:in `block in <top (required)>'
	13: from /Users/tom/.rbenv/versions/2.5.5/lib/ruby/gems/2.5.0/gems/imap-backup-2.0.0/lib/imap/backup/account/connection.rb:48:in `run_backup'
	12: from /Users/tom/.rbenv/versions/2.5.5/lib/ruby/gems/2.5.0/gems/imap-backup-2.0.0/lib/imap/backup/account/connection.rb:104:in `each_folder'
	11: from /Users/tom/.rbenv/versions/2.5.5/lib/ruby/gems/2.5.0/gems/imap-backup-2.0.0/lib/imap/backup/account/connection.rb:104:in `each'
	10: from /Users/tom/.rbenv/versions/2.5.5/lib/ruby/gems/2.5.0/gems/imap-backup-2.0.0/lib/imap/backup/account/connection.rb:107:in `block in each_folder'
	 9: from /Users/tom/.rbenv/versions/2.5.5/lib/ruby/gems/2.5.0/gems/imap-backup-2.0.0/lib/imap/backup/account/connection.rb:50:in `block in run_backup'
	 8: from /Users/tom/.rbenv/versions/2.5.5/lib/ruby/gems/2.5.0/gems/imap-backup-2.0.0/lib/imap/backup/account/folder.rb:42:in `uid_validity'
	 7: from /Users/tom/.rbenv/versions/2.5.5/lib/ruby/gems/2.5.0/gems/imap-backup-2.0.0/lib/imap/backup/account/folder.rb:78:in `examine'
	 6: from /Users/tom/.rbenv/versions/2.5.5/lib/ruby/2.5.0/net/imap.rb:470:in `examine'
	 5: from /Users/tom/.rbenv/versions/2.5.5/lib/ruby/2.5.0/monitor.rb:226:in `mon_synchronize'
	 4: from /Users/tom/.rbenv/versions/2.5.5/lib/ruby/2.5.0/net/imap.rb:472:in `block in examine'
	 3: from /Users/tom/.rbenv/versions/2.5.5/lib/ruby/2.5.0/net/imap.rb:1253:in `send_command'
	 2: from /Users/tom/.rbenv/versions/2.5.5/lib/ruby/2.5.0/monitor.rb:226:in `mon_synchronize'
	 1: from /Users/tom/.rbenv/versions/2.5.5/lib/ruby/2.5.0/net/imap.rb:1271:in `block in send_command'
/Users/tom/.rbenv/versions/2.5.5/lib/ruby/2.5.0/net/imap.rb:1217:in `get_tagged_response':  Unknown Mailbox: Personal/2 (now in authenticated state) (Failure) (Net::IMAP::NoResponseError)

You can go into ~/.imap-backup/config.json and remove the old folders manually from the folders JSON key, and then it operates normally.
A solution to this would be for subsequent folder specifications (via imap-backup setup) to remove non-existent folders from the current list of selected folders, though I'm not sure what impact this would have on previously fetched .mbox files.

@msbit Thanks for the bug report.
I've released version 2.1.0 to address this issue.
Missing folders are now skipped during download, and are removed from the list of folders during setup.


Draft: Allow USB pass through of specific port path

With the fixes to USB device pass-through, allowing multiple identical
devices to be used inside one virtual machine, users may want to route
specific USB devices to specific instances. This can be done by
following the physical topology of hubs and ports.
The new portglob property can be used to optionally match the port
path to a glob. Port path is a sequence of numbers separated with
dashes, with each number representing a port and dash representing
connections between hubs.
This allows adding arbitrary device plugged to a physical port or a
particular hub to a specific instance. The property is supported for
usb device type both virtual machines and on containers and for
unix-hotplug on containers only.
Signed-off-by: Zygmunt Krynicki<EMAIL_ADDRESS>

This pull request didn't trigger Jenkins as its author isn't in the whitelist.
An organization member must perform one of the following:

To have this branch tested by Jenkins, use the "ok to test" command.
To have a one time test done, use the "test this please" command.

Those commands are simple Github comments of the format: "jenkins: COMMAND"

Looks like a pretty useful feature.
From a commit structure, we'd need:

api: Add usb_portpath extension (adds to doc/api-extensions.md and shared/version/api.go)
doc: Add portpath field to usb and unix-hotplug
shared/validate: Add IsGlob
lxd/device: Add portpath support

Thanks for the review @stgraber, I'll re-word and split this as suggested.
I've realized that the unix-hotplug code I wrote is buggy, I'd either leave that out OR look at how to reliably find the port mapping from DEVPATH from udev. The problem is that unlike in the easier usb case, the port is hidden somewhere in the path, and we are looking at /some/very/long/1-2/path/like/this. It's not immediately clear to me how to approach this without walking sysfs to look at something that is a usb device in the chain.

Oh and for a bit of extra context: Initially I've used bus number and device number but I quickly realized those are useless as they are dynamically allocated and thus entirely unstable.
I wish there was something higher-level, like "always plug this device to VM", where lxd could compute something akin to snap hotplug interfaces, where for certain device types, there's a bit more uniqueness than the port path. In my world, usb/ttl uarts have serial numbers, mbed devices have serial numbers, disks have plenty of identification. I wish we could offer that to users. Still, the port path is a perfectly serviceable compromise as it gets the job done.

There's some conflicts to resolve on this branch.

I lost track of this branch, I'll pick it up shortly.

Thanks!

I lost track of this branch, I'll pick it up shortly.

Any luck with this @zyga ?

@zyga this needs rebasing please

@zyga this needs rebasing please

Ack. I will rebase this as soon as I can.
I'm sorry for neglecting this change.

@stgraber shall we close this?


Modify READMe.md file

Issue ticket number and link
Add clickup ticket link here
Description
Add a few steps in the README.md file to assist users with configuring the server and clients side monitoring tools.
Type of change
Please delete option that is not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

Related PRs
List related PRs below

branch
PR

other_pr
link

Thanks! This looks pretty minor, LGTM


Split up required and optional args in help output

:wave: @bcoe  Love this project. While using this on my own project I found that I had a handful of optional arguments which produced a very busy help output.
With a small change I was able to split up the arguments which are required from those which are optional.

I'll open a pull request which closes this issue out also, but I wanted to give you a heads up first.

@ammeep I don't want to speak for Ben, but I do want to say thanks!
I think this is a good idea, but we might want to consider implementing option groups as a more flexible way to achieve this. Then CLI authors could organize options in usage content any way they'd like.
Another thing to consider is i18n. If option grouping could be based on any arbitrary string, then it would be nice if there was an "official" way to support different languages/locales for the consumer-defined strings (i.e. some kind of built-in support for translating "Required options:" into the OS locale/language that yargs is going to use for its own strings). CLI authors can use y18n on their own, but there's currently no way to couple/sync that with the y18n instance/files that yargs uses.
So I think a more robust solution would include (a) arbitrary option grouping that (b) accounted for i18n in some way. Thoughts?

Hey @ammeep, sorry for the slow response it's been a crazy busy few weeks for me. I love the idea of providing more flexibility for grouping together options! I'm with @nexdrew, however, that it would be slick if we could provide a generic API for handling the grouping together of options.
@andrew and I have been discussing the work we'd like to take on for<EMAIL_ADDRESS>
I'd like to overhaul the command API a little bit, I think it could be made more intuitive.
Andrew already had a few thoughts about making argument layout more flexible.
I'd like to triage the existing tickets, there might be some other potentially breaking changes worth making if we're planning on a major bump.

Long story short, I'd love to start a conversation about some API changes that are worth making for the next major version, and I think we can provide the functionality you're looking for in the process. I sent you an invite to the yargs Slack, I'll be hanging out and hacking a bit this weekend.

See the new .groups() option in<EMAIL_ADDRESS>\o/ let me know if this does the trick.


Replace InferenceDataFrame with VirtualDataFrame

Depends on https://github.com/NVIDIA-Merlin/core/pull/102

Closing since the upstream PR was also closed


Graceful Tunnel Shutdown

Adding an option for SSH to cleanup a broken connection endpoint in case of network failure, as discussed in #25

Would you like to add your name (nick or email) to CONTRIBUTORS.md?


All TCP outbound traffic drooped with CODE NR during istio upgrade

Bug Description
We are experiencing an intermediate issue while upgrading istio from 1.7.8 to 1.8.6. During the upgrade, all outbound TCP traffic originated where 1.7.8 are drooped if the respective sidecar proxy connects to the istiod 1.8.6.
The connection works fine when the control plane and proxy are both 1.7.8 or 1.8.6.
Access Log
 "- - -" 0 NR "-" "-" 0 0 0 - "-" "-" "-" "-" "-" - - <IP_ADDRESS>:6369 <IP_ADDRESS>:48660 - -
The 1.7.8 proxy configured by 1.8.6 istiod has filter chain matches that look like bellow. The match config included   "transportProtocol": "raw_buffer" which I think is the source of the issue.
{
  "transportProtocol": "raw_buffer",
  "applicationProtocols": [
    "http/1.0",
    "http/1.1",
    "h2c"
  ]
}

It's not clear what's the root cause but looks like code NR indicates a filter mismatch case.
Any suggestion?
Version
$istioctl version
client version: 1.8.6
control plane version: 1.8.6
data plane version: 1.7.8 (198 proxies)

Additional Information
No response

@softcane sorry you are seeing issues. Unfortunately, istio 1.7 and 1.8 are EOL, so even if we did discover a bug here we could not patch it. I would recommend looking into https://istio.io/latest/docs/setup/upgrade/canary/, which is the recommended way to upgrade and makes this type of error nearly impossible (its likely due to version skew between proxy and control plane - with canary upgrade there is no skew).


broken react-router-redux 5.0.0-alpha.7 pulled in

The broken react-router-redux 5.0.0-alpha.7 is pulled in by the very unfortunate react-router-redux ~5.0.0-alpha.6 pinning, resulting in
Module not found: Error: Cannot resolve 'file' or 'directory' ./selectors in
/.../node_modules/admin-on-rest/node_modules/react-router-redux

Can you open a PR against master removing the ~ from the dependency?

This was fixed in alpha.8 a few hours ago


Which versions of keras and theano were used in this implementation?

Hi,
I would like to reproduce your experiment. Could you please give the versions of the dependency libraries?

We use the Keras 1.1.0 with the Theano 0.8.2 backend for this repo.

Thank you so much!


Add string.{char, lower, upper, reverse} to stdlib

I believe that a "sufficiently smart compiler" would compile this String::new to the same machine code as the existing implementation. (Pretty sure rustc isn't that compiler, though.)
Could retain the existing implementation for performance.

Should be rebased to resolve conflicts


Adding initial ci workflows

Issues

Fixes #5 #7

Description

Added unit test workflow that runs on every pull request (currently not running unit tests, just compiling.
Added pre-release workflow that compiles the application, firmware, driver installer, creates an advanced installer and a draft pre-release. It runs on every push to master.
The idea is to create a draft pre-release with every pull request merge that can be manually downloaded and tested before creating a public release.\
Added release workflow, same as the pre-release but runs on tag creation and creates a public release.

Types of changes
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[x ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] Compiled and tested requested changes
[x] Updated the documentation, if necessary
[x] Added myself to the copyright holder to the AUTHORS file
[x] Reviewed the guidelines for contributing to this repository.
[x] I am requesting to pull a topic/feature/bugfix branch.

Eliminate pre-release. Tags don't exists so we'd need to create releases with commit hashes and it becomes messy. Instead upload the artifacts to the job.


Walk Through Effect in pannellum?

Hello Friends,
Can any one help me. In implementing Walk through effect in pannellum..
Thanks in Advance.

You're going to have to be a bit more specific with what you need help with.

Am using pannellum for stitching 360 degree images..I want to implement walk through effect when transition happens between the images...

I guess (s)he means the effect one sees in Google Street View between some panoramas.

@strasis exactly I mean the same..
How can I achieve transition switching between panoramas

Perhaps a zoom towards hotspot feature like that in #706 would be a compromise?
I've implement such a feature using LookAt before changing the scene, but it requires some extra coding.
I was also toying with the idea of manually separating a panorama into two layers; foreground and background.  Imagine a panorama of a forest with mountains behind / above.  The foreground layer would consist of forest with the remainder transparent. The background layer would consist of the mountains with lower half (the forest) removed and grassy slopes reconstructed using gimp.  The idea was then to place the two panoramas in two separate pannellum divs, the foreground on top of the background, and then zoom in on the foreground faster than the background. This would give the Street View-Like transition.
One stumbling block I don't think Pannellum supports transparencies, or am I wrong?

Am manipulating the hfov value to get the zoom effect, but it's not up to the mark. Can you please provide any sample example how to use LookAt

Sure.  It will take me a while to unpick some of the extra code in my scripts first.
Regards
Derek

On 31 Aug 2019, at 14:23, sravan406<EMAIL_ADDRESS>wrote:
Am manipulating the hfov value to get the zoom effect, but it's not up to the mark. Can you please provide any sample example how to use LookAt
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Okay, untangling my 2000 plus lines of code is too large of an undertaking.  But this should give you the jist of how a zoom to a new scene can be achieved.
Please note that I've not tested this outside my own script, so you may need to tidy this up.
Declare a Hotspot Click Handler up front. Something like this...
var HotSpotClickHandler = function(){StartZoom()}

Add clickHandlerFunc to your pannellum hotspot instead of a sceneId, eg
"hotSpots": [
		{
			"pitch": 2,
			"yaw": 132,
			"type": "scene",
			"text": "Next Scene",
			"clickHandlerFunc": HotSpotClickHandler
		}
	]

Create the MoveLocation function called by the event handler.
{
	var pZ = 0 ; // Or other pan angle to Zoom in on.
	var yZ = 0 ; // Or other yaw angle to Zoom in on.
	var vZ = 25 ; // Or other Hfov angle to Zoom in on.
	var pS = 100 ; // Or other zoom speed
	Pannellum.lookAt(pZ,yZ,vZ,pS); // Will initiate the zoom where Pannellum is the name of the pannellum instance.
	setTimeout(function(){Step_2();}, 100);  // Call Step 2
}`

function Step_2()  // Loops until the LookAt is finished
{

   pI=Math.round(Pannellum.getPitch()); // get actual pitch and round
   yI=Math.round(Pannellum.getYaw()); // get actual yaw and round
	vI=Math.round(Pannellum.getHfov()); // get actual Hfov and round

	if(yI>180){yI=yI-360;Pannellum.setYaw(yI,0);}
	if(yI<-180){yI=yI+360;Pannellum.setYaw(yI,0);}

	if(pI===pZ1 && yI===yZ1 && vI===vZ1)  // Has LookAt finished
	{
		setTimeout(function(){Step_3();}, 10);
	}
	else
	{
		setTimeout(function(){Step_2();}, 100);  // Call Step 2 again, loop until LookAt has finished
	}

}

function Step_3()  // Loops until the LookAt is finished
{
	var nameOfNewScene = "Scene2" // Or what ever the name of the next scene is.
	Pannellum.loadScene(nameOfNewScene);
}`

That gets very complicated very quickly. The feature matching would need to be at least semi-automated to make it useful, and the transforms would need to be implemented on the sphere instead of the plane, which would be more difficult. I suspect a better approach would be to use a machine-learning-based algorithm to pre-calculate a depth map for each panorama and use those as part of the transition (for both the source and destination panoramas). Such an approach would be fully automated and could treat each panorama separately, which simplifies things.


Fix/regression 18110 composer should have the same height in other platforms

Details

Composer in Android should have the same height in other platforms
Fixed Issues

$ https://github.com/Expensify/App/issues/18110
PROPOSAL: https://github.com/Expensify/App/issues/18110#issuecomment-1540545428
$ https://github.com/Expensify/App/issues/19358
Tests

Open any chat
Lose focus from compose box
Verify Composer in all platforms should have the same height and hover over compose box and observe that few area above and below 'Write something...'
Verify app should display edit pointer on the whole compose box and on double click, it shouldn't select placeholder text

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

Open any chat
Lose focus from compose box
Verify Composer in all platforms should have the same height and hover over compose box and observe that few area above and below 'Write something...'
Verify app should display edit pointer on the whole compose box and on double click, it shouldn't select placeholder text

[ ] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos 18110

Web

https://github.com/Expensify/App/assets/129500732/6ef673f2-8c43-469f-b37b-4d35aec50553

Mobile Web - Chrome

https://github.com/Expensify/App/assets/129500732/6ad3fc10-adcd-420e-ad02-0d773b32d7f8

Mobile Web - Safari

https://github.com/Expensify/App/assets/129500732/cb0045be-c006-4bd4-bd6a-668d30ce592b

Desktop

https://github.com/Expensify/App/assets/129500732/81382f98-845a-4d86-93c4-1ce1ce49abf3

iOS

https://github.com/Expensify/App/assets/129500732/2dbb07a1-0764-4139-a4b4-635cd28e716e

Android

https://github.com/Expensify/App/assets/129500732/6130788c-f047-4cff-a5fe-349a83241912

Screenshots/Videos 19358

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

@MariaHCD I added the link to the issue is "#18110", but right format is "https://github.com/Expensify/App/issues/", so please help to assign reviewer again. Sorry for this inconvenience.

@dukenv0307 Can you remove the word REGRESSION and just keep the linked issue?

@dukenv0307 Can you remove the word REGRESSION and just keep the linked issue?

I updated

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

https://github.com/Expensify/App/assets/3069065/ad8a090b-226b-460b-9666-0bc3cc7caaa9

Mobile Web - Chrome

Mobile Web - Safari

Desktop

https://github.com/Expensify/App/assets/3069065/bdf954a5-ec80-49ff-8a46-fa4ae162b384

iOS

Android

@dukenv0307 for all my Android emulators, the height shows up as 38.2, unlike 38 in your screenshot (and other platforms).

I think it's best to fix in another PR. Thanks for highlighting that. Can you take the latest pull for main and resolve conflicts?

@tgolen did you get a chance to look at the previous comments?

Quick bump @tgolen

Thanks for the bump @dukenv0307. Can you resolve the conflicts please?
@tgolen I've tested this, can you please take a look at the PR?

Hi! I was out on sabbatical for 2 months. Next time, if I (or anyone from Expensify) doesn't respond in a couple of days, please start asking for help in Slack to see what is going on and move forward with urgency on issues, not just waiting for an update indefinitely.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.


Style improvement: Pop-up border

Seems like there should not be a border around this popup

This might be a local issue for me, since other extensions are doing this aswell


Library throws "The specified Visual is not an ancestor of this Visual"

I'm using your library (version 1.0.0-ALPHA011) for ordering and moving items beetween ListViews and sometimes an exception "The specified Visual is not an ancestor of this Visual" is thrown. It happens randomly (~10-20% of drag&drops).
Update: it happens only with ListView items which contains in their DataTemplate a nested ListView and I start dragging by clicking on the item from a nested ListView (also after item is dropped, an item from dropped item's nested listview is moved out from parent item... but nested ListView has not allowed drag&drop functionaliy -> IsDragSource is set to false and drag adorner shows entire item with nested ListView while dragging)
Stack trace:
   at System.Windows.Media.Visual.TrySimpleTransformToAncestor(Visual ancestor, Boolean inverse, GeneralTransform& generalTransform, Matrix& simpleTransform)
   at System.Windows.Media.Visual.TransformToAncestor(Visual ancestor)
   at GongSolutions.Wpf.DragDrop.Utilities.ItemsControlExtensions.GetClosest(ItemsControl itemsControl, List`1 items, Point position, Orientation searchDirection) in d:\projects\git\gong-wpf-dragdrop\GongSolutions.Wpf.DragDrop\Utilities\ItemsControlExtensions.cs:line 361
   at GongSolutions.Wpf.DragDrop.Utilities.ItemsControlExtensions.GetItemContainerAt(ItemsControl itemsControl, Point position, Orientation searchDirection) in d:\projects\git\gong-wpf-dragdrop\GongSolutions.Wpf.DragDrop\Utilities\ItemsControlExtensions.cs:line 134
   at GongSolutions.Wpf.DragDrop.DropInfo..ctor(Object sender, DragEventArgs e, DragInfo dragInfo) in d:\projects\git\gong-wpf-dragdrop\GongSolutions.Wpf.DragDrop\DropInfo.cs:line 78
   at GongSolutions.Wpf.DragDrop.DragDrop.DropTarget_PreviewDragOver(Object sender, DragEventArgs e) in d:\projects\git\gong-wpf-dragdrop\GongSolutions.Wpf.DragDrop\DragDrop.cs:line 845
   at GongSolutions.Wpf.DragDrop.DragDrop.DropTarget_PreviewDragEnter(Object sender, DragEventArgs e) in d:\projects\git\gong-wpf-dragdrop\GongSolutions.Wpf.DragDrop\DragDrop.cs:line 820
   at System.Windows.DragEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget)
   at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
   at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
   at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
   at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
   at System.Windows.ContentElement.RaiseEvent(RoutedEventArgs e)
   at System.Windows.OleDropTarget.RaiseDragEvent(RoutedEvent dragEvent, Int32 dragDropKeyStates, Int32& effects, DependencyObject target, Point targetPoint)
   at System.Windows.OleDropTarget.MS.Win32.UnsafeNativeMethods.IOleDropTarget.OleDragOver(Int32 dragDropKeyStates, Int64 point, Int32& effects)

@DominikPalo Can you provide some code? What kind of items are hosted in your ListViews? Is there a special template or something else?

    <DataTemplate DataType="{x:Type vm:MyParentItemModel}">
        <Grid AllowDrop="True">
            <Grid.RowDefinitions>
                <RowDefinition />
                <RowDefinition />
            </Grid.RowDefinitions>
            <Label Grid.Row="0" Content="My label" />
            <!-- This nested ListView contains some items and problem occurs when I start dragging parent item from position in nested ListView -->
            <ListView Grid.Row="1" ItemsSource="{Binding ChildItems}" AllowDrop="False" ScrollViewer.HorizontalScrollBarVisibility="Disabled" ScrollViewer.VerticalScrollBarVisibility="Disabled" />
        </Grid>
    </DataTemplate>

This is not my original DataModel, but I created this simplified DataModel for demonstration - it also throws the described exception.


Question on how to use update_one function

Hi,
I am having problem with update_one function. I want store time series data in MongoDB and, as suggested in many tutorials, I want to store one minute per document and each second I would like to store in a vector field the measurement. My question is: how can I update the vector inside the document? How can I add each second a new measurement value?
Thanks in advance guys.

Does $push not work?
let update = doc! { "$push" => { "minutes.5" => 25 } };
db.collection('times').update_one(query, update, None).ok().expect("update failed");

This should probably be all right to close now, given that there hasn't been any response for a few months.

Yep good call


Implement c_cpp_properties.json file generator fixes #1201

What problem did you solve?
This PR implements a command "Generate c_cpp_properties.json" that generates the file by collecting information from invoking the compiler and from the DESCRIPTION file.
This enables code completion, IntelliSense, etc. for C/C++ files in R packages.
The issue is described in more detail here: https://github.com/REditorSupport/vscode-R/issues/1201
Demo
https://user-images.githubusercontent.com/33600480/192030853-b1674671-192c-44a8-b7ae-845c62aaa02a.mp4
TODO

This seems to work under Windows and Ubuntu for the projects I tried it with, it should however be tested on more packages and platforms before it's merged.
At some point it might make sense to suggest to the user to run this when the Makevars or DESCRIPTION files change.
The command could be renamed to something like 'Configure R-extension for C/C++' to be more descriptive.

I just realized: With some packages you need to run ./configure before running the command (and might want to run ./cleanup after) in order to capture all includes and defines. I will add an automation of this later.

I came across this tweet which points to https://github.com/r-lib/usethis/blob/main/R/vscode.R, but it does not look like general enough. Not sure if it is helpful here.

Thanks, this captures LinkingTo detectives from the DESCRIPTION and general R paths, but this PR also compiles dummy files to capture everything in configure and Makevars (defines, local includes, system dependencies, ...). I imagine the usethis script is meant to be edited manually later.
(I'm not sure why the CI fails, it might be an unrelated issue)

I tried it with latest httpgd on macOS, and the following file is produced (an empty includePath is present):
{
  "configurations": [
    {
      "name": "Mac",
      "defines": [
        "NDEBUG",
        "BOOST_NO_AUTO_PTR",
        "FMT_HEADER_ONLY"
      ],
      "includePath": [
        "${workspaceFolder}/src",
        "/Library/Frameworks/R.framework/Versions/4.2/Resources/include",
        "${workspaceFolder}/src/lib",
        "/usr/local/include",
        ""
      ],
      "compilerPath": "/usr/bin/clang++",
      "cStandard": "${default}",
      "cppStandard": "gnu++14",
      "intelliSenseMode": "macos-clang-x64"
    }
  ],
  "version": 4
}

with the following error:

That has probably to do with the the escaping of the small R code that collects the library paths, I will put it in an R file shortly.
R code is executed at many parts of the extension in different ways, maybe there should be a unified interface for that. If I have time I will prepare a separate PR.

If the command is executed in a package that does not require c/c++ compilation (e.g. lintr), the following error shows up:

It would be nice to have more understandable error messages regarding such case.

Thank you for your comments and the review!


Add new :append_datetime param and fix dates to UTC.

This PR adds a new stamp_changelog action argument: stamp_date_time. Specifying true stamps the changelog in the format of standard iso8601 date time "2020-12-17T22:25:13Z". By default it is false and when true it overrides stamp_date. The date chosen, whether by specifying stamp_date: true or stamp_date_time: true are placed in the env variable FL_UPDATE_DATE_VAL, FL_UPDATE_DATE_TIME_VAL respectively.
It also fixes the error being given by fastlane that the stamp_date arg was not a string and makes all the dates used for the stamp_dates be in UTC time.
I figure this PR may require some additional modifications depending on the needs of the project but I figured it could be built upon 😄.

Hi @donileo ,
thanks a lot for the idea how to improve the plugin and actual contribution ❤. I understand your need from issue #52

I'm looking to include the time along with the date in the form of 2020-12-08T21:51Z

the approach (add additional stamp_date_time param in update_changelog.rb and stamp_changelog.rb ) you have chosen in this PR to satisfy your need is OK, but I see 2 potential problems long-term:

testability & complexity : adding an additional param increases the code complexity and what has to be tested
confusion for users : it may be confusing at glance to figure out why this plugin has 2 params for date/time instead of just one

Suggestion for improvement:
Instead of adding a new param for date & time format, I suggest to enhance the existing stamp_date and let the user specify (override) the (default) format of date/time, here is how:

rename stamp_date param to something like.....e.g. stamp_datetime_format?
make stamp_date's default_value %Y-%m-%d - so that we stay backwards compatible.
make stamp_date's is_string true
Once we have the above interface in place, any user (such as yourself 😉) can pass in stamp_datetime_format: %FT%T%:z, which will result in 2020-12-08T21:51Z
In the update_changelog.rb you won't need this if/else and instead leverage the strftime Ruby method to create date & time format specified via string 👍

Wow I forgot about this 😄 lol. That's what happens when you get caught up with work, implement your own solution that works for your own cases and then forget about requested changes such as the above lol. Let's see if I can do this today 😄, no promises..

Ok doing this now. Good suggestions. On the make stamp_date's default_value %Y-%m-%d - so that we stay backwards compatible. there is an issue with "staying compatible". Staying compatible means using keep a changelog bad time format of not specifying whether the date being stamped is in local time or UTC/Zulu time. If we assume they mean local their standard needs to specify the local timezone offset such as -0500 but they don't do that. Given all of that I'm making the default assumption that the time being stamped is UTC time and as such append Z to the end of the date formats to let the user know this.

@pajapro Thanks 👍, no problem.
I think another change (not sure if its considered breaking) that needs to be mentioned in the release is that the actual stamped date is now in UTC format - not local since previously it was using Time.now which returned local time. I feel that is important enough to possibly even mention in other places like in the stamp_datetime_format for which I'll make a future PR. Please let me know your thoughts.

Good point, for now I at least updated release notes.


Suggestion: Switch to https://github.com/gofrs/uuid

you might want to switch your UUID library
see
https://github.com/gofrs/uuid
https://github.com/satori/go.uuid/pull/75
your friends at the AKS engine did as well
https://github.com/Azure/aks-engine/pull/466
cheers

We have switched to github.com/google/uuid https://github.com/google/uuid seems to be maintained, but I am not sure if Microsoft is allowed to use Google's code.

iirc, google/uuid was marked unstable back when satori/go.uuid broke everything so I hesitated to move then.  There's nothing preventing me from referencing either as long as they're BSD-licensed.  We are using the Go standard library, after all.
I'll also have a look at gofrs.  It's probably the most straightforward option.  I think I want to keep the hacky uuid.go stuff because it's used in some contexts that are not really situated to handle errors.

To think of it... How about having a hook (register a function) that allows users to specify func() string that returns uuid ? This way everybody will use the one that is already used in the app. The mechanism could be similar to what sql package uses for registration
Why the heck uuid generation is not a part of standard library is beyond me...

So why was this closed without switching to https://github.com/gofrs/uuid? This is a forked but maintained repo unlike the satori repo

@adrianliechti


Exporting model as ONNX for inference using barracuda.

I wonder if once you are able to create the custom dataset pipeline, it would be an issue to try and deploy the resulting NGP into unity via barracuda. I presume exporting the model to ONNX and running it through barracuda wouldn't be much of an issue? I foresee using the a pipeline closely related to the Style Transfer One.

I use tinycudann, and am unsure that library supports onnx. You are free to try, but it's not in my plan currently