OpenEBS NDM LUKS encrypted volume toggles between Active/Inactive state

Description
We have setup LUKS encryption for openebs on our kubernetes cluster
however we noticed that the status of the encrypted BD status toggled  between Active and Inactive state every second.
Hence, our application was not able to claim the BD and create pvc's.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-Architecture
We have a three node kubernetes cluster setup with 1 LUKS encrypted volume created on every node

**node01**

ls -lrt /dev/mapper/encrypted-openebs
lrwxrwxrwx. 1 root root 8 Dec 20 06:35 /dev/mapper/encrypted-openebs -> ../dm-16
lsblks
sde                                                              8:64   0   16G  0 disk
└─encrypted-openebs                           252:16   0   16G  0 crypt

**node02**

#ls -lrt /dev/mapper/encrypted-openebs
lrwxrwxrwx. 1 root root 8 Dec 20 05:35 /dev/mapper/encrypted-openebs -> ../dm-20
#lsblk
sde                                                                                8:64   0   16G  0 disk
└─encrypted-openebs                                                                           252:20   0   16G  0 crypt
lsblk | grep 252:16
│   ├─docker-252:1-134309954-763s4152135ja1d3095604c92f8a72a30e88b298f849e3c0bfaf23d93517c3ad70 252:16   0   10G  0 dm    /path/docker/devicemapper/mnt/763s4152135ja1d3095604c92f8a72a30e88b298f849e3c0bfaf23d93517c3ad70

**node03**

#ls -lrt /dev/mapper/encrypted-openebs
lrwxrwxrwx. 1 root root 8 Dec 20 06:26 /dev/mapper/encrypted-openebs -> ../dm-42
#lsblk
sde                                                                                8:64   0   16G  0 disk
└─encrypted-openebs                                                                                252:42   0   16G  0 crypt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
**Logs**
From the ndm pod logs , we could see a error at /dev/dm-16 on node02

E1227 10:21:33.174561       6 logs.go:35] unable to set flag, Error: no such flag -logtostderr
I1227 10:21:33.174801       6 commands.go:72] Starting Node Device Manager Daemon...
I1227 10:21:33.174816       6 commands.go:73] Version Tag : 1.6.0
I1227 10:21:33.174820       6 commands.go:74] GitCommit : dc2311c1e635d7fc7d15eaeeaba3bdebbc8168ac
I1227 10:21:33.177159       6 features.go:128] Feature gate: MountChangeDetection, state: disable
I1227 10:21:33.177180       6 features.go:128] Feature gate: GPTBasedUUID, state: enable
I1227 10:21:33.177187       6 features.go:128] Feature gate: APIService, state: disable
I1227 10:21:33.177191       6 features.go:128] Feature gate: UseOSDisk, state: disable
I1227 10:21:35.205088       6 controller.go:252] BlockDevice CRD is available
I1227 10:21:35.210759       6 filter.go:60] registering filters
I1227 10:21:35.210804       6 filter.go:68] configured os disk exclude filter : state enable
E1227 10:21:35.212530       6 osdiskexcludefilter.go:92] unable to configure os disk filter for mountpoint: /etc/hosts, error: could not get device mount attributes, Path/MountPoint not present in mounts file
E1227 10:21:35.213764       6 osdiskexcludefilter.go:92] unable to configure os disk filter for mountpoint: /path/docker, error: could not get device mount attributes, Path/MountPoint not present in mounts file
E1227 10:21:35.214093       6 osdiskexcludefilter.go:92] unable to configure os disk filter for mountpoint: /path/docker/devicemapper, error: could not get device mount attributes, /MountPoint not present in mounts file
E1227 10:21:35.215625       6 osdiskexcludefilter.go:104] unable to configure os disk filter for mountpoint: /boot, error: could not get device mount attributes, Path/MountPoint not present in mounts file
E1227 10:21:35.215756       6 osdiskexcludefilter.go:104] unable to configure os disk filter for mountpoint: /path, error: could not get device mount attributes, Path/MountPoint not present in mounts file
E1227 10:21:35.215870       6 osdiskexcludefilter.go:104] unable to configure os disk filter for mountpoint: /path/docker, error: could not get device mount attributes, Path/MountPoint not present in mounts file
E1227 10:21:35.215988       6 osdiskexcludefilter.go:104] unable to configure os disk filter for mountpoint: /path/docker/devicemapper, error: could not get device mount attributes, Path/MountPoint not present in mounts file
E1227 10:21:35.216103       6 osdiskexcludefilter.go:104] unable to configure os disk filter for mountpoint: /storage, error: could not get device mount attributes, Path/MountPoint not present in mounts file
E1227 10:21:35.216207       6 osdiskexcludefilter.go:104] unable to configure os disk filter for mountpoint: /path/docker/devicemapper/mnt/9ad808b82c1284595604c92f8a72a30e88b298f849e3c0bfaf23d93517c3ad70, error: could not get device mount attributes, Path/MountPoint not present in mounts file
I1227 10:21:35.216261       6 filter.go:68] configured vendor filter : state enable
I1227 10:21:35.216282       6 filter.go:68] configured path filter : state enable
I1227 10:21:35.216292       6 filter.go:68] configured device validity filter : state enable
I1227 10:21:35.216804       6 probe.go:65] registering probes
I1227 10:21:35.216852       6 probe.go:87] configured seachest probe : state disable
I1227 10:21:35.216866       6 probe.go:87] configured smart probe : state enable
I1227 10:21:35.216876       6 probe.go:87] configured mount probe : state enable
I1227 10:21:35.216922       6 probe.go:87] configured udev probe : state enable
I1227 10:21:35.217038       6 udevprobe.go:337] starting udev probe listener
I1227 10:21:35.230149       6 udevprobe.go:198] device: /dev/sda, WWN: 0x6000c29cbe985f70 filled during udev scan
I1227 10:21:35.230173       6 udevprobe.go:202] device: /dev/sda, Serial: 6000c29cbe985f7038040f0b3d123ba0 filled during udev scan
I1227 10:21:35.230477       6 udevprobe.go:231] Dependents of /dev/sda : {Parent: Partitions:[/dev/sda1 /dev/sda2] Holders:[] Slaves:[]}
I1227 10:21:35.230511       6 udevprobe.go:241] Device: /dev/sda is of type: disk
I1227 10:21:35.230736       6 udevprobe.go:198] device: /dev/sda1, WWN: 0x6000c29cbe985f70 filled during udev scan
I1227 10:21:35.230753       6 udevprobe.go:202] device: /dev/sda1, Serial: 6000c29cbe985f7038040f0b3d123ba0 filled during udev scan
I1227 10:21:35.230759       6 udevprobe.go:214] device: /dev/sda1, FileSystemUUID: 479a7b4c-c6f6-437e-b268-bb84e5aa1f4e filled during udev scan
I1227 10:21:35.230966       6 udevprobe.go:231] Dependents of /dev/sda1 : {Parent:/dev/sda Partitions:[] Holders:[] Slaves:[]}
I1227 10:21:35.230982       6 udevprobe.go:241] Device: /dev/sda1 is of type: partition
I1227 10:21:35.231193       6 udevprobe.go:198] device: /dev/sda2, WWN: 0x6000c29cbe985f70 filled during udev scan
I1227 10:21:35.231208       6 udevprobe.go:202] device: /dev/sda2, Serial: 6000c29cbe985f7038040f0b3d123ba0 filled during udev scan
I1227 10:21:35.231214       6 udevprobe.go:214] device: /dev/sda2, FileSystemUUID: a674e624-3c0b-4e72-bf04-379e67e2de82 filled during udev scan
I1227 10:21:35.231414       6 udevprobe.go:231] Dependents of /dev/sda2 : {Parent:/dev/sda Partitions:[] Holders:[] Slaves:[]}
I1227 10:21:35.231430       6 udevprobe.go:241] Device: /dev/sda2 is of type: partition
I1227 10:21:35.231643       6 udevprobe.go:198] device: /dev/sdb, WWN: 0x6000c2988a8a5da5 filled during udev scan
I1227 10:21:35.231660       6 udevprobe.go:202] device: /dev/sdb, Serial: 6000c2988a8a5da52c3faff753efa33c filled during udev scan
I1227 10:21:35.231665       6 udevprobe.go:214] device: /dev/sdb, FileSystemUUID: DAloPY-Knfc-Z8ey-Q1Pi-mEOY-bzZp-ypePGJ filled during udev scan
I1227 10:21:35.231942       6 udevprobe.go:231] Dependents of /dev/sdb : {Parent: Partitions:[] Holders:[/dev/dm-2 /dev/dm-3] Slaves:[]}
I1227 10:21:35.231960       6 udevprobe.go:241] Device: /dev/sdb is of type: disk
I1227 10:21:35.232181       6 udevprobe.go:198] device: /dev/sdc, WWN: 0x6000c29d5bf293ac filled during udev scan
I1227 10:21:35.232201       6 udevprobe.go:202] device: /dev/sdc, Serial: 6000c29d5bf293acce965c73164314b3 filled during udev scan
I1227 10:21:35.232207       6 udevprobe.go:214] device: /dev/sdc, FileSystemUUID: 5Mh5Lq-G0lF-GE4O-BXBU-7M1r-Y774-sM9HsQ filled during udev scan
I1227 10:21:35.232504       6 udevprobe.go:231] Dependents of /dev/sdc : {Parent: Partitions:[] Holders:[/dev/dm-1] Slaves:[]}
I1227 10:21:35.232529       6 udevprobe.go:241] Device: /dev/sdc is of type: disk
I1227 10:21:35.232735       6 udevprobe.go:198] device: /dev/sdd, WWN: 0x6000c292259fd19a filled during udev scan
I1227 10:21:35.232751       6 udevprobe.go:202] device: /dev/sdd, Serial: 6000c292259fd19a0e3221a2252b0914 filled during udev scan
I1227 10:21:35.232756       6 udevprobe.go:214] device: /dev/sdd, FileSystemUUID: 6wqLMr-TFd4-P2bK-B5O5-8jYg-TJLG-2ua4sf filled during udev scan
I1227 10:21:35.233100       6 udevprobe.go:231] Dependents of /dev/sdd : {Parent: Partitions:[] Holders:[/dev/dm-0] Slaves:[]}
I1227 10:21:35.233121       6 udevprobe.go:241] Device: /dev/sdd is of type: disk
I1227 10:21:35.233333       6 udevprobe.go:198] device: /dev/sde, WWN: 0x6000c2960743056a filled during udev scan
I1227 10:21:35.233349       6 udevprobe.go:202] device: /dev/sde, Serial: 6000c2960743056aeb1a84ec803820c9 filled during udev scan
I1227 10:21:35.233357       6 udevprobe.go:214] device: /dev/sde, FileSystemUUID: 4d43e29e-5938-4baf-9371-1e510fd88d95 filled during udev scan
I1227 10:21:35.233727       6 udevprobe.go:231] Dependents of /dev/sde : {Parent: Partitions:[] Holders:[/dev/dm-20] Slaves:[]}
I1227 10:21:35.233749       6 udevprobe.go:241] Device: /dev/sde is of type: disk
I1227 10:21:35.233903       6 udevprobe.go:214] device: /dev/dm-0, FileSystemUUID: ac402ab0-f28c-4e07-a3e1-975163c7c5ce filled during udev scan
I1227 10:21:35.234204       6 udevprobe.go:231] Dependents of /dev/dm-0 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/sdd]}
I1227 10:21:35.234298       6 udevprobe.go:241] Device: /dev/dm-0 is of type: lvm
I1227 10:21:35.234461       6 udevprobe.go:214] device: /dev/dm-1, FileSystemUUID: a7575c32-fdf2-4708-9b49-386e4c3cf4de filled during udev scan
I1227 10:21:35.234691       6 udevprobe.go:231] Dependents of /dev/dm-1 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/sdc]}
I1227 10:21:35.234745       6 udevprobe.go:241] Device: /dev/dm-1 is of type: lvm
I1227 10:21:35.234887       6 udevprobe.go:214] device: /dev/dm-10, FileSystemUUID: d0d8059d-68a2-4997-917c-06a9e7c60914 filled during udev scan
I1227 10:21:35.235111       6 udevprobe.go:231] Dependents of /dev/dm-10 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/dm-4]}
I1227 10:21:35.235163       6 udevprobe.go:241] Device: /dev/dm-10 is of type:
I1227 10:21:35.235310       6 udevprobe.go:214] device: /dev/dm-11, FileSystemUUID: d0d8059d-68a2-4997-917c-06a9e7c60914 filled during udev scan
I1227 10:21:35.235543       6 udevprobe.go:231] Dependents of /dev/dm-11 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/dm-4]}
I1227 10:21:35.235605       6 udevprobe.go:241] Device: /dev/dm-11 is of type:
I1227 10:21:35.235741       6 udevprobe.go:214] device: /dev/dm-12, FileSystemUUID: d0d8059d-68a2-4997-917c-06a9e7c60914 filled during udev scan
I1227 10:21:35.235955       6 udevprobe.go:231] Dependents of /dev/dm-12 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/dm-4]}
I1227 10:21:35.236003       6 udevprobe.go:241] Device: /dev/dm-12 is of type:
I1227 10:21:35.236132       6 udevprobe.go:214] device: /dev/dm-13, FileSystemUUID: d0d8059d-68a2-4997-917c-06a9e7c60914 filled during udev scan
I1227 10:21:35.236396       6 udevprobe.go:231] Dependents of /dev/dm-13 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/dm-4]}
I1227 10:21:35.236448       6 udevprobe.go:241] Device: /dev/dm-13 is of type:
I1227 10:21:35.236594       6 udevprobe.go:214] device: /dev/dm-14, FileSystemUUID: d0d8059d-68a2-4997-917c-06a9e7c60914 filled during udev scan
I1227 10:21:35.236815       6 udevprobe.go:231] Dependents of /dev/dm-14 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/dm-4]}
I1227 10:21:35.236902       6 udevprobe.go:241] Device: /dev/dm-14 is of type:
I1227 10:21:35.237041       6 udevprobe.go:214] device: /dev/dm-15, FileSystemUUID: d0d8059d-68a2-4997-917c-06a9e7c60914 filled during udev scan
I1227 10:21:35.237295       6 udevprobe.go:231] Dependents of /dev/dm-15 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/dm-4]}
I1227 10:21:35.237361       6 udevprobe.go:241] Device: /dev/dm-15 is of type:
I1227 10:21:35.237545       6 udevprobe.go:214] device: /dev/dm-16, FileSystemUUID: d0d8059d-68a2-4997-917c-06a9e7c60914 filled during udev scan
I1227 10:21:35.237829       6 udevprobe.go:231] Dependents of /dev/dm-16 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/dm-4]}
I1227 10:21:35.237908       6 udevprobe.go:241] Device: /dev/dm-16 is of type:
I1227 10:21:35.238110       6 udevprobe.go:214] device: /dev/dm-17, FileSystemUUID: d0d8059d-68a2-4997-917c-06a9e7c60914 filled during udev scan
I1227 10:21:35.238618       6 udevprobe.go:231] Dependents of /dev/dm-17 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/dm-4]}
I1227 10:21:35.238775       6 udevprobe.go:241] Device: /dev/dm-17 is of type:
I1227 10:21:35.238990       6 udevprobe.go:214] device: /dev/dm-18, FileSystemUUID: d0d8059d-68a2-4997-917c-06a9e7c60914 filled during udev scan
I1227 10:21:35.239663       6 udevprobe.go:231] Dependents of /dev/dm-18 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/dm-4]}
I1227 10:21:35.239728       6 udevprobe.go:241] Device: /dev/dm-18 is of type:
I1227 10:21:35.239886       6 udevprobe.go:214] device: /dev/dm-19, FileSystemUUID: d0d8059d-68a2-4997-917c-06a9e7c60914 filled during udev scan
I1227 10:21:35.240123       6 udevprobe.go:231] Dependents of /dev/dm-19 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/dm-4]}
I1227 10:21:35.240174       6 udevprobe.go:241] Device: /dev/dm-19 is of type:
I1227 10:21:35.240561       6 udevprobe.go:231] Dependents of /dev/dm-2 : {Parent: Partitions:[] Holders:[/dev/dm-4] Slaves:[/dev/sdb]}
I1227 10:21:35.240626       6 udevprobe.go:241] Device: /dev/dm-2 is of type: lvm
I1227 10:21:35.241079       6 udevprobe.go:231] Dependents of /dev/dm-20 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/sde]}
I1227 10:21:35.241139       6 udevprobe.go:241] Device: /dev/dm-20 is of type: crypt
I1227 10:21:35.241345       6 udevprobe.go:214] device: /dev/dm-21, FileSystemUUID: d0d8059d-68a2-4997-917c-06a9e7c60914 filled during udev scan
I1227 10:21:35.241669       6 udevprobe.go:231] Dependents of /dev/dm-21 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/dm-4]}
I1227 10:21:35.241731       6 udevprobe.go:241] Device: /dev/dm-21 is of type:
I1227 10:21:35.241886       6 udevprobe.go:214] device: /dev/dm-22, FileSystemUUID: d0d8059d-68a2-4997-917c-06a9e7c60914 filled during udev scan
I1227 10:21:35.242120       6 udevprobe.go:231] Dependents of /dev/dm-22 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/dm-4]}
I1227 10:21:35.242172       6 udevprobe.go:241] Device: /dev/dm-22 is of type:
I1227 10:21:35.242325       6 udevprobe.go:214] device: /dev/dm-23, FileSystemUUID: d0d8059d-68a2-4997-917c-06a9e7c60914 filled during udev scan
I1227 10:21:35.242584       6 udevprobe.go:231] Dependents of /dev/dm-23 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/dm-4]}
I1227 10:21:35.242636       6 udevprobe.go:241] Device: /dev/dm-23 is of type:
I1227 10:21:35.242773       6 udevprobe.go:214] device: /dev/dm-24, FileSystemUUID: d0d8059d-68a2-4997-917c-06a9e7c60914 filled during udev scan
I1227 10:21:35.242985       6 udevprobe.go:231] Dependents of /dev/dm-24 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/dm-4]}
I1227 10:21:35.243036       6 udevprobe.go:241] Device: /dev/dm-24 is of type:
I1227 10:21:35.243169       6 udevprobe.go:214] device: /dev/dm-25, FileSystemUUID: d0d8059d-68a2-4997-917c-06a9e7c60914 filled during udev scan
I1227 10:21:35.243393       6 udevprobe.go:231] Dependents of /dev/dm-25 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/dm-4]}
I1227 10:21:35.243441       6 udevprobe.go:241] Device: /dev/dm-25 is of type:
I1227 10:21:35.243794       6 udevprobe.go:231] Dependents of /dev/dm-3 : {Parent: Partitions:[] Holders:[/dev/dm-4] Slaves:[/dev/sdb]}
I1227 10:21:35.243844       6 udevprobe.go:241] Device: /dev/dm-3 is of type: lvm
I1227 10:21:35.243983       6 udevprobe.go:214] device: /dev/dm-31, FileSystemUUID: d0d8059d-68a2-4997-917c-06a9e7c60914 filled during udev scan
I1227 10:21:35.244194       6 udevprobe.go:231] Dependents of /dev/dm-31 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/dm-4]}
I1227 10:21:35.244250       6 udevprobe.go:241] Device: /dev/dm-31 is of type:
I1227 10:21:35.244382       6 udevprobe.go:214] device: /dev/dm-32, FileSystemUUID: d0d8059d-68a2-4997-917c-06a9e7c60914 filled during udev scan
I1227 10:21:35.244612       6 udevprobe.go:231] Dependents of /dev/dm-32 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/dm-4]}
I1227 10:21:35.244660       6 udevprobe.go:241] Device: /dev/dm-32 is of type:
I1227 10:21:35.244809       6 udevprobe.go:214] device: /dev/dm-33, FileSystemUUID: d0d8059d-68a2-4997-917c-06a9e7c60914 filled during udev scan
I1227 10:21:35.245018       6 udevprobe.go:231] Dependents of /dev/dm-33 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/dm-4]}
I1227 10:21:35.245082       6 udevprobe.go:241] Device: /dev/dm-33 is of type:
I1227 10:21:35.245226       6 udevprobe.go:214] device: /dev/dm-34, FileSystemUUID: d0d8059d-68a2-4997-917c-06a9e7c60914 filled during udev scan
I1227 10:21:35.245565       6 udevprobe.go:231] Dependents of /dev/dm-34 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/dm-4]}
I1227 10:21:35.245641       6 udevprobe.go:241] Device: /dev/dm-34 is of type:
I1227 10:21:35.245896       6 udevprobe.go:214] device: /dev/dm-35, FileSystemUUID: d0d8059d-68a2-4997-917c-06a9e7c60914 filled during udev scan
I1227 10:21:35.246202       6 udevprobe.go:231] Dependents of /dev/dm-35 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/dm-4]}
I1227 10:21:35.246279       6 udevprobe.go:241] Device: /dev/dm-35 is of type:
I1227 10:21:35.246455       6 udevprobe.go:214] device: /dev/dm-36, FileSystemUUID: d0d8059d-68a2-4997-917c-06a9e7c60914 filled during udev scan
I1227 10:21:35.246767       6 udevprobe.go:231] Dependents of /dev/dm-36 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/dm-4]}
I1227 10:21:35.246819       6 udevprobe.go:241] Device: /dev/dm-36 is of type:
I1227 10:21:35.246999       6 udevprobe.go:214] device: /dev/dm-37, FileSystemUUID: d0d8059d-68a2-4997-917c-06a9e7c60914 filled during udev scan
I1227 10:21:35.247217       6 udevprobe.go:231] Dependents of /dev/dm-37 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/dm-4]}
I1227 10:21:35.247276       6 udevprobe.go:241] Device: /dev/dm-37 is of type:
I1227 10:21:35.247431       6 udevprobe.go:214] device: /dev/dm-38, FileSystemUUID: d0d8059d-68a2-4997-917c-06a9e7c60914 filled during udev scan
I1227 10:21:35.247664       6 udevprobe.go:231] Dependents of /dev/dm-38 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/dm-4]}
I1227 10:21:35.247720       6 udevprobe.go:241] Device: /dev/dm-38 is of type:
I1227 10:21:35.248250       6 udevprobe.go:231] Dependents of /dev/dm-4 : {Parent: Partitions:[] Holders:[/dev/dm-10 /dev/dm-11 /dev/dm-12 /dev/dm-13 /dev/dm-14 /dev/dm-15 /dev/dm-16 /dev/dm-17 /dev/dm-18 /dev/dm-19 /dev/dm-21 /dev/dm-22 /dev/dm-23 /dev/dm-24 /dev/dm-25 /dev/dm-31 /dev/dm-32 /dev/dm-33 /dev/dm-34 /dev/dm-35 /dev/dm-36 /dev/dm-37 /dev/dm-38 /dev/dm-5 /dev/dm-6 /dev/dm-7 /dev/dm-8 /dev/dm-9] Slaves:[/dev/dm-2 /dev/dm-3]}
I1227 10:21:35.248315       6 udevprobe.go:241] Device: /dev/dm-4 is of type: lvm
I1227 10:21:35.248455       6 udevprobe.go:214] device: /dev/dm-5, FileSystemUUID: d0d8059d-68a2-4997-917c-06a9e7c60914 filled during udev scan
I1227 10:21:35.248677       6 udevprobe.go:231] Dependents of /dev/dm-5 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/dm-4]}
I1227 10:21:35.248725       6 udevprobe.go:241] Device: /dev/dm-5 is of type:
I1227 10:21:35.248867       6 udevprobe.go:214] device: /dev/dm-6, FileSystemUUID: d0d8059d-68a2-4997-917c-06a9e7c60914 filled during udev scan
I1227 10:21:35.249084       6 udevprobe.go:231] Dependents of /dev/dm-6 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/dm-4]}
I1227 10:21:35.249133       6 udevprobe.go:241] Device: /dev/dm-6 is of type:
I1227 10:21:35.249296       6 udevprobe.go:214] device: /dev/dm-7, FileSystemUUID: d0d8059d-68a2-4997-917c-06a9e7c60914 filled during udev scan
I1227 10:21:35.249518       6 udevprobe.go:231] Dependents of /dev/dm-7 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/dm-4]}
I1227 10:21:35.249573       6 udevprobe.go:241] Device: /dev/dm-7 is of type:
I1227 10:21:35.249719       6 udevprobe.go:214] device: /dev/dm-8, FileSystemUUID: d0d8059d-68a2-4997-917c-06a9e7c60914 filled during udev scan
I1227 10:21:35.249974       6 udevprobe.go:231] Dependents of /dev/dm-8 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/dm-4]}
I1227 10:21:35.250030       6 udevprobe.go:241] Device: /dev/dm-8 is of type:
I1227 10:21:35.250197       6 udevprobe.go:214] device: /dev/dm-9, FileSystemUUID: d0d8059d-68a2-4997-917c-06a9e7c60914 filled during udev scan
I1227 10:21:35.250480       6 udevprobe.go:231] Dependents of /dev/dm-9 : {Parent: Partitions:[] Holders:[] Slaves:[/dev/dm-4]}
I1227 10:21:35.250544       6 udevprobe.go:241] Device: /dev/dm-9 is of type:
I1227 10:21:35.264870       6 blockdevicestore.go:130] eventcode=ndm.blockdevice.deactivate.success msg=Deactivated blockdevice rname=blockdevice-c6e873995091af193f8995e1fecbbfff
I1227 10:21:35.264935       6 probe.go:87] configured sysfs probe : state enable
I1227 10:21:35.264947       6 probe.go:87] configured used-by probe : state enable
I1227 10:21:35.264963       6 probe.go:87] configured Custom Tag Probe : state enable
I1227 10:21:35.265000       6 sparsefilegenerator.go:145] No sparse file path/size provided. Skip creating sparse files.
I1227 10:21:35.265084       6 controller.go:282] started the controller
.
.
.
I1227 07:34:42.927208       6 eventhandler.go:62] Processing details for /dev/dm-15
I1227 07:34:42.927497       6 probe.go:116] details filled by udev probe
I1227 07:34:42.927622       6 sysfsprobe.go:99] blockdevice path: /dev/dm-15 capacity :10737418240 filled by sysfs probe.
I1227 07:34:42.927703       6 sysfsprobe.go:128] blockdevice path: /dev/dm-15 logical block size :512 filled by sysfs probe.
I1227 07:34:42.927765       6 sysfsprobe.go:140] blockdevice path: /dev/dm-15 physical block size :512 filled by sysfs probe.
I1227 07:34:42.927829       6 sysfsprobe.go:152] blockdevice path: /dev/dm-15 hardware sector size :512 filled by sysfs probe.
I1227 07:34:42.927883       6 sysfsprobe.go:163] blockdevice path: /dev/dm-15 drive type :HDD filled by sysfs probe.
I1227 07:34:42.927898       6 probe.go:116] details filled by sysfs probe
E1227 07:34:42.927943       6 smartprobe.go:101] map[errorCheckingConditions:the device type is not supported yet, device type: "unknown"]
I1227 07:34:42.927959       6 probe.go:116] details filled by smart probe
I1227 07:34:42.928312       6 mountprobe.go:135] no mount point found for /dev/dm-15. clearing mount points if any
I1227 07:34:42.928331       6 probe.go:116] details filled by mount probe
I1227 07:34:42.928342       6 usedbyprobe.go:122] device: /dev/dm-15 is not having any zfs partitions
I1227 07:34:42.928389       6 probe.go:116] details filled by used-by probe
I1227 07:34:42.928397       6 probe.go:116] details filled by Custom Tag Probe
I1227 07:34:42.928403       6 addhandler.go:52] device: /dev/dm-15 does not exist in cache, the device is now connected to this node
I1227 07:34:42.928426       6 osdiskexcludefilter.go:131] applying os-filter regex ^/dev/sda[0-9]$ on /dev/dm-15
I1227 07:34:42.928469       6 osdiskexcludefilter.go:131] applying os-filter regex ^/dev/sda[0-9]$ on /dev/dm-15
I1227 07:34:42.928505       6 osdiskexcludefilter.go:131] applying os-filter regex ^/dev/dm-1(p[0-9]+)?$ on /dev/dm-15
I1227 07:34:42.928542       6 osdiskexcludefilter.go:131] applying os-filter regex ^/dev/dm-0(p[0-9]+)?$ on /dev/dm-15
I1227 07:34:42.928582       6 osdiskexcludefilter.go:131] applying os-filter regex ^/dev/dm-18(p[0-9]+)?$ on /dev/dm-15
I1227 07:34:42.928627       6 osdiskexcludefilter.go:131] applying os-filter regex ^/dev/sda[0-9]$ on /dev/dm-15
I1227 07:34:42.928657       6 filter.go:89] /dev/dm-15 ignored by path filter
I1227 07:34:42.928666       6 eventhandler.go:62] Processing details for /dev/dm-16
I1227 07:34:42.928935       6 probe.go:116] details filled by udev probe
I1227 07:34:42.929062       6 sysfsprobe.go:99] blockdevice path: /dev/dm-16 capacity :10737418240 filled by sysfs probe.
I1227 07:34:42.929130       6 sysfsprobe.go:128] blockdevice path: /dev/dm-16 logical block size :512 filled by sysfs probe.
I1227 07:34:42.929184       6 sysfsprobe.go:140] blockdevice path: /dev/dm-16 physical block size :512 filled by sysfs probe.
I1227 07:34:42.929234       6 sysfsprobe.go:152] blockdevice path: /dev/dm-16 hardware sector size :512 filled by sysfs probe.
I1227 07:34:42.929298       6 sysfsprobe.go:163] blockdevice path: /dev/dm-16 drive type :HDD filled by sysfs probe.
I1227 07:34:42.929314       6 probe.go:116] details filled by sysfs probe
E1227 07:34:42.929359       6 smartprobe.go:101] map[errorCheckingConditions:the device type is not supported yet, device type: "unknown"]
I1227 07:34:42.929382       6 probe.go:116] details filled by smart probe
I1227 07:34:42.929736       6 mountprobe.go:135] no mount point found for /dev/dm-16. clearing mount points if any
I1227 07:34:42.929752       6 probe.go:116] details filled by mount probe
I1227 07:34:42.929762       6 usedbyprobe.go:122] device: /dev/dm-16 is not having any zfs partitions
I1227 07:34:42.929818       6 probe.go:116] details filled by used-by probe
I1227 07:34:42.929834       6 probe.go:116] details filled by Custom Tag Probe
I1227 07:34:42.929842       6 addhandler.go:52] device: /dev/dm-16 does not exist in cache, the device is now connected to this node
I1227 07:34:42.929864       6 osdiskexcludefilter.go:131] applying os-filter regex ^/dev/sda[0-9]$ on /dev/dm-16
I1227 07:34:42.929899       6 osdiskexcludefilter.go:131] applying os-filter regex ^/dev/sda[0-9]$ on /dev/dm-16
I1227 07:34:42.929929       6 osdiskexcludefilter.go:131] applying os-filter regex ^/dev/dm-1(p[0-9]+)?$ on /dev/dm-16
I1227 07:34:42.929969       6 osdiskexcludefilter.go:131] applying os-filter regex ^/dev/dm-0(p[0-9]+)?$ on /dev/dm-16
I1227 07:34:42.930002       6 osdiskexcludefilter.go:131] applying os-filter regex ^/dev/dm-18(p[0-9]+)?$ on /dev/dm-16
I1227 07:34:42.930037       6 osdiskexcludefilter.go:131] applying os-filter regex ^/dev/sda[0-9]$ on /dev/dm-16
I1227 07:34:42.930075       6 eventhandler.go:75] Processed details for /dev/dm-16
I1227 07:34:42.930094       6 addhandler.go:105] checking if device: /dev/dm-16 can be uniquely identified
I1227 07:34:42.930103       6 uuid.go:84] device(/dev/dm-16) has a filesystem, using filesystem UUID: d0d8059d-68a2-4997-917c-06a9e7c60914
I1227 07:34:42.930113       6 uuid.go:91] generated uuid: blockdevice-77febe261d83b6d39cc957a8fbf5f2c9 for device: /dev/dm-16
I1227 07:34:42.930122       6 addhandler.go:129] uuid: blockdevice-77febe261d83b6d39cc957a8fbf5f2c9 has been generated for device: /dev/dm-16
I1227 07:34:42.930130       6 addhandler.go:46] device: /dev/dm-16 already exists in cache, the event was likely generated by a partition table re-read or a change in some of the devices was detected
E1227 07:34:42.933392       6 blockdevicestore.go:142] Unable to get blockdevice object : blockdevices.openebs.io "blockdevice-77febe261d83b6d39cc957a8fbf5f2c9" not found
I1227 07:34:42.933419       6 addhandler.go:135] device: /dev/dm-16, uuid: blockdevice-77febe261d83b6d39cc957a8fbf5f2c9 not found in etcd
I1227 07:34:42.933426       6 addhandler.go:259] creating block device resource for device: /dev/dm-16 with uuid: blockdevice-77febe261d83b6d39cc957a8fbf5f2c9
E1227 07:34:42.936313       6 blockdevicestore.go:51] eventcode=ndm.blockdevice.create.failure msg=Creation of blockdevice object failed : BlockDevice.openebs.io "blockdevice-77febe261d83b6d39cc957a8fbf5f2c9" is invalid: spec.details.deviceType: Unsupported value: "\n": supported values: "disk", "partition", "sparse", "loop", "lvm", "crypt", "dm", "mpath" rname=blockdevice-77febe261d83b6d39cc957a8fbf5f2c9
E1227 07:34:42.936335       6 addhandler.go:596] unable to push blockdevice-77febe261d83b6d39cc957a8fbf5f2c9 (/dev/dm-16) to etcd
E1227 07:34:42.936342       6 addhandler.go:269] BlockDevice.openebs.io "blockdevice-77febe261d83b6d39cc957a8fbf5f2c9" is invalid: spec.details.deviceType: Unsupported value: "\n": supported values: "disk", "partition", "sparse", "loop", "lvm", "crypt", "dm", "mpath"
E1227 07:34:42.936350       6 eventhandler.go:86] BlockDevice.openebs.io "blockdevice-77febe261d83b6d39cc957a8fbf5f2c9" is invalid: spec.details.deviceType: Unsupported value: "\n": supported values: "disk", "partition", "sparse", "loop", "lvm", "crypt", "dm", "mpath"
I1227 07:34:42.936358       6 eventhandler.go:62] Processing details for /dev/dm-17
I1227 07:34:42.936593       6 probe.go:116] details filled by udev probe
I1227 07:34:42.936689       6 sysfsprobe.go:99] blockdevice path: /dev/dm-17 capacity :10737418240 filled by sysfs probe.
I1227 07:34:42.936734       6 sysfsprobe.go:128] blockdevice path: /dev/dm-17 logical block size :512 filled by sysfs probe.
I1227 07:34:42.936772       6 sysfsprobe.go:140] blockdevice path: /dev/dm-17 physical block size :512 filled by sysfs probe.
I1227 07:34:42.936813       6 sysfsprobe.go:152] blockdevice path: /dev/dm-17 hardware sector size :512 filled by sysfs probe.
I1227 07:34:42.936854       6 sysfsprobe.go:163] blockdevice path: /dev/dm-17 drive type :HDD filled by sysfs probe.
I1227 07:34:42.936860       6 probe.go:116] details filled by sysfs probe
E1227 07:34:42.936894       6 smartprobe.go:101] map[errorCheckingConditions:the device type is not supported yet, device type: "unknown"]
I1227 07:34:42.936905       6 probe.go:116] details filled by smart probe
I1227 07:34:42.937194       6 mountprobe.go:135] no mount point found for /dev/dm-17. clearing mount points if any
I1227 07:34:42.937209       6 probe.go:116] details filled by mount probe
I1227 07:34:42.937217       6 usedbyprobe.go:122] device: /dev/dm-17 is not having any zfs partitions
I1227 07:34:42.937271       6 probe.go:116] details filled by used-by probe
I1227 07:34:42.937282       6 probe.go:116] details filled by Custom Tag Probe
I1227 07:34:42.937290       6 addhandler.go:52] device: /dev/dm-17 does not exist in cache, the device is now connected to this node
I1227 07:34:42.937314       6 osdiskexcludefilter.go:131] applying os-filter regex ^/dev/sda[0-9]$ on /dev/dm-17
I1227 07:34:42.937347       6 osdiskexcludefilter.go:131] applying os-filter regex ^/dev/sda[0-9]$ on /dev/dm-17
I1227 07:34:42.937366       6 osdiskexcludefilter.go:131] applying os-filter regex ^/dev/dm-1(p[0-9]+)?$ on /dev/dm-17
I1227 07:34:42.937392       6 osdiskexcludefilter.go:131] applying os-filter regex ^/dev/dm-0(p[0-9]+)?$ on /dev/dm-17
I1227 07:34:42.937420       6 osdiskexcludefilter.go:131] applying os-filter regex ^/dev/dm-18(p[0-9]+)?$ on /dev/dm-17
I1227 07:34:42.937441       6 osdiskexcludefilter.go:131] applying os-filter regex ^/dev/sda[0-9]*$ on /dev/dm-17
I1227 07:34:42.937484       6 filter.go:89] /dev/dm-17 ignored by path filter
NOTE: The ndm scans /path/docker/devicemapper/mnt/<id> even when it is excluded in os-disk-exclude-filter.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

**Configurations**
NDM Config MAP
`apiVersion: v1
data:
  node-disk-manager.config: |
    probeconfigs:
      - key: udev-probe
        name: udev probe
        state: true
      - key: seachest-probe
        name: seachest probe
        state: false
      - key: smart-probe
        name: smart probe
        state: true
    filterconfigs:
      - key: os-disk-exclude-filter
        name: os disk exclude filter
        state: true
        exclude: "/,/etc/hosts,/boot,/path,/path/docker,/path/docker/devicemapper,/storage"
      - key: vendor-filter
        name: vendor filter
        state: true
        include: ""
        exclude: "CLOUDBYT,OpenEBS"
      - key: path-filter
        name: path filter
        state: true
        include: "/dev/dm-16,/dev/dm-20,/dev/dm-42"
        exclude: "loop,fd0,sr0,/dev/ram,/dev/md,/dev/rbd,/dev/zd,/dev/sda,/dev/sdb,/dev/sdc,/dev/sdd,/dev/sde"`

This can be solved in 2 ways,

either make os-disk-exclude filter support regex, so all the unwanted docker mountpoints can be excluded
see why the dm/uuid is not empty on the docker volumes which are given as device mappers, causing NDM to fail to detect the device type.

cc: @z0marlin @RealHarshThakur @kmova


Package request: TabbyAPI

Project description
A FastAPI based application that allows for generating text using an LLM (large language model) using the Exllamav2 backend.
Metadata

homepage URL: https://github.com/theroyallab/tabbyAPI
source URL: https://github.com/theroyallab/tabbyAPI
license: AGPL-3.0
platforms: windows & linux mentioned in docs, potentially darwin

Add a :+1: reaction to issues you find important.

I may attempt this when i find the time for it, i have already packaged exllamav2 for CUDA

Packaged tabbyapi in my own repo temporarily, seems to work. Will look into creating a PR for nixpkgs in the coming days


Split posminting

This PR is for Francois eyes only, I would like to re-do it when my other PR called stake-vulnerability has gone in, unless someone else is OK to put it in


docker volume inspect --help does not contain --help option

In current master:
$ docker volume inspect --help

Usage:  docker volume inspect [OPTIONS] [VOLUME NAME]

Return low-level information on a volume

  -f, --format=      Format the output using the given go template.

There is no --help=false       Print usage line. --help is available, though.
The other subcommands of docker volume are correct in this regard.
$ docker --version
Docker version 1.9.0-dev, build 3a539c6

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

Thanks @albers! Do you want to create a PR yourself, or want someone else to pick this up?
/cc @cpuguy83

@thaJeztah I already tried to fix it but failed. --help has some special treatment, and I really don't understand why it doesn't appear in this specific command.

No worries, @albers! I'm sure there's a maintainer that can pick it up; I wanted to check first if you weren't working on it already :+1:

I got it - the flag stuff is kind of funky

I'm looking forward to the solution of that puzzle.

Here's the diff of the fix - creating the testcase to make sure we don't break again is actually the hard part...
diff --git a/api/client/volume.go b/api/client/volume.go
index ccb0188..d320259 100644
--- a/api/client/volume.go
+++ b/api/client/volume.go
@@ -104,13 +104,14 @@ func (cli *DockerCli) CmdVolumeLs(args ...string) error {
 func (cli *DockerCli) CmdVolumeInspect(args ...string) error {
        cmd := Cli.Subcmd("volume inspect", []string{"[VOLUME NAME]"}, "Return l
        tmplStr := cmd.String([]string{"f", "-format"}, "", "Format the output u
-       if err := cmd.Parse(args); err != nil {
-               return nil
-       }

        cmd.Require(flag.Min, 1)
        cmd.ParseFlags(args, true)

+       if err := cmd.Parse(args); err != nil {
+               return nil
+       }
+
        var tmpl *template.Template
        if *tmplStr != "" {
                var err error

PR#16158


Update 'build SMTP email' link

Description of the change: update 'build SMTP email' link
Reason for the change: 404 page not found error
Link to original source: https://sendgrid.com/docs/for-developers/sending-email/building-an-smtp-email/

Closes #

Hello @cemurray,Thanks again for the PR! We appreciate your contribution and look forward to                                              continued collaboration. Thanks!                                             Team SendGrid DX


Unable to access the tinymce object

Hi,
I'm fairly new to TinyMCE and to using it in Svelte, but it I cannot find a way to access tinymce using this wrapper. What I am trying to do is build a plugin as per this blog.
In the blog they reference the script library tinymce in the header, but this Svelte wrapper does not expose that in

hey @deshartman , the svelte wrapper will just create an instance of the TinyMCE editor. When creating a new instance, the wrapper will try to find the global TinyMCE object (tinymce), if it can't find that it will fall back to downloading a new tinymce script and creating a global tinymce object. Your console log is not showing anything because at mount there is no global tinymce instance.
An easy way to sort this out is by copying your tinymce folder to your public folder and importing your own tinymce script in the index.html entry point of your app to ensure that editor instances will have access to a global tinymce object. By loading the tinymce script in your index you'll have access to the PluginManager.
Finally, in your <Editor {conf} /> component you can use the plugin you added via the PluginManager
Hope this helps

@jscasca Thank you for coming back to me. I have done what you suggested and tinymce is now available on mount.
I also imported the local tinymce in App.svelte

Hello Tiny

  <Editor />

Although the onMount is fine, it did not display and had errors:

I would like to still clarify if there is a better way to do this? As I understand it, if you pass in a value for "scriptSrc" on Editor, it picks up the local copy on tinymce, so why can this not be exposed, rather than relying on index.html script? could you expose the tinymce in Editor like this? Just seems like a neat way to do it all in Svelte, rather than fiddling with header scripts.

Hello Tiny

  <Editor scriptSrc="tinymce/tinymce.min.js" />

If you choose to go the import route you'll have more headaches than it's worth. I rather recommend the index approach.
If you go the import route, you'll have to bundle all its libraries. That means all the plugins, skins, themes, and the sort. Otherwise it will complain about not finding the resources (as your screenshot).
The tinymce-svelte does expose the tinymce object but only after it has been initialised. The reason for this is that you don't know at what point the svelte app will create the component. With this in mind you should be able to create the plugin for your instance during the setup of the editor (I'll try to create a sample for this during the weekend).
The scriptSrc property is used to select where to download a tinymce script in case there is no tinymce object available at runtime. So basically it goes like this: is there a tinymce object? Then load it, otherwise: do you have a script src? Then download from it, otherwise download from the default cdn

Perfect, thanks. Looking forward to the example. Just trying to get my head around this ;-)

Hello @jscasca, this is very timely for me as well - I look forward to your example!
In my case, I'd like to enable svelte-based inline-editing as per the example at https://www.tiny.cloud/docs/general-configuration-guide/use-tinymce-inline/
Those examples all depend on calling  tinymce.init(someConfig);  which I can't figure out how to do when using the svelte Editor component.  (I am importing the tinymce code via the Editor's  scriptSrc="/tinymce/tinymce.min.js" from my public directory, which works fine for the regular iFrame mode.)

@deshartman  I made a quick sample of how to add a plugin in the setup phase of the wrapper. As I was mentioning before, the wrapper will look for TinyMCE instances and if it can;t find one it will download a new tinymce script from the scriptSrc or from the Tiny CDN by default. After downloading the tinymce script, you will have the tinymce object available before the editor is created.

Hello {name}!

Visit the Svelte tutorial to learn how to build Svelte apps.

  <Editor {conf} />

Following is an inline editor

  <Editor {inline} bind:value={editorValue} cssClass={"inlineEditor"} conf={secondConf}/>

{@html editorValue}

@dmccallie there are multiple ways to get an inline editor. The closest thing to running init would be using the conf property as it takes an initialization object the same way the pure editor would. However, the wrapper comes with an auxiliary inline property that you can use instead. I made an inline editor in the same example using let inline = true; and then <Editor {inline} /> but you can do <Editor inline={true} /> just the same way. This should be documented here: https://www.tiny.cloud/docs/integrations/svelte/#exampleusinginline
Hope this helps

@jscasca thank you so much for making the time to explain this and build the example. I can see now how this works.


feat(client, cli): dynamic prisma:// urls engine loading

This PR brings the removal --data-proxy and enables the handling of prisma:// URLs to happen dynamically instead.
closes https://github.com/prisma/team-orm/issues/284
closes https://github.com/prisma/prisma/issues/12734
closes https://github.com/prisma/prisma/pull/18128
closes https://github.com/prisma/prisma/issues/13608
closes https://github.com/prisma/team-orm/issues/285
closes https://github.com/prisma/team-orm/issues/292
closes https://github.com/prisma/team-orm/issues/286
closes https://github.com/prisma/team-orm/issues/291
closes https://github.com/prisma/team-orm/issues/290
closes https://github.com/prisma/team-orm/issues/289
closes https://github.com/prisma/prisma/issues/17796
closes https://github.com/prisma/team-orm/issues/266
closes https://github.com/prisma/team-orm/issues/288
closes https://github.com/prisma/team-orm/issues/287
/integration

The ecosystem-tests run can be seen here. As you can see, we have some tests failing which are related to:

File changes: We are creating more files by default
Engine not being detected due to the removal of _clientEngineType

So nothing is fundamentally broken, just some assertions need to be updated.

ci test all

After ci test all It looks like it fails on a few binary runs 🤔

Change in public package, removed data-proxy.js & data-proxy.d.ts see
Before

After


fix: line charts colors too quickly choose similar colors

Overview
Currently when trends are added to a widget, the colors cycle towards similar colors quicker than desired. Changed the getDefaultColor function to offset color selection by 1 so colors don't repeat.
Verifying Changes
https://github.com/awslabs/iot-app-kit/assets/145582655/7e364c13-8ebc-4466-bbdc-c2829ce77271
Legal
This project is available under the Apache 2.0 License.

In the verification video I noticed the green unmodelled data stream didn't show up on the chart, is that intended?

Seems to be a bug in general. Just testing in RC and none of the modeled data streams are showing up on the line chart.


Fix decoding from file-like object reading too much data (#9)

Changes

Decoder uses buffer if seeking possible, minimal reads otherwise
Encoder/decoder buffers now unset/NULL after freeing (ext)
Added test cases for successful and failing post-decode seek calls (ext)

Testing
Versions

Python 3.6.7 64-bit (Ubuntu 18.04, macOS 10.14.4)
Python 2.7.15 64-bit (Ubuntu 18.04)
Python 3.7.3 64-bit (Windows 10)

What

C-extenions builds (with/without extra GCC flags as per setup.py where applicable)
Unit tests in pure Python & C-extension

suite now exercises both in one run
additional tests to cover this issue

Reference leak testing using pympler
Performance tests as per #9
Coverage tests (including for C extension)

Have fixed the comment typo(s).


resample methods in to_model_ds

When modelling a large area it can be necessary to coarsen the grid beyond the default 100 m resolution dictated by the REGIS dataset. The method to_model_ds uses resample.ds_to_structured_grid, using nearest neighbour interpolation by default (the argument is not set).
I think it would be useful to have other scaling methods for the hydraulic conductances, such as the mean and harmonic mean. Have you considered to implement these in nlmod?

I agree that it would be nice to have this in nlmod. We have not yet implemented this. If you use the update_ds_from_layer_ds function there are more resampling methods than just nearest neighbor  (example here: https://nlmod.readthedocs.io/en/stable/examples/12_layer_generation.html).
However the harmonic mean is not one of them. For geotop we use the arithmetic weighted mean for kh and a harmonic eighted mean for kv by default. So it would be nice to implement this logic for scaling in the update_ds_from_layer_ds function.


gitea: using remote postgres server does not work

Describe the bug
I've installed a gitea server with the following settings among other things, which I expected would use my remotely configured postgresql server. However, the database.host setting seems to be ignored and has installed a local postgresql server instead, and gitea is using that instead of using the remote server.
Maybe there is something else that needs to be set before I can use the remote server, but it is unclear to me what that should be.
Settings:
services.gitea = {
  enable = true;
  appName = "Toot toot Gitea";
  database = {
    host = "postgresql.localdomain";
    type = "postgres";
    passwordFile = config.age.secrets.giteadbpw.path;
  };
  stateDir = "/keep/gitea";
  settings = {
    database = {
      LOG_SQL = false;
    };

Notify maintainers
🍀 @srhb @Ma27 @theHedgehog0 🍀
Much thanks,
-voidzero

You have not disabled creating a local database instance, which can be done by setting services.gitea.database.createDatabase to false. Please add this to your configuration and retry!

Ahh, that works. Fantastic. Thanks!


Support CUDA surfaces

Textures are read only, but surfaces are writable

Looks like these are not supported yet, from looking into code.

Not currently supported, will leave this open as we mature the HIP Texture support.  Can you share more on your use case?

Thanks. So, use case is porting an OpenCL image compression program to HIP. I need a HIP equivalent
of an OpenCL image that can be either read from or written to.  So, I would need a HIP surface to do this.
My OpenCL program makes heavy use of OpenCL images, to improve caching performance.

When may we expect support for surfaces ?  It's quite important for image processing applications.

So, I can now use full OpenCL image features on ROCm.  It is working really well with latest release.
We need an equivalent feature for HIP, i.e. surfaces.

@bensander I see a lot of commit activity relating to textures. Are you able to give us an update on when you guys will tackle surfaces ?
Thanks so much,
Aaron

We are getting closer!  @gargrahul is scoping this feature now.

Great! Thanks for the update.

it looks like this is now supported :) closing


test out uglify for minifying js

Webpack still in the works, but we are going to try to simple paste all of the js files into one big one, then run uglify (see https://www.rdocumentation.org/packages/js/versions/1.1/topics/uglify) and see if there are improvements to performance.
merge in separate branch and deploy on Jenkins to test performance

Test complete, and we are accepting. Went from about 4.7 seconds to 2.2/2.3 seconds for time to first paint. As jread mentioned in the Slack conversation:

wow, so 2 seconds of load time saved because we reduced the number of files being loaded...
yeah, and makes you wonder about the load cost of those 6 tiny svgs we are pulling in as external files vs embedding in the DOM (e.g., https://beta-owi.usgs.gov/vizlab/water-use-15/images/github.svg and others)

As a future task, we could look into having the tiny svgs be part of the page template, so that they are part of the DOM and not being loaded in as files.
On Alison's treo before (using East region networks):

On David's treo after (using West region networks):

Since we used different networks, David set it up using East network, too. It was very similar:


Updates to the PowerShell modules

[x] I have signed the Contributor License Agreement.
[x] This pull request is related to an issue
- fixes #4411
- fixes #4680

Microsoft Reviewers: Open in CodeFlow

edit by @denelon - formatting for checkboxes :)

FYI I could not build this small part locally at all getting this error no matter what I do to try and build it
error MSB4019: The imported project "C:\Microsoft.Cpp.Default.props" was not found.
Confirm that the expression in the Import declaration "\Microsoft.Cpp.Default.props" is correct, and that the file exists on disk.

I also was thinking that on push to this repo that a build would be automatically triggered, though looking at other pr's it's manually being kicked off using the /azp run mechanism (which I don't think I would be able to run)
Other than that this is ready to merge if a build completes no issue

/azp run

was worth a shot 🤷🏻♂

Just working on adding the additional bits needed for #4680 to get this all added in a single PR

@JohnMcPMS thanks for the comments, I'll get back to these during this week (hopefully tonight) as I have some updates on another device that was in progress at the end of the week.

@kilasuit thanks for jumping in here!
I think we'd want to make sure and update the appropriate "Help" files with the changes as well. Assuming this is all "non-breaking" changes, that can be a separate PR. I know we're also adding a new cmdlet for the WinGet Repair command.

So this should be good for merging now & thanks for the ping @denelon
Only other thoughts

[ ] Is the file name changes for the depluralised cmdlet files ok or does this need reverting
[ ] Is the change to the class name as per https://github.com/microsoft/winget-cli/pull/4716/commits/696bab0e0f0fec615bb49c9bf5c9b32c11b5281e ok?
[ ] Do you want this rebased with cleaner commit history at all or is it fine as is?

If the cmdlets have been renamed to singular, I'd say we should keep them plural unless the help files get included in the PR. Probably best to do the rename in a separate PR so the help files don't break or confuse users. Get-Help and Get-Command should stay in sync.
I'll let one of our engineers make the call on the remaining "other thoughts".

Thought it best to add all in together so I have updated the helpfiles in this PR - though I can easily remove those commits if desired

OK, we're cutting a build with the current cmdlets and help. As soon as that is out, we can dig back through this PR to get updates for all the changes. I really appreciate the help here!

Looking good to me; we need to fix some infrastructure issues and then we can run the build/test pass.

The following PR was just merged:

#4781

Those examples should be included here.

/azp run

The following PR was just merged:
* [Updates to PowerShell help docs #4781](https://github.com/microsoft/winget-cli/pull/4781)

Those examples should be included here.

I just rebased from the master branch & resolved the last comment so all good to go :-)

/azp run

/azp run

Build was successful with my changes.  @kilasuit, please sign off on the PR to indicate that you are done with changes and ready to merge.

Yeah all good with me @JohnMcPMS


Latest Chromium warns about canvas's willReadFrequently

Describe the bug
Getting a warning from latest Chromium:

Canvas2D: Multiple readback operations using getImageData are faster with the willReadFrequently attribute set to true. See: https://html.spec.whatwg.org/multipage/canvas.html#concept-canvas-will-read-frequently

https://github.com/openlayers/openlayers/blob/daf604b0a83e841d0ebbf9e79d7f6a7a18a540ce/src/ol/render/canvas/ExecutorGroup.js#L222-L228
To Reproduce
Steps to reproduce the behavior:

Go to https://openlayers.org/en/latest/examples/custom-hit-detection-renderer.html
Move the mouse over the map
See warning in console

Expected behavior
Maybe its worth investigating a performance gain here.
Also warns at this line:
https://github.com/openlayers/openlayers/blob/daf604b0a83e841d0ebbf9e79d7f6a7a18a540ce/src/ol/style/IconImage.js#L111

Same issue for me, nowhere to set canvas context parameter setting for method  createCanvasContext2D with:
const canvas = document.createElement(‘canvas’);
const ctx = canvas.getContext(‘2d’, {willReadFrequently: true});

I'm going to create a pull request to address this. We don't want to set willReadFrequently: true for all contexts we create. Only for those we use for hit detection and style symbols.


Modifying UserConfig to simplify user update and enforce lower case convert on user value

@billgib,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


[VEN-1065] Testnet Deployment

Description
This PR introduces the completely new testnet deployment of IL. The configuration consists of 2 Pools with 2 markets each:
Pool1:
vBNX
vWBNB
Pool2:
vCAKE
vWBTC
Resolves # [VEN-1065]
Checklist

[ ] I have updated the documentation to account for the changes in the code.
[ ] If I added new functionality, I added tests covering it.
[ ] If I fixed a bug, I added a test preventing this bug from silently reappearing again.
[ ] My contribution follows Venus contribution guidelines.

@gleiser-oliveira cannot answer on top of my head right now, but I think there is a task for that created in the backlog assigned to me ( VEN-1092 ) could you please check it and say if it reflects this problem? If not we ca create a task and assign it to me.

@0xlucian can we bring the typechain import fix into this so we merge this PR and generate a new package? https://github.com/VenusProtocol/isolated-pools/pull/172

The PR with typechain is already fixed, but I will rebase the branch and tiday hpefully we will have a new deployment, so this PR will contain the typechain fix as well


ImportError: Keras requires TensorFlow 2.2 or higher. Install TensorFlow via pip install tensorflow

MLPrimitives version: 0.2.5.dev0
Python version: 3.6
Operating System: Ubuntu

Description
Keras 2.4 is incompatible with tensorflow < 2.2, but mlprimitives requires tensorflow < 2 as well as Keras<3.
As a result, after Keras 2.4 was released, when using Keras-based primitives in MLPrimitives a dependency error is raised.
What I Did
Steps to reproduce the error: Install the latest version of mlprimitives and create an instance of any pipeline that uses Keras:
$ python
Python 3.6.9 (default, Apr 18 2020, 01:56:04)
[GCC 8.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from mlblocks import MLPipeline
>>> pipeline = MLPipeline('text.classification.lstm')
Exception caught building MLBlock keras.preprocessing.text.Tokenizer
Traceback (most recent call last):
  File "/home/xals/.virtualenvs/MLPrimitives.clean/lib/python3.6/site-packages/keras/__init__.py", line 3, in <module>
    from tensorflow.keras.layers.experimental.preprocessing import RandomRotation
ModuleNotFoundError: No module named 'tensorflow.keras.layers.experimental.preprocessing'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/xals/.virtualenvs/MLPrimitives.clean/lib/python3.6/site-packages/mlblocks/mlblock.py", line 20, in import_object
    parent = importlib.import_module(parent_name)
  File "/home/xals/.virtualenvs/MLPrimitives.clean/lib/python3.6/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 994, in _gcd_import
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 941, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "<frozen importlib._bootstrap>", line 994, in _gcd_import
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 941, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "<frozen importlib._bootstrap>", line 994, in _gcd_import
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/home/xals/.virtualenvs/MLPrimitives.clean/lib/python3.6/site-packages/keras/__init__.py", line 6, in <module>
    'Keras requires TensorFlow 2.2 or higher. '
ImportError: Keras requires TensorFlow 2.2 or higher. Install TensorFlow via `pip install tensorflow`

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/xals/.virtualenvs/MLPrimitives.clean/lib/python3.6/site-packages/keras/__init__.py", line 3, in <module>
    from tensorflow.keras.layers.experimental.preprocessing import RandomRotation
ModuleNotFoundError: No module named 'tensorflow.keras.layers.experimental.preprocessing'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/xals/.virtualenvs/MLPrimitives.clean/lib/python3.6/site-packages/mlblocks/mlpipeline.py", line 113, in _build_blocks
    block = MLBlock(primitive, **block_params)
  File "/home/xals/.virtualenvs/MLPrimitives.clean/lib/python3.6/site-packages/mlblocks/mlblock.py", line 164, in __init__
    self.primitive = import_object(self.metadata['primitive'])
  File "/home/xals/.virtualenvs/MLPrimitives.clean/lib/python3.6/site-packages/mlblocks/mlblock.py", line 23, in import_object
    grand_parent = importlib.import_module(grand_parent_name)
  File "/home/xals/.virtualenvs/MLPrimitives.clean/lib/python3.6/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 994, in _gcd_import
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 941, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "<frozen importlib._bootstrap>", line 994, in _gcd_import
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/home/xals/.virtualenvs/MLPrimitives.clean/lib/python3.6/site-packages/keras/__init__.py", line 6, in <module>
    'Keras requires TensorFlow 2.2 or higher. '
ImportError: Keras requires TensorFlow 2.2 or higher. Install TensorFlow via `pip install tensorflow`
Traceback (most recent call last):
  File "/home/xals/.virtualenvs/MLPrimitives.clean/lib/python3.6/site-packages/keras/__init__.py", line 3, in <module>
    from tensorflow.keras.layers.experimental.preprocessing import RandomRotation
ModuleNotFoundError: No module named 'tensorflow.keras.layers.experimental.preprocessing'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/xals/.virtualenvs/MLPrimitives.clean/lib/python3.6/site-packages/mlblocks/mlblock.py", line 20, in import_object
    parent = importlib.import_module(parent_name)
  File "/home/xals/.virtualenvs/MLPrimitives.clean/lib/python3.6/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 994, in _gcd_import
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 941, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "<frozen importlib._bootstrap>", line 994, in _gcd_import
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 941, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "<frozen importlib._bootstrap>", line 994, in _gcd_import
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/home/xals/.virtualenvs/MLPrimitives.clean/lib/python3.6/site-packages/keras/__init__.py", line 6, in <module>
    'Keras requires TensorFlow 2.2 or higher. '
ImportError: Keras requires TensorFlow 2.2 or higher. Install TensorFlow via `pip install tensorflow`

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/xals/.virtualenvs/MLPrimitives.clean/lib/python3.6/site-packages/keras/__init__.py", line 3, in <module>
    from tensorflow.keras.layers.experimental.preprocessing import RandomRotation
ModuleNotFoundError: No module named 'tensorflow.keras.layers.experimental.preprocessing'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/xals/.virtualenvs/MLPrimitives.clean/lib/python3.6/site-packages/mlblocks/mlpipeline.py", line 183, in __init__
    self.blocks = self._build_blocks()
  File "/home/xals/.virtualenvs/MLPrimitives.clean/lib/python3.6/site-packages/mlblocks/mlpipeline.py", line 113, in _build_blocks
    block = MLBlock(primitive, **block_params)
  File "/home/xals/.virtualenvs/MLPrimitives.clean/lib/python3.6/site-packages/mlblocks/mlblock.py", line 164, in __init__
    self.primitive = import_object(self.metadata['primitive'])
  File "/home/xals/.virtualenvs/MLPrimitives.clean/lib/python3.6/site-packages/mlblocks/mlblock.py", line 23, in import_object
    grand_parent = importlib.import_module(grand_parent_name)
  File "/home/xals/.virtualenvs/MLPrimitives.clean/lib/python3.6/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 994, in _gcd_import
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 941, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "<frozen importlib._bootstrap>", line 994, in _gcd_import
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/home/xals/.virtualenvs/MLPrimitives.clean/lib/python3.6/site-packages/keras/__init__.py", line 6, in <module>
    'Keras requires TensorFlow 2.2 or higher. '
ImportError: Keras requires TensorFlow 2.2 or higher. Install TensorFlow via `pip install tensorflow`

Solution
Either ensure tensorflow>2 support or cap Keras version to <2.4

To note, Keras is now the default API in TensorFlow 2.0 and above. Therefore, you should not need to import it separately. The version of Keras on my end at least is 2.3.0 (see below).
To upgrade TensorFlow to the latest version (and given you are using Python 3.6.9), you can upgrade TF in the terminal as follows:
pip3 install --upgrade tensorflow --user

My TF version is 2.2, and I was able to import tensorflow.keras.layers.experimental.preprocessing without any issues.
To check your TensorFlow version:
>>> import tensorflow as tf
>>> print(tf.__version__)
2.2.0

Additionally, the indicated version of Keras on my end under TF v2.2 is as follows:
>>> tf.keras.__version__
'2.3.0-tf'

Hope this helps.


Fixes related to open issues.

Summary

Adjust landing page for .NET Framework winforms.
Add tip about the DesignerSerializationVisibilityAttribute attribute.
Add MultiTrigger and MultiDataTrigger to WPF overview.
Fix some comments in a code snippet.
Add some spacing in get started table.
Add missing single quote character in XAML info and link to reference.
Change DesiredHeight to Height on XAML style.

Fixes #61
Fixes #27
Fixes #47
Fixes #62
Fixes #67
Fixes #83

Verified that the snippets5000 error is related to old snippet that I'm not going to port.


Add Official D Blog to menu

Is there any special sorting mechanism of the menu? Should I sort the links alphabetically?
Ping @JackStouffer @mdparker
Btw

the font-size for the menu on http://dlang.org/blog/ should be 15px and your menu seems to be outdated (e.g. #1303 is missing)
have you tried the blog on your phone yet? The D menu doesn't seem to be responsive anymore :/

The menu on the blog is up to date and is now 15px. Not sure yet where the problem is with the menu responsiveness, but working on it. Thanks, Seb!

Thanks, David. I'll dig into it. Or maybe @JackStouffer  can figure it out first.

@mdparker @JackStouffer again a bit off-topic, but I also have a few more nitpicks and ideas:

the fonts used seem a bit different - at least on dlang.org nearly everything is thin
how about adding to the li item "Community" the css class active?
instead of word press search box you could use the Dlang search bar (you might fix the menu shift with this)
there are currently two links to WordPress. Afaik it's not required to mention that, so in terms of hiding a bit that we use PHP, you might consider to remove that ;-)

the fonts used seem a bit different - at least on dlang.org nearly everything is thin

The headings are the same font, the body text is intentionally different, as to distinguish the body and the headers.

how about adding to the li item "Community" the css class active?

Simple enough.

instead of word press search box you could use the Dlang search bar (you might fix the menu shift with this)

Hmm, I think this could be possible. I could add a "only search the blog" dropdown.

there are currently two links to WordPress. Afaik it's not required to mention that, so in terms of hiding a bit that we use PHP, you might consider to remove that ;-)

you probably want to hide the login link too, it just makes script kiddies more aware of your backend

These are up to @mdparker

there are currently two links to WordPress. Afaik it's not required to mention that, so in terms of hiding a bit that we use PHP, you might consider to remove that ;-)

Ugh. The one in the footer wasn't supposed to be there. The function generating it was hiding the Copyright text I had there. That bit is sorted now. As for the one in the meta box...

you probably want to hide the login link too, it just makes script kiddies more aware of your backend

I honestly don't think it makes a difference. It's easy enough to see what we're running just by typeing in a WP specific URL. I always have the meta widget turned off on my personal blogs, simply because I don't allow multiple accounts. My initial thoughts here was that other people will eventually have accounts and so it will be convenient to have a log in link on the front page.
That said, there's no way to edit the Meta widget to remove the WP link without modifying the core Wordpress files. I looked into that when I first set the blog up. And now that you've mentioned it here, I realize I really don't like having the WP link there either. So, I've removed the meta box (log- in link and all, which I may add back in later) and replaced it with links to the RSS feeds.
@WalterBright  @andralex Is there anyway we can get the repo @JackStouffer created for the blog theme transferred to the dlang organization? I keep getting issues reported all over the place.

@WalterBright @andralex Is there anyway we can get the repo @JackStouffer created for the blog theme transferred to the dlang organization? I keep getting issues reported all over the place.

I created a news group thread for this.


Documentation for ConnectionConfig

It would be nice if there was some documentation around ConnectionConfig. While working with connectionDefinitions I only noticed that connectionFields was available by digging into the type definitions.

Sorry for the late reply.
We planning to move this library into graphql-js and use JSDoc comment we already have to generate documentation.
So this issue should resolve itself after we achieve this goal.