ndm pod pod are getting restarted due to 'invalid memory address or nil pointer dereference'.

Description

In openebs deployment, ndm pods were observed to be crashed due to 'invalid memory address or nil pointer dereference'

[root@master-1552853078 workload]# kubectl get pods -n openebs
NAME                                         READY     STATUS    RESTARTS   AGE
cstor-sparse-pool-6dsu-7666c6bfc9-ctlqv      2/2       Running   0          5h
cstor-sparse-pool-og1t-8dddd49fb-jkd5t       2/2       Running   0          5h
cstor-sparse-pool-v8bw-74c496879d-dqk52      2/2       Running   0          5h
maya-apiserver-68bbb44bd4-gr787              1/1       Running   0          5h
openebs-ndm-9jvcs                            1/1       Running   1          5h
openebs-ndm-ftt5z                            1/1       Running   0          5h
openebs-ndm-t5lqg                            1/1       Running   1          5h
openebs-provisioner-75bb89fbc9-bxvxt         1/1       Running   0          5h
openebs-snapshot-operator-546b6fc75d-9rllj   2/2       Running   0          5h

Steps to Reproduce

Deployed openebs 0.8.2-RC4 with ndm-v0.3.3.  Used quay.io/openebs/node-disk-manager-amd64:v0.3.3 image to create ndm containers.
Deployed an application consuming jiva based volumes.
In some time, two of the three ndm pods were observed to be restarted.

ndm previous pod logs:
[root@master-1552853078 workload]# kubectl logs openebs-ndm-t5lqg -n openebs -p
[entrypoint.sh] enabling core dump.
[entrypoint.sh] launching ndm process.
I0405 04:50:19.721348       8 controller.go:170] Disk CRD is available
I0405 04:50:19.721627       8 filter.go:58] registering filters
I0405 04:50:19.721706       8 filter.go:66] configured os disk exclude filter : state enable
I0405 04:50:19.723866       8 filter.go:66] configured vendor filter : state enable
I0405 04:50:19.723933       8 filter.go:66] configured path filter : state enable
I0405 04:50:19.723989       8 probe.go:61] registering probes
I0405 04:50:19.724064       8 probe.go:83] configured seachest probe : state enable
I0405 04:50:19.724101       8 probe.go:83] configured smart probe : state enable
I0405 04:50:19.724389       8 probe.go:83] configured udev probe : state enable
I0405 04:50:19.724719       8 udevprobe.go:196] starting udev probe listener
I0405 04:50:19.731767       8 udevprobe.go:154] Partition Data for disk-41faf01a244b9b5580bb84f289718822 : [{0x83 xfs}]
I0405 04:50:19.732476       8 udevprobe.go:154] Partition Data for disk-ae0369e9f8b897643f5c8d4e04bec22b : [{0x8e LVM2_member}]
I0405 04:50:19.738147       8 probe.go:83] configured capacity probe : state enable
I0405 04:50:19.738247       8 sparsefilegenerator.go:173] Sparse file already exists: 0-ndm-sparse.img
I0405 04:50:19.738302       8 sparsefilegenerator.go:225] Updating the Disk CR for Sparse Disk: sparse-f07034986caf1a7024046d320da29b57
I0405 04:50:19.738506       8 server.go:42] Starting HTTP server at http://localhost:9090/metrics for metrics.
I0405 04:50:19.741048       8 eventhandler.go:49] processing details for disk-c675f9ba8cb715d3eefaa25b739bb11e
I0405 04:50:19.741889       8 probe.go:107] details filled by udev probe
I0405 04:50:19.747324       8 diskstore.go:31] created disk object : sparse-f07034986caf1a7024046d320da29b57
I0405 04:50:19.747845       8 controller.go:200] started the controller
I0405 04:50:23.618480       8 seachestprobe.go:126] Disk: /dev/sr0 Capacity:0 filled by seachest.
I0405 04:50:23.618605       8 seachestprobe.go:136] Disk: /dev/sr0 Vendor:NECVMWar filled by seachest.
I0405 04:50:23.618644       8 seachestprobe.go:141] Disk: /dev/sr0 FirmwareRevision:1.00 filled by seachest.
I0405 04:50:23.618681       8 seachestprobe.go:146] Disk: /dev/sr0 LogicalSectorSize:0 filled by seachest.
I0405 04:50:23.618711       8 seachestprobe.go:151] Disk: /dev/sr0 PhysicalSectorSize:0 filled by seachest.
I0405 04:50:23.618734       8 seachestprobe.go:156] Disk: /dev/sr0 RotationRate:0 filled by seachest.
I0405 04:50:23.618761       8 seachestprobe.go:161] Disk: /dev/sr0 DriveType:Not Available filled by seachest.
I0405 04:50:23.618773       8 seachestprobe.go:166] Disk: /dev/sr0 TotalBytesRead:0 filled by seachest.
I0405 04:50:23.618785       8 seachestprobe.go:171] Disk: /dev/sr0 TotalBytesWritten:0 filled by seachest.
I0405 04:50:23.618797       8 seachestprobe.go:176] Disk: /dev/sr0 DeviceUtilizationRate:%!d(float64=0) filled by seachest.
I0405 04:50:23.618826       8 seachestprobe.go:181] Disk: /dev/sr0 PercentEnduranceUsed:%!d(float64=0) filled by seachest.
I0405 04:50:23.618839       8 seachestprobe.go:186] Disk: /dev/sr0 TemperatureDataValid:false filled by seachest.
I0405 04:50:23.618853       8 probe.go:107] details filled by seachest probe
E0405 04:50:23.618987       8 smartprobe.go:100] map[errorCheckingConditions:the device type is not supported yet, device type: "unknown"]
I0405 04:50:23.619027       8 probe.go:107] details filled by smart probe
I0405 04:50:23.619288       8 probe.go:107] details filled by capacity probe
I0405 04:50:23.619384       8 filter.go:87] disk-c675f9ba8cb715d3eefaa25b739bb11e ignored by path filter
I0405 04:50:23.619408       8 eventhandler.go:49] processing details for disk-17fcdc00d81c2c5b7104ba54b3355d39
I0405 04:50:23.619824       8 probe.go:107] details filled by udev probe
I0405 04:50:23.620936       8 seachestprobe.go:126] Disk: /dev/sda Capacity:107374181888 filled by seachest.
I0405 04:50:23.620971       8 seachestprobe.go:131] Disk: /dev/sda Serial: filled by seachest.
I0405 04:50:23.620986       8 seachestprobe.go:141] Disk: /dev/sda FirmwareRevision:1.0  filled by seachest.
I0405 04:50:23.621006       8 seachestprobe.go:146] Disk: /dev/sda LogicalSectorSize:512 filled by seachest.
I0405 04:50:23.621023       8 seachestprobe.go:151] Disk: /dev/sda PhysicalSectorSize:512 filled by seachest.
I0405 04:50:23.621034       8 seachestprobe.go:156] Disk: /dev/sda RotationRate:0 filled by seachest.
I0405 04:50:23.621044       8 seachestprobe.go:161] Disk: /dev/sda DriveType:Not Available filled by seachest.
I0405 04:50:23.621060       8 seachestprobe.go:166] Disk: /dev/sda TotalBytesRead:0 filled by seachest.
I0405 04:50:23.621073       8 seachestprobe.go:171] Disk: /dev/sda TotalBytesWritten:0 filled by seachest.
I0405 04:50:23.621087       8 seachestprobe.go:176] Disk: /dev/sda DeviceUtilizationRate:%!d(float64=0) filled by seachest.
I0405 04:50:23.621101       8 seachestprobe.go:181] Disk: /dev/sda PercentEnduranceUsed:%!d(float64=0) filled by seachest.
I0405 04:50:23.621113       8 seachestprobe.go:186] Disk: /dev/sda TemperatureDataValid:false filled by seachest.
I0405 04:50:23.621135       8 probe.go:107] details filled by seachest probe
I0405 04:50:23.621500       8 probe.go:107] details filled by smart probe
I0405 04:50:23.621528       8 probe.go:107] details filled by capacity probe
I0405 04:50:23.621543       8 filter.go:87] disk-17fcdc00d81c2c5b7104ba54b3355d39 ignored by os disk exclude filter
I0405 04:50:23.621556       8 eventhandler.go:49] processing details for disk-41faf01a244b9b5580bb84f289718822
I0405 04:50:23.621897       8 probe.go:107] details filled by udev probe
I0405 04:50:23.624362       8 seachestprobe.go:126] Disk: /dev/sda1 Capacity:107374181888 filled by seachest.
I0405 04:50:23.624430       8 seachestprobe.go:131] Disk: /dev/sda1 Serial: filled by seachest.
I0405 04:50:23.624462       8 seachestprobe.go:141] Disk: /dev/sda1 FirmwareRevision:1.0  filled by seachest.
I0405 04:50:23.624492       8 seachestprobe.go:146] Disk: /dev/sda1 LogicalSectorSize:512 filled by seachest.
I0405 04:50:23.624521       8 seachestprobe.go:151] Disk: /dev/sda1 PhysicalSectorSize:512 filled by seachest.
I0405 04:50:23.624555       8 seachestprobe.go:156] Disk: /dev/sda1 RotationRate:0 filled by seachest.
I0405 04:50:23.624618       8 seachestprobe.go:161] Disk: /dev/sda1 DriveType:Not Available filled by seachest.
I0405 04:50:23.624654       8 seachestprobe.go:166] Disk: /dev/sda1 TotalBytesRead:0 filled by seachest.
I0405 04:50:23.624692       8 seachestprobe.go:171] Disk: /dev/sda1 TotalBytesWritten:0 filled by seachest.
I0405 04:50:23.624728       8 seachestprobe.go:176] Disk: /dev/sda1 DeviceUtilizationRate:%!d(float64=0) filled by seachest.
I0405 04:50:23.624767       8 seachestprobe.go:181] Disk: /dev/sda1 PercentEnduranceUsed:%!d(float64=0) filled by seachest.
I0405 04:50:23.624803       8 seachestprobe.go:186] Disk: /dev/sda1 TemperatureDataValid:false filled by seachest.
I0405 04:50:23.624834       8 probe.go:107] details filled by seachest probe
I0405 04:50:23.625338       8 probe.go:107] details filled by smart probe
I0405 04:50:23.625380       8 probe.go:107] details filled by capacity probe
I0405 04:50:23.625418       8 eventhandler.go:55] processed data for disk-41faf01a244b9b5580bb84f289718822
I0405 04:50:23.625452       8 eventhandler.go:60] Skipping partition of already excluded disk disk-41faf01a244b9b5580bb84f289718822
I0405 04:50:23.625474       8 eventhandler.go:49] processing details for disk-ae0369e9f8b897643f5c8d4e04bec22b
I0405 04:50:23.626188       8 probe.go:107] details filled by udev probe
I0405 04:50:23.628268       8 seachestprobe.go:126] Disk: /dev/sda2 Capacity:107374181888 filled by seachest.
I0405 04:50:23.628476       8 seachestprobe.go:131] Disk: /dev/sda2 Serial: filled by seachest.
I0405 04:50:23.628528       8 seachestprobe.go:141] Disk: /dev/sda2 FirmwareRevision:1.0  filled by seachest.
I0405 04:50:23.628596       8 seachestprobe.go:146] Disk: /dev/sda2 LogicalSectorSize:512 filled by seachest.
I0405 04:50:23.628639       8 seachestprobe.go:151] Disk: /dev/sda2 PhysicalSectorSize:512 filled by seachest.
I0405 04:50:23.628669       8 seachestprobe.go:156] Disk: /dev/sda2 RotationRate:0 filled by seachest.
I0405 04:50:23.628708       8 seachestprobe.go:161] Disk: /dev/sda2 DriveType:Not Available filled by seachest.
I0405 04:50:23.628748       8 seachestprobe.go:166] Disk: /dev/sda2 TotalBytesRead:0 filled by seachest.
I0405 04:50:23.628783       8 seachestprobe.go:171] Disk: /dev/sda2 TotalBytesWritten:0 filled by seachest.
I0405 04:50:23.628815       8 seachestprobe.go:176] Disk: /dev/sda2 DeviceUtilizationRate:%!d(float64=0) filled by seachest.
I0405 04:50:23.628852       8 seachestprobe.go:181] Disk: /dev/sda2 PercentEnduranceUsed:%!d(float64=0) filled by seachest.
I0405 04:50:23.628887       8 seachestprobe.go:186] Disk: /dev/sda2 TemperatureDataValid:false filled by seachest.
I0405 04:50:23.628916       8 probe.go:107] details filled by seachest probe
I0405 04:50:23.629543       8 probe.go:107] details filled by smart probe
I0405 04:50:23.629627       8 probe.go:107] details filled by capacity probe
I0405 04:50:23.629682       8 eventhandler.go:55] processed data for disk-ae0369e9f8b897643f5c8d4e04bec22b
I0405 04:50:23.629713       8 eventhandler.go:60] Skipping partition of already excluded disk disk-ae0369e9f8b897643f5c8d4e04bec22b
I0405 04:50:23.629740       8 eventhandler.go:49] processing details for disk-9e9ffd2a25d387bf128d3ab8299dd414
	Vendor ID: NECVMWar
	Model Number: VMware IDE CDR10
	Serial Number:
	Firmware Revision: 1.00
	World Wide Name: Not Supported
	Drive Capacity (B/B): 0.00/0.00
	Temperature Data:
		Current Temperature (C): Not Reported
		Highest Temperature (C): Not Reported
		Lowest Temperature (C): Not Reported
	Power On Time: Not Reported
	Power On Hours: Not Reported
	MaxLBA: 0
	Native MaxLBA: Not Reported
	Logical Sector Size (B): 0
	Physical Sector Size (B): 0
	Sector Alignment: 0
	Rotation Rate (RPM): Not Reported
	Form Factor (inch): Not Reported
	Last DST information:
		Not supported
	Long Drive Self Test Time: Not Supported
	Interface speed:
		Not Reported
	Annualized Workload Rate (TB/yr): Not Reported
	Total Bytes Read (B): Not Reported
	Total Bytes Written (B): Not Reported
	Encryption Support: Not Supported
	Cache Size (MiB): Not Reported
	Read Look-Ahead: Not Supported
	Write Cache: Not Supported
	SMART Status: Unknown or Not Supported
	ATA Security Information: Not Supported
	Firmware Download Support: Full, Segmented
	Specifications Supported:
		SPC-3
	Features Supported:
		Power Conditions
	Vendor ID: VMware
	Model Number: Virtual disk
	Serial Number:
	Firmware Revision: 1.0
	World Wide Name: Not Supported
	Drive Capacity (GB/GiB): 107.37/100.00
	Temperature Data:
		Current Temperature (C): Not Reported
		Highest Temperature (C): Not Reported
		Lowest Temperature (C): Not Reported
	Power On Time: Not Reported
	Power On Hours: Not Reported
	MaxLBA: 209715199
	Native MaxLBA: Not Reported
	Logical Sector Size (B): 512
	Physical Sector Size (B): 512
	Sector Alignment: 0
	Rotation Rate (RPM): Not Reported
	Form Factor (inch): Not Reported
	Last DST information:
		Not supported
	Long Drive Self Test Time: Not Supported
	Interface speed:
		Max Speed (MB/s): 10.00 (FAST-10)
		Negotiated Speed (MB/s): Not Reported
	Annualized Workload Rate (TB/yr): Not Reported
I0405 04:50:23.630655       8 probe.go:107] details filled by udev probe
	Total Bytes Read (B): Not Reported
	Total Bytes Written (B): Not Reported
	Encryption Support: Not Supported
	Cache Size (MiB): Not Reported
	Read Look-Ahead: Not Supported
	Write Cache: Not Supported
	SMART Status: Unknown or Not Supported
	ATA Security Information: Not Supported
	Firmware Download Support: Full, Segmented
	Specifications Supported:
		SCSI-2
	Features Supported:
		None reported or an error occurred while trying to determine
		the features.

	Vendor ID: VMware
	Model Number: Virtual disk
	Serial Number:
	Firmware Revision: 1.0
	World Wide Name: Not Supported
	Drive Capacity (GB/GiB): 107.37/100.00
	Temperature Data:
		Current Temperature (C): Not Reported
		Highest Temperature (C): Not Reported
		Lowest Temperature (C): Not Reported
	Power On Time: Not Reported
	Power On Hours: Not Reported
	MaxLBA: 209715199
	Native MaxLBA: Not Reported
	Logical Sector Size (B): 512
	Physical Sector Size (B): 512
I0405 04:50:23.633514       8 seachestprobe.go:126] Disk: /dev/sdb Capacity:53687090688 filled by seachest.
I0405 04:50:23.633617       8 seachestprobe.go:131] Disk: /dev/sdb Serial: filled by seachest.
I0405 04:50:23.633653       8 seachestprobe.go:141] Disk: /dev/sdb FirmwareRevision:1.0  filled by seachest.
I0405 04:50:23.633691       8 seachestprobe.go:146] Disk: /dev/sdb LogicalSectorSize:512 filled by seachest.
I0405 04:50:23.633736       8 seachestprobe.go:151] Disk: /dev/sdb PhysicalSectorSize:512 filled by seachest.
I0405 04:50:23.633761       8 seachestprobe.go:156] Disk: /dev/sdb RotationRate:0 filled by seachest.
I0405 04:50:23.633784       8 seachestprobe.go:161] Disk: /dev/sdb DriveType:Not Available filled by seachest.
I0405 04:50:23.633811       8 seachestprobe.go:166] Disk: /dev/sdb TotalBytesRead:0 filled by seachest.
I0405 04:50:23.633839       8 seachestprobe.go:171] Disk: /dev/sdb TotalBytesWritten:0 filled by seachest.
I0405 04:50:23.633874       8 seachestprobe.go:176] Disk: /dev/sdb DeviceUtilizationRate:%!d(float64=0) filled by seachest.
I0405 04:50:23.633907       8 seachestprobe.go:181] Disk: /dev/sdb PercentEnduranceUsed:%!d(float64=0) filled by seachest.
I0405 04:50:23.633951       8 seachestprobe.go:186] Disk: /dev/sdb TemperatureDataValid:false filled by seachest.
I0405 04:50:23.633980       8 probe.go:107] details filled by seachest probe
I0405 04:50:23.634657       8 probe.go:107] details filled by smart probe
I0405 04:50:23.634712       8 probe.go:107] details filled by capacity probe
I0405 04:50:23.634756       8 eventhandler.go:55] processed data for disk-9e9ffd2a25d387bf128d3ab8299dd414
I0405 04:50:23.647213       8 diskstore.go:31] created disk object : disk-9e9ffd2a25d387bf128d3ab8299dd414
I0405 04:50:23.654892       8 eventhandler.go:49] processing details for disk-ba6a9954a38fbcd390583db68ee87af3
I0405 04:50:23.655485       8 probe.go:107] details filled by udev probe
SG_GET_VERSION_NUM: Invalid argument
I0405 04:50:23.655862       8 seachestprobe.go:116] Disk: /dev/fd0 Model: filled by seachest.
I0405 04:50:23.655925       8 seachestprobe.go:126] Disk: /dev/fd0 Capacity:0 filled by seachest.
I0405 04:50:23.655961       8 seachestprobe.go:131] Disk: /dev/fd0 Serial: filled by seachest.
I0405 04:50:23.655993       8 seachestprobe.go:136] Disk: /dev/fd0 Vendor: filled by seachest.
I0405 04:50:23.656048       8 seachestprobe.go:141] Disk: /dev/fd0 FirmwareRevision: filled by seachest.
I0405 04:50:23.656100       8 seachestprobe.go:146] Disk: /dev/fd0 LogicalSectorSize:0 filled by seachest.
I0405 04:50:23.656147       8 seachestprobe.go:151] Disk: /dev/fd0 PhysicalSectorSize:0 filled by seachest.
I0405 04:50:23.656180       8 seachestprobe.go:156] Disk: /dev/fd0 RotationRate:0 filled by seachest.
I0405 04:50:23.656208       8 seachestprobe.go:161] Disk: /dev/fd0 DriveType:Not Available filled by seachest.
I0405 04:50:23.656242       8 seachestprobe.go:166] Disk: /dev/fd0 TotalBytesRead:0 filled by seachest.
I0405 04:50:23.656286       8 seachestprobe.go:171] Disk: /dev/fd0 TotalBytesWritten:0 filled by seachest.
I0405 04:50:23.656329       8 seachestprobe.go:176] Disk: /dev/fd0 DeviceUtilizationRate:%!d(float64=0) filled by seachest.
I0405 04:50:23.656367       8 seachestprobe.go:181] Disk: /dev/fd0 PercentEnduranceUsed:%!d(float64=0) filled by seachest.
I0405 04:50:23.656405       8 seachestprobe.go:186] Disk: /dev/fd0 TemperatureDataValid:false filled by seachest.
I0405 04:50:23.656433       8 probe.go:107] details filled by seachest probe
E0405 04:50:23.656532       8 smartprobe.go:100] map[errorCheckingConditions:the device type is not supported yet, device type: "unknown"]
I0405 04:50:23.656629       8 probe.go:107] details filled by smart probe
I0405 04:50:23.656919       8 probe.go:107] details filled by capacity probe
I0405 04:50:23.656977       8 filter.go:87] disk-ba6a9954a38fbcd390583db68ee87af3 ignored by path filter
I0405 04:50:23.657002       8 eventhandler.go:49] processing details for disk-72a3dc3afef83c50cb34ec1528ff0eb3
I0405 04:50:23.657618       8 probe.go:107] details filled by udev probe
	Sector Alignment: 0
	Rotation Rate (RPM): Not Reported
	Form Factor (inch): Not Reported
	Last DST information:
		Not supported
	Long Drive Self Test Time: Not Supported
	Interface speed:
		Max Speed (MB/s): 10.00 (FAST-10)
		Negotiated Speed (MB/s): Not Reported
	Annualized Workload Rate (TB/yr): Not Reported
	Total Bytes Read (B): Not Reported
I0405 04:50:23.659465       8 seachestprobe.go:116] Disk: /dev/dm-0 Model:Virtual disk     filled by seachest.
I0405 04:50:23.659527       8 seachestprobe.go:126] Disk: /dev/dm-0 Capacity:107374181888 filled by seachest.
I0405 04:50:23.659560       8 seachestprobe.go:131] Disk: /dev/dm-0 Serial: filled by seachest.
I0405 04:50:23.659631       8 seachestprobe.go:136] Disk: /dev/dm-0 Vendor:VMware   filled by seachest.
I0405 04:50:23.659670       8 seachestprobe.go:141] Disk: /dev/dm-0 FirmwareRevision:1.0  filled by seachest.
I0405 04:50:23.659710       8 seachestprobe.go:146] Disk: /dev/dm-0 LogicalSectorSize:512 filled by seachest.
I0405 04:50:23.659740       8 seachestprobe.go:151] Disk: /dev/dm-0 PhysicalSectorSize:512 filled by seachest.
I0405 04:50:23.659763       8 seachestprobe.go:156] Disk: /dev/dm-0 RotationRate:0 filled by seachest.
I0405 04:50:23.659786       8 seachestprobe.go:161] Disk: /dev/dm-0 DriveType:Not Available filled by seachest.
I0405 04:50:23.659821       8 seachestprobe.go:166] Disk: /dev/dm-0 TotalBytesRead:0 filled by seachest.
I0405 04:50:23.659849       8 seachestprobe.go:171] Disk: /dev/dm-0 TotalBytesWritten:0 filled by seachest.
I0405 04:50:23.659875       8 seachestprobe.go:176] Disk: /dev/dm-0 DeviceUtilizationRate:%!d(float64=0) filled by seachest.
I0405 04:50:23.659911       8 seachestprobe.go:181] Disk: /dev/dm-0 PercentEnduranceUsed:%!d(float64=0) filled by seachest.
I0405 04:50:23.659944       8 seachestprobe.go:186] Disk: /dev/dm-0 TemperatureDataValid:false filled by seachest.
I0405 04:50:23.659967       8 probe.go:107] details filled by seachest probe
	Total Bytes Written (B): Not Reported
	Encryption Support: Not Supported
	Cache Size (MiB): Not Reported
	Read Look-Ahead: Not Supported
	Write Cache: Not Supported
	SMART Status: Unknown or Not Supported
	ATA Security Information: Not Supported
E0405 04:50:23.660069       8 smartprobe.go:100] map[errorCheckingConditions:the device type is not supported yet, device type: "unknown"]
I0405 04:50:23.660130       8 probe.go:107] details filled by smart probe
	Firmware Download Support: Full, Segmented
	Specifications Supported:
		SCSI-2
	Features Supported:
		None reported or an error occurred while trying to determine
		the features.
	Vendor ID: VMware
	Model Number: Virtual disk
	Serial Number:
	Firmware Revision: 1.0
	World Wide Name: Not Supported
	Drive Capacity (GB/GiB): 53.69/50.00
	Temperature Data:
		Current Temperature (C): Not Reported
		Highest Temperature (C): Not Reported
		Lowest Temperature (C): Not Reported
	Power On Time: Not Reported
I0405 04:50:23.660410       8 probe.go:107] details filled by capacity probe
I0405 04:50:23.660458       8 filter.go:87] disk-72a3dc3afef83c50cb34ec1528ff0eb3 ignored by path filter
I0405 04:50:23.660481       8 eventhandler.go:49] processing details for disk-7eebe2a8a36ba61754c34cf1c368183d
	Power On Hours: Not Reported
	MaxLBA: 104857599
	Native MaxLBA: Not Reported
	Logical Sector Size (B): 512
	Physical Sector Size (B): 512
	Sector Alignment: 0
	Rotation Rate (RPM): Not Reported
	Form Factor (inch): Not Reported
	Last DST information:
		Not supported
	Long Drive Self Test Time: Not Supported
	Interface speed:
		Max Speed (MB/s): 10.00 (FAST-10)
		Negotiated Speed (MB/s): Not Reported
	Annualized Workload Rate (TB/yr): Not Reported
	Total Bytes Read (B): Not Reported
	Total Bytes Written (B): Not Reported
	Encryption Support: Not Supported
	Cache Size (MiB): Not Reported
	Read Look-Ahead: Not Supported
	Write Cache: Not Supported
	SMART Status: Unknown or Not Supported
	ATA Security Information: Not Supported
	Firmware Download Support: Full, Segmented
	Specifications Supported:
		SCSI-2
	Features Supported:
		None reported or an error occurred while trying to determine
		the features.
I0405 04:50:23.661048       8 probe.go:107] details filled by udev probe
get_Device: SG_GET_VERSION_NUM on /dev/fd0 failed version=0
Target Device does not have a valid interface 0
Target Device does not have a valid interface 0
Target Device does not have a valid interface 0
Target Device does not have a valid interface 0
Target Device does not have a valid interface 0
Target Device does not have a valid interface 0
Target Device does not have a valid interface 0
Target Device does not have a valid interface 0
Target Device does not have a valid interface 0
Target Device does not have a valid interface 0
Target Device does not have a valid interface 0
Target Device does not have a valid interface 0
Target Device does not have a valid interface 0
Target Device does not have a valid interface 0
Target Device does not have a valid interface 0
Target Device does not have a valid interface 0
Target Device does not have a valid interface 0
	Model Number:
	Serial Number:
	Firmware Revision:
	World Wide Name: Not Supported
	Drive Capacity (B/B): 0.00/0.00
	Temperature Data:
		Current Temperature (C): Not Reported
		Highest Temperature (C): Not Reported
		Lowest Temperature (C): Not Reported
	Power On Time: Not Reported
	Power On Hours: Not Reported
	MaxLBA: 0
	Native MaxLBA: Not Reported
	Logical Sector Size (B): 0
	Physical Sector Size (B): 0
	Sector Alignment: 0
	Rotation Rate (RPM): Not Reported
	Form Factor (inch): Not Reported
	Last DST information:
		Not supported
	Long Drive Self Test Time: Not Supported
	Interface speed:
		Not Reported
	Annualized Workload Rate (TB/yr): Not Reported
	Total Bytes Read (B): Not Reported
	Total Bytes Written (B): Not Reported
	Encryption Support: Not Supported
	Cache Size (MiB): Not Reported
	Read Look-Ahead: Not Supported
	Write Cache: Not Supported
	SMART Status: Unknown or Not Supported
	ATA Security Information: Not Supported
	Firmware Download Support: Full, Segmented
	Specifications Supported:
		None reported by device.
	Features Supported:
		None reported or an error occurred while trying to determine
		the features.
	Vendor ID: VMware
	Model Number: Virtual disk
I0405 04:50:23.662884       8 seachestprobe.go:116] Disk: /dev/dm-1 Model:Virtual disk     filled by seachest.
I0405 04:50:23.662953       8 seachestprobe.go:126] Disk: /dev/dm-1 Capacity:107374181888 filled by seachest.
I0405 04:50:23.662986       8 seachestprobe.go:131] Disk: /dev/dm-1 Serial: filled by seachest.
I0405 04:50:23.663034       8 seachestprobe.go:136] Disk: /dev/dm-1 Vendor:VMware   filled by seachest.
I0405 04:50:23.663074       8 seachestprobe.go:141] Disk: /dev/dm-1 FirmwareRevision:1.0  filled by seachest.
I0405 04:50:23.663115       8 seachestprobe.go:146] Disk: /dev/dm-1 LogicalSectorSize:512 filled by seachest.
I0405 04:50:23.663145       8 seachestprobe.go:151] Disk: /dev/dm-1 PhysicalSectorSize:512 filled by seachest.
I0405 04:50:23.663180       8 seachestprobe.go:156] Disk: /dev/dm-1 RotationRate:0 filled by seachest.
I0405 04:50:23.663204       8 seachestprobe.go:161] Disk: /dev/dm-1 DriveType:Not Available filled by seachest.
I0405 04:50:23.663246       8 seachestprobe.go:166] Disk: /dev/dm-1 TotalBytesRead:0 filled by seachest.
I0405 04:50:23.663275       8 seachestprobe.go:171] Disk: /dev/dm-1 TotalBytesWritten:0 filled by seachest.
I0405 04:50:23.663302       8 seachestprobe.go:176] Disk: /dev/dm-1 DeviceUtilizationRate:%!d(float64=0) filled by seachest.
I0405 04:50:23.663338       8 seachestprobe.go:181] Disk: /dev/dm-1 PercentEnduranceUsed:%!d(float64=0) filled by seachest.
I0405 04:50:23.663364       8 seachestprobe.go:186] Disk: /dev/dm-1 TemperatureDataValid:false filled by seachest.
I0405 04:50:23.663386       8 probe.go:107] details filled by seachest probe
E0405 04:50:23.663507       8 smartprobe.go:100] map[errorCheckingConditions:the device type is not supported yet, device type: "unknown"]
I0405 04:50:23.663607       8 probe.go:107] details filled by smart probe
I0405 04:50:23.663866       8 probe.go:107] details filled by capacity probe
I0405 04:50:23.663929       8 filter.go:87] disk-7eebe2a8a36ba61754c34cf1c368183d ignored by path filter
I0405 04:50:23.663954       8 eventhandler.go:49] processing details for disk-f006be38013ceefa365655a38ef0bde3
I0405 04:50:23.664489       8 probe.go:107] details filled by udev probe
I0405 04:50:23.666135       8 seachestprobe.go:116] Disk: /dev/dm-2 Model:Virtual disk     filled by seachest.
I0405 04:50:23.666205       8 seachestprobe.go:126] Disk: /dev/dm-2 Capacity:107374181888 filled by seachest.
I0405 04:50:23.666238       8 seachestprobe.go:131] Disk: /dev/dm-2 Serial: filled by seachest.
I0405 04:50:23.666272       8 seachestprobe.go:136] Disk: /dev/dm-2 Vendor:VMware   filled by seachest.
I0405 04:50:23.666305       8 seachestprobe.go:141] Disk: /dev/dm-2 FirmwareRevision:1.0  filled by seachest.
I0405 04:50:23.666337       8 seachestprobe.go:146] Disk: /dev/dm-2 LogicalSectorSize:512 filled by seachest.
I0405 04:50:23.666366       8 seachestprobe.go:151] Disk: /dev/dm-2 PhysicalSectorSize:512 filled by seachest.
I0405 04:50:23.666392       8 seachestprobe.go:156] Disk: /dev/dm-2 RotationRate:0 filled by seachest.
I0405 04:50:23.666415       8 seachestprobe.go:161] Disk: /dev/dm-2 DriveType:Not Available filled by seachest.
I0405 04:50:23.666446       8 seachestprobe.go:166] Disk: /dev/dm-2 TotalBytesRead:0 filled by seachest.
I0405 04:50:23.666476       8 seachestprobe.go:171] Disk: /dev/dm-2 TotalBytesWritten:0 filled by seachest.
I0405 04:50:23.666503       8 seachestprobe.go:176] Disk: /dev/dm-2 DeviceUtilizationRate:%!d(float64=0) filled by seachest.
I0405 04:50:23.666543       8 seachestprobe.go:181] Disk: /dev/dm-2 PercentEnduranceUsed:%!d(float64=0) filled by seachest.
I0405 04:50:23.666612       8 seachestprobe.go:186] Disk: /dev/dm-2 TemperatureDataValid:false filled by seachest.
I0405 04:50:23.666638       8 probe.go:107] details filled by seachest probe
E0405 04:50:23.666735       8 smartprobe.go:100] map[errorCheckingConditions:the device type is not supported yet, device type: "unknown"]
I0405 04:50:23.666864       8 probe.go:107] details filled by smart probe
I0405 04:50:23.667135       8 probe.go:107] details filled by capacity probe
I0405 04:50:23.667204       8 filter.go:87] disk-f006be38013ceefa365655a38ef0bde3 ignored by path filter
I0405 05:54:05.442769       8 event.go:44] processing new event for disk-1e134ed0e3bafbde3c606e25f3e4a57a action type add
I0405 05:54:05.454222       8 eventhandler.go:49] processing details for disk-1e134ed0e3bafbde3c606e25f3e4a57a
I0405 05:54:05.455117       8 probe.go:107] details filled by udev probe
open: No such file or directory
E0405 05:54:05.456835       8 seachest.go:83] Unable to get device info for device:%s with error:%s/dev/sdcFailed
E0405 05:54:05.456914       8 seachestprobe.go:100] 1
I0405 05:54:05.456940       8 probe.go:107] details filled by seachest probe
E0405 05:54:05.457103       8 smartprobe.go:100] map[DetectScsiTypeError:no such file or directory]
I0405 05:54:05.457173       8 probe.go:107] details filled by smart probe
I0405 05:54:05.457481       8 probe.go:107] details filled by capacity probe
I0405 05:54:05.457529       8 filter.go:87] disk-1e134ed0e3bafbde3c606e25f3e4a57a ignored by vendor filter
I0405 05:54:06.608422       8 event.go:44] processing new event for disk-1e134ed0e3bafbde3c606e25f3e4a57a action type change
I0405 05:54:10.424327       8 event.go:44] processing new event for disk-1e134ed0e3bafbde3c606e25f3e4a57a action type change
I0405 06:29:09.935855       8 event.go:44] processing new event for disk-1e134ed0e3bafbde3c606e25f3e4a57a action type add
I0405 06:29:09.943635       8 eventhandler.go:49] processing details for disk-1e134ed0e3bafbde3c606e25f3e4a57a
I0405 06:29:09.944640       8 probe.go:107] details filled by udev probe
open: No such file or directory
E0405 06:29:09.945529       8 seachest.go:83] Unable to get device info for device:%s with error:%s/dev/sddFailed
E0405 06:29:09.945624       8 seachestprobe.go:100] 1
I0405 06:29:09.945660       8 probe.go:107] details filled by seachest probe
E0405 06:29:09.945825       8 smartprobe.go:100] map[DetectScsiTypeError:no such file or directory]
I0405 06:29:09.945895       8 probe.go:107] details filled by smart probe
I0405 06:29:09.946266       8 probe.go:107] details filled by capacity probe
I0405 06:29:09.946326       8 filter.go:87] disk-1e134ed0e3bafbde3c606e25f3e4a57a ignored by vendor filter
I0405 06:29:09.973159       8 event.go:44] processing new event for disk-14367d6b3eb5ef5bacc2961eb8d57c46 action type add
I0405 06:29:09.978043       8 eventhandler.go:49] processing details for disk-14367d6b3eb5ef5bacc2961eb8d57c46
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0xf75afd]

goroutine 26 [running]:
panic(0x112efc0, 0x1c4f390)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/panic.go:540 +0x45e fp=0xc42020f9b8 sp=0xc42020f910 pc=0x43a1be
runtime.panicmem()
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/panic.go:63 +0x5e fp=0xc42020f9d8 sp=0xc42020f9b8 pc=0x438eee
runtime.sigpanic()
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/signal_unix.go:367 +0x17c fp=0xc42020fa28 sp=0xc42020f9d8 pc=0x45074c
github.com/openebs/node-disk-manager/cmd/probe.(*udevProbe).FillDiskDetails(0xc4203c8d40, 0xc420062a80)
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/cmd/probe/udevprobe.go:172 +0x5d fp=0xc42020fb48 sp=0xc42020fa28 pc=0xf75afd
github.com/openebs/node-disk-manager/cmd/controller.(*Probe).FillDiskDetails(0xc4203afc20, 0xc420062a80)
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/cmd/controller/probe.go:47 +0x3e fp=0xc42020fb68 sp=0xc42020fb48 pc=0xf6314e
github.com/openebs/node-disk-manager/cmd/controller.(*Controller).FillDiskDetails(0xc420184460, 0xc420062a80)
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/cmd/controller/probe.go:106 +0xdf fp=0xc42020fbd8 sp=0xc42020fb68 pc=0xf639cf
github.com/openebs/node-disk-manager/cmd/probe.(*ProbeEvent).addDiskEvent(0xc42000e008, 0xc42034079d, 0x3, 0xc42000e0b0, 0x1, 0x1)
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/cmd/probe/eventhandler.go:50 +0x214 fp=0xc42020ff20 sp=0xc42020fbd8 pc=0xf72604
github.com/openebs/node-disk-manager/cmd/probe.(*udevProbe).listen(0xc4203c8d40)
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/cmd/probe/udevprobe.go:201 +0x200 fp=0xc42020ffd8 sp=0xc42020ff20 pc=0xf76040
runtime.goexit()
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/asm_amd64.s:2337 +0x1 fp=0xc42020ffe0 sp=0xc42020ffd8 pc=0x468d41
created by github.com/openebs/node-disk-manager/cmd/probe.(*udevProbe).Start
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/cmd/probe/udevprobe.go:115 +0x3f

goroutine 1 [chan receive, 98 minutes]:
runtime.gopark(0x12ebc98, 0xc4200a4898, 0x1272a19, 0xc, 0x1cc8317, 0x3)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/proc.go:287 +0x12c fp=0xc42020dab0 sp=0xc42020da80 pc=0x43c2bc
runtime.goparkunlock(0xc4200a4898, 0x1272a19, 0xc, 0x17, 0x3)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/proc.go:293 +0x5e fp=0xc42020daf0 sp=0xc42020dab0 pc=0x43c3ae
runtime.chanrecv(0xc4200a4840, 0x0, 0x1, 0x1)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/chan.go:506 +0x304 fp=0xc42020dba0 sp=0xc42020daf0 pc=0x4147f4
runtime.chanrecv1(0xc4200a4840, 0x0)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/chan.go:388 +0x2b fp=0xc42020dbd0 sp=0xc42020dba0 pc=0x41449b
github.com/openebs/node-disk-manager/cmd/controller.(*Controller).run(0xc420184460, 0x2, 0xc4200a4840, 0xfaa18a, 0x465480)
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/cmd/controller/controller.go:201 +0x82 fp=0xc42020dc28 sp=0xc42020dbd0 pc=0xf5ff12
github.com/openebs/node-disk-manager/cmd/controller.(*Controller).Start(0xc420184460)
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/cmd/controller/controller.go:180 +0x54 fp=0xc42020dc80 sp=0xc42020dc28 pc=0xf5fd84
github.com/openebs/node-disk-manager/cmd/app/command.NewCmdStart.func1(0xc420010a00, 0x1ce88f8, 0x0, 0x0)
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/cmd/app/command/start.go:66 +0x218 fp=0xc42020dcd8 sp=0xc42020dc80 pc=0xfaa198
github.com/openebs/node-disk-manager/vendor/github.com/spf13/cobra.(*Command).execute(0xc420010a00, 0x1ce88f8, 0x0, 0x0, 0xc420010a00, 0x1ce88f8)
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/vendor/github.com/spf13/cobra/command.go:766 +0x2c1 fp=0xc42020ddc8 sp=0xc42020dcd8 pc=0x5adbf1
github.com/openebs/node-disk-manager/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0xc420010280, 0xc420212020, 0xc420010500, 0xc420010a00)
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/vendor/github.com/spf13/cobra/command.go:852 +0x334 fp=0xc42020df08 sp=0xc42020ddc8 pc=0x5ae834
github.com/openebs/node-disk-manager/vendor/github.com/spf13/cobra.(*Command).Execute(0xc420010280, 0x0, 0x0)
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/vendor/github.com/spf13/cobra/command.go:800 +0x2b fp=0xc42020df38 sp=0xc42020df08 pc=0x5ae4db
main.run(0x0, 0x0)
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/cmd/main.go:45 +0x87 fp=0xc42020df60 sp=0xc42020df38 pc=0xfaa747
main.main()
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/cmd/main.go:27 +0x22 fp=0xc42020df80 sp=0xc42020df60 pc=0xfaa682
runtime.main()
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/proc.go:195 +0x226 fp=0xc42020dfe0 sp=0xc42020df80 pc=0x43be06
runtime.goexit()
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/asm_amd64.s:2337 +0x1 fp=0xc42020dfe8 sp=0xc42020dfe0 pc=0x468d41

goroutine 2 [force gc (idle), 2 minutes]:
runtime.gopark(0x12ebc98, 0x1cc7430, 0x127571f, 0xf, 0x1cc8b14, 0x1)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/proc.go:287 +0x12c fp=0xc420026768 sp=0xc420026738 pc=0x43c2bc
runtime.goparkunlock(0x1cc7430, 0x127571f, 0xf, 0xc400000014, 0x1)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/proc.go:293 +0x5e fp=0xc4200267a8 sp=0xc420026768 pc=0x43c3ae
runtime.forcegchelper()
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/proc.go:245 +0xcc fp=0xc4200267e0 sp=0xc4200267a8 pc=0x43c0dc
runtime.goexit()
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/asm_amd64.s:2337 +0x1 fp=0xc4200267e8 sp=0xc4200267e0 pc=0x468d41
created by runtime.init.4
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/proc.go:234 +0x35

goroutine 18 [GC sweep wait]:
runtime.gopark(0x12ebc98, 0x1cc7780, 0x12733d5, 0xd, 0x463e14, 0x1)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/proc.go:287 +0x12c fp=0xc420022760 sp=0xc420022730 pc=0x43c2bc
runtime.goparkunlock(0x1cc7780, 0x12733d5, 0xd, 0x14, 0x1)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/proc.go:293 +0x5e fp=0xc4200227a0 sp=0xc420022760 pc=0x43c3ae
runtime.bgsweep(0xc42006e000)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/mgcsweep.go:71 +0x134 fp=0xc4200227d8 sp=0xc4200227a0 pc=0x42eab4
runtime.goexit()
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/asm_amd64.s:2337 +0x1 fp=0xc4200227e0 sp=0xc4200227d8 pc=0x468d41
created by runtime.gcenable
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/mgc.go:216 +0x58

goroutine 19 [finalizer wait, 98 minutes]:
runtime.gopark(0x12ebc98, 0x1ce87f0, 0x1274728, 0xe, 0x14, 0x1)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/proc.go:287 +0x12c fp=0xc420022f00 sp=0xc420022ed0 pc=0x43c2bc
runtime.goparkunlock(0x1ce87f0, 0x1274728, 0xe, 0x14, 0x1)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/proc.go:293 +0x5e fp=0xc420022f40 sp=0xc420022f00 pc=0x43c3ae
runtime.runfinq()
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/mfinal.go:175 +0xb8 fp=0xc420022fe0 sp=0xc420022f40 pc=0x425808
runtime.goexit()
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/asm_amd64.s:2337 +0x1 fp=0xc420022fe8 sp=0xc420022fe0 pc=0x468d41
created by runtime.createfing
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/mfinal.go:156 +0x62

goroutine 20 [chan receive]:
runtime.gopark(0x12ebc98, 0xc420070118, 0x1272a19, 0xc, 0xc42001e117, 0x3)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/proc.go:287 +0x12c fp=0xc420023670 sp=0xc420023640 pc=0x43c2bc
runtime.goparkunlock(0xc420070118, 0x1272a19, 0xc, 0x17, 0x3)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/proc.go:293 +0x5e fp=0xc4200236b0 sp=0xc420023670 pc=0x43c3ae
runtime.chanrecv(0xc4200700c0, 0xc4200237b0, 0x1cc8301, 0x1cc83d8)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/chan.go:506 +0x304 fp=0xc420023760 sp=0xc4200236b0 pc=0x4147f4
runtime.chanrecv2(0xc4200700c0, 0xc4200237b0, 0x1)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/chan.go:393 +0x2b fp=0xc420023790 sp=0xc420023760 pc=0x4144db
github.com/openebs/node-disk-manager/vendor/github.com/golang/glog.(*loggingT).flushDaemon(0x1cc83c0)
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/vendor/github.com/golang/glog/glog.go:882 +0x9f fp=0xc4200237d8 sp=0xc420023790 pc=0x50c0ef
runtime.goexit()
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/asm_amd64.s:2337 +0x1 fp=0xc4200237e0 sp=0xc4200237d8 pc=0x468d41
created by github.com/openebs/node-disk-manager/vendor/github.com/golang/glog.init.0
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/vendor/github.com/golang/glog/glog.go:410 +0x203

goroutine 21 [syscall]:
runtime.notetsleepg(0x1cc7e80, 0x12a04ac91, 0x1)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/lock_futex.go:227 +0x42 fp=0xc420023f60 sp=0xc420023f30 pc=0x41f4a2
runtime.timerproc()
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/time.go:216 +0x305 fp=0xc420023fe0 sp=0xc420023f60 pc=0x459b05
runtime.goexit()
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/asm_amd64.s:2337 +0x1 fp=0xc420023fe8 sp=0xc420023fe0 pc=0x468d41
created by runtime.addtimerLocked
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/time.go:122 +0xed

goroutine 34 [GC worker (idle), 2 minutes]:
runtime.gopark(0x12ebb28, 0xc42041b640, 0x12760e4, 0x10, 0x14, 0x0)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/proc.go:287 +0x12c fp=0xc42045e748 sp=0xc42045e718 pc=0x43c2bc
runtime.gcBgMarkWorker(0xc42001c000)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/mgc.go:1710 +0x143 fp=0xc42045e7d8 sp=0xc42045e748 pc=0x429393
runtime.goexit()
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/asm_amd64.s:2337 +0x1 fp=0xc42045e7e0 sp=0xc42045e7d8 pc=0x468d41
created by runtime.gcBgMarkStartWorkers
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/mgc.go:1658 +0x7e

goroutine 35 [GC worker (idle), 2 minutes]:
runtime.gopark(0x12ebb28, 0xc42041b650, 0x12760e4, 0x10, 0x14, 0x0)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/proc.go:287 +0x12c fp=0xc42045ef48 sp=0xc42045ef18 pc=0x43c2bc
runtime.gcBgMarkWorker(0xc42001d300)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/mgc.go:1710 +0x143 fp=0xc42045efd8 sp=0xc42045ef48 pc=0x429393
runtime.goexit()
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/asm_amd64.s:2337 +0x1 fp=0xc42045efe0 sp=0xc42045efd8 pc=0x468d41
created by runtime.gcBgMarkStartWorkers
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/mgc.go:1658 +0x7e

goroutine 36 [GC worker (idle), 2 minutes]:
runtime.gopark(0x12ebb28, 0xc42041b660, 0x12760e4, 0x10, 0x14, 0x0)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/proc.go:287 +0x12c fp=0xc42045f748 sp=0xc42045f718 pc=0x43c2bc
runtime.gcBgMarkWorker(0xc42001e600)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/mgc.go:1710 +0x143 fp=0xc42045f7d8 sp=0xc42045f748 pc=0x429393
runtime.goexit()
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/asm_amd64.s:2337 +0x1 fp=0xc42045f7e0 sp=0xc42045f7d8 pc=0x468d41
created by runtime.gcBgMarkStartWorkers
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/mgc.go:1658 +0x7e

goroutine 37 [GC worker (idle), 10 minutes]:
runtime.gopark(0x12ebb28, 0xc42041b670, 0x12760e4, 0x10, 0x14, 0x0)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/proc.go:287 +0x12c fp=0xc42045ff48 sp=0xc42045ff18 pc=0x43c2bc
runtime.gcBgMarkWorker(0xc42001f900)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/mgc.go:1710 +0x143 fp=0xc42045ffd8 sp=0xc42045ff48 pc=0x429393
runtime.goexit()
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/asm_amd64.s:2337 +0x1 fp=0xc42045ffe0 sp=0xc42045ffd8 pc=0x468d41
created by runtime.gcBgMarkStartWorkers
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/mgc.go:1658 +0x7e

goroutine 3 [syscall, 98 minutes]:
runtime.notetsleepg(0x1ce8c20, 0xffffffffffffffff, 0x0)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/lock_futex.go:227 +0x42 fp=0xc420028780 sp=0xc420028750 pc=0x41f4a2
os/signal.signal_recv(0x0)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/sigqueue.go:131 +0xa6 fp=0xc4200287a8 sp=0xc420028780 pc=0x451626
os/signal.loop()
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/os/signal/signal_unix.go:22 +0x22 fp=0xc4200287e0 sp=0xc4200287a8 pc=0xf5ae02
runtime.goexit()
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/asm_amd64.s:2337 +0x1 fp=0xc4200287e8 sp=0xc4200287e0 pc=0x468d41
created by os/signal.init.0
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/os/signal/signal_unix.go:28 +0x41

goroutine 39 [select]:
runtime.gopark(0x12ebcd0, 0x0, 0x126d069, 0x6, 0x18, 0x1)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/proc.go:287 +0x12c fp=0xc420037c48 sp=0xc420037c18 pc=0x43c2bc
runtime.selectgo(0xc420037f00, 0xc4202aa000)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/select.go:395 +0x1149 fp=0xc420037ec0 sp=0xc420037c48 pc=0x44bc19
github.com/openebs/node-disk-manager/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil(0x12ea3d8, 0x12a05f200, 0x0, 0x442401, 0xc4200a44e0)
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:145 +0x17e fp=0xc420037f90 sp=0xc420037ec0 pc=0x9a83ce
github.com/openebs/node-disk-manager/vendor/k8s.io/apimachinery/pkg/util/wait.Until(0x12ea3d8, 0x12a05f200, 0xc4200a44e0)
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:88 +0x4d fp=0xc420037fc8 sp=0xc420037f90 pc=0x9a823d
runtime.goexit()
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/asm_amd64.s:2337 +0x1 fp=0xc420037fd0 sp=0xc420037fc8 pc=0x468d41
created by github.com/openebs/node-disk-manager/pkg/logs.InitLogs
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/pkg/logs/logs.go:50 +0x89

goroutine 25 [chan send, 98 minutes]:
runtime.gopark(0x12ebc98, 0xc4200a4658, 0x126fe91, 0x9, 0xc42001f416, 0x3)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/proc.go:287 +0x12c fp=0xc420460698 sp=0xc420460668 pc=0x43c2bc
runtime.goparkunlock(0xc4200a4658, 0x126fe91, 0x9, 0xc420460716, 0x3)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/proc.go:293 +0x5e fp=0xc4204606d8 sp=0xc420460698 pc=0x43c3ae
runtime.chansend(0xc4200a4600, 0xc4204607c0, 0x1, 0xf65331, 0x1)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/chan.go:222 +0x26b fp=0xc420460778 sp=0xc4204606d8 pc=0x4139cb
runtime.chansend1(0xc4200a4600, 0xc4204607c0)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/chan.go:113 +0x43 fp=0xc4204607b0 sp=0xc420460778 pc=0x413753
github.com/openebs/node-disk-manager/cmd/controller.(*Controller).Broadcast.func1(0xc420184460)
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/cmd/controller/controller.go:193 +0x41 fp=0xc4204607d8 sp=0xc4204607b0 pc=0xf65331
runtime.goexit()
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/asm_amd64.s:2337 +0x1 fp=0xc4204607e0 sp=0xc4204607d8 pc=0x468d41
created by github.com/openebs/node-disk-manager/cmd/controller.(*Controller).Broadcast
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/cmd/controller/controller.go:191 +0x3f

goroutine 23 [IO wait]:
runtime.gopark(0x12ebc68, 0x7f19ea430f28, 0x126d696, 0x7, 0xc42001c01b, 0x5)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/proc.go:287 +0x12c fp=0xc420039678 sp=0xc420039648 pc=0x43c2bc
runtime.netpollblock(0x7f19ea430f00, 0x72, 0x1000)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/netpoll.go:366 +0xaa fp=0xc4200396c0 sp=0xc420039678 pc=0x4373ca
internal/poll.runtime_pollWait(0x7f19ea430f00, 0x72, 0x0)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/netpoll.go:173 +0x57 fp=0xc4200396e8 sp=0xc4200396c0 pc=0x4369c7
internal/poll.(*pollDesc).wait(0xc420480018, 0x72, 0xffffffffffffff00, 0x1c65820, 0x1c5ef08)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/internal/poll/fd_poll_runtime.go:85 +0xae fp=0xc420039720 sp=0xc4200396e8 pc=0x494b9e
internal/poll.(*pollDesc).waitRead(0xc420480018, 0xc420102000, 0x1000, 0x1000)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/internal/poll/fd_poll_runtime.go:90 +0x3d fp=0xc420039758 sp=0xc420039720 pc=0x494c1d
internal/poll.(*FD).Read(0xc420480000, 0xc420102000, 0x1000, 0x1000, 0x0, 0x0, 0x0)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/internal/poll/fd_unix.go:126 +0x18a fp=0xc4200397a8 sp=0xc420039758 pc=0x4959ba
net.(*netFD).Read(0xc420480000, 0xc420102000, 0x1000, 0x1000, 0x894, 0x0, 0x0)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/net/fd_unix.go:202 +0x52 fp=0xc420039810 sp=0xc4200397a8 pc=0x52ac42
net.(*conn).Read(0xc420082250, 0xc420102000, 0x1000, 0x1000, 0x0, 0x0, 0x0)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/net/net.go:176 +0x6d fp=0xc420039878 sp=0xc420039810 pc=0x53cf7d
crypto/tls.(*block).readFromUntil(0xc42026c030, 0x7f19ea34c0f0, 0xc420082250, 0x5, 0xc420082250, 0x0)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/crypto/tls/conn.go:488 +0x95 fp=0xc4200398c0 sp=0xc420039878 pc=0x715e85
crypto/tls.(*Conn).readRecord(0xc420462380, 0x12ebd17, 0xc4204624a0, 0x20)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/crypto/tls/conn.go:590 +0xe0 fp=0xc420039b10 sp=0xc4200398c0 pc=0x7163f0
crypto/tls.(*Conn).Read(0xc420462380, 0xc4200f0000, 0x1000, 0x1000, 0x0, 0x0, 0x0)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/crypto/tls/conn.go:1134 +0x110 fp=0xc420039b70 sp=0xc420039b10 pc=0x719f40
bufio.(*Reader).Read(0xc4200f6960, 0xc42021a3b8, 0x9, 0x9, 0xc42024a400, 0xc4200013a8, 0xc420039c50)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/bufio/bufio.go:213 +0x30b fp=0xc420039c08 sp=0xc420039b70 pc=0x4f311b
io.ReadAtLeast(0x1c607a0, 0xc4200f6960, 0xc42021a3b8, 0x9, 0x9, 0x9, 0xc4202f8201, 0xc420039cf8, 0x99c3bb)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/io/io.go:309 +0x86 fp=0xc420039c68 sp=0xc420039c08 pc=0x472b96
io.ReadFull(0x1c607a0, 0xc4200f6960, 0xc42021a3b8, 0x9, 0x9, 0x1c60de0, 0xc420074030, 0xc420039d28)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/io/io.go:327 +0x58 fp=0xc420039cc0 sp=0xc420039c68 pc=0x472d08
github.com/openebs/node-disk-manager/vendor/golang.org/x/net/http2.readFrameHeader(0xc42021a3b8, 0x9, 0x9, 0x1c607a0, 0xc4200f6960, 0x0, 0x0, 0x876, 0x0)
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/vendor/golang.org/x/net/http2/frame.go:237 +0x7b fp=0xc420039d20 sp=0xc420039cc0 pc=0x986a2b
github.com/openebs/node-disk-manager/vendor/golang.org/x/net/http2.(*Framer).ReadFrame(0xc42021a380, 0xc4204a4900, 0x0, 0x0, 0x0)
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/vendor/golang.org/x/net/http2/frame.go:492 +0xa4 fp=0xc420039e08 sp=0xc420039d20 pc=0x987394
github.com/openebs/node-disk-manager/vendor/golang.org/x/net/http2.(*clientConnReadLoop).run(0xc420039fb8, 0x12eae90, 0xc42045d7b8)
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/vendor/golang.org/x/net/http2/transport.go:1616 +0x90 fp=0xc420039f68 sp=0xc420039e08 pc=0x999210
github.com/openebs/node-disk-manager/vendor/golang.org/x/net/http2.(*ClientConn).readLoop(0xc420222000)
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/vendor/golang.org/x/net/http2/transport.go:1544 +0x68 fp=0xc420039fd8 sp=0xc420039f68 pc=0x998ab8
runtime.goexit()
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/asm_amd64.s:2337 +0x1 fp=0xc420039fe0 sp=0xc420039fd8 pc=0x468d41
created by github.com/openebs/node-disk-manager/vendor/golang.org/x/net/http2.(*Transport).newClientConn
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/vendor/golang.org/x/net/http2/transport.go:619 +0x6ec

goroutine 27 [syscall]:
syscall.Syscall6(0x17, 0x7, 0xc420036ea8, 0x0, 0x0, 0x0, 0x0, 0x462f20, 0xc4200a4660, 0xc420036e50)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/syscall/asm_linux_amd64.s:44 +0x5 fp=0xc420036dd0 sp=0xc420036dc8 pc=0x47f415
syscall.Select(0x7, 0xc420036ea8, 0x0, 0x0, 0x0, 0x1, 0x0, 0x0)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/syscall/zsyscall_linux_amd64.go:1374 +0xae fp=0xc420036e60 sp=0xc420036dd0 pc=0x47dc3e
github.com/openebs/node-disk-manager/pkg/udevevent.(*monitor).process(0xc420074cd0, 0x6, 0x0, 0x0)
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/pkg/udevevent/monitor.go:85 +0xd4 fp=0xc420036f70 sp=0xc420036e60 pc=0xf718f4
github.com/openebs/node-disk-manager/pkg/udevevent.Monitor()
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/pkg/udevevent/monitor.go:118 +0x12b fp=0xc420036fe0 sp=0xc420036f70 pc=0xf71cab
runtime.goexit()
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/asm_amd64.s:2337 +0x1 fp=0xc420036fe8 sp=0xc420036fe0 pc=0x468d41
created by github.com/openebs/node-disk-manager/cmd/probe.(*udevProbe).Start
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/cmd/probe/udevprobe.go:116 +0x57

goroutine 29 [IO wait, 98 minutes]:
runtime.gopark(0x12ebc68, 0x7f19ea430e68, 0x126d696, 0x7, 0x1b, 0x5)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/proc.go:287 +0x12c fp=0xc420473b20 sp=0xc420473af0 pc=0x43c2bc
runtime.netpollblock(0x7f19ea430e40, 0x72, 0xd0)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/netpoll.go:366 +0xaa fp=0xc420473b68 sp=0xc420473b20 pc=0x4373ca
internal/poll.runtime_pollWait(0x7f19ea430e40, 0x72, 0xffffffffffffffff)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/netpoll.go:173 +0x57 fp=0xc420473b90 sp=0xc420473b68 pc=0x4369c7
internal/poll.(*pollDesc).wait(0xc420106018, 0x72, 0xc420473c00, 0x0, 0x0)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/internal/poll/fd_poll_runtime.go:85 +0xae fp=0xc420473bc8 sp=0xc420473b90 pc=0x494b9e
internal/poll.(*pollDesc).waitRead(0xc420106018, 0xffffffffffffff00, 0x0, 0x0)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/internal/poll/fd_poll_runtime.go:90 +0x3d fp=0xc420473c00 sp=0xc420473bc8 pc=0x494c1d
internal/poll.(*FD).Accept(0xc420106000, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/internal/poll/fd_unix.go:335 +0x1e2 fp=0xc420473c68 sp=0xc420473c00 pc=0x497072
net.(*netFD).accept(0xc420106000, 0x7f19ea48cd90, 0x0, 0x12ebd88)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/net/fd_unix.go:238 +0x42 fp=0xc420473d40 sp=0xc420473c68 pc=0x52b662
net.(*TCPListener).accept(0xc42000e010, 0xc420473da8, 0x420a08, 0x30)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/net/tcpsock_posix.go:136 +0x2e fp=0xc420473d70 sp=0xc420473d40 pc=0x54720e
net.(*TCPListener).AcceptTCP(0xc42000e010, 0xc4201920f0, 0xc4201920f0, 0x1118260)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/net/tcpsock.go:234 +0x49 fp=0xc420473db8 sp=0xc420473d70 pc=0x5455e9
net/http.tcpKeepAliveListener.Accept(0xc42000e010, 0xc42009a010, 0x1118260, 0x1c4f2b0, 0x1237040)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/net/http/server.go:3120 +0x2f fp=0xc420473df0 sp=0xc420473db8 pc=0x7bfb8f
net/http.(*Server).Serve(0xc420190000, 0x1c78860, 0xc42000e010, 0x0, 0x0)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/net/http/server.go:2695 +0x1b2 fp=0xc420473ea8 sp=0xc420473df0 pc=0x7be832
net/http.(*Server).ListenAndServe(0xc420190000, 0xc420190000, 0x1)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/net/http/server.go:2636 +0xa9 fp=0xc420473ef8 sp=0xc420473ea8 pc=0x7be579
net/http.ListenAndServe(0x126b3f8, 0x5, 0x0, 0x0, 0x5, 0x126e91a)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/net/http/server.go:2882 +0x7f fp=0xc420473f28 sp=0xc420473ef8 pc=0x7bf70f
github.com/openebs/node-disk-manager/pkg/server.StartHttpServer(0x1cc8140, 0xc4202505a0)
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/pkg/server/server.go:43 +0x170 fp=0xc420473fd0 sp=0xc420473f28 pc=0xfa8950
runtime.goexit()
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/asm_amd64.s:2337 +0x1 fp=0xc420473fd8 sp=0xc420473fd0 pc=0x468d41
created by github.com/openebs/node-disk-manager/cmd/app/command.NewCmdStart.func1
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/cmd/app/command/start.go:65 +0x20a

goroutine 54 [select, 98 minutes, locked to thread]:
runtime.gopark(0x12ebcd0, 0x0, 0x126d069, 0x6, 0x18, 0x1)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/proc.go:287 +0x12c fp=0xc42045d4a0 sp=0xc42045d470 pc=0x43c2bc
runtime.selectgo(0xc42045d750, 0xc4200a4900)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/select.go:395 +0x1149 fp=0xc42045d718 sp=0xc42045d4a0 pc=0x44bc19
runtime.ensureSigM.func1()
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/signal_unix.go:511 +0x220 fp=0xc42045d7e0 sp=0xc42045d718 pc=0x465990
runtime.goexit()
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/asm_amd64.s:2337 +0x1 fp=0xc42045d7e8 sp=0xc42045d7e0 pc=0x468d41
created by runtime.ensureSigM
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/signal_unix.go:494 +0xda

goroutine 6 [chan receive, 98 minutes]:
runtime.gopark(0x12ebc98, 0xc4202aa7d8, 0x1272a19, 0xc, 0xc42001ce17, 0x3)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/proc.go:287 +0x12c fp=0xc420569690 sp=0xc420569660 pc=0x43c2bc
runtime.goparkunlock(0xc4202aa7d8, 0x1272a19, 0xc, 0x17, 0x3)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/proc.go:293 +0x5e fp=0xc4205696d0 sp=0xc420569690 pc=0x43c3ae
runtime.chanrecv(0xc4202aa780, 0x0, 0x1, 0x0)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/chan.go:506 +0x304 fp=0xc420569780 sp=0xc4205696d0 pc=0x4147f4
runtime.chanrecv1(0xc4202aa780, 0x0)
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/chan.go:388 +0x2b fp=0xc4205697b0 sp=0xc420569780 pc=0x41449b
github.com/openebs/node-disk-manager/pkg/signals.SetupSignalHandler.func1(0xc4202aa780, 0xc4200a4840)
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/pkg/signals/signal.go:37 +0x34 fp=0xc4205697d0 sp=0xc4205697b0 pc=0xf5b204
runtime.goexit()
	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/runtime/asm_amd64.s:2337 +0x1 fp=0xc4205697d8 sp=0xc4205697d0 pc=0x468d41
created by github.com/openebs/node-disk-manager/pkg/signals.SetupSignalHandler
	/home/travis/gopath/src/github.com/openebs/node-disk-manager/pkg/signals/signal.go:36 +0xd0
/usr/local/bin/entrypoint.sh: line 34:     8 Aborted                 (core dumped) /usr/sbin/ndm start

Screenshots

Your Environment

kubectl get nodes:
kubectl get pods --all-namespaces:
kubectl get services:
kubectl get sc:
kubectl get pv:
kubectl get pvc:
OS (from /etc/os-release):
Kernel (from uname -a):
Install tools:
Others:

Fixed in PR 230 in ndm repository.


Implement handling for the CSRF token

Django expects a CSRF token with every POST request. This token is set as a cookie, but Elm doesn't offer a way to read cookies. That's why we need to implement a native module (or use https://github.com/jessitron/elm-cookie). We can use this as inspiration for the native module https://github.com/NoRedInk/elm-rails/blob/master/src/Native/Rails.js.

In the end, a better solution is to use programWithFlags and pass the token to the app when we initialize it.


[material-ui][docs] Standardize all references to Material Design 3 (M3)

Raised in this comment thread: https://github.com/mui/material-ui/pull/40446#discussion_r1471634637

(From https://developer.android.com/codelabs/jetpack-compose-theming#0)
This PR replaces mentions of "Material 3" and "MD3" with either "Material Design 3" or "M3."
Though "Material 3" might be considered an acceptable synonym, I think it's overly confusing in our context. (Are we talking about Material UI v3?). We should err on the side of clarifying that we're talking about Material Design most of the time; after first mention, I think M3 works well to maintain that clarity.
I removed the names of the components from the headers in the component demo docs because they just felt redundant. The search experience could be better, but that's something we should address with the design of the search results if we want to improve it.
I've also done some rewriting of the @mui/material-next docs to reflect the changes to the release schedule (since M3 is coming in v7, not v6).

Nice 👍


get rid of references to plugins registry

In the welcome message we're making multiple references to the jQuery plugins registry and publishing plugins in there. That doesn't really make sense anymore, since the plugins site is currently in "read-only mode".

:+1: Wanna do a PR?

Sorry, @sindresorhus, missed your comment. Will do PR this evening ;)

@sindresorhus https://github.com/yeoman/generator-jquery/pull/37


Fixed up inconsistencies in blog example (e.g. whitespace, quotes)

We are using wintersmith as our blog framework and noticed a lot of inconsistencies in the boilerplate example for the blog template. This PR attempts to fix them up. In this PR:

Converted archive.jade from tab indentation to spaces indentation
Added missing semicolons
Guaranteed consistent spacing for functions function(param) { /* body */ }
Moved to consistently use Jade loops outside of variable generation
Always use each for loops in Jade
Removed excess semicolons from inline styles
Removed excess trailing whitespace in files (e.g. 5 newlines at end of a file)
Always use single quotes in templates
Added missing spaces around + and after = for a tag's content
Added leading whitespace line for extended Jade templates

Thanks :beers:


Small docs change

See #320 - I did a quick audit and changed the couple of things that could use it. I did not confirm whether or not any of the code samples in the docs have any changes that are inconsistent with the current codebase... My hope is that they were already update and tested :sweat_smile:
Anyway... this may or may not completely resolve #320.

I enabled building PR previews @ RTD but it fails currently because the RTD config file needs to be updated: https://readthedocs.org/projects/aiosmtpd/builds/23289246/.
The GHA linting is failing is unrelated either, because of the unpinned flake8 plugin version, I suppose.

the RTD config file needs to be updated

Filed an issue for this with pointers: https://github.com/aio-libs/aiosmtpd/issues/393.

@waynew needs conflict resolution


metronome_channel flag

-Adds an flag option to define the MIDI channel the metronome messages
come in on (comes in on MIDI Channel 1 by default). Allows separating
generated content and click (for recording/monitoring)
-Ability to add metronome to playback of generated material
-Adds a flag option to define the mix amount of metronome click that is
heard during playback vs capture. By default, it is set to 0% so that
no click is heard unless flag is set.
-include default metronome velocity as a variable

Sorry for all of these nit-picky google style rules!

FYI: https://google.github.io/styleguide/pyguide.html

Great, this is a good thing to know about ;) No need to apologize!

On Aug 8, 2016, at 10:16 AM, Adam Roberts<EMAIL_ADDRESS>wrote:
FYI: https://google.github.io/styleguide/pyguide.html https://google.github.io/styleguide/pyguide.html
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/tensorflow/magenta/pull/143#issuecomment-238305450, or mute the thread https://github.com/notifications/unsubscribe-auth/AP7D9eZ5AZV_vbGavmMnsfTWlQAnVGoRks5qd2RjgaJpZM4JeVp4.

I still need to add the sequence.tempos check

LGTM, but can you sync with master to get rid of merge conflicts?


Kubewatcher: trigger functions from Kubernetes Watch callbacks

This is the start of an implementation to get Kubernetes watches to trigger Fission functions.  It uses HTTP to call functions, so perhaps the Kubewatcher service can be made a more general part of K8s.
(Using Kubernetes watches/events to launch functions was a use case suggested by @kelseyhightower at Kubecon. Thanks!!)
Contents of this PR:
fission.Watch object in the API; its implementation in server and CLI.  A fission.Watch contains a namespace, object type and label and field selectors; together these can be used to create a Kubernetes watch.  It also contains the metadata of the function to call.  Label and field selectors aren't implemented yet, and for now only Pods and Services are supported as object types.
A new kubewatcher service which:

Syncs with the controller API to find out what it needs to watch on the K8s API

Creates/destroys K8s watches

Does a POST to the function's URL when the watch fires.  When a K8s watch callback fires, it gives us a Kubernetes watch.Event, containing an event type and an object.  We serialize the object into JSON (using the JSON serialization code from kubectl) and place the event type in a X-Kubernetes-Watch-Event-Type header.

There is currently no reliability implemented; we drop events if there's any kind of error from the endpoint.
Separately, we also send the events serially, so if one event is processed slowly, they all slow down.  I'm not sure what the right approach is here; making events concurrent might be a confusing interface for people implementing the handlers.
Further work:

Separate out the Kubewatcher service from Fission entirely; it could be potentially a good thing to add to K8s itself?  In other words some sort general Kube Watch -> webhook connector.

Kubewatcher event reliability.  i.e. what happens when you get an event but the function had an error?  Or kubewatcher itself was down? There are several possible approaches here:
a. No reliability, i.e. it's the user's problem.  Practically this would mean the user has to write some sort of poll on the objects they're watching to reconcile their view of the state.  This may be hard to get right for every webhook implementer.
b. Kubewatcher persists (in etcd?) the event.Object.Metadata.ResourceVersion of the last successfully acknowledged watch event.  Assumes resourceVersion is monotonically increasing; it looks like it is but I haven't verified it.
c. Kubewatcher takes events and sends them into real message queue: AMQP/NATS.io Streaming/Kafka/etc.  Some of these queues are a fair amount of operational complexity for the user, so their usage should be optional in some way.

With the latest changes the publisher is an interface.  Currently there's only a webhook publisher satisfying this interface.  WebhookPublisher does best-effort delivery but drops events if it can't reach the endpoint.  #64 will track the work of using a message queue, probably nats-streaming.
#63 will track separating out the kubewatcher service from fission.


IDEM-9

#9

As discussed with @pondpiu and @xiangzhe0812 the implementation will change. Probably new PRs


Fix -debug-prefix-map handling

Previously only the values were passed through not the options as well.
This also adds the validation from Driver.cpp that they are correctly
formatted.

@swift-ci test


Search extensions

Codecov Report

Merging #57 (4f94ab6) into master (528d656) will increase coverage by 0.10%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #57      +/-   ##
==========================================
+ Coverage   80.68%   80.79%   +0.10%
==========================================
  Files          49       49
  Lines        4494     4509      +15
  Branches      563      565       +2
==========================================
+ Hits         3626     3643      +17
+ Misses        651      650       -1
+ Partials      217      216       -1

Impacted Files
Coverage Δ

...monMain/kotlin/dev/evo/elasticmagic/SearchQuery.kt
97.71% <100.00%> (+0.09%)
:arrow_up:

...ev/evo/elasticmagic/compile/SearchQueryCompiler.kt
93.75% <100.00%> (-0.45%)
:arrow_down:

...n/kotlin/dev/evo/elasticmagic/query/Expressions.kt
54.54% <100.00%> (+1.42%)
:arrow_up:

...ev/evo/elasticmagic/compile/CreateIndexCompiler.kt
74.41% <0.00%> (-6.98%)
:arrow_down:

...o/elasticmagic/transport/ElasticsearchException.kt
39.39% <0.00%> (-6.07%)
:arrow_down:

.../evo/elasticmagic/compile/UpdateMappingCompiler.kt
93.33% <0.00%> (-3.34%)
:arrow_down:

...in/kotlin/dev/evo/elasticmagic/compile/Compiler.kt
82.45% <0.00%> (-1.76%)
:arrow_down:

...lin/dev/evo/elasticmagic/compile/ActionCompiler.kt
56.66% <0.00%> (-1.67%)
:arrow_down:

...Main/kotlin/dev/evo/elasticmagic/aggs/Histogram.kt
85.78% <0.00%> (-1.48%)
:arrow_down:

... and 1 more

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 528d656...4f94ab6. Read the comment docs.


What if I don't use IIS?

I use Domino as a web server. Is there a way to specify the path where the answer file will be created?
letsencrypt-win-simple seems to automatically decide to put the answer file in its well-known...... directory then tell the ACME server to check immediately, not giving me a chance to copy it to the proper directory of the web server.

The --webroot switch is your friend. I guess you are using v1.9.6? v1.9.7 should have asked you for the path if none was provided.

In deed, turns out I have been using an old release (by mistake).
Thank you!


cluster-up: Unify detection of podman or docker as runtime

What this PR does / why we need it:
These changes unify the detection of podman or docker as runtime. This
makes 'make cluster-up' and 'make cluster-sync' always use the same
runtime. Prior to these changes 'make cluster-up' would have used docker
while 'make cluster-sync' would have used podman if both were installed
at the same time and podman.socket was not available.
These changes also set the path of the podman's socket to
'${XDG_RUNTIME_DIR}/podman/podman.socket' so podman can be started with
'systemctl start --user podman.socket' which is the standard way of
starting podman as user on distributions using systemd.
Which issue(s) this PR fixes
Special notes for your reviewer:
Release note:

NONE

See also https://github.com/kubevirt/kubevirtci/pull/741

@iholder-redhat I tested it locally on FC35 and it worked fine with rootful podman. Rootless podman still had networking problems during make cluster-up. Using the podman.sock is a convenient way to switch between rootless and rootful podman. [1]
[1] https://github.com/kubevirt/kubevirtci/blob/main/PODMAN.md

/retest

Hi @0xFelix, thanks for the PR.
What are the preliminary steps required to run make cluster-up and make cluster-sync using podman?
I've found this document you co-wrote.

Hi @orelmisan
Right, the document outlines all necessary steps. It could be included in the kubevirt/kubevirt repo too?

IMO it would be nice to have it in getting-started or some other file under the docs directory.
@enp0s3 could you please provide guidance?

/retest

I changed to PR so every call to podman uses a socket. This guarantees that rootless and rootful podman are not mixed. It is up to the user to provide a podman.socket which is either rootless or rootful. See also https://github.com/kubevirt/kubevirtci/pull/757.
Additionally I added a note to getting-started.

/assign

/approve

/retest

Great work thanks @0xFelix
Would you have the honors please to update https://github.com/kubevirt/kubevirtci/blame/main/PODMAN.md#L11 ?
It says it doesn't work with rootless still but it does thanks to this PR

Thank you @oshoval :+1:
Unfortunately the documentation is right. It does not work 100% with rootless podman. :(
The cluster is not able to access external resources when running in rootless podman. However as long as the cluster does not need external resources it works fine.


JS error when OverflowMenuItem click causes disabled state change

E.g. if i have an item that closes files, but is only enabled if files are opened:

<ToolbarMenu icon={Menu20} iconDescription="Menu">
	<!-- ... -->
	<ToolbarMenuItem on:click={() => data = []}
		disabled={data.length == 0}>
		Close files
	</ToolbarMenuItem>
</ToolbarMenu>```

An error happens in this callback, because ref is null:
// in /OverflowMenu/OverflowMenuItem.svelte
afterUpdate(() => {
  if (primaryFocus) {
    ref.focus();
  }
});

My suspicion is that the disabled change causes this callback to be executed after the menu has already been closed and the DOM discarded. The same could probably happen for the other properties as well.
Maybe just make that call defensive?
afterUpdate(() => {
  if (primaryFocus && ref != null) {
    ref.focus();
  }
});

Good catch. Thanks for reporting this!

Fixed in v0.38.2


[build] Avoid types generation from interferring with itself (alternative to 30200)

Another way to solve https://github.com/mui-org/material-ui/pull/30200
Just remove the -b flag to avoid referenced projects from being built. It will keep using the buildTypes script for each package. But this requires lerna to build the packages in order, so we can't use the --parallel flag. Let's see what the impact is on performance.
We could look into using https://turborepo.org/ to maximize parallelization of these build scripts.

See https://github.com/mui/material-ui/pull/30200#issuecomment-1609088857


Adding 100vh to the visualization code feels better

import networkx as nx
from pyvis.network import Network
import random
G = nx.read_graphml('./test_ollama_t2/graph_chunk_entity_relation.graphml')
net = Network(height="100vh", notebook=True)
net.from_nx(G)
for node in net.nodes:
node['color'] = "#{:06x}".format(random.randint(0, 0xFFFFFF))
net.show('knowledge_graph.html')
Now it can be displayed in full screen

Thanks!


I2C byte write return value

The return value for the i2c_byte_write in i2c_api.h does not match the documentation for the write function in I2C.h.

Can you please be more specific, I'll have a look

/** Write single byte out on the I2C bus
 *
 *  @param data data to write out on bus
 *
 *  @returns
 *    '1' if an ACK was received,
 *    '0' otherwise
 */
int write(int data);

/** Write one byte.

@param obj The i2c object
@param data Byte to be written
@return 1 if NAK was received, 0 if ACK was received, 2 for timeout.
*/
int  i2c_byte_write(i2c_t *obj, int data);

Any update on this?

Please say something. I think it's pretty obvious that there's something wrong here.

The problem comes:
int I2C::write(int data) {
    return i2c_byte_write(&_i2c, data);
}

Looking at HAL implementations, the documentation for the i2c_byte_write is wrong and should be fixed. The documentation to HAL was added later, so many implementation should follow what write() method defines. There are some implementations (KL25Z) which has it reversed, we should fix it. Thanks for reporting.

Here's summary from our targets implementations:
Silabs - ack = 1
Freescale - ack = 0
Atmel  - ack = 0
STM - can't guess from the code, seems like timeout is 0 (might mean its nak), ack = 1 ?
NXP - ack = 1
I got a fix for the documentation, and we might need to fix all those targets.


real time collaboration?

how?

Hi there are two branches in the repo names collab_1 and collab_2 which seem to be ones where collaborative editing was being implemented.  We could see collaboration work with these, but with inconsistencies.  Is there any update on these branches?  Whether any further work shall be done on these?  Also are there any known issues?  And why two branches 1 and 2 for this.. Any feedback much appreciated

any update on this? @hedgerwang


Linux desktop app crashes when disconnecting from 2nd monitor

Every time I disconnect my laptop from a second monitor, Toggl Desktop crashes. I'm running Toggl on Ubuntu 15.10.
linux_native_app/7.3.247
Reported with desk case #247230

Dear all,
I can confirm this issue on Ubuntu 15.10.
Steps to reproduce:

Launch Toogl Desktop while being connected to an external monitor.
Disconnect the external monitor.
Click on the tray indicator icon to start a new task.

At this stage, Toggl Desktop will crash.

This occurs also on Ubuntu 14.04.
Sometimes the whole Ubuntu desktop and all open windows freeze so that only mouse cursor moves.
Only way to recover is to press Ctrl + Alt + F1 and sudo kill -9 <toggl process id>

duplicate of #1721


Feature: Add css class to horizontal rule node for targeted styling

A horizontal rule element is not given any editor specific class name to target the styling. Adding a class similar to other nodes would allow to target the hr inside editor without effecting all other hr elements of the application.

Can I Work On It.

@Rbcoder1 Sure!

Can i work on it?

Hi @madhusudhand , can you give me the file/directory of the code which responsible for rendering the horizontal rule so that I can work on it. Thanks

hi @madhusudhand ,are you talking about api page  ?

I can fix this issue
can you assign me

@acywatson I am interested to work on it.

I want to work on this, can you assign me this issue?

Issue description:
A horizontal rule element when exported to HTML/DOM is not given any editor specific class name to target the styling, additionally it does not work consistently with paragraph element.
Workaround:
Use pure CSS by just using selectors specific to your editor contentEditable.
.my-editor hr {
// my styles
}

Expected result:
When converting horizontal rule node to HTML (or using exportDOM())
 element shall have class based on the applied theme. Ex:

Code refs:

HR code: https://github.com/facebook/lexical/blob/4c30b5215f0269c069c6c01f5eea973163a77321/packages/lexical-react/src/LexicalHorizontalRuleNode.tsx#L104
Paragraph code: https://github.com/facebook/lexical/blob/4c30b5215f0269c069c6c01f5eea973163a77321/packages/lexical/src/nodes/LexicalParagraphNode.ts#L46

I want to work on it, assign me

so i want to add a class in Horizontal Rule when it converted into HTML/DOM


Make HikariConfig able to retrieve passwords dynamically from a password supplier

This patch makes HikariConfig able to retrieve passwords from a provided password supplier at runtime when getPassword is called. This is useful for scenarios where expiring database passwords are dynamically generated at runtime (e.g. RDS access tokens) and one wants to avoid having to create a new DataSource or scheduling a task that periodically updates the password via HikariConfigMXBean.

Found this PR while trying to integrate AWS Secrets Manager with auto-rotating credentials. It would help a lot.
In the meantime, for those looking for a workaround, configuring Hikari with a custom DataSource that handles dynamic credentials seems to work.

@marcioos With the addition of a "getter" for the password supplier, I am prepared to merge this pull request.

I like where this is going because I too am using Hikari and need to support AWS SecretsManager based password rotation. Be aware, however, that AWS describes several scenarios for rotation. If changing only the password (which the changes above seem to support) then a small amount of downtime as the password change is applied is possible.
Other options include rotating between two sets of credentials so that the username and password are changing together, so the username would need to change as well. However, having two getters that could fetch and external data opens up a race condition, so perhaps there is an option to obtain a pair?

Any plans to proceed with this PR?

Hi,
I'm currently working on a project that uses AWS Aurora (MySQL flavor) and uses AWS Secrets Manager service to rotate passwords every so often. My current implementation to integrate both services with HikariCP is to have a wrapper around the HikariDataSource, and on getConnection() check for SQLExceptions with a 1045 error code. This error code represents a DBAcesssDenied in MySQL. When this exception occurs, I will fetch the new username/password from AWS, and then through the HikariConfigMXBean change those properties at runtime.
That said, I've manage to get this working, however, I'm not completely satisfied. The main reason is because when I try to acquire a new connection with expired/wrong credentials the HikariDataSource#getConnection method will keep retrying with those bad credentials until a ConnectionTimeout occurs.
I'm fairly new to HikariCP, and from my current understanding, it seems like there is no way to avoid this loop right ? Do any of you guys have any suggestions apart from simply reducing the connection timeout ?
Let me know your thoughts,
Thanks!

Great to see this was already opened, what is missing to get this merged and made available?

This effort would be really helpful for my team, but it doesn't quite do enough to settle the issue of dynamic credentials completely.  We are currently wrapping the underlying DataSource in order to intercept the getConnection() invocations, and it would be great for HikariCP to support dynamic credentials natively.  This PR doesn't quite address our problem, however, because we need both the username and the password to be dynamically resolved (we alternate between two application users so that we can roll them more seamlessly).  It seems like @brettwooldridge is reluctant to add more surface area to the Hikari API, so to me it would be short-sighted to support a password supplier without addressing usernames. I would like to see some kind of CredentialSupplier (so that both the password and username can be provided together, guaranteeing that they are not out of sync).  I'm curious whether anyone else also has this problem?

Given the considerations from @brettwooldridge and my lack of time to work on the suggested improvements, I'm thinking about just closing this pull request. Also, I'm not sure if this patch has everything needed to make the feature work correctly. I haven't checked if it is necessary to recreate the datasource or start a periodic task that keeps updating the ConfigMXBean.

Any plans to merge it into the master?

I was working on getting RDS IAM working with Hikari and came across this thread.  I was able to get it working (for MySQL at least) with no code changes using the AWS IAM Credential Plugin provided in the MariaDB Connector/J driver which handles generating, caching and refreshing the auth token - I put a little more detail here.
But I also saw that you can implement your own MariaDB CredentialPlugin - this might be an option for others upthread who are trying to pull from AWS Secrets Manager, etc.


fix normalization in TSNE

The current version contains an error in normalization. Need to subtract mean first.

Thank you! merged


nixos/vmagent: use dynamic user and cache directory, cleanup

Description of changes

The vmagent module currently uses a full user instead of dynamic user, which is unnecessary.
Also currently it's not possible to use the module when not using remote_write.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I do think it might be nice to squash the two edits to the module into one commit

I do think it might be nice to squash the two edits to the module into one commit

I wouldn't do that, as both a unrelated changes. If something doesn't work, it might be easier to understand the changes.

rebased and fixed a typo. I will merge now, as this has two approvals including one by a maintainer, so this gets in 24.05.


[chip-test] - chip_sw_rv_core_ibex_double_fault

Test point name
chip_sw_rv_core_ibex_double_fault
Host side component
TBD
OpenTitanTool infrastructure implemented
Unknown
Contact person
gac
Checklist
Please fill out this checklist as items are completed. Link to PRs and issues as appropriate.

[ ] Check if existing test covers most or all of this testpoint (if so, either extend said test to cover all points, or skip the next 3 checkboxes)
[ ] Device-side (C) component developed
[ ] Bazel build rules developed
[ ] Host-side component developed
[ ] HJSON test plan updated with test name (so it shows up in the dashboard)
[ ] Test added to dvsim nightly regression (and passing at time of checking)

Test description
Verify the functionality of the ibex double fault dump.

Purposely create an ibex double exception during execution, by performing an unmapped read and in the exception handler perform another unmapped read.
Ensure the rstmgr fault dump correctly captures both dumps correctly and indicates the previous dump is valid.

can we double check if this test is a duplicate of this one here?
Or whether the test could be enhanced to satisfy the requirements of both?

I beleive it is dublicated. I discussed with @HU90m and we beleive there's room for improvement in the existing chip_sw_rstmgr_cpu_info, thats why this issue is still opened.

sounds great!

Passed three nightly regressions.


Update github docs v2 to reflect changes in unity actions since v2 alpha

Is your feature request related to a problem? Please describe.
We have recently introduced versioning into the docs. Unity actions on GitHub now have v1 and v2.

v1 should no longer be changed
v2 should be updated to show latest behaviour with the new images and use repo version v2.0-alpha or higher.

I raised https://github.com/game-ci/documentation/pull/99 with the assumption users will be able to use a simple v2 as the version.

I have tried that, but this in fact does not work as far as I know. I remember trying it and failing it. (this may have been due to the -alpha suffix though).

Closing this as #99 is merged.


Req. #07 - Investigate the utility of ISA extensions other than RVV

Description: Investigate whether any RISC-V extensions other than RVV are relevant to the purpose of our accelerator card.
Artifact: Any RISC-V extensions (other than RVV) that may be useful in our project will be reported, along with the motivation for including them, in a discussion page. The discussion page will be linked in the end-of-sprint release on GitHub and reported to the GTA in the meeting the following day. Supporting these extensions may become a goal in the later stages of our project.
Story Points: 8

Discussion page opened at https://github.com/amacgillivray/linear_algebra_accelerator/discussions/56


fix: move "notification" event args types back into zwave-js package

They weren't used anywhere else and this makes more sense for the event handler definitions

@zwave-js-bot approve


Fix failing test by initializing default header values for ClientIp middleware

Thank you! (and sorry for this stupid bug)


WIP : Register models for admin

[x] Register data models for admin
[x] Register core models for admin
[ ] Customize data models listing / edition
[ ] Customize core models listing / edition
[ ] Rebase to master

Coverage increased (+0.03%) to 98.953% when pulling 134d84f3f948e33c342fe6fab773cfd9cff67bd9 on Data_ModelAdmin into eeebb9e3d1824d1759808a173c10bec9b803ee9f on master.

I think you can pursue your work in this branch/PR (with the WIP flag). Also, don't forget to rebase your branch:
# From the Data_ModelAdmin branch
$ git checkout master
$ git pull origin master
$ git checkout -
$ git rebase master

Coverage increased (+0.03%) to 98.953% when pulling f4c8b5f3b5e5971b1256d11688e2a034ba70960e on Data_ModelAdmin into eeebb9e3d1824d1759808a173c10bec9b803ee9f on master.

Coverage remained the same at 100.0% when pulling 03af918f7e81ccfa3c7c1e3cc9ddbeb322f0de4a on Data_ModelAdmin into 47f351a7f72acf11c47d839989fd90be19be7d54 on master.

Normally, the rebase is ok.

Coverage decreased (-0.2%) to 99.847% when pulling e4eaceb56ac3962250c6e40b8e97f392937d2863 on Data_ModelAdmin into 47f351a7f72acf11c47d839989fd90be19be7d54 on master.

Coverage decreased (-0.7%) to 99.307% when pulling 0414829c51d38917a573b493b7e40352bcb85773 on Data_ModelAdmin into 27a61cb429b6371b36cb8a13215ade58dd316528 on master.

Coverage decreased (-2.3%) to 97.742% when pulling 8706049cda2e0661a82248f529e8796c8c81939e on Data_ModelAdmin into 27a61cb429b6371b36cb8a13215ade58dd316528 on master.

Coverage decreased (-2.3%) to 97.742% when pulling 97b51c2903bba8033c92df6f9ef3d7b83948e3b3 on Data_ModelAdmin into 27a61cb429b6371b36cb8a13215ade58dd316528 on master.

Coverage decreased (-2.3%) to 97.748% when pulling 76c2bdec0945b2ca1fa71adc198a679657a5456d on Data_ModelAdmin into 27a61cb429b6371b36cb8a13215ade58dd316528 on master.

Coverage decreased (-2.3%) to 97.748% when pulling 43be9ed4587937229ca98357cc5c0f3f6a98baa4 on Data_ModelAdmin into 27a61cb429b6371b36cb8a13215ade58dd316528 on master.

Last question: why did you update the docs/pixel-db.pdf document?

It is not voluntary... Sorry :confused:

Coverage decreased (-2.02%) to 97.978% when pulling 13dcb77e0fc0d405197593a7c49ebae1b6110f83 on Data_ModelAdmin into 27a61cb429b6371b36cb8a13215ade58dd316528 on master.

Coverage decreased (-1.9%) to 98.103% when pulling 128d925294a9964d16aefe4ae6e52285da2e7fe5 on Data_ModelAdmin into 27a61cb429b6371b36cb8a13215ade58dd316528 on master.

Coverage decreased (-1.9%) to 98.103% when pulling d1bd008073776c4fc09e4970b609454654244e0a on Data_ModelAdmin into 27a61cb429b6371b36cb8a13215ade58dd316528 on master.

Coverage decreased (-1.9%) to 98.103% when pulling d1bd008073776c4fc09e4970b609454654244e0a on Data_ModelAdmin into 27a61cb429b6371b36cb8a13215ade58dd316528 on master.

Coverage decreased (-1.9%) to 98.108% when pulling 59e521a6eeec7472a42131ba8d36f8ca64e47300 on Data_ModelAdmin into 27a61cb429b6371b36cb8a13215ade58dd316528 on master.

Coverage decreased (-1.9%) to 98.108% when pulling 79921c6dcef8739e0fb6dbe31fe048659181e554 on Data_ModelAdmin into 27a61cb429b6371b36cb8a13215ade58dd316528 on master.

Coverage decreased (-0.6%) to 99.398% when pulling b71155f49a886e70e766fa31f87e6c4397d718ab on Data_ModelAdmin into 722e652dccb2a19e06493e98e6970bcb594f2739 on master.

Coverage decreased (-0.6%) to 99.398% when pulling 486613951ac8b1584720b23c2a03d427bdf38162 on Data_ModelAdmin into 71b925325cf3c3f8a8425ed82226507d44212d67 on master.

Coverage remained the same at 100.0% when pulling e0ae8bba500d2445f4e37db0c39270f9c64a8b7e on Data_ModelAdmin into 71b925325cf3c3f8a8425ed82226507d44212d67 on master.

Coverage remained the same at 100.0% when pulling 1d435fe7911d254a615d22cf6c76a03396a97841 on Data_ModelAdmin into 71b925325cf3c3f8a8425ed82226507d44212d67 on master.

Coverage remained the same at 100.0% when pulling 501282d87efc64de567cc30e43ea61bbfe616158 on Data_ModelAdmin into 71b925325cf3c3f8a8425ed82226507d44212d67 on master.

Coverage remained the same at 100.0% when pulling 7e1db0f39aa55050a99d1e1f7aa613067ff64bd2 on Data_ModelAdmin into 71b925325cf3c3f8a8425ed82226507d44212d67 on master.


[SDK 2.0] merge changes from next to main

Description

[!IMPORTANT]
This PR needs to be merged by a maintainer as we need to merge it non-squashed. Otherwise we'll not have the full history from next on main.

Updates main with the latest changes from next, all changes here are pre-reviewed already, except for the changes to

README.md (manually merged from README_NEXT.md into README.md, adapted warning about this being the 2.0 development branch).
CHANGELOG.md (manually merged from CHANGELOG_NEXT.md into CHANGELOG.md).
v1.x develoment will continue through bugfix backports and security fixes only on the v1.x branch.

Tracking issue #5148

This is a lot... but i think it all looks good to me. There's no great way to review a 3000 line diff that touches 146 files 🤣

True - for future reference: all of these commits that are merged here from next went through the proper review process that matches the one on main. So the reveiew in this case would consist mostly just verifying that I did not add anything extra that should not be there - one "okay" way would be to look at the diff for the head of this branch and next - that diff should just match my last commit here (https://github.com/open-telemetry/opentelemetry-js/pull/5284/commits/2610521b1638265dd5f12bcdd72e5a36d19157c7), and then reviewing that diff. 🙂

This is a lot... but i think it all looks good to me. There's no great way to review a 3000 line diff that touches 146 files 🤣

True - for future reference: all of these commits that are merged here from next went through the proper review process that matches the one on main. So the reveiew in this case would consist mostly just verifying that I did not add anything extra that should not be there - one "okay" way would be to look at the diff for the head of this branch and next - that diff should just match my last commit here (2610521), and then just reviewing that diff. 🙂

thats basically what i did. I also looked for things like merge conflict markers, but you'd expect most basic merge conflicts to break the build anyway so i'm reasonably confident


[observatory] feature request: upload result to a local server, so that we can analyse offline

it's a feature request instead of a bug, so i don't post the environment variables. but i'll do that if you need it.
for the great profiler observatory, we can only analysis on the fly in a single device, and it's up to the single developer/tester to care about the profiling data. he may or may not do it. we cannot analysis the profiling data for all the test devices of developers and testers as a whole. so i believe it's a giant waste of the profiling data.
i wonder if it's possible to upload the profiling data to a local server, so that we as a team can analyse the profiling data offline and don't waste the data.
l'll edit my post if it's wrong or not clear.
thanks for reading.

I don't think this is within scope for Dart SDK. vmservice protocol provides you a way to automatically pull profiling data from a running program, but we have no plans to build ready made server side solutions for aggregating profiling data from a fleet of devices.

I don't think this is within scope for Dart SDK. vmservice protocol provides you a way to automatically pull profiling data from a running program, but we have no plans to build ready made server side solutions for aggregating profiling data from a fleet of devices.


float3x3 implement inconsistent for dx and cuda

see the test case src/test/feat/test_buffer.cpp in "next-test" branch, the test case "buffer::float3x3" will act inconsistently in dx and cuda backend:
compile with xmake and run with xmake run test_feat -tc="buffer::float3x3 -sc=dx" or  xmake run test_feat -tc="buffer::float3x3 -sc=cuda", as shown in figure:

this test case will fill two float3x3 a and b and add them together, then save the result to c. The value in c shall be all 2.0f as expected/
dx backend will pass the test case as expected but cuda backend will find itself mistaken when index = 3 or 7, maybe because the value is casted in 4 but not 3?

the copy_from method for float3x3 is ambious for dx and cuda backends

The test is in-correct because reading alignment bytes is undefined behavior.


New npm release in order to use mocha 3

Since #106 is merged a new npm release would be wonderful so we can start using it. TA

It's just a devdependency, mocha is set as peerDependency, so you can already use mocha@3. I'm already doing it in multiple projects.

True, make sense. Thanks for clearing that up


webpack_public_path is ignored in file-loader 0.11.2

I'm loading an <img src="..."> from a .vue component with vue-loader, but I think it doesn't matter where the asset is coming from.
In file-loader 0.10.1 __webpack_public_path__ works, output of the module:
/* 87 */
/***/ (function(module, exports, __webpack_require__) {

module.exports = __webpack_require__.p + "images/631bf234f883acfbc030ae0866517933.png";

/***/ }),

In file-loader 0.11.1, __webpack_public_path__ is honored, but publicPath is prepended. I think that is covered by #160 and is not what this issue is about. Module output:
/* 87 */
/***/ (function(module, exports, __webpack_require__) {

module.exports = __webpack_require__.p + "assets/images/631bf234f883acfbc030ae0866517933.png";

/***/ }),

Now in file-loader 0.11.2, __webpack_public_path__ is completely ignored (but publicPath is still prepended):
/* 87 */
/***/ (function(module, exports) {

module.exports = "assets/images/631bf234f883acfbc030ae0866517933.png";

/***/ }),

I just found out that publicPath can take a function, which seems like a much nicer solution anyway, so maybe this is on purpose and __webpack_public_path__ is kind of deprecated?

@AndreKR can your create minimum reproducible test repo, thanks!

Closing due to inactivity. Please test with latest version and feel free to reopen if still regressions. Thanks!


Certain MIDI files don't work at all with Magenta.

I've found quite a lot of the MIDI files I have don't work at all, especially ones I've made myself using Ableton. Does anyone have any suggestions to fix this? I've tried a few things like converting between MIDI formats 0 and 1 but nothing seems to work.
In Drums_RNN for instance everything seems to work up until the generation of training_drum_tracks.tfrecord which for some MIDI files contains data but for most remains blank.

I believe drum tracks need to be on Channel 10 for Magenta to recognize them. Give that a shot and reopen if you still have an issue.

It doesn't look like that's the problem. I have some MIDI files which use channel 10 that don't work either, I also tried converting the others to channel 10 without any luck.