Docker certs not valid with 1.7 upgrade

Getting the following error when trying to connect to the Docker daemon.  Was previously on 1.6.2 and working fine, upgraded to 1.7.0 this afternoon.
An error occurred trying to connect: Get https://<IP_ADDRESS>:2376/v1.19/containers/json: x509: certificate is valid for <IP_ADDRESS>, <IP_ADDRESS>, not <IP_ADDRESS>
The <IP_ADDRESS> IP isn't written to /var/lib/boot2docker/tls/hostnames after rebooting, so it doesn't appear to be picking up the IP during startup.
Running the restart script manually inside the VM does pick up the IP, but all the certs get clobbered and are incorrect after rebooting the whole VM anyways.
Mac OS X 10.10.3, B2D 1.7.0, Docker client 1.7.0, VBox 4.3.20

Deleting the boot2docker image with boot2docker delete and creating a new one with boot2docker init resolved the issue for me.
It doesn't change the fact that the upgrade from 1.6 -> 1.7 is broken, but at least you can get past it.

You will also need to update your environment variable in .bash_profile too, because the DOCKER_HOST  ip/port may have changed.

As mentioned by @rcsa-jr you can disable TLS as a workaround. Set DOCKER_TLS_VERIFY=0 or call each docker command with flag --tlsverify=false

+1 for me. Either an IP change need to be done or the environment need to be reset.

+1 having the same problem

Not sure if this is relevant, but I did do a delete/init, which allowed TLS to function again.
However, afterwards I went through the resizing steps here, which went fine (and I had done that before).  Upon restarting b2d the TLS cert problem came back.
Disabling TLS does work though.

+1
It's seems everyone at my office is suffering from this.

:+1: I got this on restart of the host machine.  Yes, the delete-init fixes it, but I hate having to do that each time I restart my machine.
skye:~ jpirkey$ boot2docker version
Boot2Docker-cli version: v1.6.2
Git commit: cb2c3bc

Does using "boot2docker shellinit" again fix it? (which re-copies the certs
from the VM)

boot2docker shellinit didn't fix it for me, but boot2docker delete and boot2docker init did work as others have mentioned.

Didn't fix it for me either ... i run shellinit in my .bash_profile

Same here :/ Issue comes back at each reboot. Are upgrade tests being run before each release?

The only proper fix I've found for now is to completely disable TLS this way: https://coderwall.com/p/siqnjg/disable-tls-on-boot2docker

1
I have same problem

➜  ~  boot2docker version
Boot2Docker-cli version: v1.7.0
Git commit: 7d89508
➜  ~  docker  version
Client version: 1.7.0
Client API version: 1.19
Go version (client): go1.4.2
Git commit (client): 0baf609
OS/Arch (client): darwin/amd64
An error occurred trying to connect: Get https://<IP_ADDRESS>:2376/v1.19/version: x509: certificate is valid for <IP_ADDRESS>, <IP_ADDRESS>, not <IP_ADDRESS>

See #824, possible duplicate

On my machine eth1 isn't UP during certs creation, so it doesn't have an ip. See https://github.com/boot2docker/boot2docker/issues/824#issuecomment-113898405

I'm seeing this as well but it's on a from-scratch install of the latest version, not an upgrade.

Thanks @sylvinus your post work for me!

I made the docker init script wait for eth1 to come UP by using this code: https://github.com/boot2docker/boot2docker/issues/824#issuecomment-113904164

the fix in #824 works for both boot2docker-OSX and boot2docker-Windows.

Thanks gesellix - your fix works for me too. I have linked it in some other places I found this being asked about to help others.

Same problem. Fix only by @gesellix workaround.

after setting env properly, try this.
boot2docker ssh 'sudo /etc/init.d/docker restart'

Same problem here, @zh-lab's fix works for me :+1:

Snap @zh-lab did it for me, after upgrading:
$ $(boot2docker shellinit)
Writing /Users/buckett/.boot2docker/certs/boot2docker-vm/ca.pem
Writing /Users/buckett/.boot2docker/certs/boot2docker-vm/cert.pem
Writing /Users/buckett/.boot2docker/certs/boot2docker-vm/key.pem
$ boot2docker ssh 'sudo /etc/init.d/docker restart'
Need TLS certs for boot2docker,<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>
-------------------
Generate server cert
/usr/local/bin/generate_cert --host=boot2docker,<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS> --ca=/var/lib/boot2docker/tls/ca.pem --ca-key=/var/lib/boot2docker/tls/cakey.pem --cert=/var/lib/boot2docker/tls/server.pem --key=/var/lib/boot2docker/tls/serverkey.pem
2015/06/24 11:12:53 Generating a server cert

The fix in #824 seems to be a partial fix since it hangs the VMbox and only works one time. In my case I'm using Google Cloud CLI gcloud commands to manage their hosted VMs and it ceases to function since it can't establish a connection to docker.
ERROR: Failed to connect to Docker Daemon due to: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)
ERROR: (gcloud.preview.app.deploy) Couldn't connect to the docker daemon.
Please check if the environment variables DOCKER_HOST, DOCKER_CERT_PATH and DOCKER_TLS_VERIFY are set correctly. If you are using boot2docker, you can set them up by executing the commands that are shown by:
boot2docker shellinit

@samkelleher the fix in #824 only works around a network interface issue inside a boot2docker vm and applies for the initial start of the docker daemon.
Your problem sounds like you used some boot2docker specific env variables (DOCKER_HOST, ...), but you might need to reconfigure them when using the Google Cloud CLI.

@buckett did you add the delay script mentioned in https://github.com/boot2docker/boot2docker/issues/824#issuecomment-113904164 ?

On 24 June 2015 at 15:25, Tobias Gesellchen<EMAIL_ADDRESS>wrote:

@buckett https://github.com/buckett did you add the delay script
mentioned in #824 (comment)
https://github.com/boot2docker/boot2docker/issues/824#issuecomment-113904164
?

No and now I've just deleted and re-created.
--
Matthew Buckett

@gesellix After many boot2docker delete && boot2docker init && boot2docker start, then ssh'ing the patch, then running eval "$(boot2docker shellinit)" to set the env variables, gcloud still won't connect (although the VM seems accessible to boot2docker commands). The variables (like DOCKER_HOST) are the same ones that init outputs. Indeed, shellinit shows the message that the vars are already set.

@samkelleher I'm not sure whether the boot2docker settings/configuration also apply to gcloud. I guess gcloud isn't aware of boot2docker. If so, I would suggest to focus on gcloud configuration and remove any boot2docker specific environment settings.

On installing 1.7.0 I had the this issue on Yosemite. I've just downgraded to 1.6.2 and had exactly the same problem after a boot2docker stop and start.

I'm seeing this issue as well. I also see patches suggested above, but that isn't a real solution it requires several manual steps to modify the boot2docker vm. This shouldn't be happening on a vanilla install of boot2docker. Is there an ETA of when this will be fixed? This is the type of bug I expect to see in the new 'experimental' docker releases, not stable.

Thank you @zh-lab!

I'm wondering if boot2docker 1.7.0 on OS X is working out of the box for
someone !
In addition to a fix, we need this use case to be tested.
On Thu, Jun 25, 2015, 10:37 AM Reiner Bruns<EMAIL_ADDRESS>wrote:

Thank you @zh-lab https://github.com/zh-lab!
—
Reply to this email directly or view it on GitHub
https://github.com/boot2docker/boot2docker/issues/938#issuecomment-115162836
.

--
Joseph Page  -  meem.io

I too have run into this issue.  @buckett solution worked for me, but I also have the follow up problem of it breaking on a restart.

@brianbianco and I were able to work around this, as he said above. But the restart problem will be fairly oppressive going forward.

+1 for a fix to this. I haven't found a workaround that persists after boot2docker restart.

:+1: same here!!
please help.

@mboersma adding the delay code from https://github.com/boot2docker/boot2docker/issues/824#issuecomment-113904164 didn't work for you after restarts? What does boot2docker ssh cat /va/log/boot2docker.log show?

what continues to work for me is docker-machine. just download it and docker-machine create --driver virtualbox dev and eval $(docker-machine env dev) and don't directly interact with boot2docker cli anymore at all. no problems with starting and stopping the vm or anything.
ps: if you have local images you want to keep, you might want to docker save -o images.tar $(docker images -q) from your boot2docker host (also docker images > imagelist.txt) and docker load -i images.tar. as this will not restore image names but only image ids, you can then docker pull the images from your imagelist.txt and the tags will be added. probably this can be done better. but i only had to do it once so .. afterwards you might want to remove your prior boot2docker vm to save some disk-space.

Docker noob and hit this on OS X 10.9.5 with a new install of b2d from the Docker "Get Started" page (ouch), which uses a pre-existing install of VirtualBox.  After switching from WiFi+VPN to directly cabled to a switch in the office, started seeing the x509 cert errors.

For the record, @aidanlister's solution worked for me. Using v1.7 on osx Yosemite.

@aidanlister @leftdevel did you try https://github.com/boot2docker/boot2docker/issues/824#issuecomment-113904164 ?

:+1: for integral fix. 1.7.0 is completely broken on OS X.

Just echoing others experience with this and the problems previously reported. I'll second the request for a better test setup for OS X so that broken releases don't make it through QA without problems like this being noted. (On the other hand it's a .0 release so i should expect something to go wrong?)

:heavy_plus_sign: :one:
While $ boot2docker delete && boot2docker init && boot2docker up && $(boot2docker shellinit) solves the issue, all of the images and data I previously had is now gone.
Using --tlsverify=false works but is not a long term solution and does not lend itself well to any higher level bash scripts I may be using to orchestrate some docker stuff.
boot2docker ssh 'sudo /etc/init.d/docker restart' works as well when I am seeing the x509 certificate issue but this will happen any time I change IPs T_T

Modifying one file seems like a minor inconvenience. You don't have to recreate the entire VM.  @isuftin did you try that fix?  It worked for me and seems to have a number of other people.

@jpirkey Nope, didn't try that. I will do so the next time I run into this issue. I assume this is probably something we want to add to /var/lib/boot2docker/profile immediately after boot2docker init.

@isuftin You can do it anytime.  You'll just need to reboot the vm after you do.  I waited until it happened again (after host machine reboot), then did applied the fix (mostly because I wanted to see if it was reproducible).

@jpirkey Sounds good. Following @ https://github.com/boot2docker/boot2docker/pull/411 and hoping it makes it into the next rls

yup, confirmed:
-------------------
Fri Jun 26 17:43:24 UTC 2015
Fri Jun 26 17:43:29 UTC 2015
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default
    link/ether 9e:86:5e:cf:b5:69 brd ff:ff:ff:ff:ff:ff
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 08:00:27:29:6c:8e brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::a00:27ff:fe29:6c8e/64 scope link tentative
       valid_lft forever preferred_lft forever
4: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 08:00:27:6a:0d:e6 brd ff:ff:ff:ff:ff:ff
-------------------
Need TLS certs for boot2docker,<IP_ADDRESS>,<IP_ADDRESS>
-------------------

when we start the Docker daemon, the eth1 is not up for some racing issue :(.

note that restarting the docker daemon manually solves it, as that triggers a cert re-generation
boot2docker ssh sudo /etc/init.d/docker restart

Perhaps the upgrade process of boot2docker should do that automatically once it's done? :)

+1
boot2docker ssh 'sudo /etc/init.d/docker restart' works but it sounds to me like a very temporary solution...

boot2docker ssh 'sudo /etc/init.d/docker restart' may be working for some people but it certainly did not work for me. This was following 1.6.1(?) -> 1.7.0 upgrade. I am using the previously mentioned patchy-hack from the issue #824 comment.

+1 delete and init helps, but you have to repeat it.

+1
becoming super annoying

+1 I've had to delete and init four times in the past 24 hours and re-downloading the cache is murdering me

@jdemaris Have you tried
boot2docker ssh sudo /etc/init.d/docker restart

rather than delete and init? It's a lot faster. (Still a hack but at least an easier to manage hack)

Thanks @vielmetti. Just saw that on @SvenDowideit's comment and it does indeed make this a bit faster to recover

Thanks @vielmetti. Just saw that on @SvenDowideit's comment and it does indeed make this a bit faster to recover

Thanks @zh-lab for this.
boot2docker ssh 'sudo /etc/init.d/docker restart'

Is there any eta on a fix for this? Currently every time I connect/disconnect from work VPN I must repeat the whole delete, init, up process, and I lose all my local images.

This issue was fixed in https://github.com/boot2docker/boot2docker/pull/960

Well, @charford - #960 should help this out, but there is a race condition between eth1 coming up and the cert being generated. If your DHCP server is unnaturally slow the race condition will probably still be triggered.

@vielmetti Have you tried the fix in #960? I was having these exact issues, and haven't seen them since using the fix in #960. It will be out in the 1.7.1 boot2docker release, so if you are not comfortable building the iso from src, it'll be available in a few days.

Thanks @charford I plan to try the fix when it comes out in the 1.7.1 & will report back then!

Thanks for fixing this in the upcoming 1.7.1!

:+1:
waiting for 1.7.1

As a workaround, you can add a line "<IP_ADDRESS> boot2docker" to /etc/hosts on your host machine.

@zh-lab's fix works for me

I experienced the same problem, until i added the file
cat ~/.dockercfg
{
"https://index.docker.io/v1/": {
"auth": "somestring",
"email": "my@email"
}
}
because before config was placed at ~/.docker/config.json insead. may be this could help for someone else

Running boot2docker upgrade - fixed this for me.

Fixed with @zh-lab command : boot2docker ssh 'sudo /etc/init.d/docker restart'

On Windows,

fresh install of boot2docker
run boot2docker upgrade (says up to date, but downloads the ISO again anyway?)

$ docker run hello-world
An error occurred trying to connect: Post https://<IP_ADDRESS>:2376/v1.19/cont
ainers/create: x509: certificate is valid for <IP_ADDRESS>, <IP_ADDRESS>, not 192.168.
59.103

boot2docker delete then init

$ docker run hello-world
An error occurred trying to connect: Post https://<IP_ADDRESS>:2376/v1.19/cont
ainers/create: dial tcp <IP_ADDRESS>:2376: ConnectEx tcp: A connection attempt
 failed because the connected party did not properly respond after a period of t
ime, or established connection failed because connected host has failed to respo
nd.

exiting minigw and re-opening boot2docker works

I have this error after boot2docker restart
I'm using
$: boot2docker version
Boot2Docker-cli version: v1.7.0
Git commit: 7d89508

I initialized my boot2docker image
$: boot2docker init
Latest release for github.com/boot2docker/boot2docker is v1.7.0

I clean my current environment variable
$: unset DOCKER_HOST; unset DOCKER_CERT_PATH; unset DOCKER_TLS_VERIFY;

I start my boot2docker
$: boot2docker start
Waiting for VM and Docker daemon to start.............................ooooooooooooooo
Started.
Writing /Users/moylop260/.boot2docker/certs/boot2docker-vm/ca.pem
Writing /Users/moylop260/.boot2docker/certs/boot2docker-vm/cert.pem
Writing /Users/moylop260/.boot2docker/certs/boot2docker-vm/key.pem

To connect the Docker client to the Docker daemon, please set:
    export DOCKER_HOST=tcp://<IP_ADDRESS>:2376
    export DOCKER_CERT_PATH=/Users/moylop260/.boot2docker/certs/boot2docker-vm
    export DOCKER_TLS_VERIFY=1

I add to my bash profile this environment variables:
export DOCKER_HOST=tcp://<IP_ADDRESS>:2376
export DOCKER_CERT_PATH=/Users/moylop260/.boot2docker/certs/boot2docker-vm
export DOCKER_TLS_VERIFY=1

And execute source command.
I read my environment variables:
$: echo ${DOCKER_HOST}--${DOCKER_CERT_PATH}--${DOCKER_TLS_VERIFY}
tcp://<IP_ADDRESS>:2376--/Users/moylop260/.boot2docker/certs/boot2docker-vm--1

I test it
$: docker pull hello-world
$: docker run hello-world
Hello from Docker.
This message shows that your installation appears to be working correctly.
...

Cool!
Now, I restart my boot2docker
$: boot2docker stop
$: boot2docker start

Now, I re-tested it
$: docker run hello-world
An error occurred trying to connect: Post https://<IP_ADDRESS>:2376/v1.19/containers/create: x509: certificate is valid for <IP_ADDRESS>, <IP_ADDRESS>, not <IP_ADDRESS>

+1 on what moylop260 mentioned above.

With respect to my last comment
https://github.com/boot2docker/boot2docker/issues/938#issuecomment-118123208
If I restart the docker from ssh now work fine.
$: boot2docker ssh 'sudo /etc/init.d/docker restart'
$: docker run hello-world
Hello from Docker.

But in each boot2docker restart I will need execute docker restart from ssh.

This set me back hours this morning.  I hope future releases are tested a little better because this seems like it should have been caught before release since it causes problems immediately after upgrading.  Until this is fixed though, running alias docker="docker --tlsverify=false" seems to have helped.  Although, I'm wondering if TLS is even necessary for boot2docker at all.  If it's only running on my local machine, why introduce unneeded complexity?

Although, I'm wondering if TLS is even necessary for boot2docker at all. If it's only running on my local machine, why introduce unneeded complexity?

RCE due to the IP address provided by the host-only adapter.  A web page can make an HTTP request to, say, <IP_ADDRESS>:2375 using JavaScript, i.e. a web page can run containers in your VM if it's not protected by TLS.
See here: https://groups.google.com/forum/#!topic/docker-announce/aQoVmQlcE0A

+1 ... above noted that release to fix 0.7.1 is waiting for docker 0.7.1 -- but we've had docker 0.7.1rc1 for almost a week now. Why not boot2docker 0.7.1rc1? (or just 0.7.1?)

+1 this is driving me nuts

I think it would be best not to have to depend on docker making an update for boot2docker to be able to make an update. I would encourage you to add a field to the versioning just for boot2docker to use the way debian packages have version numbers added by the package maintainers. This would allow for an easier mid-cycle release for bug fixes or even to address security vulnerabilities.

@devries :+1: absolutely, this bug is very, very annoying.

+1 oh please fix this soon. cant push to gcloud docker

+1 on pushing fix separately

+1 I have the same problem!

+1 please, please slow down development and increase testing - I'm very grateful for all your hardwork it just get's spoilt by this: https://www.dropbox.com/s/1zsqfgm91puk58h/Screenshot 2015-07-10 14.09.52.png?dl=0

This "bug" is 22 days old.  It would seem that they would have fixed it by now.  This is a MAJOR annoyance.  Each time I reboot my work laptop, I have to docker delete and init and lose all the base images I have downloaded.  Very aggravating.

@neilellis and @scawa1952 - if you follow the path of restarting docker inside the VM instead of delete and init, you can save a lot of time. https://github.com/boot2docker/boot2docker/issues/938#issuecomment-118123208 is the relevant comment.

@vielmetti  Thanks.....

@vielmetti thanks, I did that first time round :)

@jpirkey's solution worked for me. Thank you!

I got the same issue upgrading from an ancient version.
I deleted the VM and things worked again. However, today the issue occurs again!
The solution of doing a boot2docker stop && boot2docker delete && boot2docker init fixed the issue.

@vielmetti restarting the docker daemon does not fix the issue for me.

This fix needs to go out ASAP, it's crushing my development cycles.

Same experience here on 1.7 (I did not upgrade, fresh install) on Windows.

+1 For Fix
My current workaround is: boot2docker poweroff && boot2docker destroy && boot2docker init && boot2docker start
But that destroys all images. It's the only solution that works for me as of now.

This is the bash alias I have been using:
alias b2dinit="boot2docker up \
     && \$(boot2docker shellinit) \
     && boot2docker ssh 'sudo /etc/init.d/docker restart'"

boot2docker ssh sudo /etc/init.d/docker restart fixed it for me.

+1 fixed it for me too

+1 fixed for me as well

+1

I prefer the option from @timlesallen to the others as the others wipe out whatever images/containers you had.

Can anyone who's able to reproduce this test with v1.7.1-rc3 (https://github.com/tianon/boot2docker/releases/tag/v1.7.1-rc3) and verify that #960 fixed it?

Thanks to @nathanleclaire, we've verified that #960 is the fix.  Let's build us an official 1.7.1 release and finally put this to bed! :+1:

Thanks @tianon.  Sorry all for any inconvenience encountered in the meantime.  In our excitement to migrate to Docker Machine this one slipped through the cracks.

Thanks b2d team for finally fixing this - just installed 1.7.1 and :beers: !

I had the same issue, installed 1.7.1 and the problem is now gone. Thanks b2d team!

@MiguelPeralvo: I agree, 1.7.1 rocks.
Thanks guys, the problem is gone!

:heart: :heart: :heart: :heart: Appreciate hearing that it is working for you.

Hit this problem too, happy to see there is a fix. It installed, but failed the same way as above. The reported client version was 1.7.1. I banged around for 20 minutes to fully un-install boot2docker and verify that VBOX was up to date. After a full un-install and install of boot2docker, it worked!
Please note, the https://docs.docker.com/mac/step_one/ page should be updated to point to the 1.7.1 release download: https://github.com/boot2docker/osx-installer/releases/download/v1.7.1/Boot2Docker-1.7.1.pkg

boot2docker ssh 'sudo /etc/init.d/docker restart'

thanks @zh-lab

Great... it worked! :+1: (I did a full clean as @dmoore247 suggested)

Hmmm... maybe I'm wrong but I think I hit this problem again...
I cleaned up and reinstalled b2d from scratch, but after restarting I encountered the problem again:
Carlos-MacBook-Pro:bin lordkada$ boot2docker init
Initialization of virtual machine "boot2docker-vm" complete.
Use `boot2docker up` to start it.
Carlos-MacBook-Pro:bin lordkada$ boot2docker up
Waiting for VM and Docker daemon to start...
.........................ooooooooooooooooooooo
Started.
Writing /Users/lordkada/.boot2docker/certs/boot2docker-vm/ca.pem
Writing /Users/lordkada/.boot2docker/certs/boot2docker-vm/cert.pem
Writing /Users/lordkada/.boot2docker/certs/boot2docker-vm/key.pem
Your environment variables are already set correctly.

Carlos-MacBook-Pro:bin lordkada$ docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
Carlos-MacBook-Pro:bin lordkada$ boot2docker stop
Carlos-MacBook-Pro:bin lordkada$ boot2docker up
Waiting for VM and Docker daemon to start...
..............oooo
Started.
Writing /Users/lordkada/.boot2docker/certs/boot2docker-vm/ca.pem
Writing /Users/lordkada/.boot2docker/certs/boot2docker-vm/cert.pem
Writing /Users/lordkada/.boot2docker/certs/boot2docker-vm/key.pem
Your environment variables are already set correctly.

Carlos-MacBook-Pro:bin lordkada$ docker ps
An error occurred trying to connect: Get https://<IP_ADDRESS>:2376/v1.19/containers/json: x509: certificate is valid for <IP_ADDRESS>, <IP_ADDRESS>, not <IP_ADDRESS>

I'm running boot2docker v1.7.1:
Carlos-MacBook-Pro:bin lordkada$ boot2docker version
Boot2Docker-cli version: v1.7.1
Git commit: 8fdc6f5

What I'm missing?

@lordkada Is the boot2docker.iso file itself on 1.7.1 (you should be able to see this if you boot2docker ssh)?  boot2docker upgrade will give you the latest of everything.

@lordkada try this:
$ docker --version && b2d ssh docker --version

You should get the same info twice:
Docker version 1.7.1, build 786b29d
Docker version 1.7.1, build 786b29d

If not, then yeah: you may be having issues. Try boot2docker delete && boot2docker up but it says you re-installed? That's odd.

@nathanleclaire & @chiefy - thanks for your support. Yes, the .iso was still old and I forced an upgrade with boot2docker upgrade. Now it works!
I'm not 100% sure, but when I uninstalled boot2docker (I use brew cask) I forgot to wipe the .bootdocker folder (or at least the .iso)... now I presume that, for safety, the .iso is not overwritten by a fresh installation...
Thanks again!

@efosao
boot2docker delete
boot2docker init
Then it will response with "Initialization of virtual machine "boot2docker-vm" complete.
Use boot2docker up to start it"
boot2docker up did the magic for me.
Docker version 1.7.1, build 786b29d
OSX 10.10.3 Yosemite

boot2docker upgrade did it for me:
~ boot2docker upgrade
docker is up to date (1.7.1), skipping upgrade...
boot2docker is up to date (v1.7.1), skipping upgrade...
Latest release for github.com/boot2docker/boot2docker is v1.7.1
Downloading boot2docker ISO image...

Success: downloaded https://github.com/boot2docker/boot2docker/releases/download/v1.7.1/boot2docker.iso
	to /Users/eddy/.boot2docker/boot2docker.iso
Waiting for VM and Docker daemon to start...
...............oooooooooo
Started.
Writing /Users/eddy/.boot2docker/certs/boot2docker-vm/ca.pem
Writing /Users/eddy/.boot2docker/certs/boot2docker-vm/cert.pem
Writing /Users/eddy/.boot2docker/certs/boot2docker-vm/key.pem
Your environment variables are already set correctly.

Also seems fixed for me after boot2docker upgrade.

boot2docker delete && boot2docker init && boot2docker start
fixed the problem for me.

docker 安装准备
env: win10 64bit
dependencies:
	docker: 1.8.0
	boot2docker.iso: 1.8.0
	boot2docker-cli: 1.7.1
	virtuaBox: 5.0.1(测试版)
	git: 1.9.5.msysgit.1

docker 启动
命令行下：
//初始化
boot2docker init
//启动
boot2docker up(报错, ssh认证无效)
//补上, 成功
boot2docker ssh

因为：
ssh<EMAIL_ADDRESS>运行参数为
2015/08/13 11:47:27 executing: E:\Program Files\Git\bin\ssh.exe ssh -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -p 2022 -i C:\Users\sysam\.ssh\id_boot2docker docker@localhost tar c /home/docker/.docker/*.pem

boot2docker ssh 运行参数为
2015/08/13 11:47:33 executing: E:\Program Files\Git\bin\ssh.exe ssh -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -p 2022 -i C:\Users\sysam\.ssh\id_boot2docker docker@localhost

多了 tar c /home/docker/.docker/*.pem

hmm i did boot2docker upgrade and i didnt see that work.

+1.  I'm experiencing this issue on Mavricks and the latest version of boot2docker.

I have handled this problem just via regenerating a new TLS certification stand in for disabling TLS roughly:
docker-machine regenerate-certs ConfusedMachine

I think it's not relevent to Docker itself at all, but the source of secure binding in the TLS certification with IP address.


query/focusable should be able to provide only-tabbable elements as well

The following methods ignore elements that are keyboard-focusable but not script-focusable. While this is the expected use case, considering these methods are for scripting, there is currently no way to identify all tabbable elements, e.g. to visually mark them as such.
To allow both uses a new option includeOnlyTabbable: true should be added to the following modules:

query/first-tabbable
query/focusable
query/tabbable
query/tabsequence

The effect of this option should be to disengage the isOnlyTabbable() constraint in is/focusable. As all elements passing is/only-tabbable must already pass is/focus-relevant, no further change should be necessary.
In #80 the cores of is/focus-relevant and is/tabbable were refactored to allow specifying options, while maintaining the function signatures - the same should be done to is/focusable.

The initial assumption regarding anything that is considered is/only-focusable is also considered is/focus-relevant is invalid as query/focusable.all considers both.
Missing from is/focus-relevant in Firefox:
[
  "label[tabindex=0]",
  "svg a[xlink|href]",
  "svg[tabindex=-1] a[xlink|href]",
  "svg[focusable=false] a[xlink|href]",
  "svg a[xlink|href][tabindex=0]",
  "svg a[xlink|href][tabindex=1]",
  "svg a[focusable=false]",
  "svg a[xlink|href][tabindex=-1]",
  "svg{tiny} a[focusable=false]",
  "svg{tiny} a[tabindex=-1]",
  "svg{tiny}[focusable=false] a"
]

Missing from is/focus-relevant in Internet Explorer:
[
  "svg",
  "svg a[xlink|href]",
  "svg rect[focusable=true]",
  "svg[tabindex=-1]",
  "svg[tabindex=-1] a[xlink|href]",
  "svg[focusable=false] a[xlink|href]",
  "svg:has(a[tabindex=0])",
  "svg a[xlink|href][tabindex=0]",
  "svg a[xlink|href][tabindex=1]",
  "svg{viewbox}",
  "svg rect[focusable=true]{viewbox}",
  "svg:has(a[tabindex=-1])",
  "svg a[xlink|href][tabindex=-1]",
  "svg{tiny}",
  "svg{tiny} rect[focusable=true]",
  "svg{tiny} a[tabindex=-1]",
  "svg{tiny} rect[focusable=true][tabindex=-1]",
  "svg{tiny}[focusable=false] a"
]

Chrome does not suffer from the is/only-tabbable workaround


Picture Gallery/Revamp Media-Tab

Is your feature request related to a problem? Please describe.
It is no secret that Twitter and now BlueSky are being used as an art-platform. I frequently watch art and pictures on the platform. But the main issue I'm having is that for each picture there is a username, post-text and likes/comments/repost: They take up a lot of space. Pictures are also not getting displayed horizontally. While that helps pictures to be displayed bigger, it's not idea for browsing them.
Describe the solution you'd like
I would be interested in having a grid- or a flow grid-layout to display media more efficiently. It would also help users to find image-posts more easily. I imagine it as a similar concept to Instagram.
For posts that have multiple pictures an artist could select the preview picture, or have them grouped into one of the squares. Another way would be to not make a grid, but rather a post-flow, where pictures take up as much space as they need.
Another cool feature for the artists, would be to hide certain pictures from the gallery to only display art and clean it up from scraps or memes. On the user side, it would still be amazing to have a way to switch them on, if someone wants them displayed.
Describe alternatives you've considered
Because Twitter was never really approachable with changes like this, I considered using the API to make my own Website that allows users to view the content as described above and link back to the original post. But… well that is no longer a viable option to me for multiple reasons. Because BlueSky is Open Source and more approachable through GitHub, I thought I could give this a shot, before I try a 2nd time to make my solution happen.
Additional context
I'm totally aware that this is most likely not in favor of BlueSky, as the idea is to use it as a short-news platform or for microblogging. But because of Twitter having a lot of artists on their platform, it kinda carries over to BlueSky as they jump ship from Twitter.
This would be a great addition to manage their content better and for consumers to have a better overview of their work.
Even tho I am certain the Media tab is not going to be sacrificed, I would still love to see some switch to turn this feature or dedicate an entire tab to it. (tho I think that would be too much)

For what it's worth, the 3rd-party client Tokimeki (https://tokimeki.blue) displays User Profiles' Media tabs in grid-view by default.

In addition, when using Tokimeki's "Decks" mode, you can choose to display feeds/timelines in both "normal" and "media" views.

Yes! That's amazing! Exactly what I was looking for. But I think it would be better to keep this open for a possible change in the official app. ^^
Tho I will probably use this modified client for now.

Twitter is now using a gallery format for the Media tab of a user. I hope that Bluesky changes it to be the same way soon.

Closing as a duplicate of https://github.com/bluesky-social/social-app/issues/2163, we're +1 to this

@pfrazee Isn't it better practice merging newer issues into the old one?

Closing duplicates is pretty common practice too, it doesn't really matter which one came first tbh. FWIW, mentioning the related issue by #number ensures that this issue will appear in the related issue's notifications, so any relevant info shared here will still be easy to find later.

Closing duplicates is pretty common practice too, it doesn't really matter which one came first tbh. FWIW, mentioning the related issue by #number ensures that this issue will appear in the related issue's notifications, so any relevant info shared here will still be easy to find later.
Please read my message again. Issue merging is a very common practice and necessary to keep the conversation of the same issue in one place. But usually you merge into the oldest issue and not to the newest to get the full history and not nest issues into issues. It creates clutter and a false representation of the full timeline. In rare cases it is fine to merge into another issue, if that one has more engagement.
To be fair I was on a short fuse and mad, when I replied to this yesterday as it took me some time and research to put the issue together. Otherwise, I would have let it slide.


How can I run the scripts under another user?

Hi guys,
I have to run some scripts with a different users. For example the Exchange Command:
Add-MailboxPermissions doesn't take a -Credential Parameter.
But I have to provide it because the normal domain User has no rights for that command. If there is no way to run a script as could you give me a tip to solve this in another way? If I would start my IDE (Visual Studio Code) as another User and then run the app, the scripts should get run from that user, am I right?

It sounds like you are doing this in Windows.  For Windows, you can do it the easy cheezy way and, like you said, run VS Code as another user to get their terminal or you can open the node command prompt as another user.  You can even run powershell as another user and have access to node.
To do it the hard way (again, for Windows) you want to look at this guide to Splatting and this guide has a section on putting it into practice.


Seen notification

I was thinking it would be part of "event" type but doesn't seem to be the case?

Sorry, I don't really understand what you're asking for here.
Are you seeing an undocumented type of event?
Or is this a feature request?

It could be termed a feature request if we don't have this type of event already.
I want to notify user, when a sent message has been marked as read on other side.
It is basically markAsRead in reverse direction..
Please let me know if it's still not clear.

@nripendra tell me if this works for you.

Assuming this works, it needs to be documented.

I'll check and comment when I get time. Thanks!


conditions to see datasets in selection GUI

The datasets you see in this list meet at least one of the following conditions:
The articles says this:
"The dataset is in one of the new workspace experience workspaces, and you're a member of that workspace. See Considerations and limitations.
You have Build permission for the dataset, which is in a new workspace experience workspace.
The dataset is in your My Workspace."
But in Power BI Desktop I see all datasets I have build permission on, regardless of if its a new or classic workspace. I think those conditions are true if you're using the service, but not Power BI Desktop.

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

ID: d0097b22-50b6-445a-10e9-a8e2a26dabbe
Version Independent ID: daf670da-4171-29b2-7171-4e46637c099d
Content: Create reports based on datasets from different workspaces (Preview) - Power BI - Power BI
Content Source: powerbi-docs/service-datasets-discover-across-workspaces.md
Service: powerbi
Sub-service: powerbi-service
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

Thanks for your comment, @klinejordan. This issue has been assigned to the doc author for review.

@klinejordan - Thank you for submitting feedback on our documentation. This article has been updated. If your feedback isn’t addressed, please feel free to submit additional feedback for the page


Live share is not working

Hi,
I'm trying to work with my friends but I cannot join live share on VSCode. I clicked a link they shared,  it does not load any files to vs code.  Other friends can join the link but my screen says Loading file tree...
Also, I tried to join manually through Live Share extension tap, Share and Join buttons do not work for me.

Closing and marking as a duplicate of #4204, please join the conversation there!


Settings defined in shopify.ui.extension.toml file not working

Please list the package(s) involved in the issue, and include the version you are using
Using "@shopify/checkout-ui-extensions-react": "^0.18.1"
Shopify cli ^3

Describe the bug
Settings defined in the config file are not available in the checkout editor. Example from our config file, copied from the sample documentation:
[settings]
  [[settings.fields]]
  key = "title"
  type = "single_line_text_field"
  name = "Banner title"
  description = "Enter a title for the banner."

Steps to reproduce the behavior:

Go to checkout editor
Add extension
Look for settings on right side

Expected behavior

Expected to see settings
Screenshots

Additional context
Link to checkout extension:
https://partners.shopify.com/941756/apps/7334592513/extensions/checkout_ui_extension/14895120385

@kumar303

👋 Hi there - I'm taking a look at this and it seems like you've uninstalled the app the ticket refers to - are you still experiencing the same problem with the new app?


WIP:Added Order Tests

I added ordering test. If you got time, please review the changes and feel free to request changes.
I added chai because I think the syntax is very intuitive. But please let me know if you dont think so.

adding tests for sorting by specific elements is a great idea. the tests you wrote seem good imho, but at this point in time i cant do a full review, due to another project im involved in right now.
including chai is very good. we were thinking about that already. so thank you for that!
right now im unsure why the tests seems to fail.
Travis says "chromiumdrivers failed to load in time". i asume you are working on that already, so plz feel free to contact me when you found a solution. i will try to make room for that as soon as it seem stable!

@N3ol4N can you check if the tests run on your mac? On windows they are running fine O.o

just checked your branch locally. same issue as with travis:

Application launch
"before each" hook for "shows an initial window":
Error: ChromeDriver did not start within 5000ms

but i tried the tests of the current master as well. same problem now.
i'm not quite sure, but i think the master passed its tests on the last merge. it seems odd that it's crashing now. maybe something outside of our codespace changed? versioning or something of chromium that's used?

That's really weird. I will create a virtual machine and try to find the misconfiguration

Good news :tada: the tests are running again! Still failing because my tests are wrong buuuuut they get executed

These are very good news :-D
Thank you very much for your help! Could you share some of your insight about that problem? Did you find the reason for the changed behaviour?

The issue seem to be the very old versions of electron and related dependencies (see commit: e0a5f9f updating dependencies helped in circleci). Electron for example was about 5 major versions behind the current. Why the master / old tests were working - I have no idea.

first of all thanks again for the fast help on the travis ci and the hotfix!
On future fixes we should use different branches to maintain the seperation of concerns in our project, but since we worked this out in direct contact and we have a stable version afterwards it should be fine this time :-)
This pull request will adress the issues #61, as well as it will add tests for sorting the table and it will fix an issue in the current master, where the repo was not opened in a correct way


CI: add github action for circleci artifact url

Merged in https://github.com/pandas-dev/pandas-sphinx-theme/pull/52


operator: check for empty configmap before update

check for empty field 'data' in configmap before updating otherwise it will through nil pointer error.

Description of your changes:
Which issue is resolved by this Pull Request:
Resolves #
Checklist:

[ ] Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide.
[ ] Reviewed the developer guide on Submitting a Pull Request
[ ] CI tests has been updated, if necessary.
[ ] Documentation has been updated, if necessary.
[ ] Unit tests have been added, if necessary.

Merging the pr, since the issue is a know timeout issue.


If an attribute is a date; and used as a dot-notation key

fix it after parent attributeToArray.
as i've noticed fromDateTime behavior on setAttribute. i still don't get it, why it's not in the getAttributesToArray

Coverage decreased (-0.15%) to 96.11% when pulling 3562a570b27faaeb5d8c8d3a5f939c52c6aa0f30 on spawn-guy:feature_mongoDotDates into 52145b0cda105219779f0a195a62bec981372e23 on jenssegers:master.

I had to merge you changes manually, they are now in dev-master, thanks!


normal logout show token expired

In GitLab by @tmon546596046 on Apr 2, 2019, 09:53
unify helm release table name to 'helm_release'

In GitLab by @sokril on Nov 8, 2019, 08:32
assigned to @liyanq528

In GitLab by @liyanq528 on Dec 23, 2019, 06:02
Passed validation by Cuiaiqin.PR 2080 on Gogs.

In GitLab by @liyanq528 on Dec 23, 2019, 06:02
closed


set_rate missing for rawGps

Hi,
rawGps info now can be accessed with v0.38+, but I found that its missing something like "telemetry.set_rate_rawGps()" as the position can do "telemetry.set_rate_position()". Is this a missing feature or there is another way to set the rawGps access rate?
Best

Hi, good question. You can actually just use set_rate_gps_info as the underlying mavlink message is the same.
@JonasVautherin should we add it nevertheless or add a comment to clarify this?

I first was thinking about adding it, and handling the case where somebody does set_rate_gps_info() AND set_rate_raw_gps like this:

If both subscribe_gps_info and subscribe_raw_gps are active, use the max of both rate values
If only one is active, take its rate

The problem is for the polling interface: what if I want to poll gps_info very fast, but subscribed to raw_gps at a slow rate? Or maybe something like:

If both subscribe_gps_info and subscribe_raw_gps are active, use the max of both rate values
If only one is active, take its rate
If set_rate_ has been called (even if the subscription is inactive), use that rate in the max computation

Which then means that if you do set_rate_gps_info and then only poll raw_gps, you see the effect of the new rate (if that rate was faster than the default). Not sure if that's a problem, though... And we should document the behavior, and maybe add a log line when set_rate_ is being set to the lower value and is therefore ignored.
Not perfect, but that's the best I can think of to have a rather natural way of using both rates :sweat_smile:


Update of store after adding ADDITIONAL XML DATA FIELDS is not resistant to duplicated id.

Steps to reproduce:

define minimal XmlDataSource :

Run job "update stores offers"
logs: https://gist.github.com/noisy/04a892bc8fdafff00dac305639ea209c

modify XmlDataSource by adding ADDITIONAL XML DATA FIELD:

Run job "update stores offers

Current behavior:
update fail
logs: https://gist.github.com/noisy/b41fb149118152a2bb7ab6adcfbd2fed
Expected behavior:
Offers with duplicated Id should be ignored (like in first update)

Because of lost old revision of XMLfiles, right now I am not able to reproduce this problem :( In case of reoccurrence, please let me know


Issue with merge-anything

I couldn't build my React Native project anymore due to an issue with merge-anything :
While trying to resolve module 'merge-anything'... this package itself specifies a 'main' module field that could not be resolved
I managed to fix this by changing the dependency in package.json from ^4.0.2 to 4.0.2.

Thanks for reporting. Can you create a PR for it?

Done! #631

@CptMaumau Thanks for you pull request. It's merged and fixed on v3.0.1. If you have any trouble, please re-open this issue. Thanks!

Fixed on v3.4.2. I removed merge-anything module completely. If you are using the hacky patch-package workaround, please stop using it and try the latest version.


calculate folder's size With filemin for clients after upgrade to 17.53

I have noticed after i have upgraded to 17.53 that when the client click on calculate folder's size at context menu it will not calculate its size always displays 0 byte.
Thx.

I will take a look.
Meanwhile, reload/clear browser's cache and restart Webmin. If you go to theme's settings and choose autocalulation feature, will it work then?

I Cleared the cache and i have restarted Webmin and i changed the setting to autocalculate but it did not solved the problem

Are you sure that you have upgraded the theme for the users. You're talking about Usermin, right?
It works for me and others I talked with in Webmin/Usermin and in other distributions... in both root and user modes.
Have a look.
https://rostovtsev.ru/pub/src/authentic/17.54b/working_file_size_detection.webm
In case it's not the same for you, please make video-screencast with opened console and will figure this out.
Which browser are you using by the way?

The problem is in virtualmin and only for clients it is working with root only
in usermin it is working very well for all clients
I am using Google Chrome
but anyway i will give you a link for a screencast after i did in couple mins.

Mmm.. I see. I'll test in VM mode.

Here is the link http://hasanalsamra.tk/sc/sc.ogv

Thanks! I see. I will try fixing it in 17.54 very soon.

Thanks alot for your response and your time
+1 Keep good job!

..I'm already fixing it.. I got the cause! Thanks for reporting!

Please update to 17.54. All should be working fine.

Yes working thank you so much
:+1:  :)

:)

Indeed calculating folder size is working fine, however what if eg. someone has 25 or more websites to check... Select one by one is a bit annoying process. Is possible to check folder size for all catalogs after clicking on eg.: "Select All" or just add another button "Calculate size"

Yes. It's in my list! ;)

Wow! Sounds good. Hope you won't stop developing this great project after starting work for eg. Google.... ;)
Thanks again for your time developing the theme.

This feature will be supported in 17.64. ;) Thank you for the great ideas!

..I meant 17.63

17.63 will also provide an ability to enter path manually. Read changelog please,

Please upgrade.


deis/mock-store container persists after test runs

After a full test-integration.sh run, there is often a container left:
$ docker ps
CONTAINER ID        IMAGE                    COMMAND             CREATED             STATUS              PORTS                    NAMES
535040b18c8c        deis/mock-store:latest   "/app/bin/boot"     17 minutes ago      Up 17 minutes                                deis-ceph-git-970515f
76d6006d59d0        registry:0.9.0           "docker-registry"   About an hour ago   Up About an hour    <IP_ADDRESS>:5000->5000/tcp   registry

We need to add similar cleanup code in the tests as we do for deis/test-etcd.

Indeed, though I see this after running the functional tests so something's not getting cleaned up there.

Potentially related is #3140


Ignore hidden files

Migration runner tried to run the migration .DS_Store which is a hidden mac filesystem file.
Should probably do some smart filtering on filenames, visibility, etc.

You can define files to ignore when running migration but maybe (hidden) files starting with dot can be ignored by default 🤔


Upstream functionality to lift single-use parameters into the module that uses them into fx.passes.split_module

We have this code to move parameters that are only used by one module into the using module:
https://github.com/jamesr66a/PiPPy/blob/527af1fd8123d35bd81b9fe304a8d0ed29c9fd8d/pippy/IR.py#L408
We should upstream this into the fx.passes.split_module implementation

cc @SherlockNoMad might be something interesting to add to the unified split infrastructure you're building


Localization of STN models

@chufengt hi thanks for sharing the code base, for localization of attributes which intermediate feature[feat3b,feat4d,feat5b] gives the best accuracy ?
Q2. Does the accuracy of localization varry based on the feature layer and the attributes eg: global attributes localization is obtained best from feat5d and local attributes localization is best from feat3b like that
Pls share your thoughts

I didn't try these 3 feature layers individually.
It makes sense since global attributes usually require high-level semantics (e.g. feat5d) and local attributes benefit from higher resolution (e.g. feat3b).

@chufengt  any thoughts on how to calculate the accuracy of the localization modules

Just try to attach the ALM module on a specific feature layer (e.g. feat3b only), and train these different models.
Using only one feature layer is usually worse than multi-layers.


This code passes, but I don't think it should.

Challenge Map the Debris has an issue.
User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.98 Safari/537.36 OPR/44.0.2510.857.
Please describe how to reproduce this issue, and include links to screenshots if possible.
Perhaps I am being pedantic, but the instructions say to 'return a new array', yet my code mutates the passed-in array, and returns it. Shouldn't the tests disallow this?
BTW, this is my first-ever issue report, so be kind to me if it's inappropriate.
My code:
function findPeriod(avgAlt) {
  var GM =<PHONE_NUMBER>,
      earthRadius = 6367.4447,
      distFromMiddleEarth = earthRadius + avgAlt,
      dme3 = Math.pow(distFromMiddleEarth,3),
      dme3overGM = dme3 / GM;

  return 2 * Math.PI * Math.sqrt(dme3overGM);
}
function orbitalPeriod(arr) {
  var i, arrLen = arr.length;
  for (i = 0; i < arrLen; i++) {
    arr[i].orbitalPeriod = Math.round(findPeriod(arr[i].avgAlt));
    delete arr[i].avgAlt;
  }
  return arr;
}

orbitalPeriod([{name : "sputnik", avgAlt : 35873.5553}]);

@dennis-wolfers thanks for the issue and feedback! Our challenges are to teach concepts and how to program. Whether it is good practice or not to modify your input parameters is another discussion :smile:  So I don't think there are any issues with mutating the passed-in array for this particular challenge, especially when the purpose of this challenge is to combine a lot of mathematical concepts you've learned. Happy coding!


Write utility function for anlayzing sparsity

Write function in the package for analyzing sparse encoding matrix. Normalize weights in a given LV. For the model that achieves > 90% sparsity, look at the encoding matrix -- is it interpretable?

Done


Metrics/collect task requires an initial delay parameter

Is your feature request related to a problem? Please describe the problem.
Even though a deployment is available,  and a service backed by this deployment is present, the routes for the service may still not have DNS entries yet in K8s, making the Fortio metrics collection fail in Iter8 handler.
Describe the feature/solution you'd like
Introduce an initialDelaySeconds input to the metrics/collect task (with a 20 second default), so that the user has a way to not start the Fortio data collection right away, but only after an init delay.
Will this feature/solution bring new benefits for Iter8 users? What are they?
Make builtin metrics more usable.
Does this issue require a design doc/discussion? If there is a link to the design document/discussions, please provide it below.
See above.
How will this feature be tested?

[ ] e2e tested in tutorials.

How will this feature be documented?

[ ] iter8.tools documentation.

Subsumed by #940


Bumping version of aiobotocore to 2.2.0

In a attempt to solve https://github.com/fsspec/s3fs/issues/558  I am following suggestion from the aiobotocore contributors to update its version to solve the issue https://github.com/aio-libs/aiobotocore/issues/901#issuecomment-1069891573

Please also update in the test runs, e.g., https://github.com/fsspec/s3fs/blob/main/.github/workflows/ci.yml#L36

Ah, if aiobotocore 2.2.0 is not even out on conda(-forge), then we'll definitely have to wait.

I have just launched a PR for aibotocore to be updated in conda-forge
https://github.com/conda-forge/aiobotocore-feedstock/pull/51

OK, please ping here when that is merged and the new packages ready.

@martindurant the package is updated on condaforge. Can you try this build again please ?


Consider extending JsonApiModelBuilder to build the collection model

Currently JsonApiModelBuilder always creates instance of JsonApiModel  which is however not the CollectionModel. This effectively prevents usage in correct custom implementation of RepresentationModelAssembler - namely there is no way how to insert included into such collection.
From the other point of view, JSON:API coumpound document (which is usually used as the collection representation) could be also considered not beeing representation of CollectionModel. So this idea is questionable.

This is true, but if you use the JSON:API model builder, you would probably like to use JSON:API specific features like relationships and included. You could then easily create your own ModelAssembler that provides a method toRepresentationModel(Iterable<? extends T> entities) that returns a RepresentetionModel<?>. In this method, you could use the builder.


Failed setting prop "attributes" on stub

Defining a prop named attributes on a stubbed component throws a warning.
Failed setting prop "attributes" on <child-component-stub>: value test123 is invalid:

https://stackblitz.com/edit/vitest-dev-vitest-wqbs9d?file=test/basic.test.ts
import { defineComponent } from 'vue';
import { mount } from '@vue/test-utils';

const ChildComponent = defineComponent({
  props: {
    attributes: {
      type: String,
      default: null,
    },
  },
});

const ParentComponent = defineComponent({
  components: { ChildComponent },
  template: `<ChildComponent attributes="test123" />`,
});

test('it stubs component', () => {
  const wrapper = mount(ParentComponent, { shallow: true });
});

Hi @ol1s
Thank you for the repro
I think this expected (sort of), as attributes is a read-only DOM property (see https://developer.mozilla.org/en-US/docs/Web/API/Element/attributes), so Vue warns you about it.
You can reproduce with Vue itself easily: https://sfc.vuejs.org/#eNpNUE1rwzAM/SvCF6eQJuyadYWxy36EL2mrLC7xB5bcDYL/++Q0gx2M/CQ9vSet6j3G7pFRDepE12Qjn423LobEsMINJ+vxIwj26LmFGQpMKTjQwtGvxgPUhz8bQdrHvGzxP61Zaw8AIefYHGCHAEkSyYOk3s4wN/pmH7oV2ZE52UtmpAFeoLSgP3FZgj48iaWGIuDU75ZVq56ej26M3Z2Cl302GbMXyKjhT9goMV+xUTNzpKHvabrWK9ypC+mrl1+XsmfrsENyx0sK34RJBhu1aRtfVPkFFY5o/Q==
I don't think we can do much about that in VTU.
In your case, you can either:

ignore the warning (spy on `console.warn for example)
name your props differently
use a custom stub instead of the automatically generated one


Anti-Malware URL in this article points to old experience (Ex Admin), and not the new SCC experience. Please update the URL in this article.

The _https://protection.office.com/antimalware_ URL in this article is now outdated and does not redirect to the updated experience. The correct URL (as of Dec 2020, and as per the M365 portal*) is https://protection.office.com/antimalwarev2
Screen capture attached for current URL redirect message when one goes to the currently listed URL.

Thank you for updating this at your earliest convenience.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: db041b73-f7c9-db6c-070b-a7c974de640c
Version Independent ID: dffb7045-3ba8-a014-d1be-462ca1d609b5
Content: Configure anti-malware policies - Office 365
Content Source: microsoft-365/security/office-365-security/configure-anti-malware-policies.md
Product: m365-security
Technology: mdo
GitHub Login: @chrisda
Microsoft Alias: chrisda

@christinamorillo, funny you should ask.
The Microsoft 365 security center became globally available (not just in Preview) only a few weeks ago. We've just started our effort to convert any/all procedures/click paths/UI references under https://docs.microsoft.com/microsoft-365/security/office-365-security/ from Security & Compliance Center to Microsoft 365 security center. That will be a rolling effort over the next several weeks (and possibly months).
For the Configure anti-malware policies topic, I did all of the updates last week and just merged the changes earlier today. The updated topic should go live after 5:00 PM PDT today Mon 5/24).
I'm going to close this issue, but feel free to re-open if you don't see the changes.
Thanks for the feedback.


Background Music event sometimes not working when changing timelines

The problem
Describe the bug
Sometimes the Background Music event doesn't start the track when changing timelines using Change Timeline.
It works as intended if I start the second timeline directly.
To Reproduce
Steps to reproduce the behavior:

Create a timeline with a Background Music event with some audio at the start and an empty Background Music event at the end.
Create a second timeline with another Background Music event at the start.
Play trough the game and sometimes the music in the second timeline doesn't start.

Expected behavior
Stop the first background music, change timelines (or scenes) then play another track.
Screenshots

System

OS: Windows 10 20H2 - 64bit
Godot Version: 3.3.stable.mono
Dialogic Version: 1.1

Solutions
Workaround
Create separate Godot scenes with different timelines assigned to them and then load and change them trough code outside of Dialogic.

I have a similar issue however I am unable to change music more than once, I can start playing music and then change it, but after this point I am stuck with that music unable to stop it or change it.

I need to revisit how these nodes work. Hopefully I can make a better version of them for 1.2

Can you try with the latest version? it might be fixed already :)

Updated to the 1.2 beta and the issue I had is now fixed thank you for the great plugin


How to use mysql find_in_set function in querydsl?

Expressions.booleanTemplate("FIND_IN_SET({0}, {1})", path, param)
It doesn't working.
It cause
Caused by: org.hibernate.hql.internal.ast.QuerySyntaxException: unexpected AST node: ( near line 3, column 18 [select task
from com.simple.entity.Task task
where FIND_IN_SET(task.parentIds, ?1)]

This is because Hibernate doenst allow the find in set function in the MySQL dialect.
You should use a custom dialect or register a custom function. It is also possible to wrap the function in a JPQL Function-function.


Exception in async_message_received

Checklist

[X] I have updated the integration to the latest version available
[X] I have checked if the problem is already reported

The problem
I am receiving the following error when the vacuum (Roborock S50) is running the 2024.5.b3 beta version of Home Assistant:
Logger: homeassistant.util.logging
Source: util/logging.py:98
First occurred: 10:00:07 (177 occurrences)
Last logged: 14:33:21

Exception in async_message_received when handling msg on 'valetudo/roborock_downstairs/BatteryStateAttribute/level': '96' Traceback (most recent call last): File "/config/custom_components/valetudo_vacuum_camera/valetudo/MQTT/connector.py", line 322, in async_message_received await self.hypfer_handle_battery_level(msg) File "/config/custom_components/valetudo_vacuum_camera/valetudo/MQTT/connector.py", line 208, in hypfer_handle_battery_level self._mqtt_vac_battery_level = int(bytes.decode(self._payload, "utf-8")) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ TypeError: descriptor 'decode' for 'bytes' objects doesn't apply to a 'str' object
Exception in async_message_received when handling msg on 'valetudo/roborock_downstairs/BatteryStateAttribute/level': '97' Traceback (most recent call last): File "/config/custom_components/valetudo_vacuum_camera/valetudo/MQTT/connector.py", line 322, in async_message_received await self.hypfer_handle_battery_level(msg) File "/config/custom_components/valetudo_vacuum_camera/valetudo/MQTT/connector.py", line 208, in hypfer_handle_battery_level self._mqtt_vac_battery_level = int(bytes.decode(self._payload, "utf-8")) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ TypeError: descriptor 'decode' for 'bytes' objects doesn't apply to a 'str' object
Exception in async_message_received when handling msg on 'valetudo/roborock_downstairs/BatteryStateAttribute/level': '98' Traceback (most recent call last): File "/config/custom_components/valetudo_vacuum_camera/valetudo/MQTT/connector.py", line 322, in async_message_received await self.hypfer_handle_battery_level(msg) File "/config/custom_components/valetudo_vacuum_camera/valetudo/MQTT/connector.py", line 208, in hypfer_handle_battery_level self._mqtt_vac_battery_level = int(bytes.decode(self._payload, "utf-8")) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ TypeError: descriptor 'decode' for 'bytes' objects doesn't apply to a 'str' object
Exception in async_message_received when handling msg on 'valetudo/roborock_downstairs/BatteryStateAttribute/level': '99' Traceback (most recent call last): File "/config/custom_components/valetudo_vacuum_camera/valetudo/MQTT/connector.py", line 322, in async_message_received await self.hypfer_handle_battery_level(msg) File "/config/custom_components/valetudo_vacuum_camera/valetudo/MQTT/connector.py", line 208, in hypfer_handle_battery_level self._mqtt_vac_battery_level = int(bytes.decode(self._payload, "utf-8")) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ TypeError: descriptor 'decode' for 'bytes' objects doesn't apply to a 'str' object
Exception in async_message_received when handling msg on 'valetudo/roborock_downstairs/BatteryStateAttribute/level': '100' Traceback (most recent call last): File "/config/custom_components/valetudo_vacuum_camera/valetudo/MQTT/connector.py", line 322, in async_message_received await self.hypfer_handle_battery_level(msg) File "/config/custom_components/valetudo_vacuum_camera/valetudo/MQTT/connector.py", line 208, in hypfer_handle_battery_level self._mqtt_vac_battery_level = int(bytes.decode(self._payload, "utf-8")) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ TypeError: descriptor 'decode' for 'bytes' objects doesn't apply to a 'str' object

What version of an integration has described problem?
2024.04.5
What was the last working version of an integration?
No response
What vacuum model do you have problems with?
Roborock S50
Please firmware installed on your Vacuum.
2024.02.0
What type of platform you use?
Intel NUC (or generic x86_64)
What version of Home Assistant do you use?
core-2024.5.0b3
What type of installation are you running?
Home Assistant OS
Camera's settings.
No response
Logs or Errors shown in the HA snapshots (please enable the Debug Mode)
No response
Additional information
No response

@tomlut I will check it as soon the b03 is completely installed, I did upload yesterday a new version of the connector.py and opened also an issue on the core for HA. It is a know issue, in any cases good that you opened it because it will help to trace the fix.

Excellent. Do you need any more diagnostic info?

Excellent. Do you need any more diagnostic info?

Well I did raised the issue on core because I catch it while testing the 2024.05.0 (camera wise).. I just confirmed that all works fine with the fix on the next version. Will update the camera later today (the pull request is open right now you can have a look on the connector.py) ;)

17 files in the PR. You have been busy!

@tomlut  released 2024.05.0 with the fix for this issue #128 hope this will work also for you ;)


python3Packages.env-canada: 0.5.1 -> 0.5.12

Motivation for this change
Update to latest upstream release 0.5.12
Change log: https://github.com/michaeldavie/env_canada/releases/tag/v0.5.12
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 via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution 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.

Result of nixpkgs-review pr 138615 run on x86_64-linux 1

2 packages built:

python38Packages.env-canada
python39Packages.env-canada


remove RCT prefix for native modules

Summary
In RN 0.36 there has been a lot of refactoring. One of the changes is that the NativeModules.js now expects the modules to not have RCT or PK prefixes anymore. Which causes the mock to be invalid. This simply changes the mock to be updated to the shape NativeModules.js expects.
Now, tests are still broken in 0.36 due to https://github.com/facebook/react-native/blob/292cc82d0ebc437a6f1cdd2e972b3917b7ee05a4/Libraries/Core/InitializeCore.js#L186-L196 which tries to start a websocket in test mode. I am not sure how to go about that. PR react-native to change it or mock it somehow in Jest?

Fixes #1912

Current coverage is 88.00% (diff: 100%)

Merging #1989 into master will not change coverage

@@             master      #1989   diff @@
==========================================
  Files            38         38
  Lines          1251       1251
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1101       1101
  Misses          150        150
  Partials          0          0

Powered by Codecov. Last update bff3bce...05f5436

Thanks @edvinerikson for your contributions. This is great!

It is released on npm ?

It's released as jest@test and jest-react-native@test. next release of Jest will likely be next week.

Ok perfect thanks! 👍


Bug: The session has expired error when connecting to version 1.3.0

Describe the bug
version 1.3.0 has websocket session expire feature, and throw The session has expired error.
Are we supposed to handle this on our own, or this should be handled by driver?
Steps to reproduce
make connection, idle for a while, then make a request
Expected behaviour
no error, and request go through, result successfully returned
SurrealDB version
surreal 1.3.0
Contact Details
No response
Is there an existing issue for this?

[X] I have searched the existing issues

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I handled this in my own code

@agufagit how did you handle it? am also facing the same issue

@agufagit how did you handle it? am also facing the same issue

if error not nil and error message contains "session has expired", close connection, call the function again to get new connection from pool
below is exact part of code where I handle this error, Query(c, query, parameters) is the function that contains this code
resultRaw, err := conn.Query(query, parameters)
if err != nil {
if strings.Contains(err.Error(), "session has expired") {
	println("1. db session expired")
	errCloseConn := conn.CloseWithNew()
	if errCloseConn != nil {
		return nil, errors.Wrap(defaultErrors.Join(err, errCloseConn), "The session has expired, error closing db connection")
	}
	return Query(c, query, parameters)
}
callback(false)

return nil, err
}

ok nice implemented it, ty also  just noticed the bug has been fixed in version 1.3.1


action failing with 'Cannot query field "customAttributes" on type "ChangeTrackingDeployment"' error

I'm using<EMAIL_ADDRESS>and earlier today action runs started failing with the message Error:  level=fatal msg="Cannot query field \"customAttributes\" on type \"ChangeTrackingDeployment\".". Here is the log for the step:
2023-10-30T18:52:16.4224730Z ##[group]Run<EMAIL_ADDRESS>2023-10-30T18:52:16.4225273Z with:
2023-10-30T18:52:16.4225685Z   apiKey: ***
2023-10-30T18:52:16.4226082Z   commit: 907328f41047766fe14794f81f92b19304b1427d
2023-10-30T18:52:16.4226594Z   deploymentType: BLUE_GREEN
2023-10-30T18:52:16.4227026Z   description: Github Actions Deploy
2023-10-30T18:52:16.4227504Z   groupId: Github Actions Deploy: main
2023-10-30T18:52:16.4228093Z   guid: ***
2023-10-30T18:52:16.4228398Z   user: benburkert
2023-10-30T18:52:16.4228729Z   version: main
2023-10-30T18:52:16.4229056Z   region: US
2023-10-30T18:52:16.4229357Z env:
2023-10-30T18:52:16.4229836Z   NEW_RELIC_GUID: ***
2023-10-30T18:52:16.4230202Z ##[endgroup]
2023-10-30T18:52:16.4530785Z ##[command]/usr/bin/docker run --name b835f03f612be9e5438aacffd18e69ecdf55_d1258d --label 47b835 --workdir /github/workspace --rm -e "NEW_RELIC_GUID" -e "INPUT_APIKEY" -e "INPUT_COMMIT" -e "INPUT_DEPLOYMENTTYPE" -e "INPUT_DESCRIPTION" -e "INPUT_GROUPID" -e "INPUT_GUID" -e "INPUT_USER" -e "INPUT_VERSION" -e "INPUT_REGION" -e "INPUT_CHANGELOG" -e "INPUT_DEEPLINK" -e "NEW_RELIC_API_KEY" -e "NEW_RELIC_DEPLOYMENT_ENTITY_GUID" -e "NEW_RELIC_REGION" -e "NEW_RELIC_DEPLOYMENT_USER" -e "NEW_RELIC_DEPLOYMENT_VERSION" -e "NEW_RELIC_DEPLOYMENT_CHANGE_LOG" -e "NEW_RELIC_DEPLOYMENT_COMMIT" -e "NEW_RELIC_DEPLOYMENT_DESCRIPTION" -e "NEW_RELIC_DEPLOYMENT_DEEPLINK" -e "NEW_RELIC_DEPLOYMENT_TYPE" -e "NEW_RELIC_DEPLOYMENT_GROUP_ID" -e "NEW_RELIC_SERVICE_NAME" -e "HOME" -e "GITHUB_JOB" -e "GITHUB_REF" -e "GITHUB_SHA" -e "GITHUB_REPOSITORY" -e "GITHUB_REPOSITORY_OWNER" -e "GITHUB_REPOSITORY_OWNER_ID" -e "GITHUB_RUN_ID" -e "GITHUB_RUN_NUMBER" -e "GITHUB_RETENTION_DAYS" -e "GITHUB_RUN_ATTEMPT" -e "GITHUB_REPOSITORY_ID" -e "GITHUB_ACTOR_ID" -e "GITHUB_ACTOR" -e "GITHUB_TRIGGERING_ACTOR" -e "GITHUB_WORKFLOW" -e "GITHUB_HEAD_REF" -e "GITHUB_BASE_REF" -e "GITHUB_EVENT_NAME" -e "GITHUB_SERVER_URL" -e "GITHUB_API_URL" -e "GITHUB_GRAPHQL_URL" -e "GITHUB_REF_NAME" -e "GITHUB_REF_PROTECTED" -e "GITHUB_REF_TYPE" -e "GITHUB_WORKFLOW_REF" -e "GITHUB_WORKFLOW_SHA" -e "GITHUB_WORKSPACE" -e "GITHUB_ACTION" -e "GITHUB_EVENT_PATH" -e "GITHUB_ACTION_REPOSITORY" -e "GITHUB_ACTION_REF" -e "GITHUB_PATH" -e "GITHUB_ENV" -e "GITHUB_STEP_SUMMARY" -e "GITHUB_STATE" -e "GITHUB_OUTPUT" -e "RUNNER_OS" -e "RUNNER_ARCH" -e "RUNNER_NAME" -e "RUNNER_ENVIRONMENT" -e "RUNNER_TOOL_CACHE" -e "RUNNER_TEMP" -e "RUNNER_WORKSPACE" -e "ACTIONS_RUNTIME_URL" -e "ACTIONS_RUNTIME_TOKEN" -e "ACTIONS_CACHE_URL" -e "ACTIONS_RESULTS_URL" -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/anchor/anchor":"/github/workspace" 47b835:f03f612be9e5438aacffd18e69ecdf55
2023-10-30T18:52:18.1942844Z level=fatal msg="Cannot query field \"customAttributes\" on type \"ChangeTrackingDeployment\"."
2023-10-30T18:52:18.2064726Z ##[error] level=fatal msg="Cannot query field \"customAttributes\" on type \"ChangeTrackingDeployment\"."

And here is what my action yml config looks like:
      - name: "Deploys: anchord New Relic deploy marker"
        env:
          NEW_RELIC_GUID: ${{ secrets.NEW_RELIC_BE_ANCHORD_PRD_GUID }}
        if: env.NEW_RELIC_GUID != ''
        uses<EMAIL_ADDRESS>        with:
          apiKey: ${{ secrets.NEW_RELIC_API_KEY }}
          commit: ${{ github.sha }}
          deploymentType: "BLUE_GREEN"
          description: "Github Actions Deploy"
          groupId: "Github Actions Deploy: ${{ github.ref_name }}"
          guid: ${{ env.NEW_RELIC_GUID }}
          user: ${{ github.actor }}
          version: ${{ github.ref_name }}

The config hasn't changed recently and, as far as I know, the credentials are still valid.

Can confirm, we just ran into the same issue earlier.

I don't see any recent commits to the action that might explain this so this is most likely a breaking change in the API ?

The action is setup to float to the latest version of the newrelic/cli container and that is now on v0.74 of the cli.
Unfortunately the latest cli version is expecting a property from their graphql api (NerdGraph), which isn't live yet.  Either they need to deploy the updated graphql api or roll back the cli to not ask for the missing property.
Not much you can do about this since they deployed a change in their client before the server, and allow the action to float to latest client.

yeah, this PR was merged in 4 hours ago, causing this issue 🤦
https://github.com/newrelic/newrelic-cli/pull/1526

PR opened to fix this by pinning the cli.  I'd argue it should always be pinned and handled like the dependency it is.

Sorry about that everyone. A version of the CLI went out today with an API that is not yet GA. I merged @barryhagan's PR to pin the CLI to the previous version hopefully unblocking you all.

@mbazhlekova i think this will still be an issue until there is a new release of this repo. And for anyone who has pinned to the current point release, wont it require a new release of the cli docker container?

@benburkert - yeah, it is still an issue if you are using the versioned action like this:
  uses<EMAIL_ADDRESS>
There needs to be a new release/tag to get an action version that is pinned to the working cli.  You should be able to workaround this immediately by specifying the main branch until there is a tagged release after my PR. (a temporary fix, not recommended long term):
  uses: newrelic/deployment-marker-action@main

Actually we're going to release a new version of the CLI without the commit that's causing the problem to get around having to update the deployment marker version.

You should still release a v2.5.0 of this with the pinned CLI version.   I appreciate that the CLI rollback will fix the 2.4.0 version that everyone is using for now, but that doesn't address the floating dependency problem.
Every single time someone runs this action, they are taking the latest release of the CLI container at that moment.  As we found today, that is not always a good thing.
This is a stable solution that I will use until you tag a new release:

@barryhagan v2.5.0 is out with your change to pin the version


endless takes over param handling

Expected behavior: endless to append whatever runtime args it needs, but preserve the application command line params.
Actual behavior: endless takes over the command line params, and treats all application params as illegal
What's most curious is that args required by the main app are still considered required, even though providing them is disallowed by endless.
1074)internationalsos/riskratings % ./rr -h
Usage of ./rr:
  -continue=false: Dummy -- needed by endless
  -debug=false: Enable debugging
  -pass="": Password
  -port=":8080": Listen port
  -refresh=10: Cache refresh time, in minutes
  -uri="******************": URI of data source
  -user="": Username
1075)internationalsos/riskratings % ./rr
Password is required
Usage of ./rr:
  -continue=false: Dummy -- needed by endless
  -debug=false: Enable debugging
  -pass="": Password
  -port=":8080": Listen port
  -refresh=10: Cache refresh time, in minutes
  -uri="******************": URI of data source
  -user="": Username
1076)internationalsos/riskratings % ./rr -pass xyz -user abc -port :8123
2015/06/29 22:33:58 start listening on localhost:8123
flag provided but not defined: -pass
Usage of ./rr:
  -continue=false: listen on open fd (after forking)
  -socketorder="": previous initialization order - used when more than one listener was started

i believe this is due to when/where/how you call flag.Parse()
endless allows other flags to be defined,  preserves them, and appends its own at the end.
have a look here: https://gist.github.com/fvbock/855a980deed441cc31cd
if you compile and run that:
$ go build -o flags flags.go
$ ./flags -paramA pValA -paramB
2015/06/30 14:55:15 Got passed: [-paramA pValA -paramB]  # this is from os.Args[1:]
2015/06/30 14:55:15 paramA pValA
2015/06/30 14:55:15 paramB true
2015/06/30 14:55:16 22335 localhost:4242

Now send SIGHUP
$ kill -1 22335

2015/06/30 14:55:30 22335 Received SIGHUP. forking.
2015/06/30 14:55:30 Got passed: [-paramA pValA -paramB -continue]
2015/06/30 14:55:30 paramA pValA
2015/06/30 14:55:30 paramB true
2015/06/30 14:55:30 22351 localhost:4242

the original parameters are kept and endless appends it's own parameters at the end.
does this help?

When I posted the issue, it briefly crossed my mind that it might be a library interaction, but the lateness of the hour left me too lazy to test it.
It turns out that this is an interaction between endless and my favorite drop-in flag parsing library by namsral.  Try this code and the pattern fails.  Use the Go standard flag library and it succeeds.
I don't yet know in which library the issue lies, so I'll withdraw the ticket until I can investigate further.
Thanks for the speedy and civil response.

FYI https://github.com/namsral/flag/issues/3

Really closed. This is not an endless issue.  For the curious, this can be followed in namsral/flag.


Auto Generate POCO

Is it possible to auto generate class like EdiFact_Issue152_Wikipedia_Transmission.cs based on schema or XSD files? I would like to create a ITAREQ, TKTREQ ... for IATA.

Hi @dvddo I am not sure I understand the question. The library is based on the foundation that you have described the spec for the transmission via dotnet attribute annotations. Theoretically one could make a dynamic class via Roslyn compiler and load that. Why you would need to generate the class based on schema. I suppose that these 3 are fixed transmissions. If you have all tree transmission types in classes you could serialize from and to an EDI text stream.

Perhaps i misunderstand how the edi.net work. EdiFact_Issue152_Wikipedia_Transmission.cs is a POCO. It is used to translate the PAORES 93.1A message. If i give it a PAOREQ 93.1A message i need a separate POCO for it. Is this is not true for other IATA Edifact messages also? If is the case, i need to create a new POCO for each different version of the Edifact 98.1A, 98.1B, 2001.1A, 2001B and so forth. There could be potentially thousands of template so building each one from scratch seems daunting. I am familiar with biztalk and believe it uses xsd file for translate PNRGOV messages into xml. I wonder if it it can be done here also? Would love to contribute to this project this is something worthwhile.

Thank you for looking into this. I understand your time needs to be manage correctly. POCO files are really up to user to create. I will try to create one from scratch to see what is involved. All of the documentation should be found in the issues search or is there a separate section i can find it?
Thanks again.

Hi @dvddo,
there is no documentation unfortunately you will have to dig into the issues. But I have strived to answer as many as I can so there is a big deal of information.
I wish I did have the time to extract that into a wiki docs folder.


[Multitimer] fix for icon

Might've accidentally uploaded an older icon - this one should work on the Bangle. Don't think I should bother with a new version?

No, that's fine - thanks!


Update Import-RecipientDataProperty.md

Related to Issue #8628

Docs Build status updates of commit 78398c3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Import-RecipientDataProperty.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit b2329f9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Import-RecipientDataProperty.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 32b55d1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Import-RecipientDataProperty.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


[Enhancement] Display a banner in the Pod Security Admission resource to ease transition of new users from PSPs

Setup

Rancher version: v2.7.2-rc3
Browser type & version: chrome

Describe the bug

When a cluster has PSAs applied in the cluster.yaml, the PSAs are not showing up when viewed through the cluster. This is because PSA works differently than PSPs, and only show through the local cluster (not downstream clusters)
To Reproduce

deploy a cluster with PSAs enabled.
Check the Pod Security Admissions resource in the downstream cluster
Result
see screenshots, no PSAs show up in the cluster (only available via the local cluster)
Expected Result

Clear to the user how to use the new security set from k8s
perhaps adding something like the following to the banner would be helpful:
Only administrators can make changes to any PSAs applied on downstream clusters via the local cluster

Screenshots

Additional Info
could just be added to the existing banner: https://github.com/rancher/dashboard/issues/8037

closing this issue, as it is intended behavior.

Some technical background information about the PodSecurityAdmissionConfigurationTemplate(PSACT) CRD in the downstream cluster:
The CRD exists in the downstream cluster but never be used. We have it due to a limitation in rancher-webhook: because the same rancher-webhook app is installed in both the local and downstream cluster(with different values, of course), and the app requires the PodSecurityAdmissionConfigurationTemplate CRD to exist in the cluster, therefore we have to install the CRD into the downstream clusters.
One more note: creating the CRs in the downstream cluster does not hurt anything, users cannot use it to configure the cluster or anything. It is simply useless.
cc @slickwarren

@slickwarren What is the ask? What do you want the banner to say? Are you asking for better wording for the banner you showed above?

I'm asking that we either add this info to the existing banner or have an additional banner in this resource to inform the user that PSA changes for downstream clusters must be done from the local cluster.
This was my original suggestion, but open to better wording / alternatives:
Only administrators can make changes to any PSAs applied on downstream clusters via the local cluster

One more note: creating the CRs in the downstream cluster does not hurt anything, users cannot use it to configure the cluster or anything. It is simply useless.

Given this extra info, I think it'd make more sense to hide PSACTs in downstream clusters entirely. What do you think @slickwarren ?

I cannot think of a use case that would be affected by hiding this in downstream clusters. As long as the CRDs for it aren't affected, that sounds like a good solution to me @mantis-toboggan-md

We can hide it purely visually without affecting the CRDs.

tested on v2.7-head (cd1a716) using dashboard https://releases.rancher.com/dashboard/latest/index.html:

local cluster still has PSA available -- pass
downstream clusters do not have PSA available in the cluster -- pass


Manual

That would be super nice to have a little manual on creating your own site modules
Could you please make it?

Currently there is only the Wiki that contains some info on creating site modules:
https://github.com/lightos/credmap/wiki
I can add more info there, but currently it has a short description and example for each possible tag.

Didnt noticed it, thanks


Exception on RfcommDeviceService.FromIdAsync

On Win10 UWP I get an error on this line in ObdWrapper.cs
service = await RfcommDeviceService.FromIdAsync(device.Id)
device.id is "\\?\BTHENUM#{00001101-0000-1000-8000-00805f9b34fb}_LOCALMFG&0002#8&861dc08&0&001DA568988B_C00000000#{b142fc3e-fa4e-460b-8abc-072b628b3c70}"
Error is "A method was called at an unexpected time. (Exception from HRESULT: 0x8000000E)"
Any idea?

Did you debug into the app and see this?
Could you check

Bluetooth is enabled and the obd device is paired and connected?
You give the permission of accessing bluetooth devices to the app?

Thank you.

After some investigation I found that the problem is in the first run (app not installed) the RfcommDeviceService.FromIdAsync(device.Id) try to present a message in the UI thread that causes the error. Try to uninstall and rerun the code to repro.
Probably the method "RequestAccessAsync" must me called in the onNaviagateTo of the UI. I didn't found it (???) .... to test I have just moved some code in the MyDrivingUWP project.

Fix is checked in.


[GOBBLIN-984] Add log4j2.xml to enable log4j2 functionality

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[ ] My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-984

Description

[x] Here are some details about my PR, including screenshots (if applicable):

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason: script and log config changes

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

@Will-Lo , pls review.
pls also take a look at this, its also related to config changes: https://github.com/apache/incubator-gobblin/pull/2788
Thanks

Codecov Report

Merging #2830 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #2830      +/-   ##
============================================
+ Coverage     45.62%   45.63%   +<.01%
- Complexity     8971     8976       +5
============================================
  Files          1902     1902
  Lines         71284    71284
  Branches       7862     7862
============================================
+ Hits          32523    32529       +6
+ Misses        35771    35764       -7
- Partials       2990     2991       +1

Impacted Files
Coverage Δ
Complexity Δ

...lin/restli/throttling/ZookeeperLeaderElection.java
70% <0%> (-2.23%)
13% <0%> (ø)

.../org/apache/gobblin/cluster/GobblinTaskRunner.java
63.88% <0%> (-1.39%)
29% <0%> (-1%)

...main/java/org/apache/gobblin/util/HadoopUtils.java
30.87% <0%> (+0.67%)
25% <0%> (+1%)
:arrow_up:

...main/java/org/apache/gobblin/yarn/YarnService.java
15.68% <0%> (+0.84%)
4% <0%> (+1%)
:arrow_up:

...e/gobblin/runtime/locks/ZookeeperBasedJobLock.java
64.44% <0%> (+1.11%)
16% <0%> (+1%)
:arrow_up:

...in/java/org/apache/gobblin/cluster/HelixUtils.java
35.51% <0%> (+2.8%)
12% <0%> (+1%)
:arrow_up:

...lin/util/filesystem/FileSystemInstrumentation.java
92.85% <0%> (+7.14%)
4% <0%> (+1%)
:arrow_up:

...a/org/apache/gobblin/util/limiter/NoopLimiter.java
60% <0%> (+20%)
3% <0%> (+1%)
:arrow_up:

Continue to review full report at Codecov.

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

So far LGTM, going to test it out first after #2788 is good to go

This needs #2685 back in to support the base log4j2 functionality.


Compatibility with Home Assitant

Would be very cool if it would be compatible with Home assistant and if it can control any button or nob allready set in Home assistant so it could just add AV fonctionnality to my home automation I allready have set :)
very cool project by the way
will try this as soon as I can

wow I didint realize it was allready like this ... amazing


History produced by test environment should be compliant with tctl history format

JavaSDK mostly migrated replaying logic and helpers onto tctl history format: https://github.com/temporalio/sdk-java/issues/300
But in case of a test fail, the history that gets generated is not compliant with tctl format.
The test environment should produce histories that can be used in the replayer.

tctl format is not really human-readable because of the way protobuf JsonFormat handles ByteString format by converting it to Base64. See https://github.com/protocolbuffers/protobuf/issues/2801#issuecomment-285812695
So we have to stick to using TextFormat for human consumption printing which is not tctl compatible.


issue when filtering empty reads

Hi,
The most recent batch of RNA-seq data that I've received back has a small number of completely empty reads (which could potentially be the result of some over-clustering since I've never seen them before).  These reads are giving me problems in some downstream analysis steps.  I thought that your program would be a good solution for removing these and I gave it at try.  Here's an example with 4 reads:
@NS500422:705:HWFKTBGX5:1:11101:15654:1151 1:N:0:GATCTATC+AGCCTCAT
GGGTTATGTAGGAGTCAAATGAGAGGTCCTTGAAGTCT
+
AAAAAAEEEEEEEEEEEEEEEEEEEEEE/EEEE/EEE6
@NS500422:705:HWFKTBGX5:1:11101:18801:1152 1:N:0:GATCTATC+AGCCTCAT

+

@NS500422:705:HWFKTBGX5:1:11101:10924:1154 1:N:0:GATCTATC+AGCCTCAT
GCCCATCCAGGTGCTTGCAGGCTGAAAAGACCACGTGT
+
AAAAAEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE
@NS500422:705:HWFKTBGX5:1:11101:22690:1084 1:N:0:GATCTATC+AGCCTCAT
CCAGCNCATAACAGCAATGTAAGGCATGTTCACCCTG
+
AAAAA#EEEAAEEEEEEEEEEEEEEEEEEEEEEEEEE

If you create a fastq file with this and run:
./fastp -A -Q -i empty_example.fq -o length_filtered.fq
You wind up with the following outfile:
@NS500422:705:HWFKTBGX5:1:11101:15654:1151 1:N:0:GATCTATC+AGCCTCAT
GGGTTATGTAGGAGTCAAATGAGAGGTCCTTGAAGTCT
+
AAAAAAEEEEEEEEEEEEEEEEEEEEEE/EEEE/EEE6
+
AAAAAEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE
@NS500422:705:HWFKTBGX5:1:11101:22690:1084 1:N:0:GATCTATC+AGCCTCAT
CCAGCNCATAACAGCAATGTAAGGCATGTTCACCCTG

My reads are paired-end (one empty read paired to a read with data) and running them in paired-end mode produced the same output as the above example with the single-end data above.  The program removes the empty read and the next two lines (header and sequence data for the read below), then it looks like it counts line 3 and 4 of that read as lines 1 and 2 going forward, so we end up with only the first two lines of the final read in the example (no "+" and no quality scores).
I'm not sure how common these empty reads are given that this is the first time I've encountered them, but for me, the simplest solution has been to run the following line of code to replace the empty lines with a single N, and then either run your program (which works normally) or go straight to the downstream analysis step.
sed 's/^$/N/' empty_example.fq > empty_example_with_Ns.fq

I just added a change to skip the reads without a valid name, which should start with a @


T01-T02: Update project config (Gradle/SDK) to 2018 standards

Neither exercise nor solution code compiles with default settings in Android Studio 3.2.1.
This PR updates all projects from T01 and T02 to use 2018 defaults for Gradle and SDK.

LMK if this is useful, and I'll update all other projects in this repo. Will keep for my own use otherwise.
Thank you for the course!

Fixed.
We appreciate the help but our repo is set-up in a non-conventional way so pull requests are hard to integrate.
In the future, I would recommend creating an issue instead.

Thanks for fixing it! And will do.


wormhole integration

is integration with wormhole planned and when ?

Why matterlabs is blocked me say matterlabs to unblock me any kind hearted person


CLIENTS: Send Audio Transcription

Closes #212

@Catalin-Andronie post a screenshot of this client running please

@Catalin-Andronie post a screenshot of this client running please

@hassanhabib Unfortunately this will not work as expected because of the next RESTFulSense feature requests:

https://github.com/hassanhabib/RESTFulSense/issues/132
https://github.com/hassanhabib/RESTFulSense/issues/130

Without https://github.com/hassanhabib/RESTFulSense/issues/132 implemented we are forced to mark all AudioTranscriptionRequest properties as string. E.g: Temperature will become a string type instead of a double as it should be.

public class AudioTranscriptionRequest
{
-    public double Temperature { get; set; } = 0.2;
+    public string Temperature { get; set; } = "0.2";
}

Without https://github.com/hassanhabib/RESTFulSense/issues/130 implemented we are forced to set all the AudioTranscriptionRequest properties with some value even if some of them are optional. For the creation of a translation, OpenAI requires only the file and model to be present in the request body and the rest of the options are optional, and if we do so we are getting an exception for the other properties since they are null or have empty values.

var inputAudioTranscription = new AudioTranscription
{
    Request = new AudioTranscriptionRequest
    {
        Content = fileContent,
        FileName = fileName,
        Model = "whisper-1",
-       Prompt = null, // This is an optional value and I should not be forced to set its value.
+       Prompt = "Some prompt...",
-       Language = "", // This will throw an exception since RESTFulSense doesn't accept empty values.
+       Language = "en"
    }
};

AudioTranscription responseAudioTranscription =
    await this.openAIClient.AudioTranscriptions.SendAudioTranscriptionAsync(
        inputAudioTranscription);

@hassanhabib what's your suggestion?

Reading the API the file in the request is a string. The file should be previously uploaded using the name (string) for this. RESTFulSense already supports this using the PostContentAsync method. If you look at the example on the API page they are only posting the name of the file "german.m4a".  Sorry for the late response been quite ill for the last 4 days.

Reading the API the file in the request is a string. The file should be previously uploaded using the name (string) for this.

The API only accepts multipart/form-data content-type, which means we cannot use PostContentAsync since that uses "json" content-type (See example request).
curl https://api.openai.com/v1/audio/transcriptions \
  -H "Authorization: Bearer $OPENAI_API_KEY" \
  -H "Content-Type: multipart/form-data" \
  -F<EMAIL_ADDRESS>\
  -F model="whisper-1"

RESTFulSense already supports this using the PostContentAsync method. If you look at the example on the API page they are only posting the name of the file "german.m4a". Sorry for the late response been quite ill for the last 4 days.

Actually, the API specifies to post the file itself as a stream of bytes, the example only illustrates what it should be there. Also, besides the file and model the API accepts other properties in the request body like temperature, language, and prompt (the latter are optional). This is the full model that can be posted:
Currently, we are using PostFormAsync in order to send the file stream to the server in order to obtain its transcription, which works like a charm. Even so, we have two issues/features which need to be implemented before moving forward and completing the Audio Transcription. Please read this comment to understand the RESTFulSense features.


Monday 13-05-2024 roll call

Roll Call!
Leave a comment with these two things:

A summary of your study using only emojis
Something you'd like to share, anything goes! (within respect)

emoji cheat sheet

Good morning!

Bien le bonjour !

salut

Morning

gud morning...

Hello

good morning

Good Morning !

Good Morning!

hi

hello

Gm

✌

hi

hi

Good morning


Combobox doesn't fire input event when an item is selected

Here's a fiddle. Basically the DOM event input (see MDN) isn't fired on the <input> element when an option is picked from the combo box. This breaks some MV* frameworks that use the input event to trigger a scope update, for example VueJS.

@TMiguelT can you listen for the change event.  Here's a working example of what I think you're trying to do?  The event is triggered in both cases where the user input text manually or choses an item from the menu.