mac_address is being ignored in docker-compose files

Before you start please confirm the following.

[X] Yes, I've searched similar issues on GitHub.
[X] Yes, I've checked whether this issue is covered in the Portainer documentation or knowledge base.

Problem Description
This is the docker-compose used for setting the mac_address line. This used to work fine until recently. If I run this outside of Portainer with docker-compose up it generates the MAC address fine.
I am not using a swarm, which another user was having an issue with the same problem:
https://github.com/portainer/portainer/issues/9152
Does this have to do with the issue?
https://github.com/moby/moby/pull/46406
# Wyoming-OpenWakeWord Container for Docker
version: "3.9"
services:
  wyomingopenwakeword:
    container_name: "wyoming-openwakeword"
    image: "rhasspy/wyoming-openwakeword:latest"
    labels:
      - "com.centurylinklabs.watchtower.enable=true"
      - "com.centurylinklabs.watchtower.monitor-only=false"
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /var/lib/libvirt/images/usb001/docker-storage/wyoming-openwakeword/data:/data
    mac_address: "9e:de:ad:be:ef:01"
    hostname: "wyomingopenwakeword"
    networks:
      - dhcp
    ports:
      - 10400:10400
    devices:
      - /dev/snd:/dev/snd
    command: --model 'ok_nabu' --model 'hey_jarvis' --model 'hey_rhasspy' --model 'hey_mycroft' --model 'alexa' --preload-model 'ok_nabu'
    # --uri 'tcp://<IP_ADDRESS>:10400'
    restart: "no"
    #restart: unless-stopped
    #privileged: true
    #network_mode: host

networks:
  dhcp:
    name: "dbrv100"
    external: true

Network
IP Address
Gateway
MAC Address
Actions

dbrv100
<IP_ADDRESS>
<IP_ADDRESS>
16:a7:42:02:66:94
Leave network

Random generated MAC ================^
I use static set IP addresses by MAC dished out from DNSMasq DHCP so this breaks all the services for me as they just get random IP addresses instead of their statically defined ones.
Expected Behavior
Generate the mac_address specified.
Actual Behavior
Generates random MAC address.
Steps to Reproduce
Add a new stack, name your stack, dump the yaml above in the web editor, deploy the stack.
Portainer logs or screenshots
Client:
Version:           24.0.5
API version:       1.43
Go version:        go1.20.6
Git commit:        ced0996600
Built:             Wed Jul 26 21:44:58 2023
OS/Arch:           linux/amd64
Context:           default
Server:
Engine:
Version:          24.0.5
API version:      1.43 (minimum version 1.12)
Go version:       go1.20.6
Git commit:       a61e2b4c9c
Built:            Wed Jul 26 21:44:58 2023
OS/Arch:          linux/amd64
Experimental:     false
containerd:
Version:          v1.7.6
GitCommit:        091922f03c2762540fd057fba91260237ff86acb.m
runc:
Version:          1.1.9
GitCommit:
docker-init:
Version:          0.19.0
GitCommit:        de40ad0
Portainer version
2.19.1
Portainer Edition
Community Edition (CE)
Platform and Version
Docker 24.0.5 | docker-compose 2.20.3
OS and Architecture
Arch Linux 6.5.5-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 23 Sep 2023 22:55:13 +0000 x86_64 GNU/Linux
Browser
Chrome Version 117.0.5938.92 (Official Build) (64-bit)
What command did you use to deploy Portainer?
Pushed the "Deploy the stack" button on the WebUI.

Additional Information
I noticed the version of compose the containers say they used seem to be perpetually set to when they were first deployed:
com.docker.compose.version | 2.20.2
Maybe this is just a database entry as when you hit redeploy it doesn't update that field. As I have 2.20.3 of compose installed or does Portainer have it's own docker-compose resource i.e. not /usr/bin/docker-compose etc?
I believe docker-compose had an issue https://github.com/moby/moby/pull/46406 with setting mac_address in this version. It said it was fixed 3 weeks ago maybe that is something? Does docker-compose need to be updated in Portainer to take advantage of this fix or it should use the system /usr/bin/docker-compose etc?
Thank you.

https://github.com/docker/compose/issues/11041

I can also confirm I was impacted by this issue, when I was unable to restore my containers through the Portainer stack interface. When I had attempted to do so, they got randomly assigned, incrementing MAC addresses from Docker / Portainer.
Workaround

Remove the impacted containers from Portainer
Copy the yaml STACK file used to deploy said containers
Connect to machine directly, and perform a docker compose -f /path/to/portainer-stack.yaml up --detach
Observe Containers getting CORRECT mac adddresses

A sample compose file of two containers that was impacted by this:
version: '2'

networks:
  macvlan_net:
    external:
      name: macvlan-network
  web_portal_network:
    external:
      name: web_portal_network

services:
  plex:
    container_name: plex
    image: plexinc/pms-docker:latest
    restart: unless-stopped
    mac_address: 00:1D:84:00:50:20
    networks:
      macvlan_net:
        ipv4_address: <IP_ADDRESS>
    environment:
      - HOSTNAME=REMOVED_REMOVED_REMOVED
      - PLEX_CLAIM=REMOVED_REMOVED_REMOVED
      - ADVERTISE_IP=REMOVED_REMOVED_REMOVED
      - TZ=UTC
    volumes:
      - /path/to/data/data:/data
    devices:
     - /dev/dri:/dev/dri

  plex-private:
    container_name: plex-private
    image: plexinc/pms-docker:latest
    restart: unless-stopped
    mac_address: 00:1D:84:00:50:21
    networks:
      macvlan_net:
        ipv4_address: <IP_ADDRESS>
    environment:
      - HOSTNAME=REMOVED_REMOVED_REMOVED
      - PLEX_CLAIM=REMOVED_REMOVED_REMOVED
      - ADVERTISE_IP=REMOVED_REMOVED_REMOVED
      - TZ=UTC
    volumes:
      - /path/to/data/data:/data
    devices:
      - /dev/dri:/dev/dri

**This is a blocking issue for me with Portainer, I am unable to deploy containers using Mac VLAN anymore through portainer at this time.
Portainer Business Edition
Server Version: 2.19.1
Database Version: 2.19.1
CI Build Number: 34747
Image Tag: linux-amd64-2.19.1
Compilation tools:
Nodejs v18.18.0
Yarn v1.22.19
Webpack v5.88.1
Go v1.20.5

My workaround was to manually compile the latest moby on the system then it seemed to function again.

I am also seeing the same issue.  I ended up rolling back to 2.17.1 to restore functionality.   Seems it was introduced with 2.18.0
Rather run latest patches/versions. Please advice on an eta for the fix.

Still happening:
Server Version: 2.19.4
Database Version: 2.19.4
CI Build Number: 35427
Image Tag: linux-amd64-2.19.4

Compilation tools:
Nodejs v18.19.0
Yarn v1.22.21
Webpack v5.88.1
Go v1.20.5

I had this issue in a different context. I found the following and it led to the solution of my problem.

Note Container runtimes might reject this value (ie. Docker Engine >= v25.0). In that case, you should use networks.mac_address instead.

See here.
So I switched from
version: '3.8' # Example version
services:
  your_service:
    image: your_image
    mac_address: your_mac_address

to
version: '3.8' # Example version
services:
  your_service:
    image: your_image
    networks:
      default:
        mac_address: your_mac_address

Now, the mac address is correctly set in my container.

I wasn't able to get my portainer to use that change, it kept complaining about the YAML.

Key
Value

OS Information
linux x86_64 Ubuntu 22.04.3 LTS

Kernel Version
5.15.0-92-generic

Total CPU
8

Total memory
33.5 GB

Version
20.10.15 (API: 1.41)

Root directory
/var/lib/docker

Storage Driver
overlay2

Logging Driver
json-file

Volume Plugins
local

Network Plugins
bridge, host, ipvlan, macvlan, null, overlay

I had this issue in a different context. I found the following and it led to the solution of my problem.

Note Container runtimes might reject this value (ie. Docker Engine >= v25.0). In that case, you should use networks.mac_address instead.

See here.
So I switched from
version: '3.8' # Example version
services:
  your_service:
    image: your_image
    mac_address: your_mac_address

to
version: '3.8' # Example version
services:
  your_service:
    image: your_image
    networks:
      default:
        mac_address: your_mac_address

Now, the mac address is correctly set in my container.

Also unable to verify.  Did not work for me

Is there any other workaround? I've lost the ability to deploy stacks from my portainer with this bug.

Thanks for raising this, I am going to follow this up internally and test this. I will give updates here

@Nick-Portainer
Here is some version info for you:
╔═[purda@codex : ~]
╚═ $ docker version
Client: Docker Engine - Community
 Version:           20.10.15
 API version:       1.41
 Go version:        go1.17.9
 Git commit:        fd82621
 Built:             Thu May  5 13:19:18 2022
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.15
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.17.9
  Git commit:       4433bf6
  Built:            Thu May  5 13:17:24 2022
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.4
  GitCommit:        212e8b6fa2f44b9c21b2798135fc6fb7c53efc16
 runc:
  Version:          1.1.1
  GitCommit:        v1.1.1-0-g52de29d
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0
╔═[purda@codex : ~]
╚═ $

From portainer:
Engine Details
Version 	20.10.15 (API: 1.41)
Root directory 	/var/lib/docker
Storage Driver 	overlay2
Logging Driver 	json-file
Volume Plugins 	local
Network Plugins 	bridge, host, ipvlan, macvlan, null, overlay

Host Details
Hostname 	codex
OS Information 	linux x86_64 Ubuntu 22.04.4 LTS
Kernel Version 	5.15.0-92-generic
Total CPU 	8
Total memory 	33.5 GB

I used to be able to deploy and maintain all my stack within the portainer UI, but now they no longer accept the custom mac address and I must deploy the docker compose file manually from the CLI using docker itself, orphaning the containers within portainer.

[~] # docker version
Client:
Version:           20.10.27-qnap1
API version:       1.41
Go version:        go1.19.12
Git commit:        662936b
Built:             Mon Dec 25 08:41:44 2023
OS/Arch:           linux/amd64
Context:           default
Experimental:      true
Server: Docker Engine - Community
Engine:
Version:          20.10.27-qnap1
API version:      1.41 (minimum version 1.12)
Go version:       go1.20.10
Git commit:       8a4e2cd
Built:            Mon Dec 25 08:42:51 2023
OS/Arch:          linux/amd64
Experimental:     false
containerd:
Version:          v1.6.22
GitCommit:        8165feabfdfe38c65b599c4993d227328c231fca
runc:
Version:          1.1.8
GitCommit:        v1.1.8-0-g82f18fe0
docker-init:
Version:          0.19.0
GitCommit:        de40ad0

I tested this and it's an issue with an older version of Docker Compose, an updated version will be included in the 2.20 release which will resolve this issue.

I tested this and it's an issue with an older version of Docker Compose, an updated version will be included in the 2.20 release which will resolve this issue.

I'm eager to see the fix and try again in-place. Thank you for helping me escalate this issue.

Is there an ETA on the 2.20 release?

I can't give dates but we are now in code freeze, so it's close :)

Thanks just was wondering if it's the next release or if there will be more 2.19.* etc... before it happens.

Are you able to point to the fix in github can I manually compile it in some way?

Are you able to point to the fix in github I can't seem to find it. Can I manually build it in some way?

Hey, so you can try our dev image of 2.20 please keep in mind this it not live and is not suitable for production and should only be used for testing, please let me know how this goes for you.
Business Edition
https://hub.docker.com/r/portainerci/portainer-ee/tags
portainerci/portainer-ee:2.20
Community Edition
https://hub.docker.com/r/portainerci/portainer/tags
docker pull portainerci/portainer:2.20

When I tried to start a container in 2:20 I got Forbidden - CSRF token invalid.
I compiled moby again after breaking my setup by accidentally updating to stock dockerd from packages. seems broken again for macs so it is giving the portainer a random mac address so it's not currenlty using It's static IP so the browser cache is fresh for that IP it is on now. I saw an issue about it and they said to clear cache to fix it. This doesn't seem like that would work for this CSRF Token issue.

When I tried to start a container in 2.20 I got Forbidden - CSRF token invalid.
I compiled moby again after breaking my setup by accidentally updating to stock dockerd from packages.
Seems like moby compose is broken just like stock dockerd for the mac_address setting.
It is giving the portainer a random mac address so it's not currenlty using it's static IP which the broswer would have cache for.
The browser cache is fresh for that IP it is on now. I saw an issue about it from 2016 and they said to clear cache to fix it. This doesn't seem like that would work for this CSRF Token issue. I looked under settings to see if there was a simple "Disable csrf token" but no luck there.
I tried to also redeploy the compose and got the same error.

Just trying to unravel your comment. So the issue you are facing is specifc to your compose? I tested the macvlan specifally in 2.20 and confirmed that worked.
I tested the below in 2.19.4 and confirmed it failed, but in 2.20 deployed fine.
version: '3.8'
services:
  nginx:
    image: nginx:latest
    networks:
      default:
        mac_address: xx:xx:xx:xx:xx:xx

Sorry, There are two things here Portainer's container MAC Address (which is a dockerd issue not yours) and the portainer containers MAC Address that portainer deploys as I also set the mac_address of my portainer container which it gets the IP address from a dnsmasq server via the static mac address like this:
dnsmasq.conf
# Portainer Docker Container
dhcp-host=de:ad:be:ef:00:01,<IP_ADDRESS>

Dockerd currently seemingly also has this issue with mac_address I worked around it way above many months ago by switching to a moby dockerd build which somehow fixed the issue for portainer as well...
A few days ago after doing a system update. I had a version mismatch error that said I was trying to use a docker client of version 1.13.1 and it needed to be at least 1.24 for docker to start any containers. The issue was with a plugin I was using called docker-net-dhcp which lets me use dnsmasq to pass the IP's off to dockerd
Me not remembering I manually updated dockerd with the moby version, overwrote it with the system package version and then after fixing the plugin version issue the mac address issue was back as well. 😢
So I then tried to rebuild the dockerd moby version to see if it would fix it again, but it seems it also has this issue now as well. When I ran my compose directly not through portainer it still wouldn't give it a static mac address being on the latest version of dockerd v25. they now changed where you place the mac_address line to under the network servicer where it used to be in the container service before v25:
https://docs.docker.com/compose/compose-file/05-services/#mac_address-1
mac_address
Available with Docker Compose version 2.24.0 and later.

mac_address sets a MAC address for the service container.

Note Container runtimes might reject this value (ie. Docker Engine >= v25.0). In that case, you should use networks.mac_address instead.

docker version
Client:
 Version:           25.0.2
 API version:       1.44
 Go version:        go1.21.6
 Git commit:        29cf629222
 Built:             Thu Feb  1 10:50:44 2024
 OS/Arch:           linux/amd64
 Context:           default

Server:
 Engine:
  Version:          dev
  API version:      1.45 (minimum version 1.24)
  Go version:       go1.21.7
  Git commit:       HEAD
  Built:            Wed Feb 28 00:02:42 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.7.13
  GitCommit:        7c3aca7a610df76212171d200ca3811ff6096eb8.m
 runc:
  Version:          1.1.12
  GitCommit:
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

When I try placing mac_address under the docker service it processes it but it just gives it a random mac like it wasn't there.  When I place it under the network service it won't start with the error shown in the comment at the end of the config below:
# Portainer Container for Docker
version: '3.9'

services:
  portainer:
    container_name: portainer
    hostname: portainer
    #image: portainer/portainer-ce:latest
    image: portainerci/portainer:2.20
    restart: 'no'
    labels:
      - "com.centurylinklabs.watchtower.enable=true"
    #restart: unless-stopped
    security_opt:
      - no-new-privileges:true
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - /var/lib/libvirt/images/sas/docker-storage/portainer/portainer-data:/data
    ports:
      - "8000:8000"
      - "9443:9443"
    mac_address: de:ad:be:ef:00:01
    networks:
      - dhcp
networks:
  dhcp:
    name: dbrv700
    external: true
    #mac_address: de:ad:be:ef:00:01 #ERROR: networks.dhcp Additional property mac_address is not allowed

So I just left it with the random MAC and checked the dnsmasq leases and saw the new IP for portainer was dhcp'd to a random IP address so I connected to that.
It was supposed to be .42 but it was .190 as dockerd gave it a random MAC instead of the one that was set in the compose file.
I connected to the new IP and was met with 2.20 as it said in the corner Community Edition 2.20.0
When I add this to the stack editor in portainer 2.20
Name: testmac
version: '3.8'
services:
  nginx:
    image: nginx:latest
    networks:
      default:
        mac_address: de:ad:be:ef:00:02

I get a notification:
Error  Deployment error Unable to deploy stack
If I try to start one of my other existing containers I get the Forbidden - CSRF token invalid.

I tested your yaml outside of portainer and it does indeed set the MAC address properly. So it must be an issue with using external network ie external: true

Figured out the syntax I had was just wrong should have been like this:
version: '3.8'
services:
  nginx:
    image: nginx:latest
    networks:
      dhcp:
        mac_address: de:ad:be:ef:00:01
networks:
  dhcp:
    name: dbrv100
    external: true

Looks like it is working now yay!
            "Networks": {
                "dbrv100": {
                    "IPAMConfig": {},
                    "Links": null,
                    "Aliases": [
                        "mactest-nginx-1",
                        "nginx",
                        "############"
                    ],
                    "MacAddress": "de:ad:be:ef:00:01",
                    "NetworkID": "0b...",
                    "EndpointID": "75...",
                    "Gateway": "<IP_ADDRESS>",
                    "IPAddress": "<IP_ADDRESS>",
                    "IPPrefixLen": 24,
                    "IPv6Gateway": "",
                    "GlobalIPv6Address": "",
                    "GlobalIPv6PrefixLen": 0,
                    "DriverOpts": null,
                    "DNSNames": [
                        "mactest-nginx-1",
                        "nginx",
                        "############"
                    ]
                }
            }

Great, thanks for testing that and providing feedback that it's now working. Please remember 2.20 is not currently released and the version I provided is just for testing :)

Great, thanks for testing that and providing feedback that it's now working. Please remember 2.20 is not currently released and the version I provided is just for testing :)

Don’t worry, I’m ready to test the production change

seems to still have a problem maybe regression in dockerd 25.0.3

I had a few machines getting random MAC's but after redeploying their stacks it fixed them up.

Case anyone has watchtower running I think they use an older version of docker-compose as well. After I redeployed, it was fine but then again today I had a bunch of updates from watchtower, and like clockwork, all those containers have bad MAC addresses. Redeploy from the modified v25 portainer and they get their proper static MACs back.

Is there an estimated release date* for 2.20 @Nick-Portainer ?

No offical date I can provide, but the team is very close :)

If 2.20 is not to be the LTS, what will be the LTS version @Nick-Portainer  ?

Any updates on the 2.21 release @Nick-Portainer ? I've been unable to re-deploy any macvlan stacks still since I'm waiting on the longer term support.

Any updates on the 2.21 release @Nick-Portainer ? I've been unable to re-deploy any macvlan stacks still since I'm waiting on the longer term support.

Within July at this stage

Any updates on the 2.21 release @Nick-Portainer ? I've been unable to re-deploy any macvlan stacks still since I'm waiting on the longer term support.

Within July at this stage

Cool I'll keep tracking this issue, I'm eager to be able to use my YAML and stacks inside portainer again, instead of the "glass break" solution of going out of portainer.

@Nick-Portainer Was this supposed to be fixed in 2.21.0 that was released? Because my server docker compose respects the MAC address i specify in compose file, but 2.21.0 portainer does not still.

@Nick-Portainer is this still being looked at? When I deploy a stack mac_address is still being ignored. I've updated to the latest version.

@tsmanz What version are you on? Can you also provide an example of your stack deployment

@Nick-Portainer Was this supposed to be fixed in 2.21.0 that was released? Because my server docker compose respects the MAC address i specify in compose file, but 2.21.0 portainer does not still.

@urda Can you confirm you Docker version please

@Nick-Portainer I moved away from using mac_address with portainer at this time, but it might have been:
$ docker --version
Docker version 27.3.1, build ce12230

@tsmanz Could you please confirm the exact version you are using? Also, let me know the Docker version you have installed. Ensure that you are running Docker version 25.0.0 or later.

I have a QNAP NAS with docker & portainer deployed via docker compose.
QTS <IP_ADDRESS>30

docker --version
Docker version 27.1.2-qnap4, build d46fd47

Portainer
Server Version: 2.21.4
Database Version: 2.21.4
CI Build Number: 121
Image Tag: linux-amd64-2.21.4
Git Commit: f54e985

And confirming @tsmanz on that version of Docker you are still facing the mac_address being ignored?

@tsmanz Could you please confirm the exact version you are using? Also, let me know the Docker version you have installed. Ensure that you are running Docker version 25.0.0 or later.

I have a QNAP NAS with docker & portainer deployed via docker compose.
QTS <IP_ADDRESS>30

docker --version
Docker version 27.1.2-qnap4, build d46fd47

Portainer
Server Version: 2.21.4
Database Version: 2.21.4
CI Build Number: 121
Image Tag: linux-amd64-2.21.4
Git Commit: f54e985

And confirming @tsmanz on that version of Docker you are still facing the mac_address being ignored?

Yes confirming mac_address it's still being ignored. I get a new mac every time I have to update containers which causes issues. It used to work quite a while ago but I don't recall the version number it was on when it did.

@Nick-Portainer is this still being looked at or is it a lost cause? If it's not going to be fixed, I'll move away from using portainer as it's a deal breaker for my environment.

What does your stack yaml look like?

I have the same issue that was never resolved.   Stack is quoted above
https://github.com/portainer/portainer/issues/10393#issuecomment-1874341234

You have the mac_address under the wrong section in the YAML please review my comment here https://github.com/portainer/portainer/issues/10393#issuecomment-1969913759

Looks promising, let me update and test against the latest.
Thanks,
Bill B.
On Fri, Dec 20, 2024 at 9:12 PM NonaSuomy @.***> wrote:

You have the mac_address under the wrong section in the YAML please review
my comment here #10393 (comment)
https://github.com/portainer/portainer/issues/10393#issuecomment-1969913759
—
Reply to this email directly, view it on GitHub
https://github.com/portainer/portainer/issues/10393#issuecomment-2557987471,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACC33KNRHJJJL7PPPSUNYUT2GTTEDAVCNFSM6AAAAAA5LDVPQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJXHE4DONBXGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Link to the updated Docs:
https://docs.docker.com/reference/compose-file/services/#mac_address

The documentation is poorly explained. So I understand why people would not figure it out 😄
Which states it's available 2.24.0 and later in the service container. Then they add a random note at the bottom to confuse you more. With no example and expects you to know that networks.mac_address means to put it under the networks section.
When I was talking with the docker devs the said they forgot to add any regression with it and that it was supposed to still work in the main service but it never did and never fixed it.
Original Documentation:
[mac_address](https://docs.docker.com/reference/compose-file/services/#mac_address)
Available with Docker Compose version 2.24.0 and later.

mac_address sets a MAC address for the service container.

Note

Container runtimes might reject this value (ie. Docker Engine >= v25.0). In that case, you should use [networks.mac_address](https://docs.docker.com/reference/compose-file/services/#mac_address) instead.

Testing Successful

Updated from ce:2.17.1 (last version that supported old schema) to Community Edition 2.21.5. (portainer/portainer-ce:latest)
Updated all Custom Templates per docker documentation.
Relaunched all stacks
Verified in Portainer and pfSense IP/Hostname assignment still successful.

Example Update:
services:
  watchtower:
    image: containrrr/watchtower:latest
    container_name: watchtower-vm
    hostname: watchtower-vm
    dns:
      - <IP_ADDRESS>
    environment:
      - DOCKER_CONFIG:/config
      - WATCHTOWER_SCHEDULE=0 0 4 * * *
      - WATCHTOWER_CLEANUP=true
      - WATCHTOWER_INCLUDE_RESTARTING=true
      - WATCHTOWER_INCLUDE_STOPPED=true
      - WATCHTOWER_DEBUG=false
      - WATCHTOWER_NOTIFICATIONS=email
      -<EMAIL_ADDRESS>      -<EMAIL_ADDRESS>      - WATCHTOWER_NOTIFICATION_EMAIL_SERVER=smtp-vm.evilminions.org
      - WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PORT=25
      - WATCHTOWER_NOTIFICATION_EMAIL_DELAY=2
      - TZ=America/Phoenix
    restart: unless-stopped
    networks:
      eth3:
        mac_address: da:de:40:30:22:ae
    volumes:
      - json-config:/config
      - type: bind
        source: /var/run/docker.sock
        target: /var/run/docker.sock

volumes:
  json-config:
    name: docker-config
    external: true

networks:
  eth3:
    name: qnet-dhcp-eth3-6d6da6
    external: true```

Just so you know, I see you use Watchtower there... which doesn't support the new mac_address under networks yet and since their repo has gone pretty dormant not sure if we will expect a fix for it.
If you use watchtower just for notifications it won't affect you, but if you use it to pull docker images... every time it does your docker will lose the mac address. If you then repull it with portainer it will fix it again.
I have a ticket with them as well for this issue. https://github.com/containrrr/watchtower/issues/1941


A "simple" eager loading approach (for has_one relations)

Affected Version
5
Description
I've been checking how the eager loading (https://github.com/silverstripe/silverstripe-framework/pull/10783) is coming along and I'm wondering if an alternative, simpler approach might be sometimes more interesting using simple joins.
For example, in one of my app, I have this very typical usage : I have a list of companies with their admin member. So, very often, in a gridfield or a table, I have a loop where I display the admin name/email. This currently leads to n+1 problem.
I've recently thought about a simple solution to this, inspired by how many_many extra fields are loaded. My solution works like so
 public function CompaniesWithAdmin()
    {
        $list = $this->Companies()->leftJoin('Member', 'Member.ID = Company.AdminID');
        $list = $list->alterDataQuery(function (SilverStripe\ORM\DataQuery $dataQuery, $list) {
            return $dataQuery->addSelectFromTable('Member', ['FirstName', 'Surname', 'Email', 'Mobile']);
        });
        return $list;
    }

With this, you get the list of companies, with the extra fields, and the 4 fields from member, which is great when I don't need a fully fledged "member" object. But the syntax is very verbose, and it's basically something that is not documented anywhere so I don't think many people will think to do so, even though it's very likely the most performant approach (for example, in my table, it's removing 100 queries). Also, a minor issue, i don't think you can add aliases using addSelectFromTable but that could be easily fixed by improving how the expressions are built.
Proposal
Add an inject method that does exactly that that would have the following signature in relation list
inject($relation, $fields)
Fix the addSelectFromTable so that it can support aliases and the inject method would prefix the fields with the name of the relation (Member_FirstName...) to avoid collision
This is meant to a be simpler alternative to something like https://github.com/gurucomkz/silverstripe-eagerloading/tree/master

If you want to play with it, here is a generic version that can be used in any project. Example usage: DatabaseHelper::inject($this->Companies(), 'Admin', ['FirstName', 'Surname', 'Email', 'Mobile']);
https://github.com/lekoala/silverstripe-base/blob/8f1cfbf4aa636791b3aafe2bd68078a2e2ba0b6c/src/Helpers/DatabaseHelper.php#L301C6-L357

Validating my understanding of this suggestion
I'm guessing in your template you would then change from something like this:
<% for $CompaniesWithAdmin %>
  Contact $Admin.Name on $Admin.Mobile or $Admin.Email
<% end_for %>

to something like this:
<% for $CompaniesWithAdmin %>
  Contact $Admin_FirstName $Admin_SurName on $Admin_Mobile or $Admin_Email
<% end_for %>

Ideally this would also use the correct DBField subclass for casting etc, which shouldn't be too hard to figure out. It would obviously require that you are okay with skipping getter methods but that's just a matter of clearly documenting what the limitations are of this approach.
Request for more information
I can see what the use case for this might be - but I can't see that it's necessarily a significant improvement over the implementation of eager loading which will be released with silverstripe/framework 5.1.0.
I would be hesitant to introduce what is essentially a second eager loading API which has potentially more limitations than the current one unless you can demonstrate that it is clearly, significantly, quantifiably, and repeatably more performant than the current implementation - or has some other clear benefit beyond performance that I'm not currently seeing.

Yes indeed, in the templates or in the gridfield display fields, you have to use Admin_FirstName instead of Admin.FirstName. I'm not sure about casting to be honest, I guess at the moment it's using the default casting ? That's probably something that needs to be handled in the createDataObject method.
While the upcoming eager loading api will cover my use case (preventing the n+1), it will have two downsides:

it will make another query with a IN (...) on the the member table. Potentially a large one.
it will initiate a full member object when you probably need only a handful of fields

There is no benefit to my approach other than performance.
Maybe this could just live in a custom module and not be part of the framework for those who need this specific kind of optimization. I thought it might make sense to add it as a convenience method for the framework, since my approach is currently possible with the framework: it's just that the syntax is very impractical without a helper method.

Maybe this could just live in a custom module and not be part of the framework for those who need this specific kind of optimization.

Given there's no clear indication of what the quantifiable performance benefit would be, I'm inclined to agree that this is something for a module, rather than a core feature. I'll close this issue given there's a way forward for this to be I olemented as a module, and no clear need or benefit to having it in core.


Add feature to seek the waveform when tapped?

Hi, can you please add feature to seek the waveform to position/duration when tapped?

+1


Download translation?

I've installed the plugin as instructions directed. When I do CMD-P "My Bible: Download translation" it

Asks if I want to download the entire ESV translation

When I click Download it:

Started download of the ESV translation

Then almost immediately says:

Completed download of the ESV translation

But I see no indication of the presence of the translation in /Bible or anywhere else in my vault.
Nor does it populate a verse when I "read" it with "[[Genesis 1#1]]" instead it merely displays the location in /Bible/01 Genesis/Genesis 1
What am I missing?

When you have a built Bible in your vault, the verses displayed in the bible are fetched from the internet. Downloading the Bible means you have a local copy that can be accessed without an internet connection.
You can verify if the translation has been downloaded by opening your vault in the OS's file explorer, and navigating to .obsidian/plugins/gslogimaker-my-bible/.mybiblecache, and you should see a lot of text files containing the text of your translation.
If you don't have the Bible built in your vault then you can run the Build Bible command with CMD-P "My Bible: Build bible", and that will build your Bible in the path specified in your My Bible settings.

Hope this helps!

Thanks. The picture you show here of the Bible folder as "Bible" with an emoticon is different than the default "/Bible/". With the default, you get the skeleton, but the My Bible: Download translation doesn't work.
With "Bible" it does. I now have 4BM of files in .obsidian/plugins/gslogimaker-my-bible

They look like this:

Question: how do I get them to appear?
Typing [[Genesis 1#1]] , which in Reading mode, looks like Genesis 1>1 opens Bible/01 Genesis/Genesis 1 and gives me a highlight, but empty location here:

I see the issue. Looks like My Bible is using an incorrect default for one of the settings.
Change the Verse body format setting to
###### {verse}
{verse_text}

and run Build bible again. That should fix the problem.

Success! Thanks.


[Dynamic Regions] qps drop to zero after inject one tikv io hang

Bug Report

What version of TiKV are you using?
./tikv-server -V
TiKV
Release Version:   6.7.0-alpha
Edition:           Community
Git Commit Hash:   fc9cf096b3eddc48e2f1df09dd6d716198067410
Git Commit Branch: heads/refs/tags/v6.7.0-alpha
UTC Build Time:    2023-03-10 11:42:08
Rust Version:      rustc 1.67.0-nightly (96ddd32c4 2022-11-14)
Enable Features:   pprof-fp jemalloc mem-profiling portable sse test-engine-kv-rocksdb test-engine-raft-raft-engine cloud-aws cloud-gcp cloud-azure
Profile:           dist_release
2023-03-10T20:30:27.276Z	INFO	k8s/client.go:1
What operating system and CPU are you using?
8c/32g
Steps to reproduce
inject one tikv io hang
https://tcms.pingcap.net/dashboard/executions/plan/1682105
clinic: https://clinic.pingcap.com.cn/portal/#/orgs/31/clusters/7208935321555813749?from=1678480214&to=1678483863
logs: http://minio.pingcap.net:38888/buckets/test-infra-testground/browse/YXJjaGl2ZS9lbmRsZXNzLWhhLXRlc3QtbXVsdGktcm9ja3MtdHBzLTE2ODIxMDUtMS03OTQ=
What did you expect?
qps can recover within 5min
What did happened?
qps drop to zero after inject one tikv io hang

/type bug
/severity major
/assign tonyxuqqi

/remove-severity major
/type bug
/severity critical

Dup with https://github.com/tikv/tikv/issues/14532.

The fix is https://github.com/tikv/tikv/issues/14532
It's because the the other two pears cannot elect a new leader.


Can OFA perform fast retrieval task as dual-stream-like models?

Hi there:
Can OFA perform fast retrieval task as dual-stream-like models? Since I want to get embedding for the image or text, and use the saved embedding for fast retrieval by calculating cosine similarity. Instead of input every pair of text and image.
How you can give me any hint!
Thanks a lot!

@JacobKong Hi, I think you can use the hidden states of <BOS> on the encoder side, or the hidden states of <EOS> on the decoder side for retrieval. However, since the pre-training tasks of OFA do not contain contrastive loss,
it is necessary to fine-tune OFA using contrastive loss before applying it to the retrieval task.

Thanks a lot for the reply! So should I input single image or should I input both the image and a instruction text to the encoder to get the final image embedding?

@JacobKong I recommend input both the image and a instruction text.

@JacobKong And I think it's better to reuse the instruction " what does the image describe? "

Thanks! I'll try it.
What about text embedding? What's the best instruction to input for extracting  text embedding?

@JacobKong I'm not sure... you may need to try it yourself.


add a checker to confirm optimizer can keep plan schema immutable.

Which issue does this PR close?

Closes #.
Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

Thanks @jackwener. This is a good improvement. Could you fill out the PR description? It helps with the reviews.

Thanks @andygrove review.
polish error message to  add the expected and actual schema, and add a UT.

This is really nice!

I think we also need to do the same check for physical optimizer.

I think we also need to do the same check for physical optimizer.

Sounds like a good idea. Do you want to file an issue for that?


local_position freeze with updated VICON pose using LPE

I am using the most updated master Firmware, and tried to control the UAV indoor with VICON system. The VICON data sent through WiFi to Odroid and forwarded to PX4 by /mavros/mocap/pose or /mavros/vision_pose/pose. But the local_position/local updated around (0, 0, 0) even though the vision estimated data was updating correctly, monitoring from QGC, when we were moving the UAV randomly.
According to issue #5945 , it seems that the LPE has worked fine with VICON system. But we got the large errrors between the local_pose/pose with /mavros/vision_pose/pose.  Also, according to issue #5102, there should be some LPE related paramters, such as
x   LPE_INTEGRATE [69,155] : 1
x   LPE_FLW_OFF_Z [70,156] : 0.0000
x   LPE_FLW_XY [71,157] : 0.0100
x   LPE_FLW_QMIN [72,158] : 75
x   LPE_SNR_Z [73,159] : 0.0500
...

we could not find those parameters in QGC.
Questions:

How should we set the parameters correctly to enable LPE working with VICON or there are no more parameters for us to configure LPE?
For /mavros/mocap/pose or /mavros/vision_pose/pose, which is the best choice to send the VICION data to PX4.

Configurations about my testing platform:
PX4

Current Master branch
Default LPE

Odroid XU4

Telem2 with UART 921600
Lubuntu 14.04
ROS Jade
Current MAVROS Branch

Ground Staion

Connect with Odroid XU4 using WiFi
Ubuntu 14.04
ROS Jade
ETH Vicion Bridge

LPE is only supported on px4fmu-v3_default and px4fmu-v4_default build targets. If you try load it with the Pixhawk default target px4fmu-v2_default you need to enable it cmake/px4fmu-v2_default config.

@LorenzMeier Thanks with the quick reply. I tested the LPE with px4fmu-v2_default version, and sent the VICON data to mocap/pose, following are the results
http://logs.uaventure.com/view/HU5iw2K7nyTHCaYbf4sKsk
It seems that the position control is not quite stable(see pictures of local position), when the set position for XY was fixed and we controlled the Z axis through the keyboard.
I already disable the GPS and Vision in LPE parameters and set PN_V=0.8.  Is this related to local position control PID parameters?  Would it be possible to share more experiences?

@weiweikong Your acceleration noise seems to be very high. I get quite good LPE results using vision, if the acceleration noise is below 0.1g in all axes.

You can maybe disable accel integration if the accel measurements are bad. It's a define somewhere in LPE.

@ecmnet Should I send VICION data to vision_pose/pose? As you mentioned vision, do you mean the optical flow sensor?

@mhkabir Do you mean the LPE_ACC_XY and LPE_ACC_Z parameters?

@ecmnet You are right that my PX4 was broken which caused the vibration in Z axis. I changed a new one, however, there is still an overshoot in axises, especially in  Z-axis

As the figure shown, after the overshoot, the UAV could fix near the setting position and the whole log file is http://logs.uaventure.com/view/jHMvjd93pZWM7XMFizwcbG.
My VICION coordinate is ENU.

@ecmnet
Hello!
Do you mean accelerate noise density? And I wonder what kind of coordinate system the vision should be? Is it ENU or what?
Thank you!

@zzzzzq Vision is not optical Flow, but vision based position and attitude estimation. I've played around with LPE_ACC_XY and LPE_ACC_Z a bit to get proper results, but acceleration noise was one of the driving factors when it comes to accuracy.


✨ Add "Dark Mode" and "Light Mode" Toggle Functionality

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
@MAVRICK-1 and @sanket95droid
The website currently only supports a single theme (light or dark).
Implementing a dark mode and light mode toggle feature would significantly enhance user experience by allowing users to switch between light and dark themes based on their preference or lighting conditions.
Use Case

A user wants to switch to a different theme (dark mode or light mode).
User Navigates to the website.
User Clicks on the dark mode/light mode toggle button.
System Switches the website's theme to the selected mode (dark or light).

Benefits

To improve user experience and accessibility,
This feature allows users to switch between light and dark themes,
Better readability and comfort in different lighting environments

Could You please assign this issue to me??
Priority
Medium
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

have assigned you the issue, looking forward to it @MastanSayyad


Use ecma-collection in JSON.

The simple list data structure has replaced with ecma-collection in the JSON object.

I've updated the pull request.

Looks good to me

lgtm

LGTM

I think we should close this issue.


Remove jQuery dependency

The game interacts with the DOM in very few ways, and native JavaScript is far more capable than it was when the game was first created.  So, replace all jQuery code with native JavaScript code (or, on occasion, an alternative library for operations such as deep cloning).
Bear in mind that there are plugins that depend upon jQuery, so replacing them will also be necessary.

"Bear in mind that there are plugins that depend upon jQuery, so replacing them will also be necessary."
FYI, the jQuery plugins were removed with my referenced commit.


"Contact Us" Button Not Working - Need to Implement Contact Page

Issue Description:
The "Contact Us" button in the navigation menu is currently non-functional and does not redirect to any page. We need to create a new "Contact Us" page where users can either fill out a form (name, email, message) or find contact information. Once the page is created, the button should be linked to it, ensuring proper navigation. Additionally, make sure the page design is consistent with the rest of the website.
sceenshot:

@SaurabhS55 please label the issuse

@SaurabhS55 please asign it to me

@TornovDutta this issue is assigned to someone already. #115
if he is unable to do it then I will assign this issue to you

Ok


CodeSwing won't run when it's the only extension enabled.

problem:
I disabled all extensions, then enabled CodeSwing. Then reloaded VS Code. However I cannot run any swings. (see below)

Why? - I was trying to test to see if Svelte apps work without any of my extension favorites.

This is a duplicate of https://github.com/codespaces-contrib/codeswing/issues/4. The issue isn't that CodeSwing depends on other extensions, it's that the preview window isn't re-opened when you reload VS Code. If you run the CodeSwing: Open Swing command, and then select your swing directory, it will re-launch the environment 👍
So I'll go ahead and close this and we can track that discussion in #4.


Breaks docusaurus-plugin-typedoc

I have no idea if this is something you can fix or even care about, but here goes.
I'm using Docusaurus for a documentation site.
This site uses docusaurus-plugin-typedoc to generate API docs, which uses typedoc-plugin-markdown.
I configured Typedoc to use this plugin.
Recently, I migrated from Docusaurus v2 to v3, but this change had this weird side effect where the API docs would still get generated but Docusaurus wouldn't detect them until a rebuild is triggered by changing some file.
When I removed this plugin, the issue disappeared.
I tried using other plugins (and disabling all plugins) and the issue seems to be related to this plugin specifically.
Oh and before I forget: thanks a lot for making this plugin!

Hm... That's weird.

Any chance you can build a minimal repository where I can reproduce the issue?

Sure, you can find it here.

Thanks a lot. I can reproduce the issue indeed. I don't have any good ideas to debug this problem however, so I'm just trying some generic things.
For example, you mentioned this issue happened after upgrading docusaurus from v2 to v3. However, I tried downgrading docusaurus in your repro (including everything it carries like react and so), but I can still reproduce the issue with docusaurus v2 in your repro repo.
Have you upgraded something else in between? I'm trying to identify what upgrade exactly caused this problem.

Strange... I'll take a look at the previous build artifacts and commit history and see if I can find anything.

I checked before and after the commit where I migrated to v3 and after the migration the problem appeared.
Are you sure you downgraded everything?
Here's a full list of dependencies changed with the upgrade:

Package
Old Version
New Version

@docusaurus/core
^2.4.3
^3.0.0

@docusaurus/preset-classic
^2.4.3
^3.0.0

@docusaurus/remark-plugin-npm2yarn
^2.4.3
^3.0.0

@mdx-js/react
^1.6.22
^3.0.0

clsx
^1.2.1
^1.2.1

docusaurus-plugin-typedoc
^0.20.1
^0.21.0

prism-react-renderer
^1.3.5
^2.3.0

react
^17.0.2
^18.2.0

react-dom
^17.0.2
^18.2.0

remark-docusaurus-tabs
^0.2.0
Removed

rimraf
^5.0.1
^5.0.5

typedoc
^0.25.1
^0.25.3

typedoc-plugin-markdown
^3.16.0
^3.17.1

typedoc-plugin-rename-defaults
^0.6.6
^0.7.0

Dev Package
Old Version
New Version

@docusaurus/module-type-aliases
^2.4.3
^3.0.0

@docusaurus/tsconfig
Added
^3.0.0

@docusaurus/types
Added
^3.0.0

@types/react
Added
^18.2.38

typescript
Added
^5.2.2

I'll try messing around a bit with the dependencies to see if anything else could be the cause.

Yes, here's how I downgraded:

https://github.com/NanderTGA/typedoc-plugin-rename-default-repro/pull/1

And I can still reproduce the issue just fine.

Ok, I think I figured it out. The upgrade of typedoc-plugin-rename-defaults from 0.6.6 to 0.7.0 triggers the issue.
I can no longer reproduce the issue after downgrading it to 0.6.6.
I will investigate.

For me the issue appeared after upgrading from 0.6.6 to 0.6.7.

Actually, specifically when upgrading from 0.6.6 to 0.6.7.

Ok, I was able to isolate the issue. What triggered this problem was the migration from commonjs to esm.
I cannot reproduce the issue with:

https://github.com/felipecrs/typedoc-plugin-rename-defaults/pull/18

@Gerrit0, do you have any idea about why this happens? Maybe when the plugin is esm, typedoc loads it asynchronously while when it's commonjs it loads it more synchronously.

Some notes:

Maybe typedoc loads plugins in a different order, for example commonjs ones first and esm ones after.
I see that typedoc-plugin-markdown is still commonjs. Maybe upgrading it to esm would help as well.

The cause of this is probably that the docusaurus plugin inappropriately handles promises. It sounds like it doesn't await something important, so it happens to work on the second import because it's cached

The docs still seem to be generated the first time, the problem is that Docusaurus doesn't see the generated files for some reason.
I opened an issue on the plugin's repo.

https://github.com/tgreyuk/typedoc-plugin-markdown/issues/530#issuecomment-1867090958


132 followup

Addresses all comments from #132 (almost all, https://github.com/interchainio/tendermint-rs/pull/132#discussion_r373813746 still needs to be addressed; will be addressed shortly too)

[ ] Referenced an issue explaining the need for the change
[ ] Updated all relevant documentation in docs
[ ] Updated all code comments where relevant
[ ] Wrote tests
[ ] Updated CHANGES.md

Codecov Report

Merging #141 into master will decrease coverage by 0.02%.
The diff coverage is 75.6%.

@@            Coverage Diff             @@
##           master     #141      +/-   ##
==========================================
- Coverage    36.9%   36.88%   -0.03%
==========================================
  Files          90       90
  Lines        3127     3137      +10
  Branches      463      470       +7
==========================================
+ Hits         1154     1157       +3
- Misses       1718     1719       +1
- Partials      255      261       +6

Impacted Files
Coverage Δ

tendermint/src/lite/verifier.rs
79.23% <100%> (-0.44%)
:arrow_down:

tendermint/src/lite/types.rs
57.71% <47.36%> (-0.42%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d0e99f9...9750575. Read the comment docs.

Thanks a lot for the quick review! I'll merge this as is and will address dealing with the 1/3 bound and https://github.com/interchainio/tendermint-rs/pull/132#discussion_r373813746 in a small separate PR .


fix: bundle with mdi fonts instead of loading from external server

Resolves #453

@akloeckner

Nice! :-) I have no clue as to the correctness of that code, however...

Can be proof-checked by just looking at the generated output in build/styles/styles.css. :)


footer section

Describe the bug
modifying/making changes to the 'en_US.yaml' file. doe not update the footer section.
  footer:
    build_on: >-
      Built on <1> Answer </1>- the open-source software that powers Q&A
      communities.
Made with love © {{cc}}.

answer > i18n > en_US.yaml > line 585
To Reproduce
Steps to reproduce the behavior:

Go to 'answer > 118n > en_US.yaml > line 585'
modify footer text 'line 585'

  footer:
    build_on: >-
      Built on <1> Answer </1>- the open-source software that powers Q&A
      communities.
Made with love © {{cc}}.

Save file.

Expected behavior
changes made to the file update footer section on all pages.

For production environment，after the modification is complete, have you re-packaged and deployed?
For development environment, if you changed this file, you should be able to see the modified copy directly!

If neither of the above two is true, please continue to give feedback

In productions/dev
log show-
[i18n] install en_US.yaml bundle success
[i18n] install es_ES.yaml file exist, try to replace it
[i18n] install es_ES.yaml bundle...
[i18n] install es_ES.yaml bundle success

Did you recompile after editing？After you edit the language file, first you should compile it, then use docker build to package the image, and finally start the above packaged image.


Crashes when picking a catwalk block.

Dear thecodewarrior,
Thanks for the mod, it is a really great alternative to vanilla fences and stairs :+1: I just found your mod on curse.com and I threw it in my mod folder and gave it a spin. I placed one Catwalk and added a Rope Light to it. When I wanted to pick it back up with my diamond pickaxe the game crashed on me, so here is the log: http://pastebin.com/q9A56bUG

Thanks, I haven't had this problem, but I think I know what it is. Is it reproducible? Does it happen every time? If it does, see if this fixes it. https://a.uguu.se/kakfhw_Catwalks-0.1.0-particleCrashFix.jar

It is reproducable and I am sorry, but it even crashes when I replace the .jar with the particleCrashFix one. :(

I was just looking at your build.gradle and saw that you are using the recommended forge release 1.8.9 - <IP_ADDRESS>2 and I am playing with 1.8.9 - <IP_ADDRESS>8. Maybe that's a issue with 1808?

Nope, here's a build so it'll yell if something tries to get the particle texture of the smart model instead of the actual model. If that's the problem we should find out who to yell at. :)
https://a.uguu.se/tgqlur_catwalks-0.1.0-nowitllyell.jar

Here you go: http://pastebin.com/GVWd2NxV :grin: According to the stacktrace we are going to yell hat Mojang?

Sorry, I forgot to let you know that I made it so it returns the missing texture instead of null. That should definitely work.
It'll be in the next version. I should be able to get it out within a week if all goes to plan, if it isn't out by then I'll release a beta without proper textures.

Take your time, mate. :smile:

I just saw the bugfix release over on curse, so I gave it another try and it still does crash. I guess I can't report that bug to the caller, because Mojang ist he caller. :) http://pastebin.com/un1EedbN

Crap, I forgot I had it error there.
On Wednesday, April 27, 2016, Sascha Wessel<EMAIL_ADDRESS>wrote:

I just saw the bugfix release over on curse, so I gave it another try and
it still does crash. I guess I can't report that bug to the caller, because
Mojang ist he caller. :) http://pastebin.com/un1EedbN
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/thecodewarrior/Catwalks3/issues/1#issuecomment-215002993

Closed as this is for an old version


eval.data argument in mx.model.FeedForward.create

How do I correctly pass data to eval.data in mx.model.FeedForward.create?  It seems to take data in a different format than the X and y arguments, which is confusing:
library(mxnet)
data(BostonHousing, package="mlbench")
train.ind = seq(1, 506, 3)
train.x = data.matrix(BostonHousing[train.ind, -14])
train.y = BostonHousing[train.ind, 14]
test.x = data.matrix(BostonHousing[-train.ind, -14])
test.y = BostonHousing[-train.ind, 14]
data <- mx.symbol.Variable("data")
fc1 <- mx.symbol.FullyConnected(data, num_hidden=1)
lro <- mx.symbol.LinearRegressionOutput(fc1)
mx.set.seed(0)
model <- mx.model.FeedForward.create(
  lro, X=train.x, y=train.y,
  eval.data=list(
    data=test.x,
    label=test.y
  ),
  ctx=mx.cpu(), num.round=50, array.batch.size=20,
  learning.rate=2e-6, momentum=0.9, eval.metric=mx.metric.rmse)

Yields:
Error: attempt to apply non-function
Traceback:
> traceback()
2: mx.model.train(symbol, ctx, input.shape, params$arg.params, params$aux.params,
       1, num.round, optimizer = optimizer, train.data = X, eval.data = eval.data,
       metric = eval.metric, epoch.end.callback = epoch.end.callback,
       batch.end.callback = batch.end.callback, kvstore = kvstore)
1: mx.model.FeedForward.create(lro, X = train.x, y = train.y, eval.data = list(data = test.x,
       data = test.y), ctx = mx.cpu(), num.round = 50, array.batch.size = 20,
       learning.rate = 2e-06, momentum = 0.9, eval.metric = mx.metric.rmse)

@zachmayer I am afraid this is something we forgot to update.
Maybe the following is what you expect.
eval_data <- mxnet:::mx.model.init.iter(t(train.x), train.y, batch.size=20, is.train = TRUE)
model <- mx.model.FeedForward.create(
  lro, X=train.x, y=train.y,
  eval.data=eval_data,
  ctx=mx.cpu(), num.round=50, array.batch.size=20,
  learning.rate=2e-6, momentum=0.9, eval.metric=mx.metric.rmse)

Auto detect layout of input matrix, use rowmajor..
Start training with 1 devices
[1] Train-rmse=18.7544198250762
[1] Validation-rmse=17.6765946079206
[2] Train-rmse=13.5563010119916
[2] Validation-rmse=10.0524487177531
[3] Train-rmse=11.0570303807623
......

ahah!  Thank you.
In general, examples like that are really useful in the documentation.  Thanks!

@thirdwing  I think we can optionally support passing in a list into eval_data

Yes, adding now. Just a few lines.

@zachmayer Now you can use your old code.
library(mxnet)
data(BostonHousing, package="mlbench")
train.ind = seq(1, 506, 3)
train.x = data.matrix(BostonHousing[train.ind, -14])
train.y = BostonHousing[train.ind, 14]
test.x = data.matrix(BostonHousing[-train.ind, -14])
test.y = BostonHousing[-train.ind, 14]
data <- mx.symbol.Variable("data")
fc1 <- mx.symbol.FullyConnected(data, num_hidden=1)
lro <- mx.symbol.LinearRegressionOutput(fc1)
mx.set.seed(0)
model <- mx.model.FeedForward.create(
  lro, X=train.x, y=train.y,
  eval.data=list(
    data=test.x,
    label=test.y
  ),
  ctx=mx.cpu(), num.round=50, array.batch.size=20,
  learning.rate=2e-6, momentum=0.9, eval.metric=mx.metric.rmse)

Auto detect layout of input matrix, use rowmajor..
Start training with 1 devices
[1] Train-rmse=16.0632823518301
[1] Validation-rmse=10.1766422920373
[2] Train-rmse=12.279237506027
[2] Validation-rmse=12.4331790778543
[3] Train-rmse=11.1984636779466
[3] Validation-rmse=10.3303056488224
......

Fantastic, thank you.  Would it be difficult to implement early stopping based on the evaluation set?

@zachmayer MXNetR is a R-package, and all the training logic, including the parameter optimization, evaluation are on R, so I suppose it is possible for any R hacker to add that feature :)

I'll take a look :-)
—
Sent from Mailbox
On Sun, Nov 15, 2015 at 1:07 PM, Tianqi Chen<EMAIL_ADDRESS>wrote:

@zachmayer MXNetR is a R-package, and all the training logic, including the parameter optimization, evaluation are on R, so I suppose it is possible for any R hacker to add that feature :)
Reply to this email directly or view it on GitHub:
https://github.com/dmlc/mxnet/issues/579#issuecomment-156840376

@zachmayer Actually it is quite easy to stop early.
Just add a new callback mx.callback.early.stop.
It takes two arguments, train.metric and eval.metric. The training will stop once one of them goes below the standard you set.
library(mxnet)
data(BostonHousing, package="mlbench")
train.ind = seq(1, 506, 3)
train.x = data.matrix(BostonHousing[train.ind, -14])
train.y = BostonHousing[train.ind, 14]
test.x = data.matrix(BostonHousing[-train.ind, -14])
test.y = BostonHousing[-train.ind, 14]
data <- mx.symbol.Variable("data")
fc1 <- mx.symbol.FullyConnected(data, num_hidden=1)
lro <- mx.symbol.LinearRegressionOutput(fc1)
mx.set.seed(0)
model <- mx.model.FeedForward.create(
  lro, X=train.x, y=train.y,
  eval.data=list(
    data=test.x,
    label=test.y
  ),
  ctx=mx.cpu(), num.round=50, array.batch.size=20,
  learning.rate=2e-6, momentum=0.9, eval.metric=mx.metric.rmse,
  epoch.end.callback=mx.callback.early.stop(10, 10))

Auto detect layout of input matrix, use rowmajor..
Start training with 1 devices
[1] Train-rmse=16.0632823518301
[1] Validation-rmse=10.1766422920373
[2] Train-rmse=12.279237506027
[2] Validation-rmse=12.4331790778543
[3] Train-rmse=11.1984636779466
[3] Validation-rmse=10.3303056488224
[4] Train-rmse=10.2645248908194
[4] Validation-rmse=8.4276043147402

Ok, I'm starting to get how callbacks work.  Can you share the source code for mx.callback.early.stop?  I'll probably modify it to stop after N iterations without an improvement in validation error, rather than a hard threshold for validation error.

It is on my github https://github.com/thirdwing/mxnet/commit/76c6d7bdf59ecae78a7c16612c4775f7427ae8ac
You can see the difference from the link. I am writing a document for callback functions. There are many things can be done through callbacks.


Add unified and simple to use API

The current API that forces users to select a specific algorithm may be confusing to new users. Add an api with sensible defaults for those users.

Fixed.


wrap invokes in try/catch

idk if you want alert() on all these because that could be jarring to interrupt. Could maybe just toast?


SpeechToText: When coexistence with FirebasePerf, happened Duplicate class on build.

Environment details
OS
Android
Java version
Java 8
Speech version
v1.24.11
Steps to reproduce

Installation Speech-to-Text with official Quickstart: Using client libraries
Installation Firebase Pref with official Add Firebase to your Android project
run build

Code example
See: Sample app's branch and app level build.gradle
Build log
% ./gradlew assemble
Execution failed for task ':app:checkDebugDuplicateClasses'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.CheckDuplicatesRunnable
   > Duplicate class com.google.api.Advice found in modules jetified-proto-google-common-protos-2.0.1 (com.google.api.grpc:proto-google-common-protos:2.0.1) and jetified-protolite-well-known-types-17.1.1-runtime (com.google.firebase:protolite-well-known-types:17.1.1)
     Duplicate class com.google.api.Advice$1 found in modules jetified-proto-google-common-protos-2.0.1 (com.google.api.grpc:proto-google-common-protos:2.0.1) and jetified-protolite-well-known-types-17.1.1-runtime (com.google.firebase:protolite-well-known-types:17.1.1)
     Duplicate class com.google.api.Advice$Builder found in modules jetified-proto-google-common-protos-2.0.1 (com.google.api.grpc:proto-google-common-protos:2.0.1) and jetified-protolite-well-known-types-17.1.1-runtime (com.google.firebase:protolite-well-known-types:17.1.1)
     Duplicate class com.google.api.AdviceOrBuilder found in modules jetified-proto-google-common-protos-2.0.1 (com.google.api.grpc:proto-google-common-protos:2.0.1) and jetified-protolite-well-known-types-17.1.1-runtime (com.google.firebase:protolite-well-known-types:17.1.1)
:
:

External references such as API reference guides

https://cloud.google.com/speech-to-text/docs/quickstart-client-libraries
https://firebase.google.com/docs/android/setup

Thanks!

Hi @yashims, please use the built-in recognition activity, if possible. Otherwise, this tutorial is a great explainer on calling Google Cloud APIs from your mobile app.

Hi @b-loved-dreamer, Thank you for response and useful information.
I tried RecognizerIntent according to your advice, and it will maybe work so well in my case!!
This issue to closed.
Thank you for politely answering to misguided question.


Add class AbstractFieldFormOrder

The class Field with attributes form and order and functions save and delete is essential for using in admin form. This should be also defined as an abstract class in order to use it without repeating the class code.
Subtask: Add test for Field delete.

I don't see the benefit of this considering there's already an abstract class for the field.


Startup Issues?

I'm out looking for a self-hosted Pastebin service. I'm mostly doing:

clone a project
run it
test it
evaluate usefulness for my needs.

I cloned this repo and moved into the pkg/pasty folder, then ran go run .
pasty/$ go run .
2022/01/08 01:02:53 Loading the application configuration...
2022/01/08 01:02:53 Loading the configured storage driver...
2022/01/08 01:02:53 Serving the web resources...

Then I went to http://localhost:8080 and got this.

Maybe this is expected, but it's certainly not user friendly. So I can back here and scanned through the README more, but found no mention of "how to use" this app. I can only assume what I'm getting from the web interface is not expected, and something is wrong here.
Then, on a whim I did cd ../.. ; go run ./cmd/pasty and got the same output, but this time the web server had actual content. So I looked in the README for the word log but found nothing. This app doesn't seem to log errors, or requests, or anything happening. Is that expected?
I finally tested it. My test is (always) paste a 5MB log file and hit save.
Does it work? Nope, it just spins.
Is it fast, or slow? Slow, and the line numbers seem to misalign with the paste lines while scrolling.
Can it be "loaded" quickly after being saved? It never saved the 5MB paste, and never printed an error.
Small pastes seem to work OK. This is my feedback, hope it's helpful.

Hello, thanks for your feedback. I'll explain some points you made.

Maybe this is expected, but it's certainly not user friendly.

Generally, running the app (or any app) using go run is never meant for production purposes. It's a command used by people who actively develop on a project to avoid rebuilding it every single time.
If you want to run the app on a production system you definitely should build it.
This said, the error you get when running the app while your CWD is cmd/pasty/ is due to a routing error. The app tries to serve the ./web/ directory which does not exist inside the cmd/pasty/ directory.
These aspects are clearly stated in the README (see 'Building from source').

So I looked in the README for the word log but found nothing. This app doesn't seem to log errors, or requests, or anything happening. Is that expected?

I have to admit I did not implement that much logging when I initially started the project. Thanks for bringing this up, I will create an issue on this topic.

I finally tested it. My test is (always) paste a 5MB log file and hit save.

Jup, piping a 5MB string into pasty causes severe performance issues. I don't see the point in having such a huge(!) paste though as the most common use case is sharing small log or code snippets which is handled pretty well.
For bigger payloads a file sharing platform (e.g. https://workupload.com) would be far more suitable in my opinion.
Again, thank you for your test and feedback ^^

I will close this issue as I created separate issues for all the points you mentioned.
Issues #32 and #37 could be of interest for you.
Feel free to open another issue if you have further questions!


Support constructing long LDAP expressions using concise C++

Fixes #246
This change is based on feedback from a user who wants to construct long LDAP expressions based on conditions in their code. See #246 for details.
Signed-off-by: The Mathworks Inc<EMAIL_ADDRESS>

Codecov Report

Merging #247 into development will decrease coverage by 0.22%.
The diff coverage is 100%.

@@               Coverage Diff               @@
##           development     #247      +/-   ##
===============================================
- Coverage        82.11%   81.88%   -0.23%
===============================================
  Files              119      119
  Lines             7848     7959     +111
===============================================
+ Hits              6444     6517      +73
- Misses            1404     1442      +38

Impacted Files
Coverage Δ

framework/include/cppmicroservices/LDAPProp.h
100% <ø> (ø)
:arrow_up:

framework/src/util/LDAPProp.cpp
100% <100%> (ø)
:arrow_up:

framework/src/bundle/BundleThread.cpp
73.83% <0%> (-1.17%)
:arrow_down:

util/src/FileSystem.cpp
95.74% <0%> (-0.09%)
:arrow_down:

framework/src/bundle/BundleStorageFile.cpp
0% <0%> (ø)
:arrow_up:

framework/src/bundle/BundleElfFile.cpp
0% <0%> (ø)
:arrow_up:

framework/src/bundle/BundlePEFile.cpp
0% <0%> (ø)
:arrow_up:

framework/src/util/Utils.cpp
62.76% <0%> (ø)
:arrow_up:

framework/src/bundle/BundleObjFile.cpp
0% <0%> (ø)
:arrow_up:

... and 11 more


@ConfigurationProperties and @RefreshScope don't work together as documented

Based on reading the docs and this https://gist.github.com/dsyer/a43fe5f74427b371519af68c5c4904c7 it was my understanding that it should be possible to place @RefreshScope on a bean defined with @ ConfigurationProperties and have the properties bean  put in the refresh scope. It would appear that this doesn't work - a bean created by scanning for ConfigurationProperties classes or via @ EnableConfigurationProperties is never put into the RefreshScope correctly. On the other hand, if the same bean is created by means of an @ Bean annotated method on a configuration class, it is correctly added to the RefreshScope.
This is frustrating because explicit bean creation for these configuration beans makes it very hard to use immutable classes for them without duplicating a bunch of spring internal binding code; and having them work in RefreshScope would be a convenient  way around not being able to rely on the EnvironmentChangedEvent rebinding for @ ConstructorBinding  ConfigurationProperties classes. From what I can see, RefreshScope.refresh results in the entire bean being thrown away and reloaded (thus compatible with ConstructorBinding) the next time a method is called on the proxy.
Testcase showing various different configurations of RefreshScope here: https://github.com/symposion/spring-test/tree/refresh-scope-properties-bean . For all but three of the beans, calling the foo() method after a refresh results in a new bean being constructed (as expected for RefreshScope). But the bean created by EnableConfigurationProperties  isn't correctly placed into the RefreshScope, so this doesn't work for it.

We have no plans to support refresh of read only properties (ie constructor binding)

A couple of  points to note:

Although my original use case concerns being able to use @ ConstructorBinding, none of the beans in my test case use ConstructorBinding. There is a bug/undocumented limitation here that relates purely to the fact that you can't combine RefreshScope and ConfigurationProperties on a bean discovered by spring's EnabledConfigurationProperties/ConfigurationPropertiesScan mechanisms. Obviously if you don't need ConstructorBinding this is easier to work around because you can define an explicit bean factory method somewhere and annotate that with RefreshScope instead, but this isn't documented and obviously entails adding some not-very-Spring-Boot boilerplate

I know from the other ticket that you didn't want to support rebinding for immutable classes via EnvironmentChangeEvent - which I understand because it's clearly going to be tricky to achieve without some sort of proxy present. But it appears that you're also saying you won't support refreshing them via RefreshScope; this is more disappointing since it closes off the last credible avenue to achieving a requirement that I believe quite a few people have, and there's already a proxying mechanism in place here to enable a bean to be swapped out.

There was a long-running spring boot ticket about allowing @ ConfigurationProperties to be used on Interfaces so that people didn't have to expose mutable properties beans to the rest of their context because of the internal needs of Spring's binding system. This ticket was eventually closed on the grounds that @ ConstructorBinding provides a credible alternative to binding fields behind an interface. If Spring Cloud won't support refreshing ConstructorBound obejcts, this undermines this decision somewhat. In a distributed microservices world, I don't think it's unreasonable to want to be able to provide an immutable interface to clients of a configuration class, but still support the idea of refreshing the values they represent when e.g. they are changed in a central config store. Not supporting this entails users either having to duplicate a  lot of property methods to a redundant interface - especially frustrating in a world of kotlin data classes and value objects - or accept that clients of configuration properties classes must be allowed (unsafely) to modify configuration that is supposed to be centrally managed

FWIW, it seems to be possible to make this work - no doubt you will tell me that what I've done is a terrible idea and will break all manner of things, but hey, what the hell:
class ConfigurationPropertiesRefreshScopeFixer : BeanDefinitionRegistryPostProcessor {
    override fun postProcessBeanFactory(beanFactory: ConfigurableListableBeanFactory) {
        //NO-OP
    }
    override fun postProcessBeanDefinitionRegistry(registry: BeanDefinitionRegistry) {
        for (name in registry.beanDefinitionNames) {
            val beanDefinition = registry.getBeanDefinition(name!!)
            if (beanDefinition.javaClass.name == "org.springframework.boot.context.properties.ConfigurationPropertiesValueObjectBeanDefinition") {
                val gbd = beanDefinition as GenericBeanDefinition
                val annAttrs = AnnotationAttributes.fromMap(AnnotationMetadata.introspect(gbd.beanClass).getAnnotationAttributes(Scope::class.java.name, false))
                val scopedProxyMode = annAttrs?.getEnum<ScopedProxyMode>("proxyMode") ?: ScopedProxyMode.NO
                gbd.scope = annAttrs?.getString("value") ?: "singleton"
                if (scopedProxyMode == ScopedProxyMode.NO) {
                    continue
                }
                val proxyTargetClass = scopedProxyMode == ScopedProxyMode.TARGET_CLASS
                registry.removeBeanDefinition(name)
                val scopedProxy = ScopedProxyUtils.createScopedProxy(BeanDefinitionHolder(gbd, name), registry, proxyTargetClass)
                registry.registerBeanDefinition(scopedProxy.beanName, scopedProxy.beanDefinition)
            }
        }
    }
}

Obviously it's a lot uglier than it needs to be because there's a bunch of package-visibility stuff in Spring that I couldn't take advantage of. But it seems to work and lets ConfigurationProperties beans be in RefreshScope - which in turn means that they get rebound even if they are using ConstructorBinding

There is a bug/undocumented limitation here that relates purely to the fact that you can't combine RefreshScope and ConfigurationProperties on a bean discovered by spring's EnabledConfigurationProperties/ConfigurationPropertiesScan mechanisms.

I think this is working as designed. If you want a refresh scope configuration properties, use an @Bean method in configuration.

@spencergibb, I'm also of the opinion that this should be looked at.
Quoting from the issue #1547 of the spring-cloud-config project. The issue was closed so replying here.

🤷♂ I'm going to keep this closed and use immutable configuration as a marker that it shouldn't be refreshed. If you want it to be, use mutable configuration objects.

@spencergibb, may I ask you to share what makes you think that immutable configuration shouldn't be REFRESHED? Because as a result, what your comment is essentially leading to, as an analogy, is that if a mutable collection contains immutable objects (e.g. configs), then it is a marker that the elements can't be replaced in the collection, because that is what I believe is asked here.
While you are right in the sense that an immutable object should not be modified, it is not the goal we are trying to achieve. We would like to have a NEW instance with NEW values injected dynamically behind the proxy object once the external configs change, without exposing setter methods to guarantee immutability of the current object. Just because we would like to use a new instance with new fields doesn't mean we have to compromise immutability of existing objects. We just want to replace it, not modify it. What do you think about it?

You should add @Component at the class that is annotated by ConfigurationProperties, after that by calling /actuator/refresh url, surprisingly you will see your configuration will ne refreshed

You should add @component at the class that is annotated by ConfigurationProperties, after that by calling /actuator/refresh url, surprisingly you will see your configuration will ne refreshed

Sadly, this doesn't work with @ConstructorBinding which is a big part of my original motivation for raising this ticket


It's happening with mine all the  time...

I've had it many times in the two weeks I've been in school...

You will have to debug it, sorry.

Any update on this?

Sorry Allen. No. I don’t have a clue how to debug this. I’m taking a coding class and am really new to all these things!
Worship Him, King of Kings!!

On May 10, 2018, at 5:55 PM, Brock Allen<EMAIL_ADDRESS>wrote:
Any update on this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Sorry, I can't help if I don't know what's wrong. Closing. If you still have issues, feel free to reopen.


feat(block): make a previous l1 block number available in public execution

Description
motivation:
This is a way to get the l1 block hash within the historic blocks tree
Please provide a paragraph or two giving a summary of the change, including relevant motivation and context.
Checklist:

[ ] I have reviewed my diff in github, line by line.
[ ] Every change is related to the PR description.
[ ] I have linked this pull request to the issue(s) that it resolves.
[ ] There are no unexpected formatting changes, superfluous debug logs, or commented-out code.
[ ] The branch has been merged or rebased against the head of its merge target.
[ ] I'm happy for the PR to be merged at the reviewer's next convenience.

Closing this issue as stale, the work has been catalogued and can be picked up in the following issue: https://github.com/AztecProtocol/aztec-packages/issues/1523


First command gets dropped after time of no actions

Hello currently running stable at 2.07.01 with fw 26660700 with conbee 2 stick on a qnap nas.
I have grouped my lights and control them either via alexa or switches.
Often times the first command by a switch goes ignored or a alexa command gets answered by alexa with 'OK', but nothing happens.
The second try always works and all consecutive commands work like a charm.
But the first command after like 5 minutes of inactivity gets dropped.
I can't see any logs that are indicative of failures.
I am using docker-compose and this is part of my setup:
version: "3.3"
services:
  deconz:
    image: marthoc/deconz:stable
    restart: unless-stopped
    container_name: deconz
    mac_address: [DELETED]
    networks:
      qnet-static-bond0-79e6cc:
        ipv4_address: [DELETED]
    restart: always
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - deconz-data:/root/.local/share/dresden-elektronik/deCONZ
    ports:
      - "5900:5900"
      - "80:80"
      - "443:443"
    devices:
      - /dev/ttyACM0
    environment:
      - DECONZ_DEVICE=/dev/ttyACM0
      - DECONZ_WEB_PORT=80
      - DECONZ_WS_PORT=443
      - DEBUG_INFO=1
      - DEBUG_APS=0
      - DEBUG_ZCL=0
      - DEBUG_ZDP=0
      - DEBUG_OTAU=0
      - TZ=Europe/Berlin
      - DECONZ_VNC_MODE=0

These are the devices in my zigbee net:

I am directly using phoscon to group and control via switches. For alexa I am using iobroker and node-red.
Node-Red for alexa is configured via node-red-contrib-amazon-echo and looks like this:

But since I also experience the problem with the switches, it should have nothing to do with alexa integration.
Has anyone else this problem or an idea of how I can find the reason for it?
Thanks in advance for help!

I restarted everything twice and cannot reproduce the error anymore.
No idea what was happening 🤷♂


chore(package.json) http -> https

Google Chrome is marking http websites as insecure starting from July 2018
https://momentjs.com as well as https://codeofmatt.com support https, so I don't see any reasons not to switch :)

Coverage report is incorrect, CI build is failing :/ You guys need to take care of robots doing chores here.

If you close and reopen the PR it should nudge CI into running again, hopefully successfully...

If you close and reopen the PR it should nudge CI into running again, hopefully successfully...

Did that, the result is the same.


API Integration

"Allow hosted API services access to the ETL data assets."
Analog to the creation of the output -> db activity in this case (#5 ), most likely

This has been implemented by virtue of the work on the IceNetETL infrastructure by @jemrobinson


When using $IonicPopup, can I change template?

Recently, I have met a confusing problem when using $IonicPopup.prompt, because I need to change the template of an IonicPopup instance after users clicks the button. As we know that, we can stop box from closing by adding e.preventDefault() in the event handler onTap:
{
    onTap: function (e) {
        e.preventDefault();

        // to get the value of the input element
        var inputValue = this.scope.data.response;
        // CONFUSING: can I change the template like changing the title
        // change the title of the box
        this.scope.title = 'new Title';

        // this.scope.tempalte??
    }
}

Hello! Thanks for opening an issue with us! As this seems like more of a support question I will urge that you ask this question on our forum or on our slack channel. Thanks for using Ionic!


CB-3864 subnet selection refactor

More logs are required

Can one of the admins verify this patch?


Failed Autentication Spid PosteID Level II

With SPID POSTE ID during authentication I enter the user name, password I click on login, From the moment I receive the SMS with the code and I insert it in the text field the message login failed appears. The message appears every time I try to authenticate.

Hi @marcodadamo,
this issue seems to be located on the IdP side. spid-laravel is a package for the SP side.
Feel free to re-open if you think there is a problem on the SP side related to the spid-laravel package and you can provide more details about the error.

Ok thanks. Open issue


Analyzer Feedback from IntelliJ

Analyzer Feedback from IntelliJ
Version information

IDEA IC-182.3911.13
2.0.0-edge.46ab040e589adc5200370dec7952ce5150850822
IC-182.3911.13, JRE 1.8.0_152-release-1248-b8x64 JetBrains s.r.o, OS Windows 10(amd64) v10.0 , screens 1536x864

Exception
Please append the contents of:
file://C:\Users\Purus\AppData\Local\Temp\report.txt
Dart analysis server, SDK version 2.0.0-edge.46ab040e589adc5200370dec7952ce5150850822, server version 1.20.3, FATAL error: Failed to handle request: {id: 3, method: analysis.setAnalysisRoots, params: {included: [F:\05. Project\01-Flutter\SilkThread], excluded: [F:\05. Project\01-Flutter\SilkThread\.idea, F:\05. Project\01-Flutter\SilkThread\.dart_tool, F:\05. Project\01-Flutter\SilkThread\.pub, F:\05. Project\01-Flutter\SilkThread\build, F:\05. Project\01-Flutter\SilkThread\out]}, clientRequestTime:<PHONE_NUMBER>907}
FileSystemException: Exists failed, path = 'F:\05. Project\01-Flutter\SilkThread\build\firebase_remote_config\generated\source\r\debug\com\google\android\gms\base' (OS Error: Access is denied.
, errno = 5)
#0      _Directory.existsSync (dart:io/directory_impl.dart:101)
#1      _WindowsDirectoryWatcher._eventsBasedOnFileSystem (package:watcher/src/directory_watcher/windows.dart:324)
#2      _WindowsDirectoryWatcher._onBatch.<anonymous closure> (package:watcher/src/directory_watcher/windows.dart:166)
#3      _HashVMBase

Content of C:\Users\Purus\AppData\Local\Temp\report.txt is below.
Dart analysis server, SDK version 2.0.0-edge.46ab040e589adc5200370dec7952ce5150850822, server version 1.20.3, FATAL error: Failed to handle request: {id: 3, method: analysis.setAnalysisRoots, params: {included: [F:\05. Project\01-Flutter\SilkThread], excluded: [F:\05. Project\01-Flutter\SilkThread\.idea, F:\05. Project\01-Flutter\SilkThread\.dart_tool, F:\05. Project\01-Flutter\SilkThread\.pub, F:\05. Project\01-Flutter\SilkThread\build, F:\05. Project\01-Flutter\SilkThread\out]}, clientRequestTime:<PHONE_NUMBER>907}
FileSystemException: Exists failed, path = 'F:\05. Project\01-Flutter\SilkThread\build\firebase_remote_config\generated\source\r\debug\com\google\android\gms\base' (OS Error: Access is denied.
, errno = 5)
#0      _Directory.existsSync (dart:io/directory_impl.dart:101)
#1      _WindowsDirectoryWatcher._eventsBasedOnFileSystem (package:watcher/src/directory_watcher/windows.dart:324)
#2      _WindowsDirectoryWatcher._onBatch.<anonymous closure> (package:watcher/src/directory_watcher/windows.dart:166)
#3      _HashVMBase&MapMixin&&_LinkedHashMapMixin.forEach (dart:collection-patch/dart:collection/compact_hash.dart:363)
#4      _WindowsDirectoryWatcher._onBatch (package:watcher/src/directory_watcher/windows.dart:163)
#5      _WindowsDirectoryWatcher._onEvent.<anonymous closure> (package:watcher/src/directory_watcher/windows.dart:157)
#6      _rootRun (dart:async/zone.dart:1122)
#7      _CustomZone.run (dart:async/zone.dart:1023)
#8      _CustomZone.runGuarded (dart:async/zone.dart:925)
#9      _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:965)
#10     _rootRun (dart:async/zone.dart:1126)
#11     _CustomZone.run (dart:async/zone.dart:1023)
#12     _CustomZone.bindCallback.<anonymous closure> (dart:async/zone.dart:949)
#13     Timer._createTimer.<anonymous closure> (dart:async-patch/dart:async/timer_patch.dart:21)
#14     _Timer._runTimers (dart:isolate-patch/dart:isolate/timer_impl.dart:382)
#15     _Timer._handleMessage (dart:isolate-patch/dart:isolate/timer_impl.dart:416)
#16     _RawReceivePortImpl._handleMessage (dart:isolate-patch/dart:isolate/isolate_patch.dart:165)

1533832904909 <= {"event":"server.status","params":{"analysis":{"isAnalyzing":true}}}
1533832904909 <= {"event":"analysis.flushResults","params":{"files":["F:\\05. Project\\01-Flutter\\SilkThread\\lib\\categories_list.dart___jb_tmp___"]}}
1533832905081 <= {"event":"analysis.errors","params":{"file":"F:\\05. Project\\01-Flutter\\SilkThread\\lib\\categories_list.dart","errors":[]}}
1533832905081 <= {"event":"analysis.highlights","params":{"file":"F:\\05. Project\\01-Flutter\\SilkThread\\lib\\categories_list.dart","regions":[{"type":"DIRECTIVE","offset":0,"length":39},{"type":"BU
1533832905081 <= {"event":"analysis.navigation","params":{"file":"F:\\05. Project\\01-Flutter\\SilkThread\\lib\\categories_list.dart","regions":[{"offset":7,"length":31,"targets":[0]},{"offset":47,"le
1533832905081 <= {"event":"analysis.closingLabels","params":{"file":"F:\\05. Project\\01-Flutter\\SilkThread\\lib\\categories_list.dart","labels":[{"offset":1405,"length":371,"label":"Scaffold"},{"off
1533832905097 <= {"event":"analysis.outline","params":{"file":"F:\\05. Project\\01-Flutter\\SilkThread\\lib\\categories_list.dart","kind":"LIBRARY","outline":{"element":{"kind":"COMPILATION_UNIT","nam
1533832905097 <= {"event":"analysis.overrides","params":{"file":"F:\\05. Project\\01-Flutter\\SilkThread\\lib\\categories_list.dart","overrides":[{"offset":167,"length":11,"superclassMember":{"element
1533832905144 <= {"event":"server.status","params":{"analysis":{"isAnalyzing":false}}}
1533832905144 <= {"event":"analysis.implemented","params":{"file":"F:\\05. Project\\01-Flutter\\SilkThread\\lib\\categories_list.dart","classes":[],"members":[]}}
1533832905331 => {"id":"383","method":"analysis.updateContent","params":{"files":{"F:\\05. Project\\01-Flutter\\SilkThread\\lib\\categories_list.dart":{"type":"remove"}}},"clientRequestTime":153383290
1533832905362 <= {"id":"383","result":{}}
1533832905362 <= {"event":"server.status","params":{"analysis":{"isAnalyzing":true}}}
1533832905394 => {"id":"384","method":"edit.getAssists","params":{"file":"F:\\05. Project\\01-Flutter\\SilkThread\\lib\\categories_list.dart","offset":449,"length":0},"clientRequestTime":1533832905394
1533832905566 <= {"event":"analysis.errors","params":{"file":"F:\\05. Project\\01-Flutter\\SilkThread\\lib\\categories_list.dart","errors":[]}}
1533832905581 <= {"id":"384","result":{"assists":[]}}
1533832905581 <= {"event":"analysis.highlights","params":{"file":"F:\\05. Project\\01-Flutter\\SilkThread\\lib\\categories_list.dart","regions":[{"type":"DIRECTIVE","offset":0,"length":39},{"type":"BU
1533832905581 <= {"event":"analysis.navigation","params":{"file":"F:\\05. Project\\01-Flutter\\SilkThread\\lib\\categories_list.dart","regions":[{"offset":7,"length":31,"targets":[0]},{"offset":48,"le
1533832905581 <= {"event":"analysis.closingLabels","params":{"file":"F:\\05. Project\\01-Flutter\\SilkThread\\lib\\categories_list.dart","labels":[{"offset":1457,"length":381,"label":"Scaffold"},{"off
1533832905581 <= {"event":"analysis.outline","params":{"file":"F:\\05. Project\\01-Flutter\\SilkThread\\lib\\categories_list.dart","kind":"LIBRARY","outline":{"element":{"kind":"COMPILATION_UNIT","nam
1533832905581 <= {"event":"analysis.overrides","params":{"file":"F:\\05. Project\\01-Flutter\\SilkThread\\lib\\categories_list.dart","overrides":[{"offset":172,"length":11,"superclassMember":{"element
1533832905581 <= {"event":"server.status","params":{"analysis":{"isAnalyzing":false}}}
1533832905581 <= {"event":"analysis.implemented","params":{"file":"F:\\05. Project\\01-Flutter\\SilkThread\\lib\\categories_list.dart","classes":[],"members":[]}}
1533832905909 => {"id":"385","method":"edit.getAssists","params":{"file":"F:\\05. Project\\01-Flutter\\SilkThread\\lib\\categories_list.dart","offset":350,"length":0},"clientRequestTime":1533832905909
1533832905909 <= {"id":"385","result":{"assists":[]}}
1533833004726 => {"id":"386","method":"edit.getAssists","params":{"file":"F:\\05. Project\\01-Flutter\\SilkThread\\lib\\categories_list.dart","offset":350,"length":0},"clientRequestTime":1533833004726
1533833004726 <= {"id":"386","result":{"assists":[]}}
1533833025746 => {"id":"387","method":"edit.getAssists","params":{"file":"F:\\05. Project\\01-Flutter\\SilkThread\\lib\\categories_list.dart","offset":497,"length":0},"clientRequestTime":1533833025746
1533833025746 <= {"id":"387","result":{"assists":[]}}
1533833049162 <= {"event":"server.error","params":{"isFatal":true,"message":"Failed to handle request: {id: 3, method: analysis.setAnalysisRoots, params: {included: [F:\\05. Project\\01-Flutter\\SilkT

This might be a package:watcher problem, or it might be that we are using is incorrectly.
I will close this issue for now, and reopen depending on the response from the package:watcher developers.

Any update for this issue?


Increase unit tests coverage

Current coverage is 77.97% (diff: 100%)

No coverage report found for master at ddf8f90.

Powered by Codecov. Last update ddf8f90...0a8e6cf


ISPN-13943 Don't implicitly enable the RESP connector if realm does n…

https://issues.redhat.com/browse/ISPN-13943
Fixes TLSWithoutAuthenticationIT and CertWithoutAuthenticationIT failures

merged! thanks @tristantarrant !


[Caroline] No audio on Fedora 39, kernel 6.8.10

Describe the bug
No audio on Fedora 39 after updating to latest kernel 6.8.10 (sound menu shows "Dummy Output"). Audio worked fine on previous kernel.
Boardname
Caroline
Logs
debugging.sh didn't produce a tar file, Fedora 39 doesn't allow debugmem access :(

audio works fine on kernel 6.8.9 :upside_down_face:

upgraded to fedora 40, issue persists

I just installed Fedora 40 cinnamon and there is no sound with the script.
Is there a way to downgrade to kernel 6.8.9?

Exact same issue here - I tested that booting to 6.8.5 fixes the issue.

It works now! Fedora 40 with kernel 6.9.7 sound works. Thanks!


Deploy contracts

What is this feature about? (1 sentence)
This allows users to deploy a contract via the Gnosis Safe web interface.
Why is it needed? What is the value? For whom do we build it?

We have received the feedback regularly that advanced users would like to deploy contracts directly from their Gnosis Safe.
The contracts support it already, no issue there.

High-level overview of the feature

It is possible to deploy a contract

I suggest to have this as part of the contract interaction flow.
On the review screen, we could already display the future deployed contract address (?)

On the tx list and tx list details, I am able to see and inspect the deployment. (No need to store the solidity code though.

Open questions

Where does the solidty code get validated?
Can a user select between CREATE and CREATE2?

Update

Nov 5, Tobias: Add more details

Closed for the moment due to its age and no further evidence supporting the need for it.


Egress logs break when enabling filtering with new Telemetry API

Is this the right place to submit this?

[X] This is not a security vulnerability or a crashing bug
[X] This is not a question about how to use Istio

Bug Description
We are on Istio 1.17.8 and trying to filter out healthcheck logs from AWS Route53 healthchecks. According to the docs, I've setup a new Telemetry object using the below YAML:
apiVersion: telemetry.istio.io/v1alpha1
kind: Telemetry
metadata:
  name: mesh-defaults
  namespace: istio-config
spec:
  accessLogging:
  - filter:
      expression: '!(request.useragent.startsWith("Amazon-Route53-Health-Check-Service"))'
    match:
      mode: CLIENT
    providers:
      - name: envoy

And it does work....however, egress logs break for some reason. I get the below log when doing a curl https://www.google.com from my Istio-injected pod:
[2023-10-23T21:14:44.179Z] "- - -" 0 - "-" 883 24293 139 - "-" "-" "-" "-" "<IP_ADDRESS>:443" outbound|443||www.google.com <IP_ADDRESS>:41698 <IP_ADDRESS>:443 <IP_ADDRESS>:38594 - - -
Once I apply that Telemetry object, this stops working. I've tried it without the match.mode block as well, same results.
Using docs here - https://istio.io/latest/docs/reference/config/telemetry/#WorkloadMode
Version
istioctl version
client version: 1.19.3
istiod version: 1.17.8
istiod version: 1.17.8
istiod version: 1.17.8

kubectl version --short
Client Version: v1.25.12
Kustomize Version: v4.5.7
Server Version: v1.25.12-eks-2d98532

Additional Information
No response

/cc @whitneygriffith

can you share the config dump? before vs after?

Is istio-config configured as the rootNamespace or where the workload runs? By default it isn't, so it may not be applying at all

I can reproduce this, configuration looks good.
- name: envoy.filters.network.tcp_proxy
      typedConfig:
        '@type': type.googleapis.com/envoy.extensions.filters.network.tcp_proxy.v3.TcpProxy
        accessLog:
        - filter:
            extensionFilter:
              name: envoy.access_loggers.extension_filters.cel
              typedConfig:
                '@type': type.googleapis.com/envoy.extensions.access_loggers.filters.cel.v3.ExpressionFilter
                expression: '!(request.useragent.startsWith("Amazon-Route53-Health-Check-Service"))'
          name: envoy.access_loggers.file
          typedConfig:
            '@type': type.googleapis.com/envoy.extensions.access_loggers.file.v3.FileAccessLog
            logFormat:
              textFormatSource:
                inlineString: |
                  [%START_TIME%] "%REQ(:METHOD)% %REQ(X-ENVOY-ORIGINAL-PATH?:PATH)% %PROTOCOL%" %RESPONSE_CODE% %RESPONSE_FLAGS% %RESPONSE_CODE_DETAILS% %CONNECTION_TERMINATION_DETAILS% "%UPSTREAM_TRANSPORT_FAILURE_REASON%" %BYTES_RECEIVED% %BYTES_SENT% %DURATION% %RESP(X-ENVOY-UPSTREAM-SERVICE-TIME)% "%REQ(X-FORWARDED-FOR)%" "%REQ(USER-AGENT)%" "%REQ(X-REQUEST-ID)%" "%REQ(:AUTHORITY)%" "%UPSTREAM_HOST%" %UPSTREAM_CLUSTER% %UPSTREAM_LOCAL_ADDRESS% %DOWNSTREAM_LOCAL_ADDRESS% %DOWNSTREAM_REMOTE_ADDRESS% %REQUESTED_SERVER_NAME% %ROUTE_NAME%
            path: /dev/stdout
        cluster: PassthroughCluster
        statPrefix: PassthroughCluster

Does request.useragent.startsWith error out on TCP request since there is no request.useragent perhaps?

Does request.useragent.startsWith error out on TCP request since there is no request.useragent perhaps?

yes, I think that's root cause.

You shouldn't be using HTTP condition on TCP traffic IMHO. That should be handled at a higher level of API.

You shouldn't be using HTTP condition on TCP traffic IMHO. That should be handled at a higher level of API.

But PassthroughCluster is sepical, can envoy provides an option tride error as false?

CEL semantics usually handles this by using short-circuiting login, e.g. (some condition that is true for TCP) || (error) evaluates to true for TCP.

is there some expression like isTCP?

I was checking but didn't find anything like isTCP. Without it, we should
handle it at a higher level in the API. That would work better long term.
On Mon, Oct 23, 2023 at 7:50 PM zirain @.***> wrote:

is there some expression like isTCP?
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/47533#issuecomment-1776416328, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACIYRRVTCFIQ5NHTRT56KLLYA4UILAVCNFSM6AAAAAA6MW6G6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZWGQYTMMZSHA
.
You are receiving this because you commented.Message ID:
@.***>

Is istio-config configured as the rootNamespace or where the workload runs? By default it isn't, so it may not be applying at all

Yes it is. I know it's working since it IS filtering out R53 health checks....it's just filtering out ALL egress logs as well for some reason

Does request.useragent.startsWith error out on TCP request since there is no request.useragent perhaps?

yes, I think that's root cause.

ah...so since egress is all TCP traffic (we use REGISTRY_ONLY and only allow our k8 pods to hit what they have ServiceEntries for), my layer 7 rule is effectively "breaking it"? If that's the case, what is the workaround? The Telemetry object exposed all this cool new filtering you can do with logs but if all the layer 7 stuff breaks layer 4 egress, it's not really useable then.....

I think you can do something like !has(request.useragent) || !(request.useragent.startsWith("Amazon-Route53-Health-Check-Service")). Not 100% sure

That worked!! You the man Mr @howardjohn. Should I just close this issue then?

IMO this is super easy to get wrong and not obvious. I had the same issue with CEL for K8s recently. Worth improving some docs around this, IMO.

In theory, trying to call startsWith on the non-existent request.useragent in TCP scenarios should have caused a runtime error.
Wasn't this error supposed to be visible in the envoy logs?

In theory, trying to call startsWith on the non-existent request.useragent in TCP scenarios should have caused a runtime error.
Wasn't this error supposed to be visible in the envoy logs?

Actually Envoy says expression errors are considered false. https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/access_loggers/filters/cel/v3/cel.proto#extensions-access-loggers-filters-cel-v3-expressionfilter
So the required documentation on our end will be to inform users that CEL expression are errors are considered false and errors are known to occur when attempting to access a non-existent field. Will this be all that's needed to close the issue?

Will this be all that's needed to close the issue?

I think so, but also could have a bit more explanation on how to handle this, possible with examples. https://kubernetes.io/docs/reference/using-api/cel/#type-checking for example. I wonder if we should even link to https://playcel.undistro.io/ now that https://github.com/undistro/cel-playground/pull/40 is merged (although it doesn't look like its live yet)

Will this be all that's needed to close the issue?

I think so, but also could have a bit more explanation on how to handle this, possible with examples. https://kubernetes.io/docs/reference/using-api/cel/#type-checking for example. I wonder if we should even link to https://playcel.undistro.io/ now that undistro/cel-playground#40 is merged

I concur, it didn't even occur to me that a layer 7 filter would blow up layer 4 egress logs, though it makes sense once I think about it. Specifically mentioning this will save folks headache who try to do anything remotely similar.