"dataPath" : "/Users/mac/Library/Developer/CoreSimulator/Devices/8485DE58-3E55-4863-A62D-0C7386E7BFE2/data",
"dataPathSize" : 483348480,
"logPath" : "/Users/mac/Library/Logs/CoreSimulator/8485DE58-3E55-4863-A62D-0C7386E7BFE2",
"udid" : "8485DE58-3E55-4863-A62D-0C7386E7BFE2",
"isAvailable" : false,
"logPathSize" : 339968,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-SE--2nd-generation-",
"state" : "Shutdown",
"name" : "iPhone SE (2nd generation)"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/mac/Library/Developer/CoreSimulator/Devices/65EE8E4A-E94A-4B85-821E-08CB34B458A0/data",
"dataPathSize" : 13312000,
"logPath" : "/Users/mac/Library/Logs/CoreSimulator/65EE8E4A-E94A-4B85-821E-08CB34B458A0",
"udid" : "65EE8E4A-E94A-4B85-821E-08CB34B458A0",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-12-mini",
"state" : "Shutdown",
"name" : "iPhone 12 mini"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/mac/Library/Developer/CoreSimulator/Devices/F8625EBE-1FAD-411B-A92F-A5C9ABA825D5/data",
"dataPathSize" :<PHONE_NUMBER>,
"logPath" : "/Users/mac/Library/Logs/CoreSimulator/F8625EBE-1FAD-411B-A92F-A5C9ABA825D5",
"udid" : "F8625EBE-1FAD-411B-A92F-A5C9ABA825D5",
"isAvailable" : false,
"logPathSize" : 360448,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-12",
"state" : "Shutdown",
"name" : "iPhone 12"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/mac/Library/Developer/CoreSimulator/Devices/D40714B4-515C-4CD1-806A-54DF90BFFBFA/data",
"dataPathSize" : 141942784,
"logPath" : "/Users/mac/Library/Logs/CoreSimulator/D40714B4-515C-4CD1-806A-54DF90BFFBFA",
"udid" : "D40714B4-515C-4CD1-806A-54DF90BFFBFA",
"isAvailable" : false,
"logPathSize" : 49152,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-12-Pro",
"state" : "Shutdown",
"name" : "iPhone 12 Pro"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/mac/Library/Developer/CoreSimulator/Devices/FD4C0748-564D-4AAF-A52B-22DAB6CFFEF7/data",
"dataPathSize" :<PHONE_NUMBER>0,
"logPath" : "/Users/mac/Library/Logs/CoreSimulator/FD4C0748-564D-4AAF-A52B-22DAB6CFFEF7",
"udid" : "FD4C0748-564D-4AAF-A52B-22DAB6CFFEF7",
"isAvailable" : false,
"logPathSize" : 3616768,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-12-Pro-Max",
"state" : "Shutdown",
"name" : "iPhone 12 Pro Max"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/mac/Library/Developer/CoreSimulator/Devices/94A3D14F-1C2B-46F8-83BD-9255DC0DFC31/data",
"dataPathSize" : 104562688,
"logPath" : "/Users/mac/Library/Logs/CoreSimulator/94A3D14F-1C2B-46F8-83BD-9255DC0DFC31",
"udid" : "94A3D14F-1C2B-46F8-83BD-9255DC0DFC31",
"isAvailable" : false,
"logPathSize" : 20480,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-13-Pro",
"state" : "Shutdown",
"name" : "iPhone 13 Pro"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/mac/Library/Developer/CoreSimulator/Devices/C145D341-67C3-4962-8D1E-EE816717CF72/data",
"dataPathSize" : 13312000,
"logPath" : "/Users/mac/Library/Logs/CoreSimulator/C145D341-67C3-4962-8D1E-EE816717CF72",
"udid" : "C145D341-67C3-4962-8D1E-EE816717CF72",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-13-Pro-Max",
"state" : "Shutdown",
"name" : "iPhone 13 Pro Max"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/mac/Library/Developer/CoreSimulator/Devices/37DDB08E-D5AD-4A58-BF27-6CD57066BD20/data",
"dataPathSize" : 13312000,
"logPath" : "/Users/mac/Library/Logs/CoreSimulator/37DDB08E-D5AD-4A58-BF27-6CD57066BD20",
"udid" : "37DDB08E-D5AD-4A58-BF27-6CD57066BD20",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-13-mini",
"state" : "Shutdown",
"name" : "iPhone 13 mini"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/mac/Library/Developer/CoreSimulator/Devices/140C2BE1-A28C-4ACA-BEBC-768B8BC0F140/data",
"dataPathSize" :<PHONE_NUMBER>,
"logPath" : "/Users/mac/Library/Logs/CoreSimulator/140C2BE1-A28C-4ACA-BEBC-768B8BC0F140",
"udid" : "140C2BE1-A28C-4ACA-BEBC-768B8BC0F140",
"isAvailable" : false,
"logPathSize" : 376832,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-13",
"state" : "Shutdown",
"name" : "iPhone 13"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/mac/Library/Developer/CoreSimulator/Devices/CB40EB24-E371-466F-85C0-561B705E846F/data",
"dataPathSize" : 762023936,
"logPath" : "/Users/mac/Library/Logs/CoreSimulator/CB40EB24-E371-466F-85C0-561B705E846F",
"udid" : "CB40EB24-E371-466F-85C0-561B705E846F",
"isAvailable" : false,
"logPathSize" : 270336,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPod-touch--7th-generation-",
"state" : "Shutdown",
"name" : "iPod touch (7th generation)"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/mac/Library/Developer/CoreSimulator/Devices/4B2ED8A6-A508-44CF-B678-2B4C92B96999/data",
"dataPathSize" : 13312000,
"logPath" : "/Users/mac/Library/Logs/CoreSimulator/4B2ED8A6-A508-44CF-B678-2B4C92B96999",
"udid" : "4B2ED8A6-A508-44CF-B678-2B4C92B96999",
"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/mac/Library/Developer/CoreSimulator/Devices/94D84564-D468-4C8A-904C-F14889AC5AD4/data",
"dataPathSize" :<PHONE_NUMBER>,
"logPath" : "/Users/mac/Library/Logs/CoreSimulator/94D84564-D468-4C8A-904C-F14889AC5AD4",
"udid" : "94D84564-D468-4C8A-904C-F14889AC5AD4",
"isAvailable" : false,
"logPathSize" : 360448,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-9th-generation",
"state" : "Shutdown",
"name" : "iPad (9th generation)"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/mac/Library/Developer/CoreSimulator/Devices/0B0A91C5-2796-4422-901C-E2F7E722744E/data",
"dataPathSize" : 13312000,
"logPath" : "/Users/mac/Library/Logs/CoreSimulator/0B0A91C5-2796-4422-901C-E2F7E722744E",
"udid" : "0B0A91C5-2796-4422-901C-E2F7E722744E",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Air--4th-generation-",
"state" : "Shutdown",
"name" : "iPad Air (4th generation)"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/mac/Library/Developer/CoreSimulator/Devices/88154A72-204C-4393-A3A8-56CE0B788E3F/data",
"dataPathSize" : 13312000,
"logPath" : "/Users/mac/Library/Logs/CoreSimulator/88154A72-204C-4393-A3A8-56CE0B788E3F",
"udid" : "88154A72-204C-4393-A3A8-56CE0B788E3F",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro-11-inch-3rd-generation",
"state" : "Shutdown",
"name" : "iPad Pro (11-inch) (3rd generation)"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/mac/Library/Developer/CoreSimulator/Devices/DC691468-096D-499F-B3DD-F5B7FABB01CF/data",
"dataPathSize" :<PHONE_NUMBER>,
"logPath" : "/Users/mac/Library/Logs/CoreSimulator/DC691468-096D-499F-B3DD-F5B7FABB01CF",
"udid" : "DC691468-096D-499F-B3DD-F5B7FABB01CF",
"isAvailable" : false,
"logPathSize" : 344064,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro-12-9-inch-5th-generation",
"state" : "Shutdown",
"name" : "iPad Pro (12.9-inch) (5th generation)"
},
{
"availabilityError" : "runtime profile not found",
"dataPath" : "/Users/mac/Library/Developer/CoreSimulator/Devices/F96EC4C4-7FC6-436D-A203-A95B3CC11055/data",
"dataPathSize" : 13312000,
"logPath" : "/Users/mac/Library/Logs/CoreSimulator/F96EC4C4-7FC6-436D-A203-A95B3CC11055",
"udid" : "F96EC4C4-7FC6-436D-A203-A95B3CC11055",
"isAvailable" : false,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-mini-6th-generation",
"state" : "Shutdown",
"name" : "iPad mini (6th generation)"
}
]
}
}
[+2930 ms] [
{
"simulator" : true,
"operatingSystemVersion" : "8.5 (19T241)",
"available" : true,
"platform" : "com.apple.platform.watchsimulator",
"companionDevice" : {
"simulator" : true,
"operatingSystemVersion" : "15.5 (19F70)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone13,3",
"identifier" : "508B61A7-1F54-4980-8BF3-F32773902C26",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-12-pro-1",
"modelName" : "iPhone 12 Pro",
"name" : "iPhone 12 Pro"
},
"modelCode" : "Watch5,3",
"identifier" : "6C1344D2-D4E1-4DCD-B6E3-C963879E7E96",
"architecture" : "x86_64",
"modelUTI" : "com.apple.watch-series5-1",
"modelName" : "Apple Watch Series 5 - 40mm",
"name" : "Apple Watch Series 5 - 40mm"
},
{
"simulator" : true,
"operatingSystemVersion" : "15.5 (19F70)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone12,3",
"identifier" : "73489BB9-5136-4427-8031-1F20C807DA8F",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-11-pro-1",
"modelName" : "iPhone 11 Pro",
"name" : "iPhone 11 Pro"
},
{
"simulator" : true,
"operatingSystemVersion" : "15.5 (19F70)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone14,5",
"identifier" : "A15EC128-EDD6-438D-85AD-C3FD48C04F67",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-13-1",
"modelName" : "iPhone 13",
"name" : "iPhone 13"
},
{
"simulator" : true,
"operatingSystemVersion" : "15.5 (19F70)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone13,1",
"identifier" : "9E06CB64-2184-40CE-92DA-30FB367AD58C",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-12-mini-1",
"modelName" : "iPhone 12 mini",
"name" : "iPhone 12 mini"
},
{
"simulator" : true,
"operatingSystemVersion" : "15.5 (19F70)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad14,1",
"identifier" : "D2251EAB-1E91-4074-BCD3-8D1EE1AAF279",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipad-mini6-1",
"modelName" : "iPad mini (6th generation)",
"name" : "iPad mini (6th generation)"
},
{
"simulator" : false,
"operatingSystemVersion" : "12.4 (21F79)",
"interface" : "usb",
"available" : true,
"platform" : "com.apple.platform.macosx",
"modelCode" : "MacBookPro14,3",
"identifier" : "F38049F4-C303-551B-91D5-2D5DBFD5335C",
"architecture" : "x86_64h",
"modelUTI" : "com.apple.macbookpro-15-retina-touchid-2017",
"modelName" : "MacBook Pro",
"name" : "My Mac"
},
{
"simulator" : true,
"operatingSystemVersion" : "15.4 (19L439)",
"available" : true,
"platform" : "com.apple.platform.appletvsimulator",
"modelCode" : "AppleTV11,1",
"identifier" : "E3BF3610-C89B-4B46-B417-9300513630D5",
"architecture" : "x86_64",
"modelUTI" : "com.apple.apple-tv-4k-2nd",
"modelName" : "Apple TV 4K (2nd generation)",
"name" : "Apple TV 4K (2nd generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "8.5 (19T241)",
"available" : true,
"platform" : "com.apple.platform.watchsimulator",
"companionDevice" : {
"simulator" : true,
"operatingSystemVersion" : "15.5 (19F70)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone14,3",
"identifier" : "2638C68F-13EC-4A2B-8CC3-E39AFDDDDF06",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-13-pro-max-1",
"modelName" : "iPhone 13 Pro Max",
"name" : "iPhone 13 Pro Max"
},
"modelCode" : "Watch6,2",
"identifier" : "84F7E819-BB5B-4028-AD83-893DBD247496",
"architecture" : "x86_64",
"modelUTI" : "com.apple.watch-series6-1",
"modelName" : "Apple Watch Series 6 - 44mm",
"name" : "Apple Watch Series 6 - 44mm"
},
{
"simulator" : true,
"operatingSystemVersion" : "15.5 (19F70)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone10,5",
"identifier" : "36F29C59-7D90-4D4F-BA32-9B4F62FAA265",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-8-plus-2",
"modelName" : "iPhone 8 Plus",
"name" : "iPhone 8 Plus"
},
{
"simulator" : true,
"operatingSystemVersion" : "15.5 (19F70)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad13,10",
"identifier" : "FCF19064-75CE-4150-9F89-69E75E07058B",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipad-pro-12point9-5th-1",
"modelName" : "iPad Pro (12.9-inch) (5th generation)",
"name" : "iPad Pro (12.9-inch) (5th generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "15.5 (19F70)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad12,2",
"identifier" : "9E9DB2A9-5D5F-47D6-A2A3-FD1C3FCEC7A6",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipad-9-wwan-1",
"modelName" : "iPad (9th generation)",
"name" : "iPad (9th generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "15.5 (19F70)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone14,6",
"identifier" : "34D906FB-47FF-43C1-BE8D-9536637F7208",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-se3-1",
"modelName" : "iPhone SE (3rd generation)",
"name" : "iPhone SE (3rd generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "15.5 (19F70)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone14,3",
"identifier" : "2638C68F-13EC-4A2B-8CC3-E39AFDDDDF06",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-13-pro-max-1",
"modelName" : "iPhone 13 Pro Max",
"name" : "iPhone 13 Pro Max"
},
{
"simulator" : true,
"operatingSystemVersion" : "15.4 (19L439)",
"available" : true,
"platform" : "com.apple.platform.appletvsimulator",
"modelCode" : "AppleTV5,3",
"identifier" : "29A9A3DB-DC7A-4C4C-8622-58BAF0C88594",
"architecture" : "x86_64",
"modelUTI" : "com.apple.apple-tv-4",
"modelName" : "Apple TV",
"name" : "Apple TV"
},
{
"modelCode" : "iPhone9,2",
"simulator" : false,
"modelName" : "iPhone 7 Plus (Model 1661, 1784, 1785, 1786)",
"error" : {
"code" : -13,
"failureReason" : "",
"underlyingErrors" : [
{
"code" : 4,
"failureReason" : "",
"description" : "Mac’s iPhone is locked.",
"recoverySuggestion" : "To use Mac’s iPhone with Xcode, unlock it.",
"domain" : "DVTDeviceIneligibilityErrorDomain"
}
],
"description" : "Mac’s iPhone is not connected",
"recoverySuggestion" : "Xcode will continue when Mac’s iPhone is connected.",
"domain" : "com.apple.platform.iphoneos"
},
"operatingSystemVersion" : "15.3.1 (19D52)",
"identifier" : "b566dc22c37bd0a23416b5e05919ba43a4adf8d5",
"platform" : "com.apple.platform.iphoneos",
"architecture" : "arm64",
"interface" : "usb",
"available" : false,
"name" : "Mac’s iPhone",
"modelUTI" : "com.apple.iphone-7-plus-4"
},
{
"simulator" : true,
"operatingSystemVersion" : "8.5 (19T241)",
"available" : true,
"platform" : "com.apple.platform.watchsimulator",
"companionDevice" : {
"simulator" : true,
"operatingSystemVersion" : "15.5 (19F70)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone13,4",
"identifier" : "114D8EE2-4FCA-4C52-AEFC-0A950B54620D",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-12-pro-max-1",
"modelName" : "iPhone 12 Pro Max",
"name" : "iPhone 12 Pro Max"
},
"modelCode" : "Watch5,4",
"identifier" : "53166BB9-0CE0-4BDA-AB54-91E7297A44BA",
"architecture" : "x86_64",
"modelUTI" : "com.apple.watch-series5-1",
"modelName" : "Apple Watch Series 5 - 44mm",
"name" : "Apple Watch Series 5 - 44mm"
},
{
"simulator" : true,
"operatingSystemVersion" : "15.5 (19F70)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone13,3",
"identifier" : "508B61A7-1F54-4980-8BF3-F32773902C26",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-12-pro-1",
"modelName" : "iPhone 12 Pro",
"name" : "iPhone 12 Pro"
},
{
"simulator" : true,
"operatingSystemVersion" : "8.5 (19T241)",
"available" : true,
"platform" : "com.apple.platform.watchsimulator",
"companionDevice" : {
"simulator" : true,
"operatingSystemVersion" : "15.5 (19F70)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone14,2",
"identifier" : "69D4AEB9-7871-44EA-8BCA-3F9169D51FA3",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-13-pro-1",
"modelName" : "iPhone 13 Pro",
"name" : "iPhone 13 Pro"
},
"modelCode" : "Watch6,1",
"identifier" : "803F5C88-7737-4F34-89DD-9FDD6132BD7B",
"architecture" : "x86_64",
"modelUTI" : "com.apple.watch-series6-1",
"modelName" : "Apple Watch Series 6 - 40mm",
"name" : "Apple Watch Series 6 - 40mm"
},
{
"simulator" : true,
"operatingSystemVersion" : "15.4 (19L439)",
"available" : true,
"platform" : "com.apple.platform.appletvsimulator",
"modelCode" : "AppleTV11,1",
"identifier" : "9C012872-43E0-4B95-AC9D-D28CB4BA0F49",
"architecture" : "x86_64",
"modelUTI" : "com.apple.apple-tv-4k-2nd",
"modelName" : "Apple TV 4K (at 1080p) (2nd generation)",
"name" : "Apple TV 4K (at 1080p) (2nd generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "15.5 (19F70)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPod9,1",
"identifier" : "63502517-17F2-4861-8383-61FEF8252898",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipod-touch-7-2",
"modelName" : "iPod touch (7th generation)",
"name" : "iPod touch (7th generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "15.5 (19F70)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone12,1",
"identifier" : "B079AF1B-B3A2-40AD-A7DC-6A38BC31A5A6",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-11-1",
"modelName" : "iPhone 11",
"name" : "iPhone 11"
},
{
"simulator" : true,
"operatingSystemVersion" : "15.5 (19F70)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone13,2",
"identifier" : "95DE544A-EA06-453F-9A77-E0518F5CDC9A",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-12-1",
"modelName" : "iPhone 12",
"name" : "iPhone 12"
},
{
"simulator" : true,
"operatingSystemVersion" : "15.5 (19F70)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad6,4",
"identifier" : "2A16F932-F09A-4BBC-B4DA-C10C732F0FB6",
"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" : "15.5 (19F70)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad13,5",
"identifier" : "A9234744-9C64-4FB1-8DA8-6149EB467F7A",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipad-pro-11-3rd-1",
"modelName" : "iPad Pro (11-inch) (3rd generation)",
"name" : "iPad Pro (11-inch) (3rd generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "15.5 (19F70)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone14,2",
"identifier" : "69D4AEB9-7871-44EA-8BCA-3F9169D51FA3",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-13-pro-1",
"modelName" : "iPhone 13 Pro",
"name" : "iPhone 13 Pro"
},
{
"simulator" : true,
"operatingSystemVersion" : "15.5 (19F70)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone12,5",
"identifier" : "49863B6C-F450-4AC1-AB08-89CCEC48D177",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-11-pro-max-1",
"modelName" : "iPhone 11 Pro Max",
"name" : "iPhone 11 Pro Max"
},
{
"simulator" : true,
"operatingSystemVersion" : "15.5 (19F70)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad13,17",
"identifier" : "EF23C260-F341-42C0-AF36-3FA5664E94C4",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipad-air5-1",
"modelName" : "iPad Air (5th generation)",
"name" : "iPad Air (5th generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "15.5 (19F70)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone13,4",
"identifier" : "114D8EE2-4FCA-4C52-AEFC-0A950B54620D",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-12-pro-max-1",
"modelName" : "iPhone 12 Pro Max",
"name" : "iPhone 12 Pro Max"
},
{
"simulator" : true,
"operatingSystemVersion" : "8.5 (19T241)",
"available" : true,
"platform" : "com.apple.platform.watchsimulator",
"companionDevice" : {
"simulator" : true,
"operatingSystemVersion" : "15.5 (19F70)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone14,4",
"identifier" : "807405E0-6BEB-40A1-ADE0-BFA83C88E240",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-13-mini-1",
"modelName" : "iPhone 13 mini",
"name" : "iPhone 13 mini"
},
"modelCode" : "Watch6,6",
"identifier" : "E36999FF-0902-4F6C-BC62-22B09F980E03",
"architecture" : "x86_64",
"modelUTI" : "com.apple.watch-series7-1",
"modelName" : "Apple Watch Series 7 - 41mm",
"name" : "Apple Watch Series 7 - 41mm"
},
{
"simulator" : true,
"operatingSystemVersion" : "15.5 (19F70)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone14,4",
"identifier" : "807405E0-6BEB-40A1-ADE0-BFA83C88E240",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-13-mini-1",
"modelName" : "iPhone 13 mini",
"name" : "iPhone 13 mini"
},
{
"simulator" : true,
"operatingSystemVersion" : "15.5 (19F70)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone10,4",
"identifier" : "5C9C6B50-E57C-4F88-9425-AD2636D925BA",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-8-2",
"modelName" : "iPhone 8",
"name" : "iPhone 8"
},
{
"simulator" : true,
"operatingSystemVersion" : "8.5 (19T241)",
"available" : true,
"platform" : "com.apple.platform.watchsimulator",
"companionDevice" : {
"simulator" : true,
"operatingSystemVersion" : "15.5 (19F70)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone14,5",
"identifier" : "A15EC128-EDD6-438D-85AD-C3FD48C04F67",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-13-1",
"modelName" : "iPhone 13",
"name" : "iPhone 13"
},
"modelCode" : "Watch6,9",
"identifier" : "69865D44-17BA-4BA4-858A-D23C75B81D45",
"architecture" : "x86_64",
"modelUTI" : "com.apple.watch-series7-1",
"modelName" : "Apple Watch Series 7 - 45mm",
"name" : "Apple Watch Series 7 - 45mm"
}
]
                2022-06-23 16:19:01.225 xcdevice[37186:342001] Requested but did not find extension point with identifier
                Xcode.IDEKit.ExtensionSentinelHostApplications for extension Xcode.DebuggerFoundation.AppExtensionHosts.watchOS of plug-in
                com.apple.dt.IDEWatchSupportCore
                2022-06-23 16:19:01.226 xcdevice[37186:342001] Requested but did not find extension point with identifier
                Xcode.IDEKit.ExtensionPointIdentifierToBundleIdentifier for extension Xcode.DebuggerFoundation.AppExtensionToBundleIdentifierMap.watchOS
                of plug-in com.apple.dt.IDEWatchSupportCore

[  +12 ms] Error: Mac’s iPhone is not connected. Xcode will continue when Mac’s iPhone is connected. (code -13)
[   +7 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[  +28 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'WindowsUwpEngineArtifacts' is not required, skipping update.
[   +4 ms] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[  +13 ms] 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.
[ +118 ms] Multiple devices found:
[  +81 ms] macOS (desktop) • macos  • darwin-x64     • macOS 12.4 21F79 darwin-x64
[        ] Chrome (web)    • chrome • web-javascript • Google Chrome 102.0.5005.115
[        ] [1]: macOS (macos)
[        ] [2]: Chrome (chrome)
[   +1 ms] Please choose one (To quit, press "q/Q")
[        ] :
[+1815 ms] q
[  +17 ms] "flutter run" took 5,849ms.
[  +37 ms]
#0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
#1      DeviceManager._chooseOneOfAvailableDevices (package:flutter_tools/src/device.dart:314:7)

#2      DeviceManager.findTargetDevices (package:flutter_tools/src/device.dart:302:37)

#3      FlutterCommand.findAllTargetDevices (package:flutter_tools/src/runner/flutter_command.dart:1378:28)

#4      RunCommand.validateCommand (package:flutter_tools/src/commands/run.dart:482:15)

#5      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:1298:5)

#6      FlutterCommand.run. (package:flutter_tools/src/runner/flutter_command.dart:1183:27)

#7      AppContext.run. (package:flutter_tools/src/base/context.dart:150:19)

#8      CommandRunner.runCommand (package:args/command_runner.dart:209:13)

#9      FlutterCommandRunner.runCommand. (package:flutter_tools/src/runner/flutter_command_runner.dart:281:9)

#10     AppContext.run. (package:flutter_tools/src/base/context.dart:150:19)

#11     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:229:5)

#12     run.. (package:flutter_tools/runner.dart:62:9)

#13     AppContext.run. (package:flutter_tools/src/base/context.dart:150:19)

#14     main (package:flutter_tools/executable.dart:94:3)

[ +286 ms] ensureAnalyticsSent: 281ms
[   +1 ms] Running shutdown hooks
[        ] Shutdown hooks complete
[   +1 ms] exiting with code 1`

yaml file
description: A new Flutter project.

# The following line prevents the package from being accidentally published to
# pub.dev using `flutter pub publish`. This is preferred for private packages.
publish_to: 'none' # Remove this line if you wish to publish to pub.dev

# The following defines the version and build number for your application.
# A version number is three numbers separated by dots, like 1.2.43
# followed by an optional build number separated by a +.
# Both the version and the builder number may be overridden in flutter
# build by specifying --build-name and --build-number, respectively.
# In Android, build-name is used as versionName while build-number used as versionCode.
# Read more about Android versioning at https://developer.android.com/studio/publish/versioning
# In iOS, build-name is used as CFBundleShortVersionString while build-number used as CFBundleVersion.
# Read more about iOS versioning at
# https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html
version: 1.0.2+4

environment:
  sdk: ">=2.12.0 <3.0.0"

# Dependencies specify other packages that your package needs in order to work.
# To automatically upgrade your package dependencies to the latest versions
# consider running `flutter pub upgrade --major-versions`. Alternatively,
# dependencies can be manually updated by changing the version numbers below to
# the latest version available on pub.dev. To see which dependencies have newer
# versions available, run `flutter pub outdated`.
dependencies:
  flutter:
    sdk: flutter

  # The following adds the Cupertino Icons font to your application.
  # Use with the CupertinoIcons class for iOS style icons.
  cupertino_icons: ^1.0.2

  image_picker: ^0.8.5+3
  path_provider: ^2.0.11
  permission_handler: ^9.2.0
  flutter_svg: ^1.0.3
  image_cropper: ^1.5.0

  shared_preferences: ^2.0.15

  connectivity_plus: ^2.3.5

  path: ^1.8.1

  image: ^3.2.0
  desktop_drop: ^0.3.3
  file_picker: ^4.6.1
  syncfusion_flutter_pdf: ^20.1.61-beta
  lottie: ^1.3.0

dev_dependencies:
  # change_app_package_name: ^1.0.0
  flutter_test:
    sdk: flutter
# flutter_icons:
#   android: "launcher_icon"
#   ios: true
#   image_path: "assets/appicon.png"
#   adaptive_icon_background: "#7B61FF"
#   adaptive_icon_foreground: "assets/forbackground.png"
  # The "flutter_lints" package below contains a set of recommended lints to
  # encourage good coding practices. The lint set provided by the package is
  # activated in the `analysis_options.yaml` file located at the root of your
  # package. See that file for information about deactivating specific lint
  # rules and activating additional ones.
  flutter_lints: ^1.0.0

# For information on the generic Dart part of this file, see the
# following page: https://dart.dev/tools/pub/pubspec

# The following section is specific to Flutter.
flutter:

  # The following line ensures that the Material Icons font is
  # included with your application, so that you can use the icons in
  # the material Icons class.
  uses-material-design: true

  # To add assets to your application, add an assets section, like this:
  assets:
    - assets/
  #   - images/a_dot_ham.jpeg

  # An image asset can refer to one or more resolution-specific "variants", see
  # https://flutter.dev/assets-and-images/#resolution-aware.

  # For details regarding adding assets from package dependencies, see
  # https://flutter.dev/assets-and-images/#from-packages

  # To add custom fonts to your application, add a fonts section here,
  # in this "flutter" section. Each entry in this list should have a
  # "family" key with the font family name, and a "fonts" key with a
  # list giving the asset and other descriptors for the font. For
  # example:
  # fonts:
  #   - family: Schyler
  #     fonts:
  #       - asset: fonts/Schyler-Regular.ttf
  #       - asset: fonts/Schyler-Italic.ttf
  #         style: italic
  #   - family: Trajan Pro
  #     fonts:
  #       - asset: fonts/TrajanPro.ttf
  #       - asset: fonts/TrajanPro_Bold.ttf
  #         weight: 700
  #
  # For details regarding fonts from package dependencies,
  # see https://flutter.dev/custom-fonts/#from-packages

@alihassan143

Next time, please try to use collapsible section for better readability (I helped to edit your comments)

[   +1 ms] Please choose one (To quit, press "q/Q")
[        ] :
[+1815 ms] q

From your flutter run -v output, I can see you chose q instead of 1 or 2, try again with an applicable option

if i use the simple CupertinoApp it also does the same

I tried with below sample code but it ran normally. Please provide a completed and minimal reproducible code sample so that we may verify this.

Sample code
import 'package:flutter/cupertino.dart';
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return CupertinoApp(
      debugShowCheckedModeBanner: false,
      home: CupertinoPageScaffold(
          child: CupertinoButton(
        color: Colors.black,
        child: const Text("Button"),
        onPressed: () {
          print("pressed");
        },
      )),
    );
  }
}

Once you complete above hints and provide such sample code, I will reopen the issue for further investigation. Thanks!


require "Forwardable"

Hi, I've recently downloaded this gem, and I had an issue where I had to go inside the gem and add a 《require "Forwardable"》or the gem would prevent my program from working.
I'm using ruby 2.3.

That's weird. I've tested and in Ruby 2.3 you can use both low and upcase.
2.3.3 :001 > require 'Forwardable'
 => true

2.3.3 :001 > require 'forwardable'
 => true

Which was your error and where exactly you added that require?

I don't recall, it happened this week-end, I'll tell you that this Thursday it is on my school's raspberry.

Ok, cool. In the meantime I'll increase the CI Ruby's versions to cover until 2.3 just in case

I couldn't use our raspberry today so I had to reproduce the bug on my macbook. After installing the gem and running this :
require 'ruby-push-notifications'
puts "foo"

I get this error :
 /Library/Ruby/Gems/2.0.0/gems/ruby-push-notifications-1.0.0/lib/ruby-push-notifications/notification_results_manager.rb:6:in `<module:NotificationResultsManager>': uninitialized constant RubyPushNotifications::NotificationResultsManager::Forwardable (NameError)

After adding require 'Forwardable' to notification_results_manager.rb everything works fine.
My macbook is running ruby 2.0.0p648


Candidate Mechanism Pertubation Amplitude notebook missing

Hi @carissableker, I think this got renamed and is now https://github.com/pybel/pybel-notebooks/blob/master/algorithms/Heat Diffusion Workflow.ipynb


Issue when running ssh tests

I see what looks like a deadlock when running the test suite with paramiko installed, on linux + 2.7:
py.test --collect-only odo/
...
platform linux2 -- Python 2.7.6 -- py-1.4.26 -- pytest-2.6.4
collecting 175 items / 12 skipped

I suspect a deadlock because the issue disappears iff I remove the ssh.connect in https://github.com/ContinuumIO/odo/blob/master/odo/backends/tests/test_ssh.py#L24, and strace shows a litany of:
[pid 10354] futex(0x180ef0a0, FUTEX_WAIT_PRIVATE, 0, NULL <unfinished ...>
[pid 10381] futex(0x180ef0a0, FUTEX_WAKE_PRIVATE, 1 <unfinished ...>
[pid 10354] <... futex resumed> )       = -1 EAGAIN (Resource temporarily unavailable)
[pid 10381] <... futex resumed> )       = 0
[pid 10354] select(0, NULL, NULL, NULL, {0, 8000} <unfinished ...>
[pid 10381] select(0, NULL, NULL, NULL, {0, 100000} <unfinished ...>
[pid 10354] <... select resumed> )      = 0 (Timeout)
[pid 10354] select(0, NULL, NULL, NULL, {0, 16000}) = 0 (Timeout)
[pid 10354] select(0, NULL, NULL, NULL, {0, 32000}) = 0 (Timeout)
[pid 10354] select(0, NULL, NULL, NULL, {0, 34890}

You may not want to do network IO in imports, as this may cause some thread creation (https://docs.python.org/2/library/threading.html#importing-in-threaded-code). I would suggest to instead implement the skip functionality using memoization.

i think a module scoped fixture would also do the trick

Hm, I can't reproduce this on OS X. It takes a long time, but it doesn't hang indefinitely.

@cournape would you care to put up a solution for this? i'm having trouble reproducing it

@cournape I'm closing this issue due to the time lag and our inability to reproduce; if you're still seeing this bug, please re-open.


Fix overflow of text and formatted student and lesson feedback messages

Codecov Report

Merging #219 (353ed41) into master (24a0d30) will decrease coverage by 0.57%.
The diff coverage is 27.77%.

@@             Coverage Diff              @@
##             master     #219      +/-   ##
============================================
- Coverage     60.21%   59.63%   -0.58%
  Complexity      691      691
============================================
  Files           129      129
  Lines          2556     2579      +23
  Branches        288      288
============================================
- Hits           1539     1538       -1
- Misses          917      941      +24
  Partials        100      100

Impacted Files
Coverage Δ

...id/logic/commands/AddStudentsToLessonsCommand.java
0.00% <0.00%> (ø)

...gic/commands/DeleteStudentsFromLessonsCommand.java
0.00% <0.00%> (ø)

src/main/java/tutoraid/model/lesson/Lesson.java
74.57% <100.00%> (-0.43%)
:arrow_down:

src/main/java/tutoraid/model/student/Student.java
76.56% <100.00%> (ø)

Continue to review full report at Codecov.

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


elm.elmPackages: Cleanup code

Be aware that this is chore so it's probably low-priority PR
Cleaning up the mess I made over several months adding elm tooling to hopefully easier to understand and more maitainable structure.

separation of HS and node based tools
removal of elm-live from nodeModules
expose elmPackages.lib.patchBinwrap

This will need a code quality review

Is this separation of node and elm based packages what we want?

Is it ok to just remove elm-live from nodePackages (maybe we should first mark it as deprecated?)

Is it fine to expose lib.patchBinwrap

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)

Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"

[ ] Tested execution of all binary files (usually in ./result/bin/)

[ ] Determined the impact on package closure size (by running nix path-info -S before and after)

[ ] Ensured that relevant documentation is up to date

[ ] Fits CONTRIBUTING.md.

Notify maintainers
cc @domenkozar

[x] made sure all other elmPackages.*

@GrahamcOfBorg build elmPackages


Translations update from Hosted Weblate

Translations update from Hosted Weblate for Food Expiration Dates/Food Expiration Dates.
Current translation status:

Merged, thanks @ngocanhtve!


🐞 [Bug]: IPV4 network option not showing with some applications

Is there an existing issue for this?

[X] I have searched the existing issues

which package/s did you face the problem with?
Dashboard
What happened?
when trying to deploy both PeerTube and Subsquid applications,  I cannot see IPV4 network option.
Steps To Reproduce
1- Navigate to the Dashboard
2- Connect your account.
3- Navigate to Deploy from the sidebar then click on Applications.
4- Navigate to the Peertube or Subsquid.
5- Expand network option.
which network/s did you face the problem on?
Dev
version
5ea3c0a
Twin ID/s
No response
Node ID/s
No response
Farm ID/s
No response
Contract ID/s
No response
Relevant screenshots/screen records

Relevant log output
n/a

verified ipv4 and ipv6 is now added to all applications

testcase


Update overview-managed-identity.md

added limitation for app configuration managed identity hard limit

@zhenlan FYI


fix build on case sensitive file system

I am signed https://github.com/mapsme/omim/blob/master/docs/CLA.md several times if it is important for this repo.


DDF-1341 Updating maven site plugin to attach descriptor

This isn't run by default with Maven 3, so we need to explicitly call it.

Verified maven site docs for attach-descriptor goal: https://maven.apache.org/plugins/maven-site-plugin/attach-descriptor-mojo.html


Contact Merge should respect Individual object regarding which Contact record to save

Raised in the Hub here.
Rather than allowing the user to select the master, the Individual object has a setting that determines what record is retained or not. Request is to respect this setting as part of our merge code (if customer is using Individual object as part of GDPR compliance, for example).

**lurch: add

Tracking W-026233

Salesforce has determined that this issue will not be explored further.


flutter drive command fails with WebDriverException when running the integration test

I'm writing a flutter app and for integration testing, I've followed the flutter tutorial.
I've written a very simple test to check the flutter driver's health status as follows:
import 'package:flutter_driver/flutter_driver.dart';
import 'package:test/test.dart';

void main() {
  group('Flutter app', () {
    FlutterDriver driver;
    setUpAll(() async {
      driver = await FlutterDriver.connect();
    });

    tearDownAll(() async {
      if (driver != null) {
        await driver.close();
      }
    });

    test('Check flutter driver health status', () async {
      final Health health = await driver.checkHealth();
      expect(health.status, HealthStatus.ok);
    });
  });
}

I've downloaded chromedriver and run the commands.
./chromedriver --port=4444
flutter drive --browser-name=chrome --release --driver-port=4444 --target=test_driver/app.dart

Testing works well with the iPhone Simulator & Android emulator.
However, on the web platform, testing fails with WebDriverException.
I've checked chromedriver's status from http://localhost:4444/status and it obviously runs well.
{"value":{"build":{"version":"81.0.4044.69<PHONE_NUMBER>a4bc83f717a2ef7cd4ac6ec1199132-refs/branch-heads/4044@{#776})"},"message":"ChromeDriver ready for new sessions.","os":{"arch":"x86_64","name":"Mac OS X","version":"10.15.3"},"ready":true}}
Here's the crash report I've got.

Flutter crash report; please file at https://github.com/flutter/flutter/issues.
command
flutter drive --browser-name=chrome --release --driver-port=4444 --target=test_driver/app.dart
exception
WebDriverException: WebDriverException (null): unknown command: unknown command: wd/hub/session
#0      parseJsonWireResponse (package:webdriver/src/handler/json_wire/utils.dart:85:9)
#1      JsonWireSessionHandler.parseInfoResponse (package:webdriver/src/handler/json_wire/session.dart:26:21)
#2      JsonWireSessionHandler.parseCreateResponse (package:webdriver/src/handler/json_wire/session.dart:18:7)
#3      SyncRequestClient.send (package:webdriver/src/common/request_client.dart:46:25)
#4      createDriver (package:webdriver/sync_core.dart:63:26)
#5      createDriver (package:webdriver/sync_io.dart:35:5)
#6      _createDriver (package:flutter_tools/src/commands/drive.dart:441:10)
#7      DriveCommand.runCommand (package:flutter_tools/src/commands/drive.dart:182:16)
<asynchronous suspension>
#8      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:638:18)
<asynchronous suspension>
#9      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:537:33)
<asynchronous suspension>
#10     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:29)
#11     _rootRun (dart:async/zone.dart:1126:13)
#12     _CustomZone.run (dart:async/zone.dart:1023:19)
#13     _runZoned (dart:async/zone.dart:1518:10)
#14     runZoned (dart:async/zone.dart:1465:12)
#15     AppContext.run (package:flutter_tools/src/base/context.dart:149:18)
#16     FlutterCommand.run (package:flutter_tools/src/runner/flutter_command.dart:527:20)
#17     CommandRunner.runCommand (package:args/command_runner.dart:197:27)
#18     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:338:21)
<asynchronous suspension>
#19     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:29)
#20     _rootRun (dart:async/zone.dart:1126:13)
#21     _CustomZone.run (dart:async/zone.dart:1023:19)
#22     _runZoned (dart:async/zone.dart:1518:10)
#23     runZoned (dart:async/zone.dart:1465:12)
#24     AppContext.run (package:flutter_tools/src/base/context.dart:149:18)
#25     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:288:19)
#26     CommandRunner.run.<anonymous closure> (package:args/command_runner.dart:112:25)
#27     new Future.sync (dart:async/future.dart:224:31)
#28     CommandRunner.run (package:args/command_runner.dart:112:14)
#29     FlutterCommandRunner.run (package:flutter_tools/src/runner/flutter_command_runner.dart:231:18)
#30     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:64:22)
#31     _rootRun (dart:async/zone.dart:1126:13)
#32     _CustomZone.run (dart:async/zone.dart:1023:19)
#33     _runZoned (dart:async/zone.dart:1518:10)
#34     runZoned (dart:async/zone.dart:1502:12)
#35     run.<anonymous closure> (package:flutter_tools/runner.dart:62:18)
<asynchronous suspension>
#36     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:29)
#37     _rootRun (dart:async/zone.dart:1126:13)
#38     _CustomZone.run (dart:async/zone.dart:1023:19)
#39     _runZoned (dart:async/zone.dart:1518:10)
#40     runZoned (dart:async/zone.dart:1465:12)
#41     AppContext.run (package:flutter_tools/src/base/context.dart:149:18)
#42     runInContext (package:flutter_tools/src/context_runner.dart:64:24)
#43     run (package:flutter_tools/runner.dart:51:10)
#44     main (package:flutter_tools/executable.dart:65:9)
#45     main (file:///Users/iMac/Development/flutter/packages/flutter_tools/bin/flutter_tools.dart:8:3)
#46     _startIsolate.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:299:32)
#47     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:168:12)

flutter doctor
[✓] Flutter (Channel unknown, v1.14.6, on Mac OS X 10.15.3 19D76, locale en-US)
    • Flutter version 1.14.6 at /Users/iMac/Development/flutter
    • Framework revision fabeb2a16f (3 months ago), 2020-01-28 07:56:51 -0800
    • Engine revision c4229bfbba
    • Dart version 2.8.0 (build 2.8.0-dev.5.0 fc3af737c7)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/iMac/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.3
    • 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.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.3.1, Build version 11C504
    • CocoaPods version 1.9.0

[✓] 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)

[✓] VS Code (version 1.44.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.9.1

[✓] Connected device (2 available)
    • Chrome     • chrome     • web-javascript • Google Chrome 81.0.4044.92
    • Web Server • web-server • web-javascript • Flutter Tools

• No issues found!

I want to run integration tests on the web platform as well.
Please give me some help.
@jonahwilliams @angjieli @yjbanov @nturgut
FYI, I'm using beta channel of v1.14.6.

Can you switch to the latest? That version might have some bug.

Thanks! It works. Now I'm using beta of v.1.17.0 and it works well.


Fix project name in README CLA

:bow:

Thank you! I really need to stop copy pasting my license stuff this happens every project… I shall add a TODO to make a script that generates those based on project name from now on lol
Thanks a ton <3


Change button text on Claim page for Ask

Instead of "Claim this ask", button text could be "Help this person"
(keep "Claim this offer" text as is)

@maebeale  Can I work on the issue?

@maebeale I see this issue is still up.  I'm currently downloading the repo, may I work on it if it's still available?

Fixed in #988.


enhancement: upgrade publisher

Pre-Flight checklist

[x] Testing

[x] Code is tested
[x] Changes have been manually tested

What are the relevant tickets?
https://github.com/mitodl/ocw-studio/issues/1821
What's this PR do?
Upgrades ocw-hugo-publisher to 0.5 (Hugo 0.112.0 and Go 1.20.4). Hugo changed --baseUrl to --baseURL, so that has been updated too.
How should this be manually tested?

Navigate to your local ocw-studio project directory.

Checkout branch hussaintaj/1821-upgrade-publisher

Start studio with docker-compose up

Choose a course you'd like to test this change on.

Run
docker-compose exec web ./manage.py backpopulate_pipelines --filter <course-id>
docker-compose exec web ./manage.py upsert_theme_assets_pipeline
docker-compose exec web ./manage.py upsert_mass_build_pipeline
docker-compose exec web ./manage.py upsert_mass_build_pipeline -o

Open your local concourse http://concourse:8080.

Trigger ocw-theme-assets build and wait for success.
Expected Behavior: Successful build and image used has the correct tag/version.

Go to your course site on studio UI http://localhost:8043/sites/name

Publish the course to live and draft both and wait for success.
Expected Behavior: Successful build and image used has the correct tag/version.

Return to the Concourse UI and trigger a mass build. You might want to lower the number of courses that run in the mass build. We can achieve that by setting publish_date and draft_publish_date to null on all of the courses except the ones you want to test with.

 docker-compose exec web ./manage.py shell
 from websites.models import Website
 Website.objects.all().update(publish_date=None, draft_publish_date=None)

Open https://localhost:8043/admin and set a publish_date so that it appears in the mass build.

Expected Behavior: Successful build and image used has the correct tag/version.

I tested this thoroughly today, and there is a major issue with the --baseURL setting.  I made a post on the Hugo support forums about it here: https://discourse.gohugo.io/t/issue-with-baseurl-in-0-112-0-0-112-6/44656
Basically, in versions 0.112.0 and up, the setting seems to not work with the way we have implemented nav URLs. Menus in Hugo can be implemented in a number of ways, but the way we have done it is to create a file in the content repos at config/_default/menus.yaml. It was done this way to facilitate the requirements of:

Must support internal and external links
Must support a custom defined order that includes the order of external vs internal links

There are two other ways menus can be implemented:

Defining the menu entry of a given page in front matter of the page to be included in the menu
Defining the menu in the config.yaml file

If we went with the first option, we would have to restructure the way ocw-studio writes menus to instead:

Write only external links to the config/_default/menus.yaml file, preserving their weight relative to all other menu items including internal ones
Write internal links to the front matter of the appropriate page, omitting the url property because it would be derived at build time from the position of the content, also preserving the weight relative to all other menu items

The second option is not viable, as we define a universal config.yaml file for all course sites and Hugo does not support merging config files as far as I know.
However, something did come to mind as I was researching it and that was a reply that Joe Mooring of the Hugo project had to an unrelated thread I posted in the Hugo support forums. Apparently there is an undocumented property on menu items that can be specified in a menu config called pageRef: https://discourse.gohugo.io/t/interaction-between-the-baseurl-and-relativeurls-settings/42770/2?u=gumaerc
As I was writing this post, he replied to the thread for this issue that I created above and confirmed that this is indeed an unintended behavioral change with Hugo 0.112.0. Either way, I tested using pageRef instead of url in the menu config, and I think we should switch to using it. I think we should wait a bit though and see if the Hugo team addresses this so the url property continues to function as expected. If we change our menu configuration to use pageRef, we will still need to mass-publish every site to make sure the configuration is updated in every Github repo before the changes in this PR go live. If we simply change the key from url to pageRef in this PR and release it, rebuilds of already published sites will result in broken nav links.
So, in summary, I believe this PR should be set on hold and another should be written up to move from url to pageRef in our menu definitions, then once that change is released and all Github repos are updated with it, we can release this PR.

I created an issue for what I describe needs to be done above here: https://github.com/mitodl/ocw-studio/issues/1833

@gumaerc thank you for the review and for looking into the issue. Thanks to your forum post, this fix should be available in v0.112.7. If I understand everything correctly, the fix should allow us to upgrade Hugo separately from https://github.com/mitodl/ocw-studio/issues/1833. Let's have a discussion on how we should proceed.


Everything is disabled

val logger = KotlingLogging.logger {}
println("DEBUG: ${logger.isDebugEnabled}")
println("TRACE: ${logger.isTraceEnabled}")
println("INFO: ${logger.isInfoEnabled}")
println("WARN: ${logger.isWarnEnabled}")
println("ERROR: ${logger.isErrorEnabled}")

Output:
DEBUG: false
TRACE: false
INFO: false
WARN: false
ERROR: false

This is an issue with the logging system used. See this note from readme:
Important note: kotlin-logging depends on slf4j-api (In the JVM artifact). In runtime, it is also required to depend on a logging implementation. More details in how-to-configure-slf4j. And an excellent detailed explanation in a-guide-to-logging-in-java.


Notifications Won't Disappear

Describe the bug
These Notifications won't disappear sometimes.
To Reproduce
Just add a bunch of songs to a playlist. Some notifications will disappear, others not.
Expected behavior
They should all disappear.
Screenshots

Environment

OS: Windows 10

Fixed with #503


Make the microphone settings function with LiveKit

The microphone settings are currently working with the Rust-based talking engine. On Linux the cpal library in Rust still doesn't manage to properly list all the microphones meaning we're gonna have to add some sort of work-around. Still experimenting with this one.
The major issue is that you currently can't select a microphone though. We're somehow gonna have to figure out how to sync the device names between LiveKit and our own talking engine. Because of the Linux issue, the section will have to be disabled on Linux again until the issue is resolved within cpal.

This has been completed on Windows. Since I'm not supporting other desktop platforms at the moment, this issue will be closed.


Attribution

Hi @Donavin97, it's great to see someone using and modifying sonify. Would you mind adding an attribution/link to the original sonify repo at https://github.com/liamtoney/sonify to your README.rst? Since this isn't a fork of that repo, the connection is not as clear. Thanks for your consideration.

Hi @liamtoney
Thanks for bringing this to my attention.
I'll gladly update the readme to atribute you.
I also wanted to thank you for creating such an amazing project.
I am a blind seismologist, I use your tool daily to review waveforms by ear to confirm seismic events.
If you have any questions, please feel free to ask.

Thank you, @Donavin97, and I am so happy to hear that this tool has been useful for you!


Simplify result copy elimination

Just realized that DEX also uses computes_result. you can use tensor_alias to check for outputs.


feat(assertions): add fail(string) that logs fail reason

This is a small extension of the current set of assertions. I've added fail(string)  to provide a clean and readable way to fail tests if a certain branch or execution point is hit

Would this mean that the other usages of vm.expectEmit && log_named_string are off

Yes - they do not affect the tests, but feel free to correct them.
While you're at it, we should do these two things as well:

Update ds-test (run forge update and commit that)
Change assertEq(bytes,bytes) to delegate to DSTest's assertEq0 because the logs have been corrected (you can also delete the tests)


Document Test Venue Strategies and Level of Service

💡 Description

Who are the responsible parties for spinning up/down resources in these venues?
Are there differences in level of service in each of these venues?
How long are resources to remain up in these venues?

More generally, should we be specific for each of these questions with regard to common resources? e.g. EC2, S3 buckets?
⚔ Parent Epic / Related Tickets
No response

@viviant100 we briefly discussed setting up timing for both dev and test to ensure services didn't go stale. has that been completed? is it documented anywhere?

📆 11/2024 status: Process has been worked out with SAs, finalizing documentation. Delayed 1 sprint. No impact on other tasks.

DSIO-6912

@viviant100 we briefly discussed setting up timing for both dev and test to ensure services didn't go stale. has that been completed? is it documented anywhere?

DSIO-6912

Waiting on SAs to implement in January


Documentation about origin / state of indices of BuiltinFun / AST terms etc

Describe the feature you'd like
The current standard of flat encoding UPLC implies that terms are distinguished by the order of their constructor. This makes i.e. finding the correct index for AddInteger very painful. Indeed the definition order does not match the indices which makes me wonder where actually one could read up which builtin function has which index?
IMO the index of elements should be independently documented and made sure that the haskell implementation fulfils the standard. The current approach of simply having the Haskell code as the standard is brittle (indexes can change and thus flat decoding will have potentially subtle errors, just by re-ordering elements) and hard to assess for outsiders and third party implementations of uplc such as https://github.com/opshin/uplc
Describe alternatives you've considered
No response

... which makes me wonder where actually one could read up which builtin function has which index?

Look at Tables C.3, C.4, and C.5 on pp 56-57 in the Plutus Core specification (pdf here).
In the Haskell source, the tags are defined here, which admittedly isn't very easy to find.


install CPLEX in conda environment

Hi, Compass team!
I installed Compass in a conda environment and I need to install CPLEX in this environment, too.
So , What command should I replace sudo with?
cd ~
chmod +x cplex_studio129.linux-x86-64.bin
sudo ./cplex_studio129.linux-x86-64.bin

Thanks for any help.
JW

Hi JW,
You should be able to use just ./cplex_studio129.linux-x86-64.bin without sudo so long as you select an install directory that you have permissions for.
Conda environments work well, just be careful that when setting up Cplex's python API that you have the conda environment activated, as otherwise Cplex will be installed to some other python distribution. That's messed up my installation once or twice.

Thanks, @schel337. It works well!
JW

Glad to help!


[FEATURE] Add example for aws-sdk-go-v2

Summary
The documentation for aws-sdk-go has already been added to this PR (https://github.com/minio/docs/pull/69) , but I can't find any documentation for aws-sdk-go-v2. So it's would be better to add it.
Goals

[ ] Add document how to use aws-sdk-for-go-v2 with MinIO server

Additional Context
In this comment(https://github.com/minio/docs/pull/348#issuecomment-861063106),  the cookbook documentation is planed to deprecate. So I'm not sure if this document should be added as cookbook.

@rennnosuke At this time, adding docs for the AWS Go SDK would not be a priority.
We do have our own Go SDK which we intend to continue creating documentation for moving forward.
With regards to the linked comment, we need to revisit the Cookbook docs to be something more maintainable and useful in the long term, vs something that goes out of date and remains stale until someone has spare cycles to take a look.
Looking at the V2 Go Docs I would presume that overriding the S3 endpoint to point to MinIO should be a good starting point.

Closing this issue as we do not have the resources to address it anytime soon.
When we get to the point of being able to bring up a cookbook/devhub, requests like these will make sense to keep open.

Sorry, I know this is closed, but it took me a while and I think it is worth leaving the solution for people stumbling onto this.
resolver := aws.EndpointResolverFunc(func(service, region string) (aws.Endpoint, error) {
    return aws.Endpoint{
        PartitionID:       "aws",
        URL:               "http://<IP_ADDRESS>:9000",
        SigningRegion:     "us-east-2",
        HostnameImmutable: true,
    }, nil
})

conn := s3.NewFromConfig(aws.Config{
    Region:           "us-east-2",
    Credentials:      credentials.NewStaticCredentialsProvider("minioadmin", "minioadmin", ""),
    EndpointResolver: resolver,
}, func(o *s3.Options) {
    o.UsePathStyle = true
})


[TEP-0091] add condition for trusted resources

Changes
This commit adds the ConditionTrustedResourcesVerified for trusted resources into pipelinerun/taskrun status to show if the resources passes verification. Failing to verify will add a false condition to the taskrun/pipelinerun status and passing the verification will add a true status condition.
Though this is a big size PR, it contains several changes which can be grouped into:

Add VerificationResult to indicate different cases when the Verification doesn't return error (Files: verify.go)
Update GetTask and GetPipeline and all the functions in call stack to return VerificationResult back to reconcile (Files: pipelineref.go, pipelinerunresolution.go, pipelinespec.go, taskref.go, taskspec.go)
Update TrustedResources condition based on VerificationResult (Files: taskrun.go, pipelinerun.go)
Unit tests to cover those cases. (all test files)

Those changes cannot be split into separate PRs.
/kind feature
Signed-off-by: Yongxuan Zhang<EMAIL_ADDRESS>
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[x] Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
[x] Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[x] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
[ ] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
Add ConditionTrustedResourcesVerified condition to pipelinerun/taskrun status indicate whether trusted resources fails verification or not. Functions including GetTask, GetTaskData, GetPipeline, GetPipelineData are updated to return VerificationResult

/kind feature

/assign @wlynch

/hold
I will try to break it down into smaller prs


⚠ Bofrost.be has degraded performance

In e55bfca, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1456 ms

Resolved: Bofrost.be performance has improved in 545dd95 after 8 minutes.


clean up error handling and add az botservice version check

This should be fix for #482 .  The recipe works but only if the correct tools are installed.
If people don't have the botservice installed (either via az distribution or as extension ) then ms bot clone can fail.
This delta detects that situation and tells the user how to upgrade their extension

Pull Request Test Coverage Report for Build 1042

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 68.388%

Totals

Change from base Build 1036:
0.0%

Covered Lines:
3744

Relevant Lines:
5243

💛  - Coveralls

also need to ensure that the native cli version is >= 2.0.45.


[FEATURE]Update ElasticApmEnricher to better support Open Telemetry

ECS integration/library project(s) (e.g. Elastic.CommonSchema.Serilog)::
Elastic.Apm.SerilogEnricher
Is your feature request related to a problem? Please describe.
I have been exploring Open Telemetry and how the Elastic Stack and Serilog would work together.  I have been able to send traces and logs to the Elastic Stack, but I was unable to link the logs to the traces with Elastic.Apm.SerilogEnricher.ElasticApmEnricher.  After reviewing the code, I saw that it relies on an (elastic) agent being present.  Because I am trying to stay true to the goals of Open Telemetry, I am trying to minimize the amount of code and dependencies I need to add that directly reference the Elastic Stack.  Currently, I only have references to the Elastic Stack as a sink (for logs) and as an Otlp Exporter target (for traces).
Describe the solution you'd like
I am not sure if I understood SpanId and TransactionId correctly, but I found the following changes would work (forgive the bad class name)...
        public class ElasticApmEnricher2 : ILogEventEnricher
	{
		public void Enrich(LogEvent logEvent, ILogEventPropertyFactory propertyFactory)
		{
			var activity = Activity.Current;
			if (null != activity)
			{
				var traceId = activity.TraceId.ToString();
				var spanId = activity.SpanId.ToString();

				logEvent.AddPropertyIfAbsent(propertyFactory.CreateProperty(
					"ElasticApmTraceId", traceId));
				logEvent.AddPropertyIfAbsent(propertyFactory.CreateProperty(
					"ElasticApmSpanId", spanId));
				logEvent.AddPropertyIfAbsent(propertyFactory.CreateProperty(
					"ElasticApmTransactionId", spanId));
			}
		}
	}

Describe alternatives you've considered
I have tried to search for newer or alternative libraries/extensions, but I could not find any.
Additional context
None.

#55 now ensures tracing information from Activity is available at a minimum.
Thanks for raising this @carlosli888 :+1:


enchancement in basketball game

PR Description 📜
Please include summary related to the issue you have fixed and describe your PR in brief over here by specifying the issue number on which you were working below
Fixes #3647

Mark the task you have completed ✅

[X ] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[ X] I have performed a self-review of my own code or work.
[ X] I have commented my code, particularly in hard-to-understand areas.
[ X] My changes generates no new warnings.
[ X] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[ X] I have added screenshot for website preview in assets/images
[ ] I have added entries for my game in main README.md
[ ] I have added README.md in my folder
[ ] I have added working video of the game in README.md (optional)
[ X] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗
I am contributing on behalf of Gssoc24

Thank you @NAVJOT-786 ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

@kunjgit  my pull request is not yet accepted Do any more changes required? Please let me know!

Thank you  @NAVJOT-786 , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


Question: Is there a recommended way to use this with Nx?

This library has been the closest way I could get to getting BDD testing working with playwright.
Nx recently added playwright generators to their toolset. It would be epic if there was a documented way on how to using this library with Nx. I'm really struggling to conceptualize how I would configure all of this.

I've got it working with the following project.json (full example code):
{
  "targets": {
    "bddgen": {
      "command": "bddgen",
      "outputs": ["{workspaceRoot}/.features-gen"]
    },
    "e2e": {
      "executor": "@nx/playwright:playwright",
      "dependsOn": ["bddgen"],
      "options": {}
    }
  }
}

Running npx nx e2e executes bddgen first to generate tests and then runs Playwright.
Could you check does it work for you? And we will add it as a recipe to docs.

The example code you provided is a little confusing.
I'm using the latest version of nx and I have multiple apps so I don't know what should go in my root directory vs at the project/app directory.

I'm using the latest version of nx and I have multiple apps so I don't know what should go in my root directory vs at the project/app directory.

Could you provide more details about your project structure - otherwise it's difficult to help.

I have a layout like this:
/apps
  /app1
    /e2e
    /src
    project.json
    ...other project specific files
  /app2
    /e2e
    /src
    project.json
nx.json
...other root level files

Then I'll run my e2e tests like this:
nx e2e app1

or
nx e2e app2

Or this if I wanted to run all e2e tests for my CI:
nx run-many --all --target=e2e

Could you try to put targets from my project.json example to app1/project.json and app2/project.json.

Yes, good point!
I've found the following project.json to run these commands in the correct cwd:
{
  "targets": {
    "bddgen": {
      "command": "bddgen",
      "outputs": ["{projectRoot}/.features-gen"],
      "options": {
        "cwd": "{projectRoot}"
      }
    },
    "e2e": {
      "executor": "@nx/playwright:playwright",
      "dependsOn": ["bddgen"],
      "options": {
        "config": "{projectRoot}"
      }
    }
  }
}

We can also move this as defaults to root nx.json:
{
  "targetDefaults": {
    "bddgen": {
      "command": "bddgen",
      "outputs": ["{projectRoot}/.features-gen"],
      "options": {
        "cwd": "{projectRoot}"
      }
    },
    "e2e": {
      "executor": "@nx/playwright:playwright",
      "dependsOn": ["bddgen"],
      "options": {
        "config": "{projectRoot}"
      }
    }
  },
  "affected": {
    "defaultBase": "main"
  }
}

And then keep project.json simple:
{
  "targets": {
    "bddgen": {},
    "e2e": {}
  }
}

(I didn't find the way to avoid these empty {} commands)

@vitalets thank you!
I will add it as a recipe to the docs.

One random thing I'm seeing is for this: "outputs": ["{projectRoot}/.features-gen"], no matter what valid path I set this value to, it always just generates at {projectRoot}/.features-gen. E.g. I want it to be {projectRoot}/e2e/generated but it still generates them to .features-gen.

Looks like I sorted it out by setting outputDir in the defineBddConfig.
Seems like the outputs for the project.json wasn't necessary at all.

Yes. I thought outputs can be useful for nx caching - to not re-generate test files when nothing changed.
But now I realize it should rely on inputs, not outputs :)
Anyway this is kind of optimization, great that basically it works.

Added to docs: https://vitalets.github.io/playwright-bdd/#/recipes?id=usage-with-nx
Thanks @barrymichaeldoyle for raising this!

@vitalets I'm not sure if this just me but I've noticed that @skip for features isn't working with this setup 🤔

Sorry I was a bit vague there.
The problem occurs when I try to @skip a Feature when it's step definitions aren't defined.
I get this message:

Missing step definition for "e2e/features/my_special.feature:24:5"

I managed to get around this by either commenting out the steps that are missing definitions or I can create empty definitions and that also does the trick.
This error occurs during the bddgen step.

Good case. Created a separate issue for that https://github.com/vitalets/playwright-bdd/issues/73


How to introduce on demand？

If I only want to use some of the features of the framework, how to introduce it on demand, reduce the volume after packaging？

You can add only the necessary components
https://github.com/lusaxweb/vuesax#or-use-individual-components

I found some problems with the introduction of individual components.
1.  The size introduced on demand is only 30kb smaller than the size of all references.
2.  The size of the css file introduced on demand is even larger than the direct introduction.

You could give me a contextual example of what you want to say thank you very much for the contribution


[Tracking] Transfer data to OSN -> Virtualize OSN dataset with beam -> View dataset repr in catalog

Meta tracking task to see if we can:

Move a set of archival files off of NCAR or another cluster into LEAP's OSN bucket.
Create a virtualizarr reference from the files on OSN.
Add the virtual dataset reference to the LEAP catalog with a repr that includes: engine = 'kerchunk'. https://github.com/leap-stc/data-management/issues/150

cc @leap-stc/data-and-compute

Another one could be Climsim


Update sbt-github-actions to 0.14.0

Updates com.codecommit:sbt-github-actions from 0.9.5 to 0.14.0.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.codecommit", artifactId = "sbt-github-actions" } ]

labels: sbt-plugin-update, early-semver-major, semver-spec-minor

Superseded by #61.


Adds spherical harmonics.

Co-authored-by: Jake VanderPlas<EMAIL_ADDRESS>

Thanks! FYI: the CI failure is unrelated and should be fixed by #7166. I'd suggest rebasing on main and then force pushing to restart the CI. I'll do a review probably by tomorrow morning.

Thanks for the comments! PTAL.

Thanks! FYI: the CI failure is unrelated and should be fixed by #7166. I'd suggest rebasing on main and then force pushing to restart the CI. I'll do a review probably by tomorrow morning.

Thanks for the fix!

Also, please add a note about this new function in the changelog!

Looks great! Please add a changelog entry & squash the changes into a single commit, and we should be able to get this merged!
Thanks again for all the effort on this functionality.

Thanks a lot for your help! Feel great to work together with you on this!


ASSIST - RACKLIB - need for unload_model?

It might be useful for the various load_model predicates to be complemented by an unload_model predicate. This can be achieved using rdf_retract_all but it is also necessary to use rdf_unload_graph, which is not obvious.

Are you anticipating that this would need to be a command-line operation or simply an ASSIST-RACKLIB provided function?

I was thinking of an ASSIST-RACKLIB function - just another predicate exported by model.pl.
I'm not sure if it would make sense as a command-line operation, although there is sometimes a need to wipe your RACK instance and start again.


src/framework/kmdf/src/core/tracing.cpp pragma typo's

"Recommended" is mis-spelled in two of the pragma declarations in this file

Thanks for bringing this up. These will be fixed in the next release.
-kumar

Good

No longer exists.


READ_PHONE_STATE permission implicitly added on android

Hello!
Looks like flutter_sodium is not providing a minimum api version, so it adds android.permission.READ_PHONE_STATE implicitly to the build bundle\apk:

uses-permission#android.permission.READ_PHONE_STATE
IMPLIED from AndroidManifest.xml reason: com.firstfloorsoftware.flutter_sodium has a targetSdkVersion < 4

Docs:
https://developer.android.com/reference/android/Manifest.permission.html#READ_PHONE_STATE

READ_PHONE_STATE
Allows read only access to phone state, including the phone number of the device, current cellular network information, the status of any ongoing calls, and a list of any PhoneAccounts registered on the device.
Note: If both your minSdkVersion and targetSdkVersion values are set to 3 or lower, the system implicitly grants your app this permission. If you don't need this permission, be sure your targetSdkVersion is 4 or higher.

Would be nice if flutter_sodium may provide minSdkVersion or targetSdkVersion  to avoid this permission, because it is about sensitive user data which is not used by our app.
Thank you :)

Thank for reporting. I've been looking into it, and AndroidManifest.xml usually doesn't contain any sdk version info for flutter plugins, but I might be mistaken.
Question: how do I reproduce this very message where the READ_PHONE_STATE is implied from the flutter_sodium package?

and AndroidManifest.xml usually doesn't contain any sdk version info for flutter plugins

Yeah, AndroidManifest.xml in the logs means a place, where permission was implicitly added :)
And the version is coming from build.gradle

Question: how do I reproduce this very message where the READ_PHONE_STATE is implied from the flutter_sodium package?

You can find that logs in \build\app\outputs\logs\manifest-merger-debug-report.txt after building an app with flutter_sodium added as a dependency.
Also, if you try to deploy a built apk (or bundle) to the Play Market, it will ask you for the privacy policy:
Your APK or Android App Bundle is using permissions that require a privacy policy: (android.permission.READ_PHONE_STATE).
Hope it helps :)

Thanks, found it.
Once I add the following minSdkVersion to the build.gradle of the plugin, the permission is indeed no longer added. Any preference for the minSdkVersion? Looks like other plugins use 16.
defaultConfig {
  minSdkVersion 16
}

Thank you for the fix!
I think minSdkVersion 16 is a good choice. As for today, it covers 99.8% of android devices:

Published flutter_sodium 0.1.9 to pub.dev
Enjoy


Where the form input components/documentation for react

Check that this is really a bug

[X] I confirm

Reproduction link
https://konstaui.com/react
Bug description
Form Inputs appear in the React kitchen sink app but not in the documentation
Expected Behavior
They should appear in the documentation
Actual Behavior
The form input components show up in the kitchen sink app but do not show up in the documentationl
Konsta UI version
3.1.3
Platform/Target and Browser Versions
latest chrome on IOS and android
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Konsta UI issue and not a framework-specific issue

Would you like to open a PR for this bug?

[ ] I'm willing to open a PR

No questions in issues


Adding CI.

Fixes #9

Not sure if Ameba is broken on nightly crystal or something.. this CI seems to be stalled, so I'm just going to move on since the rest passed.


basic auth in options?

how do you implement this in mtd?
thanks.

You can pass the auth params to the request() function — https://github.com/tusharmath/Multi-threaded-downloader#HTTP.request

how?
the master branch does README not have clear examples on how to use MTD, which makes it very unattractive to use.

Sorry if the README isn't clear. I'd be happy to merge a PR if you think it can be made better.
Internally mtd use the npm's request module for making HTTP requests. So to create a new HTTP request you could do something like —
const response$ = HTTP.request({
  url : 'a.b.c',
  auth: {
    'user': 'username',
    'pass': 'password',
    'sendImmediately': false
  }
})

Thanks.
I mean that in the other branches (which i have no idea which one is the most update one) the README is more clear and with examples of the options.
Thanks for MTD its really good!

@pantchox master is the most updated branch right now. I'd be more than happy to fix the documentation.

A simple basic usage example such as requiring the module and instantiating the class with the download options and events (start, pause, resume, finish) would make it more clear, its nice that the library looks very maintained and all the objects are being described what they do and all BUT there is NON of any examples of simple usage, digging in other branches/tags shows examples but how do i know they are aligned with this latest release.
I am not trying to be annoying or having something served on a silver plate i am just saying that simple users like me need to have a concrete USAGE example.
Thanks!


Claims plugin allows claiming instance worlds.

Players are able to claim instance worlds (outpost, microdungeons, etc.). Once an instance world is claimed, all other instance worlds are claimed as well.

Implemented a fix in commit 14d364e13f7d5fa3a1c96722a55a472654a5bc28.


fix(progress reporter): Simpify reported progress

Simplify the progress reporter to now only show relevant information about the progress: 3/23 tested (1 survived)
fixes #400

Looks good!


proton.json, steamcmd.py: Support Proton 7.0 (1887720)

SteamDB: https://steamdb.info/app/1887720/
It can be installed when updating game with -i 7.0.
Note: As of Feb 17 2022, Proton 7.0 requires logging in (+login [your_steam_account]). Without logging in, users can't install Proton 7.0 even if specifying AppId directly (-i 1887720).

Proton 7.0 requires logging in

Strange change. Does the account have to "own" proton now by acquiring a license?


Building fails (node 8.11.3, npm 6.2.0, ubuntu 18.04)

Do you want to request a feature or report a bug?
bug
What is the current behavior?
fails to build, can't view examples
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. You can use this jsfiddle to get started: https://jsfiddle.net/stopachka/m6z0xn4r/.
followed steps in documentation to build and see examples
What is the expected behavior?
build succeeds and can view examples
Which versions of Draft.js, and which browser / OS are affected by this issue? Did this work in previous versions of Draft.js?
These are the versions I tried:

master
v.0.10.0
v.0.10.5

I get some different errors depending on which version of node or npm I use, but the following is what I get for node 8.11.3 and npm 6.2.0:
[16:29:03] Starting 'modules'...
[16:29:03] Starting 'flow'...

events.js:183
      throw er; // Unhandled 'error' event
      ^
SyntaxError: /home/irf/draft-js/src/component/base/DraftEditor.react.js: Missing class properties transform.
  68 |  */
  69 | class DraftEditor extends React.Component<DraftEditorProps, State> {
> 70 |   static defaultProps: DraftEditorDefaultProps = {
     |   ^
  71 |     blockRenderMap: DefaultDraftBlockRenderMap,
  72 |     blockRendererFn: emptyFunction.thatReturnsNull,
  73 |     blockStyleFn: emptyFunction.thatReturns(''),
    at File.buildCodeFrameError (/home/irf/draft-js/node_modules/babel-core/lib/transformation/file/index.js:427:15)
    at NodePath.buildCodeFrameError (/home/irf/draft-js/node_modules/babel-traverse/lib/path/index.js:140:26)
    at ClassTransformer.pushBody (/home/irf/Dropbox/PublicPhotos/htdocs/irfanbaig.com/www.react/node_modules/babel-plugin-transform-es2015-classes/lib/vanilla.js:262:20)
    at ClassTransformer.buildBody (/home/irf/Dropbox/PublicPhotos/htdocs/irfanbaig.com/www.react/node_modules/babel-plugin-transform-es2015-classes/lib/vanilla.js:229:10)
    at ClassTransformer.run (/home/irf/Dropbox/PublicPhotos/htdocs/irfanbaig.com/www.react/node_modules/babel-plugin-transform-es2015-classes/lib/vanilla.js:143:10)
    at PluginPass.ClassExpression (/home/irf/Dropbox/PublicPhotos/htdocs/irfanbaig.com/www.react/node_modules/babel-plugin-transform-es2015-classes/lib/index.js:48:60)
    at newFn (/home/irf/draft-js/node_modules/babel-traverse/lib/visitors.js:276:21)
    at NodePath._call (/home/irf/draft-js/node_modules/babel-traverse/lib/path/context.js:76:18)
    at NodePath.call (/home/irf/draft-js/node_modules/babel-traverse/lib/path/context.js:48:17)
    at NodePath.visit (/home/irf/draft-js/node_modules/babel-traverse/lib/path/context.js:105:12)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: `gulp`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!  Exit status 1

Incidentally, is there any place online to see the latest examples instead of having to build it?

Nevermind, it appears I beguiled myself with some symlinking and had installed this under another node project hierarchy. Issue was resolved by moving it out of the hierarchy.


Update Disable-SPTimerJob.md

Simplified example.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-server/Disable-SPTimerJob.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Highlighted, big number is "0"

In the arrays with text and svg, we probably miss some Javascript as the highlighted  numbers are showing "0". Example URL /what-we-do/exploration

First step at enabling javascript for the archived pages


Add debug to sandcastle

I started using sandcastle in a personal project and I had a pretty tough debugging why some tasks were timing out. Adding a debug statement made it quite a bit easier as I could see what errors were be thrown by the api supplied.

:+1: awesome, will get this merged as soon as possible.

@thedjpetersen your changes are published in 1.3.3, I've added you as a collaborator on the npm modules/repo, to make it easier for you to make future contributions.

Neat - I'll probably still go through the normal pull request process.


Add Runner class

it should

have a method toy_simulation
have a method to call fitting of StatisticalModel
have a method inference_interafce
have a method run_toy_fit(generate_parameters, fit_parameters, , data) which call toy_simulation

Runner must:

initialise statistical model (give correct class + any kwargs taken by the init of said class)
Either call the models generate data, or read in a cached file containing toyMCs.

for each toy:

generate data or read in cached data.
fit data for all hypotheses (i.e. "free", {}, {"signal_rate_multiplier":3})
Compute confidence intervals for one or more hypotheses.
Store fitted parameters and likelihood values to results array
optional: store toyMC data to list
THen:
output fitted parameters and likelihood values in the inference_interface structure
optional: store toyMC data list in the inference_interface structure.

what I should not do in the first stage of runner development:

first run runner with the Gaussian model as an example, the later implemented complex statistical model will have the same API as the Gaussian model, so should not read the yaml configuration files
also should only care about manipulating the likelihood but not job submitting in the runner, so should not do job submission

I think for now, we just stick with the best-fit for the purposes of confidence interval computations being the 0th in the list of hypotheses

List of needed keyword arguments:

statistical_model
statistical_model_args
generate_values
fit_guesses
n_mc
poi (parameter_of_interest)
hypotheses
confidence_level
compute_confidence_interval
confidence_intervl_kind
outputfile
data_generation_mode (check #3)


[Rate limiting]Design Configuring Rate limit policies in Choreo Connect components

Description:
Design on data plane behaviour (Choreo Connect) once it received rate limit policies.

[x] Design how each component is going to be configured.

[x] Rate limit service
[x] Router
[x] Enforcer

[x]  Identify conditional policies (Advanced policies) going to support.

Please find the design doc: https://docs.google.com/document/d/1-qpcZaJW9cECDipG2Wmmp36lsjroc8sGUY_6Wa7qmB8/edit?usp=sharing


In Vegacapsule the logs are outputed to stderr instead of stdout

Since the beginning, the liqbot has been using logrus as the 3rd party logger. In the context of liqbot logging, out-of-the-box configuration ends up having the logs written to stderr instead of stdout. The solution is probably replacing logrus with Vega standard logger (wrapper for uber.zap).

closed in


bug: rc0 popup showing scrollbars on android 4.4 >

Type: bug
Platform: android 4.4 webview
ionic popup is showing scrollbars on rc0 on 4.4 and 5.0.
Tested on 4.1, 4.2, 4.3, 4.4, 5.0
rc0 codepin - http://codepen.io/nickh364/pen/emPNmJ
beta 14 codepin - http://codepen.io/nickh364/pen/bNmdey

Same problem here on firefox.
But seems to be a Duplicate of #3204

closing as duplicate. please continue the discussion on #3204


bosch sensor.energy_consumption 10 times to high

Describe the bug
Seem to have a format problem. According to sensor.energy_consumption my heatpump has an daily energy consumption > 100 kWh. Whereas between 10 and 25 is appropriate. (sensor sensor.recording_rconsumedenergy is ok)
To Reproduce
Steps to reproduce the behavior:

Go to 'sensor.energy_consumption' in bosch-custom-component integration
Expected behavior

A clear and concise description of what you expected to happen.
A value 10 times smaller.
Screenshots
not necessary
Version

Home Assistant 2022.11.4
Bosch custom component v0.19.4
HTTP -> IVT
RC300, Gateway iCom_Low_NSC_v1, firmware 04.08.02.

** Debug SCAN **
bosch_scan.json.txt
Additional context
Add any other context about the problem here.

Hi,
I have the same issue, here is a graph for yesterday's "sensor.energy_comsumption":

Which look like I consumed 2464 kWh. I consumed 64.82 kWh that day according to my energy meter.
My config is similar to OP:
Home Assistant 2022.11.4
Bosch custom component v0.19.4
HTTP -> IVT
RC300, Gateway iCom_Low_NSC_v1, firmware 04.08.02.

My debug scan is here -> http://jsonblob.com/1049957328480387072
BTW, what is the difference between recording_rconsumedenergy and energy_consumption ?
Thanks!

BTW, what is the difference between recording_rconsumedenergy and energy_consumption ?
Should be the same. rconsumedenergy seems to be stored in RC300 components (recorder inside, pushes every hour to my device, in kWh, without summing up) whereas energy_consumption value is summing up the energy consumption (both power x time).

sensor.energy_consumption is broken since 2 years, for some people it 10 times too high, for other 20x, for other too low.
That's the reason for recording sensors implemenation.
If you want to have entity state recording sensor will be 1 hour shifted as HA doesn't allow to give state from the last hour (data for last hour HH-01 is available from bosch at HH:05).
With NEW API option enabled you can have data only available in energy panel but those data won't be 1 hour shifted as component put those data directly into statistic database (kind of a hack)

Thanks for the answers, I believe I will keep using recording_rconsumedenergy since it seems to be working just fine :) I thank you @pszafer and all the contributors for this very useful HA integration. Have a great day.
C/N


Frame.f_trace, paving the way to support pdb debugging

f_trace is initialized with PyNone. I do not know if it would be better on memory/cpu to handle Option::None instead.
No tests for now, just wanting a feedback. Specially on the RwLock used.

I think it would be a micro-optimization for PyObjectRef vs Option<PyObjectRef>, as they're the same size since Option::<Rc>::None is represented by a null pointer. vm.is_none(&obj) vs opt.is_none() is I think 1 asm instruction different, as it's basically ptr == 0 vs ptr == vm->none_address

I see. The part intriguing me is that Option::None codepath is followed by return vm.get_none()
But storing PyNone lead to return .unwrap().clone() and I could not dodge this refcount cost on .clone()

I may be overthinking this all. Will keep pushing "just work" code until pdb.set_trace() works and then get back to optimize.
What about the rwlock? Is it ok? The rational was that I expect it to be checked on every single line change, so should be fast. But also light on memory as will be on every frame created.

...and thanks for the attention @coolreader18.

Yeah, I think the RwLock is good, it makes sense since you might occasionally be reading the f_trace property concurrently.

pdb.runcall() working, but not quite right. The 1st line stopped is into bdb yet :thinking:
(pdb) args works, but also behaves as if I had (pdb) next too :thinking:
Changed from RwLock to Mutex. On single-threaded is faster, on multiple it works IIUC.
Optimized a bit the codepath of vm::trace_event for the case of no trace function set, the default.

And this is the end of PyCon US 2020 sprint:

(pdb) continue works as expected, not breaking at some del frame.f_trace

Thanks @youknowone for the help on Gitter.
Had not found how do CPython implement del frame.f_trace. I implemented via frame.__delattr__. Yet I do not know how to call super() from Rust side. Will need help on this.
Now may need support for a setter on frame.lineno if wanting to have (pdb) jump to work. Maybe for (pdb) next too, as seems broken.
Good night.

Do you want to work more for this or want to merge part of the work?

Both 😬.
Better to merge the actual progress for this to not get rotten when I find the time to finish it.

Will you make a new PR with finished commits after rebase?

Will you make a new PR with finished commits after rebase?

I am not used to rebase stuff, but can learn to.
Should I go cherry-picking over master and send a new PR? Is this the way?

Oh, yep. Because this one is very aged, cherry-pick could be easier than rebase. That sounds very reasonable.

Oh, right -- looks like the errors are from .lock().unwrap(); we switched to parking_lot Mutexs since this PR was opened, so the .unwrap()s shouldn't be necessary.

Is the gc.py module necessary if everything raises a NotImplementedError anyway? We've mostly just been commenting out gc imports and function calls in modules that have them, is there a reason that can't work for pdb?

Is the gc.py module necessary if everything raises a NotImplementedError anyway? We've mostly just been commenting out gc imports and function calls in modules that have them, is there a reason that can't work for pdb?

bdb.py imports it to use somewhere, but I had not hit the case when it calls gc for real.
Anyway I do not feel bad by stubbing C-based stuff that we want not to implement right now.
(I need to say that sometimes I am missing the ability of calling rust code directly from python code. Maybe on future a custom importhook can do the trick.)

@youknowone what do you think?

We've mostly just been commenting out gc imports and function calls in modules that have them

My approach on this is to try to do the lowest number of changes possible on foreign code, if we want to get back to the original somewhere in future. That is why I am trying to provide a bogus gc instead of messing with bdb.py original code.
Less changes to track upstream on bdb.py and keep patching here until a fully compatible gc is ready.

https://github.com/RustPython/RustPython/pull/1918/checks?check_run_id=973313037#step:10:7685
AttributeError: module 'sys' has no attribute 'stdout'

What? I though that this was been fixed before :thinking:. I saw a PR about this!

Looks like sys.displayhook was natively implemented in meantime. Removing my hack from site.py and waiting for completion.
For some reason my local tests passes. I may have a local environment messed up.

Yay! Got green.
Now pdb.set_trace() "works" but stops on the wrong place.
Then works:

a(rgs)
c(ontinue)
h(elp)
l(ist)
w(here)
local evaluation also works

Yet broken:

n(ext): Is ignored, showing the very same line forever
r(eturn): Is ignored, showing the very same line forever
j(ump): Is ignored, and a follow c(ontinue) raises AttributeError: attribute 'f_lineno' of 'frame' objects is not writable

This PR is good to go. At least locals() and globals() variables inspection are working. Clojure variables inspection seemed broken.
Lets get this merged and open another to fix j(ump) and n(ext)

I'm merging this manually to fix this weird lf->crlf change in frame.rs

Alright, this is merged to master even though github doesn't show it.


Can't read the details section and the future contributionstion section bar cant be shown on screen

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
OS Version:

Steps to Reproduce:

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!


update dubbogo to v1.5.0-rc1

Issues associated with this PR
Your PR should present related issues you want to solve.
Solutions
You should show your solutions about the issues in your PR, including the overall solutions, details and the changes. At this time, Chinese is allowed to describe these.
UT result
Unit Test is needed if the code is changed, your unit test should cover boundary cases, corner cases, and some exceptional cases. And you need to show the UT result.
Benchmark
If your code involves the processing of every request, you should give the Benchmark Result.
Code Style

Make sure Goimports has run
Show Golint result

Codecov Report

Merging #1076 into master will decrease coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1076      +/-   ##
==========================================
- Coverage   56.08%   56.06%   -0.03%
==========================================
  Files         246      246
  Lines       23073    23073
==========================================
- Hits        12941    12935       -6
- Misses       8974     8978       +4
- Partials     1158     1160       +2

Impacted Files
Coverage Δ

pkg/module/http2/server.go
81.63% <0.00%> (-0.30%)
:arrow_down:

pkg/module/http2/transport.go
78.76% <0.00%> (-0.15%)
:arrow_down:

Continue to review full report at Codecov.

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


this PR moves all data mangement into quilt and fixes tests accordingly

we were already using quilt for larger data files (like tract shapefiles) but this PR moves the rest of the data into that model as well. The county and state shapefiles are now distributed with quilt, which trims down the size of the repo and keeps things consistent. When users import LTDB or NCDB, they will now be stored in a local quilt database, which provides some benefits

Awesome amount of work!


Batch inference

Hi,
I had a question regarding inference on octo. Is there a way where we can perform batch inference on octo ?

I modified the batch size to 2 in the inference notebook given in the examples. New shapes are -
Primary image - (2, 1, 256, 256, 3)
pad mask - (2, 1)
I am getting the following error after that -
TypeError: Cannot concatenate arrays with shapes that differ in dimensions other than the one being concatenated: concatenating along dimension 4 for shapes (2, 1, 256, 256, 3), (1, 1, 256, 256, 3).