LXD v2.9.3 won't properly initialize existing ZFS datapool

Hi,
seems like the latest LXD v2.9.3 on stock 16.04.2 won't properly initialize ZFS datapool. When doing lxd init and using existing ZFS datapool, we always get this error:
Would you like to create a new network bridge (yes/no) [default=yes]? no error: Failed to create ZFS filesystem: mount: mount(2) failed: No such file or directory cannot mount 'testpool/lxd/containers': No such device or address filesystem successfully created, but not mounted
I have workarounded this by manually creating zfs sub-datasets under the testpool/lxd dataset like this (before lxd init):
for i in deleted containers custom images; do zfs create testpool/lxd/$i -o mountpoint=/var/lib/lxd/$i; done
Afterwards when I run lxd init and use existing testpool/lxd dataset, this time it will initialize correctly and is ready to run and launching containers seems to work at the moment.
How can I help you fix this? Many thanks!

I have probably forgot to mention it, but that dedicated datapool is for LXD only and is empty when doing zfs init.
Do you have any clue what could be causing this? This doesn't happen using v2.8 ...
Thanks!

Hm, can't really reproduce this problem locally. Can you show me the output of zfs list -t all?

Also, are you using an existing dataset as pool (e.g. tank/vol1) or a whole existing pool (e.g. tank)?

This is lxd init using an existing zpool pool2:

This is lxd init using an existing dataset pool2/vol2:

It's sub-dataset under a parent dataset testpool, which is both shared between Docker (it has testpool/docker dataset) and LXD on the same machine. No problems at all on v2.8, Docker and LXD perfectly coexisted there until upgrade to v2.9.3, so there must be some change causing this. On v2.8, either using dataset testpool or testpool/lxd it works just fine.

root@finaltest-ubuntu:~# zfs list -t all
NAME                                                                                USED  AVAIL  REFER  MOUNTPOINT
testpool                                                                                8.38G  11.8G    40K  /testpool
testpool/docker                                                                                374M  11.8G  12.0M  /var/lib/docker
testpool/docker/0b54701688f28d024776d5fdfb58aecca7c1c2560e7b119c9522d0a46bf2304c                        137M  11.8G   136M  legacy
testpool/docker/0b54701688f28d024776d5fdfb58aecca7c1c2560e7b119c9522d0a46bf2304c@230988306             1.29M      -   136M  -
testpool/docker/1969eafc5da5a9348407856a7d068045f01f5bbab142ba7f6f721b606b9fd50a                       45.4M  11.8G   179M  legacy
testpool/docker/1969eafc5da5a9348407856a7d068045f01f5bbab142ba7f6f721b606b9fd50a@439515542              166K      -   179M  -
testpool/docker/24ba85380f4953abf48478842b6995aa1c16a70cf26b124670812a79f771f1ef                        552K  11.8G   218M  legacy
testpool/docker/24ba85380f4953abf48478842b6995aa1c16a70cf26b124670812a79f771f1ef@651193083               31K      -   218M  -
testpool/docker/26d43c2e3d0bb785bd867b5bb599d8b6dfbc0432b7e74e311115d962a026bffe                         31K  11.8G   348M  legacy
testpool/docker/30d03c384b6f3d30ab68959a040f8efa2710fbcd2801d69dc2e9229b96493ef0                       31.5K  1024M  4.29M  legacy
testpool/docker/30d03c384b6f3d30ab68959a040f8efa2710fbcd2801d69dc2e9229b96493ef0-init                    28K  1024M  4.29M  legacy
testpool/docker/30d03c384b6f3d30ab68959a040f8efa2710fbcd2801d69dc2e9229b96493ef0-init@473599918            0      -  4.29M  -
testpool/docker/4c9a44e236867b5d9b8699e671fdccc53605e91bbb25d8c12d8d92136d391240                         82K  11.8G   220M  legacy
testpool/docker/4c9a44e236867b5d9b8699e671fdccc53605e91bbb25d8c12d8d92136d391240@822378919               26K      -   220M  -
testpool/docker/5397c3c90f62ed4154b04e350afcf1a5af4da24c4811a76e0319cc274db53e45                       2.70M  11.8G   220M  legacy
testpool/docker/5397c3c90f62ed4154b04e350afcf1a5af4da24c4811a76e0319cc274db53e45@321227897               31K      -   220M  -
testpool/docker/63631ea5a6a2c6368c6e5e2417e487e160bc69ebebfb25c1c3a875eeb333417d                       39.1M  11.8G   218M  legacy
testpool/docker/63631ea5a6a2c6368c6e5e2417e487e160bc69ebebfb25c1c3a875eeb333417d@124367543              588K      -   218M  -
testpool/docker/af66826a8aa157ebc27d637d801da28261f7df7f3822a235567e75da4ccab82a                       4.29M  11.8G  4.29M  legacy
testpool/docker/af66826a8aa157ebc27d637d801da28261f7df7f3822a235567e75da4ccab82a@814462152                 0      -  4.29M  -
testpool/docker/ce6dcf0ec1841c851fdd19dcda5d2cbcc748e8cb57f56fb8b1ff6e4193b994d6                        132M  11.8G   348M  legacy
testpool/docker/ce6dcf0ec1841c851fdd19dcda5d2cbcc748e8cb57f56fb8b1ff6e4193b994d6@926339297             3.05M      -   348M  -
testpool/docker/d307b457bc53fbdfe59cedfe550f3f1015994924c41f1b81e19ed4f9eb361392                        101K  11.8G   348M  legacy
testpool/docker/d307b457bc53fbdfe59cedfe550f3f1015994924c41f1b81e19ed4f9eb361392@192348497               27K      -   348M  -
testpool/docker/e436b176a2c580a891ca6515b83334a0c6bea6e99bf50970f369e46892613987                        178K  11.8G   180M  legacy
testpool/docker/e436b176a2c580a891ca6515b83334a0c6bea6e99bf50970f369e46892613987@218086432               32K      -   180M  -
testpool/docker/e734fc4636e687ac547847397bbfbe9dd4d0abd083435b8a15a5a5d7a7317d74                        556K  11.8G   180M  legacy
testpool/docker/e734fc4636e687ac547847397bbfbe9dd4d0abd083435b8a15a5a5d7a7317d74@749050931               31K      -   180M  -
testpool/lxd                                                                                7.03G  11.8G    19K  /testpool/lxd
testpool/lxd/containers                                                                                213M  11.8G    19K  none
testpool/lxd/containers/a15495cb2ed229d6                                                                609K  1023M  8.04M  /var/lib/lxd/storage-pools/default/containers/a15495cb2ed229d6
testpool/lxd/containers/b456c7f862346192                                                               34.6M   989M  1.23G  /var/lib/lxd/storage-pools/default/containers/b456c7f862346192
testpool/lxd/containers/bbb47409882fbae6                                                               1.86M  1022M   374M  /var/lib/lxd/storage-pools/default/containers/bbb47409882fbae6
testpool/lxd/containers/bc8371bf00eb8084                                                               15.7M  1008M   306M  /var/lib/lxd/storage-pools/default/containers/bc8371bf00eb8084
testpool/lxd/containers/cee537a69183dd13                                                               8.27M  1016M   418M  /var/lib/lxd/storage-pools/default/containers/cee537a69183dd13
testpool/lxd/containers/cf9195bd92ca12a7                                                               16.6M  1007M   457M  /var/lib/lxd/storage-pools/default/containers/cf9195bd92ca12a7
testpool/lxd/containers/d8196b861e3ce0ef                                                               8.23M  1016M   673M  /var/lib/lxd/storage-pools/default/containers/d8196b861e3ce0ef
testpool/lxd/containers/e2dc402853874e8b                                                                610K  1023M  8.04M  /var/lib/lxd/storage-pools/default/containers/e2dc402853874e8b
testpool/lxd/containers/e4c5a8a7b5aeb0f5                                                               12.1M  1012M   252M  /var/lib/lxd/storage-pools/default/containers/e4c5a8a7b5aeb0f5
testpool/lxd/containers/f84bcd0fd691403c                                                               1.80M  1022M   390M  /var/lib/lxd/storage-pools/default/containers/f84bcd0fd691403c
testpool/lxd/containers/f9337c7b26e44a0d                                                                112M   912M   613M  /var/lib/lxd/storage-pools/default/containers/f9337c7b26e44a0d
testpool/lxd/custom                                                                                19K  11.8G    19K  none
testpool/lxd/deleted                                                                                2.32G  11.8G    19K  none
testpool/lxd/deleted/images                                                                            2.32G  11.8G    19K  none
testpool/lxd/deleted/images/3afd8ae3e68a1af8bdcc67b719533095e1fda4c48437d393985422f069b13484            390M  11.8G   390M  none
testpool/lxd/deleted/images/3afd8ae3e68a1af8bdcc67b719533095e1fda4c48437d393985422f069b13484@readonly      0      -   390M  -
testpool/lxd/deleted/images/44f04a0afed786a88d2a3c4f9a545850237be527ceecf7fd8ed5f163b35fbbd1            373M  11.8G   373M  none
testpool/lxd/deleted/images/44f04a0afed786a88d2a3c4f9a545850237be527ceecf7fd8ed5f163b35fbbd1@readonly      0      -   373M  -
testpool/lxd/deleted/images/559f47f1d5dcf50f6d398d77c100a89077837459deb388f341d3f1464da5350e            420M  11.8G   420M  none
testpool/lxd/deleted/images/559f47f1d5dcf50f6d398d77c100a89077837459deb388f341d3f1464da5350e@readonly      0      -   420M  -
testpool/lxd/deleted/images/967740d48b4bf5abac83394850fe9e49b6559463c909908184f2620e8f478687            442M  11.8G   442M  none
testpool/lxd/deleted/images/967740d48b4bf5abac83394850fe9e49b6559463c909908184f2620e8f478687@readonly      0      -   442M  -
testpool/lxd/deleted/images/9cd6e728f7f8e530f1e20daca863f23b46f4324d1ac8c3a114e0bdaa10d38978            503M  11.8G   503M  none
testpool/lxd/deleted/images/9cd6e728f7f8e530f1e20daca863f23b46f4324d1ac8c3a114e0bdaa10d38978@readonly      0      -   503M  -
testpool/lxd/deleted/images/d056035475f1f876ca4ce227b0b55308770a07c21696db87271804f00424ca09            244M  11.8G   244M  none
testpool/lxd/deleted/images/d056035475f1f876ca4ce227b0b55308770a07c21696db87271804f00424ca09@readonly      0      -   244M  -
testpool/lxd/images                                                                                4.51G  11.8G    19K  none
testpool/lxd/images/3e4d9bea32dc885755d597ae6d2346ae59910062866b488c6b5291673138a9a7                    292M  11.8G   292M  none
testpool/lxd/images/3e4d9bea32dc885755d597ae6d2346ae59910062866b488c6b5291673138a9a7@readonly              0      -   292M  -
testpool/lxd/images/47defcd671d700576a3b9e93cd072b71a0e008b0aa38ad010ed21be76311a153                    442M  11.8G   442M  none
testpool/lxd/images/47defcd671d700576a3b9e93cd072b71a0e008b0aa38ad010ed21be76311a153@readonly              0      -   442M  -
testpool/lxd/images/6b47cb531e65ba5a182a5842bd18bff94d8f67f923ebc95006c7a8aadc203cdd                    675M  11.8G   675M  none
testpool/lxd/images/6b47cb531e65ba5a182a5842bd18bff94d8f67f923ebc95006c7a8aadc203cdd@readonly              0      -   675M  -
testpool/lxd/images/7445ff338e464f4a359dacef9264146b617df172be652202ec6fbbfb1aa6489b                   7.52M  11.8G  7.52M  none
testpool/lxd/images/7445ff338e464f4a359dacef9264146b617df172be652202ec6fbbfb1aa6489b@readonly              0      -  7.52M  -
testpool/lxd/images/749146bc245146f3d4639dd6a7303654dfc2a8c44f3120ae7a1697773eb3d7ba                   1.23G  11.8G  1.23G  none
testpool/lxd/images/749146bc245146f3d4639dd6a7303654dfc2a8c44f3120ae7a1697773eb3d7ba@readonly              0      -  1.23G  -
testpool/lxd/images/9ec561e79ead1a830381471b4504f325f948b5f752c8d2f5631c7857935d101d                    244M  11.8G   244M  none
testpool/lxd/images/9ec561e79ead1a830381471b4504f325f948b5f752c8d2f5631c7857935d101d@readonly              0      -   244M  -
testpool/lxd/images/c16dcf4e08e3d5740947dae8c5baf6acd3615e333743b0338b4889284b86916c                   7.62M  11.8G  7.62M  none
testpool/lxd/images/c16dcf4e08e3d5740947dae8c5baf6acd3615e333743b0338b4889284b86916c@readonly              0      -  7.62M  -
testpool/lxd/images/cd14831d8d6d7bed4960e77b21ca550e5d7b5c5f2f0fc4724ea2e4230fa80c83                    390M  11.8G   390M  none
testpool/lxd/images/cd14831d8d6d7bed4960e77b21ca550e5d7b5c5f2f0fc4724ea2e4230fa80c83@readonly              0      -   390M  -
testpool/lxd/images/e7e41e747d9d19bae6cfbec0fcdf04721d90bdcc8abcaa0cc9e7612fcd7be486                    373M  11.8G   373M  none
testpool/lxd/images/e7e41e747d9d19bae6cfbec0fcdf04721d90bdcc8abcaa0cc9e7612fcd7be486@readonly              0      -   373M  -
testpool/lxd/images/eccdd40cf2ca2c2311107ef4e19798da1ece96ac798a6561f28326fb6bb8860d                    420M  11.8G   420M  none
testpool/lxd/images/eccdd40cf2ca2c2311107ef4e19798da1ece96ac798a6561f28326fb6bb8860d@readonly              0      -   420M  -
testpool/lxd/images/fcdfa6b9f6a8bcf5d2eeae6725b6e99579b03dc6e239deab7bb6d9994849aabd                    503M  11.8G   503M  none
testpool/lxd/images/fcdfa6b9f6a8bcf5d2eeae6725b6e99579b03dc6e239deab7bb6d9994849aabd@readonly              0      -   503M  -
testpool/lxdvar                                                                                1001M  11.8G  1001M  /var/lib/lxd
testpool/snapshots                                                                                2.85M  11.8G  2.85M  /testpool/snapshots

Also, in the /var/lib/lxd/lxd.log there is roughly the same as I've posted in the first comment ...

Wait, previously you said

I have probably forgot to mention it, but that dedicated datapool is for LXD only and is empty when doing lxd init.

but then you showed a fully populated zfs dataset. So what exactly are you saying? Is the zfs dataset testpool/lxd empty by the time you run lxd init or not? :)

Aha, okay, we misunderstood a little bit ;) I've written in the first post of this issue that I've workarounded it by manually creating the sub-datasets needed for lxd with respective mountpoints. So actually before that workaround and lxd init (I've pasted after the workaround, sorry), the zfs dataset would be populated only by docker, but I don't see any problem there - this works perfectly fine under v2.8, no matter if the dataset is empty, or use by docker, etc.

Ah, thanks. Can you give me the exact commands you used to create the initial zpool and datasets that you have LXD use.

The error message you posted is weird, since testpool/lxd/containers should never have a mountpoint property set in the first place. So the fact that zfs is trying to mount it seems weird.
Can you also show me the output of:

lxc storage show <pool-name> (The name of your pool as LXD stores it in the db can be gathered from lxc storage list.)

Here you are, nothing strange here:

zpool create -f testpool /dev/vda1
zfs set compression=off testpool
zfs set dedup=off testpool
zfs set sync=disabled testpool
zfs set primarycache=none testpool
zfs create testpool/docker -o mountpoint=/var/lib/docker
zfs create testpool/lxdvar -o mountpoint=/var/lib/lxd
zfs create testpool/lxd

The is exactly the same as it's working on v2.8.

root@finaltest-ubuntu:~# lxc storage list
+---------+--------+---------------+---------+
|  NAME   | DRIVER |    SOURCE     | USED BY |
+---------+--------+---------------+---------+
| default | zfs    | testpool/lxd  | 22      |
+---------+--------+---------------+---------+

root@finaltest-ubuntu:~# lxc storage show default
config:
  source: testpool/lxd
  zfs.pool_name: testpool/lxd
name: default
driver: zfs
used_by:
- /1.0/containers/a15495cb2ed229d6
- /1.0/containers/b456c7f862346192
- /1.0/containers/bbb47409882fbae6
- /1.0/containers/bc8371bf00eb8084
- /1.0/containers/cee537a69183dd13
- /1.0/containers/cf9195bd92ca12a7
- /1.0/containers/d8196b861e3ce0ef
- /1.0/containers/e2dc402853874e8b
- /1.0/containers/e4c5a8a7b5aeb0f5
- /1.0/containers/f84bcd0fd691403c
- /1.0/containers/f9337c7b26e44a0d
- /1.0/images/3e4d9bea32dc885755d597ae6d2346ae59910062866b488c6b5291673138a9a7
- /1.0/images/47defcd671d700576a3b9e93cd072b71a0e008b0aa38ad010ed21be76311a153
- /1.0/images/6b47cb531e65ba5a182a5842bd18bff94d8f67f923ebc95006c7a8aadc203cdd
- /1.0/images/7445ff338e464f4a359dacef9264146b617df172be652202ec6fbbfb1aa6489b
- /1.0/images/749146bc245146f3d4639dd6a7303654dfc2a8c44f3120ae7a1697773eb3d7ba
- /1.0/images/9ec561e79ead1a830381471b4504f325f948b5f752c8d2f5631c7857935d101d
- /1.0/images/c16dcf4e08e3d5740947dae8c5baf6acd3615e333743b0338b4889284b86916c
- /1.0/images/cd14831d8d6d7bed4960e77b21ca550e5d7b5c5f2f0fc4724ea2e4230fa80c83
- /1.0/images/e7e41e747d9d19bae6cfbec0fcdf04721d90bdcc8abcaa0cc9e7612fcd7be486
- /1.0/images/eccdd40cf2ca2c2311107ef4e19798da1ece96ac798a6561f28326fb6bb8860d
- /1.0/images/fcdfa6b9f6a8bcf5d2eeae6725b6e99579b03dc6e239deab7bb6d9994849aabd

But this is after the workaround, so not sure if you need it.

I can't reproduce. Works totally fine here with the commands you gave me on all LXD 2.9.3 versions.

Thanks very much, I will try to strace and catch that strange error zfs message. Will report back then.

@audiocricket, just so that you know what exactly I did to reproduce this:

So one option I can think of is that you unmount the pool or dataset and then when LXD tries to remount the pool/dataset, the /var/lib/lxd directory is already populated due to the daemon start and so the pool/dataset will refuse the mount.

Any luck in getting this to work or are you still running into this issue?

Will most probably check this over weekend or past weekend.

Cool, no rush. I was just interested. :)

We can probably close this issue, since it's not happening anymore with latest LXD v2.11 and ZFSonLinux <IP_ADDRESS>. Will reopen/create new issue shall it happen again. Thanks!

Good to hear!


LCD OTA update broken

Something in the v0.2.0 release has broken LCD OTA updating, need to take a look at what's happening there.

Fixed with v0.2.1 release


New version 1.18.0 open and freezes on OSX sierra

Description
Just updated to the new version of Atom 1.18.0 and it freezes after it's initialization
Steps to Reproduce

open app

Expected behavior: [What you expect to happen]
open as usual with the elcome screen and stuff
Actual behavior: [What actually happens]
open as the image above
Reproduces how often: [What percentage of the time does it reproduce?]
if you initialize it straigh from a file it opens normally
Versions
it was ok in the 1.17.2, after the update to 1.18.0 it ahs this behaviour

Thanks for the report!  Can you confirm If disabling the github package gets you past the freeze?  If so, I think we can close this as a duplicate of https://github.com/atom/atom/issues/14806.

Oh also, it would be helpful if you can fill out the entire issue template for future issues - in particular, can you confirm if you see the same behavior in safe mode (atom --safe)?

Oh ok,
I've tried to make those teste but the issue is not repeating after I configured the atom-github package with the token and stuff, probably it have something to do with the atom-github ans its configs

I've tried to make those tests but the issue is not repeating after I configured the atom-github package with the token and stuff, probably it have something to do with the atom-github and its configs

Thanks for letting us know, that's interesting that logging in with a token in the GitHub panel made the problem go away.  I wasn't able to reproduce by starting Atom while not logged in through the GitHub tab but if you run into this issue again, feel free to open an issue in https://github.com/atom/github/issues :v:


Tabs stretch after enabling close-on-left

With the "One Dark" theme enabled (current default), tabs stretch to fill up the entire tab bar after installing this package. The X button is also positioned further from the left edge of the tab than how far it was from right edge of the tab before installing this package

Hi, I’m sorry for the late response to this!
This package was created to replicate the tab style of built-in OS X applications, which have full-width tabs with left-aligned close buttons. The name "close-on-left" insufficiently describes this, but I’m not sure whether the best solution is to 1. rename this package, 2. split this into two packages, or 3. note this idiosyncrasy in the README. Any recommendations?
More context is included in the discussion for this PR.

Hi,
Thanks for the reply! The name of the package was definitely the issue for me then. I may or may not have even read the README at the time, I simply assumed based on the name that the only thing it does is switch the close button to the left side.
I do personally think there should be a package that only does that, and maybe another package that either 1) does this and adjusts the tab with or 2) only adjusts the width (thus the two packages could be installed together to achieve the desired behavior) for those looking for the MacOS like behavior.
Thanks for creating this package, though! I might just use your css as a reference and add the behavior I'm looking for as a customization in my own Atom stylesheet.


Foyer modifications for "custom" forcefields

Modify Foyer to accept a specific itp file and specific rules.py file (also make it so you can easily define rules in a notebook and pass them to foyer).

Moved: https://github.com/iModels/foyer/issues/31


Undo/Redo should never leave text selected.

As titled. This is a very common mistake by vim emulator implementors.

Thanks for the report.
They call VSCode original functions yet, so they don't same works as VIM.
I have a plan to develop them, but it is still way off.


ERROR: for bigchaindb_bigchaindb_1  Cannot start service bigchaindb: OCI runtime create failed:

I was trying to start bigchaindb and this error occured when I did make run.
The whole error message is here
INFO:bigchaindb.config_utils:Cannot find config file `/root/.bigchaindb`.
Generating default configuration for backend localmongodb
Configuration written to /root/.bigchaindb
Ready to go!
Removing intermediate container 9d4aa0c6934e
 ---> 9a83ebfbb983
Successfully built 9a83ebfbb983
Successfully tagged bigchaindb_bigchaindb:latest
WARNING: Image for service bigchaindb was built because it did not already exist. To rebuild this image you must use `docker-compose build` or `docker-compose up --build`.
Creating bigchaindb_tendermint_1 ... done
Creating bigchaindb_mongodb_1    ... done
Creating bigchaindb_bigchaindb_1 ... error

ERROR: for bigchaindb_bigchaindb_1  Cannot start service bigchaindb: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:402: container init caused \"rootfs_linux.go:58: mounting \\\"/mnt/c/Users/akino/Downloads/bigchaindb/tox.ini\\\" to rootfs \\\"/var/lib/docker/overlay2/9f3f5f3b08ce22bcc62bb48eb3f7e86b687348749101c16c37266ac5cb6066a0/merged\\\" at \\\"/var/lib/docker/overlay2/9f3f5f3b08ce22bcc62bb48eb3f7e86b687348749101c16c37266ac5cb6066a0/merged/usr/src/app/tox.ini\\\" caused \\\"not a directory\\\"\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

ERROR: for bigchaindb  Cannot start service bigchaindb: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:402: container init caused \"rootfs_linux.go:58: mounting \\\"/mnt/c/Users/akino/Downloads/bigchaindb/tox.ini\\\" to rootfs \\\"/var/lib/docker/overlay2/9f3f5f3b08ce22bcc62bb48eb3f7e86b687348749101c16c37266ac5cb6066a0/merged\\\" at \\\"/var/lib/docker/overlay2/9f3f5f3b08ce22bcc62bb48eb3f7e86b687348749101c16c37266ac5cb6066a0/merged/usr/src/app/tox.ini\\\" caused \\\"not a directory\\\"\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
ERROR: Encountered errors while bringing up the project.
Makefile:59: recipe for target 'run' failed
make: *** [run] Error 1

I'm using WSL which is connected to Docker on Windows.
How can I fix this error?

If I had to guess, I'd guess the problem is WSL, Docker on Windows, or their combination. We generally run everything on actual Linux machines or VMs.

@spider-hand can you retry with the latest master? There were some problems with docker-compose.yml that should be fixed now.

Hi, still the same error happens.

This is an old issue, on an unsupported operating system, so I'm closing it.

Please tell me how can a Linux VM user run bigchaindb?

@KevinBaylor Please read the docs, e.g. http://docs.bigchaindb.com/projects/server/en/latest/simple-deployment-template/index.html


Bug in v0.7.0 - please tag with fix

What happened?
There is a bug in release v0.7.0
Did you expect to see some different?
Service names for controller-manager, scheduler and dns are same.
How to reproduce it (as minimally and precisely as possible):
Use v0.7.0 to create manifests for kube-prometheus/kube-prometheus-kops.libsonnet
Environment

Kubernetes version information:
1.19.7

Kubernetes cluster kind:
Kops

Anything else we need to know?:
Following is the issue.
{
  prometheus+:: {
    kubeControllerManagerPrometheusDiscoveryService: service(
      'kube-controller-manager-prometheus-discovery',
      'kube-system',
      { 'k8s-app': 'kube-controller-manager' },
      { 'k8s-app': 'kube-controller-manager' },
      [{ name: 'https-metrics', port: 10257, targetPort: 10257 }]
    ),
    kubeSchedulerPrometheusDiscoveryService: service(
      'kube-controller-manager-prometheus-discovery',
      'kube-system',
      { 'k8s-app': 'kube-scheduler' },
      { 'k8s-app': 'kube-scheduler' },
      [{ name: 'https-metrics', port: 10259, targetPort: 10259 }]
    ),
    kubeDnsPrometheusDiscoveryService: service(
      'kube-controller-manager-prometheus-discovery',
      'kube-system',
      { 'k8s-app': 'kube-dns' },
      { 'k8s-app': 'kube-dns' },
      [{ name: 'metrics', port: 10055, targetPort: 10055 }, { name: 'http-metrics-dnsmasq', port: 10054, targetPort: 10054 }]
    ),
  },
}

I suggest using release-0.7 branch.

@prometheus-operator/kube-prometheus-reviewers why do we even tag and do releases when in docs we suggest using branches and not tags? This seems confusing and IMHO we should either stop tagging or use patch versions every time we update release-* branch. WDYT?


[QUESTION]Client-ID

Write your question
Im getting an error in my console.
TypeError [ERR_HTTP_INVALID_HEADER_VALUE]: Invalid value "undefined" for header "Client-ID"
    at ClientRequest.setHeader (node:_http_outgoing:576:3)
    at new ClientRequest (node:_http_client:256:14)
    at Object.request (node:https:353:10)
    at C:\Users\skullgaming31\Desktop\SkulledBot\node_modules\tesjs\lib\utils.js:16:31
    at new Promise (<anonymous>)
    at request (C:\Users\skullgaming31\Desktop\SkulledBot\node_modules\tesjs\lib\utils.js:10:16)
    at C:\Users\skullgaming31\Desktop\SkulledBot\node_modules\tesjs\lib\tes.js:144:17
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  code: 'ERR_HTTP_INVALID_HEADER_VALUE'
}

im not sure if its something i havnt set up up but im not using Client-ID anywhere in my code
Additional context
TESjs Current Version: v0.5.1

Hi!  The Client-ID is the id property you set when initializing TES:
const tes = new TES({
    identity: {
        id: YOUR_CLIENT_ID, <-- your client id goes here
        secret: YOUR_CLIENT_SECRET
    },
    listener: {
        baseURL: "https://example.com",
        secret: WEBHOOKS_SECRET,
    }
});

The error message you gave indicates that you did not include that in your TES config object (which TES should probably catch so this sort of thing doesn't happen now that I think about it).
If you do not have a client id for your project, you'll need to go create an application here and you'll receive one.
For more info on the TES configuration, you can take a look at the docs here which also outlines which properties are required and what types they should be, etc.
Hopefully this helps!


A GUI extension / toolbar app for quick access

This can be done in python, a small extension will do the job to execute the commands in the background when buttons are pressed representing those tasks supported by the script.

Not Interested as I don't use linux anymore.


Do not associate claim information with files

When calling API command file_list , various claim information is attached onto the file from the wallet
see Daemon._get_lbry_file_dict() : https://github.com/lbryio/lbry/blob/master/lbrynet/daemon/Daemon.py#L863
and ManagedEncryptedFileDownloader.load_file_attributes()
https://github.com/lbryio/lbry/blob/master/lbrynet/file_manager/EncryptedFileDownloader.py#L111
This is wrong, because the claim information at the time of download can be completely different from the claim information at the time of checking the claim information. Resulting in confusion and bugs when claims get updated and abandoned. Further more, files can and do exist without having any claim information attached to them at all (for example , files that have been uploaded to reflector. Calling file_list on reflector takes forever because it has to fetch all the claim information from lbryum-server since it doesn't have the information in the wallet cache).
This has resulted in numerous bugs in the app side and daemon side, when claims get abandoned and updated ( see:  https://github.com/lbryio/lbry/issues/944, https://github.com/lbryio/lbry-app/issues/694 )
We need to completely remove claim information from the file_list and also file_delete API command. Below is the exact API change that will happen:
Individual files in the output of API command file_list will no longer contain fields "name", "outpoint", "claim_id", "metadata", "channel_name", "has_signature", "signature_is_valid"
"claim_id", "outpoint", "name" is no longer a valid argument to search for files for API command file_list, file_delete, and file_reflect

:+1: from me. This will be relatively trivial to adjust app-side.

merged here https://github.com/lbryio/lbry/commit/188822ef201d38b511472d01a1a7e370029e070a


Adjust coverage

Codecov Report

Merging #141 (bed7206) into stable/v8.x (11d0e97) will decrease coverage by 0.21%.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@               Coverage Diff               @@
##           stable/v8.x     #141      +/-   ##
===============================================
- Coverage        57.27%   57.06%   -0.21%
===============================================
  Files              121      121
  Lines            10583    10587       +4
  Branches          1037     1038       +1
===============================================
- Hits              6061     6042      -19
- Misses            4187     4209      +22
- Partials           335      336       +1

see 8 files with indirect coverage changes


shortening breaks when html is copied/pasted from an area that has been shortened already

thanks for this plugin. i have been using it on my site for a while and generally it is fine. i just found a problem though, that i have no idea of the cause of. someone posted a comment to my site that was partially freshly typed text and partially pasted text from another comment she had written. the shorten code correctly shortened the text, but when i click the 'expand' link, the full text is not revealed. the animation is triggered, but there is no more text to read...
edit: i have debugged this a bit now and found that the cause of the problem includes that the text that was pasted into the comment that i am applying the shortening function to... contains a class that had been previously added by the shorten function when it was applied to the source comment.
in other words, the text that the shorten function is being run against already contains an html 'class' definition called 'allcontent' because the user copied and pasted text from an area that already had been shortened previously on the page...
i changed the line:
$this.find(".allcontent").hide(); // Hide all text

to
$this.find(".allcontent:first-of-type").hide(); // Hide all text

to see if that might improve the situation but it didn't provide a quick workaround and instead some of the text was duplicated on the page.

i have fixed this on my site now by filtering out the class 'allcontent' from all html before it reaches the browser.


Slow rendering of feeds containing iframes

I've noticed, that it takes about 1 second to render an article from Slashdot. Is this because they using iframes?
Feed URL: http://rss.slashdot.org/Slashdot/slashdotMain?format=usm
Note, if you already read that article, it will render fast, only iframe will take loading, but when reading it for the first time, in pool of other unread articles it will be slower to render.

Yes — that iframe takes extra time to load.

We’re using Apple’s WebKit for that view. We don’t have a way of affecting how quickly it renders, unfortunately. (Well, we could just strip out the iframe, but that’s probably not what you want.)

Well, we could just strip out the iframe, but that’s probably not what you want

It's actually what I want, but was afraid to ask.
But the problem is not that iframe renders after the view loaded. For some reason on multiple different systems (iMac5k, iMac Pro, 2012 MacBook pro) these articles take about 1s to load the article view.

This no longer appears to be an issue. If it still is an issue, we can re-open this ticket.


BTE did not find a subset of DMDB edges

There are 16 edges of  DMDB  could not be found from SemMedDB APIs after validations with the latest copy of SemMedDB. After doing some studies, I found below issues/actions have to be addressed:

Review and update data in SemMed-related APIs
BTE did not (trigger to) find any edges for Drug (ChemicalSubstance in Biolink v.1.1)
Inconsistent (missing) mappings in the registry and API codes

Full Report

Let me add a bit more context.  Sander's work on #181 revealed a few things we will want to do with the semmed APIs.  I asked him to create this ticket to start discussions on prioritizations

the Semmed APIs appear to be based on the 2020 data files -- would be good to update them to the latest 2021 files (related to https://github.com/biothings/pending.api/issues/25)
we need to update the APIs to Biolink 2.0.2 (related to https://github.com/biothings/BioThings_Explorer_TRAPI/issues/207)
Right now, the mappings to Biolink Model happen in the parsers (see, for example, https://github.com/kevinxin90/semmedphen/blob/master/parser.py). We should consider whether it's possible for the APIs to more closely reflect the original source files, and then do the mappings to Biolink Model in the Smart API mapping files.

Let's discuss more at an upcoming internal Translator meeting...

Is this issue still relevant/should it be added to the project tracker?

I think with the child issues that were created and resolved, this issue can be closed.

I agree, looks like it was related to the big push to update semmeddb https://github.com/biothings/pending.api/issues/30#issuecomment-910768268


##[error]Could not find the modules: 'Az.Accounts' with Version: '5.5.0'. If the module was recently installed, retry after restarting the Azure Pipelines task agent

Description
After the Build Agents for vmImage: windows-latest, were moved to Windows 2022, we get the following error on every task that uses Az.Accounts
##[error]Could not find the modules: 'Az.Accounts' with Version: '5.5.0'. If the module was recently installed, retry after restarting the Azure Pipelines task agent
Virtual environments affected

[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11
[ ] Windows Server 2016
[ ] Windows Server 2019
[X] Windows Server 2022

Image version and build link
We are not allowed to share this data publically, as we are a European Financial institution.
Is it regression?
no it' s a new issue
Expected behavior
Az.Accounts 5.5.0 will be loaded without errors
Actual behavior
Build Agent throws an error
##[error]Could not find the modules: 'Az.Accounts' with Version: '5.5.0'. If the module was recently installed, retry after restarting the Azure Pipelines task agent
Repro steps
Create a task that uses 5.5.0 for Az.Accounts and run it.

Hello @rdoetjes,
We don't preinstall Az.Account=5.5.0 on Windows Server 2022, you can check the doc file - https://github.com/actions/virtual-environments/blob/main/images/win/Windows2022-Readme.md#powershell-tools

@rdoetjes, Any updates?

Hi Alexander,
We have not yet reached the people who create our resource templates, to check what they are using.
Big corporations make these sorts of things always hard :)
Sent from my iPhone

On 4 Apr 2022, at 09:38, Aleksandr Chebotov @.***> wrote:

@rdoetjes, Any updates?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

Feel free to open the issue if you get a chance to collect more info how to reproduce it.


Added My Solution

Added 2-line solution of FizzBuzz. Although it was possible to put it into one-line, but was looking messy.
Thanking You

neat, thanks!


escape filenames when building commands

Resolves issue #10

I remember seeing other places in the repo where shell escapes would be a good plan, though I don't recall where they all were.  If I'm not misremembering these, it might be a good plan to escape those while you're at it...


Add endpoint for getting post

Added in https://github.com/duckduck-team/quackit-api/commit/06b678f5bffd53cfb86f4686cd68a8470776e097


Is there any python demo?

Hallo, thanks for you awesome work. I found the FEARDemo here only provide swift version on iOS. Will you further provide a version of python? Or could you please give me some instruction to write an python demo? Thanks a lot!

@20XYSong thanks for mentioning, we've just added it today
https://github.com/PinataFarms/FEARTracker/pull/2

Thanks for your help！o(￣▽￣)ｄ


"Module could not be loaded" error

Hi Jan,
I'm facing an annoying "Module could not be loaded" error when running the benchmark according to the tutorial you described in the project's README.
Here is the stacktrace extracted from the<EMAIL_ADDRESS>file :
=ERROR REPORT==== 27-Sep-2012::19:30:19 ===
** State machine <0.95.0> terminating
** Last message in was {ssl,{sslsocket,5,<0.97.0>},
                            <<"HTTP/1.1 101 Switching Protocols\r\nUpgrade: websocket\r\nConnection: Upgrade\r\nSec-WebSocket-Accept: 13YSWplcdyC/rjZYDmr2CHpn3z4=\r\n\r\n">>}
** When State == wait_ack
**      Data  == {state_rcv,
                     {sslsocket,5,<0.97.0>},
                     {{0,0,0,0},0},
                     undefined,0,10000,"<IP_ADDRESS>",8080,ssl,
                     {proto_opts,negociate,10,600000,32768,32768,undefined,
                         undefined},
                     true,1,
                     {ts_request,parse,false,[],[],
                         {websocket_request,connect,"/ws",
                             "https://<IP_ADDRESS>/",<<>>},
                         false,undefined,undefined,undefined},
                     true,
                     {1348,767019,128147},
                     {1348,767019,120299},
                     10,11,false,
                     {1348,767019,128147},
                     {1348,767019,128147},
                     [],<<>>,
                     {websocket,initial,<<"13YSWplcdyC/rjZYDmr2CHpn3z4=">>,
                         undefined},
                     0,1,524288,524288,
                     {dyndata,
                         [{tsung_userid,"1"}],
                         {websocket_dyndata,undefined}},
                     ts_websocket,[],undefined,none}
** Reason for termination =
** {'module could not be loaded',
       [{binary,longest_common_suffix,
            [[<<"HTTP/1.1 101 Switching Protocols\r\nUpgrade: websocket\r\nConnection: Upgrade\r\nSec-WebSocket-Accept: 13YSWplcdyC/rjZYDmr2CHpn3z4=\r\n\r\n">>,
              <<"\r\n\r\n">>]]},
        {ts_websocket,extract_accept,1},
        {ts_websocket,parse,2},
        {ts_client,handle_data_msg,2},
        {ts_client,handle_info,3},
        {gen_fsm,handle_msg,7},
        {proc_lib,init_p_do_apply,3}]}

This trace appears each time tsung attempts to connect through WebSocket.
I use the latest tsung 1.4.2 on an Ubuntu 10.04 64-bit VM.
Any idea ?

Seven years later than you I encounter with the same problem :)  I'm using Tsung 1.7.0 and erlang 18.3

Hey, I'm going to take a look at this soon, thanks for reporting!

As mentioned in #6 Tsung 1.5.0 added native support for websocket connections, so you shouldn't need this extensions if you're using modern Tsung.


Show version mismatch in -driver-show-incremental

SR-2855 suggests -driver-show-incremental not only print information about why certain files are included in incremental compilation, but also print out why incremental compilation may be disabled altogether.
Add a message for one such reason: when the version of the Swift compiler being used to incrementally compile doesn't match the one used to compile previously.

This addresses one part of SR-2855.

@swift-ci please test and merge


Radial fog for clustered renderer

This pull request is for the issue #52707, however, it is for the "clustered renderer" back end only since I could not make the fog appear in the "forward mobile" back end by user means.
It is possibly a bug or there is a way to enable it that I don't know.
Bugsquad edit: Fixes #52707.

This pull request is for the issue #52707, however, it is for the "clustered renderer" back end only since I could not make the fog appear in the "forward mobile" back end by user means.
It is possibly a bug or there is a way to enable it that I don't know.

It sounds like a bug. Changes that affect core rendering should be made both in the clustered renderer and the mobile renderer.
Also, after testing, can you confirm that this change fixes the issue in #52707?

After this commit the fog behaves radially, which fixes the #52707.
Something that I did not consider is the Sky.glsl shader referred in the issue #52707. It uses scene_data.z_far to calculate the fog amount, which from my testing seems to be the viewport's frustum far distance, and affects the only background rendering. I am not sure if it should be that way and the fog cannot be computed radially with that information.
I will make the changes of the mobile renderer the same way I did for the clustered renderer.

As the person who opened #52707 I'd say it works just fine so I confirm it fixes the issue, but yeah Mobile renderer is currently in a broken state, Lights are also missing right now.

Looks good. Can you please squash your commits together?

Something that I did not consider is the Sky.glsl shader referred in the issue #52707. It uses scene_data.z_far to calculate the fog amount, which from my testing seems to be the viewport's frustum far distance, and affects the only background rendering. I am not sure if it should be that way and the fog cannot be computed radially with that information.

You don't need to make changes to the sky. Since it uses a constant fog amount it doesn't have the problem described in #52707

I spend more time with the squashing that I'd like to admit, at least i get to practice with source control, I hope is correct now. If not, let me know.

It looks like you added two more commits instead of squashing them. The docs have a very helpful explanation for how to squash commits here https://docs.godotengine.org/en/stable/community/contributing/pr_workflow.html#the-interactive-rebase

How about now? if the source controls is not in the right state I will consider doing another pull request.

Thanks!


[5.8] Fix replaceRouteParameters() for query-string parameters

I am working on a search-engine application. It has routes that use optional route-parameters in combination with query-string parameters.
One of my routes looks like this
Route::get('/{location?}', 'ProfileController@index')->name('profiles.index');

The URL-strings for search-results pages may look something like these:

http://homestead.local/London?age=30
http://homestead.local/?status[0]=single&status[1]=married

The last one searches for profiles in any location whose statuses are either 'single' or 'married'.
In my controller, I wanted to redirect to a route using given query-string parameters. For example, if I wanted to redirect to the 2nd example from above, I might have attempted something like this:
return redirect()->route('profiles.index', ['status' => ['single', 'married']]);

Doing so resulted in an "Array to string conversion" ErrorException.
I noticed replaceRouteParameters() in Illuminate/Routing/RouteUrlGenerator uses array_shift($parameters) to pull the first element from the $parameters array and put it in place of the optional location route parameter. This breaks when the first element is an array.
In the example above, the intention was not to use the location parameter at all. The given parameters were meant to be used as the query-string.
A workaround was to explicitly specify an empty location like this:
return redirect()->route('profiles.index', ['status' => ['single', 'married'], 'location' => '']);

In the pull-request I've made changes to replaceRouteParameters() such that it better accommodates query-string parameters.
It should work with combinations of query-string and route parameters. It assumes that any associative elements in $parameters that haven't already been filtered in replaceNamedParameters() are referring to query-string parameters and should not be used for route-parameter replacement.
I've used Arr::pull($parameters, 0) instead of array_shift($parameters) to pull the first non-associative element. Arr::pull does not reset the array keys, so I've used $parameters = array_merge($parameters) to reset the numeric keys before each replacement.
This is my first ever pull request on Github. Please excuse me if I did anything wrong.

I am closing this pull request because it lacks sufficient explanation, tests, or both. It is difficult for us to merge pull requests without these things because the change may introduce breaking changes to the framework.
Feel free to re-submit your change with a thorough explanation of the feature and tests - integration tests are preferred over unit tests. Please include it's benefit to end users; the reasons it does not break any existing features; how it makes building web applications easier, etc.
Thanks!


Added multipart/form-data encoding.

I have added the ability to specify a request be sent in the multipart/form-data encoding, as well as adding a file to be sent as part of the request.
A number of other adjustments were also made so this form of encoding could be used for other purposes.

The new FileParameter class takes a java.io.File which will be added as a part of the message body. This is an extension of the Parameter class.
Each parameter can now have a disposition as specified by RFC-2388.
It may be useful to add other attributes in the future such as content-type,  charset, content-transfer-encoding, etc.
Individual parameter types can now indicate whether or not they are to be included as part of the base string. This is to account for instances where parameters are identified separately from files at the server end.
An example of this is in PHP, where a single submission results in fields going to the $_POST array while uploads go the $_FILES array. This results in the signature expected by the server being different from that sent by the client.

It is showing that the entire file was modified, in the case of Parameter.java for example. This is due to the format command in eclipse.  Sorry for any confusion it may cause.

Hi guys, I'm curious to learn why this PR eventually was never merged.
And btw, I <3 Scribe!


Reddit subreddit subscribers badge

:clipboard: Description

Which service is this badge for e.g: GitHub, Travis CI

Reddit

What sort of information should this badge show?
Provide an example in plain text e.g: "version | v1.01" or as a static badge
(static badge generator can be found at https://shields.io)

Subreddit subscribers count badge like :

:link: Data

Is there a public API?

Here : https://www.reddit.com/r/Portapps/about.json (replace Portapps with another subreddit)

Does the API requires an API key?

Seems not required

Link to the API documentation.

https://www.reddit.com/dev/api/#GET_r_{subreddit}_about
:microphone: Motivation
Like Twitter badge, display subscribers count for a subreddit :)
I have already worked on previous badges, I can work on it if you want ;)

I have already worked on previous badges, I can work on it if you want ;)

Awesome!

Just adding a quick note that you can also create this badge with the dynamic-json badge:
https://img.shields.io/badge/dynamic/json.svg?label=r/Portapps%20subscribers&query=$.data.subscribers&url=https://www.reddit.com/r/Portapps/about.json

But i think this could be a good addition to add to shields.

Guys, today I'm starting with this issue. I have an initial question: should we allow the user to change the color o use the reddit's color? Thanks!

I don't know exactly how to do it, but I've created a new branch in my fork in order to show you my progress.
Am I doing the workflow correctly?
That's the last commit where I've just pushed what I've done. I'm a little bit stuck because I don't know how to solve the issues.
I've been using other services in order to learn how it works.

#3443 is ready to merge to add this badge, but there is one item we'd like to get your thoughts on @crazy-max as the OP of this issue.
The new badge #3443 will add the badge using our social badge style, so the badges will look like:

instead of the badge style discussed above:

I think the social style is a better fit considering, but what are your thoughts?

@calebcartwright We can do both using styles arg no ?

Thanks @crazy-max  - I was thinking more about the fact that the default style is different, but yes you should still be able to override the style. I also believe that the fact that default style is social means that the links are embedded into the badge image itself (which I believe still holds true even if you change the style).

@calebcartwright Yes indeed we could use the same implementation as twitter for example.

Thanks @crazy-max! I'll go ahead and merge

Closed in https://github.com/badges/shields/commit/d685cde52bd26070bccdf50cc555dfcb9118f130
It should be deployed in a few days, but anyone interested can track the deployment status here


use latest genome-nexus-java-api-client

standardize indenting of pom.xml files to two space indenting
standardize all components to same groupId

annotator module moved from group "org.cbioportal.annotator" to group "org.cbioportal.annotation.pipeline"

@averyniceday : I've updated the hash for the genome-nexus-java-api-client repo to the lastest head. I've also standardized the pom files ... so that all components belong to the same group, use two space indenting, and have the entries in a consistent order for the module and parent.
Maybe look at the changes with the "do not show whitespace only changes" option to help focus on the true changes.


Add myself as a maintainer for pam-auth-plugin

Description
Adding myself as a maintainer for pam-auth-plugin. Received confirmation from @jglick about joining.

Submitter checklist for changing permissions

Always

[x] Add link to plugin/component Git repository in description above

When adding new uploaders (this includes newly created permissions files)

[x] Make sure to @mention an existing maintainer to confirm the permissions request, if applicable
[x] Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
[x] All newly added users have logged in to Artifactory at least once

Ideally @stephenc would approve, since he's actually in the file.

Don’t know why i’m In the file... go for it and take me out of the file on this plugin (don’t remember ever doing anything with this plugin)


New package: JqData v0.0.2

Registering package: JqData
Repository: https://github.com/hzgzh/JqData.jl
Created by: @hzgzh
Version: v0.0.2
Commit: 9713d4cbb64d13138d0bf49647b1b2d026b22702
Git reference: master

https://github.com/JuliaRegistries/General/pull/8748#issuecomment-581772617


Memo documentation is duplicate of Computed

Hello,
Just found about legend-state from React Newsletter. Reading the docs it feels like you brought a core piece of Solid into React, excited to give this a try! 💜
I noticed the code sample for Memo is the same as Computed.

https://legendapp.com/open-source/state/fine-grained-reactivity/#memo
If it's as simple as to replace Computed by Memo I can put a PR up, but I would expect a difference or two.
Cheers,

Never mind, the main branch already fixed this so the website is likely pending deployment.
https://github.com/LegendApp/legend-state/commit/ce8c48bf9b9cac2e367d6bab846d3c8708776758


Web interface not reachable since 0.64.0

Home Assistant release (hass --version):
0.64.0
Python release (python3 --version):
3.6.4
Component/platform:
core
Description of problem:
The web interface is not reachable. It is not even possible to establish a connection as Home Assistant immediately rejects any request. There is one error logged which appears right after startup is finished, but no more messages as I try to open the web interface. Did not have this problem before switching to 0.64.0.
Expected:
The web interface shows up when accessing the server on port 8123.
Problem-relevant configuration.yaml entries and steps to reproduce:

Start Home Assistant
Wait for all the components to finish loading
Try to start the web interface

Traceback (if applicable):
Feb 27 15:23:29 home hass[1847]: 2018-02-27 15:23:29 INFO (MainThread) [homeassistant.bootstrap] Home Assistant initialized in 26.52s
Feb 27 15:23:29 home hass[1847]: 2018-02-27 15:23:29 INFO (MainThread) [homeassistant.core] Starting Home Assistant core loop
Feb 27 15:23:29 home hass[1847]: 2018-02-27 15:23:29 INFO (MainThread) [homeassistant.core] Starting Home Assistant
Feb 27 15:23:29 home hass[1847]: 2018-02-27 15:23:29 INFO (MainThread) [homeassistant.core] Bus:Handling <Event homeassistant_start[L]>
Feb 27 15:23:29 home hass[1847]: 2018-02-27 15:23:29 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Feb 27 15:23:29 home hass[1847]: Traceback (most recent call last):
Feb 27 15:23:29 home hass[1847]:   File "/usr/lib/python3.6/asyncio/tasks.py", line 180, in _step
Feb 27 15:23:29 home hass[1847]:     result = coro.send(None)
Feb 27 15:23:29 home hass[1847]:   File "/usr/lib/python3.6/site-packages/homeassistant/components/http/__init__.py", line 147, in start_server
Feb 27 15:23:29 home hass[1847]:     yield from server.start()
Feb 27 15:23:29 home hass[1847]:   File "/usr/lib/python3.6/site-packages/homeassistant/components/http/__init__.py", line 282, in start
Feb 27 15:23:29 home hass[1847]:     yield from self.app.startup()
Feb 27 15:23:29 home hass[1847]:   File "/usr/lib/python3.6/site-packages/aiohttp/web_app.py", line 249, in startup
Feb 27 15:23:29 home hass[1847]:     await self.on_startup.send(self)
Feb 27 15:23:29 home hass[1847]:   File "/usr/lib/python3.6/site-packages/aiohttp/signals.py", line 32, in send
Feb 27 15:23:29 home hass[1847]:     raise RuntimeError("Cannot send non-frozen signal.")
Feb 27 15:23:29 home hass[1847]: RuntimeError: Cannot send non-frozen signal.

I am getting this on a brand new 17.10 Server installation.  It actually crashes the entire server and I have to hard reboot.

Your issue is not related to mine, I do not even get a response from the server while you do.

I'm experiencing connection refused on a 0.64.2 startup

I have the same Issue on 0.64.3, it works fine with 0.64.2. Trace looks exactly like what flak3 posted, and no connection to the WebUI / API is possible.

I also have the same issue.

seems to me like a problem with aiohttp. Hass uses aiohttp-2.3.10, but appdaemon pulls aiohttp-3.0.5 which breaks hass. Switching back to aiohttp-2.3.10 solved this for me (appdaemon not tested with aiohttp-2.3.10)

That sounds right,  I first upgraded hass to 0.64.3, and then did an upgrade of appdaemon. Hass was broken after this, and appdaemon did install aiohttp. I then downgraded Hass to 0.64.2, which in turn installed aiohttp-2.3.10 again. Appdaemon seems to still work with this version of aiohttp (at least HAdashboards do still work)

I have no issues running hass 0.64.0 & 0.64.3 with aiohttp-3.0.5. I recreated my config and database, which was all I needed to make hass work again.


Updated example hash-sharded index names

Fixes https://github.com/cockroachdb/docs/issues/9604.
AFAICT, there are no examples of implicit columns in auto-generated index names. But I could be overlooking something.

This change is


Add flag to skip latest version check progress.

Really not needed to check in each run.

I've completed it on v0.4.6.


add new method eachElementCount for array

takes an array and return an object
which says each array elements occurrence
it works also works for an array of object

Hi.
Sorry my very late reply. I've been busy.
Collect.js is a JS implementation of Laravel Collection.
I can't seem to find this method in Laravel Collection source; So I'll have to decline this PR.
https://github.com/laravel/framework/blob/5.7/src/Illuminate/Support/Collection.php
Thank you for the contribution.


Frontend homework 12

Video URL:
https://drive.google.com/file/d/1qgqdd2IdgKUm-jsvhqAIHeYEfHgh9udT/view?usp=sharing
Add items:

Search:

Deletion:

Metric
Value

alert_status
:white_check_mark: OK

bugs
0

code_smells
5

reliability_rating
A (0 Bugs)Note: A being best, E being worst

security_rating
A (0 Vulnerabilities)Note: A being best, E being worst

vulnerabilities
0

Metric
Value

alert_status
:white_check_mark: OK

bugs
0

code_smells
5

reliability_rating
A (0 Bugs)Note: A being best, E being worst

security_rating
A (0 Vulnerabilities)Note: A being best, E being worst

vulnerabilities
0

Metric
Value

alert_status
:x: ERROR

bugs
0

code_smells
2

reliability_rating
A (0 Bugs)Note: A being best, E being worst

security_rating
A (0 Vulnerabilities)Note: A being best, E being worst

vulnerabilities
0

Preparing review...

Preparing review...

PR Reviewer Guide 🔍
Here are some key observations to aid the review process:

⏱ Estimated effort to review: 2 🔵🔵⚪⚪⚪
🧪 No relevant tests
🔒 No security concerns identified
⚡ Recommended focus areas for review
Unnecessary CodeThe added code lines 101-102 and 105 seem unnecessary and unrelated to the test case. They should be removed to keep the test focused and clean.
TypoThe variable name 'valuespeltwrony' on line 216 has a typo. It should be corrected to a meaningful name.
Commented Out CodeThe commented out code on lines 244-245 should be removed. If it's important, convert it to a proper test or delete it to keep the code clean.


Connection to self

Fix #1084
SelfEndpointTracker to store Endpoints known to be self (via the nonce check between peer versions)
Check in PeerConnector to not connect if known to be self.

Although this is an improvement to previous state, it is not complete to fix what was left in issue #1084. I like the idea of the node reacting to detection of connection to itself. This way we can to prevent the difficult task to open a list of all our external endpoints.
This modification does not affect PeerDiscoveryLoop, so it seems that the Discovery component will still connect to itself even after 1st attempt when it is detected.
Most importantly,It does not change the database of peers, therefore after the node is restarted, it will again connect to itself. I think this is crucial at should be added to this PR, because without it, it is very weak.
So I suggest that peer discovery is also affected and that upon detection the peer information is removed from the peer database, so that it won't be used after the node is restarted. Maybe the information should not be removed from the database, just a special flat should be said that this peer represents our own node and we should not connect to it. That is probably even better then removing the peer from the database, because it will prevent the entry to reappear later.

ok I see the point of using a singleton interface, this can be injected to the discovery loop to check connection to self.
So to add to apro suggestion in peerdiscoveryloop we can remove the self ip addresses from the db I think keeping a flag is a bit too much work for a maybe one extra short connection now and then

I think keeping a flag is a bit too much work for a maybe one extra short connection now and then

I disagree with that, but it is not critical.
Having it in the discovery loop, however, seems important.

added the check to peer discovery.

So to add to apro suggestion in peerdiscoveryloop we can remove the self ip addresses from the db I think keeping a flag is a bit too much work for a maybe one extra short connection now and then

I will filter inside PeerSelector.SelectPeer  too  but in terms of removing from db @fassadlr suggests this is a bad idea to actually remove from db as this would propogate round and effectively ban yourself from the network

I went briefly through the code and it looks good to me, but as usual I have done no tests, so I can't approve and someone else needs to do the testing.

I am on this now


Is Layered scrollify sections with same background image possible?

First posted on stack overflow here - sorry to post here, but i didnt have much luck there.
https://stackoverflow.com/questions/75504739/layered-scrollify-sections-with-same-background-image
I have the following page structure that I need to have sections scrolled to (using scrollify hopefully)
Hero video with background A (standard section)
Section with text A and background B
Section with text B and background B
Section with text C and background B
Section with Image B (standard section)
Section with Image C (standard section)
Section with Image D (standard section)
I have the sections working using scrollify for the non italic sections above, but is it possible to add the three sections with different text and the same background? In a similar way to the layered example here (which seems to have no example code)?
https://projects.lukehaas.me/scrollify/examples/layered-scrolling/
So on each scroll between italic sections, the text is replaced from A to B to C, but the background stays the same as B each time? And then after that goes back to the standard flow..
Here is my scrollify code -
$.scrollify({
section: ".section_wrap",
sectionName: "section-name",
interstitialSection: "",
easing: "easeOutExpo",
scrollSpeed: 600,
offset: 0,
scrollbars: true,
standardScrollElements: ".section-approach .section-projects .section-team",
updateHash: false,
});
Other info - this is a wordpress site that also has bootstrap 5.
cheers david

Yes, that should be possible. If you want to see the code for the layered example, it's viewable from the console:

hey, thanks for the quick reply. i cant see how i would specify that one background would be used three times though with the foreground changing each time?

When you said background I presumed you were referring to a background image or background colour etc.
Scrollify doesn't have the concept of background/foreground so I'm not really sure what to advise.

yes, it is a background image. That over the italic sections above remains the same background image, while the text changes on each scroll to show different text. So you don't see the background image change, but it shows a different piece of text each time you action the scroll.

I see. This is really more of a CSS challenge than a Scrollify one. Scrollify is always going to scroll the page so the trick will be to create the effect of a fixed background via CSS.


Minor fixes to the RNN-T Conformer model

Disable weight decay
Remove BatchNorm layers
Replace the BatchNorm in Conformer with LayerNorm
Replace relu with tahn in the joiner
Decrease the number of decoder layers from 4 to 2-layer LSTM
Remove SOS. We only need to keep the blank symbol

I just started an experiment with this PR. Will report the results once they are available.

With the changes listed in https://github.com/k2-fsa/icefall/pull/152#issue-1083738230
The WERs of this PR is

test-clean
test-other

WER
3.07
7.51

using --epoch 34 --avg 11 with greedy search.
I have updated the pre-trained model on hugging face and its usage in the colab notebook


File.writeFile() not creating file.

Ionic version:  (check one with "x")
(For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[x] 3.x
[ ] 4.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
Current behavior:
I am trying to create a file using writeFile() of File and attach the same to the email on the success callback.However, the file is never created and the email application does not open.If I remove the attachment from the email(file path to the created), the email application opens.Also I am unable to find the file in explorer.
Expected behavior:
Without the bug, the file would be created and would be attached on the email.
Steps to reproduce:
Sample code
this.file.writeFile(this.file.dataDirectory, 'test.csv', 'hello,world,', {replace: true})
.then(() => {
let email = {
to: 'email@email',
attachments: [this.file.dataDirectory + 'test.csv'],
subject: 'subject',
body: 'body text...',
isHtml: true
};
this.emailComposer.open(email);
})
.catch((err) => {
console.error(err);
});
Related code:
Other information:
I have not been able to find this issue anywhere.On other issues, the writer was creating file but not writing into it but in my case the file is not being created.
Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
cli packages: (C:\Users\HK491441\AppData\Roaming\npm\node_modules)

    @ionic/cli-plugin-proxy : 1.4.11
    @ionic/cli-utils        : 1.12.0
    ionic (Ionic CLI)       : 3.12.0

global packages:

    cordova (Cordova CLI) : not installed

local packages:

    @ionic/app-scripts : 2.1.4
    Cordova Platforms  : android 6.2.3 browser 4.1.0
    Ionic Framework    : ionic-angular 3.6.1

System:

    Android SDK Tools : 26.0.2
    Node              : v7.6.0
    npm               : 5.3.0
    OS                : Windows 7

Misc:

    backend : legacy

Hello! Thank you for opening an issue with us! Would you be able to provide a sample application via GitHub that demonstrates the issue you are having?
This does not sound like an Ionic Framework issue. This appears to be an issue you are having with one or more of the ionic-native plug-ins, so I am going to move this issue over there. Please follow-up using the issue that is created over there.
Thanks for using Ionic!

This issue was moved to ionic-team/ionic-native#2001


Streaming performance

Hi @jcupitt,
I saw the promising streaming features from the 8.9 release 🥳.
So I tested to see if I could gain some perf improvement over one of my uses of vips.
The result is not what I hoped for.
Here is a synthetic test I used:
puts "Ruby version: #{RUBY_VERSION}"

require "bundler/inline"

gemfile(true) do
  source "https://rubygems.org"

  gem "benchmark-ips"
  gem "down"
  gem "http"
  gem "ruby-vips"
end

require "benchmark/ips"
require "down/http"

IMAGE_URL = "https://images.unsplash.com/photo-1491933382434-500287f9b54b?q=80&w=5000"
SIZE = 512

def calc_shrink(image)
  image_size = image.size.min

  exp = Math.log2(image_size / (SIZE * 2.0)).floor

  [2 ** exp, 8].min # max for jpeg is 8x8
end

def vips_ops(image)
  image = image.thumbnail_image(SIZE, height: SIZE, crop: "centre")
  image = image.sharpen(sigma: 1, x1: 2, y2: 10, y3: 20, m1: 0, m2: 3)

  image
end

def old_way
  buffer = HTTP.get(IMAGE_URL).to_s

  image = Vips::Image.new_from_buffer(buffer, "", access: :sequential)
  shrink = calc_shrink(image)

  image = Vips::Image.new_from_buffer(buffer, "", access: :sequential, shrink: shrink) if shrink > 1
  image = vips_ops(image)

  # simulate old process then write to file
  result = image.jpegsave_buffer(Q: 95, interlace: true, strip: true)
  File.write("old_way.jpg", result)
end

def stream_way
  remote = Down::Http.open(IMAGE_URL)

  source = Vips::SourceCustom.new
  source.on_read { |length| remote.read(length) }
  source.on_seek { |offset, whence| remote.seek(offset, whence) }

  image = Vips::Image.new_from_source(source, "", access: :sequential)
  shrink = calc_shrink(image)

  image = Vips::Image.new_from_source(source, "", access: :sequential, shrink: shrink) if shrink > 1
  image = vips_ops(image)

  image.write_to_file("stream_way.jpg", Q: 95, interlace: true, strip: true)
  remote.close
end

Benchmark.ips do |x|
  x.config(time: 10, warmup: 2)

  x.report("old_way") { old_way }
  x.report("stream_way") { stream_way }
end

Result:
Ruby version: 2.6.5
Fetching gem metadata from https://rubygems.org/............
Resolving dependencies...
Using rake 13.0.1
Using public_suffix 4.0.3
Using addressable 2.7.0
Using benchmark-ips 2.7.2
Using bundler 1.17.3
Using unf_ext <IP_ADDRESS>
Using unf 0.1.4
Using domain_name 0.5.20190701
Using down 5.1.0
Using ffi 1.11.3
Using ffi-compiler 1.0.1
Using http-cookie 1.0.3
Using http-form_data 2.2.0
Using http-parser 1.2.1
Using http 4.3.0
Using ruby-vips 2.0.17
Warming up --------------------------------------
             old_way     1.000  i/100ms
          stream_way     1.000  i/100ms
Calculating -------------------------------------
             old_way      3.326  (± 0.0%) i/s -     33.000  in  10.105056s
          stream_way      3.230  (± 0.0%) i/s -     32.000  in  10.044809s

Do you have any insight? Maybe I missed something.

Hello @maximeg,
That's very interesting, thank you for testing this.
I think what's happening is that your processing is relatively quick, so being able to do it during the download does not save a great deal of time.
I tried:
$ time vips jpegload 'photo-1491933382434-500287f9b54b?q=80&w=5000' x.jpg --shrink 8
real	0m0.099s
user	0m0.102s
sys	0m0.005s

It's only 100ms of CPU that can be overlapped with download.
It should save you a useful chunk of memory -- you're no longer buffering the entire source image.
I don't know why implementing seek makes a difference, that seems very curious (and inefficient). I'll investigate.

I had a thought: how about adding upload as well, to simulate writing back to S3?
The stream version should be able to overlap download and upload, and that ought to give a nice speedup.

I spent a little time on this again. Here's a revised version of that nice benchmark:
puts "Ruby version: #{RUBY_VERSION}"

require "bundler/inline"

gemfile(true) do
  source "https://rubygems.org"

  gem "benchmark-ips"
  gem "down"
  gem "http"
  gem "ruby-vips"
end

require "benchmark/ips"
require "down/http"

IMAGE_URL = "https://images.unsplash.com/photo-1491933382434-500287f9b54b?q=80&w=5000"
SIZE = 512

def vips_ops(image)
  image = image.sharpen(sigma: 1, x1: 2, y2: 10, y3: 20, m1: 0, m2: 3)

  image
end

def old_way
  buffer = HTTP.get(IMAGE_URL).to_s

  image = Vips::Image.thumbnail_buffer(buffer, SIZE, crop: "centre")
  image = vips_ops(image)
  image.write_to_file("old_way.jpg", Q: 95, strip: true)
end

def stream_way
  remote = Down::Http.open(IMAGE_URL)

  source = Vips::SourceCustom.new
  source.on_read { |length| remote.read(length) }
  # fails if we don't implement seek() ... why?
  source.on_seek { |offset, whence| remote.seek(offset, whence) }

  image = Vips::Image.thumbnail_source(source, SIZE, crop: "centre")
  image = vips_ops(image)
  image.write_to_file("stream_way.jpg", Q: 95, strip: true)
  remote.close
end

def download_and_stream_way
  tmpfile = Down::Http.download(IMAGE_URL)
  source = Vips::Source.new_from_memory tmpfile.read
  tmpfile.unlink

  image = Vips::Image.thumbnail_source(source, SIZE, crop: "centre")
  image = vips_ops(image)
  image.write_to_file("download_and_stream_way.jpg", Q: 95, strip: true)
end

Benchmark.ips do |x|
  x.config(time: 10, warmup: 2)

  # streaming is slower overall, perhaps because of the number of callbacks we
  # end up triggering ... try buffering reads?
  x.report("old_way") { old_way }
  x.report("stream_way") { stream_way }
  x.report("download_and_stream_way") { download_and_stream_way }
end

Changes:

don't write with interlace since that will force the whole image to buffer
don't use thumbnail_image since that will stop shrink-on-load
add a third path: download to memory, then stream from memory

I see:
Calculating -------------------------------------
             old_way      2.412  (± 0.0%) i/s -     25.000  in  10.377908s
          stream_way      2.349  (± 0.0%) i/s -     24.000  in  10.247770s
download_and_stream_way
                          2.426  (± 0.0%) i/s -     25.000  in  10.315862s

Notes:

stream_way is slower overall by ~3%
downloading and then streaming from the buffer is the same speed as the old way
Source is generating ~220 callbacks for each resize

So I think it's likely that the slowdown is just the Ruby callback overhead. Therefore:

investigate and find out why the seek needs to be implemented (this would save 20 pointless callbacks)
see if we can make the JPEG reader fetch the image in fewer pieces (it's averaging 2.3kb per read at the moment)


add grant command

Thanks! Keep them coming, just what I needed @billysometimes !
Will implement these soon


x/website GitHub stars in go.pkg.dev

What did you expect to see?
Upon loading any module in the go.pkg.dev, it would be great to see the star count as well if the module is from GitHub.

Have you seen related issues like https://github.com/golang/go/issues/41805?
GitHub is just one hosting provider, so it seems wrong to hardcode features just for it. Plus, stars rarely mean anything on their own. I think some form of "popularity score" or "quality score" could be interesting to do (see the issue above), but it certainly can't be just stars.

See also #36952

apologies, I will close this issue., I can understand why not GitHub stars definitely too.


1.Hi, I would like to know what do you refer to as Rademacher distribution in A.4, and why

2.In page 21 of the paper, i.e. my diagram below, how do I get the last step from (iii)

3.In Sec4.1, you only proved that g is an L-smooth objective function, but the loss function (1) in the paper is obviously not an L-smooth function, so how do you explain the convergence of the algorithm you proposed in this paper?

@max-andr

Hi,

Rademacher distribution is the uniform distribution over {-1, 1}, i.e. we take -1 or 1 with 50% probability. I think it's pretty common to call this distribution "Rademacher", e.g. see the Wikipedia page: https://en.wikipedia.org/wiki/Rademacher_distribution.

Hmm, the Jensen's inequality in step (iii) actually should not be there. So please just ignore that step. The final lower bound is correct, though. The trick is to explicitly write out E_{(r,s)} ||V_{(r,s)}||_2 as the sum of L2 norms of patches V_{(r,s)} normalized by w^2 (since we have w^2 possible positions of the coordinates r and s). We can then reduce this sum to h^2 summations of L2 norms over non-overlapping patches, each of the summation is lower bounded by ||v||_2 (this lower bound is essentially similar to the fact that L1-norm is always greater or equal to the L2-norm). Thus, we get that E_{(r,s)} ||V_{(r,s)}||_2 \geq h^2 / w^2 ||v||_2

Indeed, for untargeted attacks we use the margin loss which is not smooth. However, for targeted attacks we do use a smooth loss (cross-entropy). Actually, we could have used the cross-entropy loss also for untargeted attacks, I don't think it would change the results much. But I agree that we should've commented on this discrepancy between the usage of the margin loss and the L-smoothness assumption.

These were all good points, thank you for the careful reading of our paper! Let me know if you find something else.
Best,
Maksym


the fixes for the temperature are not in the release

Can you make a new release with the latest fixes?
SO I can that use in the docker image

I have fixed it I download the zip from the master and overwrite the files

Don't forget to change the installation instructions, it still points to version 1.2.1 :)

I guess you mean the code change from #17. So I close this issue as a duplicate.


Error while fetching extensions. XHR failed.

Type: Bug
Click extensions icon to load Python. Starts running. Then stops and shows the message in the title.
VS Code version: Code 1.90.0 (89de5a8d4d6205e5b11647eb6a74844ca23d2573, 2024-06-04T19:33:54.889Z)
OS version: Windows_NT x64 10.0.22631
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz (8 x 2394)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
7.91GB (3.03GB free)

Process Argv
--crash-reporter-id f9525af4-20b2-4f14-b153-124f6dc1d7b8

Screen Reader
no

VM
0%

Extensions: none

This is an installation issue. /cc @sandy081

What's the fix?

@Daviddv2 I am not familiar with the area, @sandy081 is I have assigned it to them to provide more input here.

/gifPlease

Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette). Lastly, please attach this file via the GitHub web interface as emailed responses will strip files out from the issue.
Happy coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Add include tag for module descriptions

it would be nice to have include tags for module descriptions, in the same way there are for element or attribute descriptions, e.g.:
{% include desc module="shared" %}

@bwbohl obsolete? That would be needed to be addressed in the ODD now, right?

@bwbohl Can we close this?


adding yield keyword

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

File
Status
Preview URL
Details

Advertising/scripts/concepts/best-practices.md
:white_check_mark:Succeeded

Advertising/scripts/examples/keywords.md
:white_check_mark:Succeeded

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Create a real website

read this http://jmcglone.com/guides/github-pages/ as well

https://jekyllrb.com/docs/structure/
https://programminghistorian.org/en/lessons/building-static-sites-with-jekyll-github-pages
https://mmistakes.github.io/minimal-mistakes/


Added missing parameters to MSFT_xExchActiveSyncVirtualDirectory/MSFT_xExchAutodiscoverVirtualDirectory/MSFT_xExchWebServicesVirtualDirectory and converted schema.mof to UTF-8 #159

This change is

Hey @IngoGege, except for one issue, this looks functionally good. I mostly just see style issues. Here's what I found.
Functional:
-I don't think the call to ($ExtendedProtectionFlags.Contains('AllowDotlessSPN') ) would work if they passed in an alternate case ('allowdotlessspn'), as .Contains is case sensitive. May want to use StringArrayToLower() from xExchangeCommon.
Duplicate Code:
-Function Test-SPN exists in both MSFT_xExchActiveSyncVirtualDirectory and xExchCommon
-Style:
-The Begin/Process/End blocks in Test-SPN need to be indented
-Case inconsistencies in begin/process/end in ConvertTo-Array vs. Test-Spn
-Case inconsistencies in test-spn parameter types (string, Switch). While updating, might as well switch to fully qualified (System.String) to make match other functions.
-No [CmdletBinding[]] in ConvertTo-Array, or parameter type ([Object[]]?)
Other:
-Modification of MSFT_xExchAutoDiscoverVirtualDirectory is not mentioned in README

Hi @mhendric,
you're absolutely correct. I fixed the style and the case-sensitivity issue for the SPN check.
Ciao,
Ingo

Hi @IngoGege , with the latest commits, why is CertificateAuthentication removed from xExchWebServicesVirtualDirectory? Also, if you intend to have it removed, it should probably be fully removed from the code rather than just commented out.
Thanks.

Hi @IngoGege , one other thing, I wanted to see what you think about moving the (#verify SPNs depending on AllowDotlesSPN ) section to a dedicated function. It looks like you have the same code block in two different files. It also looks like there's some other resources that may benefit from this (OAB and OutlookAnywhere... you don't have to check and modify those now, but we may want to at a later point if it makes sense).

Hi @mhendric, the function Test-SPN was moved to xExchangeCommon.psm1 as I saw this as well. I don't see it in any of the other DSCResources I modified. In regards of the CertificateAuthentication in the DSCResource xExchWebServicesVirtualDirectory, I wasn't sure about deleting or removing the code. I'll remove it.
Ciao,
Ingo

Hi @IngoGege , regarding CertificateAuthentication on xExchWebServicesVirtualDirectory, I was really trying to understand why you want it removed (or commented) in the first place? It looks like it's still a valid parameter on Set-WebServicesVirtualDirectory, at least as far as TechNet shows (https://technet.microsoft.com/en-us/library/aa997233(v=exchg.160).aspx).
Regarding the (#verify SPNs depending on AllowDotlesSPN ) section, I see the same code block in Set-TargetResource in both xExchAutoDiscoverVirtualDirectory and xExchWebServicesVirtualDirectory. This is outside of the Test-SPN function (although it calls the Test-SPN function). I think this could possibly be abstracted into a dedicated function (Test-ExtendedProtectionSPNList perhaps).

Hi @mhendric, have a look at the description "This parameter affects the /ews/management/ virtual directory. It doesn't affect the /ews/ virtual directory.". I've tested this and the parameter didn't do anything for me. Certificate based authentication is not enabled. Therefore I decided to remove it.
In regards of the SPN section:
Thus means you want to have the whole code-block simplified into a function, correct?
Ciao,
Ingo

I think it makes sense to move it to a single function, as you have the same multi-line code block in two files right now, and it looks like there's other resources that could benefit from it in the future. Let me know what you think.
Regarding CertificateAuthentication, I would probably opt to leave it in there. It will be a breaking change to remove it, as anyone who does use it in their scripts (whether it does anything or not) will have to update their scripts next time they compile. And even if it modifies a different virtual directory, it's still part of the Set-WebServicesVirtualDirectory cmdlet, which xExchWebServicesVirtualDirectory is supposed to map to. Unless you feel it could cause harm to leave it in there, I think it's safer just to leave it.

@mhendric now I got it...sorry that this took so long..yes, I'll put the CertificateAuthentication back in place, but we need to exclude this from the integration tests. I'll also re-write the function for the SPN check.
Ciao,
Ingo

Hi @mhendric ,
I stumbled across an issue: When you want to reset ExtendedProtectionFlags, you need to use the value 'None'. With this the returned array is empty. I can either force to return 'None' in Get-TargetResource of overwrite in Test-TargetResource the ExpectedValue (instead of 'None', empty array).
I was going to force the output to 'None'. What do you think?
Ciao,
Ingo

Hi @IngoGege , what about modifying the Test-TargetResource section so that it verifies the array conents, but also checks whether None was passed, and there's an empty array. Like:
if (-not (VerifySetting -Name "ExtendedProtectionFlags" -Type "Array" -ExpectedValue $ExtendedProtectionFlags -ActualValue $autoDVdir.ExtendedProtectionFlags -PSBoundParametersIn $PSBoundParameters -VerbosePreference $VerbosePreference) -and -not ((StringArrayToLower $ExtendedProtectionFlags).Contains("none") -and $autoDVdir.ExtendedProtectionFlags.Count -eq 0))
Since this modified test would be done in multiple files, you'd probably want to move it to a common function.
On a related note, do you know what happens if None is passed along with another valid flag? Any thoughts on whether we should check for that and block the resource from trying to set it, or if we should just let it fail on the Exchange side? I'm leaning towards just letting it fail, but wanted to get your opinion.

Hi @mhendric ,
I have almost all covered in a new function Test-ExtendedProtectionSPNList as you proposed. As we already let in other DSCResources invalid combination of parameters fail in Set-Targetresource, I would proceed and let it there fail. For verifying, I would enhance the function VerifySetting with the type ExtendedProtection to cover the 'None'/NULL scenario.
Another reason is that the function VerifySetting can verify only 2 input objects, whereas we would need to check 3 (Flags,SPNList and current value), which makes it most likely too complex.
To summurize:

in Set-TargetResource let invalid combination of parameters fail with function Test-ExtendedProtectionSPNList

for Test-TargetResource enhance function VerifySetting with type ExtendedProtection to have a valid check in case 'None' is used as this results in an empty arry
Makes sense?
Ciao,
Ingo

Sounds good to me, @IngoGege . Thanks.

Hi @mhendric ,
I finally made it. There were some other minor things I also had to fix.
Ciao,
Ingo


Lab 6 spacing needed

Ex 2, Task 2, Step 1 - Note and JSON code blocks need to be spaced over to realign the numbering sequence.

Thanks for the heads-up. Much appreciated. We'll investigate and get back to you.


update translations

This is missing strings, due to #763, but it's still worth doing.

Correction --- the strings are correctly being picked up, but due to #763 they won't actually appear correctly on Crowdin. So there's no reason to delay merging this.


storePublicly() is not storing file automatically in public storage unless explicitly defined

Laravel Version: 5.1
PHP Version: 7.1
Database Driver & Version:

Description:
When I call Request->file()->storePublicly() files does not save automatically under storage/app/public unless i define in options array and pass as argument.
Steps To Reproduce:

Looks like this method does not mean to save in public pool hence it means saving as public accessible file in s3 or extenrnal storage. This makes sense now.


HTTPProvider.bootlift catch UnavailableException but should not

Mailing List thread: https://groups.google.com/forum/#!topic/liftweb/BHYjE5C-kIk
The HTTPProvider.bootLift method is catching javax.servlet.UnavailableException, which it should not because the exception is here to tell the application server that the servlet failed to boot.
In Lift 2.6.x, it was even worse because the method was catching ALL exceptions, even Errors.
How to reproduce
Throws a javax.servlet.UnavailableException in Lift boot() method. The exception is caught during boot and the log displays a big warning message:
------------------------------------------------------------------
------------------------------------------------------------------
------------------------------------------------------------------
------------------------------------------------------------------
******** Failed to Boot! Your application may not run properly
[here the exception message]
------------------------------------------------------------------
------------------------------------------------------------------
------------------------------------------------------------------
------------------------------------------------------------------

Use case
I'm doing a lot of initialization and resource availability checking at bootstrap, and it was natural to put them in Lift boot() method. The UnavailableException was a conventionnal way to tell the web-app server that something went horribly wrong during init and the servlet is  unavailable. Jetty (for ex) will then respond with "error 503: service unavailable" when a query is done to that app.
Workaround
For now, I added a ServletContextListener where I'm doing the init and throw UnavailableException, but it  splits the initialization logic between it and Lift boot() and make the code harder to follow.

Going to aim to handle this for 3.1.0-M3.


Update to support sourceUri field

Importer needs to send source URI information to Seiso.
This will require a URI template since the data masters don't themselves include hypermedia links. (Do we want to add self links here? I don't think so, but it's a possibility.)

On hold. Will figure out how we want to handle sources and reopen if necessary.


Sauce Labs Case # 37748 - latest-n chrome

MAR 31, 2016  |  04:07PM PDT
Original message
skatejs wrote:
Our builds started failing, because the newly introduced feature with "latest-n" does not seem to work for Chrome any longer:
https://travis-ci.org/skatejs/skatejs/builds/119106979
browser config: https://github.com/skatejs/build/commit/2485e67430297a871ce72c2979799e2a2ab4f539
has worked up until a day ago.
MAR 31, 2016  |  04:55PM PDT
Albert Sison replied:
Hello,
Thank you for writing in to Sauce Labs support. Can you re-run your Sauce tests explicitly specifying a platform version (ex. Linux) in your desired capabilities for your Chrome version latest-1 and latest-2 tests?
Regards,
Albert

Closing this as I think we're going to test out using BrowserStack instead.


Not able to pull development images from docker hub registry

While installing compose-on-kubernetes on Openshift, docker is not able to pull the images.
I had a sucessful installation before this a few days ago and upon trying to install again got the following errors in the events log.
$ oc get events

25s         33s          3         compose-6f86bfd5df-kb9p2.15872989417a6a81       Pod                                     Normal    SandboxChanged      kubelet, shiftnode1     Pod sandbox changed, it will be killed and re-created.
22s         1m           2         compose-6f86bfd5df-kb9p2.1587297fa20fd69c       Pod          spec.containers{compose}   Normal    Pulling             kubelet, shiftnode1     pulling image "docker/kube-compose-dev-controller:v0.4.18"
12s         55s          2         compose-api-7d54c4c88b-5dsv4.1587298436dad512   Pod          spec.containers{compose}   Warning   Failed              kubelet, shiftnode1     Failed to pull image "docker/kube-compose-dev-api-server:v0.4.18": rpc error: code = Unknown desc = repository docker.io/docker/kube-compose-dev-api-server not found: does not exist or no pull access
12s         55s          2         compose-api-7d54c4c88b-5dsv4.1587298436db5795   Pod          spec.containers{compose}   Warning   Failed              kubelet, shiftnode1     Error: ErrImagePull
11s         51s          3         compose-api-7d54c4c88b-5dsv4.15872985211b345f   Pod          spec.containers{compose}   Normal    BackOff             kubelet, shiftnode1     Back-off pulling image "docker/kube-compose-dev-api-server:v0.4.18"
11s         51s          3         compose-api-7d54c4c88b-5dsv4.15872985211bae48   Pod          spec.containers{compose}   Warning   Failed              kubelet, shiftnode1     Error: ImagePullBackOff

I was able to pull the docker/kube-compose-controller and  docker/kube-compose-api-server images but not the developer ones.
docker images | grep compose
docker/kube-compose-controller                                       latest<PHONE_NUMBER>87        4 weeks ago         30.8MB
docker/kube-compose-api-server                                       latest              3a4f4d2514c0        4 weeks ago         48.4MB

$ docker version
Client:
 Version:           18.09.2
 API version:       1.39
 Go version:        go1.10.6
 Git commit:        6247962
 Built:             Sun Feb 10 04:13:56 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.2
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.6
  Git commit:       6247962
  Built:            Sun Feb 10 03:47:25 2019
  OS/Arch:          linux/amd64
  Experimental:     false

$ docker info
Containers: 19
 Running: 0
 Paused: 0
 Stopped: 19
Images: 21
Server Version: 18.09.2
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version:<PHONE_NUMBER>f7fe2f4e74d43e2fc7ccd237edcbce
runc version: 09c8266bf2fcf9519a651b04ae54c967b9ab86ec
init version: fec3683
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.18.10-200.fc28.x86_64
Operating System: Fedora 28 (Workstation Edition)
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 19.31GiB
Name: localhost.localdomain
ID: 6DYY:6P6W:LHQN:S7HN:MQHN:3W3T:SCWZ:WLWT:GWXS:4RQM:OLCD:DEBO
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false
Product License: Community Engine

Dev images are only built using your local daemon and are never pushed to the registry. The development workflow is currently tailored for developers using Docker Desktop (which provides a single-node local kubernetes).
This works on Docker Desktop, because the daemon used for building images is the same as the one using to run Kubernetes workloads (so when you do a docker build, the built image is available for Kubernetes workloads without having to push to a registry).
For developing on an external cluster, you can play with the IMAGE_REPO_PREFIX env variable and push the images in your own repository.

Was able to change the image, using the IMAGE_REPO_PREFIX, so that a workable image could be pulled from dockerHub without giving an ErrImagePull error.
 # export IMAGE_REPO_PREFIX="docker/kube-compose-"


fix issue 2091

Resubmission of fix for issue 2091 (https://github.com/slimphp/Slim/pull/2094).

@akrabat This should now target slimphp/Slim-Http right?

Yes, please.

Done.


Adjust metric names and drop redundant metrics

JIRA issue: DCOS_OSS-5436

Codecov Report

Merging #53 into master will increase coverage by 0.43%.
The diff coverage is 83.33%.

@@            Coverage Diff             @@
##           master      #53      +/-   ##
==========================================
+ Coverage   81.02%   81.46%   +0.43%
==========================================
  Files          29       29
  Lines        1713     1710       -3
==========================================
+ Hits         1388     1393       +5
+ Misses        325      317       -8

Impacted Files
Coverage Δ

src/lashup_kv_sync_tx_fsm.erl
92.3% <ø> (+1.53%)
:arrow_up:

src/lashup_kv_sync_rx_fsm.erl
87.87% <ø> (ø)
:arrow_up:

src/lashup_hyparview_membership.erl
81.19% <100%> (+0.22%)
:arrow_up:

src/lashup_gm_mc.erl
76.19% <100%> (+1.19%)
:arrow_up:

src/lashup_gm.erl
81.5% <100%> (ø)
:arrow_up:

src/lashup_kv.erl
79.47% <75%> (-0.26%)
:arrow_down:

src/lashup_hyparview_ping_handler.erl
88.05% <0%> (+7.46%)
: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 9819e1d...a2e0446. Read the comment docs.

ditto https://github.com/dcos/dcos-net/pull/168#pullrequestreview-273368762

I'd say it is not ditto in this case.

In case of Lashup metrics, we have not a dashboard yet. And it is easy to backport it to 1.13
This PR is not simply about polishing metric names. Some names are just confusing (handle_cast, for instance, is it about Erlang's handle_cast function, multicast, anycast?), and some metrics are simply erroneous (for instance, measuring operation execution, exceptions, execution rejections, whichever gets to happen)


Viewing a previous score that was played with a different judge has incorrect info

Describe the bug
If I view a J7 score, everything on the eval screen looks to be using J7 except the graph. Once you change the judge it updates the judgements, MA/PA, acc % accordingly.
To Reproduce
Steps to reproduce the behavior:

Make sure you're on J4/J5
View a J7 score
Note judgements, MA/PA, acc % are shown for J7
Change judge on eval screen
Score now correctly uses your current judge

Expected behavior
The initial judgement counts and MA/PA ratio when first viewing a score match your current judge.
Screenshots
Viewing a J7 score while using J4:

Switch to another judge then go back to J4:

Desktop (please complete the following information):

OS: Windows 10
Version 0.67.0
64bit

Oversight due to laziness

We have to assume that all site replays are J4, but I have this working clientside, kind of.

Mitigated but not fully solved in hotfix by a series of commits.
Basically, when viewing a local replay the judge you start on in the eval screen is now the judge of the replay regardless of what you chose. So that works consistently. It doesn't match gameplay, but is more consistent with the score. This lets view eval make sense in a simpler way. At the same time, custom windows doesn't support this. So if you have custom windows on, this fix does not work.
Closed when merged.


When I try to "mvn clean package docker:build"  ,it is always show a Error "failed: connect timed out"

Description
When I try to "mvn clean package docker:build"  ,it is always show a Error "failed: connect timed out"
How to reproduce
1.Open the docker remote API port
vi /usr/lib/systemd/system/docker.service
After the code ExecStart=/usr/bin/dockerd , I add this code
-H tcp://<IP_ADDRESS>:2375 -H unix:///var/run/docker.sock
2.Execute command
systemctl daemon-reload
systemctl start docker

Afterwards,
netstat -anp|grep 2375

curl <IP_ADDRESS>:2375/info

3. add a environment variable

and this is docker ip:

4. My pom.xml

5. I execute mvn clean package docker:build
What do you expect
BUILD SUCCESS
What happened instead

Software:

docker version: server 18.09.3  client 18.09.3
docker-maven-plugin version: 1.0.0
maven version:3.0.5

Full backtrace

The problem is fixed, the reason is the CentOS 7 's firewall is not closed

But a another Error appear