[1.12 rc4]service discovery failed

now i create two service and network like this
   docker network create --driver overlay mynet
   docker service create --network mynet --name redis redis
   docker service create --network mynet --name web my-web

now i try to connect redis server in my web server but failed
➜  ~ docker exec -it  web.1.4i3r3f3djfgpwmtkc6kivacvf  sh
# ping redis
PING redis (<IP_ADDRESS>): 56 data bytes
92 bytes from f8c0f07ea3e3 (<IP_ADDRESS>): Destination Host Unreachable
92 bytes from f8c0f07ea3e3 (<IP_ADDRESS>): Destination Host Unreachable
92 bytes from f8c0f07ea3e3 (<IP_ADDRESS>): Destination Host Unreachable
92 bytes from f8c0f07ea3e3 (<IP_ADDRESS>): Destination Host Unreachable

because the redis container ip is changed
➜  ~ docker exec -it redis.1.6y9v4qwgd68b1e4b04khxl754 sh
# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
68: eth0@if69: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UP group default
    link/ether 02:42:0a:00:00:03 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::42:aff:fe00:3/64 scope link
       valid_lft forever preferred_lft forever
70: eth1@if71: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 02:42:ac:12:00:03 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/16 scope global eth1
       valid_lft forever preferred_lft forever
    inet6 fe80::42:acff:fe12:3/64 scope link
       valid_lft forever preferred_lft forever

docker version
➜  ~ docker info
Containers: 1
 Running: 1
 Paused: 0
 Stopped: 0
Images: 2
Server Version: 1.12.0-rc4
Storage Driver: devicemapper
 Pool Name: docker-253:0-34333044-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 10.74 GB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 959.6 MB
 Data Space Total: 107.4 GB
 Data Space Available: 17.27 GB
 Metadata Space Used: 2.425 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.145 GB
 Thin Pool Minimum Free Space: 10.74 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 WARNING: Usage of loopback devices is strongly discouraged for production use. Use `--storage-opt dm.thinpooldev` to specify a custom block storage device.
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.107-RHEL7 (2015-10-14)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: overlay bridge null host
Swarm: active
 NodeID: 3q9rse4k6v0jlf12hb68fuelr
 IsManager: No
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 3.10.0-327.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 3.703 GiB
Name: localhost
ID: PD5B:R7W4:Q64C:X5VW:ET6Q:OFQP:GFYE:5NYG:V3DU:XS5Q:B6UL:RWIV
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 42
 Goroutines: 101
 System Time: 2016-07-15T05:15:55.033930206-04:00
 EventsListeners: 1
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-ip6tables is disabled
Experimental: true
Insecure Registries:
 <IP_ADDRESS>/8

service redis
➜  ~ docker service inspect redis
[
    {
        "ID": "8jiozk9zwwm3ujry15kgn0alh",
        "Version": {
            "Index": 224
        },
        "CreatedAt": "2016-07-15T08:33:11.804914778Z",
        "UpdatedAt": "2016-07-15T08:33:11.808655794Z",
        "Spec": {
            "Name": "redis",
            "TaskTemplate": {
                "ContainerSpec": {
                    "Image": "redis"
                },
                "Resources": {
                    "Limits": {},
                    "Reservations": {}
                },
                "RestartPolicy": {
                    "Condition": "any",
                    "MaxAttempts": 0
                },
                "Placement": {}
            },
            "Mode": {
                "Replicated": {
                    "Replicas": 1
                }
            },
            "UpdateConfig": {},
            "Networks": [
                {
                    "Target": "28om24odrwbevea8kuwww7kpb"
                }
            ],
            "EndpointSpec": {
                "Mode": "vip"
            }
        },
        "Endpoint": {
            "Spec": {
                "Mode": "vip"
            },
            "VirtualIPs": [
                {
                    "NetworkID": "28om24odrwbevea8kuwww7kpb",
                    "Addr": "<IP_ADDRESS>/24"
                }
            ]
        }
    }
]

service web
➜  ~ docker service inspect web
[
    {
        "ID": "9zx2r9jpxrb04vsx8mdn10oe2",
        "Version": {
            "Index": 233
        },
        "CreatedAt": "2016-07-15T08:35:29.858726294Z",
        "UpdatedAt": "2016-07-15T08:35:29.86259807Z",
        "Spec": {
            "Name": "web",
            "TaskTemplate": {
                "ContainerSpec": {
                    "Image": "demoregistry.dataman-inc.com/library/yaoyun-web:0711"
                },
                "Resources": {
                    "Limits": {},
                    "Reservations": {}
                },
                "RestartPolicy": {
                    "Condition": "any",
                    "MaxAttempts": 0
                },
                "Placement": {}
            },
            "Mode": {
                "Replicated": {
                    "Replicas": 1
                }
            },
            "UpdateConfig": {},
            "Networks": [
                {
                    "Target": "28om24odrwbevea8kuwww7kpb"
                }
            ],
            "EndpointSpec": {
                "Mode": "vip"
            }
        },
        "Endpoint": {
            "Spec": {
                "Mode": "vip"
            },
            "VirtualIPs": [
                {
                    "NetworkID": "28om24odrwbevea8kuwww7kpb",
                    "Addr": "<IP_ADDRESS>/24"
                }
            ]
        }
    }
]

Hi @upccup;
First of all, I'd say the title of your issue is wrong. Service discovery works in your case as you're getting the container ip address via the docker embed DNS server. The problem should be elsewhere, but there is definitely a problem.
I have to say I have been experiencing the same error. But also with the same service. Service discovery works for me for other services (php-fpm, nginx, mailcatcher) but not for redis.
I wonder if there is some sort of default configuration in redis container that make the connection to fail.
Looking forward to read what the experts have to say in this regard.
Thank for your post!

How did you init/join the cluster? Did you specify a --listen-addr?

@cpuguy83  yes i was init and join cluster with this conmand
docker swarm init --listen-addr <IP_ADDRESS>:2377

and
 docker swarm join  \
   --secret 9781uimms4epyyzzfhgc8shr1 \
   --ca-hash  sha256:a46be44f491e08afe0a1c59c136a25668df1c3c012338f3a0c7fe6d5a27872ec \
   --listen-addr <IP_ADDRESS>:2377   <IP_ADDRESS>:2377

hi @hvpareja  misunderstand service discovery of new swarm with 1.12rc. but if this is not the right way to do service discovery how can id do this.
moreover ithink this problem was case by the service network not update when the container ip was changed

Hi @upccup. As you know, I was dealing with apparently the same issue. Then, I realised that one of my worker nodes had a different revision of the docker engine. As you surely know, you can check the version metadata with the command: docker version.
Once I updated the outdated node and recreated the whole swarm cluster, the overlay network worked internally with no issues. However, I now can't access to the published services from outside the docker network; I have the feeling it's something related with a miss-configured iptables. Though this is another issue I just wanted to share it.
I haven't said you're doing wrongly, by the way. I wouldn't dare as I don't consider I'm an expert to criticise others. I just pointed that your title doesn't describe your issue. You have a problem with the routing, not with the DNS resolution.
Let us know about the consistency of the docker version across your cluster.
Regards.

@hvpareja I'm so sorry of some may allow you to self-critical remarks that because of my bad english.
this is the docker version of the cluster
swarm manager
➜  ~ docker info
Containers: 1
 Running: 1
 Paused: 0
 Stopped: 0
Images: 2
Server Version: 1.12.0-rc4
Storage Driver: devicemapper
 Pool Name: docker-253:0-34333044-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 10.74 GB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 954 MB
 Data Space Total: 107.4 GB
 Data Space Available: 17.21 GB
 Metadata Space Used: 2.318 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.145 GB
 Thin Pool Minimum Free Space: 10.74 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 WARNING: Usage of loopback devices is strongly discouraged for production use. Use `--storage-opt dm.thinpooldev` to specify a custom block storage device.
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.107-RHEL7 (2015-10-14)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host overlay null
Swarm: active
 NodeID: dghvvy08ix9nbdy88nctadwwi
 IsManager: Yes
 Managers: 1
 Nodes: 2
 CACertHash: sha256:a46be44f491e08afe0a1c59c136a25668df1c3c012338f3a0c7fe6d5a27872ec
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 3.10.0-327.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 3.703 GiB
Name: localhost
ID: PD5B:R7W4:Q64C:X5VW:ET6Q:OFQP:GFYE:5NYG:V3DU:XS5Q:B6UL:RWIV
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 52
 Goroutines: 151
 System Time: 2016-07-15T16:22:43.855599467-04:00
 EventsListeners: 1
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-ip6tables is disabled
Experimental: true
Insecure Registries:
 <IP_ADDRESS>/8

swarm worker
➜  ~ docker info
Containers: 3
 Running: 2
 Paused: 0
 Stopped: 1
Images: 2
Server Version: 1.12.0-rc4
Storage Driver: devicemapper
 Pool Name: docker-253:0-34333044-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 10.74 GB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 970.5 MB
 Data Space Total: 107.4 GB
 Data Space Available: 17.26 GB
 Metadata Space Used: 2.527 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.145 GB
 Thin Pool Minimum Free Space: 10.74 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 WARNING: Usage of loopback devices is strongly discouraged for production use. Use `--storage-opt dm.thinpooldev` to specify a custom block storage device.
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.107-RHEL7 (2015-10-14)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null host overlay bridge
Swarm: active
 NodeID: 3q9rse4k6v0jlf12hb68fuelr
 IsManager: No
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 3.10.0-327.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 3.703 GiB
Name: localhost
ID: PD5B:R7W4:Q64C:X5VW:ET6Q:OFQP:GFYE:5NYG:V3DU:XS5Q:B6UL:RWIV
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 52
 Goroutines: 119
 System Time: 2016-07-15T16:21:52.198587549-04:00
 EventsListeners: 2
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-ip6tables is disabled
Experimental: true
Insecure Registries:
 <IP_ADDRESS>/8

swarm node list
➜  ~ docker node ls
ID                           HOSTNAME        MEMBERSHIP  STATUS  AVAILABILITY  MANAGER STATUS
3q9rse4k6v0jlf12hb68fuelr    <IP_ADDRESS>  Accepted    Ready   Active
dghvvy08ix9nbdy88nctadwwi *  <IP_ADDRESS>  Accepted    Ready   Active        Leader

and about the iptables i have add all ports in 10-60000 with tcp/udp into firewall

@hvpareja  may this log of docker  deamon has some help
7月 15 16:42:10 localhost dockerd[3313]: time="2016-07-15T16:42:10.177723179-04:00" level=debug msg="starting exec command 03d00c71c7ba602c66f5b644dc16da1688decdd05983275cc46813b63067433e in container 1a33144b3136bc307052b7c8cad8d94a0b5e893c8376216b86f8960c46bc2827"
7月 15 16:42:10 localhost dockerd[3313]: time="2016-07-15T16:42:10.178831105-04:00" level=debug msg="Calling POST /v1.24/exec/03d00c71c7ba602c66f5b644dc16da1688decdd05983275cc46813b63067433e/resize?h=68&w=272"
7月 15 16:42:10 localhost dockerd[3313]: time="2016-07-15T16:42:10.178887900-04:00" level=debug msg="attach: stdin: begin"
7月 15 16:42:10 localhost dockerd[3313]: time="2016-07-15T16:42:10.178978227-04:00" level=debug msg="attach: stdout: begin"
7月 15 16:42:10 localhost dockerd[3313]: time="2016-07-15T16:42:10.250269931-04:00" level=debug msg="received containerd event: &types.Event{Type:\"start-process\", Id:\"1a33144b3136bc307052b7c8cad8d94a0b5e893c8376216b86f8960c46bc2827\", Status:0x0, Pid:\"03d00c71c7ba602c
7月 15 16:42:10 localhost dockerd[3313]: time="2016-07-15T16:42:10.250907482-04:00" level=debug msg="event unhandled: type:\"start-process\" id:\"1a33144b3136bc307052b7c8cad8d94a0b5e893c8376216b86f8960c46bc2827\" pid:\"03d00c71c7ba602c66f5b644dc16da1688decdd05983275cc4681
7月 15 16:42:11 localhost dockerd[3313]: time="2016-07-15T16:42:11.948577261-04:00" level=debug msg="2016/07/15 16:42:11 [DEBUG] memberlist: TCP connection from=<IP_ADDRESS>:37410\n"
7月 15 16:42:16 localhost dockerd[3313]: time="2016-07-15T16:42:16.593211671-04:00" level=debug msg="Name To resolve: redis."
7月 15 16:42:16 localhost dockerd[3313]: time="2016-07-15T16:42:16.593261132-04:00" level=debug msg="Lookup for redis.: IP [<IP_ADDRESS>]"
7月 15 16:42:16 localhost dockerd[3313]: time="2016-07-15T16:42:16.593495039-04:00" level=debug msg="miss notification for dest IP, <IP_ADDRESS>"
7月 15 16:42:16 localhost dockerd[3313]: time="2016-07-15T16:42:16.593544540-04:00" level=error msg="could not resolve peer \"<IP_ADDRESS>\": could not resolve peer: serf instance not initialized"
7月 15 16:42:17 localhost dockerd[3313]: time="2016-07-15T16:42:17.593585766-04:00" level=debug msg="miss notification for dest IP, <IP_ADDRESS>"
7月 15 16:42:17 localhost dockerd[3313]: time="2016-07-15T16:42:17.593644882-04:00" level=error msg="could not resolve peer \"<IP_ADDRESS>\": could not resolve peer: serf instance not initialized"
7月 15 16:42:18 localhost dockerd[3313]: time="2016-07-15T16:42:18.595962016-04:00" level=debug msg="miss notification for dest IP, <IP_ADDRESS>"
7月 15 16:42:18 localhost dockerd[3313]: time="2016-07-15T16:42:18.596015556-04:00" level=error msg="could not resolve peer \"<IP_ADDRESS>\": could not resolve peer: serf instance not initialized"

Looks like this may be relevant;
could not resolve peer: serf instance not initialized

@thaJeztah  but i think this error is cause thy wrong ip

I found a way how to easily get into state of "could not resolve peer: serf instance not initialized". Create 3 docker-machine instances, initialize swarm mode on one of them, create network=overlay also on this node, after that join another two nodes - you will get into state, when docker on other two nodes will report serf instance not initialized. If you will create 3 docker-machine instances, initialize and join the swarm - and only after that create network=overlay - everything seems working.

Actually still getting these errors

Could this issue:
https://github.com/docker/docker/issues/25087
Be related? Neither too very conclusive anyway ...

ping @mavenugo

@upccup @Ismael I just want to clarify that SD is working as expected. If the connectivity is failing, we have to figure out whats going on with overlay networking and load-balancing. That would require more information or clear reproduction steps so that we can see whats going on.

In 1.12 all issues with load balancing are gone, but the network discovery by hostname does not work, see https://github.com/docker/docker/issues/25236. It does not seem like the same bug as described here.

@mavenugo @thaJeztah afaik this is expected because ping isn't supported by ipvs implementation currently.

Service discovery seems fine to me though. I can both ping and curl services.
docker service create --name swarmtest --replicas 2 --network backend jhorwit2/swarm-test:0.0.1

Then in another container:
$ docker exec -it (docker ps -lq)  bash
curl swarmtest
eth0:	<IP_ADDRESS>
root@b4184eab6c47:/# curl swarmtest
eth0:	<IP_ADDRESS>
root@b4184eab6c47:/# curl swarmtest
eth0:	<IP_ADDRESS>
root@b4184eab6c47:/# curl swarmtest
eth0:	<IP_ADDRESS>

As you can see i'm RR between each vip in the network for swarmtest service.

Thanks @jhorwit2 for confirming. and yes we added partial support for ping service-name due to popular demand.
anyways, I think we still need to figure out the specifics of issues seen in @upccup @Ismael environments.

I updated to 1.12 and still have the same issue, I can't ping. But wget from one to the other does work. It didn't occur to me to try wget directly. Ping is the basic tool for network connectivity for me.
You should complete the docs. docker service create doesn't tell you how to mount things. In rc5 the parameter was "dest", but now it's "destination" (I found it by trial and error).

How to reproduce my environment
Networking
In Debian's /etc/network/interfaces
auto lxcbr0
iface lxcbr0 inet dhcp
        bridge_ports eth1
        bridge_fd 0
        bridge_maxwait 0

Vagrant File
# -*- mode: ruby -*-
# vi: set ft=ruby :

# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure(2) do |config|
  config.vm.box = "debian/jessie64"

  # Create a public network, which generally matched to bridged network.
  # Bridged networks make the machine appear as another physical device on
  # your network.
  config.vm.network "public_network", bridge: "lxcbr0", use_dhcp_assigned_default_route: true

  config.vm.provider "virtualbox" do |vb|
     vb.memory = "1024"
  end

  config.vm.provision "shell", inline: <<-SHELL
    sudo apt-get update
    sudo apt-get install htop
    sudo sh /vagrant/getdocker.sh #script from get docker
    sudo usermod -aG docker vagrant

    sudo echo "<IP_ADDRESS>:/fileserver/archivos/Ismael/docker /media/fileserver nfs rw 0 0" >> /etc/fstab
    sudo mount -a

  SHELL

  config.vm.define "d1" do |d1|
    config.vm.provision "shell", inline: <<-SHELL
       echo "d1" > /etc/hostname
    SHELL
  end

  config.vm.define "d2" do |d2|
    config.vm.provision "shell", inline: <<-SHELL
       echo "d2" > /etc/hostname
    SHELL
  end

  config.vm.define "d3" do |d3|
    config.vm.provision "shell", inline: <<-SHELL
       echo "d3" > /etc/hostname
    SHELL
  end

end

Swarm creation
In my case, my dhcp assigned d1: <IP_ADDRESS>, d2: <IP_ADDRESS>, d3: <IP_ADDRESS>
For d1
vagrant ssh d1
docker swarm init --listen-addr <IP_ADDRESS>  --advertise-addr <IP_ADDRESS>

Copy and paste the how to join masters
For d2
docker swarm join --token TOKEN --advertise-addr <IP_ADDRESS> --listen-addr <IP_ADDRESS> <IP_ADDRESS>:2377
For d3
docker swarm join --token TOKEN --advertise-addr <IP_ADDRESS> --listen-addr <IP_ADDRESS> <IP_ADDRESS>:2377
Net
I don't know if this is really necessary
docker network create --driver=overlay mynet
Service creation
I used grafana and Influxdb because that was what I wanted to test, I guess it'd do the same with any other container
Grafana
docker service create --name=grafana --network mynet -p 3000:3000 --mount type=bind,source=/media/fileserver/grafana,destination=/var/lib/grafana grafana/grafana
InfluxDB
docker service create --replicas 1 --network mynet --name influxdb -p 8083:8083 -p 8086:8086 -p 2004:2004 --mount type=bind,source=/media/fileserver/,destination=/media/fileserver/ --mount type=bind,source=/media/fileserver/influxdb.conf,destination=/etc/influxdb/influxdb.conf:ro  influxdb:0.13 -config /etc/influxdb/influxdb.conf

After I recreated the VMs from scratch using 1.12.0, I can't ping or wget from machine to machine. The DNS does not resolve to anything.
Furthermore, now I can't access the exposed ports in ANY host. Before I could access the container port from the host it was running on (and only that one). Now, I can't access it from outside.
Thanks for any help!

I redid all my install and now I can use the container port from the host it is running on. Trying to access on another master does not work.

I redid all my install and now I can use the container port from the host it is running on. Trying to access on another master does not work.

Changed the base os to CentOS 7. Here this works. Should I create a separate issue for this?

with docker 1.12 in CentOS 7 this problem has been solved

@upccup did you update CentOS, or docker? What were you running before?

@thaJeztah  Yes i update docker from 1.12rc4 to 1.12

Closing this issue, as it is resolved in 1.12.0

It's still broken on Debian. Follow my setup.
El 04/08/2016 05:45, "Sebastiaan van Stijn"<EMAIL_ADDRESS>escribió:

Closed #24679 https://github.com/docker/docker/issues/24679.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/issues/24679#event-744970941, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAHVzs-oanEdbFYElxJLER-OtEi_KmY8ks5qcaafgaJpZM4JNRxR
.

@Ismael sorry, I interpreted your previous comment as "it's resolved"; could you also provide docker info and docker version of a machine in your setup?

I don't know what happened that it can't establish the leader
now  (probably dchp expired the leases, this was a test setup after all).
Anyhow, I'm personally not interested in this issue anymore. Docker swarm
is too early too consider for production. I'm gonna try Kubernetes instead.
My replication steps should suffice to help you reproduce the bug, as it
only depends on having vagrant running.
Hope that helps you, sorry.
'
vagrant@d1:~$ docker info
Containers: 1
Running: 0
Paused: 0
Stopped: 1
Images: 1
Server Version: 1.12.0
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 5
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host null overlay
Swarm: pending
NodeID: 9qrv3etcy4970myhgnksmp3cz
Error: rpc error: code = 2 desc = raft: no elected cluster leader
Is Manager: true
ClusterID:
Managers: 0
Nodes: 0
Orchestration:
Task History Retention Limit: 0
Raft:
Snapshot interval: 0
Heartbeat tick: 0
Election tick: 0
Dispatcher:
Heartbeat period: Less than a second
CA configuration:
Expiry duration: Less than a second
Node Address: <IP_ADDRESS>
Runtimes: runc
Default Runtime: runc
Security Options:
Kernel Version: 3.16.0-4-amd64
Operating System: Debian GNU/Linux 8 (jessie)
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 1000 MiB
Name: d1
ID: 6RMK:MRSS:V577:ZGMC:ONII:OBR3:GLNQ:7HLJ:IEWB:JF23:24ZX:UPXC
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No memory limit support
WARNING: No swap limit support
WARNING: No kernel memory limit support
WARNING: No oom kill disable support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
Insecure Registries:
<IP_ADDRESS>/8
'
'
vagrant@d1:~$ docker version
Client:
Version:      1.12.0
API version:  1.24
Go version:   go1.6.3
Git commit:   8eab29e
Built:        Thu Jul 28 21:40:59 2016
OS/Arch:      linux/amd64
Server:
Version:      1.12.0
API version:  1.24
Go version:   go1.6.3
Git commit:   8eab29e
Built:        Thu Jul 28 21:40:59 2016
OS/Arch:      linux/amd64
'
On Thu, Aug 4, 2016 at 10:30 AM, Sebastiaan van Stijn <
<EMAIL_ADDRESS>wrote:

Reopened #24679 https://github.com/docker/docker/issues/24679.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/issues/24679#event-745271585, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAHVzgqd1h1oT3on5Y7qa8VtZ2RAF8jQks5qcelpgaJpZM4JNRxR
.

Does this relate to the issue reported here?:
https://forums.docker.com/t/interconnecting-services-in-1-12-swarm-mode-nginx-in-front-of-elastic/18583
Crate.io has the same problem as Elastic, our nodes are incapable of communication with each other since 1.12 rc4 (and including 1.12.0). Exactly as is described in the forum post I have linked above.

This is an old issue.  I will close it as stale.


updating circom version to v2.2.1

This PR updated the circom version to v2.2.1 for https://github.com/hyperledger-labs/zeto/issues/100:

Increased PTAU size to adopt the default fast simplification as it significantly reduces the circuit compilation time. More details here: https://github.com/iden3/circom/blob/master/mkdocs/docs/circom-language/circom-insight/simplification.md
fixed the types of several test data for stricter type check
updated gen.js concurrency to avoid overloading the CPU which makes the compiling less efficient

using fast simplification, the circuit asset generation reduced from 42 mins to 18 mins:
before:

this PR:


Rewritten in JavaScript and HTML

I've completely rewritten this code from GO to a simple web page (JS+HTML) that allows drawing and generating profiles STL's.

Wow, thank you so much. I will looking over the code later today.

Hi ValkA. I merged but I am running into issues with this code.

The pattern is not flat. It seems to have an unwanted Z dimension:

The pattern does not seem to complete a full circle:

I think there is an issue with the stl writer since I cannot import into Sketchup. What program have you been importing them into?


chore(main): release 1.1.1

:robot: I have created a release beep boop
1.1.1 (2023-01-27)
update

更新频道编辑 (846cf4a)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/School-of-Website-Engineering/Heimatoutiao/releases/tag/v1.1.1 :sunflower:


feat(library): add new property _title for sources data

:tada: This PR is included in version 3.15.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


add undefined to build package types

one for the wishlist @aomarks

undefined isn't doesn't exist in JSON. We could do null, and there's also the concept of optional properties. We probably want both of those, but do you have a specific use case to pick one or the other?

the specific case this time is in the pop node again. Where the return can be an item of undefined.

This has just made me think of another case, const in JSON Schema.

I think we want all input/output values to be JSON serializable, probably. So, since undefined isn't, we may want to use null instead for the pop node. (So I think we should add null to the type system).

I just landed https://github.com/breadboard-ai/breadboard/pull/1231 which will ensure that we only return JSON serializable types from our nodes.
BTW, the main reason I think we want every value to be JSON serializable is so that we can easily support save/restore of runs.


Forks and data corruption

I recently had data corruption which I traced to the fact that, when a Highland stream is forked, all consumers are sent the exact same Buffer. I was passing the forked streams through a transform which was modifying the Buffer; one fork would modify the data and the other fork would receive (from Highland) the now-corrupt data (related: https://github.com/mafintosh/csv-parser/pull/60).
Is this something that should be addressed within Highland? Highland can clone the Buffer once per consumer (+per observer) and send out those copies, though I guess this will inflate memory usage. IMO it's bad form for a fork consumer to directly modify the passed Buffer, but arguably Highland should still offer some guarantee that all forks receive the same data.
Demonstration:
'use strict';
const highland = require('highland');

const input = highland([new Buffer(':)')]);
const fork1 = input.fork();
const fork2 = input.fork();

fork1.each(
  (x) => {
    console.log('fork 1:', x.toString());
    x[1] = '('.charCodeAt(0);
  }
);

fork2.each(
  (x) => {
    console.log('fork 2:', x.toString());
  }
);

Output:
fork 1: :)
fork 2: :(

Although this example uses a Buffer explicitly passed into a Highland constructor, the situation is the same when we are forking a "real" stream, like a download.

I'm -1 on this. Highland should not be in the business of sniffing its value types and applying special logic to certain cases. It gets hairy fast. If we do it for Buffer, then people will want us to do it for arrays or any number of mutable types. And that's not getting into cases like nested data (what if you're passing around a {foo: new Buffer()} rather than a Buffer) or memory usage (people not modifying their Buffers should not have to pay for the allocations).
Highland offers the guarantee that all forks receive the same value. It does not (and in the general case cannot) guarantee that the contents and behavior of said value will not change as the forks execute.
If you need to clone the data, you should do it immediately after the fork()
...
const fork1 = input.fork().map(Buffer.from);
const fork2 = input.fork().map(Buffer.from);
...

or before you modify.

Thanks for the quick response. You make several good points as to why this should not be Highland's responsibility, and I have to agree with you.
Nevertheless, the behavior I described is surprising, particularly when one is forking a readable stream. There's an expectation that that data would be immutable, inert; obviously it's not necessarily the case, and I agree that it's not on Highland to solve that. Maybe this warrants mentioning on the documentation for fork.


JobSchedule check

Hello, Is there any check to confirm if the Job is scheduled or not?
eg: dispatcher.isScheduled(TAG);

Hi Darshan,
Unfortunately there is not such check.
However we plan to implement the this in the future.
For now you can use "adb shell dumpsys activity service GcmService --endpoints YOUR_SERVICE".
You should not rely on the output because in will change in the future.
Thanks,
Egor


wip: Add yngping underlying to index

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Default Eviction strategy

How much data it can store? What happens to extra data when we are trying to store it (extra than maximum storeage)?

Please refer to the documentation, particularly Increase Async Storage size.


Use a captive portal to ease access to ideascube.lan or koombook.lan

Many users are connecting through their own device, thus don't know how to connect to our server.
Second, using .lan extension is chromium address bar will launch a google search instead of connecting to the server (need to explicitly type http:// -_-).
Using a captive portal forcing first connection to ideascube.lan would be a nice solution. But, notice that only first connection must be redirected. After some talking, best way seems to use iptables DNAT to redirect and then, when first connection is made, add source MAC address to an iptables white list.
Using conntrack may be a nice solution to keep white list up to date, as we'd like user to go back to ideascube.lan if browser is closed and reopened again.

In progress PR #72

PR #72 has been merged


chore(input): switch to OnPush change detection

Switches the MdInputContainer to OnPush change detection and sorts out the various change detection-related issues.
Relates to #5035.

Addressed the feedback @jelbourn.
@willshowell if nothing else, #5660 still provides some value by adding the extra unit test.

@crisbeto looks to be a few lint errors

@crisbeto Rebase?

Rebased.


update request dependency

To avoid outdated bluebird dependency.
├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   └─┬<EMAIL_ADDRESS>│     └─┬<EMAIL_ADDRESS>│       └──<EMAIL_ADDRESS>

Thanks, sorry for the delay merging this.


SSL error possibly when trying to connect to remote bot

When trying to connect to my remote bot using the bot framework emulator.

write EPROTO<PHONE_NUMBER>71200:error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error:../../vendor/node/deps/openssl/openssl/ssl/s23_clnt.c:769:

Here is a screenshot of the log:

I am using Bot Framework Emulator 3.5.31 on a Mac OSX Sierra 10.12.6

Looking at your log, there are a few things going on:

It looks like your bot is running remotely, but ngrok isn't configured or running. This configuration means your bot will be able to receive messages from you, but the emulator will not be able to receive replies from the bot. This can be remedied by installing ngrok and configuring it in App Settings.
As you said, something about SSL is unhappy. This is one of the most intractable issues that our users encounter. Things you can try:

If the bot endpoint you specified in the emulator is using https, switch it to http (only in the emulator, not your bot)
Conversely, switch it to https if using http. (Weird, I know.)
If you have a network admin or IT department, engage with them to troubleshoot network configuration.

Closing due to inactivity.


Multiple fit_items without all having 'affected'

Heya Frank,
I stumbled across this while trying to implement parameter estimation for shared and non-shared experiments.
When I run something like:
fit_items = [
    {'name': "Values[k_on]", 'lower': 1e05, 'upper': 1e09, 'affected': [exp_name]},
    {"name": "Values[k_off]", 'lower': 1e-05, 'upper': 1e04}
]

bsc.set_fit_parameters(fit_items)

It happens whenever the 'affected' key is present in one but not all of the fit_items dictionaries. Then I get a type error: TypeError: 'float' object is not iterable.
I think this happens because when _set_fit_item function tries to iterate through the affected variable but the 'affected' is actually a NaN value, so seen as a float in the error. I think this may happen because pandas fills in blanks as NaN with line 757 in the set_fit_parameters function: fit_parameters = pandas.DataFrame(data=fit_parameters). Hope any of that is helpful.
Otherwise, it's a pretty avoidable I think as I can just put an empty list probably.
Thanks,
Theo

release 0.67 ignores nan values in there and is now available on pypi. Thanks again for reporting.


Support building with base-4.19.* (GHC 9.8)

I tried bumping the upper version bounds on base to allow this:
diff --git a/kvitable.cabal b/kvitable.cabal
index 9c551ad..565c5f8 100644
--- a/kvitable.cabal
+++ b/kvitable.cabal
@@ -53,7 +53,7 @@ library
                      , Data.KVITable.Render.ASCII
                      , Data.KVITable.Render.HTML
   -- other-modules:
-  build-depends:       base >=4.12 && <4.19
+  build-depends:       base >=4.12 && <4.20
                      , containers
                      , lucid  >= 2.9 && < 2.12
                      , microlens >= 0.4 && < 0.5

But this results in a volley of -Wx-partial warnings:
$ cabal build -w ghc-9.8
Resolving dependencies...
Build profile: -w ghc-9.8.1 -O1
In order, the following will be built (use -v for more details):
 - kvitable-<IP_ADDRESS> (lib) (first run)
Configuring library for kvitable-<IP_ADDRESS>..
Preprocessing library for kvitable-<IP_ADDRESS>..
Building library for kvitable-<IP_ADDRESS>..
[1 of 4] Compiling Data.KVITable
[2 of 4] Compiling Data.KVITable.Render
[3 of 4] Compiling Data.KVITable.Render.ASCII

src/Data/KVITable/Render/ASCII.hs:84:26: warning: [GHC-63394] [-Wx-partial]
    In the use of ‘head’
    (imported from Prelude, but defined in GHC.List):
    "This is a partial function, it throws an error on empty lists. Use pattern matching or Data.List.uncons instead. Consider refactoring to use Data.List.NonEmpty."
   |
84 |            l = sig sep $ head vals
   |                          ^^^^

src/Data/KVITable/Render/ASCII.hs:126:59: warning: [GHC-63394] [-Wx-partial]
    In the use of ‘head’
    (imported from Prelude, but defined in GHC.List):
    "This is a partial function, it throws an error on empty lists. Use pattern matching or Data.List.uncons instead. Consider refactoring to use Data.List.NonEmpty."
    |
126 |     lastFmt = if null hrows then fmtLine [] else hdrFmt $ head $ reverse hrows
    |                                                           ^^^^

src/Data/KVITable/Render/ASCII.hs:170:48: warning: [GHC-63394] [-Wx-partial]
    In the use of ‘head’
    (imported from Prelude, but defined in GHC.List):
    "This is a partial function, it throws an error on empty lists. Use pattern matching or Data.List.uncons instead. Consider refactoring to use Data.List.NonEmpty."
    |
170 |       szexts = let subVW = fmtWidth . hdrFmt . head
    |                                                ^^^^

src/Data/KVITable/Render/ASCII.hs:173:71: warning: [GHC-63394] [-Wx-partial]
    In the use of ‘head’
    (imported from Prelude, but defined in GHC.List):
    "This is a partial function, it throws an error on empty lists. Use pattern matching or Data.List.uncons instead. Consider refactoring to use Data.List.NonEmpty."
    |
173 |                                               fmtEmptyCols $ hdrFmt $ head sh
    |                                                                       ^^^^

src/Data/KVITable/Render/ASCII.hs:224:78: warning: [GHC-63394] [-Wx-partial]
    In the use of ‘head’
    (imported from Prelude, but defined in GHC.List):
    "This is a partial function, it throws an error on empty lists. Use pattern matching or Data.List.uncons instead. Consider refactoring to use Data.List.NonEmpty."
    |
224 |                           then let subl = [ (True, replicate (length $ snd $ head subs) Separator) ]
    |                                                                              ^^^^
[4 of 4] Compiling Data.KVITable.Render.HTML

src/Data/KVITable/Render/HTML.hs:138:33: warning: [GHC-63394] [-Wx-partial]
    In the use of ‘head’
    (imported from Prelude, but defined in GHC.List):
    "This is a partial function, it throws an error on empty lists. Use pattern matching or Data.List.uncons instead. Consider refactoring to use Data.List.NonEmpty."
    |
138 |         (HdrLine fmt vals tr) = head nexthdrs -- safe: there were keys
    |                                 ^^^^

src/Data/KVITable/Render/HTML.hs:141:43: warning: [GHC-63394] [-Wx-partial]
    In the use of ‘tail’
    (imported from Prelude, but defined in GHC.List):
    "This is a partial function, it throws an error on empty lists. Replace it with drop 1, or use pattern matching or Data.List.uncons instead. Consider refactoring to use Data.List.NonEmpty."
    |
141 |     in ( (HdrLine fmt' (val : vals) tr) : tail nexthdrs
    |                                           ^^^^

src/Data/KVITable/Render/HTML.hs:169:52: warning: [GHC-63394] [-Wx-partial]
    In the use of ‘head’
    (imported from Prelude, but defined in GHC.List):
    "This is a partial function, it throws an error on empty lists. Use pattern matching or Data.List.uncons instead. Consider refactoring to use Data.List.NonEmpty."
    |
169 |                 else L.replicate (length titles) $ head subTtlHdrs
    |                                                    ^^^^

src/Data/KVITable/Render/HTML.hs:171:33: warning: [GHC-63394] [-Wx-partial]
    In the use of ‘head’
    (imported from Prelude, but defined in GHC.List):
    "This is a partial function, it throws an error on empty lists. Use pattern matching or Data.List.uncons instead. Consider refactoring to use Data.List.NonEmpty."
    |
171 |       joinHdrs hl = foldl (<>) (head hl) (tail hl)
    |                                 ^^^^

src/Data/KVITable/Render/HTML.hs:171:43: warning: [GHC-63394] [-Wx-partial]
    In the use of ‘tail’
    (imported from Prelude, but defined in GHC.List):
    "This is a partial function, it throws an error on empty lists. Replace it with drop 1, or use pattern matching or Data.List.uncons instead. Consider refactoring to use Data.List.NonEmpty."
    |
171 |       joinHdrs hl = foldl (<>) (head hl) (tail hl)
    |                                           ^^^^

It's not immediately clear to me what the best way to resolve these warnings would be.

Thanks for the report.  I'll try to resolve these but it may be a couple of days before I have time to work on this.

Fixed and released on Hackage as v<IP_ADDRESS>


Typescript types

Currently converting Jest to TypeScript, so we need this module to be typed. Can submit to DefinitelyTyped, but would be better if it was in this repo 🙂

Codecov Report

Merging #52 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #52   +/-   ##
=======================================
  Coverage   71.11%   71.11%
=======================================
  Files           1        1
  Lines          45       45
  Branches       16       16
=======================================
  Hits           32       32
  Misses          5        5
  Partials        8        8

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 9ea29f1...a6f40c5. Read the comment docs.

:tada: This PR is included in version 4.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


chore(deps): patch release via chore

GH-27
Description
When dependencies are updated using chore as the type a patch version will be released
Fixes #27
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Intermediate change (work in progress)

Checklist:

[x] Performed a self-review of my own code
[x] npm test passes on your machine
[ ] New tests added or existing tests modified to cover all changes
[ ] Code conforms with the style guide
[ ] API Documentation in code was updated
[ ] Any dependent changes have been merged and published in downstream modules

:tada: This PR is included in version 3.1.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Cookies set in the response of a custom rest API are not stored in browser

Before opening, please confirm:

[X] I have searched for duplicate or closed issues and discussions.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

JavaScript Framework
React
Amplify APIs
REST API
Amplify Categories
api
Environment information

# Put output below this line
  System:
    OS: Windows 10 10.0.19042
    CPU: (4) x64 Intel(R) Core(TM) i7-6650U CPU @ 3.20GHz
    Memory: 4.53 GB / 15.92 GB
  Binaries:
    Node: 12.16.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.4 - C:\Fitoo\web-app\node_modules\.bin\yarn.CMD
    npm: 7.16.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 94.0.4606.81
    Edge: Spartan (44.19041.1266.0), Chromium (95.0.1020.30)
  npmGlobalPackages:
    @angular/cli: 9.0.5
    @aws-amplify/cli: 6.3.1
    @ionic/cli: 6.17.1
    amplify-category-video: 3.9.1
    amplify-cli: 1.0.0
    amplify-slow-table-create: 1.0.0
    bootstrap: 4.3.1
    bower: 1.8.8
    eslint-plugin-unused-imports: 1.1.1
    eslint: 7.23.0
    expo-cli: 4.1.0
    generator-aspnet-spa: 0.1.3
    generator-aspnetcore-spa: 1.0.0
    grunt: 1.0.4
    json-server: 0.14.2
    n: 2.1.11
    native-run: 1.5.0
    node: 13.10.1
    npm: 7.16.0
    redis-cli: 1.4.0
    stable: 0.1.8
    typescript: 3.6.3
    webpack: 2.6.1
    windows-build-tools: 5.0.0
    wscat: 2.2.1
    yarn: 1.22.10
    yo: 2.0.2

Describe the bug
I am trying to control who can access my content using cloudfront signed cookies (I am aware of signed urls and it does not work for me as I need to support iOS/Safari). Every required component from s3, cloudfront, api gateway to token generator function are implemented and tested. The only issue that I am facing right now is getting the browser to store the cookies.
The Cloudfront and the api gateway have  custom domains (cdn.mydomain.com) and (api.mydomain.com) respectively. When the calls are intercepted (using postman) I can confirm that the right cookies are returned and when attached to the call to the cdn I get 200 (using postman). However, in browser, I need to use amplify API library to make the call to the api. To set a cookie with CORS, I need to set withCredentials  flag when making the request.
    await API.post("myapi", "/xxxx", {
      headers: {
        withCredentials: "true"
      },
      body: { content },
    })

But I keep getting the following error (if I dont add withCredentials header. I get 200 but the cookies are not stored)
Access to XMLHttpRequest at 'https://api.mydomain.com/xxxx' from origin 'http://localhost:3000' has been blocked by CORS policy: Request header field withcredentials is not allowed by Access-Control-Allow-Headers in preflight response.

I have tried to add the header to allowed headers in the api gateway integration (CloudFormation)
"x-amazon-apigateway-integration": { 									"responses": { 										"default": { 											"statusCode": "200", 											"responseParameters": { 												"method.response.header.Access-Control-Allow-Methods": "'DELETE,GET,HEAD,OPTIONS,PATCH,POST,PUT'", 												"method.response.header.Access-Control-Allow-Headers": "'<<<HERE>>>>,Content-Type,X-Amz-Date,Authorization,X-Api-Key,X-Amz-Security-Token,X-Amz-User-Agent'", 												"method.response.header.Access-Control-Allow-Origin": "'*'" 											} 										} 									},
my function uses express. CORS is enabled and headers are handled accordingly
app.use(function (request, res, next) {
  const allowedOrigins = ['http://localhost:3000', 'xxxxxxxx'];
  const origin = request.headers.origin;
  if (allowedOrigins.includes(origin)) {
    res.setHeader('Access-Control-Allow-Origin', origin);
  }
  res.header('Access-Control-Allow-Headers', '*');
  res.header('Access-Control-Allow-Credentials', 'true');
  res.header('Access-Control-Allow-Methods', 'GET,HEAD,OPTIONS,POST,PUT');
  //intercept the OPTIONS call so we don't double up on calls to the integration
  if ('OPTIONS' === request.method) {
    res.send(200);
  } else {
    next();
  }
});

But no success. It is very frustrating and any help would be very appreciated.
Expected behavior
When calling api with credentials, the cookies to be set and stored in the browser and consequently being able to call the cloudfront and get 200 response.
Reproduction steps
Create a rest api using amplify
use express with api gateway integration
Enable Cors as follows:
// Enable CORS for all methods
app.use(function (request, res, next) {
  const allowedOrigins = ['http://localhost:3000', 'xxxx'];
  const origin = request.headers.origin;
  if (allowedOrigins.includes(origin)) {
    res.setHeader('Access-Control-Allow-Origin', origin);
  }
  res.header('Access-Control-Allow-Headers', '*');
  res.header('Access-Control-Allow-Credentials', 'true');
  res.header('Access-Control-Allow-Methods', 'GET,HEAD,OPTIONS,POST,PUT');
  //intercept the OPTIONS call so we don't double up on calls to the integration
  if ('OPTIONS' === request.method) {
    res.send(200);
  } else {
    next();
  }
});

Set response cookies as follows:
app.post('/xxx', async (req, res) => {
  const cookies = await signPath(req.body.content);
  Object.keys(cookies).map((cookieName) => {
    res.cookie(cookieName, cookies[cookieName], { path: "/", domain: ".mydomain.com", sameSite: "None", secure: true });
  })
  res.json({ body })
});

Call the API and check if the browser stores the returned cookies in response
P.s. This could very much be a CLI issue.

Hey @pedramp20 :wave: thanks for raising this! I noticed withCredentials is being placed in the request's headers, but does this work with withCredentials outside of the headers? (This may not be required if we are calling this API from the same domain)
await API.post("myapi", "/xxxx", {
  withCredentials: true,
  body: { content },
})

For reference, the REST API module uses axios under the hood.


[MaaS] swift-recon.py plugin runs swift-recon locally

Do NOT include any confidential information, this issue will be created on a public repo
This section is completed by the issue reporter
On which version(s) do you encounter this issue?
Please provide the output to 'git describe --all' for  all deployments where you have confirmed it occurs.
What type of issue is this? Please tick the appropriate box.

[x] bug - existing functionality that does not work for you as documented
[ ] feature - new functionality that you would like to see added

What is the expected behavior?
The swift-recon.py plugin doesn't try to invoke swift-recon on the infra hosts.
What is actually happening?
After running the setup-maas.yml playbook, I noticed that the swift-recon checks are being dropped in my infra hosts:
root@568575-infra01:/opt/rpc-openstack/rpcd/playbooks# ls /etc/rackspace-monitoring-agent.conf.d/ | grep swift
filebeat_process_check-568575-infra01_swift_proxy_container-65b24edd.yaml
lb_api_check_swift_access.yaml
lb_api_check_swift_healthcheck.yaml
swift_account_replication_check--568575-infra01_swift_proxy_container-65b24edd.yaml
swift_async_check--568575-infra01_swift_proxy_container-65b24edd.yaml
swift_container_replication_check--568575-infra01_swift_proxy_container-65b24edd.yaml
swift_md5_check--568575-infra01_swift_proxy_container-65b24edd.yaml
swift_object_replication_check--568575-infra01_swift_proxy_container-65b24edd.yaml
swift_proxy_server_check--568575-infra01_swift_proxy_container-65b24edd.yaml
swift_quarantine_check--568575-infra01_swift_proxy_container-65b24edd.yaml
swift_time_sync_check--568575-infra01_swift_proxy_container-65b24edd.yaml

The current swift_recon.py maas plugin is trying to invoke the swift-recon executable on the host it's running on. That can be seen here:
https://github.com/rcbops/rpc-openstack/blob/newton-14.0/rpcd/playbooks/roles/rpc_maas/files/plugins/swift-recon.py#L65-L67
The result of this is that we now have failing checks on the infra hosts since the infra hosts aren't running swift binaries. cc @xeregin
What were you attempting to do when you encountered this error (give as much detail as possible)?
We ran setup-maas.yml on our multi-node lab for QE testing after blowing away all of the content in /etc/rackspace-monitoring-agent.conf/*. We noticed that the swift recon checks are also being dropped into this directory on our infra hosts.
How can we reproduce this issue?
See above.
How can we verify your issue is addressed?
The swift-recon.py plugin runs successfully.
If you are using or know of a workaround please describe the necessary steps?
NA
What is your evaluation on the importance of this issue, and why?
prio-1. This should be fixed before our Newton rc1 release.
This section is completed during the issue resolution process. If you are reporting an issue, please do not modify the section below.
Which branches are impacted by this issue?
Remove branches that are not impacted.
For each pull request, update the branch line to reference it.

[x] master
[x] newton-14.0
[ ] mitaka-13.1
[ ] liberty-12.2

Upgrade impact. Consider the impact on moving between major, minor and patch releases.

[x] This change does not impact upgrades
[ ] This change addresses a potential upgrade impact
[x] The upgrade impact is being tracked by another issue.

The issue tracking the upgrade impact is:
Testing impact

[ ] An issue/pull-request has been create or exists to track the testing gap, and is referenced below
[ ] This change includes additional testing
[x] This change is tested by the existing setup

Additional testing links:
Release note

[ ] This change includes a release note.
[x] This change does not require a release note.

Doc Impact
Does your change require documentation?

[ ] Yes, and I submitted an issue to Docs issues
[ ] Yes, and I contributed a documentation patch to docs-rpc
[x] No documentation required for this change

Additional documentation links (please add links if you have ticked yes):

I think the problem here is that we are writing out the compound conditional expression here as a yaml list, which munges the expressions together with an 'OR':
https://github.com/rcbops/rpc-openstack/blob/newton-14.0/rpcd/playbooks/roles/rpc_maas/tasks/main.yml#L80-L82
Of course the first conditional, groups['swift_all'] | length > 0 will be true for every hosts on an environment with swift deployed.
That conditional needs to be fixed to use an AND operator.

IGNORE MY LAST COMMENT!
Turns out that conditional is correct the way it is. I suspect the problem is that these checks are being dropped into the infra hosts via delegation. Note in this Ansible output:
changed: [568575-infra01_swift_proxy_container-65b24edd -> <IP_ADDRESS>] => (item={u'group': u'swift_proxy', u'name': u'swift_quarantine_check'})

The task is being delegated over to <IP_ADDRESS>(infra1), which is the physical host of the swift proxy container. The delegation is being done here:
https://github.com/rcbops/rpc-openstack/blob/newton-14.0/rpcd/playbooks/roles/rpc_maas/tasks/ensure_local_checks.yml#L28
Dropping this check into the infra hosts is a problem, since the current swift_recon.py maas plugin is trying to invoke the swift-recon executable on the host it's running on. That can be seen here:
https://github.com/rcbops/rpc-openstack/blob/newton-14.0/rpcd/playbooks/roles/rpc_maas/files/plugins/swift-recon.py#L65-L67
The only way I can see of solving this is writing bits into the swift-recon.py plugin to run the swift-recon command on a remote server(i.e. the swift proxy container). I say this because, AFAIK, these plugins can only run on a host with the maas agent on them -- the physical hosts.
It'll also be possible to run the swift-proxy command using 'lxc-attach', or some other container connection python module, but either way it'll still require the swift_recon.py maas plugin to change.
cc @antonym @major @cloader89

So I have what seems like a simple question. How did we make it this far into a bunch of AIO deployments without seeing this? Are we not deploying Swift in our AIOs? IS this error not happening in gating with Swift turned on?
It seems strange to see this rather late in the process. It's not like we just added Swift and Swift MaaS checks last week.

@claco: I was thinking about that too. I would like to investigate some of the multi-node AIOs that @mkam is working with to see if it's happening there.
The reason it wasn't caught in palin-old regular AIO is because the swift object-server runs on the host on AIO deployments, causing the plugin to succeed.
Still, I would like to figure out why the multi-node AIO isn't catching this.

FYI - I'm backporting this to newton. I'll leave the other backports to @antonym.

Backported this to Mitaka and Liberty, but they break as the release number does not line up to {{ rpc_release }} (DISTRIB_RELEASE).  The script currently grabs the version from /etc/rpc-release.
Example:
Kilo: No venvs so I'll need to adjust appropriately
Liberty: DISTRIB_RELEASE="r12.2.8", {{ openstack_release }} = "12.2.8"
Mitaka: DISTRIB_RELEASE='"r13.1.4", {{ openstack_release }} = "13.3.15"
I guess that behavior changed here: https://github.com/rcbops/rpc-openstack/commit/36cb8bea267999f54d69bbcb91c3877e7c4f225e so going forward it should be more consistent.
It looks like if I grab DISTRIB_RELEASE from /etc/openstack-release instead of /etc/rpc-release, it's more consistent across all releases and this issue goes away.

It looks like if I grab DISTRIB_RELEASE from /etc/openstack-release instead of /etc/rpc-release, it's more consistent across all releases and this issue goes away.

That's a solid change for the <= Mitaka backports. I don't think it's a necessary one for the newton release though.

Yeah, your call, this is my proposed patch which would work for all except Kilo:
https://github.com/rcbops/rpc-openstack/pull/2023

Let's go ahead and get that patch into all of the branches before mitaka, then. Or you could modify the backport PRs you already have open and make a note in the commit message.
The newton PR can stay using /etc/rpc-release.


[Bug] grant_access_to doesn't seem to work for materialized views

Is this a new bug in dbt-bigquery?

[X] I believe this is a new bug in dbt-bigquery
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
We currently grant access to views with this config:
salesforce:
  +grant_access_to:
    - project: data-lake
      dataset: salesforce

Which works well for views. Now we're transitioning to using materialized views, which doesn't seem to trigger the authorization.
Expected Behavior
I expect views and materialized views to work the same, in the UI there's no discernible difference when granting access, the API seems to be the same.
Steps To Reproduce

Create a source dataset with a table
Create a target model in another dataset, materialized as a materialized view
In the target model, add config to grant access to the source dataset.
Run the models
Check if materialized view is listed under authorized views on the source dataset

Relevant log output
No response
Environment
- OS: Debian 12
- Python: Python 3.9.18
- dbt-core: 1.7.6
- dbt-bigquery: 1.7.6

Additional Context
No response

Materialized views don't currently support grant_access_to, though that would definitely be useful. I'm going to update this to a feature request so that it can be prioritized against the feature backlog.

so this chunk of code in dbt-bigquery's view materialization will need to somehow make it into the "materialized_view" materialization.
https://github.com/dbt-labs/dbt-bigquery/blob/955afbd74b19d37f6c7919a4a92dd2cc50eae905/dbt/include/bigquery/macros/materializations/view.sql#L21-L25

so this chunk of code in dbt-bigquery's view materialization will need to somehow make it into the "materialized_view" materialization.
https://github.com/dbt-labs/dbt-bigquery/blob/955afbd74b19d37f6c7919a4a92dd2cc50eae905/dbt/include/bigquery/macros/materializations/view.sql#L21-L25

Presumably? I'd need to look more into it. And then we would want a test or two for it as well, and we'd need to update the docs.


iOS build fails with new arch enabled

I have this library installed as a dependency of https://github.com/gev2002/react-native-vision-camera-image-labeler. I have the following package versions:
"react-native-vision-camera": "^4.5.2",
"react-native-vision-camera-image-labeler": "^2.2.0",
"expo": "^51.0.31",
"react-native": "0.74.5",

If I disable the new architecture, my project builds successfully. However, if I enable the new architecture and run eas build, I get the following error:
[INSTALL_PODS] [!] The following Swift pods cannot yet be integrated as static libraries:
[INSTALL_PODS] The Swift pod `VisionCamera` depends upon `react-native-worklets-core`, which does not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set `use_modular_headers!` globally in your Podfile, or specify `:modular_headers => true` for particular dependencies.
[INSTALL_PODS] [!] [Codegen] warn: using experimental new codegen integration
[INSTALL_PODS] [!] `<PBXResourcesBuildPhase UUID=`13B07F8E1A680F5B00A75B9A`>` attempted to initialize an object with an unknown UUID. `A67C1F8C08C340EF9D61287B` for attribute: `files`. This can be the result of a merge and the unknown UUID is being discarded.
[INSTALL_PODS]
Error: pod install exited with non-zero code: 1
    at ChildProcess.completionListener (/Users/stevengoldberg/.npm/_npx/5e31c5d24a898acf/node_modules/@expo/spawn-async/build/spawnAsync.js:42:23)
    at Object.onceWrapper (node:events:629:26)
    at ChildProcess.emit (node:events:514:28)
    at maybeClose (node:internal/child_process:1091:16)
    at ChildProcess._handle.onexit (node:internal/child_process:302:5)
    ...
    at spawnAsync (/Users/stevengoldberg/.npm/_npx/5e31c5d24a898acf/node_modules/@expo/spawn-async/build/spawnAsync.js:7:23)
    at spawn (/Users/stevengoldberg/.npm/_npx/5e31c5d24a898acf/node_modules/@expo/turtle-spawn/dist/index.js:16:47)
    at installPods (/Users/stevengoldberg/.npm/_npx/5e31c5d24a898acf/node_modules/@expo/build-tools/dist/ios/pod.js:12:50)
    at runInstallPodsAsync (/Users/stevengoldberg/.npm/_npx/5e31c5d24a898acf/node_modules/@expo/build-tools/dist/builders/ios.js:200:70)
    at /Users/stevengoldberg/.npm/_npx/5e31c5d24a898acf/node_modules/@expo/build-tools/dist/builders/ios.js:74:19
    at BuildContext.runBuildPhase (/Users/stevengoldberg/.npm/_npx/5e31c5d24a898acf/node_modules/@expo/build-tools/dist/context.js:107:34)
    at buildAsync (/Users/stevengoldberg/.npm/_npx/5e31c5d24a898acf/node_modules/@expo/build-tools/dist/builders/ios.js:73:19)
    at async runBuilderWithHooksAsync (/Users/stevengoldberg/.npm/_npx/5e31c5d24a898acf/node_modules/@expo/build-tools/dist/builders/common.js:12:13)
    at async Object.iosBuilder (/Users/stevengoldberg/.npm/_npx/5e31c5d24a898acf/node_modules/@expo/build-tools/dist/builders/ios.js:33:16)
    at async buildIosAsync (/Users/stevengoldberg/.npm/_npx/5e31c5d24a898acf/node_modules/eas-cli-local-build-plugin/dist/ios.js:41:12)
[CLEAN_UP_CREDENTIALS] Destroying keychain - /var/folders/l4/03vzqz3d0y1bbtryk8ckdhvw0000gn/T/eas-build-f948fd61-26a7-4145-bdd2-dc7f30aeef86.keychain
[CLEAN_UP_CREDENTIALS] Removing provisioning profile

Build failed

Have the same problem on<EMAIL_ADDRESS>and<EMAIL_ADDRESS>Any progress on this issues?

Same issue here building for new arch
"react-native": "0.75.3",
"react-native-vision-camera": "^4.5.3",
"react-native-worklets-core": "2.0.0-beta.1",
any update ?


Integrate question generator and QA pipeline

Integrate the question generator pipeline I built for the thesis and create a QA pipeline of a similar structure.

Completed this and now have both tools working (with bugs). Issues will be created to improve the tool calling capabilities since there are still some bugs where the bot incorrectly formats the tool call.


Add nupkg option to add database reference dialog

This PR adds the "Published data-tier application" option to the add database reference dialog, which allows for database references to .dacpacs in a NuGet package. The previous PRs https://github.com/microsoft/azuredatastudio/pull/22762 and https://github.com/microsoft/azuredatastudio/pull/22757 added the logic for doing this, so this PR only has the UI changes and hooking up to the previously added function calls.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

17 of 41 (41.46%)  changed or added relevant lines in 3 files are covered.
4 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.01%) to 41.745%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

extensions/sql-database-projects/src/controllers/projectController.ts
0
2
0.0%

extensions/sql-database-projects/src/dialogs/addDatabaseReferenceDialog.ts
13
35
37.14%

Files with Coverage Reduction
New Missed Lines
%

extensions/notebook/src/jupyter/serverInstance.ts
4
75.5%

Totals

Change from base Build<PHONE_NUMBER>:
-0.01%

Covered Lines:
30501

Relevant Lines:
67676

💛  - Coveralls


Add Adj*BQM::linear

Gives slightly nicer access to the linear biases in c++ BQMs. E.g.
bqm.linear(v) += 1;

rather than
bqm.set_linear(v, bqm_get_linear(v) + 1);

I would love to have bqm.quadratic(u, v) as well, but because we keep two copies of the bias around for quadratic, we can't just return a reference like we do with .linear. Open to suggestions.

Codecov Report

Merging #696 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #696   +/-   ##
=======================================
  Coverage   91.85%   91.85%
=======================================
  Files          60       60
  Lines        4222     4222
=======================================
  Hits         3878     3878
  Misses        344      344

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 b362847...2c447b8. Read the comment docs.

LGTM


Installation in Zotero 6 not working

I have tried to install the add-on, but I get the message: "The add-on "Better BibTex for Zotero" could not be installed. It may be incompatible with this version of Zotero."
Could you help me spot what is going wrong?
Add-on file: zotero-better-bibtex-6.7.19.xpi
See Zotero Debug file attached. D1298517107.txt

I think this issue was raised in https://github.com/retorquere/zotero-better-bibtex/issues/2243. Basically 6.0.3 doesn't work but if you can upgrade to 6.0.10 you should be fine.
(I just hit the same issue and this resolved it for me)

Indeed, thanks! I don't know why Manjaro didn't update Zotero automatically... I had to install 6.0.10 through another package zotero-bin.


Compilation error: main.go:36:35: undefined: assetFS

While trying to compile and install from source I got this error:
❯ GOBIN=/usr/local/bin/ go get github.com/egeozcan/json-tail
# github.com/egeozcan/json-tail
../../.cache/go/src/github.com/egeozcan/json-tail/main.go:36:35: undefined: assetFS

Hi, you need to clone the repo to build, because it needs to generate assets. You'll need node.js. I'll update the readme for detailed instructions and keep this issue open until I do.


DO NOT MERGE

Just to see the diff with v2.0.2 to help with writing release notes for 3.0

Do not work for unholy reasons ...


OAuth2/OpendID connect documentation: How to add multiple client_ids from same domain?

Issue
How to specify more than one client_id + client_secret, for members in the same domain?
Scenario
We want to be able to add multiple users from the same domain (OAuth2/OpenID Connect). In this particular case, I will be using google_oauth2.
Steps to reproduce
Inconfig.yml (or config-local.yml if you prefer) there is the following settings to enable google_oauth2 authentication:
google_oauth2:
    enabled: true
    id: "{{ google_client_id }}"
    secret: "{{ google_client_secret }}"
    domain: "{{ google_domain }}"
    options:
      # G Suite domain. If set, then only members of the domain can sign in/up.
      # If it's empty then any google users con sign in/up.
      hd: ""

After spinning up the containers, I can successfully login to Portus using my Google account.
Now I want the service to be available to my colleagues -- for that, I need to specify their client_id and client_secret in the file. But I don't see to find a way to add them.
The latest comment line from the above snippet says that any Google users could be able to sign in/up if a domain is not specified, but I get the following error if client_id/client_secret are not in the desired format:
Error: invalid_request
Missing required parameter: client_id
Providing logs of the moment when the issue has happened would also be
useful. If you are in production, you might want to set the `PORTUS_LOG_LEVEL`
to `debug` to get a more verbose log.

So that makes clear that we need client_id. I have tried to pass more cliend_ids as arguments to the file but that didn't work.
Portus version
image: opensuse/portus:2.4

I haven't find a solution to this issue yet. Portus' developers got any suggestions?

This isn't possible, as this isn't a typical case.
rafael<EMAIL_ADDRESS>schrieb am Mo., 9. Sep. 2019, 20:20:

I haven't find a solution to this issue yet. Portus' developers got any
suggestions?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/SUSE/Portus/issues/2207?email_source=notifications&email_token=AALMIJ2VO7IKTARXTJXMBLLQI2HWFA5CNFSM4HWUWDLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6IR3FQ#issuecomment-529603990,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALMIJZ7BSDKY2TLHJDYZSLQI2HWFANCNFSM4HWUWDLA
.

bump

Bump


Unable to locate the package

Problem encountered on https://dotnet.microsoft.com/download/linux-package-manager/ubuntu14-04/sdk-current
Operating System: Linux Ubuntu 14.04 - x64
E: Unable to locate package dotnet-sdk-3.0
E: Couldn't find any package by glob 'dotnet-sdk-3.0'
E: Couldn't find any package by regex 'dotnet-sdk-3.0'
Soource : https://dotnet.microsoft.com/download/linux-package-manager/ubuntu14-04/sdk-current
I ran into this error in the final step of installing. I am currently running on Linux mint 19.2 . It supports all apps which are supported in linux ubuntu 14.04.

.NET Core 3.0 doesn't support Ubuntu 14.04: https://github.com/dotnet/core/blob/master/release-notes/3.0/3.0-supported-os.md. Have you tried using a later Ubuntu repository that .NET Core 3.0 supports and Linux Mint 19.2 is compatible with?
I'm filing an internal issue about the 14.04 dropdown entry being there--it probably shouldn't be because it's not a valid selection for 3.0. Arguably we should have a direct entry for Linux Mint, I believe that's tracked over at https://github.com/dotnet/core/issues/2576.

The change to remove the Ubuntu 14.04 entry from the dropdown is merged and deployed now.


[AIRFLOW-530] Update connection environment var docs

Dear Airflow Maintainers,
Please accept this PR that addresses the following issues:
https://issues.apache.org/jira/browse/AIRFLOW-530
Right now, the documentation does not clearly state that connection names are converted to uppercase form when searched in the environment (https://github.com/apache/incubator-airflow/blob/master/airflow/hooks/base_hook.py#L60-L60).
This is confusing as the best practice in Airflow seems to be to define connections in lower case form.

Current coverage is 65.48% (diff: 100%)

Merging #1811 into master will increase coverage by 0.01%

@@             master      #1811   diff @@
==========================================
  Files           127        127
  Lines          9650       9650
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           6318       6319     +1
+ Misses         3332       3331     -1
  Partials          0          0

Powered by Codecov. Last update 5a8a448...6da3096

Any reason not to alter the code to handle mixed case rather than just document the behavior. I don't specify connections in env vars, but based on this PR,  I agree the current behavior looks incorrect.

@r39132 I personally don't think it matters much as long as it's explicit.
I'd even go the other way and say that connection names should be case insensitive. Saying that, I don't have a preference, we could merge this one as an improvement for the docs which describe the current behavior and create a new ticket with specification on how the new behavior should be.

question.. I did the following...
export AIRFLOW_CONN_VIA_ENV=postgresql://siddharth@localhost:5432/airflow
airflow webserver

I then looked in http://localhost:8080/admin/connection/, but don't see any connection id resembling VIA_ENV (in any case) on the connection list view.
What am I doing wrong?

+1

@r39132 I don't think right now it reflects in the admin. The admin only exposes connections which are stored in the database AFAIK.

+1


Introspection page lacks details on how to use ctrlz in a running cluster

https://preliminary.istio.io/help/ops/controlz/
It would be ideal to guide the user to reach the controlz page for the Kubernetes deployments as well. i.e.
kubectl port-forward -n istio-system  <podname> 9876:9876
browse http://localhost:9876

Issue moved to istio/istio.io #3344 via ZenHub


New event Space Law Change

About the PR

Added a new event Space Law Change. It is announced to the station that something has become illegal. To confirm that the law has been changed, all faxes receive a fax with the same text and the stamp of Central Command.
Why / Balance

The event creates new role-playing situations and also adds flavor to the round.. The drop chance is very low, similar to the Ion Storm event. And the meaning is similar to the Ion Storm event only for people.
Everything can be edited - the frequency of event, what exactly will be illegal. I would be glad to see such an event appear in SS14. There is exactly the same event in SS13, which is what I was inspired by when I did it.
This is my first serious implementation of programming knowledge. I learned C# specifically to implement this event in SS14, so I would be very happy if my pull request is accepted. 👉👈🥺
Technical details

The event fully supports localization. First, a random message is generated using a list with the last digits of the localization keys for this event. Then this message is announced and then sent to all faxes with the seal of the Central Command. At first I wanted the fax to arrive only to the faxes of the captain and the Central Command, but I was unable to do this, so it is sent to everyone. I think this is even good. More players will have access to documented evidence that the law has actually been changed.
Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl: to4no_fix

add: Added a new event Space Law Change. It is announced to the station that something has become illegal. To confirm that the law has been changed, all faxes receive a fax with the same text and the stamp of Central Command.

I did not find any errors or fatal errors during testing. Everything worked and should work.

These papers should probably be locked and un-editable with the cybersun pen as they use the Centcomm stamp

These papers should probably be locked and un-editable with the cybersun pen as they use the Centcomm stamp.
But besides that I really like this and think it would be pretty damn funny to have every so often

Nah, if they are editable it would be much more fun. Tricking the captain with a document sent from centcom about law changes could be some fun rp.

These papers should probably be locked and un-editable with the cybersun pen as they use the Centcomm stamp.
But besides that I really like this and think it would be pretty damn funny to have every so often

Nah, if they are editable it would be much more fun. Tricking the captain with a document sent from centcom about law changes could be some fun rp.

This is the essence, like the essence of the entire event - to add fun to the round :) You can experiment with options from banning alcohol to banning wearing clothes, for example, with the color green :)))) But I settled on something more or less concrete, since the event is new and it’s worth starting slowly.

I don't really have an opinion one way or another, but a suggestion. Maybe use one of these form's for the fax paper to make it feel more official? https://github.com/Moomoobeef/ss14-forms-txt/tree/master/General-Headers-Footers

A lot of the text in the announcements is repeated. If it's possible to separate the "Due to recent changes..." template from the law subjects (hats, knifes, not greeting), you should probably do that.

A lot of the text in the announcements is repeated. If it's possible to separate the "Due to recent changes..." template from the law subjects (hats, knifes, not greeting), you should probably do that.

This is problematic to do while maintaining full accessibility to localization.  At least I don’t know how to implement this without losing some of the localization capabilities.  Moreover, the event is sensitive and I think the opportunity to completely rewrite some version of the message will be useful if someone wants to seriously change something.  It will be enough to change this simply in localization.

I like the idea, and the idea of captains creating custom laws but theres 2 issues i find
1: Theres nowhere to check these new laws unless relayed through constant announcements or people telling you
2: people already dont follow basic contraband rules and sec does nothing to enforce the law unless a literal murder has been committed.

sec does nothing to enforce the law unless a literal murder has been committed.

That is an admin issue. They need to ban these security players for refusing to do their jobs.
There is already a rule for this.

I guess your right but it feels really silly to have to ahelp some third party because someone decided to wear some pajamas

I like the idea, and the idea of captains creating custom laws but theres 2 issues i find 1: Theres nowhere to check these new laws unless relayed through constant announcements or people telling you 2: people already dont follow basic contraband rules and sec does nothing to enforce the law unless a literal murder has been committed.

I like the idea, and the idea of captains creating custom laws but theres 2 issues i find 1: Theres nowhere to check these new laws unless relayed through constant announcements or people telling you 2: people already dont follow basic contraband rules and sec does nothing to enforce the law unless a literal murder has been committed.

As for the impossibility of verification, absolutely all faxes at the station will receive a confirmation document, especially since, according to the meaning of the message, before the law comes into force, players have 15 minutes to adapt to the change in the law and receive information about it.
Of course, there is also the option of creating news about this, but it is easily erased and even easier to falsify. Although it would be very convenient for obtaining information.

Nah, if they are editable it would be much more fun. Tricking the captain with a document sent from centcom about law changes could be some fun rp.

Many people see papers stamped by Centcom as messages by ADMINS. If the stamped paper said "kill X", the chance is high that someone does it even if it goes 100% against rules.

laminate the paper to make it un-editable

laminate the paper to make it un-editable

@Djungelskog2  I'm not sure it's worth doing, but I don't know how to do it either. Could you tell? If the reviewer decides that it needs to be made uneditable

I just said that as a flavourful way that un-editable papers could be implemented, im guessing a new texture would be overlapped onto the paper but yea thats all I got

What papers in the game are un-editable?

There was a PR recently that allowed admins to lock papers from the admin fax menu

Many people see papers stamped by Centcom as messages by ADMINS. If the stamped paper said "kill X", the chance is high that someone does it even if it goes 100% against rules.

If that is the way it is intended we should probably remove or lock the Centcom stamped papers (like the PA instructions) some maps have lying around at round start. I used a cybersun pen on those before to gain free access from HOP. I consider this a fun feature tough.

Many people see papers stamped by Centcom as messages by ADMINS. If the stamped paper said "kill X", the chance is high that someone does it even if it goes 100% against rules.

If that is the way it is intended we should probably remove or lock the Centcom stamped papers (like the PA instructions) some maps have lying around at round start. I used a cybersun pen on those before to gain free access from HOP. I consider this a fun feature tough.

@slarticodefast I think that nothing prevents you from asking the Central Command for confirmation of the document that confuses you.

Nah, if they are editable it would be much more fun. Tricking the captain with a document sent from centcom about law changes could be some fun rp.

Many people see papers stamped by Centcom as messages by ADMINS. If the stamped paper said "kill X", the chance is high that someone does it even if it goes 100% against rules.

If admins rely on CentCom-stamped faxes to be seen as admin rules, that is their problem for using faxes for OOC rules information. At best CentCom-stamps should be seen as being sent by your in-universe corporate overlords.
As someone who makes up a new stupid law every single Captain shift I do, I think this PR is good on paper but is likely to have pitfalls. It is very easy to write a law that is unfun, and the ones written in Space Law have gone through several revisions to ensure that Sec & Command can enforce them without impacting gameplay.
You don't want to have a rule that ruins actual gameplay for people; by all means, ban cigarettes or alcohol or force everyone to wear hardhats indoors. But you can't ban Science from doing artifacts (without good reason), that just screws over players who want to do that part of the game and is no fun. So you have to be very careful what laws are being changed.

Update:

Localization optimized

Now, after time has passed for adaptation, a confirmation message is sent that the law has indeed come into force

It's also worth considering that:

It seems the laws don't have any sentence tied to them, so if you catch someone doing something that has been outlawed there is no guidance on what the punishment should be.
The message claims the station should hurry up to avoid potential negative consequences. Since there are none, I would reword this into something that pushes Sec to enforce it. E.g. "Security & Command are to ensure the station is fully compliant with the law by the time the adjustment period is over."

It's also worth considering that:

It seems the laws don't have any sentence tied to them, so if you catch someone doing something that has been outlawed there is no guidance on what the punishment should be.
The message claims the station should hurry up to avoid potential negative consequences. Since there are none, I would reword this into something that pushes Sec to enforce it. E.g. "Security & Command are to ensure the station is fully compliant with the law by the time the adjustment period is over."

Hi am epic space lawyer person here it does do this. 1-XX is a Minor crime if thats what the "law code" Within the current screenshots.

I hope I added the final winter events to the event code. Everything should work. If anyone wants, I will be glad to have suggestions for adding message options.

I'm away for the weekend, but I'll give this another review when I get back.

I'm away for the weekend, but I'll give this another review when I get back.

@Tayrtahn ok thank you I will be looking forward to your review

going to be transparent here and state that even if it seems like a good idea on paper, it's going to be terrible in implementation on average
borrowing an example from a private discussion about this:

latejoin crewmember shows up after space law bs, let's assume space law is cigs are now contraband
get arrested for smoking
ahelp because they (rightfully) think sec is being shitsec and arresting for no reason

and let's be honest - sec could literally show the person in question the fax stating the "space law change" and they would still refuse to believe it
either current round admin has to investigate - or the more likely scenario, an admin has to get on and sanity check

that its not just shitsec
that the law change actually occured

and let's be honest - people are already under the impression that their ahelps regularly go unheard because admin presence is stretched incredibly thin

in practice, making random things an arrestable offense doesn't serve to make anything more fun for any party involved. random player feels like they're being metagrudged by sec, sec has to put up with even more harassment from people than they already do, and admins have to spend more time looking into non-issues that absolutely should not be an issue in the first place.
as such, even if @Tayrtahn finds no further issues on review after their return from their weekend trip, i'm not in favor of this being merged in any capacity upstream. the only reason i'm not closing the PR outright is because i'm typically not a reviewer for these sorts of things and would like to get other PM opinions on the matter, since this extends beyond just a fun player feature by a significant margin.
tl;dr - please leave random amendable laws to borgs and non-organics, no one who logs into the game is sane as is and this would just exacerbate the issue

going to be transparent here and state that even if it seems like a good idea on paper, it's going to be terrible in implementation on average
borrowing an example from a private discussion about this:

latejoin crewmember shows up after space law bs, let's assume space law is cigs are now contraband
get arrested for smoking
ahelp because they (rightfully) think sec is being shitsec and arresting for no reason. and let's be honest - sec could literally show the person in question the fax stating the "space law change" and they would still refuse to believe it
either current round admin has to investigate - or the more likely scenario, an admin has to get on and sanity check:

that its not just shitsec
that the law change actually occured

which poses additional issues because people are already under the impression that their ahelps regularly go unheard, because admin presence is stretched incredibly thin

in practice, making random things an arrestable offense doesn't serve to make anything more fun for any party involved. random player feels like they're being metagrudged by sec, sec has to put up with even more harassment from people than they already do, and admins have to spend more time looking into non-issues that absolutely should not be an issue in the first place.
as such, even if @Tayrtahn finds no further issues on review after their return from their weekend trip, i'm not in favor of this being merged in any capacity upstream. the only reason i'm not closing the PR outright is because i'm typically not a reviewer for these sorts of things and would like to get other PM opinions on the matter, since this extends beyond just a fun player feature by a significant margin.
tl;dr - please leave random amendable laws to borgs and non-organics, no one who logs into the game is sane as is and this would just exacerbate the issue

I think that the problem you mentioned relates exclusively to the state of administration on the server. If necessary, I can try to additionally indicate on the fax the time it was sent so that players can check the current time and make sure that the law has come into force. But I don't know how to do it yet. A person will simply look at his PDA and find out whether the time has come for the law to come into force. Well, if he still doesn’t believe after that, then this is clearly not a problem with the event, but a problem with the player himself who doesn’t believe.
I also focus on other servers where the situations you mentioned are much less common (I’ll take your word for it that such situations do exist). Provided that this event is very rare and can occur a maximum of 2 times per round (can be reduced to once), nothing particularly bad can happen and rather brings new roleplay experience. If this pull request is closed, I will be very upset because I put a lot of effort as a person who wrote some code for the first time in my life a week ago. I really think it would add variety to the round.

wouldn't it be more player-inclusive if it was reported via the news app on the PDA rather than just being faxed to some certain people who then have to diseminate the information to the rest of the crew? that way people can still have access to it if they latejoin

wouldn't it be more player-inclusive if it was reported via the news app on the PDA rather than just being faxed to some certain people who then have to disseminate the information to the rest of the crew? that way people can still have access to it if they latejoin

@Plykiya I could create news about changing the cosmic law and thought about it, but I'm afraid that it would be easy for players to delete it and compromise it

the law on wizden is not very good implemented to change it midround

wouldn't it be more player-inclusive if it was reported via the news app on the PDA rather than just being faxed to some certain people who then have to disseminate the information to the rest of the crew? that way people can still have access to it if they latejoin

@Plykiya I could create news about changing the cosmic law and thought about it, but I'm afraid that it would be easy for players to delete it and compromise it

people can delete news articles?

wouldn't it be more player-inclusive if it was reported via the news app on the PDA rather than just being faxed to some certain people who then have to disseminate the information to the rest of the crew? that way people can still have access to it if they latejoin

@Plykiya I could create news about changing the cosmic law and thought about it, but I'm afraid that it would be easy for players to delete it and compromise it

people can delete news articles?

As I remember, yes. Service level access is sufficient

Sounds like news articles just need a bool to ensure some can't be deleted then, same thing as how some papers can be locked to prevent any tampering

the law on wizden is not very good implemented yet to change it midround

Sounds like news articles just need a bool to ensure some can't be deleted then, same thing as how some papers can be locked to prevent any tampering

I thought about this and I would try to create a new type of news from an authorized source that cannot be deleted and it will be clear that it is definitely from the Central Command, but I am afraid my skills are not enough. I spent a week making these 158 lines for the event.

Thank you for your contribution! However, after discussion among maintainers, we have decided to close this PR on the grounds that the feature is not desired. Concerns were raised about discoverability of law changes, difficulty for admins, and potential to create undesirable player behavior.
For these reasons, this PR will be closed. You are however encouraged to continue contributing if you are still interested, and you are free to offer this code to forks as well.
On a personal note, I would like to add that I was impressed by how quickly you were able to respond to code review with improvements - I get the sense that you most have learned a fair bit about our codebase and architecture in the process, so I hope to see your work here again in the future.

Thank you for your contribution! However, after discussion among maintainers, we have decided to close this PR on the grounds that the feature is not desired. Concerns were raised about discoverability of law changes, difficulty for admins, and potential to create undesirable player behavior.
For these reasons, this PR will be closed. You are however encouraged to continue contributing if you are still interested, and you are free to offer this code to forks as well.
On a personal note, I would like to add that I was impressed by how quickly you were able to respond to code review with improvements - I get the sense that you must have learned a fair bit about our codebase and architecture in the process, so I hope to see your work here again in the future.

It's a pity I really tried  :( The people in the discord helped me figure out the architecture, for which I thank them! Well, then I'll do localization, probably this will be in demand. Thank you for your words.


Provide Consul dynamic configuration center implementation

Please answer these questions before submitting pull request

Why submit this pull request?

[ ] Bug fix

[x] New feature provided

[ ] Improve performance

Related issues

resolves #2895

/run e2e

/run e2e

/run e2e

/run e2e

/run e2e

/run ci

/run ci

/run ci

/run e2e


fix: fix rabbitmq import errors

fixes #381
Also in this PR:

added e2e tests
uniformed the c-tor to the new format we introduced for Kafka

coverage: 72.155% (+0.005%) from 72.15%
when pulling 569d4ce65ca04fbc0014fb5e702f50a66769d59c on massi/381
into 910f7c62ed9ba5005b85dd1ba252c38afe421cbe on main.


Fix example code in the readme

As the decoded data is accessed like an array, the second parameter must be true.

Thanks for your PR. Merged.


Add warning to kind-up if non-gnu tools were detected

How to categorize this PR?

/area dev-productivity
/kind enhancement
What this PR does / why we need it:
Add checks to verify that the required Gnu tools are being used, and print a warning otherwise.
Which issue(s) this PR fixes:
make kind-up will succeed without errors, even if e.g. BSD sed is used. However, the results of the commands while using BSD sed are different and may cause some "hidden" issues. In my particular case, the required patches for the CorerDNS condfigMap were missing, which caused the gardenlet to fail to start during the make gardener-up.
Thanks @timebertt for the troubleshooting.

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

Example output:
 make kind-up
./hack/kind-up.sh \
		--cluster-name gardener-local \
		--path-kubeconfig ./gardener/example/provider-local/seed-kind/base/kubeconfig \
		--path-cluster-values ./gardener/example/gardener-local/kind/local/values.yaml \
		--with-lpp-resize-support false \

Error: Required shell dependencies not met. Please refer to https://github.com/gardener/gardener/blob/master/docs/development/local_setup.md#macos-only-install-gnu-core-utilities:
    - Current sed version does not support the --version flag. Please ensure GNU sed is installed.
    - BSD tar detected. Please ensure GNU tar is installed.
    - BSD grep detected. Please ensure GNU grep is installed.
make: *** [kind-up] Error 1


Dependency updates not respecting "ignore" section

Hello,
I'm trying to ignore updates for a NuGet package ("Moq") in my dependabot.yml but it keeps creating pull requests anyway.
It looks like someone was having this issue recently (https://github.com/dependabot/dependabot-core/issues/7377) but it was filed under the official repository and no conclusion was reached.
I've tried the possible fixes mentioned in #582 (Removing BOM, removing comments, etc..) but nothing fixed it.
dependabot.yml:
version: 2
registries:
  my-feed:
    type: 'nuget-feed'
    url: 'https://pkgs.dev.azure.com/<ORG>/<PROJECT>/_packaging/<FEED>/nuget/v3/index.json'
    token: 'PAT:${{ nugetAccessToken }}'

updates:
  - package-ecosystem: 'nuget'
    directory: '/'
    schedule:
      interval: 'weekly'
    ignore:
      - dependency-name: 'Moq'

I've also tried all lowercase "moq" but to no avail.

Repro?

I've since removed this particular dependency from all my projects and I wouldn't be able to provide a public reproduction unfortunately.
The types of projects it was run against were .NET standard libraries and .NET 6 web apps/function apps.


Override Scss Variable value when body direction rtl

I want to Override Scss Variable value when body direction rtl. I tried like below but its not working. I have used $FONT_REGULAR variable in lot of components, now we want to change the font name arabic version but its not working.
$FONT_REGULAR: "Roboto-Regular";
body[dir='rtl'] {
$FONT_REGULAR: "FSAlbertArabicWeb-Regular";
}

This is not how Sass works, it doesn't now on compile time what the context is.
We use RTLCSS to post-process our compiled CSS, as mentioned in our docs.

This will output a second CSS file, dedicated to RTL.
If you want to keep your single file and use [dir] selector, you need to create another variable.

Unfortunately after reading carefully the documentation and trying to implement I am having a similar issue.
It seems it does not work. Are there any examples somewhere end-to-end so i can see how it is properly implemented in a simple HTML file?
Much appreciated

You need three steps.
In your sources, this should be something like:
$FONT_REGULAR: "Roboto-Regular" #{/* rtl:"FSAlbertArabicWeb-Regular" */}
}

Then compile your Sass to get your LTR CSS file (which should contain the RTL comment).
Finally run RTLCSS on your LTR CSS file to postprocess RTL comments. This will output another CSS file for RTL.
You may have a look at Bootstrap's package.json to see how we run this.


Exogenous transition path for shipping, Steel, and Aluminum production

Transformation of shipping demand, as well as production of Steel and Aluminum, is currently assumed to occur overnight.
(i.e. is only represented by one value in the config.yaml file). This PR enables the use of exogenously defined transition paths for these transformations.

I just realized that I missed adding the oil consumed in shipping as a load to the EU oil bus.

That is really cool! I guess n the Snakefile there is the wildcard planning_horizons missing for the benchmarks see here. I made a new pull request based on this branch to include today's district heating share and the options to increase it during the planning horizon.

That is really cool! I guess n the Snakefile there is the wildcard planning_horizons missing for the benchmarks see here. I made a new pull request based on this branch to include today's district heating share and the options to increase it during the planning horizon.

That was my mistake when I merged the master.

Great, flexibly switching between exogenous transition paths and fixed choices for parameters is very nicely implemented and we can surely use this as role model for other parameters, too.