"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-SE",
"state" : "Shutdown",
"name" : "iPhone SE"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/714BA482-C3FA-4CDF-A002-8BD4D42559D1/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/714BA482-C3FA-4CDF-A002-8BD4D42559D1",
"udid" : "714BA482-C3FA-4CDF-A002-8BD4D42559D1",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-7",
"state" : "Shutdown",
"name" : "iPhone 7"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/AB0714F4-E7FF-43D3-9863-B5AB075F1933/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/AB0714F4-E7FF-43D3-9863-B5AB075F1933",
"udid" : "AB0714F4-E7FF-43D3-9863-B5AB075F1933",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-7-Plus",
"state" : "Shutdown",
"name" : "iPhone 7 Plus"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/EEE91E10-0896-48B2-BA1A-B3C0504861A4/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/EEE91E10-0896-48B2-BA1A-B3C0504861A4",
"udid" : "EEE91E10-0896-48B2-BA1A-B3C0504861A4",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-8",
"state" : "Shutdown",
"name" : "iPhone 8"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/CF0E54A9-99CA-4C72-AE98-5B35FA170C38/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/CF0E54A9-99CA-4C72-AE98-5B35FA170C38",
"udid" : "CF0E54A9-99CA-4C72-AE98-5B35FA170C38",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-8-Plus",
"state" : "Shutdown",
"name" : "iPhone 8 Plus"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/427C0BDA-D563-4C2F-B00F-A23A7A2021F1/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/427C0BDA-D563-4C2F-B00F-A23A7A2021F1",
"udid" : "427C0BDA-D563-4C2F-B00F-A23A7A2021F1",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-X",
"state" : "Shutdown",
"name" : "iPhone X"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/A9886C5B-F16E-4173-A40D-F1AED17B99D2/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/A9886C5B-F16E-4173-A40D-F1AED17B99D2",
"udid" : "A9886C5B-F16E-4173-A40D-F1AED17B99D2",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-XS",
"state" : "Shutdown",
"name" : "iPhone XS"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/A93C53D6-6378-4F0E-B6F3-B9C44E5405A1/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/A93C53D6-6378-4F0E-B6F3-B9C44E5405A1",
"udid" : "A93C53D6-6378-4F0E-B6F3-B9C44E5405A1",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-XS-Max",
"state" : "Shutdown",
"name" : "iPhone XS Max"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/7AAC8E8C-3184-4870-B055-6BE622E8821E/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/7AAC8E8C-3184-4870-B055-6BE622E8821E",
"udid" : "7AAC8E8C-3184-4870-B055-6BE622E8821E",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-XR",
"state" : "Shutdown",
"name" : "iPhone XR"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/4A5B488F-5440-4F1D-85B4-C0C5F4024F1D/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/4A5B488F-5440-4F1D-85B4-C0C5F4024F1D",
"udid" : "4A5B488F-5440-4F1D-85B4-C0C5F4024F1D",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Air",
"state" : "Shutdown",
"name" : "iPad Air"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/8AB0C564-4304-40B3-98D4-E20C672AE2BF/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/8AB0C564-4304-40B3-98D4-E20C672AE2BF",
"udid" : "8AB0C564-4304-40B3-98D4-E20C672AE2BF",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Air-2",
"state" : "Shutdown",
"name" : "iPad Air 2"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/9A200EE8-426C-4D35-9DDA-A7A0DB6A4F95/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/9A200EE8-426C-4D35-9DDA-A7A0DB6A4F95",
"udid" : "9A200EE8-426C-4D35-9DDA-A7A0DB6A4F95",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro--9-7-inch-",
"state" : "Shutdown",
"name" : "iPad Pro (9.7-inch)"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/3787E177-82D1-4A60-9A3B-D390A24C8540/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/3787E177-82D1-4A60-9A3B-D390A24C8540",
"udid" : "3787E177-82D1-4A60-9A3B-D390A24C8540",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro",
"state" : "Shutdown",
"name" : "iPad Pro (12.9-inch)"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/ABB454B6-8D25-437A-A590-22266C63322E/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/ABB454B6-8D25-437A-A590-22266C63322E",
"udid" : "ABB454B6-8D25-437A-A590-22266C63322E",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad--5th-generation-",
"state" : "Shutdown",
"name" : "iPad (5th generation)"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/E38894F3-E076-4FC0-8564-82421341AD2A/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/E38894F3-E076-4FC0-8564-82421341AD2A",
"udid" : "E38894F3-E076-4FC0-8564-82421341AD2A",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro--12-9-inch---2nd-generation-",
"state" : "Shutdown",
"name" : "iPad Pro (12.9-inch) (2nd generation)"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/268EFC34-B313-417D-8D45-8704DA368D09/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/268EFC34-B313-417D-8D45-8704DA368D09",
"udid" : "268EFC34-B313-417D-8D45-8704DA368D09",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro--10-5-inch-",
"state" : "Shutdown",
"name" : "iPad Pro (10.5-inch)"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/070CA5E0-9452-4288-979A-E78A7BB799D1/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/070CA5E0-9452-4288-979A-E78A7BB799D1",
"udid" : "070CA5E0-9452-4288-979A-E78A7BB799D1",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad--6th-generation-",
"state" : "Shutdown",
"name" : "iPad (6th generation)"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/213CDB56-6A4E-4A87-B3E0-389270591F4B/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/213CDB56-6A4E-4A87-B3E0-389270591F4B",
"udid" : "213CDB56-6A4E-4A87-B3E0-389270591F4B",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro--12-9-inch---3rd-generation-",
"state" : "Shutdown",
"name" : "iPad Pro (12.9-inch) (3rd generation)"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/CFCFED52-2566-472C-8BB4-80A4881054D0/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/CFCFED52-2566-472C-8BB4-80A4881054D0",
"udid" : "CFCFED52-2566-472C-8BB4-80A4881054D0",
"isAvailable" : false,
"state" : "Shutdown",
"name" : "iPad Pro (11-inch)"
}
],
"com.apple.CoreSimulator.SimRuntime.watchOS-5-0" : [
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/EF0C6D2C-F7E6-4BCF-BFBD-B2812377A2C3/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/EF0C6D2C-F7E6-4BCF-BFBD-B2812377A2C3",
"udid" : "EF0C6D2C-F7E6-4BCF-BFBD-B2812377A2C3",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-2-38mm",
"state" : "Shutdown",
"name" : "Apple Watch Series 2 - 38mm"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/95FDA285-95E6-409D-820B-2C769C7295CA/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/95FDA285-95E6-409D-820B-2C769C7295CA",
"udid" : "95FDA285-95E6-409D-820B-2C769C7295CA",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-2-42mm",
"state" : "Shutdown",
"name" : "Apple Watch Series 2 - 42mm"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/84641CF3-E7D3-4FAD-A9F3-4CC545C9F781/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/84641CF3-E7D3-4FAD-A9F3-4CC545C9F781",
"udid" : "84641CF3-E7D3-4FAD-A9F3-4CC545C9F781",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-3-38mm",
"state" : "Shutdown",
"name" : "Apple Watch Series 3 - 38mm"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/5DC929FB-DFB2-4F70-91E5-FE4EF41E8910/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/5DC929FB-DFB2-4F70-91E5-FE4EF41E8910",
"udid" : "5DC929FB-DFB2-4F70-91E5-FE4EF41E8910",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-3-42mm",
"state" : "Shutdown",
"name" : "Apple Watch Series 3 - 42mm"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/D1588F41-59E5-4665-8BA9-23677F9A4C65/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/D1588F41-59E5-4665-8BA9-23677F9A4C65",
"udid" : "D1588F41-59E5-4665-8BA9-23677F9A4C65",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-4-40mm",
"state" : "Shutdown",
"name" : "Apple Watch Series 4 - 40mm"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/8D93DC67-5ADE-4BD1-B2C8-ECC2DBEB6D94/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/8D93DC67-5ADE-4BD1-B2C8-ECC2DBEB6D94",
"udid" : "8D93DC67-5ADE-4BD1-B2C8-ECC2DBEB6D94",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-4-44mm",
"state" : "Shutdown",
"name" : "Apple Watch Series 4 - 44mm"
}
],
"com.apple.CoreSimulator.SimRuntime.iOS-13-3" : [
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/9E771F26-557B-4CD9-A73A-0E3C0A2CAC71/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/9E771F26-557B-4CD9-A73A-0E3C0A2CAC71",
"udid" : "9E771F26-557B-4CD9-A73A-0E3C0A2CAC71",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-8",
"state" : "Shutdown",
"name" : "iPhone 8"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/6D71B969-0BCE-4F09-B0BF-ABCB77F156B5/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/6D71B969-0BCE-4F09-B0BF-ABCB77F156B5",
"udid" : "6D71B969-0BCE-4F09-B0BF-ABCB77F156B5",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-8-Plus",
"state" : "Shutdown",
"name" : "iPhone 8 Plus"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/DD306105-7A13-4751-A104-CAEDA8796563/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/DD306105-7A13-4751-A104-CAEDA8796563",
"udid" : "DD306105-7A13-4751-A104-CAEDA8796563",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-11",
"state" : "Shutdown",
"name" : "iPhone 11"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/A613D339-C179-4D55-87E5-EDA70CC34D3B/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/A613D339-C179-4D55-87E5-EDA70CC34D3B",
"udid" : "A613D339-C179-4D55-87E5-EDA70CC34D3B",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-11-Pro",
"state" : "Shutdown",
"name" : "iPhone 11 Pro"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/BE26DA22-322B-4106-877D-700DA2BE31A3/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/BE26DA22-322B-4106-877D-700DA2BE31A3",
"udid" : "BE26DA22-322B-4106-877D-700DA2BE31A3",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-11-Pro-Max",
"state" : "Shutdown",
"name" : "iPhone 11 Pro Max"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/C61CED0F-B5E3-47FD-8455-3DD667E7D265/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/C61CED0F-B5E3-47FD-8455-3DD667E7D265",
"udid" : "C61CED0F-B5E3-47FD-8455-3DD667E7D265",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro--9-7-inch-",
"state" : "Shutdown",
"name" : "iPad Pro (9.7-inch)"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/A0C295A6-2A88-4B73-A382-7AF6FE286489/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/A0C295A6-2A88-4B73-A382-7AF6FE286489",
"udid" : "A0C295A6-2A88-4B73-A382-7AF6FE286489",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad--7th-generation-",
"state" : "Shutdown",
"name" : "iPad (7th generation)"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/C466E3CD-C490-4F82-B2CA-0BFB78B06583/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/C466E3CD-C490-4F82-B2CA-0BFB78B06583",
"udid" : "C466E3CD-C490-4F82-B2CA-0BFB78B06583",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro--12-9-inch---3rd-generation-",
"state" : "Shutdown",
"name" : "iPad Pro (12.9-inch) (3rd generation)"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/BE8BAB32-658B-4C63-A936-9F58CC009307/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/BE8BAB32-658B-4C63-A936-9F58CC009307",
"udid" : "BE8BAB32-658B-4C63-A936-9F58CC009307",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Air--3rd-generation-",
"state" : "Shutdown",
"name" : "iPad Air (3rd generation)"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/0B28B6EC-E9F6-4960-A86D-DE6475817F61/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/0B28B6EC-E9F6-4960-A86D-DE6475817F61",
"udid" : "0B28B6EC-E9F6-4960-A86D-DE6475817F61",
"isAvailable" : false,
"state" : "Shutdown",
"name" : "iPad Pro (11-inch)"
}
],
"com.apple.CoreSimulator.SimRuntime.tvOS-13-4" : [
{
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/E5628CF8-4218-494C-8CD3-9076489FB11F/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/E5628CF8-4218-494C-8CD3-9076489FB11F",
"udid" : "E5628CF8-4218-494C-8CD3-9076489FB11F",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-TV-1080p",
"state" : "Shutdown",
"name" : "Apple TV"
},
{
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/7C32B8BE-F363-4BF2-B859-128BC955E3DB/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/7C32B8BE-F363-4BF2-B859-128BC955E3DB",
"udid" : "7C32B8BE-F363-4BF2-B859-128BC955E3DB",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-TV-4K-4K",
"state" : "Shutdown",
"name" : "Apple TV 4K"
},
{
"dataPath" : "/Users/vasilich/Library/Developer/CoreSimulator/Devices/D6572C74-A48C-438A-927E-95B0090FCF79/data",
"logPath" : "/Users/vasilich/Library/Logs/CoreSimulator/D6572C74-A48C-438A-927E-95B0090FCF79",
"udid" : "D6572C74-A48C-438A-927E-95B0090FCF79",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-TV-4K-1080p",
"state" : "Shutdown",
"name" : "Apple TV 4K (at 1080p)"
}
]
}
}
[+2457 ms] [
{
"simulator" : true,
"operatingSystemVersion" : "11.1 (15B87)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone7,2",
"identifier" : "806339FD-3D27-4B59-8C4C-4C25DA23F495",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-6-b4b5b9",
"modelName" : "iPhone 6",
"name" : "iPhone 6"
},
{
"simulator" : true,
"operatingSystemVersion" : "6.2 (17T256)",
"available" : true,
"platform" : "com.apple.platform.watchsimulator",
"modelCode" : "Watch4,3",
"identifier" : "8C37B229-904E-4AAD-9F7D-70D07F971265",
"architecture" : "i386",
"modelUTI" : "com.apple.watch-series4-1",
"modelName" : "Apple Watch Series 4 - 40mm",
"name" : "Apple Watch Series 4 - 40mm"
},
{
"simulator" : true,
"operatingSystemVersion" : "11.1 (15B87)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone6,1",
"identifier" : "5F038AF5-A3D6-40C3-B4ED-20714FADFC4F",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-5s-a1453-d4c5b3",
"modelName" : "iPhone 5s",
"name" : "iPhone 5s"
},
{
"simulator" : true,
"operatingSystemVersion" : "13.4 (17L255)",
"available" : true,
"platform" : "com.apple.platform.appletvsimulator",
"modelCode" : "AppleTV5,3",
"identifier" : "E5628CF8-4218-494C-8CD3-9076489FB11F",
"architecture" : "x86_64",
"modelUTI" : "com.apple.apple-tv-4",
"modelName" : "Apple TV",
"name" : "Apple TV"
},
{
"simulator" : true,
"operatingSystemVersion" : "11.1 (15B87)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad5,4",
"identifier" : "91A1916A-B836-405C-A1F5-5A2DA6FF543B",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipad-air2-a1567-b4b5b9",
"modelName" : "iPad Air 2",
"name" : "iPad Air 2"
},
{
"simulator" : true,
"operatingSystemVersion" : "13.4 (17E255)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone10,4",
"identifier" : "2C43137E-6FCE-417B-832D-382E9D4DF225",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-8-2",
"modelName" : "iPhone 8",
"name" : "iPhone 8"
},
{
"simulator" : true,
"operatingSystemVersion" : "13.4 (17L255)",
"available" : true,
"platform" : "com.apple.platform.appletvsimulator",
"modelCode" : "AppleTV6,2",
"identifier" : "7C32B8BE-F363-4BF2-B859-128BC955E3DB",
"architecture" : "x86_64",
"modelUTI" : "com.apple.apple-tv-4k",
"modelName" : "Apple TV 4K",
"name" : "Apple TV 4K"
},
{
"simulator" : true,
"operatingSystemVersion" : "13.4 (17E255)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad7,12",
"identifier" : "1CB697C2-DBFC-486E-AB7A-ADCF847661E4",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipad-7-wwan-1",
"modelName" : "iPad (7th generation)",
"name" : "iPad (7th generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "11.1 (15B87)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone8,2",
"identifier" : "FCA8D35E-A58B-49D0-9150-1772E7E59879",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-6s-plus-b9b7ba",
"modelName" : "iPhone 6s Plus",
"name" : "iPhone 6s Plus"
},
{
"simulator" : true,
"operatingSystemVersion" : "11.1 (15B87)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone10,5",
"identifier" : "674FB556-433E-40D5-8FB4-3EADAF25DD9C",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-8-plus-2",
"modelName" : "iPhone 8 Plus",
"name" : "iPhone 8 Plus"
},
{
"simulator" : true,
"operatingSystemVersion" : "11.1 (15B87)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad7,3",
"identifier" : "C65D5D3F-943F-43D2-AD1A-831F4A9671A9",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipad-pro-10point5-a1701-1",
"modelName" : "iPad Pro (10.5-inch)",
"name" : "iPad Pro (10.5-inch)"
},
{
"simulator" : true,
"operatingSystemVersion" : "6.2 (17T256)",
"available" : true,
"platform" : "com.apple.platform.watchsimulator",
"modelCode" : "Watch5,3",
"identifier" : "97529DE7-6B52-4340-94DC-20971714A46D",
"architecture" : "i386",
"modelUTI" : "com.apple.watch-series5-1",
"modelName" : "Apple Watch Series 5 - 40mm",
"name" : "Apple Watch Series 5 - 40mm"
},
{
"simulator" : true,
"operatingSystemVersion" : "11.1 (15B87)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone8,1",
"identifier" : "54C549A9-01A3-4074-AD84-369F1C528212",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-6s-b9b7ba",
"modelName" : "iPhone 6s",
"name" : "iPhone 6s"
},
{
"simulator" : true,
"operatingSystemVersion" : "11.1 (15B87)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone9,1",
"identifier" : "80453461-984B-4D4E-A00B-CFE24346F7F0",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-7-1",
"modelName" : "iPhone 7",
"name" : "iPhone 7"
},
{
"simulator" : true,
"operatingSystemVersion" : "13.4 (17E255)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone12,3",
"identifier" : "D4225890-D557-4053-B3B8-CFF07284BFA8",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-11-pro-1",
"modelName" : "iPhone 11 Pro",
"name" : "iPhone 11 Pro"
},
{
"simulator" : true,
"operatingSystemVersion" : "13.4 (17E255)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone12,5",
"identifier" : "2DDA4F7B-399F-4FFA-BFCA-C302D3D95F6B",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-11-pro-max-1",
"modelName" : "iPhone 11 Pro Max",
"name" : "iPhone 11 Pro Max"
},
{
"simulator" : true,
"operatingSystemVersion" : "13.4 (17E255)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad6,4",
"identifier" : "1508A8B6-24D9-4A69-9867-FB22A6D86C41",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipad-pro-9point7-a1674-b9b7ba",
"modelName" : "iPad Pro (9.7-inch)",
"name" : "iPad Pro (9.7-inch)"
},
{
"simulator" : true,
"operatingSystemVersion" : "13.4 (17E255)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad11,3",
"identifier" : "C893BF35-B2A5-4286-9F4F-3D3D8FFBAD2A",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipad-air3-wifi-1",
"modelName" : "iPad Air (3rd generation)",
"name" : "iPad Air (3rd generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "11.1 (15B87)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad7,1",
"identifier" : "EE964458-2122-4084-B616-B86A4BD0029F",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipad-pro-a1670-1",
"modelName" : "iPad Pro (12.9-inch) (2nd generation)",
"name" : "iPad Pro (12.9-inch) (2nd generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "13.4 (17E255)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone10,5",
"identifier" : "C2BDDBF8-944E-4D83-814D-8897BF5E0FA3",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-8-plus-2",
"modelName" : "iPhone 8 Plus",
"name" : "iPhone 8 Plus"
},
{
"simulator" : true,
"operatingSystemVersion" : "11.1 (15B87)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone9,2",
"identifier" : "D91C27DC-A02C-401D-94AE-8DC98968CB34",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-7-plus-1",
"modelName" : "iPhone 7 Plus",
"name" : "iPhone 7 Plus"
},
{
"simulator" : true,
"operatingSystemVersion" : "11.1 (15B87)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone8,4",
"identifier" : "5C7324FE-949A-45D3-8593-2ED74BBC9EA9",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-se-a1662-aeb1b8",
"modelName" : "iPhone SE",
"name" : "iPhone SE"
},
{
"simulator" : true,
"operatingSystemVersion" : "6.2 (17T256)",
"available" : true,
"platform" : "com.apple.platform.watchsimulator",
"modelCode" : "Watch4,4",
"identifier" : "1211AEE6-CCE5-41E3-9ED3-0E7B2915CEBA",
"architecture" : "i386",
"modelUTI" : "com.apple.watch-series4-1",
"modelName" : "Apple Watch Series 4 - 44mm",
"name" : "Apple Watch Series 4 - 44mm"
},
{
"simulator" : true,
"operatingSystemVersion" : "11.1 (15B87)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad6,4",
"identifier" : "945F3C0B-AE8D-4A52-81C9-54EBD9D99BBD",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipad-pro-9point7-a1674-b9b7ba",
"modelName" : "iPad Pro (9.7-inch)",
"name" : "iPad Pro (9.7-inch)"
},
{
"simulator" : true,
"operatingSystemVersion" : "11.1 (15B87)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone10,4",
"identifier" : "EF5A5BFD-9604-48B0-AA93-6E1740E11678",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-8-2",
"modelName" : "iPhone 8",
"name" : "iPhone 8"
},
{
"simulator" : true,
"operatingSystemVersion" : "6.2 (17T256)",
"available" : true,
"platform" : "com.apple.platform.watchsimulator",
"modelCode" : "Watch5,4",
"identifier" : "D433F9B9-C755-4F1A-BDDC-BC6E3BAE7901",
"architecture" : "i386",
"modelUTI" : "com.apple.watch-series5-1",
"modelName" : "Apple Watch Series 5 - 44mm",
"name" : "Apple Watch Series 5 - 44mm"
},
{
"simulator" : true,
"operatingSystemVersion" : "11.1 (15B87)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad4,2",
"identifier" : "A8436A93-3729-4838-B0C6-CFF7F9B5EC54",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipad-air-a1475-d7d9d8",
"modelName" : "iPad Air",
"name" : "iPad Air"
},
{
"simulator" : true,
"operatingSystemVersion" : "13.4 (17L255)",
"available" : true,
"platform" : "com.apple.platform.appletvsimulator",
"modelCode" : "AppleTV6,2",
"identifier" : "D6572C74-A48C-438A-927E-95B0090FCF79",
"architecture" : "x86_64",
"modelUTI" : "com.apple.apple-tv-4k",
"modelName" : "Apple TV 4K (at 1080p)",
"name" : "Apple TV 4K (at 1080p)"
},
{
"simulator" : true,
"operatingSystemVersion" : "11.1 (15B87)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone10,6",
"identifier" : "A97B392E-1C33-4C82-973D-CC87B2B00484",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-x-1",
"modelName" : "iPhone X",
"name" : "iPhone X"
},
{
"simulator" : true,
"operatingSystemVersion" : "13.4 (17E255)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad8,9",
"identifier" : "65853EFF-F2E6-4F17-9B2E-F3898F8950A0",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipad-pro-11-2nd-1",
"modelName" : "iPad Pro (11-inch) (2nd generation)",
"name" : "iPad Pro (11-inch) (2nd generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "11.1 (15B87)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone7,1",
"identifier" : "BDACD025-7410-473F-A523-6C323AF9C679",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-6-plus-b4b5b9",
"modelName" : "iPhone 6 Plus",
"name" : "iPhone 6 Plus"
},
{
"simulator" : true,
"operatingSystemVersion" : "11.1 (15B87)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad6,12",
"identifier" : "150FAB4A-20E9-48AA-A3D1-460BC2AD3ACE",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipad-gen5-a1823-1",
"modelName" : "iPad (5th generation)",
"name" : "iPad (5th generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "13.4 (17E255)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone12,1",
"identifier" : "797089E4-3411-4610-9223-A8BD01267937",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-11-1",
"modelName" : "iPhone 11",
"name" : "iPhone 11"
},
{
"simulator" : true,
"operatingSystemVersion" : "13.4 (17E255)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad8,12",
"identifier" : "353CE5FB-AECD-4C82-BAB4-C0F80FDB60C6",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipad-pro-12point9-4th-1",
"modelName" : "iPad Pro (12.9-inch) (4th generation)",
"name" : "iPad Pro (12.9-inch) (4th generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "11.1 (15B87)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad6,8",
"identifier" : "0CCDF64F-B967-465E-9CEB-3C89B1073AD7",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipad-pro-a1652-b4b5b9",
"modelName" : "iPad Pro (12.9-inch)",
"name" : "iPad Pro (12.9-inch)"
}
]
[   +7 ms] /Users/vasilich/Library/Android/sdk/platform-tools/adb -s 4200bf97cc953600 shell getprop
[  +95 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[   +3 ms] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[   +4 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[   +2 ms] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[  +54 ms] More than one device connected; please specify a device with the '-d ' flag, or use '-d all' to act on all devices.
[   +4 ms] ro.hardware = qcom
[ +120 ms] SM T720             • 4200bf97cc953600                     • android-arm64  • Android 9 (API 28)
[        ] iPad Pro (9.7-inch) • 1508A8B6-24D9-4A69-9867-FB22A6D86C41 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-13-4 (simulator)
[        ] macOS               • macOS                                • darwin-x64     • Mac OS X 10.15.4 19E264b
[        ] Chrome              • chrome                               • web-javascript • Google Chrome 80.0.3987.149
[        ] Web Server          • web-server                           • web-javascript • Flutter Tools
[  +12 ms] "flutter run" took 3,263ms.
#0      throwToolExit (package:flutter_tools/src/base/common.dart:14:3)
#1      RunCommand.validateCommand (package:flutter_tools/src/commands/run.dart:336:7)

#2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:702:11)

#3      FlutterCommand.run. (package:flutter_tools/src/runner/flutter_command.dart:619:33)

#4      FlutterCommand.run. (package:flutter_tools/src/runner/flutter_command.dart)
#5      AppContext.run. (package:flutter_tools/src/base/context.dart:150:29)
#6      _rootRun (dart:async/zone.dart:1184:13)
#7      _CustomZone.run (dart:async/zone.dart:1077:19)
#8      _runZoned (dart:async/zone.dart:1619:10)
#9      runZoned (dart:async/zone.dart:1539:10)
#10     AppContext.run (package:flutter_tools/src/base/context.dart:149:18)
#11     FlutterCommand.run (package:flutter_tools/src/runner/flutter_command.dart:609:20)
#12     CommandRunner.runCommand (package:args/command_runner.dart:197:27)
#13     FlutterCommandRunner.runCommand. (package:flutter_tools/src/runner/flutter_command_runner.dart:339:21)
#14     _rootRunUnary (dart:async/zone.dart:1192:38)
#15     _CustomZone.runUnary (dart:async/zone.dart:1085:19)
#16     _FutureListener.handleValue (dart:async/future_impl.dart:141:18)
#17     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:682:45)
#18     Future._propagateToListeners (dart:async/future_impl.dart:711:32)
#19     Future._completeWithValue (dart:async/future_impl.dart:526:5)
#20     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:36:15)
#21     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:298:13)
#22     FlutterVersion.checkFlutterVersionFreshness (package:flutter_tools/src/version.dart)
#23     _rootRunUnary (dart:async/zone.dart:1192:38)
#24     _CustomZone.runUnary (dart:async/zone.dart:1085:19)
#25     _FutureListener.handleValue (dart:async/future_impl.dart:141:18)
#26     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:682:45)
#27     Future._propagateToListeners (dart:async/future_impl.dart:711:32)
#28     Future._completeWithValue (dart:async/future_impl.dart:526:5)
#29     Future._asyncComplete. (dart:async/future_impl.dart:556:7)
#30     _rootRun (dart:async/zone.dart:1184:13)
#31     _CustomZone.run (dart:async/zone.dart:1077:19)
#32     _CustomZone.runGuarded (dart:async/zone.dart:979:7)
#33     _CustomZone.bindCallbackGuarded. (dart:async/zone.dart:1019:23)
#34     _microtaskLoop (dart:async/schedule_microtask.dart:43:21)
#35     _startMicrotaskLoop (dart:async/schedule_microtask.dart:52:5)
#36     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
#37     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:169:5)

Analyzing flutter_container_zero_height...
No issues found! (ran in 2.5s)

[✓] Flutter (Channel master, v1.17.1-pre.23, on Mac OS X 10.15.4 19E264b, locale en-UA)
• Flutter version 1.17.1-pre.23 at /Users/vasilich/flutter
• Framework revision a2e6c30b44 (9 hours ago), 2020-04-03 20:26:01 -0700
• Engine revision 09bc1fc45e
• Dart version 2.8.0 (build 2.8.0-dev.20.0 e736495eb7)
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
• Android SDK at /Users/vasilich/Library/Android/sdk
• Platform android-29, build-tools 28.0.3
• ANDROID_HOME = /Users/vasilich/Library/Android/sdk
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 11.4)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 11.4, Build version 11E146
• CocoaPods version 1.9.1
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 3.6)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin version 44.0.2
• Dart plugin version 192.7761
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
[!] IntelliJ IDEA Ultimate Edition (version 2018.3)
• IntelliJ at /Applications/IntelliJ IDEA.app
✗ Flutter plugin not installed; this adds Flutter specific functionality.
✗ Dart plugin not installed; this adds Dart specific functionality.
• For information about installing plugins, see
https://flutter.dev/intellij-setup/#installing-the-plugins
[✓] VS Code (version 1.40.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.4.1
[✓] Connected device (5 available)
• SM T720             • 4200bf97cc953600                     • android-arm64  • Android 9 (API 28)
• iPad Pro (9.7-inch) • 1508A8B6-24D9-4A69-9867-FB22A6D86C41 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-13-4 (simulator)
• macOS               • macOS                                • darwin-x64     • Mac OS X 10.15.4 19E264b
• Chrome              • chrome                               • web-javascript • Google Chrome 80.0.3987.149
• Web Server          • web-server                           • web-javascript • Flutter Tools
! Doctor found issues in 1 category.

Containers by default do not clip. That's why the icon is allowed to draw outside of the bounds of the container. You can fix this by setting a clipBehavior on the container that is not "none": https://master-api.flutter.dev/flutter/widgets/Container/clipBehavior.html


Skip matches in interactive mode

⭐ Suggestion
I would like to have an ability to skip matches in interactive mode. Now, all the matches are suggested to be applied at once (maybe you can only skip a file? not sure), but sometimes it's very useful to skip some matches.
💻 Use Cases
What do you want to use this for? To apply matches selectively
What shortcomings exist with current approaches? None I believe
What workarounds are you using in the meantime? I tried to use structured search and replace plugin in neovim which allows skipping, but it segfaults for some reason, so I just edit files manually.

Hi, thanks for trying out ast-grep.
I have not quite sure of the desired UX of skipping matches.
Currently, all matches for one rule are reported at once for one file.
We can present matches one by one but it will be too inefficient.

Hello @HerringtonDarkholme, here's the plugin: https://github.com/cshuaimin/ssr.nvim.
Regarding the UX, maybe the matches can still be all reported at once for a file visually, but the currently focused match will be highlighted somehow, and default options to choose will be "to replace all matches in this block (file)", "to skip all matches in this block", "to mark current match for replacement", "to skip current match", though there can be problems with this approach and I am not sure either. I agree that it's not quite trivial to design.

I have changed the behavior to print only one match at a time.


Add explicit close to connection

In #4159 , we seem to be experiencing cases where connections to marathon essentially become stale, potentially due to leadership changes. I have to admit that I am not particularly well versed in scala or akka, but I suspect that it is because the actor servicing the connection is stopped but the underlying connection itself is left open in these cases.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Withdrawing. Tests indicate that handle.close is called separately, and running an abdication manually does not seem to cause behavior. Apologies for any inconvenience.


Documentation

Add documentation.

Hi Adolfo, is this issue still open? I would love to add documentation.

If this issue is still open, may I add a working demo of the python module using a GIF in the markdown?

If this issue is still open, may I add onto the documentation?

Sure, go ahead.


Management - Modify Delegated Trader Payment Structure

Telegram user @eggwards currently acts as the AGFI Delegated Trader, which was established in Proposal #10. The payments for his services have now been exhausted.
This proposal is to modify the payment for @eggwards to be a commissions-based payment structure instead. The payment structure will be as follows:

30% of all profits earned will be paid to @eggwards as commission.
Any losses will be required to be recovered by @eggwards before earning commission again.
There will be no periodic base salary paid. Payment will only be taken from profits earned.
Profits will be sent to 0x16cc620dBBACc751DAB85d7Fc1164C62858d9b9f which will then be forwarded to @eggwards for on-chain records for the DAO.

This vote will be run on snapshot, as we do not require any on-chain contract modifications.

Very nice modification, he really deserve it.
He was there during the difficult moments, and this is the better proof to show him we all thanks him at the beginning of the good moments.

Well deserved commission structure! Happy
To approve.

I also agree with it

More than happy, to approve this proposal!

Proposal queued on Snapshot:
https://snapshot.org/#/aggregatedfinance.eth/proposal/0x0434d5766bf7fc55826e41d77541a1aaf3e5f22ed3c25d18388ce1cb13100aad


Update LICENSE

The repository makes use of two different licenses, namely Apache 2.0 and BSD

I thought we changed to Apache 2.0 , how can we remove the other one?

I changed in the master branch to Apache 2.0 :)

I have also updated the copyright holder.


Memory and handles leak

Describe the bug
Memory and descriptors leaks occur during RPC.
To Reproduce
Steps to reproduce the behavior:

Run this code

public class Program
    {
        private static void Main(string[] args)
        {
            try
            {
                var server = new RemotingServer(new ServerConfig
                {
                    HostName = Environment.MachineName,
                    NetworkPort = 7999,
                    RegisterServicesAction = container =>
                    {
                        container.RegisterService<ITestService, TestService>(ServiceLifetime.Singleton);
                    },
                    Serializer = new BinarySerializerAdapter()
                });

                server.Error += Server_Error;
                server.Start();

                var client = new RemotingClient(new ClientConfig
                {
                    ServerHostName = Environment.MachineName,
                    ServerPort = 7999,
                    Serializer = new BinarySerializerAdapter()
                });

                client.Connect();

                ITestService testService = client.CreateProxy<ITestService>();
                int i = 0;
                while (i < 10000)
                {
                    var res = testService.GetString();
                    i++;
                }
            }
            catch (Exception ex)
            {
                Console.WriteLine(ex);
            }
        }

        private static void Server_Error(object sender, Exception e)
        {
            Console.WriteLine(e);
        }
    }

    public interface ITestService
    {
        string GetString();
    }

    public class TestService : ITestService
    {
        public string GetString()
        {
            return "test";
        }
    }

Expected behavior
No Memory and descriptor leak.
Additional notes
Here the snapshot of memory

https://github.com/theRainbird/CoreRemoting/blob/37c09ae2e81086b128f15d3e4347347571bc0651/CoreRemoting/RemotingClient.cs#L509
I think should be !_activeCalls.TryRemove(...).

@zii-dmg, thanks, that helped. I've made PR #38 .

Accepted submitted fix: https://github.com/theRainbird/CoreRemoting/commit/2bb44ba9837a279f5f48a78ea734da4c55e6ee92
Many thanks for submitting the fix.


CustomStore insert and update methods return identifier instead of custom promise result

devexteme version: 18.1.3
devextreme-angular version: 18.1.3
[x] bug Report
[ ] feature request
[ ] support inquiry
Desired behaviour
insert and update promises of CustomStore should be resolved with custom implementation results
Current behaviour
When using CustomStore that is provided below, update and insert promises are resolved with record identifier instead of web service result.
Code example
store = new CustomStore({
  key: 'id',
  // getList: () => Observable<UserModel[]>
  load: () => this.service.getList().toPromise(),

  // post: (model: UserModel) => Observable<UserModel>
  insert: (model: UserModel) => this.service.post(model).toPromise(),

  // delete: (id: number) => Observable<any>
  remove: (id: number) => this.service.delete(id).toPromise(),

  // put: (model: UserModel) => Observable<UserModel>
  update: (id: number, model: UserModel) => this.service.put(model).toPromise()
});

save(model: UserModel) {
  let promise = Promise.resolve();
  if (model.id) {
	promise = promise.then(() => this.store.update(model.id, model));
  } else {
	promise = promise.then(() => this.store.insert(model))
  }

  promise.then((model: UserModel) => {
     /* Getting model identifier instead of model itself */
    console.log(model)
  })
}

Have you looked into the documentation? It clearly shows that the first parameter is key and the second is the actual updated item.

@hakimio According to the promise specification, it receives only one input parameter. So if you use native Promise you get only identifier as argument of your resolve method.

Hello,
This issue was solved in the context of this ticket.


what time can support windows?

just like title, what time can support windows?

Not in foreseeable future, but depends on contribution from the community


Autosave with SQLite interfering with publishing

Link to reproduction
https://github.com/mikecebul/versions-sqlite
Environment Info
Binaries:
Node: 20.14.0
npm: 10.7.0
Yarn: N/A
pnpm: 9.7.0
Relevant Packages:
payload: 3.0.0-beta.113
next: 15.0.0-canary.173
@payloadcms/graphql: 3.0.0-beta.113
@payloadcms/next/utilities: 3.0.0-beta.113
@payloadcms/translations: 3.0.0-beta.113
@payloadcms/ui/shared: 3.0.0-beta.113
react: 19.0.0-rc-3edc000d-20240926
react-dom: 19.0.0-rc-3edc000d-20240926
Operating System:
Platform: darwin
Arch: x64
Version: Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT 2024; root:xnu-10063.141.2~1/RELEASE_X86_64
Available memory (MB): 8192
Available CPU cores: 8
Describe the Bug
I created issue #8597 and realized it should be redone properly.
With SQLite only, when versions.drafts.autosave === true, it never says published, only changed. This prevents the ability to unpublish.
Since the autosave is getting triggered when it shouldn't I am seeing the collection data saved as null when it first loads. This happens because the data hasn't loaded yet and the autosave is triggered. I'm unable to come up with a simple reproduction because using single field and throttling to 3G doesn't trigger it. But setting the autosave.interval: 100, using many fields,  a free Vercel server, and Turso does cause this issue repeatedly.
Reproduction Steps
To see the bug you cannot use the test suite from the monorepo. I've tried and for some reason it works as expected as you can see here. So follow the steps below:

Create a blank beta sqlite app npx create-payload-app@latest
Create a new collection with a text field and a versions.drafts.autosave === true
Add a collection and press publish

You can also just use my reproduction.
Adapters and Plugins
db-sqlite

I think the problem was related to incorrect timestamps for versions which we fixed in this PR https://github.com/payloadcms/payload/pull/8646
After this change we were unable to reproduce this error. We'll do another release in the next day or so and you can confirm.


[DOCS] Add an example for the Inducing Path function

Closes #81
Changes proposed in this pull request:

Add an example in examples/intro

Before submitting

[ ] I've read and followed all steps in the Making a pull request
section of the CONTRIBUTING docs.
[ ] I've updated or added any relevant docstrings following the syntax described in the
Writing docstrings section of the CONTRIBUTING docs.
[ ] If this PR fixes a bug, I've added a test that will fail without my fix.
[ ] If this PR adds a new feature, I've added tests that sufficiently cover my new functionality.

After submitting

[ ] All GitHub Actions jobs for my pull request have passed.

@adam2392 How do you want me to proceed with this? Should I include scenarios where there is no path as well? And are the comments like this ok?

@adam2392 How do you want me to proceed with this? Should I include scenarios where there is no path as well? And are the comments like this ok?

The goal is to educate the user and serve as a quick reminder for yourself as a dev in case you need to review something.
I would proceed in sections:

setup the data and graph
draw the graph, perhaps comment that there is only 1 inducing path relative to L and S. This one inducing path is why the MAG in Figure 2 of the paper contains an extra adjacency
Run the inducing path algorithm and actually verify this 1 inducing path and verify a few non-inducing path examples as well
Show and explain what happens when we include the node into set S

Lmk if that makes sense

@adam2392 What do you think?

Yes I think this is a good start and direction!
Can you take a look at the other examples and use "# %%" to break up into sections where it makes sense?
It makes the final rendering easier to read.

@adam2392 can you take a look now?

Can you add a test in inducing_path that a graph should only have directed and/or bidirected edges? Otw, and inducing path doesn't make sense to run.

Do you want me to add it to this PR or create a new issue and a new PR?

You can just add it here since it's just a line just checking the types of edges present.

@adam2392 there's one problem. There is no graph class that is only has directed and bidirected edges. Even ADMG can have undirected edges. Do you want me to just check if the argument is an instance of PAG or CPDAG instead?

@adam2392 there's one problem. There is no graph class that is only has directed and bidirected edges. Even ADMG can have undirected edges. Do you want me to just check if the argument is an instance of PAG or CPDAG instead?

I wouldn't check the class as we are going to eventually try to refactor that so there is no explicit PAG/CPDAG class.
Instead, I would check the edge types for right now 'directed', 'bidirected' keywords.

Instead, I would check the edge types for right now 'directed', 'bidirected' keywords.

The problem is PAG would pass this test. It can have both of these edge types.

Instead, I would check the edge types for right now 'directed', 'bidirected' keywords.

The problem is PAG would pass this test. It can have both of these edge types.

We don't want any other edge. It can only have these types of edges.

@adam2392 Unless you're ok with instances of PAG class being valid as long as they only have directed and bidirected edges. Otherwise there is no way to differentiate between the different types.

@adam2392 I added the check. Also, I can't get the references to render, can you take a look at both?

@adam2392 The last run didn't make any documentation artifacts?

Are you able to see the status of the circle CI docs build? The artifacts are listed there.

Thanks @aryan26roy !


Update/docs

Description
Added installation guides for windows, macOS and ubuntu to the docs. Tested installations on clean virtual machines for each of the 3 OS's.
Type of change

[x] documentation update

How Has This Been Tested?
Locally rebuilt sphinx docs with
sphinx-build -M html ./ ./build

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

Contents (#118)
Other

README for docs code
docs readme
typo and hyperlink license
dependency for markup support
windows installation guide
markdown parser
example of massdash open in browser
ubuntu installation guide
note
macos installation guide
windows, macos, and ubuntu installation guides
installation guide list
main readme to include docs

Uncategorised!

[DOC] update links
[DOC] fix typo

Also I want to try and add a test for readthedocs before this goes live.

@singjc  Ready to merge when you like


PGDSAcceptance extension

The stores a graph test is successful when hasGraph returns true, but doesn't actually try a Cypher query on the stored graph. I think it should, ensuring that the actual data has been written and can be retrieved.

We should define in the contract what is to happen when an attempt is made to store a graph under the same name that already exists; this should be an error (no overwrite), but it should be a well-defined error, similar to what we do with GraphNotFoundException

Added more tests for special property names and unicode support here: https://github.com/opencypher/cypher-for-apache-spark/pull/433/files#diff-58730d2c1b97e61db53fe9df87cb4bd0R200

Agreed.


Adding events one by one and not losing them in process

Hello,
Using your calendar as one of my school project's backbone. I've been changing the source code somewhat. Though I can't seem to find the place where I can modify it so that
A. I can add an event
B. Add another event without losing the last one
C. Keep doing that
I'm not using backend techniques, just plain local storaging.
Also I scrapped the randomEvent function. Made it so it only passes one at a time with customized fields.
Thanks in advance :)

@TheMeteoRain You need to add a new event in a separate page.
Normally what you can do is:

Put a button somewhere which can navigate to a new page
Add the navigation logic in the timeSelected callback exposed by the calendar
Once you successfully added the event, you can navigate back to the calendar page and passes the events stored in local storage.

@twinssbc
Maybe I should have added more info. I have all the things mentioned.
I can access the selected date/data (that data comes from timeSelected, like you told) in calendar view and also I have a button to add event(not events).
Problem is whenever I add new event it replaces the old one, so I can never have multiple events.
I just need guidance where to fork the code, so it does not scrap past events.
Because it can get pretty messy there, since there is not documentation right in the source code.
Thanks

@TheMeteoRain
I think your current approach is correct.
The calendar watches the eventSource array, whenever it's changed, it will refresh the view.
I don't quite understand what you mean by the new events replaces the old one.
When you add a new event, I suppose you add one more entry in local storage. And next time you fetch events from the local storage, there will be two entries and they both get passed to eventSource array?

@twinssbc
The same thing happens when you at your own createRandomEvents() function.
It will create events and shows them, but after you click it again, all the previous ones go away and are replaced with new ones. Hope that clears it up of what is happening.
But yeah. I think I got it now. Made my own events array. Seems to be working just fine with this.

So the events being displayed are the ones in the events array. As long as the new event doesn't replace the existing event in the array, you should be able to see both the existing one and the new one.


"Ghizdita", "Gura Bădicului", "Jghiab" and "Plavățu" are listed in the drop-down menu

Description:
"Ghizdita", "Gura Bădicului", "Jghiab" and "Plavățu" are listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Ghizdita" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Ghizdita, BUZĂU(Mânzălești)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Type "Jghiab" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Jghiab, BUZĂU(Mânzălești)".

Step 6
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 7
Type "Plavățu" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Plavățu, BUZĂU(Mânzălești)".


[VS Code] Unable to connect to the host. Verify both you and the host are online.

#[VS Code] Unable to connect to the host. Verify both you and the host are online.

Reproduce on my machine (Session: https://insiders.liveshare.vsengsaas.visualstudio.com/join?24320B37787938E0153953467BBD62722426 ) when connecting to a VS Enterprise host (Windows 10, RS5 insdiers preview)
How do I export logs in VS Enterprise?

Best way to get the logs to us is to use the "report a problem" from the Feedback menu:

@Chuxel
How the mac system sends you logs

Hey @Surile, you can run the "Live Share: Export Logs" command in VS Code and then drag-and-drop the zip here or email it to<EMAIL_ADDRESS>

Migrating the logs from #1058: https://github.com/MicrosoftDocs/live-share/files/2435367/share-log.zip.

From the latest logs, looks like the host had indeed gone offline. Not sure what the bug is here, this is the behavior of the product.
[2018-10-01 19:37:07.703 Agent I] Connecting to address 1/4: {Host=<11:bd64c870> IPAddress=<192.168.bd64c870.> Port=5990 Timeout=00:00:02}
[2018-10-01 19:37:07.705 Agent I] Connecting to address 2/4: {Host=<15:611ac6c2> IPAddress=<.611ac6c2.> Port=5990 Timeout=00:00:02}
[2018-10-01 19:37:07.705 Agent I] Connecting to address 3/4: {Host=<8:39c3ea1c> IPAddress=<10.39c3ea1c.> Port=5990 Timeout=00:00:02}
[2018-10-01 19:37:07.706 Agent I] Connecting to address 4/4: sb://vsls-prod-ins-use-private-relay.servicebus.windows.net/42bd0d21da2e5a443f81662e1716f5775187--7bb3a8c6-87d7-4b7e-8ff9-279e5b0a119e
[2018-10-01 19:37:07.738 Agent I] Attempting client conection to relay (attempt 1)
[2018-10-01 19:37:07.786 Agent.Proxy I] WinHttpGetProxyForUrl failed with win32 error code: 12006
[2018-10-01 19:37:07.787 Agent.Proxy I] Read system proxy settings with auto winhttp mode, and proxy was null
[2018-10-01 19:37:08.356 Agent V] < #1 {Name=telemetry.genericOperation Arguments={EventName=complete-clientrelayconnection Result=Failure}}
[2018-10-01 19:37:08.361 Agent V] Microsoft.Cascade.Agent.RelayConnectionException: Client relay connection failed. ---> Microsoft.Azure.Relay.EndpointNotFoundException: There are no listeners connected for the endpoint.

Since the issue is stale and has been more than a year, I'm closing the issue. If there is a more recent repro, then reopn.

Please Re-open [VS Code] Unable to connect to the host. Verify both you and the host are online.  #327
I would like to reopen this issue as We are experiencing the same issue with out visual studio codes running Live Share.  Current version of Visual Studio Code:
Version: 1.74.1
Commit: 1ad8d514439d5077d2b0b7ee64d2ce82a9308e5a
Date: 2022-12-14T10:32:34.075Z
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 22.1.0
Sandboxed: No

I'm including my logs:
live_share_logs.zip

Hi @tempusthales please review our connectivity docs to confirm that the host is online and the appropriate connection mode has been set.
For example, if the connection mode was set to "Direct" and the host was not reachable, this error would be returned.

I turned off my vpn and it worked. i hope this helps someone


Add XorPal Code

https://www.codechef.com/MAY222D/problems/XOR_PAL

Please assign this code to me. As I am a 5 star coder at codechef - Userhandle(yati1103).


Python 2.7 packages

From<EMAIL_ADDRESS>on 2010-09-09T02:00:45Z
would be nice to have py27.exe as py26.exe won't install when only 2.7 is installed.
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=337

From pierre.raybaut on 2010-09-09T08:28:06Z
Status: Done


Landing page instance #6

Description
Please check this link for landing page
https://habeebanaaz1.wixsite.com/watermonitoringsys
Please include a summary of the change and which issue is fixed.
Please also include relevant motivation and context.
List any dependencies that are required for this change.
Fixes #172
Type of change
Please delete options that are not relevant.

[ ] New feature (non-breaking change which adds functionality)
[ ] This change requires a documentation update

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] Any dependent changes have been merged and published in downstream modules

Reviewer: Vinit Shahdeo

Please pull the upstream changes before pushing anything. Also, you are not required to develop the website on your own for this task. Although it might help us later since you have done it. You can create a separate issue for this on our repo and assign it to yourself. Then you can submit your work as a submission.
For this task, you can take the screenshot of the webpage and add it inside the screenshots/ directory as others have done. Good Luck!

Okay sure...thank you for advice

@habeeba-naaz please resolve merge conflicts before you submit for review again and please see that your changes are not to be pushed to the master branch but to the feature/documentation branch.

can i close this pull request

You can update this PR too if you wish. If you find that difficult, you may close this and open a new one.

I opened a new one but that linked to another issue

I pushed to feature/documentation but linked to other issue..actually I didn’t created PR yet .what should I do?

You have to create a PR for the design task to the feature/frontend branch and not to the feature/documentation branch. If you find it difficult to work with this PR, you can close this PR, update your local copy of the repo by pulling the feature/frontend branch from the upstream using a command something like git pull upstream feature/frontend, and then add your designs inside the screenshots/Instance #{number} directory. After that, you can create a PR. Good Luck!


Permissions for results downloads

This issue was identified by @antgonza (and possibly others), so please add comments if I describe this incorrectly.
Currently, analysis results are viewable by anyone that does a little bit of URL hacking, even if they should not have access to the analysis.

That is correct. Basically, the handler checks for permissions of the
main template but the actual result files are accessible by anyone.

@squirrelo and others, is the /results/(.*) URI only for analysis results, or are there other types of results that might need to be retrieved through that URI?

AFAIK only results.

Yes, should only be analysis results.

okay, thanks!


Mo tuples mo problems

[silgen] Fix another tuple explosion -> borrow + copy since we do not have the destructure operation yet.
rdar://29791263

@swift-ci Please smoke test and merge

@swift-ci Please smoke test and merge

@swift-ci Please smoke test and merge

The assertion failure that I hit in XCTest was correct! We had a tuple that was forwarding two types with conflicting ownership!
I loosened the assert when SILOwnership is disabled to return a conservative Any result.


Hacktoberfest

I was reading through some of the issues and found one that I thought would be pretty easy to tackle.  Then I remembered Digitial Ocean's Hacktoberfest is coming up.  It's a super-easy way to get contributions.
https://hacktoberfest.digitalocean.com/details#maintainers
I'm happy to help and super excited after installing last night.  Just thought why not share.

Contributions are very welcome! A selection of issues that are good for getting started are marked with "good first issue". For all other issues and requests, contributions are of course highly appreciated as well.

do you run Teslamate in Digital Ocean cloud?

@adriankumpf Perhaps you should tag those issues also with a Hacktoberfest label?

Done!

After reading the hacktoberfest rules i noticed that contributions to the hacktoberfest are only counted if the repository has the topic hacktoberfest or pull requests get the label hacktoberfest-accepted. Labelling issues with hacktoberfest is for visibility only i guess, people won't get credit for it.

They had to change some of the rules last week due to spammy low effort PRs.  Thanks for checking up on it.


Using volumes_from to compose a volume only docker image into my docker image

The usage guide talk about volumes but there is not example of the case where one would like to use something as volumes_from as is available in docker compose.
My question is if there is support for using volumes_from to mount a volumes only docker image into another image using spotify docker client?

I'm not sure. I looked in docker's API documentation, and I could not find a reference to that. I know it is possible to do through their API, because that's what the CLI uses, but I'm not exactly sure how. Let me do some checking to see if I can figure it out.

Yes, it is possible. Create a HostConfig, and use the .volumesFrom(String...) method on its Builder. Example:
final String volumeContainer = "some existing container name";
final HostConfig hostConfig = HostConfig.builder()
    .volumesFrom(volumeContainer)
    .build();
final ContainerConfig config = ContainerConfig.builder()
    .image("busybox:latest")
    .hostConfig(hostConfig)
    .cmd("ls", "/foo")
    .build();
client.createContainer(config);

Ok thanks very much


Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter tractive-gps for common errors and appropiate suggestions to keep this adapter up to date.
Please see the result of the check below.
ioBroker.tractive-gps
   -

:thumbsup: No errors found
WARNINGS:

[ ] :eyes: [W040] "keywords" within package.json should contain "ioBroker"
[ ] :eyes: [W174] Potential sensitive data "password" not listed at "encryptedNative" in io-package.json
[ ] :eyes: [W184] "common.main" is deprecated and ignored. Please remove from io-package.json. Use "main" at package.json instead.
[ ] :eyes: [W184] "common.materializeTab" is deprecated for admin >= 5 at io-package.json. Please use property "adminUI".

Please review issues reported and consider fixing them as soon as appropiate.
Warnings reported by repository checker should be reviewed. While some warnings can be considered as a suggestion and be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
You may start a new check at any time by adding the following comment to this issue:
@iobroker-bot recheck
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
Note: This issue replaces issue #201
@mcm1957 for evidence

RE-CHECK!

@ioBroker-Bot recheck

Thanks for contacting me.
I received your request to recheck this repository. I will start doing my work soon.
I will close an existing issue and create a new one if still any issues are to be evaluated and potentially to be fixed.
Thanks for spending your time and working at an ioBroker adapter.
your
ioBroker Check and Service Bot

Thanks for contacting me.
I received your request to recheck this repository. I will start doing my work soon.
I will close an existing issue and create a new one if still any issues are to be evaluated and potentially to be fixed.
Thanks for spending your time and working at an ioBroker adapter.
your
ioBroker Check and Service Bot

This issue has been replaced by new isse #204
This issue can be closed.
your
ioBroker Check and Service Bot


Add telemetry

We should probably add telemetry to the dotnet task where we own it.

A unit test would be valuable to check for the telemetry logic.

I would also add a variable which disables logging telemetry, in case anything goes south.


Ability to change the value of defaultWrap

As the title says, I'd like to be able to change the value of defaultWrap in my program. I know I can pass, for example, --help=120 if I wanted to but I want to change the default, which is currently 80.
I am not sure how portable or worth the effort this is, but the terminal-size library or something similar could also be nice.
This becomes particularly important when a program has a lot of command line flags and long descriptions for each of them.
As a side issue/question, line-breaks seem to be dropped from the help text. What's the reason for that?
Thanks for the great library!

Any updates on using terminal-size for this?


Searching for ADV does not result in a list with all ADV vampires

When search for "adv", Xaviar and Nergal are missing from the resulting list.
As an aside, ADV could be a trait to check, as it's something relevant to a number of vampires.

Text search for "ADV" works for other vampires, because their Card Text starts with "Advanced, [rest of card text]".
Xaviar was printed this way (without "Advanced, ") and is so in official card base. I already informed Vincent about inconsistensy, so once it's resolved in official cardbase it will be resolved in VDB also (it's decided to stick with official cardbase without monkey-patching).
Howevere, "Advanced" as a trait options sounds useful and will be added in the future.

Advanced trait added in 12fb633.


Doesn't work

It doesn't work
SyntaxError: Missing parentheses in call to 'print'. Did you mean print(' [-] Password Found!')?

Same Here


CodeLength incorrectly calculated when there are kwargs that should be counted as one

When there are keyword arguments, and the configuration says that hashes should be counted as one line, the code length module calculates the length incorrectly, by always subtracting 2.
I tracked the issue down to the Metrics::Utils::CodeLengthCalculator which includes this line
# Subtract 2 length of opening and closing brace if method argument omits hash braces.
length -= 2 if descendant.hash_type? && !descendant.braces?

This is valid in this example:
foo(
              foo: :bar,
              baz: :quux
            )

But not this one:
foo(foo: :bar, baz: :quux)

As a reproduction spec:
it 'folds hashes as method kwargs if asked' do
        source = parse_source(<<~RUBY)
          def test
            foo(foo: :bar, baz: :quux)
          end
        RUBY

        length = described_class.new(source.ast, source, foldable_types: %i[hash]).calculate
        expect(length).to eq(1)
      end

This gives a result of -1
RuboCop version
Tested on master
$ rubocop -V
1.26.1 (using Parser <IP_ADDRESS>, rubocop-ast 1.16.0, running on ruby 2.6.8 universal.arm64e-darwin21)
  - rubocop-performance 1.13.3
  - rubocop-rake 0.6.0
  - rubocop-rspec 2.9.0

#10520 fixes just a specific case. If the node is multiline, but still starts at the line of the parent node, it still gives the wrong result
it 'folds hashes as method args if asked' do
        source = parse_source(<<~RUBY)
          def test
            foo(foo: :bar,
                baz: :quux)
          end
        RUBY

        length = described_class.new(source.ast, source, foldable_types: %i[hash]).calculate
        expect(length).to eq(1)
      end

The actual of the above is -1

I'm sorry for I didn't enough consider about coverage of cases pray

That's alright - you have improved the calculation nevertheless. Just haven't fully resolved the issue

I'll attempt some additional fix on new branch.

Thank you :bow:

Do the following examples cover all cases for this issue?

Seems exhaustive enough. Well, if you want to go to extremes:
# pattern 5
def test
  foo(
    # those are keyword arguments
    foo: :bar, baz: :quux

  )
end

Though it's not clear whether we should count the comment as part of the hash or not :man_shrugging:

I created PR (https://github.com/rubocop/rubocop/pull/10543) for this. I'd be happy if you take a look at it :)

Fixed in #10543


fix tile gaps on movement

Currently, when the player is moving some ugly gaps between the tiles show up in the tilemap. This can be fixed by telling the camera to round the pixels.

Hey @Annoraaq! Thank you very much for you PR.
I'm solving this issue the same way with my bigger PR - #38.
If you don't mind I would close this one and go with my bigger one - I don't want to mess around with conflicts.
It's very nice of you to keep an eye on our project. Feel free to suggest best solutions with using your plugin :)

Sure no problem :) 👍

It's going to be fixed in #38


Pin to the older msrv version.

Fix the CI failure
https://github.com/eclipse-uprotocol/up-transport-zenoh-rust/actions/runs/11265771929/job/31328151458
If we use msrv 0.16.x, it needs at least Rust 1.78.0. I guess it will be good to support the minimum version we need.
Therefore, I decide to fix at 0.15.1.

IMHO the issue is that you are explicitly setting the rust toolchain to 1.75 using the rust-toolchain.yaml file.
FMPOV this is not really necessary. The msrv check in the nightly build is specifically designed to make sure that your code can actually be compiled using rust 1.75 ...
If you remove the rust-toolchain.yaml file, everthing should work as expected. Alternatively, you could explicitly switch to the stable toolchain before invoking cargo install msrv-check ...

IMHO the issue is that you are explicitly setting the rust toolchain to 1.75 using the rust-toolchain.yaml file. FMPOV this is not really necessary. The msrv check in the nightly build is specifically designed to make sure that your code can actually be compiled using rust 1.75 ... If you remove the rust-toolchain.yaml file, everthing should work as expected. Alternatively, you could explicitly switch to the stable toolchain before invoking cargo install msrv-check ...

I remember the reason I added rust-toolchain.yaml is because Zenoh couldn't compile with the latest compiler at that time. Since this is not the case, I agree it's fine to remove it now.


[Feature Request] How to make row table if click show expand?

Existing Component
Yes
Component Name
table
Description
I want to make the table if click the row show the expand. and column to show the expand ( > ) disappear. how to implemetation?

In 2.0 you can expand or collapse rows programmatically. You can hide the expand icon using CSS.

Can you please provide an example for this?


go/common/crypto/signature: Fail when unmarshaling nil keys

Fixes #2379

Should ToMapKey have a special case as well?

Should ToMapKey have a special case as well?

Good idea.

Please take another look.


How to migrate your pull request from py-evm to the trinity repository

We have just executed #728 which moves the p2p and trinity modules from this repository into https://github.com/ethereum/trinity
Anyone with an open pull request that touches either of the p2p or trinity modules will need to migrate their pull requests from this repository into the new one.  The following guide should help with this process.
1. fork the ethereum/trinity repository
First you need to get your own fork of the https://github.com/ethereum/trinity repository.

Do not clone it to your machine, yet

2. setting up your local version of the trinity repo

Before doing this ensure that you have pulled the latest master for py-evm

In your projects directory where your py-evm repository lives make a copy of the project directory and change into that new directory.
cp -R path/to/py-evm new/path/to/trinity
cd new/path/to/trinity

3. resetting your git history to 76276d586f5a365acdf79d8b7e823b607ea419a9
Now, from within our new trinity repository, you need to reset your master branch
git checkout master
git reset --hard 76276d586f5a365acdf79d8b7e823b607ea419a9

4. updating your remotes.
Now you need to edit the .git/config file.  It should currently look something like this.
$ cat .git/config
[remote "upstream"]
        url = git@github.com:ethereum/py-evm.git
        fetch = +refs/heads/*:refs/remotes/upstream/*
[remote "origin"]
        url = git@github.com:pipermerriam/py-evm.git
        fetch = +refs/heads/*:refs/remotes/pipermerriam/*
[branch "master"]
        remote = origin
        merge = refs/heads/master
[submodule "fixtures"]
        active = true
        url = https://github.com/ethereum/tests.git

You need to replace all of the places that are currently pointed at py-evm to now point at trinity.  The above file would become:
[remote "upstream"]
        url = git@github.com:ethereum/trinity.git
        fetch = +refs/heads/*:refs/remotes/upstream/*
[remote "origin"]
        url = git@github.com:pipermerriam/trinity.git
        fetch = +refs/heads/*:refs/remotes/pipermerriam/*
[branch "master"]
        remote = origin
        merge = refs/heads/master
[submodule "fixtures"]
        active = true
        url = https://github.com/ethereum/tests.git

5. pulling down new changes from the main trinity repo
Now you need to pull down any new changes from the trinity repository.  This command will vary depending on how you name your remotes.  For the config above, the command would be:
git pull upstream master

6. rebasing your local branches.
Next you'll need to switch to your local branch for your pull request and rebase it on top of the new master for the trinity repository.
git checkout my-branch
git rebase master

See https://help.github.com/articles/about-git-rebase/ for more information on rebasing
7. open your new pull request in the ethereum/trinity repository.
You can do this by simply copy/pasting the pull request text from the py-evm issue into a new pull request under the trinity repository.  Please provide a link to the old pull request in the new pull request.

It seems like it would be simpler (though slower) to run a fresh checkout of your personal ethereum/trininty fork, and add the upstream remote as usual. (skipping steps 2-4)
Maybe it's worth listing reasons not to do that like:

you keep copies of your local work (branches) in your new trinity repo
anything else?

you keep copies of your local work (branches) in your new trinity repo

This was the primary motivation.  People have existing forks and this seemed like an approach that would preserve those.  I'm open to other options.

Totally, I just updated the instructions to help motivate this other migration method: :+1:


added my favourite font :D

I hope the commit is ready

Thanks! If you could have a look at my notes, I'll pull this after the corrections.

done
I use
atom-workspace {
    font-family: Mononoki;
}

in my styles.less file to change the font for UI too, i think we should make this an option too or at least add it as a tip in the readme file

It's usually not a good idea for packages to change theme styling. It's impossible to know how all themes have been styled and it's even harder to keep track of changes. However, I'm not opposed to adding a tip to the readme.

I amended the last commit
all good?

I think you need to update the filenames to lower case?

I did!
other files than the 4 font files?

yeah I noticed now
something really weird is going on
git status says nothing to commit. finder also looks fine!!!

Weird.. are you on Windows?

mac :D

renamed inside atom. using Sourcetree for Git but never seen something like this before!

Double weird. Well I guess it's fine then. I pull this and see if I need to make fixes before publishing. Thanks for the effort!

uw 👍

About the case change not being seen by git: https://www.garron.me/en/bits/git-ignorecase-rename-lowercase-uppercase.html


Release Google.Cloud.Dialogflow.V2Beta1 version 1.0.0-beta01

Changes in this release:
Initial release.

Created release for Google.Cloud.Dialogflow.V2Beta1-1.0.0-beta01


When extracting features with the VGG, at what layer level do we stop on the VGG?

Thank you very much for this model. I have a question about this model. It's about feature extraction when training the model.
How to know which layer to stop when using for example VGG19 or VGG16 for feature extraction?

@jojupiter you should look the paper, it said which layers to use.


Cannot subscript a value of type 'JSON' with an index of type '[String]'

Using XCode 6.3 (Swift 1.2), this works just fine:
let that = json[["_source", "customer", "first_name"]]

However, this next block reports a compiler error:
let that = ["_source", "customer", "first_name"]
let thing = json[that]

Error: Cannot subscript a value of type 'JSON' with an index of type '[String]'
I don't understand why these two would be any different.

@tempire Try:
let that:[SubscriptType] = ["_source", "customer", "first_name"]
let thing = json[that]

This issue has been inactive for a while so I'm gonna go ahead and consider it fixed. Please let us know if you want to reopen it.

I have the same issue here...

@Domsware Can you try @tangplin 's solution and get back to me with your result? Thanks!


Updated Hybrid/SQL Exception

We have fixed the issue in the updated HC Manager, so I edited the answer to point to the HC Manager download.

@jamesche75 : Thanks for your contribution to the Azure documentation! The author, @genlin, has been notified to review your proposed change.

Looks good.
#sign-off


Update README for Manifest Config

Hi,
Thanks for creating the awesome library for Hexo platform. I really appreciate that.
For make the README.md keep update, I want  to add a little update in config manifest corresponding to Progressive Web App Manifest by Google Developer (https://developers.google.com/web/fundamentals/web-app-manifest/)
Thanks,

Thanks for your PR.


Add option to verify local image

This builds on the previous work to support saving an image and its signature for airgapped environments. This adds a flag, --local-image, to verify a signed image from disk.
Example:
cosign save us-west1-docker.pkg.dev/project/docker-repo/image:tag1 --dir .
cosign verify --key cosign.pub --local-image . --verbose

With --verbose, we see no network calls.
Ref #1015
Release Note
Add `cosign verify --local-image path` for verifying signed images from disk

cc @priyawadhwa

cc @dlorenc - FYI, this should allow for offline verification too

Amazing!!!
cc @jonjohnsonjr


Threads stuck on HttpRequestStream.Read

We're running into an issue in a Kestrel web application (using Microsoft.AspNetCore.Server.Kestrel 2.2.0) where some threads are stuck on the callstack:
[HelperMethodFrame_1OBJ: 00007f8357234f30] System.Threading.Monitor.ObjWait(Boolean, Int32, System.Object)
System.Threading.ManualResetEventSlim.Wait(Int32, System.Threading.CancellationToken)
System.Threading.Tasks.Task.SpinThenBlockingWait(Int32, System.Threading.CancellationToken)
System.Threading.Tasks.Task.InternalWaitCore(Int32, System.Threading.CancellationToken)
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpRequestStream.Read(Byte[], Int32, Int32)
**user code**

We have our own handling for timeouts. The task returned to aspnetcore is roughly:
await Task.WhenAny(TimeoutLogic(), RequestProcessingLogic());

All the stuck threads are in the "RequestProcessingLogic" part, for requests that timed out. Not all timeouts result in a stuck thread, this is a random occurrence.
I've captured a memory dump and tried to dig further to understand why those threads are stuck:

The pipe Http1Connection.RequestBodyPipe keeps a reference to the stuck task awaiter callback in its _readerAwaitable field. So it seems that the pipe wasn't completed/reset.
The _body field of the HttpRequestStream instance on which the read operation is performed is null, so StopAcceptingReads was called
HttpProtocol._requestAborted is true, Http1Connection._requestAborted is 0
It seems that Http1Connection.Reset was called (_requestProcessingStatus is RequestPending, Method is None, etc...)

I'm not sure where to look next. I've tried reproducing the issue locally but couldn't, for now it only happens on our production servers. I assume MessageBody.StopAsync hasn't been called (otherwise it should have called RequestBodyPipe.Reset which would have completed the task), but HttpRequestStream._body being null shows that HttpProtocol.StopStreams has been called. This could happen if HasStartedConsumingRequestBody was false, but I don't see how that would be possible (and I can't check what value it had because it has been overwritten when Http1Connection.Reset was called).
Does it ring a bell?

@stephentoub, any idea on how to diagnose this further?

Just in case, I'd like to add that I'm 100% sure that the threads are stuck:

I've removed all the traffic from the application and waited for a while
I checked that the local and global threadpool queues are empty

@kevingosse where is that timeout code? Is it in the middleware pipeline? Can you show the bottom of the stack? Are you spawning a task in order to make that timeout logic work?
In short, when our middleware is called:

We start a Task.Delay. When it completes, we set an error status code on the response
We start processing the request on a separate thread (that's the above callstack)
We return Task.WhenAny of all this

@kevingosse That's super sketchy. You can't return from the middleware pipeline and still have code that is touching the http request. Just so I get the picture, you effectively doing this
app.Use((context, next) =>
{
    var timeout = Task.Delay(1000);
    await Task.WhenAny(timeout,  Task.Run(next))
});

That code will never be reliable, my guess is (looking at your clues) the state of the request gets reset while your deserialize is still running. Can you buffer the request body instead?
app.Use(async (context, next) =>
{
    context.Request.EnableBuffering();
    await context.Request.Body.DrainAsync(context.RequestAborted);
    context.Request.Body.Position = 0;

    // Do synchronous protobuf deserialize here operation
});

I was kind of expecting to receive an exception if trying to read the request after the connection is closed. We have synchronization to make sure we don't write a response concurrently with the timeout, but we assumed that reading would be safe. In hindsight, since aspnetcore recycles a lot of objects under the hood, it doesn't sound so safe anymore.
I'll check if I can rework our logic the way you suggested. Thanks for the hint!

I was kind of expecting to receive an exception if trying to read the request after the connection is closed

Are you aborting the request? Here's what the bad version looks like:
app.Use(async (context, next) =>
{
    void ProcessBody()
    {
        // Do synchronous operation
        context.Request.Body.Read(new byte[4096]);
    }

    var delay = Task.Delay(1000);
    var doWork = Task.Run(ProcessBody);
    var ret = await Task.WhenAny(delay, doWork);

    if (ret == delay)
    {
        context.Abort();
    }

    await doWork;
});

We're not aborting the request. We do nothing fancy in case of timeout, from Kestrel perspective it's processed like any normal request.
I'm a bit surprised that we've noticed this behavior in only one application, even though we use the exact same timeout logic everywhere. There's still something missing in the equation. I'll try digging some more, while rewriting the timeout handling the way you suggested.

I think you're right that there's something else going on, it might be a race somewhere. I'm looking/

@kevingosse in the simplest repro I see several behaviors but haven't caught a hang condition yet:

ObjectDisposedException
RequestAbortedException

cc @halter73

I found something else that looks fishy in the memory dump.
For various reasons, we make a copy of the HTTP headers at the beginning of the processing of the request. In a small number of stuck threads (12 out of 3253), I found a mismatch between the Content-Length header that we copied and the value of _contentLength in the Http1MessageBody.ForContentLength object. Are you aware of a scenario where those two values could mismatch?

The only scenario I can think of for the content-length mismatch is:

Thread1 starts processing request1. Processing times out so kestrel believes we're done with the request
Thread2 starts processing request2, reusing the HttpProtocol object. Streams.Start is called, resulting in a new MessageBody being assigned to the HttpRequestStream
Thread1 finally gets to the point where it tried to read from the stream, and ends up reading from the MessageBody of request2

It confirms that we have to rethink our timeout logic. Those threads getting stuck are likely a variation of this scenario, where we end up manipulating the wrong objects because of the recycling.

I agree with your final analysis @kevingosse. Applications are responsible for ensuring they are done using the HttpContext and related objects prior to completing their Tasks. As soon as the app middleware Task completes, Kestrel will reuse those objects for the next request, so all bets are off if you're still using them.
Http1ContentLengthMessageBody. _contentLength is a readonly field populated directly from the Content-Length request header, so if it's not matching what you expect, that's a pretty good sign that you're referencing an object after it's been reused for another request.

Glad you got a deterministic repro!

I couldn't reproduce the hang, but at this point I believe it's safe to conclude that it's another consequence of using the HttpContext past the end of the request. To fix this in our code we'll need to prefetch the content of the request (equivalent to what DrainAsync does). On the plus side it means we won't have to worry anymore about Protobuf accessing the stream synchronously, so that's killing two birds with one stone. On the minus side, it means that in the off chance that the issue was actually unrelated to our usage of the HttpContext, it won't be detectable anymore (since our reads won't block).
That aside, I think you should consider making HttpContext recycling opt-in. It's a great feature performance-wise, but it's easy to misuse if you're not aware of it. Given that it paves the way to the worst possible kind of bug for a web app (replying a request with the content of another), you should make sure that the developers know what they're dealing with.


Add note for location matters for snapshot

If don't select the same location as the disk to be snapshot, there is no options for the disk in Source disk of Step 7.

@simonzhaoms : Thanks for your contribution! The author, @cynthn, has been notified to review your proposed change.

#please-close - @simonzhaoms thank you for the feedback! I'll add something to the docs on the next update.


This heading is more appropriately somewhere under 'File System Filter Drivers'

This document should be moved under the 'File System Filter Drivers' heading, to simplify where someone implementing a filter driver should look.  (Either that, or a "see also" link should be added under that heading to ensure that people look here as well.)

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

ID: bb3aee6c-10fa-7833-79f2-d7eec03e73c5
Version Independent ID: 5c45a552-2cf3-13ba-8f9f-b76ceb580292
Content: Using ECPs to Process IRP_MJ_CREATE in File System Filter Drivers - Windows drivers
Content Source: windows-driver-docs-pr/ifs/using-ecps-to-process-irp-mj-create-operations-in-a-file-system-filter.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @lorihollasch
Microsoft Alias: loriwhip

@kyanha, thanks for reporting this, and apologies that I was only now able to act on it. I've reorganized the entire File Systems table of contents, and have moved ECP info under the minifilter section, starting at Introduction to Extra Create Parameters.


thresholdType in .govverreport.yml is never considered  as metric

metric command line args has default value as block.
So the if block which assigns thresholdType when metric is not empty (https://github.com/mcubik/goverreport/blob/master/main.go#L64) never fails and always considers only the command line args.
Also the documentation for .govverreport.yml is not updated with thresholdType. It still has metric as the key.

:+1:
Regarding goverreport.yml documentation: I originally used the name thresholdType and later came up with what I thought was a better name: metric. As you correctly pointed out, the configuration file is still using the old key thesholdType instead of metric. I created the issue #7 to fix it.

@mcubik I have raised a PR for this issue: https://github.com/mcubik/goverreport/pull/6

@preethi29 In the branch issue/5-configured-metric-ignored I sketched an alternative solution which avoids making the metric argument mandatory (actually, the default value was still working but it was retrieved indirectly through the "default configuration", which I realized was unclear).
Would you check it out?


Add support for dump/restore to read from/writing to stdin/stdout.

@tailhook Is this already working with the new CLI?

(if not please change the project to A4)

Yes it was working. Added a bit of help (need explicit -, because stdin/stdout by default doesn't make a lot of sense).


A simple way of disabling XDS in grpc_unsecure (both for bazel and cmake).

Built on top of https://github.com/grpc/grpc/pull/25586.
Shows a simple way how to unconditionally remove XDS from grpc_unsecure.

grpc_unsecure now doesn't have the libssl dependency.
because no bazel-level options are used (which would result in conditional dependencies and conditional defines), the extract_metadata_from_bazel_xml.py can easily process the grpc_unsecure build and produces a cmake build without libssl dependency (no extra work needed).
the last commit is just regenerating the projects based on changes in bazel BUILD (feel free to ignore).

@markdroth @yihuazhang


multiline click-drag that starts on a token should de-select the token

Current behavior exists in both graph and linear view and results in unexpected behavior when trying to copy a chunk of code.

Fixed in build 3050


read a config ts file instead of using that textarea

this might introduce extra complexity to the plugin.