master: Waiting for Kubernetes master to become ready..

It seems that vagrant configures the master node but then it, for some reason does not report correctly its status, not really sure what happens but it either takes really long to wait for the master - at least 30 minutes, or it never finishes. Here's my output if it would help.
vagrant up
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/pre-rubygems.rb:31: warning: Insecure world writable dir /home/gngeorgiev/android-sdk in PATH, mode 040777
/opt/vagrant/embedded/gems/gems/bundler-1.10.5/lib/bundler/shared_helpers.rb:78: warning: Insecure world writable dir /home/gngeorgiev/android-sdk in PATH, mode 040777
Bringing machine 'master' up with 'virtualbox' provider...
Bringing machine 'node-01' up with 'virtualbox' provider...
Bringing machine 'node-02' up with 'virtualbox' provider...
==> master: Running triggers before up...
==> master: Setting Kubernetes version 1.0.6
==> master: Configuring Kubernetes cluster DNS...
==> master: Importing base box 'coreos-alpha'...
==> master: Matching MAC address for NAT networking...
==> master: Checking if box 'coreos-alpha' is up to date...
==> master: Setting the name of the VM: kubernetes-vagrant-coreos-cluster_master_1442694599808_18282
==> master: Clearing any previously set network interfaces...
==> master: Preparing network interfaces based on configuration...
    master: Adapter 1: nat
    master: Adapter 2: hostonly
==> master: Forwarding ports...
    master: 22 => 2222 (adapter 1)
==> master: Running 'pre-boot' VM customizations...
==> master: Booting VM...
==> master: Waiting for machine to boot. This may take a few minutes...
    master: SSH address: <IP_ADDRESS>:2222
    master: SSH username: core
    master: SSH auth method: private key
    master: Warning: Connection timeout. Retrying...
==> master: Machine booted and ready!
==> master: Setting hostname...
==> master: Configuring and enabling network interfaces...
==> master: Running provisioner: file...
==> master: Running provisioner: file...
==> master: Running provisioner: shell...
    master: Running: inline script
==> master: Running triggers after up...
==> master: Sanitizing stuff...
Identity added: /home/gngeorgiev/.vagrant.d/insecure_private_key (/home/gngeorgiev/.vagrant.d/insecure_private_key)
==> master: Installing kubectl for the kubernetes version we just bootstrapped...
Downloading and installing linux version of 'kubectl' v1.0.6 into /usr/local/bin. This may take a couple minutes, depending on your internet speed..
Setting environment variables..
==> master: Waiting for Kubernetes master to become ready...

How fast is your internet speed? See #116

hi @gngeorgiev , the loop that wait for master is the following :
info "Waiting for Kubernetes master to become ready..."
j, uri, res = 0, URI("http://#{MASTER_IP}:8080"), nil
loop do
    j += 1
    begin
        res = Net::HTTP.get_response(uri)
    rescue
        sleep 10
    end
    break if res.is_a? Net::HTTPSuccess or j >= 50
end

It breaks after 8' ... it must have happen something during that one.
During that wait time, you can ssh in to try to understand what the problems came from :
vagrant ssh master

Then do that one :
systemctl status

Should appear something like that :
core@master ~ $ systemctl status
● master
    State: running
     Jobs: 3 queued
   Failed: 0 units
    Since: Sun 2015-09-20 07:00:40 UTC; 3min 41s ago
   CGroup: /
           ├─1 /usr/lib/systemd/systemd --switched-root --system --deserialize 21
           └─system.slice
             ├─dbus.service
             │ └─608 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
             ├─rpc-statd.service
             │ └─1291 /sbin/rpc.statd --no-notify
             ├─update-engine.service
             │ └─618 /usr/sbin/update_engine -foreground -logtostderr
             ├─system-sshd.slice
             │ ├─sshd@0-<IP_ADDRESS>:22-<IP_ADDRESS>:51236.service
             │ │ ├─949 sshd: core [priv]
             │ │ └─954 sshd: core@notty
             │ └─sshd@2-<IP_ADDRESS>:22-<IP_ADDRESS>:51435.service
[...]

Look at the top, it says that 3 jobs are queued.
We can look to that jobs with systemctl list-jobs :
core@master ~ $ systemctl list-jobs
 JOB UNIT                                                                         TYPE  STATE
3065 kube-apiserver.service                                                       start waiting
3164 kube-install.service                                                         start running
1315<EMAIL_ADDRESS>start running

3 jobs listed.

Bringing machine 'node-01' up with 'virtualbox' provider...
Bringing machine 'node-02' up with 'virtualbox' provider...
==> master: Running triggers before up...
==> master: Setting Kubernetes version 1.0.6
==> master: Configuring Kubernetes cluster DNS...
==> master: Checking if box 'coreos-alpha' is up to date...
==> master: VirtualBox VM is already running.
==> master: Running triggers after up...
==> master: Sanitizing stuff...
Identity added: /Users/Bruno/.vagrant.d/insecure_private_key (/Users/Bruno/.vagrant.d/insecure_private_key)
==> master: Installing kubectl for the kubernetes version we just bootstrapped...
Downloading and installing darwin version of 'kubectl' v1.0.6 into /usr/local/bin. This may take a couple minutes, depending on your internet speed..
Password:
Setting environment variables..
==> master: Waiting for Kubernetes master to become ready...

and it waits forever... i'm using Mac OS X 10.10.5

Can you vagrant ssh master and tell what's becoming inside please ? (reference to my previous post)

Having same issue as above...waiting for master.
Running systemctl status shows 1 failed job,
on checking the failed units (systemctl list-units), i see kube-certs.service failed
core@master ~ $ systemctl status kube-certs.service -n1000
● kube-certs.service - Generate Kubernetes API Server certificates
   Loaded: loaded (/etc/systemd/system/kube-certs.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Tue 2015-09-29 07:31:10 UTC; 3min 17s ago
  Process: 2177 ExecStart=/tmp/make-certs.sh <IP_ADDRESS> IP:<IP_ADDRESS>,IP:<IP_ADDRESS>,DNS:kubernetes,DNS:kubernetes.default,DNS:kubernetes.default.svc,DNS:kubernetes.default.svc.cluster.local (code=exited, status=203/EXEC)
  Process: 2173 ExecStartPre=/usr/bin/chmod u=rwx,go= /tmp/make-certs.sh (code=exited, status=0/SUCCESS)
  Process: 2172 ExecStartPre=/usr/sbin/groupadd -r kube-cert (code=exited, status=9)
 Main PID: 2177 (code=exited, status=203/EXEC)

Sep 29 07:31:10 master systemd[1]: Starting Generate Kubernetes API Server certificates...
Sep 29 07:31:10 master systemd[1]: kube-certs.service: Main process exited, code=exited, status=203/EXEC
Sep 29 07:31:10 master systemd[1]: Failed to start Generate Kubernetes API Server certificates.
Sep 29 07:31:10 master systemd[1]: kube-certs.service: Unit entered failed state.
Sep 29 07:31:10 master systemd[1]: kube-certs.service: Failed with result 'exit-code'.
Sep 29 07:31:10 master groupadd[2172]: groupadd: group 'kube-cert' already exists

@potgieterdl it seems it's failing to execute /tmp/make-certs.sh <IP_ADDRESS> IP:<IP_ADDRESS>,IP:<IP_ADDRESS>,DNS:kubernetes,DNS:kubernetes.default,DNS:kubernetes.default.svc,DNS:kubernetes.default.svc.cluster.local. Can you try and run that manually, please?

I am unable to reproduce this. Need more feedback.
$ systemctl status kube-certs.service
● kube-certs.service - Generate Kubernetes API Server certificates
   Loaded: loaded (/etc/systemd/system/kube-certs.service; static; vendor preset: disabled)
   Active: active (exited) since Tue 2015-09-29 08:44:51 UTC; 1min 7s ago
  Process: 1547 ExecStart=/tmp/make-certs.sh <IP_ADDRESS> IP:<IP_ADDRESS>,IP:<IP_ADDRESS>,DNS:kubernetes,DNS:kubernetes.default,DNS:kubernetes.default.svc,DNS:kubernetes.default.svc.cluster.local (code=exited, status=0/SUCCESS)
  Process: 1546 ExecStartPre=/usr/bin/chmod u=rwx,go= /tmp/make-certs.sh (code=exited, status=0/SUCCESS)
  Process: 1542 ExecStartPre=/usr/sbin/groupadd -r kube-cert (code=exited, status=0/SUCCESS)
 Main PID: 1547 (code=exited, status=0/SUCCESS)
   Memory: 0B
      CPU: 0
   CGroup: /system.slice/kube-certs.service

Sep 29 08:44:50 master systemd[1]: Starting Generate Kubernetes API Server certificates...
Sep 29 08:44:50 master groupadd[1542]: group added to /etc/group: name=kube-cert, GID=149
Sep 29 08:44:50 master groupadd[1542]: group added to /etc/gshadow: name=kube-cert
Sep 29 08:44:50 master groupadd[1542]: new group: name=kube-cert, GID=149
Sep 29 08:44:51 master make-certs.sh[1547]: 3
Sep 29 08:44:51 master make-certs.sh[1547]: 4
Sep 29 08:44:51 master systemd[1]: Started Generate Kubernetes API Server certificates.

@potgieterdl why groupadd: group 'kube-cert' already exists? Even though this command is allowed to fail when executing the service, I don't see why this group would exist. What changes have you made to the tree?

I had the same.
group exists: running "vagrant up" multiple times?

Well, if one doesn't destroy the VMs, yes you may find yourself in the middle of a shitstorm when vagrant up again. This behavior is unfortunately not supported. The same for reload/resume.

Ok, I've run:
vagrant halt
vagrant destroy
vagrant up

but it happens something similary:
Bringing machine 'master' up with 'virtualbox' provider...
Bringing machine 'node-01' up with 'virtualbox' provider...
Bringing machine 'node-02' up with 'virtualbox' provider...
==> master: Running triggers before up...
==> master: Setting Kubernetes version 1.0.6
==> master: Configuring Kubernetes cluster DNS...
==> master: Importing base box 'coreos-alpha'...
==> master: Matching MAC address for NAT networking...
==> master: Checking if box 'coreos-alpha' is up to date...
==> master: Setting the name of the VM: kubernetes-vagrant-coreos-cluster_master_1443522387210_35584
==> master: Clearing any previously set network interfaces...
==> master: Preparing network interfaces based on configuration...
    master: Adapter 1: nat
    master: Adapter 2: hostonly
==> master: Forwarding ports...
    master: 22 => 2222 (adapter 1)
==> master: Running 'pre-boot' VM customizations...
==> master: Booting VM...
==> master: Waiting for machine to boot. This may take a few minutes...
    master: SSH address: <IP_ADDRESS>:2222
    master: SSH username: core
    master: SSH auth method: private key
    master: Warning: Connection timeout. Retrying...
==> master: Machine booted and ready!
==> master: Setting hostname...
==> master: Configuring and enabling network interfaces...
==> master: Running provisioner: file...
==> master: Running provisioner: file...
==> master: Running provisioner: file...
==> master: Running provisioner: file...
==> master: Running provisioner: file...
==> master: Running provisioner: shell...
    master: Running: inline script
==> master: Running triggers after up...
==> master: Sanitizing stuff...
Could not open a connection to your authentication agent.
==> master: Installing kubectl for the kubernetes version we just bootstrapped...
==> master: Executing remote command "sudo -u core /bin/sh /home/core/kubectlsetup install"...
==> master: Downloading and installing linux version of 'kubectl' v1.0.6 into /opt/bin. This may take a couple minutes, depending on your internet speed..
==> master: Setting environment variables..
==> master: Remote command execution finished.
==> master: Waiting for Kubernetes master to become ready...

core@master ~ $ systemctl status kube-certs.service -n1000
● kube-certs.service - Generate Kubernetes API Server certificates
   Loaded: loaded (/etc/systemd/system/kube-certs.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Tue 2015-09-29 10:28:44 UTC; 2s ago
  Process: 1761 ExecStart=/tmp/make-certs.sh <IP_ADDRESS> IP:<IP_ADDRESS>,IP:<IP_ADDRESS>,DNS:kubernetes,DNS:kubernetes.default,DNS:kubernetes.default.svc,DNS:kubernetes.default.svc.cluster.local (code=exited, status=203/EXEC)
  Process: 1759 ExecStartPre=/usr/bin/chmod u=rwx,go= /tmp/make-certs.sh (code=exited, status=0/SUCCESS)
  Process: 1756 ExecStartPre=/usr/sbin/groupadd -r kube-cert (code=exited, status=9)
 Main PID: 1761 (code=exited, status=203/EXEC)

Sep 29 10:28:44 master systemd[1]: Starting Generate Kubernetes API Server certificates...
Sep 29 10:28:44 master systemd[1]: kube-certs.service: Main process exited, code=exited, status=203/EXEC
Sep 29 10:28:44 master systemd[1]: Failed to start Generate Kubernetes API Server certificates.
Sep 29 10:28:44 master groupadd[1756]: groupadd: group 'kube-cert' already exists
Sep 29 10:28:44 master systemd[1]: kube-certs.service: Unit entered failed state.
Sep 29 10:28:44 master systemd[1]: kube-certs.service: Failed with result 'exit-code'.

@remoe please run and post back the results of:
ls -las /tmp
and
/tmp/make-certs.sh <IP_ADDRESS> IP:<IP_ADDRESS>,IP:<IP_ADDRESS>,DNS:kubernetes,DNS:kubernetes.default,DNS:kubernetes.default.svc,DNS:kubernetes.default.svc.cluster.local

core@master ~ $ ls -las /tmp
total 12
0 drwxrwxrwt  9 root root  220 Sep 29 11:52 .
4 drwxr-xr-x 18 root root 4096 Sep 29 11:52 ..
0 drwxrwxrwt  2 root root   40 Sep 29 11:51 .ICE-unix
0 drwxrwxrwt  2 root root   40 Sep 29 11:51 .Test-unix
0 drwxrwxrwt  2 root root   40 Sep 29 11:51 .X11-unix
0 drwxrwxrwt  2 root root   40 Sep 29 11:51 .XIM-unix
0 drwxrwxrwt  2 root root   40 Sep 29 11:51 .font-unix
4 -rw-r--r--  1 core core 2937 Sep 29 11:52 make-certs.sh
0 drwx------  2 core core   60 Sep 29 11:52 ssh-nk8m1Gjquy
0 drwx------  3 root root   60 Sep 29 11:51 systemd-private-3e9e6d7e56694382929a924d0e88b145-systemd-timesyncd.service-WjRmmj
4 -rwxr-xr-x  1 core core  759 Sep 29 11:52 vagrant-shell

$ vagrant ssh master
CoreOS valpha (815.0.0)
<.8.101,IP:<IP_ADDRESS>,DNS:kubernetes,DNS:kubernetes.default,DNS:kubernetes.default.svc,DNS:kubernetes.default.svc.cluster.local
-bash: /tmp/make-certs.sh: Permission denied

I know, wrong user, but ...
00:00:22.809893 NAT: DHCP offered IP address <IP_ADDRESS>
00:01:15.221412 PGM: Failed to procure handy pages; rc=VERR_NO_MEMORY rcAlloc=VINF_SUCCESS rcSeed=VINF_SUCCESS cHandyPages=0x8
00:01:15.221424      cAllPages=0x40c24 cPrivatePages=0x1b799 cSharedPages=0x0 cZeroPages=0x25489
00:01:15.221450 GMM: Statistics:
00:01:15.221451      Allocated pages: 1ab9d
00:01:15.221452      Maximum   pages: 4009e
00:01:15.221452      Ballooned pages: 0
00:01:15.222756 VM: Raising runtime error 'HostMemoryLow' (fFlags=0x2)
00:01:15.222766 AssertLogRel F:\tinderbox\win-5.0\src\VBox\VMM\VMMR3\VMM.cpp(1771) int __cdecl VMMR3EmtRendezvous(struct VM *,unsigned int,int (__cdecl *)(struct VM *,struct VMCPU *,void *),void *): !pVCpu->vmm.s.fInRendezvous
00:01:15.222775 Console: VM runtime error: fatal=false, errorID=HostMemoryLow message="Unable to allocate and lock memory. The virtual machine will be paused. Please close applications to free up memory or close the VM"
00:01:15.245114 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:01:15.245123 Console: Machine state changed to 'GuruMeditation'

-bash: /tmp/make-certs.sh: Permission denied is the culprit. weird! why would it work for me and not for you guys?

What is your host OS ?
-rw-r--r-- <= make-certs.sh
maybe it comes from git configuration as there is no .gitattributes in the project

@tdeheurles , Windows 7 x64

@remoe I run it on the same OS. But I had lots of issues with that (not in that project, but can't remind when I config it globally).
Try a git status just after your git clone. Maybe it changes permissions. I'm not really sure it comes from there ... but maybe ^^
If it changes permissions, you will need to configure your git for linux LF.

@remoe @potgieterdl @brunomacf @gngeorgiev care to try https://github.com/pires/kubernetes-vagrant-coreos-cluster/pull/161 and let me know?

@pires here is the result:
core@master ~ $ systemctl status kube-certs.service -n1000
● kube-certs.service - Generate Kubernetes API Server certificates
   Loaded: loaded (/etc/systemd/system/kube-certs.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Tue 2015-09-29 13:54:18 UTC; 14s ago
  Process: 1555 ExecStart=/tmp/make-certs.sh <IP_ADDRESS> IP:<IP_ADDRESS>,IP:<IP_ADDRESS>,DNS:kubernetes,DNS:kubernetes.default,DNS:kubernetes.default.svc,DNS:kubernetes.default.svc.cluster.local (code=exited, status=2)
  Process: 1553 ExecStartPre=/usr/bin/chmod 755 /tmp/make-certs.sh (code=exited, status=0/SUCCESS)
  Process: 1550 ExecStartPre=/usr/sbin/groupadd -r kube-cert (code=exited, status=9)
 Main PID: 1555 (code=exited, status=2)

Sep 29 13:54:18 master systemd[1]: Starting Generate Kubernetes API Server certificates...
Sep 29 13:54:18 master groupadd[1550]: groupadd: group 'kube-cert' already exists
Sep 29 13:54:18 master make-certs.sh[1555]: [27B blob data]
Sep 29 13:54:18 master make-certs.sh[1555]: Usage:        /bin/sh [GNU long option] [option] ...
Sep 29 13:54:18 master make-certs.sh[1555]: /bin/sh [GNU long option] [option] script-file ...

Sep 29 13:54:18 master systemd[1]: kube-certs.service: Unit entered failed state.
Sep 29 13:54:18 master systemd[1]: kube-certs.service: Failed with result 'exit-code'.
Hint: Some lines were ellipsized, use -l to show in full.

@tdeheurles , thanks, I called git status after clone.

@remoe I'm sorry but there's something pretty nasty going on with your stuff.
Run the following exactly as typed:
git clone https://github.com/pires/kubernetes-vagrant-coreos-cluster
cd kubernetes-vagrant-coreos-cluster
vagrant destroy -f
NODES=0 vagrant up

windows 8.1, now trying on windows 10 at home. Running the above as described. Will feedback in few min

@pires , results are same as @remoe
core@master ~ $ systemctl status kube-certs.service -n1000
● kube-certs.service - Generate Kubernetes API Server certificates
   Loaded: loaded (/etc/systemd/system/kube-certs.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Tue 2015-09-29 14:55:56 UTC; 13s ago
  Process: 1616 ExecStart=/tmp/make-certs.sh <IP_ADDRESS> IP:<IP_ADDRESS>,IP:<IP_ADDRESS>,DNS:kubernetes,DNS:kubernetes.default,DNS:kubernetes.default.svc,DNS:kubernetes.default.svc.cluster.local (code=exited, status=2)
  Process: 1614 ExecStartPre=/usr/bin/chmod 755 /tmp/make-certs.sh (code=exited, status=0/SUCCESS)
  Process: 1611 ExecStartPre=/usr/sbin/groupadd -r kube-cert (code=exited, status=9)
 Main PID: 1616 (code=exited, status=2)

Sep 29 14:55:56 master systemd[1]: Starting Generate Kubernetes API Server certificates...
Sep 29 14:55:56 master groupadd[1611]: groupadd: group 'kube-cert' already exists
Sep 29 14:55:56 master make-certs.sh[1616]: [27B blob data]
Sep 29 14:55:56 master make-certs.sh[1616]: Usage:        /bin/sh [GNU long option] [option] ...
Sep 29 14:55:56 master make-certs.sh[1616]: /bin/sh [GNU long option] [option] script-file ...

Sep 29 14:55:56 master systemd[1]: kube-certs.service: Unit entered failed state.
Sep 29 14:55:56 master systemd[1]: kube-certs.service: Failed with result 'exit-code'.

core@master ~ $  ls -las /tmp
total 12
0 drwxrwxrwt  9 root root  220 Sep 29 14:51 .
4 drwxr-xr-x 18 root root 4096 Sep 29 14:50 ..
0 drwxrwxrwt  2 root root   40 Sep 29 14:50 .ICE-unix
0 drwxrwxrwt  2 root root   40 Sep 29 14:50 .Test-unix
0 drwxrwxrwt  2 root root   40 Sep 29 14:50 .X11-unix
0 drwxrwxrwt  2 root root   40 Sep 29 14:50 .XIM-unix
0 drwxrwxrwt  2 root root   40 Sep 29 14:50 .font-unix
4 -rwxr-xr-x  1 core core 2939 Sep 29 14:50 make-certs.sh
0 drwx------  2 core core   60 Sep 29 14:50 ssh-A6kbg5UJqx
0 drwx------  3 root root   60 Sep 29 14:50 systemd-private-aba9617942e540bd8793a09b13f6bdcd-systemd-timesyncd.service-rbxwyx
4 -rwxr-xr-x  1 core core  759 Sep 29 14:50 vagrant-shell

core@master ~ $ systemctl list-units | grep failed                                                                                4● kube-certs.service                                                                       loaded failed failed    Generate Kubernetes API Server certificates

and the most important, I think
core@master ~ $ /tmp/make-certs.sh <IP_ADDRESS> IP:<IP_ADDRESS>,IP:<IP_ADDRESS>,DNS:kubernetes,DNS:kubernetes.default,DNS:kubernetes.default.svc,DNS:kubernetes.default.svc.cluster.local
: invalid option
Usage:  /bin/sh [GNU long option] [option] ...
        /bin/sh [GNU long option] [option] script-file ...
GNU long options:
        --debug
        --debugger
        --dump-po-strings
        --dump-strings
        --help
        --init-file
        --login
        --noediting
        --noprofile
        --norc
        --posix
        --protected
        --rcfile
        --restricted
        --verbose
        --version
Shell options:
        -irsD or -c command or -O shopt_option          (invocation only)
        -abefhkmnptuvxBCHP or -o option

Above is on a brand new windows 10, with clean vagrant (fresh install), docker and virtual box.
Only ran vagrant up once.

Ok, think I might have found the issue. If I open the file via winscp (commander like scp/ftp tool) and change encoding to utf-8 then small change (add new line) then save. It works.

Can you please do that and open a PR with the changes?

will do, testing change from beginning quickly.

ok....no idea how to fix this.
I have changed the file encoding in windows to utf-8, destroyed everything and ran vagrant up. It had the same effect, cant execute the make-certs.sh.
If I open it through winscp (ssh to the vagrant master <IP_ADDRESS>:2222) and change the encoding from latin to utf-8 and then run manually. it works perfect.
It seems the encoding is either changed when creating the vagrant (coping the file) or the vagrant image`s default encoding is wrong.
I don't know enough about vagrant to fix this....will scratch around, but will be good if someone else can also scratch around.

create PR. stuffed up the first commit a bit. Fixed it.
Seems to work fine on mine now, once merged @remoe can try as well.
Will double check on my work pc tomorrow morning.

@remoe please try @potgieterdl PR and let me know.

>git clone https://github.com/potgieterdl/kubernetes-vagrant-coreos-cluster.git
>cd kubernetes-vagrant-coreos-cluster
>set NODES=0
>vagrant up

coreos:

core@master ~ $ systemctl status kube-certs.service -n1000
● kube-certs.service - Generate Kubernetes API Server certificates
   Loaded: loaded (/etc/systemd/system/kube-certs.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Tue 2015-09-29 19:35:33 UTC; 3min 1s ago
  Process: 1767 ExecStart=/tmp/make-certs.sh <IP_ADDRESS> IP:<IP_ADDRESS>,IP:<IP_ADDRESS>,DNS:kubernetes,DNS:kubernetes.default,DNS:kubernetes.default.svc,DNS:kubernetes.default.svc.cluster.local (code=exited, status=2)
  Process: 1765 ExecStartPre=/usr/bin/chmod 755 /tmp/make-certs.sh (code=exited, status=0/SUCCESS)
  Process: 1762 ExecStartPre=/usr/sbin/groupadd -r kube-cert (code=exited, status=9)
 Main PID: 1767 (code=exited, status=2)

Sep 29 19:35:33 master systemd[1]: Starting Generate Kubernetes API Server certificates...
Sep 29 19:35:33 master groupadd[1762]: groupadd: group 'kube-cert' already exists
Sep 29 19:35:33 master make-certs.sh[1767]: [27B blob data]
Sep 29 19:35:33 master make-certs.sh[1767]: Usage:        /bin/sh [GNU long option] [option] ...
Sep 29 19:35:33 master make-certs.sh[1767]: /bin/sh [GNU long option] [option] script-file ...
Sep 29 19:35:33 master systemd[1]: kube-certs.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Sep 29 19:35:33 master systemd[1]: Failed to start Generate Kubernetes API Server certificates.

Sep 29 19:35:33 master systemd[1]: kube-certs.service: Failed with result 'exit-code'.

@remoe try with #162.

@pires Pulled latest changes at work pc and getting same result as @remoe. I opened the make-certs file and removed lines around license at the top. Saved as utf-8 and destoryed the vagrant vm`s. Restared with vagrant up and now working fine.
I presume this might be a issue with the encoding of the file on windows and how it gets moved to the vm.

@potgieterdl @remoe can you vagrant ssh master and:
ls -las /tmp/make-certs.sh
cat /tmp/make-certs.sh

and paste results here?

I can't reproduce the issue on Win7x64 with fresh new git clone ...
CoreOS valpha (815.0.0)
Update Strategy: No Reboots
core@master ~ $ kubectl get nodes
NAME           LABELS                                STATUS
<IP_ADDRESS>   kubernetes.io/hostname=<IP_ADDRESS>   Ready
<IP_ADDRESS>   kubernetes.io/hostname=<IP_ADDRESS>   Ready
core@master ~ $

I don't thing I have changed anything that touch to utf-8 etc ...

vboxmanage -v
5.0.2r102096

vagrant version
Installed Version: 1.7.3
Latest Version: 1.7.4

@tdeheurles can you try upgrading to Vagrant 1.7.4 and give it a fresh try?

Yes, I'm going to try

vboxmanage -v
5.0.4r102546

vagrant version
Installed Version: 1.7.4
Latest Version: 1.7.4

git config --global core.eol lf
git config --global core.autocrlf false

CoreOS valpha (815.0.0)
Update Strategy: No Reboots
core@master ~ $ systemctl status kube-certs.service -n1000
● kube-certs.service - Generate Kubernetes API Server certificates
   Loaded: loaded (/etc/systemd/system/kube-certs.service; static; vendor preset: disabled)
   Active: active (exited) since Wed 2015-09-30 07:15:43 UTC; 4min 39s ago
  Process: 1517 ExecStart=/tmp/make-certs.sh <IP_ADDRESS> IP:<IP_ADDRESS>,IP:<IP_ADDRESS>,DNS:kubernetes,DNS:kubernetes.default,DNS:kubernetes.default.svc,DNS:kubernetes.default.svc.cluster.local (code=exited, status=0/SUCCESS)
  Process: 1514 ExecStartPre=/usr/bin/chmod 755 /tmp/make-certs.sh (code=exited, status=0/SUCCESS)
  Process: 1466 ExecStartPre=/usr/sbin/groupadd -r kube-cert (code=exited, status=0/SUCCESS)
 Main PID: 1517 (code=exited, status=0/SUCCESS)
   Memory: 0B
      CPU: 0
   CGroup: /system.slice/kube-certs.service

Sep 30 07:15:42 master systemd[1]: Starting Generate Kubernetes API Server certificates...
Sep 30 07:15:41 master groupadd[1466]: group added to /etc/group: name=kube-cert, GID=149
Sep 30 07:15:41 master groupadd[1466]: group added to /etc/gshadow: name=kube-cert
Sep 30 07:15:41 master groupadd[1466]: new group: name=kube-cert, GID=149
Sep 30 07:15:43 master make-certs.sh[1517]: 3
Sep 30 07:15:43 master make-certs.sh[1517]: 4
Sep 30 07:15:43 master systemd[1]: Started Generate Kubernetes API Server certificates.
Sep 30 07:15:50 master systemd[1]: Started Generate Kubernetes API Server certificates.

core@master ~ $  kubectl get nodes
NAME      LABELS    STATUS

core@master ~ $ systemctl list-jobs
No jobs running.

core@master ~ $ systemctl status
WARNING: terminal is not fully functional
● masters RETURN)
    State: running
     Jobs: 0 queued
   Failed: 0 units
    Since: Wed 2015-09-30 07:13:50 UTC; 8min ago
   CGroup: /
           ├─1 /usr/lib/systemd/systemd --switched-root --system --deserialize 21
           └─system.slice
             ├─docker-da90c7fd985a9b6f005c814252d9d10970bed2b8f96796504e0a7b253b09d39a.scope
             │ └─1411 /opt/bin/flanneld --ip-masq=true
             ├─dbus.service
             │ └─632 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
             ├─rpc-statd.service
             │ └─1092 /sbin/rpc.statd --no-notify
             ├─update-engine.service
             │ └─1635 /usr/sbin/update_engine -foreground -logtostderr
             ├─docker-83c02469fe962a4d32c7f50c3a4168ab55088b13f45190aa4d30ae3affff142d.scope
             │ ├─1309 /usr/bin/python /usr/bin/gunicorn --access-logfile - --error-logfile - --max-requests 100 -k gevent
             │ ├─1330 /usr/bin/python /usr/bin/gunicorn --access-logfile - --error-logfile - --max-requests 100 -k gevent
             │ ├─1331 /usr/bin/python /usr/bin/gunicorn --access-logfile - --error-logfile - --max-requests 100 -k gevent
             │ ├─1332 /usr/bin/python /usr/bin/gunicorn --access-logfile - --error-logfile - --max-requests 100 -k gevent
             │ └─1333 /usr/bin/python /usr/bin/gunicorn --access-logfile - --error-logfile - --max-requests 100 -k gevent
             ├─system-sshd.slice
             │ ├─sshd@0-<IP_ADDRESS>:22-<IP_ADDRESS>:12786.service
             │ │ ├─750 sshd: core [priv]
             │ │ └─765 sshd: core@notty
             │ └─sshd@2-<IP_ADDRESS>:22-<IP_ADDRESS>:13078.service
             │   ├─1696 sshd: core [priv]
             │   ├─1698 sshd: core@pts/0
             │   ├─1699 -bash
             │   ├─1726 systemctl status
             │   └─1727 systemctl status
             ├─systemd-journald.service
             │ └─482 /usr/lib/systemd/systemd-journald
             ├─fleet.service
             │ └─1272 /usr/bin/fleetd
             ├─kube-controller-manager.service
             │ └─1620 /opt/bin/kube-controller-manager --root-ca-file=/srv/kubernetes/ca.crt --service-account-private-key
             ├─systemd-resolved.service
             │ └─655 /usr/lib/systemd/systemd-resolved
             ├─systemd-timesyncd.service
             │ └─595 /usr/lib/systemd/systemd-timesyncd
             ├─systemd-logind.service
             │ └─628 /usr/lib/systemd/systemd-logind
             ├─systemd-networkd.service
             │ └─933 /usr/lib/systemd/systemd-networkd
             ├─system-getty.slice
             │<EMAIL_ADDRESS>             │   └─629 /sbin/agetty --noclear tty1 linux
             ├─systemd-udevd.service
             │ └─508 /usr/lib/systemd/systemd-udevd
             ├─kube-scheduler.service
             │ └─1628 /opt/bin/kube-scheduler --master=<IP_ADDRESS>:8080
             ├─docker-cache.service
             │ └─1269 /usr/bin/docker run --rm --net host --name docker-registry -e STANDALONE=false -e GUNICORN_OPTS=[--p
             ├─rpcbind.service
             │ └─1090 /sbin/rpcbind
             ├─early-docker.service
             │ └─1093 docker daemon --host=fd:// --bridge=none --iptables=false --ip-masq=false --graph=/var/lib/early-doc
             ├─kube-apiserver.service
             │ └─1609 /opt/bin/kube-apiserver --client-ca-file=/srv/kubernetes/ca.crt --tls-cert-file=/srv/kubernetes/serv
             ├─docker.service
             │ └─1455 docker daemon --host=fd:// --registry-mirror=http://<IP_ADDRESS>:5000 --bip=<IP_ADDRESS>/24 --mtu=150
             ├─etcd2.service
             │ └─1276 /usr/bin/etcd2
             └─flanneld.service
               ├─1352 /usr/libexec/sdnotify-proxy /run/flannel/sd.sock /usr/bin/docker run --net=host --privileged=true --
               └─1356 /usr/bin/docker run --net=host --privileged=true --rm --volume=/run/flannel:/run/flannel --env=NOTIFcore@master ~

vagrant:              1.7.4
start time:  12 minutes

 kubectl get nodes
NAME           LABELS                                STATUS
<IP_ADDRESS>   kubernetes.io/hostname=<IP_ADDRESS>   Ready
<IP_ADDRESS>   kubernetes.io/hostname=<IP_ADDRESS>   Ready

@remoe seems fine for last start, just need to start with some NODES

@remoe: WARNING: terminal is not fully functional ==> should have a look to babun, if you have any issue with it, just mail me questions<EMAIL_ADDRESS>

I agree with @tdeheurles assessment.
So it seems the trick is
git config --global core.eol lf
git config --global core.autocrlf false

?

In any case we should add a gitattributes to the project. I look for one.

@tdeheurles on my way!

It's something like that:
# Set the default behavior, in case people don't have core.autocrlf set.
* text=auto

# Explicitly declare text files you want to always be normalized and converted
# to native line endings on checkout.
*.sh text
*.yaml text
*.tmpl text
Vagrantfile text

text correspond to lf

@pires, @tdeheurles , congrats it WORKS!
It takes a lot of time to start this nodes :/
What are your strategies to debug/develop this environment? On every change you start the whole thing?
$ vagrant ssh master
CoreOS valpha (815.0.0)
Update Strategy: No Reboots
core@master ~ $ kubectl get nodes
NAME           LABELS                                STATUS
<IP_ADDRESS>   kubernetes.io/hostname=<IP_ADDRESS>   Ready
<IP_ADDRESS>   kubernetes.io/hostname=<IP_ADDRESS>   Ready

Bringing machine 'master' up with 'virtualbox' provider...
Bringing machine 'node-01' up with 'virtualbox' provider...
Bringing machine 'node-02' up with 'virtualbox' provider...
==> master: Running triggers before up...
==> master: Setting Kubernetes version 1.0.6
==> master: Configuring Kubernetes cluster DNS...
==> master: Importing base box 'coreos-alpha'...
==> master: Matching MAC address for NAT networking...
==> master: Checking if box 'coreos-alpha' is up to date...
==> master: Setting the name of the VM: kubernetes-vagrant-coreos-cluster_master_1443599592654_61835
==> master: Clearing any previously set network interfaces...
==> master: Preparing network interfaces based on configuration...
    master: Adapter 1: nat
    master: Adapter 2: hostonly
==> master: Forwarding ports...
    master: 22 => 2222 (adapter 1)
==> master: Running 'pre-boot' VM customizations...
==> master: Booting VM...
==> master: Waiting for machine to boot. This may take a few minutes...
    master: SSH address: <IP_ADDRESS>:2222
    master: SSH username: core
    master: SSH auth method: private key
    master: Warning: Remote connection disconnect. Retrying...
==> master: Machine booted and ready!
==> master: Setting hostname...
==> master: Configuring and enabling network interfaces...
==> master: Running provisioner: file...
==> master: Running provisioner: file...
==> master: Running provisioner: file...
==> master: Running provisioner: file...
==> master: Running provisioner: file...
==> master: Running provisioner: shell...
    master: Running: inline script
==> master: Running triggers after up...
==> master: Sanitizing stuff...
Could not open a connection to your authentication agent.
==> master: Installing kubectl for the kubernetes version we just bootstrapped...
==> master: Executing remote command "sudo -u core /bin/sh /home/core/kubectlsetup install"...
==> master: Downloading and installing linux version of 'kubectl' v1.0.6 into /opt/bin. This may take a couple minutes, depending on your internet speed..
==> master: Setting environment variables..
==> master: Remote command execution finished.
==> master: Waiting for Kubernetes master to become ready...
==> master: Executing remote command "/opt/bin/kubectl create -f /home/core/dns-controller.yaml"...
==> master: replicationcontrollers/kube-dns
==> master: Remote command execution finished.
==> master: Executing remote command "/opt/bin/kubectl create -f /home/core/dns-service.yaml"...
==> master: services/kube-dns
==> master: Remote command execution finished.
==> node-01: Importing base box 'coreos-alpha'...
==> node-01: Matching MAC address for NAT networking...
==> node-01: Checking if box 'coreos-alpha' is up to date...
==> node-01: Setting the name of the VM: kubernetes-vagrant-coreos-cluster_node-01_1443599715103_77861
==> node-01: Fixed port collision for 22 => 2222. Now on port 2200.
==> node-01: Clearing any previously set network interfaces...
==> node-01: Preparing network interfaces based on configuration...
    node-01: Adapter 1: nat
    node-01: Adapter 2: hostonly
==> node-01: Forwarding ports...
    node-01: 22 => 2200 (adapter 1)
==> node-01: Running 'pre-boot' VM customizations...
==> node-01: Booting VM...
==> node-01: Waiting for machine to boot. This may take a few minutes...
    node-01: SSH address: <IP_ADDRESS>:2200
    node-01: SSH username: core
    node-01: SSH auth method: private key
    node-01: Warning: Remote connection disconnect. Retrying...
==> node-01: Machine booted and ready!
==> node-01: Setting hostname...
==> node-01: Configuring and enabling network interfaces...
==> node-01: Running provisioner: file...
==> node-01: Running provisioner: file...
==> node-01: Running provisioner: shell...
    node-01: Running: inline script
==> node-01: Running triggers after up...
==> node-01: Waiting for Kubernetes minion [node-01] to become ready...
==> node-02: Importing base box 'coreos-alpha'...
==> node-02: Matching MAC address for NAT networking...
==> node-02: Checking if box 'coreos-alpha' is up to date...
==> node-02: Setting the name of the VM: kubernetes-vagrant-coreos-cluster_node-02_1443599777702_24048
==> node-02: Fixed port collision for 22 => 2222. Now on port 2201.
==> node-02: Clearing any previously set network interfaces...
==> node-02: Preparing network interfaces based on configuration...
    node-02: Adapter 1: nat
    node-02: Adapter 2: hostonly
==> node-02: Forwarding ports...
    node-02: 22 => 2201 (adapter 1)
==> node-02: Running 'pre-boot' VM customizations...
==> node-02: Booting VM...
==> node-02: Waiting for machine to boot. This may take a few minutes...
    node-02: SSH address: <IP_ADDRESS>:2201
    node-02: SSH username: core
    node-02: SSH auth method: private key
    node-02: Warning: Connection timeout. Retrying...
==> node-02: Machine booted and ready!
==> node-02: Setting hostname...
==> node-02: Configuring and enabling network interfaces...
==> node-02: Running provisioner: file...
==> node-02: Running provisioner: file...
==> node-02: Running provisioner: shell...
    node-02: Running: inline script
==> node-02: Running triggers after up...
==> node-02: Waiting for Kubernetes minion [node-02] to become ready...

@remoe master takes a while because of the Docker cache, which will speed up your development in the future by reusing local images instead of downloading them again. And while you feel this may be slow, you should try the official way then and then let us know ;)
@remoe care to try #163?

Yes VM are loooooooonnng to start ...
I'm looking for a docker/container way but Windows is so problematic with containers for now.
There was an issue here but that project have been a great kubernetes start for month now.
Hard to do better than:
git clone ..
vagrant up

no ?

@pires, I tested it again with '158-fix_line_ending' - branch. It works.

@remoe awesome! @gngeorgiev @potgieterdl @brunomacf care to try one more time with #163?

Just remind to add the code below to .gitattributes if it doesn't work for the next one.
*.sh text
*.yaml text
*.tmpl text
Vagrantfile text

This:
git config --global core.eol lf
git config --global core.autocrlf false

is global, so it will works now for the different projects.
I'm not sure that * text=auto is enough.
The way I understand it is to follow the global rules define above.
We will see ^^

.gitattributes will work per repo. We can override eol and autocrlf too and that's why I'm asking people to give it a try.

@tdeheurles, hey thank you for this babun link!! awesome! I used http://cmder.net/ ... but I had some terminal issues.

@remoe no problem (didnt know that cmder)

I tried with both master and the e6670b4 commit. Getting the following:
==> master: Executing remote command "/opt/bin/kubectl create -f /home/core/dns-controller.yaml"...
==> master: error: could not read an encoded object from /home/core/dns-controller.yaml: unable to connect to a server to handle "replicationcontrollers": couldn't read version from server: Get http://localhost:8080/api: dial tcp <IP_ADDRESS>:8080: connection refused
==> master: error: no objects passed to create
==> master: Remote command execution finished.
The command "/opt/bin/kubectl create -f /home/core/dns-controller.yaml" returned a failed exit code. The
error output is shown below:

error: could not read an encoded object from /home/core/dns-controller.yaml: unable to connect to a server to handle "replicationcontrollers": couldn't read version from server: Get http://localhost:8080/api: dial tcp <IP_ADDRESS>:8080: connection refused

error: no objects passed to create

I'm behind a corporate proxy, which I'm battling with on other grounds. I've checked and I don't have an existing ~/.kube directory. My host is windows.
Could this be related?

A lot of Windows users seem to be complaining.

Closing this in order to get more feedback from Windows users. Before providing more feedback, please test with latest changes.

hi @pires, can you just describe me shortly what you want to test on windows. Will make a try.
For others: windows create a lot of issues as most of the parts are different:

the filesystem
the endofline
...

For that you need to prepare your git client to clone with that :
git config --global core.eol lf
git config --global core.autocrlf false

Then finally clone the repository and have a look to that (before running vagrant up) :
git status

It should tell you if the files have been changed.
==> Lots of issue take their source in the script that need to configure everything are broken on windows


3 actions: AddAndCommit, CreateBranch and PullRequest

I added three actions:

action: AddAndCommitV8 https://github.com/EndBug/add-and-commit
action: CreateBranchV210 https://github.com/peterjgrainger/action-create-branch
action: PullRequestV2 https://github.com/repo-sync/pull-request

With them, I was to built the challenge I had for myself to convert to Kotlin
the YAML workflow from this article https://akjaw.com/keeping-gradle-dependencies-up-to-date-with-github-actions-and-refreshversions/
which brings dependabot-like feature to my software https://jmfayard.github.io/refreshVersions/
It is working here: https://github.com/LouisCAD/kotlin-libraries-playground/pull/115
Actually I had to tweak it manually to able to make it work, I need support for GitHub variables https://github.com/krzema12/github-actions-kotlin-dsl/issues/26

Please ensure that these wrappers work, after the changes around versions (v2.1.0 -> v2 may be an incorrect suggestion from my side).


ARROW-14778: [C++] Round mean of decimal types after division

With this, the mean and hash_mean aggregate kernels will accumulate sums and perform the final division with decimal values, but the final division will be rounded away from zero (towards infinity) based on the remainder after division instead of rounding towards zero (truncating).

You mention this in the Jira, but could we add in the cast back to decimal proactively? What I'm seeing in postgres (haven't tried others yet) is it "just" blows up the precision on the decimal but does still return a decimal with AVG.
If someone has a decimal already it seems odd that it would return a double when a decimal result is possible (it's not quite like division of integers where you have to return something with more precision than an integer there). Even of (for now? until someone complains?) we cast back to the same decimal precision as the input, I think that would be more natural for what operations on decimals like this behave like elsewhere.
postgres=# create table df (dec decimal(3, 2));
                insert into df (dec) values (0.01);
                insert into df (dec) values (0.02);
                insert into df (dec) values (0.02);
                insert into df (dec) values (0.02);
CREATE TABLE
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
postgres=# alter table df add column flt float;
                insert into df (flt) values (0.01);
                insert into df (flt) values (0.02);
                insert into df (flt) values (0.02);
                insert into df (flt) values (0.02);
ALTER TABLE
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
postgres=# select pg_typeof(dec), pg_typeof(flt) from df;
 pg_typeof |    pg_typeof
-----------+------------------
 numeric   | double precision
 numeric   | double precision
 numeric   | double precision
 numeric   | double precision
 numeric   | double precision
 numeric   | double precision
 numeric   | double precision
 numeric   | double precision
(8 rows)

postgres=# select AVG(dec), pg_typeof(AVG(dec)), AVG(flt), pg_typeof(AVG(flt)) from df;
          avg           | pg_typeof |  avg   |    pg_typeof
------------------------+-----------+--------+------------------
 0.01750000000000000000 | numeric   | 0.0175 | double precision

Just for reference it seems DuckDB actually outputs a double:
D create table df (dec decimal(3, 2), flt float);
D insert info df (dec, flt) values (0.01, 0.01);
Error: Parser Error: syntax error at or near "info"
LINE 1: insert info df (dec, flt) values (0.01, 0.01);
               ^
D insert into df (dec, flt) values (0.01, 0.01);
D insert into df (dec, flt) values (0.02, 0.02);
D insert into df (dec, flt) values (0.02, 0.02);
D insert into df (dec, flt) values (0.02, 0.02);
D select typeof(dec), typeof(flt) from df;
┌──────────────┬─────────────┐
│ typeof(dec)  │ typeof(flt) │
├──────────────┼─────────────┤
│ DECIMAL(3,2) │ FLOAT       │
│ DECIMAL(3,2) │ FLOAT       │
│ DECIMAL(3,2) │ FLOAT       │
│ DECIMAL(3,2) │ FLOAT       │
└──────────────┴─────────────┘
D select avg(dec), avg(flt), typeof(avg(dec)), typeof(avg(flt)) from df;
┌──────────┬─────────────────────┬──────────────────┬──────────────────┐
│ avg(dec) │      avg(flt)       │ typeof(avg(dec)) │ typeof(avg(flt)) │
├──────────┼─────────────────────┼──────────────────┼──────────────────┤
│ 0.0175   │ 0.01749999960884452 │ DOUBLE           │ DOUBLE           │
└──────────┴─────────────────────┴──────────────────┴──────────────────┘

We can cast back to Decimal, but how should we round/truncate the result?

nods yeah. We can ask them what their philosophy is there. I'm not sure I know the history.
As for round/trunc I would vote for rounding to whatever the precision is (if we truncate we'll get the same result we have now IIRC). Or if it's easier to do the postgres blow up precision to max, that would be ok by me

I would say that if the summation is done as decimal, then the result should probably be decimal as well. People use decimals when floats are not adequate, AFAIK.

Reverted the original change and instead added a rounding step directly on the decimal result.

This looks good to me. Someone with more C++ should probably look at the code in more detail, though

Thanks for the reminder, I've updated the title/description.

Thanks for the reminder, I've updated the title/description.

round half toward infinity?

Thanks for the reminder, I've updated the title/description.

round half toward infinity?

Ah yup, that's right, thanks.


Silence RemovedInDjango110Warning

Silence RemovedInDjango110Warning for the renamed/moved package.
https://docs.djangoproject.com/en/1.9/releases/1.8/#qn-replaced-by-compiler

Sorry, it looks like this breaks compatibility with Django < 1.9 and I don't want to break compatibility. Also, it looks like your commit is based on master; if you want to remove the extraaneous commits, rebase on develop. Thanks for the PR!

A lot of these were taken care of in https://github.com/alex/django-taggit/pull/385. Open a new PR if you see any more!


Compilation under Windows and Linux were different.

Fixed problem with different compilation.
Preview bug:
http://i.cubeupload.com/l9a25u.png - included file
http://i.cubeupload.com/pA4LVu.png - result, left - windows, right - linux

Hey there,
thanks for the addition. This makes a lot of sense. However, would you mind adjusting the tests as well. It seems to only break 3 test. I would probably push that as a minor version at least. I think we have at least one other thread with a feature for a major push.
It would definitely land in there.

I'v merged your changes into a v2.0 branch. I won't merge this into master quite yet but it's on the way.


MGDCTRS-1789: OpenAPI rest connector doesn't set the Content-Type header

MGDCTRS-1789: OpenAPI rest connector doesn't set the Content-Type header
chore: remove duplicated declaration of camel-quarkus-jq dependency

@lburgazzoli I am curious, which change in the PR exactly fixes the problem? How did the problem come about in the first place?

@lburgazzoli I am curious, which change in the PR exactly fixes the problem? How did the problem come about in the first place? Merely f7113a?

The root cause is wrong configuration of the data shape [1] - which is probably the result of copy&paste - that forced the connector to encode the data as base64 causing the petstore server to fail.
[1] https://github.com/bf2fc6cc711aee1a0c2a/cos-fleet-catalog-camel/pull/568/files#diff-faefc1ef496a72be8b030feb7f3fe5f962e8b16d9986eff9bbcd44b663ac461bL52-L58


Handling other plugin unloading better

Changes

Checking to see if plugin that is being unloaded is this plugin, before disposing component

Motivation
This listener hears all of the plugins being unloaded, so if a user uninstalls any other dynamic plugin, the tinter looses config updates until restart.

I am a bit confused... why would this component's listeners be executed for  plugins?

Sorry for not including steps to replicate:

Install One Dark Theme
Remove One Dark
Observe that the listener is called with the unloaded One-Dark plugin

Apparently the listeners to this topic get to see all the plugins.

Aaaah... I understand now. Okay!


Change the default value of install_salt_bundle to true

What does this PR change?
This PR change the default value of install_salt_bundle variable in the majority of modules.
It keeps untouched the host modules from other backends.
The aim of this refactor is to simplify our main.tf for most of our environments, where we were replacing the value of this variable in almost all the cases.

Not tested yet.


chore(main): release 4.1.1

:robot: I have created a release beep boop
4.1.1 (2024-09-24)
Bug Fixes

token (6278def)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v4.1.1
:sunflower:


Random Quotes Generator

Aim

to generate random quotes on user given category
to generate n number of quotes where n is the user input

Details

this script allows user to get random quotes based on the category they have opt to and also the n number of quotes they needed under that category.

@1e9abhi1e10 abd @avinashkranjan please assign this issue to me .!!

@pavansai5448 How's it different from this?
https://github.com/avinashkranjan/Amazing-Python-Scripts/tree/master/Random-Quote-generator

@Yashbhadiyadra
my script gives random n number of quotes based on the user selected category , whereas the other script doesn't

Go ahead @pavansai5448


fixes issue #1290

Unfortunately, I've just merged a PR which means that this needs to be implemented against https://github.com/slimphp/Slim/blob/develop/Slim/Http/Stream.php.

@akrabat, ok, i have changed it.

Changes Unknown when pulling a5d98f3c511a8ad63c864625cf57023176720575 on HardieBoeve:fix-issue-1290 into ** on slimphp:develop**.


feat(temp-role): add temporary role system

[x] basic temprole
- [ ] temprole for Giveaway

for the giveaway temp role i will transfer it to another branch

Possible bug: If two identical roles are added to one user, there will be an overlap, causing the second command to be ignored. It still exists in the table but is not used until the same condition again.

tested, lgtm
https://discord.com/channels/761644411486339073/774322083319775262/1269293768352333875


Mm 43597

Summary
For Cloud instances that hit the message history limit, show the limits reached modal to admins that are doing a fresh login.
Ticket Link
https://mattermost.atlassian.net/browse/MM-43597
Screenshots
Clip of admin not seeing the modal until they re log-in, and of regular user (nn2) not seeing the modal at all on log in.
Release Note
For Cloud instances that hit the message history limit, show the limits reached modal to admins that are doing a fresh login.

E2E tests not automatically triggered, because PR has no approval yet. Please ask a developer to review and then try again to attach the QA label.

/e2e-test

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/234194


Consolidate and update Borsh for TS/JS

Currently we have three different implementation of TS/JS that have slightly different functionality and bugs:

https://github.com/nearprotocol/borsh
https://github.com/nearprotocol/nearlib/blob/master/src.ts/utils/serialize.ts
https://github.com/nearprotocol/near-bridge/blob/master/ethrelay/index.js

We should unify them into one implementation that lives in https://github.com/nearprotocol/borsh .
Also, https://github.com/nearprotocol/borsh/pull/57 and https://github.com/nearprotocol/borsh/pull/56 introduced a slightly modified Borsh schema format which now allows serializing any Rust types, even with generics, and it is not Rust-specific. We should make sure we follow this new schema format.
Note, as requested by @vgrichina Borsh Schema is in Borsh format rather than JSON.

@nearmax Is this the correct list of TODOs?

Update borsh-ts and borsh-js to the new schema
Replace usage of nearlib/utils/serialize with borsh-ts
Replace custom serializer in near-bridge/eth-relay with borsh-js

There are few important points that shouldn't be missed:

borsh-ts is most out of date and untested implementation, but it ultimately should be destination where new implementation lands
https://github.com/nearprotocol/nearlib/blob/master/src.ts/utils/serialize.ts likely has the best error handling (e.g. keeping track of field path so that you can see where exactly stuff fails: https://github.com/near/near-api-js/blob/092d6477854906e51a59a406f0587b1174e4d02b/src.ts/utils/serialize.ts#L287). It also uses js-fuzz which helps to find bugs with implementation. Likely nearlib is the best starting point for new implementation.
https://github.com/nearprotocol/near-bridge/blob/master/ethrelay/index.js improves one thing which is important to fix elsewhere – Borsh schema doesn't depend on JS constructors anymore (fragile and breaks in many weird environments).  Compare https://github.com/nearprotocol/near-bridge/blob/75fab60c92b672a9f86e633a2ea66bdad5af8bfb/ethrelay/index.js#L301 and https://github.com/near/near-api-js/blob/092d6477854906e51a59a406f0587b1174e4d02b/src.ts/transaction.ts#L126

@kcole16 I don't know how I missed your comment.

@nearmax Is this the correct list of TODOs?

Update borsh-ts and borsh-js to the new schema
Replace usage of nearlib/utils/serialize with borsh-ts
Replace custom serializer in near-bridge/eth-relay with borsh-js

Yes, correct.
@vgrichina

borsh-ts is most out of date and untested implementation, but it ultimately should be destination where new implementation lands

I agree.

improves one thing which is important to fix elsewhere – Borsh schema doesn't depend on JS constructors anymore

This is an important improvement, which will allow us in the future to directly convert JSON to Borsh using Borsh schema

@vgrichina Please also note that this is not blocking our Mainnet launch, so we have removed it from Mainnet release in Zenhub last week. If you have other items that are blocking the Mainnet launch then you might consider them more important.

@nearmax re mainnnet priorities we likely need to do smth about RPCs. Looks like long polling on nearcore side works bad (e. g. tx-status for non existing hash). This will require changes both in nearcore and in nearlib, though should be pretty localized.

@nearmax re mainnnet priorities we likely need to do smth about RPCs. Looks like long polling on nearcore side works bad (e. g. tx-status for non existing hash). This will require changes both in nearcore and in nearlib, though should be pretty localized.

Yes, but these changes look orthogonal to Borsh changes. CC @frol

This issue indeed looks orthogonal to the RPC.
I agree that RPC and the whole node need benchmarks () and load testing. We have tracking issues for those and will work on those items in the near future.
RPC polling is never a good idea, and we will need to implement some streaming APIs, but this can be done after the mainnet, I believe.

@kcole16 , @vgrichina We need to bump priority on this. Flux has been asking examples on JS-side Borsh serialization, which we cannot do until we consolidate different implementations.

Requires: https://github.com/near/borsh/issues/71

@vgrichina @nearmax this issues is a bit outdated

[ ] Update borsh-ts and borsh-js to the new schema
[ ] Replace usage of nearlib/utils/serialize with borsh-ts
[ ] Replace custom serializer in near-bridge/eth-relay with borsh-js (has it's own issue here: https://github.com/near/rainbow-bridge/issues/438)

should we consider Update borsh-ts and borsh-js to the new schema as a P1?

@volovyk-s not sure it’s a P1 but it’s relatively important as would solve the problem with using multiple near-api-js instances in your app. Basically the idea is to avoid relying on constructor instances to identify schema.

Closing this issue since it's not relevant to near-api-js anymore. borsh-js schema should be fixed in https://github.com/near/borsh-js/issues/10


Integrate drag and drop api

Cherry-pick the following PRs:
https://github.com/microsoft/vscode/pull/122239
https://github.com/microsoft/vscode/pull/123542
https://github.com/microsoft/vscode/pull/128666

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 42.47%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
26784

Relevant Lines:
57118

💛  - Coveralls


Add a experimental expandable control-strip

Related to https://github.com/muxinc/media-chrome/discussions/123
This adds a new component to make it super easy to add an expandable part in the control bar like
https://en.wikipedia.org/wiki/Control_Strip
For the volume range but can also work like in the Apple Magic touch bar where part of the controls are hidden and there is a special expand button.
Still experimental and needs a few more attributes to make it work like the magic touch bar.
Also thoughts on accessibility are welcome.
https://media-chrome-git-fork-luwes-control-strip-mux.vercel.app/examples/advanced.html

It'll be good to try and do all the opening stuff via css-only rather than events in JS. Makes it easier to make sure that things work properly for both mouse and keyboard and screen readers.

I've been wanting to build this for a player for a while now but never got to it.
to me this seems a nicer solution than having the "gear icon" with a panel and sub menu panels like the YT player.
it's similar to Wistia in mobile view but they choose to fully hide all right side controls. Best to keep as many as possible still visible with the available space. Could even be smart about which ones to be visible, like the ones which are interacted with the most.
I'm also not sure if it needs to be part of Media Chrome, it's possible to make it even more generic since it's just a UI component.

closing for now, needs more polishing


Create first release on Sonartype/Maven Central

See instructions on https://issues.sonatype.org/browse/OSSRH-80456 and https://issues.sonatype.org/browse/OSSRH-80457

Congratulations! Welcome to the Central Repository!
io.github.ascopes has been prepared, now user(s) ascopes can:
Publish snapshot and release artifacts to s01.oss.sonatype.org
Have a look at this section of our official guide for deployment instructions:
https://central.sonatype.org/publish/publish-guide/#deployment
Depending on your build configuration, your first component(s) might be released automatically after a successful deployment.
If that happens, you will see a comment on this ticket confirming that your artifact has synced to Maven Central.
If you do not see this comment within an hour or two, you can follow the steps in this section of our guide:
https://central.sonatype.org/publish/release/

As part of our efforts to improve the security and quality posture of the open source supply chain,
we plan to enable additional scanning of dependencies for security alerts soon. Since you're already
hosting your source code in Github, you can get these insights today by enabling Sonatype Lift.
Sonatype Lift is free forever on public repositories! Lift tells you about open source
vulnerabilities
during code review, and goes beyond open source to scan your code for both code quality and security issues,
providing feedback right in your pull requests.
More information can be found at https://links.sonatype.com/products/lift/github-integration

Depends on #135, #136.
I will make a 0.0.1-M1 release first to verify the pipelines.

https://github.com/ascopes/java-compiler-testing/releases/tag/v0.0.1-M1


@Tdortiz ASAP. I want to take advantage of your PR to merge other dependencies upgrades pull requests. 😉


Zlib decoder calls reduction and index fix

Motivation:
The JdkZlibDecoder and JZlibDecoder call isReadable and readableBytes in the same method. There is an opportunity to reduce the number of methods calls to just use readableBytes.  JdkZlibDecoder reads from a ByteBuf with an absolute index instead of using readerIndex()
Modifications:

Use readableBytes where isReadable was used
Correct absolute ByteBuf index to be relative to readerIndex()

Result:
Less method calls duplicating work and preventing an index out of bounds exception.

@normanmaurer @trustin - FYI.  This is based upon https://github.com/netty/netty/pull/3344#discussion_r23516644

@Scottmitch thx cherry-picked


cucumber-json-formatter for macOS is not working (cucumber-json-formatter ENOENT)

After run the tests an error is displayed:
An error was thrown in your plugins file while executing the handler for the after:run event.
The error we received was:
Error: spawn cucumber-json-formatter ENOENT
at Process.ChildProcess._handle.onexit (node:internal/child_process:283:19)
at onErrorNT (node:internal/child_process:478:16)
at processTicksAndRejections (node:internal/process/task_queues:83:21)
I downloaded the file cucumber-json-formatter-darwin-amd64 and followed the steps as described in the readme, but this error is displayed.
Obs: I using macOS with apple silicon chip (M1)
My .cypress-cucumber-preprocessorrc.json file:
{
"json": {
"enabled": true,
"output": "jsonlogs/log.json",
"formater": "cucumber-json-formatter"
},
"messages": {
"enabled": true,
"output": "jsonlogs/messages.ndjson"
},
"stepDefinitions": [
"[filepath]/**/.{js,ts}",
"[filepath].{js,ts}",
"cypress/support/step_definitions/.{js,ts}"
]
}

I have same issue on Mac
Error: spawn cucumber-json-formatter ENOENT

I am trying to migrate cypress to 10+, but I am getting an error while creating the cucumber report as below on M1 mac, could anyone please help me with it.
An error was thrown in your plugins file while executing the handler for the after:run event.
The error we received was:
Error: spawn cucumber-json-formatter ENOENT at Process.ChildProcess._handle.onexit (node:internal/child_process:283:19) at onErrorNT (node:internal/child_process:478:16) at processTicksAndRejections (node:internal/process/task_queues:83:21)
Have the same issue like above
Thank you!

FYI, this project and its authors have no relationship with Cypress nor the cypress-cucumber-preprocessor.
The errors mentioned here indicated that you have not successfully made the executable available in your PATH. The PATH variable has to include a directory containing cucumber-json-formatter (or whichever name you've configured) and it has to have execute permissions. Any failure in this results in ENOENT.

@badeball Thanks for the update,
cucumber-json-formatter is in path of cypress project and have the below config
{
    "json": {
      "enabled": true,
      "output": "jsonlogs/log.json",
      "formater": "cucumber-json-formatter"
    },
    "messages": {
      "enabled": true,
      "output": "jsonlogs/messages.ndjson"
    },
    "html": {
      "enabled": true
    },
    "stepDefinitions": [
        "[filepath]/**/*.{js,ts}",
        "[filepath].{js,ts}",
        "cypress/e2e/step_definitions/*.{js,ts}"
    ]
}

I did the samething on windows, its working fine, but facing this issue on mac
Could you please provide little insight of it
Thank you!

Hi.
I have been trying to get the cucumber-json-formatter working on my MacBook. I have been using the instructions on their GitHub page - https://github.com/cucumber/json-formatter
I followed these steps (as suggested on the GitHub page):-
MacOS

Download cucumber-json-formatter-darwin-amd64 and rename it to cucumber-json-formatter

Move it to a directory that's on your PATH

Make it executable with chmod +x cucumber-json-formatter

Verify that you can run it: cucumber-json-formatter --help
At the last step, you may get a security warning from MacOS. If you do, open System Preferences. Go to Security Settings. You should see a question asking if you want to open it anyway. Say yes.

When I run the command in step 4. I get the following error:-
cucumber-json-formatter: command not found
Further information - I am doing this on a  M1 MacBook.

I have an M1 Mac and what I needed to do for step 4 to work was manually opening the cucumber-json-formatter file, only then my Mac allowed me to use it.
Besides that, make sure to open a new terminal session to read your updated PATH , run echo $PATH just for the sake of it and if you can see your folder containing the cucumber-json-formatter, then cucumber-json-formatter --help should work

Hi a8rejo. When you say manually open the cucumber-json-formatter, what do you mean? Double click on the file?

Hi @a8trejo I double clicked on the cucumber-json-formatter file, and allowed the permission, but the error is the same.

@ashort-zaizi yes, as @adinizs did
@adinizs when you run echo $PATH do you see the folder where your cucumber-json-formatter file is?
If it helps for reference, this is what I do on a Github Actions workflow to get it working too,
- name: Set Up Environment
        run: |
          mkdir cypress/config/cucumber_json
          echo "${{ github.workspace }}/cypress/config/cucumber_json" >> $GITHUB_PATH
          cd cypress/config/cucumber_json
          curl https://github.com/cucumber/json-formatter/releases/download/v19.0.0/cucumber-json-formatter-linux-amd64 -o cucumber-json-formatter
          chmod +x cucumber-json-formatter

as for how to set the folder where cucumber-json-formatter is located, into your PATH, if I have it in /Users/myUserName/Workspace/tools/path/cucumber-json-formatter  I do it with:
vi ~/.zprofile
and I add:
# Cucumber Standalone JSON Formatter
CUSTOM_FOLDER=/Users/myUserName/Workspace/tools/path
export PATH=$CUSTOM_FOLDER:$PATH

I set this information in my .zprofile, but the error is the same. @a8trejo
# Cucumber Standalone JSON Formatter CUSTOM_FOLDER=/Users/diniz/Projects/qa export PATH=$CUSTOM_FOLDER:$PATH

Also close and reopen Visual Studio or the terminal so it reads the system variable again, if that still doesn't work, I'm out of ideas ^^

@adinizs what is the output of your echo $PATH ?

I got it!!
Steps for success:
MacOS

Download cucumber-json-formatter-darwin-amd64 and rename it to cucumber-json-formatter
Move it to a directory that's on your PATH
Set in your ~/.zprofile the follow information:

# Cucumber Standalone JSON Formatter
CUSTOM_FOLDER=/Users/YourUser/Workspace/path
export PATH=$CUSTOM_FOLDER:$PATH

Restart yout terminal and VS Code (or your code editor)
Make it executable with chmod +x cucumber-json-formatter
Verify that you can run it: cucumber-json-formatter --help

Thank you @a8trejo !!

happy to help! :D

I have added cucumber-json-formatter to my PATH . I have updated my system preferences to allow my MacBook to open the cucumber-json-formatter executable.
When I open a terminal window and run the following command :--
cucumber-json-formatter --help
I can see that I have configured my PATH variable correctly as I see this response in the terminal window:-
Usage of cucumber-json-formatter:
When I open VSCode and open a terminal window with VSCode and run the following command:-
cucumber-json-formatter --help
I get this response:-
bash: cucumber-json-formatter: command not found
I have tried closing and re-opening VSCode, but I see the same error. Im very confused in what to do now. Any help would be great. Thanks!

I found the problem!!
in macOS we need to create a .bash_profile file, in this file we need to add environmental variables and add macOS path.
Maybe I don't describe very well the solution but I gonna attach a imag
Steps:

macOS
*Download cucumber-json-formatter-darwin-amd64 and rename it to cucumber-json-formatter
*Move it to a directory that's on your PATH
*Make it executable with chmod +x cucumber-json-formatter

2.Create file .bash_profile

Add into .bash_prifile the next:3:3.
export CUSTOM_FOLDER="directory that's on your PATH. the same in the step 1 "
export PATH=$CUSTOM_FOLDER:$PATH

Open terminal an run an type source ~/.bash_profile (activate environment variables)

Verify that you can run it: cucumber-json-formatter --help

It depends on your MAC Operating system, ~/.bash_profile won't work for all MACs, ~/.zprofile works in mine, but the root cause/solution is the same
Make the system variable $PATH (nothing related to any cypress config file or path at all), includes the path where cucumber-json-formatter is
How to update the system variable $PATH , changes depending on the operating system

FIX:
Have stumbled a similar issue when I was following a certain course and was able to make it work by adding the
"./" inside the formatter

and the ENOENT error does not persist anymore inside the terminal and the /jsonlogs folder generates as expected

FIX:
Have stumbled a similar problem when I was following a certain course.
If ever your cucumber-json-formatter is moved inside your project, you only need to add "./" in your formatter path

and the ENOENT error will not persist anymore inside the terminal after running $cypress run and will generate the /jsonlogs folder based on your configuration

Hello @badeball,
Firstly, many thanks for your helping library which is very useful.
I have followed exact steps but couldn't generate json file on my mac and also on linux. I have also followed all above suggestions but no luck, please can you help as I'm currently blocked :(? Below are details from my mac and our project is mono repo project.
@adinizs @KShewengger   I have followed your steps too but no luck. Please help if you can.
Package.json

Formatter is present at root folder

PATH Variable

Result from command

Debug log
DevTools listening on ws://<IP_ADDRESS>:52532/devtools/browser/6d6f2fb9-1346-48bb-8097-555a1c01e87f
cypress-cucumber-preprocessor resolved environment overrides {} +0ms
cypress-cucumber-preprocessor resolved explicit user configuration {
cypress-cucumber-preprocessor   json: { enabled: true, output: 'jsonlogs' },
cypress-cucumber-preprocessor   messages: { enabled: true, output: 'messages.ndjson' },
cypress-cucumber-preprocessor   stepDefinitions: [ './apps/host-e2e/src/support/step_definitions/.js' ]
cypress-cucumber-preprocessor } +1ms
cypress-cucumber-preprocessor resolved configuration {
cypress-cucumber-preprocessor   stepDefinitions: [ './apps/host-e2e/src/support/step_definitions/.js' ],
cypress-cucumber-preprocessor   messages: { enabled: true, output: 'messages.ndjson' },
cypress-cucumber-preprocessor   json: { enabled: true, output: 'jsonlogs' },
cypress-cucumber-preprocessor   html: { enabled: false, output: 'cucumber-report.html' },
cypress-cucumber-preprocessor   pretty: { enabled: false },
cypress-cucumber-preprocessor   filterSpecsMixedMode: 'hide',
cypress-cucumber-preprocessor   filterSpecs: false,
cypress-cucumber-preprocessor   omitFiltered: false,
cypress-cucumber-preprocessor   implicitIntegrationFolder: '/',
cypress-cucumber-preprocessor   isTrackingState: true
cypress-cucumber-preprocessor } +1ms
====================================================================================================
(Run Starting)
┌────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Cypress:        13.13.0                                                                        │
│ Browser:        Electron 118 (headless)                                                        │
│ Node Version:   v20.12.2 (/Users/pavgurra/.nvm/versions/node/v20.12.2/bin/node)                │
│ Specs:          1 found (upl-e2e-journeys.feature)                                             │
│ Searched:       apps/host-e2e/src/integration/e2e/upl/upl-e2e-journeys.feature                 │
│ Experiments:    experimentalMemoryManagement=true                                              │
└────────────────────────────────────────────────────────────────────────────────────────────────┘
cypress-cucumber-preprocessor beforeRunHandler() +2s
cypress-cucumber-preprocessor resolved environment overrides {} +2ms
cypress-cucumber-preprocessor resolved explicit user configuration {
cypress-cucumber-preprocessor   json: { enabled: true, output: 'jsonlogs' },
cypress-cucumber-preprocessor   messages: { enabled: true, output: 'messages.ndjson' },
cypress-cucumber-preprocessor   stepDefinitions: [ './apps/host-e2e/src/support/step_definitions/.js' ]
cypress-cucumber-preprocessor } +0ms
cypress-cucumber-preprocessor resolved configuration {
cypress-cucumber-preprocessor   stepDefinitions: [ './apps/host-e2e/src/support/step_definitions/.js' ],
cypress-cucumber-preprocessor   messages: { enabled: true, output: 'messages.ndjson' },
cypress-cucumber-preprocessor   json: { enabled: true, output: 'jsonlogs' },
cypress-cucumber-preprocessor   html: { enabled: false, output: 'cucumber-report.html' },
cypress-cucumber-preprocessor   pretty: { enabled: false },
cypress-cucumber-preprocessor   filterSpecsMixedMode: 'hide',
cypress-cucumber-preprocessor   filterSpecs: false,
cypress-cucumber-preprocessor   omitFiltered: false,
cypress-cucumber-preprocessor   implicitIntegrationFolder: '/',
cypress-cucumber-preprocessor   isTrackingState: true
cypress-cucumber-preprocessor } +0ms
────────────────────────────────────────────────────────────────────────────────────────────────────
Running:  upl-e2e-journeys.feature                                                        (1 of 1)
cypress-cucumber-preprocessor beforeSpecHandler() +2s
cypress-cucumber-preprocessor resolved environment overrides {} +66ms
cypress-cucumber-preprocessor resolved explicit user configuration {
cypress-cucumber-preprocessor   json: { enabled: true, output: 'jsonlogs' },
cypress-cucumber-preprocessor   messages: { enabled: true, output: 'messages.ndjson' },
cypress-cucumber-preprocessor   stepDefinitions: [ './apps/host-e2e/src/support/step_definitions/.js' ]
cypress-cucumber-preprocessor } +0ms
cypress-cucumber-preprocessor resolved configuration {
cypress-cucumber-preprocessor   stepDefinitions: [ './apps/host-e2e/src/support/step_definitions/.js' ],
cypress-cucumber-preprocessor   messages: { enabled: true, output: 'messages.ndjson' },
cypress-cucumber-preprocessor   json: { enabled: true, output: 'jsonlogs' },
cypress-cucumber-preprocessor   html: { enabled: false, output: 'cucumber-report.html' },
cypress-cucumber-preprocessor   pretty: { enabled: false },
cypress-cucumber-preprocessor   filterSpecsMixedMode: 'hide',
cypress-cucumber-preprocessor   filterSpecs: false,
cypress-cucumber-preprocessor   omitFiltered: false,
cypress-cucumber-preprocessor   implicitIntegrationFolder: '/Users/pavgurra/Desktop/Apps/Admiral/repo/ui-admiralmoney-public/apps/host-e2e/src/integration/e2e/upl',
cypress-cucumber-preprocessor   isTrackingState: true
cypress-cucumber-preprocessor } +0ms
cypress-cucumber-preprocessor resolving step definitions using template(s) [ './apps/host-e2e/src/support/step_definitions/.js' ] +0ms
cypress-cucumber-preprocessor replacing [filepath] with 'upl-e2e-journeys' +0ms
cypress-cucumber-preprocessor replacing [filepart] with [ 'upl-e2e-journeys' ] +0ms
cypress-cucumber-preprocessor for 'apps/host-e2e/src/integration/e2e/upl/upl-e2e-journeys.feature' yielded patterns [ 'apps/host-e2e/src/support/step_definitions/.js' ] +1ms
cypress-cucumber-preprocessor found step definitions [
cypress-cucumber-preprocessor   'apps/host-e2e/src/support/step_definitions/steps_partner.js',
cypress-cucumber-preprocessor   'apps/host-e2e/src/support/step_definitions/steps_motor_pos.js',
cypress-cucumber-preprocessor   'apps/host-e2e/src/support/step_definitions/steps_motor.js',
cypress-cucumber-preprocessor   'apps/host-e2e/src/support/step_definitions/steps_mock_quote.js',
cypress-cucumber-preprocessor   'apps/host-e2e/src/support/step_definitions/steps_mock_motor.js',
cypress-cucumber-preprocessor   'apps/host-e2e/src/support/step_definitions/steps_mock_hub.js',
cypress-cucumber-preprocessor   'apps/host-e2e/src/support/step_definitions/steps_mock_help.js',
cypress-cucumber-preprocessor   'apps/host-e2e/src/support/step_definitions/steps_mock_auth.js',
cypress-cucumber-preprocessor   'apps/host-e2e/src/support/step_definitions/steps_mock_app.js',
cypress-cucumber-preprocessor   'apps/host-e2e/src/support/step_definitions/steps_mock.js',
cypress-cucumber-preprocessor   'apps/host-e2e/src/support/step_definitions/steps_manual.js',
cypress-cucumber-preprocessor   'apps/host-e2e/src/support/step_definitions/steps_independent.js',
cypress-cucumber-preprocessor   'apps/host-e2e/src/support/step_definitions/steps_halo.js',
cypress-cucumber-preprocessor   'apps/host-e2e/src/support/step_definitions/steps_common.js',
cypress-cucumber-preprocessor   'apps/host-e2e/src/support/step_definitions/steps_accessibility.js',
cypress-cucumber-preprocessor   'apps/host-e2e/src/support/step_definitions/steps_UPL.js'
cypress-cucumber-preprocessor ] +4ms
End to End Regression Test Scenarios
cypress-cucumber-preprocessor specEnvelopesHandler() +4s
cypress-cucumber-preprocessor testCaseStartedHandler() +9ms
cypress-cucumber-preprocessor testStepStartedHandler() +6ms
cypress-cucumber-preprocessor testStepFinishedHandler() +70ms
cypress-cucumber-preprocessor testCaseFinishedHandler() +6ms
✓ Test - UPL Journey (154ms)
1 passing (215ms)
cypress-cucumber-preprocessor afterSpecHandler() +17ms
(Results)
┌────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Tests:        1                                                                                │
│ Passing:      1                                                                                │
│ Failing:      0                                                                                │
│ Pending:      0                                                                                │
│ Skipped:      0                                                                                │
│ Screenshots:  0                                                                                │
│ Video:        false                                                                            │
│ Duration:     0 seconds                                                                        │
│ Spec Ran:     upl-e2e-journeys.feature                                                         │
└────────────────────────────────────────────────────────────────────────────────────────────────┘
====================================================================================================
(Run Finished)
   Spec                                              Tests  Passing  Failing  Pending  Skipped

┌────────────────────────────────────────────────────────────────────────────────────────────────┐
│ ✔  upl-e2e-journeys.feature                 217ms        1        1        -        -        - │
└────────────────────────────────────────────────────────────────────────────────────────────────┘
✔  All specs passed!                        217ms        1        1        -        -        -

Hi @PavanGurram-DevOps, I recommend that you use the latest version of @badeball/cypress-cucumber-preprocessor, for which the external cucumber-json-formatter is no longer necessary.

Thanks @badeball for the response.
I have resolved it just now. The issue is not with the version, it is with multiple plugins in cypress.config.js file and I ahve seen one more closed ticket which mentions to use cypress-on-fix library.
It would have been easier and time saving if this is mentioned in the documentation itslef so that it would have saved many hours of mine :)
But thats fine, the solution worked which is what needed.
Thanks again for your nice work :)

It would have been easier and time saving if this is mentioned in the documentation itslef so that it would have saved many hours of mine :)

This is mentioned in the FAQ and there's a whole page dedicated to this very problem.

Many thanks @badeball . You are awesome :)


Typo on page

There's a small typo on the 4th line "Prior to generating these reports, you must first connect to Analyticss using the Power BI data connector."

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

ID: c9bc092b-7e31-59c0-148c-6dd2508a9c25
Version Independent ID: db29bd31-fa3f-b959-0ae7-40213bbfeda9
Content: Example reports for Power BI Data Connector - Azure DevOps
Content Source: docs/report/powerbi/data-connector-examples.md
Product: devops
Technology: devops-analytics
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

@toetang - Thank you for the correction. I'll update the article as needed.


[0.5pt] Add header - group task

Create page header according to the wireframe:

@NAVIGATION: LOGO | NAME | TVSERIES | MOVIES


Added a list of paper in the README.md with the non-selectable text.

I had to create another PR because the first one was already merged into the repository.

Thanks Alcemir!


Adding Harvard GSE Scratch Book

What does this PR do?
Adds Harvard's Graduate School of Education Creative Curriculum Guide to Scratch
For resources
Description
Scratch Tutorials PDF
Why is this valuable (or not)
Great Scratch Guide for Students and Teachers
How do we know it's really free?
CC-BY-SA
For book lists, is it a book?
Checklist:

very cool. could be added in several languages - if you don't want to do it I suggest adding an issue.
Welcome to Free-programming-books as one of over a thousand contributors!

Sure, I can add it in the languages listed at the site. It might take me a while, but I'll do it.

great! take your time.


Examples

@tj are you thinking an example for each of the data source types? i.e. Kinesis, S3, SNS, etc?

yep! would

Was thinking about  a Kinesis example. How do you feel about golang function that accepts records from stream and sends the messages to requestb.in so there is an in -> out component to the example.

sounds good to me!

@tj is it possible to set ENV vars through Apex in Lambda? I'd like to be able to initialize some variables in lambda function (independent of the data coming from the stream).
I've seen some examples of using tags (metadata) from the stream itself. Not sure if apex supports pulling that data yet.

yup! either via environment: {} in the project/function json or --set foo=bar with the cli


[.NET] Code Examples - Proposed fix for #2780.

Ref = #2780
This will fix the short-circuit problem for "No Preference" in topping selection.

@CXuesong,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

Thank you for your submission


Lock files should be pipeline ID specific in some way -- this will enable pipelines to flag when old run locks are present.

Tagging @Oufattole as this will help MEDS-Tab be more usable too.

This will be a bit tricky as it depends on hydra nonsense. Basically we need all workers to be able to have the same "pipeline ID" as assigned via the hydra config, meaning when you run a job with multirun, we need a variable to interpolate once before the sweeper goes, then the sweeper to go and not reset that variable. This can be a little finnicky with hydra interpolation rules. But I think some resolvers work like that -- in particular maybe the hydra specific ones do, like now. This would also preclude someone from manually launching multiple workers, which I am fine with, as I can't imagine a situation where that would be better than using hydra launchers.


Disconnect or Close on keepalive fail

I also had to clean up the termination signals and the mechanism when we close frameTransport with onComplete vs. onError.

Looks good, just one case with formatting screwed


Actual worker count is --max-workers+1

Context
In https://github.com/gradle/gradle/commit/2db9e648562e51d5d337a51fd2c9c2d392e17b19 we made some change to allow main thread (i.e. the thread which is waiting for build operation queue's completion) to execute some work. The consequence is, the actual worker number is max-workers number +1. Since we can't set --max-workers=0 via command line, that means the work would always be executed parallelly.
In most cases, this isn't a big problem. However, this does seem misleading (and error-prone! see https://github.com/gradle/gradle-private/issues/977). We have the following possible choices:

Don't allow main thread to run any work.
Keep this behaviour, but clarify it in documentation. In addition, allow --max-workers=0

Personally, I like the former one.

At least for now, we need to keep the main thread executing work.  The issue here is that we have a shared, bounded execution thread pool and worker leases.  What can happen is that multiple threads with obtained worker leases can submit at the same time, but one of them can flood the thread pool with workers that can't acquire a worker lease.  Meanwhile, other workers that can acquire a lease will be stuck trying to get onto the thread pool.  It's not a deadlock situation, but it does decrease performance dramatically.  By allowing the main thread to process work, then we ensure that at least one thread that has already acquired a worker lease is always executing (regardless of the thread pool).
This isn't the only solution to the problem, but its the simplest until we design something better.  For now, we should make the BuildOperationQueue only submit up to max-workers-1 workers to the thread pool - this should fix the issue when max-workers=1.

Yes, that should be the appropriate solution. Thank you very much @ghale !


Investigate & fix datasets not getting translated

Some charts are not using localized datasets (see Operator Dash -> Active Learners)

while other charts are fine.

Investigate why this happens and how to fix it.
Also investigate if metrics created on the chart (not the dataset) are translated.

FYI @Ian2012 if you have any insight into this


Add Path Error

Getting an error that the Add-Path option is deprecated, and that environment variables should be used. I'm new to using GitHub actions so some of the examples I'm looking at are breaking.

Hi @davewolfe-asti this is a dupe of #26 and has been resolved in latest version if you change to that.

Hi @davewolfe-asti this is a dupe of #26 and has been resolved in latest version if you change to that.

Hi @timheuer I'm still getting this error. As you can see I'm using @master
Run microsoft/setup-msbuild@master
  with:
C:\ProgramData\Chocolatey\bin\vswhere.exe -products * -requires Microsoft.Component.MSBuild -property installationPath -latest
C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise
Error: Unable to process command '::add-path::C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin' successfully.
Error: The `add-path` command is disabled. Please upgrade to using Environment Files or opt into unsecure command execution by setting the `ACTIONS_ALLOW_UNSECURE_COMMANDS` environment variable to `true`. For more information see: github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands

The script is https://github.com/imba-tjd/build-miengine/blob/master/.github/workflows/build.yml

@imba-tjd Don't use the '@master' versioning on Actions -- always use a version/hash/tag -- as you note using the appropriate version per the documentation works.


chore: update defaults for timeline_detach_ancestor

by having 100 copy operations in flight twe climb up to 2500 requests per min or 41/s. This is still probably less than is allowed, but fast enough for our purposes.

@problame I still have the TODO about moving this into pageserver configuration. this will however make the next manual operation less easily failed.


per to pear review

Congratulations excellent code.

Hi
Thank you and please feel free to if you have feedback for improvement also it helps me a lot


haskellPackages.graphviz: hardcode references to graphviz tools

This will make everything using graphviz just work without graphviz
having to be able from PATH (in a nix-shell or installed globally).
Did a small sanity check, more testing would be appreciated.

Motivation for this change
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

I just tried running ghc-vis on this branch on its own and it worked just fine, thanks so much!


modify cube in eh-FDTD

This PR modifies input of cube file  in eh-FDTD.
test2.zip
test1.zip

I checked on FX100. For both examples, last 3 lines of obs1_at_point.data were completely same as provided ones. So I merge this PR.

Thank you for checking and merging, @mn2007 san!


Default skip indexing files that can't be accessed (usually due to permissions)

Validations

[X] I believe this is a way to improve. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that requests the same enhancement

Problem
The codebase index feature often doesn't work because of files that are inaccessible for one reason or another.
I'm using continue in VS Code. I often work inside VS Code workspaces. Docker often creates files with root permissions inside directories that I have open (often these go into __pycache__ folders). When these files exist, clicking the button to start indexing (or restart) hangs indefinitely.
When I run sudo git clean -dxf in every directory where I believe this is an issue, continue's codebase index will start working.
Solution
I think it should be possible to check file permissions as part of your indexing process. There also might be other ways to avoid having the indexing process hang when attempting to access inaccessible files.

@ericchansen this is a very good idea for us to check. As a temporary solution, you can use .continueignore


Symlink today's file in rotation handler

It would be very useful to edit/tail today's log file without having to handle the date in the filename. This PR adds a simple symlink to the current log file. Ex:
prod.log -> /var/www/acme/app/logs/prod-2015-07-21.log
prod-2015-07-21.log
prod-2015-07-20.log
prod-2015-07-19.log
...

It's updated on each rotation but it's not created anymore when you don't rotate, that sounds like a mistake, especially since rotation doesn't typically happen unless a script runs through the midnight mark. Otherwise every request just opens the log of the current date and writes into it.
That said I am not sure if this features makes sense at all though, as it means it might cause failures on windows and adds overall complexity for not so much gain.
I really think using logrotate is a better alternative than this handler for any kind of serious environment, so I would rather keep it simple.


DaskDataframe is not able to read remote csv file with content-encoding: gzip

What happened:
We have a remote csv file which is pre-compressed with gzip.
The metadata in s3 is set as
Content-type: text/csv
Content-encoding: gzip

When reading it from DaskDataframe, got the following error, while pandas was able to read the file.
In [5]: df=dd.read_csv(url)
---------------------------------------------------------------------------
ClientPayloadError                        Traceback (most recent call last)
<ipython-input-5-dca40d3a1bb6> in <module>
----> 1 df=dd.read_csv(url)

/usr/local/anaconda3/envs/dask-sql/lib/python3.9/site-packages/dask/dataframe/io/csv.py in read(urlpath, blocksize, lineterminator, compression, sample, enforce, assume_missing, storage_options, include_path_column, **kwargs)
    643         **kwargs,
    644     ):
--> 645         return read_pandas(
    646             reader,
    647             urlpath,

/usr/local/anaconda3/envs/dask-sql/lib/python3.9/site-packages/dask/dataframe/io/csv.py in read_pandas(reader, urlpath, blocksize, lineterminator, compression, sample, enforce, assume_missing, storage_options, include_path_column, **kwargs)
    477         sample = blocksize
    478     b_lineterminator = lineterminator.encode()
--> 479     b_out = read_bytes(
    480         urlpath,
    481         delimiter=b_lineterminator,

/usr/local/anaconda3/envs/dask-sql/lib/python3.9/site-packages/dask/bytes/core.py in read_bytes(urlpath, delimiter, not_zero, blocksize, sample, compression, include_path, **kwargs)
    167                 sample_buff = f.read(sample)
    168                 while True:
--> 169                     new = f.read(sample)
    170                     if not new:
    171                         break

/usr/local/anaconda3/envs/dask-sql/lib/python3.9/site-packages/fsspec/implementations/http.py in read(self, length)
    347         else:
    348             length = min(self.size - self.loc, length)
--> 349         return super().read(length)
    350
    351     async def async_fetch_all(self):

/usr/local/anaconda3/envs/dask-sql/lib/python3.9/site-packages/fsspec/spec.py in read(self, length)
   1397             # don't even bother calling fetch
   1398             return b""
-> 1399         out = self.cache._fetch(self.loc, self.loc + length)
   1400         self.loc += len(out)
   1401         return out

/usr/local/anaconda3/envs/dask-sql/lib/python3.9/site-packages/fsspec/caching.py in _fetch(self, start, end)
    335         elif start < self.start:
    336             if self.end - end > self.blocksize:
--> 337                 self.cache = self.fetcher(start, bend)
    338                 self.start = start
    339             else:

/usr/local/anaconda3/envs/dask-sql/lib/python3.9/site-packages/fsspec/asyn.py in wrapper(*args, **kwargs)
    119     def wrapper(*args, **kwargs):
    120         self = obj or args[0]
--> 121         return maybe_sync(func, self, *args, **kwargs)
    122
    123     return wrapper

/usr/local/anaconda3/envs/dask-sql/lib/python3.9/site-packages/fsspec/asyn.py in maybe_sync(func, self, *args, **kwargs)
     98         if inspect.iscoroutinefunction(func):
     99             # run the awaitable on the loop
--> 100             return sync(loop, func, *args, **kwargs)
    101         else:
    102             # just call the blocking function

/usr/local/anaconda3/envs/dask-sql/lib/python3.9/site-packages/fsspec/asyn.py in sync(loop, func, callback_timeout, *args, **kwargs)
     69     if error[0]:
     70         typ, exc, tb = error[0]
---> 71         raise exc.with_traceback(tb)
     72     else:
     73         return result[0]

/usr/local/anaconda3/envs/dask-sql/lib/python3.9/site-packages/fsspec/asyn.py in f()
     53             if callback_timeout is not None:
     54                 future = asyncio.wait_for(future, callback_timeout)
---> 55             result[0] = await future
     56         except Exception:
     57             error[0] = sys.exc_info()

/usr/local/anaconda3/envs/dask-sql/lib/python3.9/site-packages/fsspec/implementations/http.py in async_fetch_range(self, start, end)
    385             if r.status == 206:
    386                 # partial content, as expected
--> 387                 out = await r.read()
    388             elif "Content-Length" in r.headers:
    389                 cl = int(r.headers["Content-Length"])

/usr/local/anaconda3/envs/dask-sql/lib/python3.9/site-packages/aiohttp/client_reqrep.py in read(self)
   1030         if self._body is None:
   1031             try:
-> 1032                 self._body = await self.content.read()
   1033                 for trace in self._traces:
   1034                     await trace.send_response_chunk_received(

/usr/local/anaconda3/envs/dask-sql/lib/python3.9/site-packages/aiohttp/streams.py in read(self, n)
    368             blocks = []
    369             while True:
--> 370                 block = await self.readany()
    371                 if not block:
    372                     break

/usr/local/anaconda3/envs/dask-sql/lib/python3.9/site-packages/aiohttp/streams.py in readany(self)
    390         # without feeding any data
    391         while not self._buffer and not self._eof:
--> 392             await self._wait("readany")
    393
    394         return self._read_nowait(-1)

/usr/local/anaconda3/envs/dask-sql/lib/python3.9/site-packages/aiohttp/streams.py in _wait(self, func_name)
    304             if self._timer:
    305                 with self._timer:
--> 306                     await waiter
    307             else:
    308                 await waiter

ClientPayloadError: 400, message='Can not decode content-encoding: gzip'

What you expected to happen:
DaskDataframe should be able to read the remote csv file (pre-compressed) as pandas does.
Minimal Complete Verifiable Example:
import pandas as pd
import dask.dataframe as dd
import fsspec as fs

url = "https://convect-test-data.s3.us-west-2.amazonaws.com/tx_3_target_time_series.csv.gz"

df = pd.read_csv(url)  # this is okay
ddf = dd.read_csv(url)  # failed with error

with fs.open(url, "r") as f:
  print(f.readline())  # this is okay

with fs.open(url, "r") as f:
  df = pd.read_csv(f)  # failed with error

Anything else we need to know?:
I think this issue maybe related to fsspec and aiohttp.
Related issue: https://github.com/aio-libs/aiohttp/issues/4462
If I removed the Content-encoding: gzip from the s3 metadata, then the following will work
import pandas as pd
import dask.dataframe as dd
import fsspec as fs

url = "https://convect-test-data.s3.us-west-2.amazonaws.com/tx_3_target_time_series.csv.gz"

df = pd.read_csv(url)  # this is okay
df = pd.read_csv(url, compression="gzip")  # this is okay
ddf = dd.read_csv(url, compression="gzip")  # need to explicitly specify compression='gzip'

It looks like pandas was able to infer the file is compressed with gzip even without setting the compression option in the read_csv.
Environment:

Dask version: 2.30.0
Python version: 3.7
Operating System:  OSX
Install method (conda, pip, source): conda

Yeah I think this is a pure fsspec issue. I am going to close this to keep the discussion in one place (https://github.com/intake/filesystem_spec/issues/720)


Add UI for setting up new rpc conneciton

settings page
add rpc modal

[x] test on firefox

there's some weird font change if you hover over the error label:

Unfortunately, this behavior where the input field's text size changes when hovering over autofill suggestion) is controlled internally by the renderer and currently has no exposed CSS declaration that I can find to override it.