dyld: Symbol not found: __T0s24_CocoaDictionaryIteratorC05cocoaB0s13_NSDictionary_pvpWvd

Description

I've run
detox init -r jest
detox test
The app is launched, and there is a symbol not found error on .err logs
Steps to Reproduce

detox test
Detox, Node, Device, Xcode and macOS Versions

Detox: 8.0.0
React Native: 53
Node: 10.5.0
Device: iPhone 6
Xcode: 9.4.1
macOS: 10.13.15

config
"detox": {
    "configurations": {
      "ios.sim.debug": {
        "binaryPath": "ios/build/Build/Products/Debug-iphonesimulator/app.app",
        "build": "xcodebuild -project ios/app.xcodeproj -scheme app -configuration Debug -sdk iphonesimulator -derivedDataPath ios/build",
        "type": "ios.simulator",
        "name": "iPhone 6"
      }
    },
    "test-runner": "jest"
  },

Device and verbose Detox logs

logs errors
dyld: Symbol not found: __T0s24_CocoaDictionaryIteratorC05cocoaB0s13_NSDictionary_pvpWvd
  Referenced from: /Users/sibelius/Library/Detox/ios/6835fdc9621ba06e099f505790cc7b06d2e6c1b5/Detox.framework/Detox
  Expected in: /Users/sibelius/Library/Developer/CoreSimulator/Devices/D8B576A1-7E16-42E0-B57F-13D40A40351B/data/Containers/Bundle/Application/55727C7C-A166-4C9A-ADE8-A663B399829E/golapp.app/Frameworks/libswiftCore.dylib
 in /Users/sibelius/Library/Detox/ios/6835fdc9621ba06e099f505790cc7b06d2e6c1b5/Detox.framework/Detox

more logs (detox test --loglevel verbose)
```
node_modules/.bin/jest e2e --config=e2e/config.json --maxWorkers=1 --testNamePattern='^((?!:android:).)*$'
 server listening on localhost:55171...
 onOpen [object Object]
 send: {"type":"login","params":{"sessionId":"e79eb251-131c-f14d-8532-e7697fc3f0d1","role":"tester"},"messageId":0}
 onMessage: {"type":"loginSuccess","params":{"sessionId":"e79eb251-131c-f14d-8532-e7697fc3f0d1","role":"tester"},"messageId":0}
  rbx
 : /usr/bin/xcrun simctl list -j
1: stdout: {
  "devicetypes" : [
    {
      "name" : "iPhone 4s",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-4s"
    },
    {
      "name" : "iPhone 5",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-5"
    },
    {
      "name" : "iPhone 5s",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-5s"
    },
    {
      "name" : "iPhone 6",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-6"
    },
    {
      "name" : "iPhone 6 Plus",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-6-Plus"
    },
    {
      "name" : "iPhone 6s",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-6s"
    },
    {
      "name" : "iPhone 6s Plus",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-6s-Plus"
    },
    {
      "name" : "iPhone 7",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-7"
    },
    {
      "name" : "iPhone 7 Plus",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-7-Plus"
    },
    {
      "name" : "iPhone 8",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-8"
    },
    {
      "name" : "iPhone 8 Plus",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-8-Plus"
    },
    {
      "name" : "iPhone SE",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-SE"
    },
    {
      "name" : "iPhone X",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-X"
    },
    {
      "name" : "iPad 2",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-2"
    },
    {
      "name" : "iPad Retina",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Retina"
    },
    {
      "name" : "iPad Air",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Air"
    },
    {
      "name" : "iPad Air 2",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Air-2"
    },
    {
      "name" : "iPad (5th generation)",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.iPad--5th-generation-"
    },
    {
      "name" : "iPad Pro (9.7-inch)",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro--9-7-inch-"
    },
    {
      "name" : "iPad Pro (12.9-inch)",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro"
    },
    {
      "name" : "iPad Pro (12.9-inch) (2nd generation)",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro--12-9-inch---2nd-generation-"
    },
    {
      "name" : "iPad Pro (10.5-inch)",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro--10-5-inch-"
    },
    {
      "name" : "iPad (6th generation)",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.iPad--6th-generation-"
    },
    {
      "name" : "Apple TV",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-TV-1080p"
    },
    {
      "name" : "Apple TV 4K",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-TV-4K-4K"
    },
    {
      "name" : "Apple TV 4K (at 1080p)",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-TV-4K-1080p"
    },
    {
      "name" : "Apple Watch - 38mm",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-38mm"
    },
    {
      "name" : "Apple Watch - 42mm",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-42mm"
    },
    {
      "name" : "Apple Watch Series 2 - 38mm",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-2-38mm"
    },
    {
      "name" : "Apple Watch Series 2 - 42mm",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-2-42mm"
    },
    {
      "name" : "Apple Watch Series 3 - 38mm",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-3-38mm"
    },
    {
      "name" : "Apple Watch Series 3 - 42mm",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-3-42mm"
    }
  ],
  "runtimes" : [
    {
      "buildversion" : "12H141",
      "availability" : "(available)",
      "name" : "iOS 8.4",
      "identifier" : "com.apple.CoreSimulator.SimRuntime.iOS-8-4",
      "version" : "8.4"
    },
    {
      "buildversion" : "13E233",
      "availability" : "(available)",
      "name" : "iOS 9.3",
      "identifier" : "com.apple.CoreSimulator.SimRuntime.iOS-9-3",
      "version" : "9.3"
    },
    {
      "buildversion" : "14E8301",
      "availability" : "(available)",
      "name" : "iOS 10.3",
      "identifier" : "com.apple.CoreSimulator.SimRuntime.iOS-10-3",
      "version" : "10.3.1"
    },
    {
      "buildversion" : "15F79",
      "availability" : "(available)",
      "name" : "iOS 11.4",
      "identifier" : "com.apple.CoreSimulator.SimRuntime.iOS-11-4",
      "version" : "11.4"
    },
    {
      "buildversion" : "15L576",
      "availability" : "(available)",
      "name" : "tvOS 11.4",
      "identifier" : "com.apple.CoreSimulator.SimRuntime.tvOS-11-4",
      "version" : "11.4"
    },
    {
      "buildversion" : "15T212",
      "availability" : "(available)",
      "name" : "watchOS 4.3",
      "identifier" : "com.apple.CoreSimulator.SimRuntime.watchOS-4-3",
      "version" : "4.3"
    }
  ],
  "devices" : {
    "com.apple.CoreSimulator.SimRuntime.tvOS-11-3" : [
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "Apple TV",
        "udid" : "3715F9B0-AE3E-412D-8F24-D158AA02F377"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "Apple TV 4K",
        "udid" : "E513892E-B6EC-4705-8599-B1FF969AA7F7"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "Apple TV 4K (at 1080p)",
        "udid" : "7C89E4D4-F226-40BB-B1CD-898DF9FC43C3"
      }
    ],
    "com.apple.CoreSimulator.SimRuntime.iOS-11-0" : [
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 5s",
        "udid" : "6564AA4F-9813-4A86-A9BF-911134A928E3"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 6",
        "udid" : "EEE4D9EA-8D33-4D9E-8D92-A43F9DBB9B50"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 6 Plus",
        "udid" : "FF773E13-B5C3-4B1D-964E-392939F1D84D"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 6s",
        "udid" : "26628E46-B34B-4340-9425-401402C7CEFD"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 6s Plus",
        "udid" : "77D26636-E3D9-4280-A101-83B41D9CEB51"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 7",
        "udid" : "98BFA8EE-7BCA-4AED-A34A-2AC9614B1638"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 7 Plus",
        "udid" : "CA460A1E-77AC-4EC5-AE10-103658C51209"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 8",
        "udid" : "55FF25DC-1558-4C0C-AD50-06977D062EAD"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 8 Plus",
        "udid" : "236A299E-E70C-48FC-B999-0F4F6329B247"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone SE",
        "udid" : "409CEFFA-A44C-4F69-A250-9E0C2582D045"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone X",
        "udid" : "56BFBD80-8DB0-4248-A08C-8418C956F4EC"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPad Air",
        "udid" : "206CEE78-9151-46FF-AF5C-D5E3E14A9EA8"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPad Air 2",
        "udid" : "3FF7820C-A520-4DC5-A5E5-3FFBBC72D820"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPad (5th generation)",
        "udid" : "96C75B37-C25E-4EC7-8280-09F62B30FF0E"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPad Pro (9.7-inch)",
        "udid" : "55636807-4FB5-490C-8116-090F1A1E56C0"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPad Pro (12.9-inch)",
        "udid" : "9F2360DC-96C6-4F6D-9091-FDA8734A2D2A"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPad Pro (12.9-inch) (2nd generation)",
        "udid" : "C7C43538-A0F6-4A06-8652-51324A52A8EC"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPad Pro (10.5-inch)",
        "udid" : "6BC53D05-2EA5-4D3F-893E-41E48FDE6352"
      }
    ],
    "com.apple.CoreSimulator.SimRuntime.watchOS-4-2" : [
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "Apple Watch - 38mm",
        "udid" : "A0C14B0B-FD12-4624-87B8-EDA7A4091D4F"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "Apple Watch - 42mm",
        "udid" : "91F56714-84D7-49A7-A340-78EFDE0DEEE0"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "Apple Watch Series 2 - 38mm",
        "udid" : "0F0538C5-9A9C-4500-8E79-2BF76225E9EE"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "Apple Watch Series 2 - 42mm",
        "udid" : "53C26596-0049-4386-968C-451AC498EADC"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "Apple Watch Series 3 - 38mm",
        "udid" : "944DE295-A6F8-4DEA-9D5A-9B53BE76A607"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "Apple Watch Series 3 - 42mm",
        "udid" : "F3B1DB45-21B4-4DB3-897C-2C721E6E5681"
      }
    ],
    "com.apple.CoreSimulator.SimRuntime.iOS-11-1" : [
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 5s",
        "udid" : "93D808BB-2EB6-4B7E-927C-48BB71BB73A5"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 6",
        "udid" : "223302B2-F247-4BD1-A984-467466C76CC1"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 6 Plus",
        "udid" : "D5270EEC-9430-4DFD-AC08-69C74E56C2DC"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 6s",
        "udid" : "AE6EA5E8-7F0C-4994-981D-D6AD35623A2D"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 6s Plus",
        "udid" : "1BE99236-57C0-41A5-BEC1-20D74AF561D3"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 7",
        "udid" : "B74BA84A-F0F8-4CB1-AE5B-BDFAC198B6EE"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 7 Plus",
        "udid" : "2C4A6F2C-BA44-4C4D-B95F-EE394014FBED"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 8",
        "udid" : "C2BF06FE-6068-4EC1-81EE-1D037D19D01D"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 8 Plus",
        "udid" : "B187A89E-A645-448F-AFEB-344A9F7939FB"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone SE",
        "udid" : "E238632C-5625-422F-B3EB-E30DA4EF7820"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone X",
        "udid" : "A9BD51EF-7936-435E-A378-3B3B056C518D"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPad Air",
        "udid" : "C1D0C7D1-394D-4095-9E21-70E77B05F113"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPad Air 2",
        "udid" : "1EF0635B-C8E6-4FE9-961A-F63C7AC52321"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPad (5th generation)",
        "udid" : "1A3E7A34-EA8A-499A-BBD6-F726892987DE"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPad Pro (9.7-inch)",
        "udid" : "5AC8E0A6-F9D6-4F4A-8A1A-3E47ADEFF6C8"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPad Pro (12.9-inch)",
        "udid" : "18AB03DD-7E8A-48C1-8E45-3C16D47898F3"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPad Pro (12.9-inch) (2nd generation)",
        "udid" : "BB3ACD2C-77CD-431B-831F-453409AB2746"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPad Pro (10.5-inch)",
        "udid" : "73E4799E-2645-46AC-81B2-EBB2BB03CDA6"
      }
    ],
    "com.apple.CoreSimulator.SimRuntime.iOS-11-2" : [
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 5s",
        "udid" : "14DA3352-CCEF-4FDF-83DC-AD30DDF11D57"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 6",
        "udid" : "B81A5A48-4289-40B1-BF40-DB0C46593A45"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 6 Plus",
        "udid" : "59583C15-C69C-41B7-BBA4-BE9314EAA0C9"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 6s",
        "udid" : "276136A8-4D1B-4159-83B1-CC4A3BC575FC"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 6s Plus",
        "udid" : "7A88771D-7DBF-48E9-8BE3-05CB080469DF"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 7",
        "udid" : "0798F4EC-0537-4CA4-937D-D1735C408D5A"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 7 Plus",
        "udid" : "26F65311-9352-41E5-8E43-4E8895FA1DE6"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 8",
        "udid" : "BB86F755-206E-45A5-B4C0-E55AB4BB2773"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 8 Plus",
        "udid" : "6B0798E9-7A6F-4706-B0A9-D4887A5AEDB2"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone SE",
        "udid" : "4115C0F0-42DC-4ACD-8C44-A6C5A7CA35A3"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone X",
        "udid" : "3606C882-6E7E-4CA5-8B95-4469F4D33ED2"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPad Air",
        "udid" : "04ACF6EE-C4A1-47BA-BA83-B3A02B1563D1"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPad Air 2",
        "udid" : "2DB96920-7AD0-462F-846A-378EBDA71480"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPad (5th generation)",
        "udid" : "18B3007E-74B4-4FDE-8C81-071D6EA1AB32"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPad Pro (9.7-inch)",
        "udid" : "13B50F09-A0F0-479F-8B0A-F6FBF1AD51C5"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPad Pro (12.9-inch)",
        "udid" : "C9569F6E-9DAC-4C8D-A969-A2032FBEA4F4"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPad Pro (12.9-inch) (2nd generation)",
        "udid" : "1D2A32C6-BFAC-4AC7-836C-83049DA94607"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPad Pro (10.5-inch)",
        "udid" : "86C51B80-9505-489E-A007-986C336B801F"
      }
    ],
    "com.apple.CoreSimulator.SimRuntime.iOS-11-3" : [
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 5s",
        "udid" : "6CBFACC4-BA99-4EC4-BF53-F365223DD3D4"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 6",
        "udid" : "AB44021F-7F4A-4ACA-AAEB-A6AE28E966A5"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 6 Plus",
        "udid" : "D2C50E36-DE69-45E2-AE94-C0477347060C"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 6s",
        "udid" : "2573B591-ABE2-4637-B0B1-B5D3A5C9FE41"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 6s Plus",
        "udid" : "0A896A98-5AAF-4F6A-B6D8-C4237C89D8DD"
      },
      {
        "state" : "Creating",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 7",
        "udid" : "8FAF80DB-1ED8-4A30-B92E-39F7A520C0A4"
      },
      {
        "state" : "Creating",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 7 Plus",
        "udid" : "30E23075-98F5-464E-92BC-6352D889D2C0"
      },
      {
        "state" : "Creating",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 8",
        "udid" : "B7F3B9FF-166E-4954-BB32-164075B4943D"
      },
      {
        "state" : "Creating",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone 8 Plus",
        "udid" : "4F8562B4-3594-4324-93C1-C77C6677FEF3"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone SE",
        "udid" : "99BDA569-A34C-404A-B0F0-5319FAEE23B8"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPhone X",
        "udid" : "0D918A82-E884-4295-BDBF-F5D17B09C1E1"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPad Air",
        "udid" : "041D032B-CAEF-4B3B-965B-6A1A191CD733"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPad Air 2",
        "udid" : "1D62ADDC-3C9C-4254-B86A-5CB66A2F16A4"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPad (5th generation)",
        "udid" : "CFB5EE19-FC54-4652-966F-08572FB5B2AB"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPad Pro (9.7-inch)",
        "udid" : "A24E4D5F-68A3-4B4B-B2EE-F8D7CB03190F"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPad Pro (12.9-inch)",
        "udid" : "41F3D019-2227-4D71-9A41-E302A45C75A7"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPad Pro (12.9-inch) (2nd generation)",
        "udid" : "8B57AE7E-9394-4483-9F8E-19AFFF16577C"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "iPad Pro (10.5-inch)",
        "udid" : "95C97922-4CAC-4565-8438-9A960921294C"
      }
    ],
    "com.apple.CoreSimulator.SimRuntime.watchOS-4-0" : [
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "Apple Watch - 38mm",
        "udid" : "228EA668-18D6-4F07-82E2-E20FBA25C244"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "Apple Watch - 42mm",
        "udid" : "E4714F89-8A4A-498C-B965-8202F5B1D6D9"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "Apple Watch Series 2 - 38mm",
        "udid" : "C39FC17F-CFAF-4991-B689-F97EE86A24E1"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "Apple Watch Series 2 - 42mm",
        "udid" : "95A6604D-4CA4-4D67-AB4A-22A56B9C7D40"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "Watch2017 - 38mm",
        "udid" : "57A2EB6D-AAD0-4489-8FF2-4F4F386D9DBF"
      },
      {
        "state" : "Shutdown",
        "availability" : " (unavailable, runtime profile not found)",
        "name" : "Watch2017 - 42mm",
        "udid" : "3802112E-748A-42C0-8539-55A168FA9C9F"
      }
    ],
    "iOS 11.4" : [
      {
        "state" : "Shutdown",
        "availability" : "(available)",
        "name" : "iPhone 5s",
        "udid" : "8386E05F-0DF6-4475-875E-0E7D7112FE44"
      },
      {
        "state" : "Booted",
        "availability" : "(available)",
        "name" : "iPhone 6",
        "udid" : "D8B576A1-7E16-42E0-B57F-13D40A40351B"
      },
      {
        "state" : "Shutdown",
        "availability" : "(available)",
        "name" : "iPhone 6 Plus",
        "udid" : "FF3D10F7-E34C-4DC4-AA71-3652DA007507"
      },
      {
        "state" : "Shutdown",
        "availability" : "(available)",
        "name" : "iPhone 6s",
        "udid" : "1CC10D05-CC5E-4ACA-BE27-A0E60F5A8602"
      },
      {
        "state" : "Shutdown",
        "availability" : "(available)",
        "name" : "iPhone 6s Plus",
        "udid" : "E93CBF20-D9F3-43F4-890E-CF28CAE5A4D5"
      },
      {
        "state" : "Booted",
        "availability" : "(available)",
        "name" : "iPhone 7",
        "udid" : "F7DF69A6-A497-4C16-9BFE-E9ACF5F77A44"
      },
      {
        "state" : "Shutdown",
        "availability" : "(available)",
        "name" : "iPhone 7 Plus",
        "udid" : "B591F32A-9825-4FFB-AAC6-2CBBF274F415"
      },
      {
        "state" : "Shutdown",
        "availability" : "(available)",
        "name" : "iPhone 8",
        "udid" : "DD41F867-CD9E-4E55-B60E-1112231D47DE"
      },
      {
        "state" : "Shutdown",
        "availability" : "(available)",
        "name" : "iPhone 8 Plus",
        "udid" : "C1BEE113-57C5-410B-8CB9-BC86D5153A0E"
      },
      {
        "state" : "Shutdown",
        "availability" : "(available)",
        "name" : "iPhone SE",
        "udid" : "C2F4AC11-BA1F-4B78-873D-72C4D096CA90"
      },
      {
        "state" : "Shutdown",
        "availability" : "(available)",
        "name" : "iPhone X",
        "udid" : "1DBA6411-7C7B-43A1-A210-09DC05B1177B"
      },
      {
        "state" : "Shutdown",
        "availability" : "(available)",
        "name" : "iPad Air",
        "udid" : "6E01FC23-AF4C-40D3-83F5-652EC04AEA90"
      },
      {
        "state" : "Shutdown",
        "availability" : "(available)",
        "name" : "iPad Air 2",
        "udid" : "5980BB28-A8E7-41C4-A45E-15C12B61A92A"
      },
      {
        "state" : "Shutdown",
        "availability" : "(available)",
        "name" : "iPad (5th generation)",
        "udid" : "F027DD6B-5800-42D8-9A21-2B4B690F78FB"
      },
      {
        "state" : "Shutdown",
        "availability" : "(available)",
        "name" : "iPad Pro (9.7-inch)",
        "udid" : "CEB9CB16-5476-4624-B6A6-CEFCFCA7225A"
      },
      {
        "state" : "Shutdown",
        "availability" : "(available)",
        "name" : "iPad Pro (12.9-inch)",
        "udid" : "B2CE6FE3-B672-474B-89AB-95C8C7825580"
      },
      {
        "state" : "Shutdown",
        "availability" : "(available)",
        "name" : "iPad Pro (12.9-inch) (2nd generation)",
        "udid" : "36382597-F19C-408F-B07A-1495CC7E9F51"
      },
      {
        "state" : "Shutdown",
        "availability" : "(available)",
        "name" : "iPad Pro (10.5-inch)",
        "udid" : "3A2CAD60-515D-4B81-871B-D299966B12A9"
      }
    ],
    "iOS 10.3" : [
],
"com.apple.CoreSimulator.SimRuntime.tvOS-11-0" : [
  {
    "state" : "Shutdown",
    "availability" : " (unavailable, runtime profile not found)",
    "name" : "Apple TV",
    "udid" : "1A21678D-25F1-48BE-AAB9-5DA015E56110"
  },
  {
    "state" : "Shutdown",
    "availability" : " (unavailable, runtime profile not found)",
    "name" : "Apple TV 4K",
    "udid" : "207397C7-43E4-436D-B00E-D55DBE22B66F"
  },
  {
    "state" : "Shutdown",
    "availability" : " (unavailable, runtime profile not found)",
    "name" : "Apple TV 4K (at 1080p)",
    "udid" : "D5774BA2-954D-45E3-836E-5B7DE84AA96B"
  }
],
"com.apple.CoreSimulator.SimRuntime.tvOS-11-1" : [
  {
    "state" : "Shutdown",
    "availability" : " (unavailable, runtime profile not found)",
    "name" : "Apple TV",
    "udid" : "0C4D1F49-D04C-4734-9808-F4FFE107778C"
  },
  {
    "state" : "Shutdown",
    "availability" : " (unavailable, runtime profile not found)",
    "name" : "Apple TV 4K",
    "udid" : "2E165873-D9DE-49ED-971D-A36E2D77FD9C"
  },
  {
    "state" : "Shutdown",
    "availability" : " (unavailable, runtime profile not found)",
    "name" : "Apple TV 4K (at 1080p)",
    "udid" : "03A7D4BF-97DA-41A1-8525-E55CBF2E0384"
  }
],
"tvOS 11.4" : [
  {
    "state" : "Shutdown",
    "availability" : "(available)",
    "name" : "Apple TV",
    "udid" : "4BBA7004-287F-4E0C-B41D-F8E40EDDDC50"
  },
  {
    "state" : "Shutdown",
    "availability" : "(available)",
    "name" : "Apple TV 4K",
    "udid" : "1F5A6546-FF26-4C8B-9930-F2263A48F6F6"
  },
  {
    "state" : "Shutdown",
    "availability" : "(available)",
    "name" : "Apple TV 4K (at 1080p)",
    "udid" : "CDC28F1D-38D3-4E75-8A64-35ADE73B00BC"
  }
],
"com.apple.CoreSimulator.SimRuntime.watchOS-4-1" : [
  {
    "state" : "Shutdown",
    "availability" : " (unavailable, runtime profile not found)",
    "name" : "Apple Watch - 38mm",
    "udid" : "23D138CF-55C0-4883-AD90-B08B23620852"
  },
  {
    "state" : "Shutdown",
    "availability" : " (unavailable, runtime profile not found)",
    "name" : "Apple Watch - 42mm",
    "udid" : "48553E41-5EE9-49BE-A0F1-17A185772B0E"
  },
  {
    "state" : "Shutdown",
    "availability" : " (unavailable, runtime profile not found)",
    "name" : "Apple Watch Series 2 - 38mm",
    "udid" : "49833B77-6588-4DB2-AE6C-4ABBE63463BD"
  },
  {
    "state" : "Shutdown",
    "availability" : " (unavailable, runtime profile not found)",
    "name" : "Apple Watch Series 2 - 42mm",
    "udid" : "60139A9E-593E-44EB-A4B6-FE1E2E450A7D"
  },
  {
    "state" : "Shutdown",
    "availability" : " (unavailable, runtime profile not found)",
    "name" : "Apple Watch Series 3 - 38mm",
    "udid" : "EF0455F4-FDCD-4803-B346-744DF2516FE7"
  },
  {
    "state" : "Shutdown",
    "availability" : " (unavailable, runtime profile not found)",
    "name" : "Apple Watch Series 3 - 42mm",
    "udid" : "234B16FB-264F-4722-A8F7-6590A7BE5F88"
  }
],
"iOS 8.4" : [

],
"watchOS 4.3" : [
  {
    "state" : "Shutdown",
    "availability" : "(available)",
    "name" : "Apple Watch - 38mm",
    "udid" : "5EEA0FC4-7181-4662-928E-35A8361E3375"
  },
  {
    "state" : "Shutdown",
    "availability" : "(available)",
    "name" : "Apple Watch - 42mm",
    "udid" : "BEE55E08-9459-4D29-93CC-A9E506C1FAD4"
  },
  {
    "state" : "Shutdown",
    "availability" : "(available)",
    "name" : "Apple Watch Series 2 - 38mm",
    "udid" : "54C4B936-3831-48D7-BC28-058D20D43129"
  },
  {
    "state" : "Shutdown",
    "availability" : "(available)",
    "name" : "Apple Watch Series 2 - 42mm",
    "udid" : "EBD32D98-B0B6-4615-A784-C553D1CB943C"
  },
  {
    "state" : "Shutdown",
    "availability" : "(available)",
    "name" : "Apple Watch Series 3 - 38mm",
    "udid" : "343FAD4C-ABED-466A-89BD-A2A3629D8F1D"
  },
  {
    "state" : "Shutdown",
    "availability" : "(available)",
    "name" : "Apple Watch Series 3 - 42mm",
    "udid" : "632F3BF5-7F24-42D5-BE9C-80F62D0A0EC6"
  }
],
"com.apple.CoreSimulator.SimRuntime.tvOS-11-2" : [
  {
    "state" : "Shutdown",
    "availability" : " (unavailable, runtime profile not found)",
    "name" : "Apple TV",
    "udid" : "6E9991E4-9070-4B4C-917F-F05B06DBF676"
  },
  {
    "state" : "Shutdown",
    "availability" : " (unavailable, runtime profile not found)",
    "name" : "Apple TV 4K",
    "udid" : "40BEB7E5-1B44-40FF-988B-DBBA5031F0DF"
  },
  {
    "state" : "Shutdown",
    "availability" : " (unavailable, runtime profile not found)",
    "name" : "Apple TV 4K (at 1080p)",
    "udid" : "DED8619F-A2E7-4363-B4A4-19DDB43078E3"
  }
],
"iOS 9.3" : [

]

},
"pairs" : {
"0F9AA0FB-B396-4F47-A7D9-B3EE1B34C45A" : {
"watch" : {
"name" : "Apple Watch Series 3 - 42mm",
"udid" : "234B16FB-264F-4722-A8F7-6590A7BE5F88",
"state" : "Shutdown"
},
"phone" : {
"name" : "iPhone 8 Plus",
"udid" : "B187A89E-A645-448F-AFEB-344A9F7939FB",
"state" : "Shutdown"
},
"state" : "(unavailable)"
},
"4238A97B-E6FF-4F5F-A21A-617DBA699D43" : {
"watch" : {
"name" : "Apple Watch Series 2 - 38mm",
"udid" : "54C4B936-3831-48D7-BC28-058D20D43129",
"state" : "Shutdown"
},
"phone" : {
"name" : "iPhone 7",
"udid" : "F7DF69A6-A497-4C16-9BFE-E9ACF5F77A44",
"state" : "Booted"
},
"state" : "(active, disconnected)"
},
"B34C79B5-1A8C-4B3F-B2AD-B6F774302DD5" : {
"watch" : {
"name" : "Apple Watch Series 2 - 42mm",
"udid" : "95A6604D-4CA4-4D67-AB4A-22A56B9C7D40",
"state" : "Shutdown"
},
"phone" : {
"name" : "iPhone 7 Plus",
"udid" : "CA460A1E-77AC-4EC5-AE10-103658C51209",
"state" : "Shutdown"
},
"state" : "(unavailable)"
},
"E52D7545-4E7E-4717-9A0B-BB4616026F17" : {
"watch" : {
"name" : "Apple Watch Series 3 - 42mm",
"udid" : "632F3BF5-7F24-42D5-BE9C-80F62D0A0EC6",
"state" : "Shutdown"
},
"phone" : {
"name" : "iPhone 8 Plus",
"udid" : "C1BEE113-57C5-410B-8CB9-BC86D5153A0E",
"state" : "Shutdown"
},
"state" : "(active, disconnected)"
},
"B9D61A57-6BA4-46EA-9F32-BD7A9597E0F3" : {
"watch" : {
"name" : "Apple Watch Series 2 - 38mm",
"udid" : "49833B77-6588-4DB2-AE6C-4ABBE63463BD",
"state" : "Shutdown"
},
"phone" : {
"name" : "iPhone 7",
"udid" : "B74BA84A-F0F8-4CB1-AE5B-BDFAC198B6EE",
"state" : "Shutdown"
},
"state" : "(unavailable)"
},
"B3743810-3C17-4163-A137-EE7E9ECB75CD" : {
"watch" : {
"name" : "Apple Watch Series 3 - 38mm",
"udid" : "EF0455F4-FDCD-4803-B346-744DF2516FE7",
"state" : "Shutdown"
},
"phone" : {
"name" : "iPhone 8",
"udid" : "C2BF06FE-6068-4EC1-81EE-1D037D19D01D",
"state" : "Shutdown"
},
"state" : "(unavailable)"
},
"3EBC1FD5-FA5D-4671-B418-48BDC5718001" : {
"watch" : {
"name" : "Apple Watch Series 2 - 42mm",
"udid" : "EBD32D98-B0B6-4615-A784-C553D1CB943C",
"state" : "Shutdown"
},
"phone" : {
"name" : "iPhone 7 Plus",
"udid" : "B591F32A-9825-4FFB-AAC6-2CBBF274F415",
"state" : "Shutdown"
},
"state" : "(active, disconnected)"
},
"3E2996B4-63B3-4685-B7CE-D7D8848FCA56" : {
"watch" : {
"name" : "Apple Watch Series 2 - 38mm",
"udid" : "C39FC17F-CFAF-4991-B689-F97EE86A24E1",
"state" : "Shutdown"
},
"phone" : {
"name" : "iPhone 7",
"udid" : "98BFA8EE-7BCA-4AED-A34A-2AC9614B1638",
"state" : "Shutdown"
},
"state" : "(unavailable)"
},
"147FC777-BACC-4570-8B0F-C698DD53E04A" : {
"watch" : {
"name" : "Apple Watch Series 3 - 38mm",
"udid" : "944DE295-A6F8-4DEA-9D5A-9B53BE76A607",
"state" : "Shutdown"
},
"phone" : {
"name" : "iPhone 8",
"udid" : "BB86F755-206E-45A5-B4C0-E55AB4BB2773",
"state" : "Shutdown"
},
"state" : "(unavailable)"
},
"C421A7F7-9DEE-4729-B6D1-D5FB385667E9" : {
"watch" : {
"name" : "Watch2017 - 38mm",
"udid" : "57A2EB6D-AAD0-4489-8FF2-4F4F386D9DBF",
"state" : "Shutdown"
},
"phone" : {
"name" : "iPhone 8",
"udid" : "55FF25DC-1558-4C0C-AD50-06977D062EAD",
"state" : "Shutdown"
},
"state" : "(unavailable)"
},
"993D2930-03A8-4659-A353-0FA4F0731C85" : {
"watch" : {
"name" : "Apple Watch Series 3 - 38mm",
"udid" : "343FAD4C-ABED-466A-89BD-A2A3629D8F1D",
"state" : "Shutdown"
},
"phone" : {
"name" : "iPhone 8",
"udid" : "DD41F867-CD9E-4E55-B60E-1112231D47DE",
"state" : "Shutdown"
},
"state" : "(active, disconnected)"
},
"B47CDAF7-1383-4022-8EB1-C83288BC0AB3" : {
"watch" : {
"name" : "Apple Watch Series 2 - 38mm",
"udid" : "0F0538C5-9A9C-4500-8E79-2BF76225E9EE",
"state" : "Shutdown"
},
"phone" : {
"name" : "iPhone 7",
"udid" : "0798F4EC-0537-4CA4-937D-D1735C408D5A",
"state" : "Shutdown"
},
"state" : "(unavailable)"
},
"4871361A-8F7B-481B-B698-653D9D2ED95E" : {
"watch" : {
"name" : "Apple Watch Series 2 - 42mm",
"udid" : "53C26596-0049-4386-968C-451AC498EADC",
"state" : "Shutdown"
},
"phone" : {
"name" : "iPhone 7 Plus",
"udid" : "26F65311-9352-41E5-8E43-4E8895FA1DE6",
"state" : "Shutdown"
},
"state" : "(unavailable)"
},
"50E3DAAE-DE67-4D5D-A31D-946854926621" : {
"watch" : {
"name" : "Watch2017 - 42mm",
"udid" : "3802112E-748A-42C0-8539-55A168FA9C9F",
"state" : "Shutdown"
},
"phone" : {
"name" : "iPhone 8 Plus",
"udid" : "236A299E-E70C-48FC-B999-0F4F6329B247",
"state" : "Shutdown"
},
"state" : "(unavailable)"
},
"7072968A-911F-42F9-9539-E82F6137ED37" : {
"watch" : {
"name" : "Apple Watch Series 2 - 42mm",
"udid" : "60139A9E-593E-44EB-A4B6-FE1E2E450A7D",
"state" : "Shutdown"
},
"phone" : {
"name" : "iPhone 7 Plus",
"udid" : "2C4A6F2C-BA44-4C4D-B95F-EE394014FBED",
"state" : "Shutdown"
},
"state" : "(unavailable)"
},
"3B8B2208-E2EF-4457-9D0E-9B9D9918BDAC" : {
"watch" : {
"name" : "Apple Watch Series 3 - 42mm",
"udid" : "F3B1DB45-21B4-4DB3-897C-2C721E6E5681",
"state" : "Shutdown"
},
"phone" : {
"name" : "iPhone 8 Plus",
"udid" : "6B0798E9-7A6F-4706-B0A9-D4887A5AEDB2",
"state" : "Shutdown"
},
"state" : "(unavailable)"
}
}
}
: applesimutils --list --byType "iPhone 6" --byOS "11.4"
: Searching for device matching iPhone 6...
2: stdout: [
{
"deviceType" : {
"name" : "iPhone 6",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-6"
},
"state" : "Booted",
"availability" : "(available)",
"name" : "iPhone 6",
"udid" : "D8B576A1-7E16-42E0-B57F-13D40A40351B",
"os" : {
"version" : "11.4",
"availability" : "(available)",
"name" : "iOS 11.4",
"identifier" : "com.apple.CoreSimulator.SimRuntime.iOS-11-4",
"buildversion" : "15F79"
}
}
]
: applesimutils --list --byId "D8B576A1-7E16-42E0-B57F-13D40A40351B"
3: stdout: [
{
"deviceType" : {
"name" : "iPhone 6",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-6"
},
"state" : "Booted",
"availability" : "(available)",
"name" : "iPhone 6",
"udid" : "D8B576A1-7E16-42E0-B57F-13D40A40351B",
"os" : {
"version" : "11.4",
"availability" : "(available)",
"name" : "iOS 11.4",
"identifier" : "com.apple.CoreSimulator.SimRuntime.iOS-11-4",
"buildversion" : "15F79"
}
}
]
: /usr/bin/xcrun simctl uninstall D8B576A1-7E16-42E0-B57F-13D40A40351B com.entria.gol.app
: Uninstalling com.entria.gol.app...
: com.entria.gol.app uninstalled
: /usr/bin/xcrun simctl install D8B576A1-7E16-42E0-B57F-13D40A40351B "/Users/sibelius/Dev/entria/gol/gol-app/ios/build/Build/Products/Debug-iphonesimulator/golapp.app"
: Installing /Users/sibelius/Dev/entria/gol/gol-app/ios/build/Build/Products/Debug-iphonesimulator/golapp.app...
: /Users/sibelius/Dev/entria/gol/gol-app/ios/build/Build/Products/Debug-iphonesimulator/golapp.app installed
: /usr/bin/xcrun simctl terminate D8B576A1-7E16-42E0-B57F-13D40A40351B com.entria.gol.app
: Terminating com.entria.gol.app...
: com.entria.gol.app terminated
7: /bin/cat /dev/null >/Users/sibelius/Library/Developer/CoreSimulator/Devices/D8B576A1-7E16-42E0-B57F-13D40A40351B/data/tmp/detox.last_launch_app_log.out 2>/Users/sibelius/Library/Developer/CoreSimulator/Devices/D8B576A1-7E16-42E0-B57F-13D40A40351B/data/tmp/detox.last_launch_app_log.err && SIMCTL_CHILD_DYLD_INSERT_LIBRARIES="/Users/sibelius/Library/Detox/ios/6835fdc9621ba06e099f505790cc7b06d2e6c1b5/Detox.framework/Detox" /usr/bin/xcrun simctl launch --stdout=/tmp/detox.last_launch_app_log.out --stderr=/tmp/detox.last_launch_app_log.err D8B576A1-7E16-42E0-B57F-13D40A40351B com.entria.gol.app --args -detoxServer ws://localhost 55171 -detoxSessionId e79eb251-131c-f14d-8532-e7697fc3f0d1
: Launching com.entria.gol.app...
7: stdout: com.entria.gol.app: 41974
7: com.entria.gol.app launched. The stdout and stderr logs were recreated, you can watch them with:
tail -F /Users/sibelius/Library/Developer/CoreSimulator/Devices/D8B576A1-7E16-42E0-B57F-13D40A40351B/data/tmp/detox.last_launch_app_log.{out,err}
send: {"type":"isReady","params":{},"messageId":-1000}
finalized artifacts successfully
FAIL  e2e/firstTest.spec.js (121.072s)
Example
✕ should have welcome screen (6ms)
✕ should show hello screen after tap (4ms)
✕ should show world screen after tap (1ms)
● Example › should have welcome screen
Timeout - Async callback was not invoked within the 120000ms timeout specified by jest.setTimeout.

  at mapper (../node_modules/jest-jasmine2/build/queue_runner.js:41:52)

● Example › should have welcome screen
ReferenceError: device is not defined

  1 | describe('Example', () => {
  2 |   beforeEach(async () => {
> 3 |     await device.reloadReactNative();
    |           ^
  4 |   });
  5 |
  6 |   it('should have welcome screen', async () => {

  at Object._callee$ (firstTest.spec.js:3:11)
  at tryCatch (../node_modules/regenerator-runtime/runtime.js:65:40)
  at Generator.invoke [as _invoke] (../node_modules/regenerator-runtime/runtime.js:303:22)
  at Generator.prototype.(anonymous function) [as next] (../node_modules/regenerator-runtime/runtime.js:117:21)
  at tryCatch (../node_modules/regenerator-runtime/runtime.js:65:40)
  at invoke (../node_modules/regenerator-runtime/runtime.js:155:20)
  at ../node_modules/regenerator-runtime/runtime.js:202:11
  at callInvokeWithMethodAndArg (../node_modules/regenerator-runtime/runtime.js:201:16)
  at AsyncIterator.enqueue (../node_modules/regenerator-runtime/runtime.js:224:13)
  at AsyncIterator.prototype.(anonymous function) [as next] (../node_modules/regenerator-runtime/runtime.js:117:21)
  at Object.<anonymous>.runtime.async (../node_modules/regenerator-runtime/runtime.js:248:14)
  at Object._callee (firstTest.spec.js:2:14)

● Example › should have welcome screen
ReferenceError: element is not defined

  4 |   });
  5 |
> 6 |   it('should have welcome screen', async () => {
    |                                    ^
  7 |     await expect(element(by.id('welcome'))).toBeVisible();
  8 |   });
  9 |

</details>

Are you using a precompiled swift library?

yes, we use this bridge: https://github.com/entria/react-native-visa-checkout

I don't see swift in that project, what am I missing?
Anyway, Detox has some swift code, and is being compiled on your computer at postinsall.
If you have two or more Xcode versions on your computer make sure your command line tools are the same version as the Xcode you use.

Could also be that the precompiled Swift lib brings precompiled Swift frameworks, different from the Xcode ones. There is no practical way to support that in Detox.

@sibelius If you run
detox clean-framework-cache
detox build-framework-cache

Does it help?

I ran this 2 commands
detox clean-framework-cache
detox build-framework-cache

but it did not help, same error
do you have any tips of how to find out if we have a swift precompiled frameworks?
we also use react-native-firebase, react-native-camera with google visio for face detector

Explore your project; see which dependencies come precompiled, rather than source. Of those, see which bring Swift frameworks. When you discover the one, you need to understand what version of Xcode it was compiled with, and use that version exactly in order for Detox to work with the dependency. Or, update the dependency for the latest available Xcode.
Because Swift does not have a stable ABI, it is very fragile, as you see. Xcode versions need to match so that Swift versions match.


pre-compiled armv7l_universal_<IP_ADDRESS> install dies, fibers is missing

OS raspbian rpi2
node -v v0.12.6 from adafruit
cd /usr/local/lib
git clone https://github.com/4commerce-technologies-AG/meteor.git
cd meteor
meteor --version
It's the first time you've run Meteor from a git checkout.
I will download a kit containing all of Meteor's dependencies.
Skipping download and installing kit from dev_bundle_Linux_armv7l_universal_<IP_ADDRESS>_RASPBIAN-WHEEZY_0.4.18.tar.gz
Installed dependency kit v0.4.18 in dev_bundle.
/usr/local/lib/meteor/dev_bundle/lib/node_modules/fibers/fibers.js:16
throw new Error(''+ modPath+ '.node is missing. Try reinstalling node-fibe               ^ Error: /usr/local/lib/meteor/dev_bundle/lib/node_modules/fibers/bin/linux-arm-v8-3.28/fibers.nodeis missing. Try reinstallingnode-fibers`?
at Object. (/usr/local/lib/meteor/dev_bundle/lib/node_modules/fibers/fibers.js:16:8)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Module.require (module.js:365:17)
at require (module.js:384:17)
at Object. (/usr/local/lib/meteor/tools/main.js:7:13)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)

You might want to recompile fibers where it is missing. Try this :
cd /usr/local/lib/meteor/dev_bundle/lib/
npm install<EMAIL_ADDRESS>
Then try to launch meteor again

Will do. Thanks
On Aug 27, 2015 1:46 AM, "Thomas P."<EMAIL_ADDRESS>wrote:

You might want to recompile fibers where it is missing. Try this :
cd /usr/local/lib/meteor/dev_bundle/lib/
npm install<EMAIL_ADDRESS>Then try to launch meteor again
—
Reply to this email directly or view it on GitHub
https://github.com/4commerce-technologies-AG/meteor/issues/22#issuecomment-135324652
.

Hi,
I guess your problem depends on  the node version. Only node v0.10.36 - v0.10.40+ is supported from meteor.
You may try our pre-compiled version as well or take a look at the tumblr blog about compiling node by your own.
Good luck
Tom

aah, I thought meteor required 0.12+. This is good info, thanks.
On Thu, Aug 27, 2015 at 7:22 AM, Tom Freudenberg<EMAIL_ADDRESS>wrote:

Hi,
I guess your problem depends on the node version. Only node v0.10.36 -
v0.10.40+ is supported from meteor.
You may try our pre-compiled version as well or take a look at the tumblr
blog about compiling node by your own.
Good luck
Tom
—
Reply to this email directly or view it on GitHub
https://github.com/4commerce-technologies-AG/meteor/issues/22#issuecomment-135426496
.

--
Dr. Craig Hollabaugh
<EMAIL_ADDRESS>970 690 4911

TPXP,
Thanks for the info. trying to recompile fibers throws an error.
root@raspbian2[504]: node -v
v0.12.6
root@raspbian2[505]: cd /usr/local/lib/meteor/dev_bundle/lib/
root@raspbian2[506]: npm install<EMAIL_ADDRESS>npm ERR! Linux 3.18.14-v7+
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"<EMAIL_ADDRESS>npm ERR! node v0.12.6
npm ERR! npm  v2.11.2
npm ERR! code ETARGET
npm ERR! notarget No compatible version found<EMAIL_ADDRESS><3.29.0'
npm ERR! notarget Valid install targets:
npm ERR! notarget ["0.1.0","0.1.1","0.1.2","0.1.3","0.1.4","0.1.6","0.1.7","0.1.8","0.2.0","0.2.1","0.2.2","0.2.3","0.2.4","0.2.5","0.2.6","0.5.0","0.6.0","0.5.1","0.6.1","0.6.2","0.6.3","0.6.4","0.6.5","0.6.6","0.6.7","0.6.8","0.6.9","1.0.0","1.0.1","1.0.2","1.0.4","1.0.5","1.0.6"]
npm ERR! notarget
npm ERR! notarget This is most likely not a problem with npm itself.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! Please include the following file with any support request:
npm ERR!     /usr/local/lib/meteor/dev_bundle/lib/npm-debug.log
Now I'm going to downgrade node from 0.12+ to 0.10 as Tom Freudenberg suggested.
Craig

OK, switched node down to version 0.10.36 per TomF's suggestion. Using the prebuilt, dev_bundle_Linux_armv7l_universal_<IP_ADDRESS>_RASPBIAN-WHEEZY_0.4.18.tar.gz, I know have a libstdc++ version error.
Error: /usr/lib/arm-linux-gnueabihf/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /usr/local/lib/meteor/dev_bundle/lib/node_modules/fibers/bin/linux-arm-v8-3.14/fibers.node)
root@raspbian2[556]: ls -l /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
lrwxrwxrwx 1 root root 19 Sep  6  2014 /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 -> libstdc++.so.6.0.19
any suggestions now? Thanks for your help.
ps. I have built from source code, node, meteor, redis, mongo in the past, see
https://www.youtube.com/watch?v=z4sM1kiLooc
just didn't want to do it again yesterday. I figured I'd try the prebuilt option this time.
My system is update to date with dist-upgrade.

Hi, I am not at a Computer right now but what about your node installation? Is is working?
node -v
npm -v
You could try to start without a prebundle and generate meteor by yourself.
Just remove the prebuild tgz and follow the guide from blog or github
What Debian you are using?
cat /etc/debian_version
Good luck
Tom

root@raspbian2[578]: node -v
v0.10.36
root@raspbian2[579]: npm -v
1.4.28
root@raspbian2[580]: cat /etc/debian_version
7.8
I'm trying the meteor build without pre-bundle now.

Just a note about the fibers npm build : I made a mistake by adding a version number after fibers in the npm install command. You might want to try again without the @3.28 after fibers (I edited my comment).
By the way, did you build the dev bundle yourself ? Maybe the one provided by Tom is a bit outdated...

When I run
scripts/generate-dev-bundle.sh
I get tons of errors, pages of stack traces. Let me start over again with a
fresh raspbian install and get back. Thanks for writing.
On Fri, Aug 28, 2015 at 11:07 AM, Thomas P<EMAIL_ADDRESS>wrote:

Just a note about the fibers npm build : I made a mistake by adding a
version number after fibers in the npm install command. You might want to
try again without the @3.28 after fibers (I edited my comment).
By the way, did you build the dev bundle yourself ? Maybe the one provided
by Tom is a bit outdated...
—
Reply to this email directly or view it on GitHub
https://github.com/4commerce-technologies-AG/meteor/issues/22#issuecomment-135834100
.

--
Dr. Craig Hollabaugh
<EMAIL_ADDRESS>970 690 4911

OK, I started over again with new SD, raspbian 2015-05-05 install, expanded disk to 16G, followed http://meteor-universal.tumblr.com/ instructions exactly (using pre-built gz file), install went flawless!  New board/SD card to 'RPI2 meteor' in about 30 minutes.
I've deleted all my dated notes on raspberrypi node, mongo, meteor install, replaced with http://meteor-universal.tumblr.com/. I'm thankful for the help and am sorry to waste everyone's time.
Where is the 'Donate' button?

Hi,
If you did not get it run with a fresh raspian, I can spend some time if you give me access to your system.
First try with a new raspian, normally list should work flawlessly.
 Thanks for not giving up.
Tom

Thanks Tom,
Have a great weekend!
I'm finishing a project now to demo a wide combination of technologies, meteor on RPI is the backend. I'll keep you posted when I publish the youtube video.
Craig


Fix mesheryctl pattern delete

Signed-off-by: Utkarsh Srivastava<EMAIL_ADDRESS>Description
mesheryctl pattern delete -f <path>  doesn't work because command is not accepting any flags. This PR just fixes that.
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

Codecov Report

Merging #3633 (57981bf) into master (2ca0b32) will decrease coverage by 8.36%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3633      +/-   ##
==========================================
- Coverage   18.60%   10.23%   -8.37%
==========================================
  Files          38       38
  Lines        3301     3301
==========================================
- Hits          614      338     -276
- Misses       2531     2894     +363
+ Partials      156       69      -87

Flag
Coverage Δ

gointegrationtests
?

unittests
10.23% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

mesheryctl/internal/cli/root/system/status.go
0.00% <0.00%> (-62.13%)
:arrow_down:

mesheryctl/internal/cli/root/system/start.go
1.20% <0.00%> (-52.40%)
:arrow_down:

mesheryctl/internal/cli/root/system/stop.go
0.90% <0.00%> (-39.10%)
:arrow_down:

mesheryctl/internal/cli/root/system/check.go
1.48% <0.00%> (-22.68%)
: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 2ca0b32...57981bf. Read the comment docs.

Post golangci-lint step is failing here...


Why the Data Source cannot be displayed

Hi,
Why the Data Source cannot be displayed, what files need to be configured
Please help me solve this problem.I would appreciate it if you can help me!
Description

hi @52766365
Please check Pinpoint supports DataSource or Dbcp that you used.
If it does not show even though it is supported, check the agent log to find the problem.
thanks :)

嗨@ 52766365
请检查Pinpoint支持您使用的DataSource或Dbcp。
如果即使支持它也没有显示，请检查代理日志以查找问题。
谢谢 ：）

hi @52766365
Please check Pinpoint supports DataSource or Dbcp that you used.
If it does not show even though it is supported, check the agent log to find the problem.
thanks :)

Does the data source data connection monitoring support DB2 database?


modified devcontainer to remove error

steps:
use ctrl+shift+P and select Dev Containers: Rebuild and Reopen in Container to open container
once successfully loaded, run in terminal npm run dev
Note: Make sure to pull node: 20 for image defined in devcontainer.json
If not installed run:
docker pull node:20

@anushamahajan5 Please resolve the conflicts

@idagelic resolved kindly check


Error: provided an invalid property of "generateScopedName"

sorry if i've missed something but i'm getting the error when trying this
.bablerc
{
  "presets": ["es2015", "stage-0", "react"],
  "plugins": [
    "css-modules-transform", {
       "generateScopedName": "[name]__[local]___[hash:base64:5]"
    }
  ]
}

error

Error: Plugin 1 specified in "..../.babelrc" provided an invalid property of "generateScopedName"

it's working fine like this, but i need it to hash it like above.
{
  "presets": ["es2015", "stage-0", "react"],
  "plugins": [
    "css-modules-transform"
  ]
}

thanks.

Hello, you need to specify it like this:
{
  "presets": ["es2015", "stage-0", "react"],
  "plugins": [
    ["css-modules-transform", {
       "generateScopedName": "[name]__[local]___[hash:base64:5]"
    }]
  ]
}

Did this help you?

yup.  thanks !


Added .gradle folder to unity.gitignore

The newest version of Unity creates a .gradle folder when creating an Android build, that is just unnecessary clutter.
This small addition helps solve that problem by ignoring it.

Looks like this was already covered by #2906 - thanks for the contribution anyway @BabyBluee!


[NOT READY]test: implement e2e tests

We should fix the context deadline error.
Also maybe mention in the docs that we use Traefik for the implementation used in the e2e tests.
Otherwise I really like how easy you can run the tests locally and with CI using the exact same mechanism :-)
Great job!

Ok I tested again, and tests always pass now.


Firmware boot files doesn't appeared in deployment directory

Yocto deploy directory should contain 'bootfiles' directory with follow files:

bootcode.bin
config.txt
fixup4.dat
fixup4db.dat
fixup_cd.dat
fixup_x.dat
start.elf
start4cd.elf
start4x.elf
start_db.elf
cmdline.txt
fixup.dat
fixup4cd.dat
fixup4x.dat
fixup_db.dat
start4.elf
start4db.elf
start_cd.elf
start_x.elf
However after partial build this directory is empty.

Should be fixed after merging https://github.com/xen-troops/meta-xt-rpi5/pull/11


zopen-build: Generate a zstd-compressed asset, use sha256 checksum, change package naming convention

Adds code to build a zstd compressed asset based on discussion in https://github.com/ZOSOpenTools/meta/issues/613#issuecomment-1849283271
Changes metadata.json to specify an array of assets, now including pax.Z and .zst
changes the package naming convention to ${PACKAGE_NAME}-${versionString}-${date}.zos.pax" so that we include the correct version string

The 'date' part can be found from the file's creation/modification time, right?
Typing this out to see how it looks :grin:
current:
zstd-<IP_ADDRESS>31124_101200.zos.pax.Z
linux/s390x:
zstd-1.5.5-4.fc39.s390x.rpm
zos/s390x:
zstd-1.5.5-4.zos24.s390x.pax.zst
Makes me wonder... do we need to pax before running zstd on it?
pax is our rough equivalent of rpm/deb... as a container of files.
The -4 here refers to 4th release of the package at this v.r.m.

By adding in the release, are we now publishing 3 versions (2.4/2.5/3.1) ??   Linux platforms add in the os release as they do publish different releases for those os's.  Eg. Fedora 39 has python3-productmd-1.37-1.fc39_1.38-1.fc39.noarch.drpm  and released similar for fc38.  The normal expectation for a user would be that if the package has a z/OS 2.4/2.5/3.1, then it will only apply to that version, not that it applies to that and later versions.
Is s390x applicable to z/OS rather than Linux or is there a different naming convention (uname reports OS/390!!) - unless we are doing 24/31/64-bit versions then maybe those could be added.
tbh, your original ${PACKAGE_NAME}-${versionString}-${date}&time.zos.pax made sense to me :-)

are we now publishing 3 versions (2.4/2.5/3.1) ??

Setting up for it, hopefully. And dropping 2.4... soon.
We will end up setting up a "build matrix" in CI to do various combos.
I'm not entirely sure if, similarly, we need to keep separate builds for Go programs built in 1.19, 1.20, 1.21, etc.

python3-productmd-1.37-1.fc39_1.38-1.fc39.noarch.drpm

In this case, it may be a deltarpm file, that contains just the stuff to go from 1.37 to 1.39 in fc39.

The normal expectation for a user would be that if the package has a z/OS 2.4/2.5/3.1, then it will only apply to that version, not that it applies to that and later versions.

Yup, a package for a particular OS.
GOOS-GOARCH is zos/s390x so s390x still applies for z/OS.
s390 being 31-bit arch and s390x being 64-bit.
24/31/64 - :scream: - this is indeed an additional term we may need to add, assuming these refer to ports that run in 31-bit.

Last 2 sentences of previous comment... I wonder... does that mean 31-bit builds should be called zstd-1.5.5-4.zos24.s390.pax.zst.

For C/C++ we're still targeting V2R4 (https://github.com/ZOSOpenTools/comp_clangport/blob/main/buildenv#L84).

are we now publishing 3 versions (2.4/2.5/3.1) ??

Setting up for it, hopefully. And dropping 2.4... soon. We will end up setting up a "build matrix" in CI to do various combos.
I'm not entirely sure if, similarly, we need to keep separate builds for Go programs built in 1.19, 1.20, 1.21, etc.

python3-productmd-1.37-1.fc39_1.38-1.fc39.noarch.drpm

In this case, it may be a deltarpm file, that contains just the stuff to go from 1.37 to 1.39 in fc39.

The normal expectation for a user would be that if the package has a z/OS 2.4/2.5/3.1, then it will only apply to that version, not that it applies to that and later versions.

Yup, a package for a particular OS.
GOOS-GOARCH is zos/s390x so s390x still applies for z/OS. s390 being 31-bit arch and s390x being 64-bit.
24/31/64 - 😱 - this is indeed an additional term we may need to add, assuming these refer to ports that run in 31-bit.

Right now we're targeting 2.4 in our C/C++ builds: https://github.com/ZOSOpenTools/comp_clangport/blob/main/buildenv#L84 . Newer OS levels for z/OS are backwards compatible. So for us, this means the min OS level is 2.4, but it should work for 2.5, 3.1 as well. Perhaps we can use just "zos" as the release for now until we decide to add builds for each version?

Does anything need to go in before this, @IgorTodorovskiIBM?
Would be nice to see standard file names in the releases section :)

Does anything need to go in before this, @IgorTodorovskiIBM? Would be nice to see standard file names in the releases section :)

Don't think so, I'll need to the sync the branch and do further testing to make sure I'm not breaking anything


Logger::ERROR logs infos

sorry, i can be very lame, but
i'm using silex with monolog over mongodb
the following code performs my registration of the service →
$app->register(new Silex\Provider\MonologServiceProvider(),[
    'monolog.name' => 'silex-mongo-api',
    'monolog.level' => Monolog\Logger::ERROR,
    'monolog.bubble' => false,
    'monolog.handler' => new Monolog\Handler\MongoDBHandler(
        new \MongoClient( $app['config']['db']['server'] ),
        $app['config']['db']['database'],
        $app['config']['db']['logs']
    ),
]);

as far as i understand Monolog\Logger::ERROR would make Monolog log only errors.
but my collection log is plenty of INFO messages like
[_id] => MongoId Object (
    [$id] => 56898f2bf3e73f9f058b456a
)
[message] => < 200
[context] => Array (
)
[level] => 200
[level_name] => INFO
[channel] => silex-mongo-api
[datetime] => 2016-01-03 22:14:19
[extra] => Array (
)

is this a bug or am i doing something wrong?

The MongoDbHandler you create has a default level of DEBUG, so try this:
$app->register(new Silex\Provider\MonologServiceProvider(),[
    'monolog.name' => 'silex-mongo-api',
    'monolog.level' => Monolog\Logger::ERROR,
    'monolog.bubble' => false,
    'monolog.handler' => new Monolog\Handler\MongoDBHandler(
        new \MongoClient( $app['config']['db']['server'] ),
        $app['config']['db']['database'],
        $app['config']['db']['logs'],
        Monolog\Logger::ERROR
    ),
]);

I don't know what monolog.level does but maybe it's only for configuring default handlers.


🐛 [firebase_messaging] Error building with XCode (GULAppEnvironmentUtil)

Bug report
Describe the bug
After adding the dependency for firebase_messaging iOS stopped building and returns the following error:
In module 'GoogleUtilities' imported from /Users/mario/Desktop/shareio/ios/Pods/FirebaseMessaging/
FirebaseMessaging/Sources/FIRMessagingUtilities.m:20:

/Users/mario/Desktop/shareio/ios/Pods/GoogleUtilities/GoogleUtilities/
Environment/Public/GoogleUtilities/GULAppEnvironmentUtil.h:21:12: note: definition here is not reachable
    @interface GULAppEnvironmentUtil : NSObject

Additional context
pubspec.yaml
Click To Expand
name: shareio
description: A new Flutter project.

version: 1.0.0+1

environment:
  sdk: ">=2.12.0 <3.0.0"

dependencies:
  flutter:
    sdk: flutter
  cupertino_icons: ^1.0.2
  flutter_webrtc: ^0.8.1
  crypto: ^3.0.1
  provider: ^6.0.2
  file_picker: ^4.3.0
  path_provider: ^2.0.8
  permission_handler: ^8.3.0
  async: ^2.8.2
  worker_manager: ^4.2.4
  app_tracking_transparency: ^2.0.2+1
  firebase_core: ^1.10.6
  firebase_messaging: ^11.2.4
  flutter_local_notifications: ^9.2.0
  firebase_crashlytics: ^2.4.4
  firebase_performance: ^0.8.0+3
  firebase_analytics: ^9.0.4
  firebase_remote_config: ^1.0.3
  google_mobile_ads: ^1.0.1
  shared_preferences: ^2.0.11
  purchases_flutter: ^3.8.0
  webview_flutter: ^3.0.0
  ionicons: ^0.1.2
  intl: ^0.17.0

dev_dependencies:
  flutter:
    sdk: flutter
  flutter_launcher_icons: ^0.9.2

flutter_icons:
  android: "launcher_icon"
  ios: true
  image_path: "assets/icon/icon.png"

flutter:

  uses-material-design: true

  assets:
    - assets/icon/icon.png

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 2.8.1, on macOS 11.4 20F71 darwin-x64, locale en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.1)
[✓] IntelliJ IDEA Community Edition (version 2021.2.4)
[✓] VS Code (version 1.63.0)
[✓] Connected device (3 available)
    ! Error: Mário’s iPhone is busy: Fetching debug symbols for Mário’s iPhone. Xcode will continue when Mário’s iPhone is finished. (code -10)

• No issues found!

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 2.15.1
Flutter SDK 2.8.1
shareio 1.0.0+1

dependencies:
- app_tracking_transparency 2.0.2+1 [flutter]
- async 2.8.2 [collection meta]
- crypto 3.0.1 [collection typed_data]
- cupertino_icons 1.0.4
- file_picker 4.3.0 [flutter flutter_web_plugins flutter_plugin_android_lifecycle plugin_platform_interface ffi path]
- firebase_analytics 9.0.4 [firebase_analytics_platform_interface firebase_analytics_web firebase_core firebase_core_platform_interface flutter]
- firebase_core 1.10.6 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_crashlytics 2.4.4 [firebase_core firebase_core_platform_interface firebase_crashlytics_platform_interface flutter stack_trace]
- firebase_messaging 11.2.4 [firebase_core firebase_core_platform_interface firebase_messaging_platform_interface firebase_messaging_web flutter meta]
- firebase_performance 0.8.0+3 [firebase_core firebase_core_platform_interface firebase_performance_platform_interface firebase_performance_web flutter]
- firebase_remote_config 1.0.3 [firebase_core firebase_core_platform_interface firebase_remote_config_platform_interface firebase_remote_config_web flutter]
- flutter 0.0.0 [characters collection meta typed_data vector_math sky_engine]
- flutter_local_notifications 9.2.0 [clock flutter flutter_local_notifications_linux flutter_local_notifications_platform_interface timezone]
- flutter_webrtc 0.8.1 [dart_webrtc flutter path_provider webrtc_interface]
- google_mobile_ads 1.0.1 [meta flutter]
- intl 0.17.0 [clock path]
- ionicons 0.1.2 [flutter]
- path_provider 2.0.8 [flutter path_provider_android path_provider_ios path_provider_linux path_provider_macos path_provider_platform_interface path_provider_windows]
- permission_handler 8.3.0 [flutter meta permission_handler_platform_interface]
- provider 6.0.2 [collection flutter nested]
- purchases_flutter 3.8.0 [flutter collection]
- shared_preferences 2.0.11 [flutter meta shared_preferences_android shared_preferences_ios shared_preferences_linux shared_preferences_macos shared_preferences_platform_interface shared_preferences_web shared_preferences_windows]
- webview_flutter 3.0.0 [flutter webview_flutter_android webview_flutter_platform_interface webview_flutter_wkwebview]
- worker_manager 4.2.5 [async collection]

dev dependencies:
- flutter 0.0.0 [characters collection meta typed_data vector_math sky_engine]
- flutter_launcher_icons 0.9.2 [args image path yaml]

transitive dependencies:
- archive 3.1.6 [crypto path]
- args 2.3.0
- characters 1.2.0
- charcode 1.3.1
- clock 1.1.0
- collection 1.15.0
- dart_webrtc 1.0.3 [webrtc_interface]
- dbus 0.6.6 [args ffi meta xml]
- ffi 1.1.2
- file 6.1.2 [meta path]
- firebase 9.0.2 [http http_parser js]
- firebase_analytics_platform_interface 3.0.3 [firebase_core flutter meta plugin_platform_interface]
- firebase_analytics_web 0.4.0+4 [firebase_analytics_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- firebase_core_platform_interface 4.2.3 [collection flutter meta plugin_platform_interface]
- firebase_core_web 1.5.3 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_crashlytics_platform_interface 3.1.11 [collection firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_platform_interface 3.1.4 [firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_web 2.2.5 [firebase_core firebase_core_web firebase_messaging_platform_interface flutter flutter_web_plugins js meta]
- firebase_performance_platform_interface 0.1.0+3 [firebase_core flutter plugin_platform_interface]
- firebase_performance_web 0.1.0+3 [firebase firebase_core firebase_core_web firebase_performance_platform_interface flutter flutter_web_plugins js]
- firebase_remote_config_platform_interface 1.0.3 [firebase_core flutter meta plugin_platform_interface]
- firebase_remote_config_web 1.0.3 [firebase_core firebase_core_web firebase_remote_config_platform_interface flutter flutter_web_plugins js]
- flutter_local_notifications_linux 0.4.1+1 [flutter flutter_local_notifications_platform_interface dbus path xdg_directories]
- flutter_local_notifications_platform_interface 5.0.0 [flutter plugin_platform_interface]
- flutter_plugin_android_lifecycle 2.0.5 [flutter]
- flutter_web_plugins 0.0.0 [flutter js characters collection meta typed_data vector_math]
- http 0.13.4 [async http_parser meta path]
- http_parser 4.0.0 [charcode collection source_span string_scanner typed_data]
- image 3.1.0 [archive meta xml]
- js 0.6.3
- meta 1.7.0
- nested 1.0.0 [flutter]
- path 1.8.1
- path_provider_android 2.0.11 [flutter path_provider_platform_interface]
- path_provider_ios 2.0.7 [flutter path_provider_platform_interface]
- path_provider_linux 2.1.4 [ffi flutter meta path path_provider_platform_interface xdg_directories]
- path_provider_macos 2.0.4 [flutter meta path_provider_platform_interface]
- path_provider_platform_interface 2.0.1 [flutter meta platform plugin_platform_interface]
- path_provider_windows 2.0.4 [ffi flutter meta path path_provider_platform_interface win32]
- permission_handler_platform_interface 3.7.0 [flutter meta plugin_platform_interface]
- petitparser 4.4.0 [meta]
- platform 3.1.0
- plugin_platform_interface 2.0.2 [meta]
- process 4.2.4 [file path platform]
- shared_preferences_android 2.0.9 [flutter meta shared_preferences_platform_interface]
- shared_preferences_ios 2.0.8 [flutter meta shared_preferences_platform_interface]
- shared_preferences_linux 2.0.3 [file flutter meta path path_provider_linux shared_preferences_platform_interface]
- shared_preferences_macos 2.0.2 [flutter shared_preferences_platform_interface]
- shared_preferences_platform_interface 2.0.0 [flutter]
- shared_preferences_web 2.0.2 [flutter flutter_web_plugins meta shared_preferences_platform_interface]
- shared_preferences_windows 2.0.3 [file flutter meta path path_provider_platform_interface path_provider_windows shared_preferences_platform_interface]
- sky_engine 0.0.99
- source_span 1.8.1 [collection path term_glyph]
- stack_trace 1.10.0 [path]
- string_scanner 1.1.0 [charcode source_span]
- term_glyph 1.2.0
- timezone 0.8.0 [path]
- typed_data 1.3.0 [collection]
- vector_math 2.1.1
- webrtc_interface 1.0.1
- webview_flutter_android 2.8.2 [flutter webview_flutter_platform_interface]
- webview_flutter_platform_interface 1.8.0 [flutter plugin_platform_interface]
- webview_flutter_wkwebview 2.7.1 [flutter webview_flutter_platform_interface]
- win32 2.3.3 [ffi]
- xdg_directories 0.2.0 [meta path process]
- xml 5.3.1 [collection meta petitparser]
- yaml 3.1.0 [collection source_span string_scanner]

@mrcsilva
Can you try to update pods with pod repo update and then flutter clean and see if it helps ?
If not, can you provide your ios/podfile ?

@darshankawar
I ran pod repo update and then the script I have to clean and recreate the flutter project
Script
#!/bin/bash

flutter clean
rm pubspec.lock
flutter create .

cd ios
rm -rf Pods/ Podfile.lock ./.symlinks
pod repo update
pod install
cd ..

Then tried to build and run again and the same error appeared:
/Users/mario/Desktop/shareio/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/FIRMessagingUtilities.m:298:8:
error: definition of 'GULAppEnvironmentUtil' must be imported from module 'GoogleUtilities.GULAppEnvironmentUtil' before it is required
      if ([GULAppEnvironmentUtil isSimulator]) {
           ^
    In module 'GoogleUtilities' imported from /Users/mario/Desktop/shareio/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/FIRMessagingUtilities.m:20:
    /Users/mario/Desktop/shareio/ios/Pods/GoogleUtilities/GoogleUtilities/Environment/Public/GoogleUtilities/GULAppEnvironmentUtil.h:21:12: note: definition here is not reachable
    @interface GULAppEnvironmentUtil : NSObject

Podfile
# Uncomment this line to define a global platform for your project
platform :ios, '12.0'

# CocoaPods analytics sends network stats synchronously affecting flutter build latency.
ENV['COCOAPODS_DISABLE_STATS'] = 'true'

project 'Runner', {
  'Debug' => :debug,
  'Profile' => :release,
  'Release' => :release,
}

def flutter_root
  generated_xcode_build_settings_path = File.expand_path(File.join('..', 'Flutter', 'Generated.xcconfig'), __FILE__)
  unless File.exist?(generated_xcode_build_settings_path)
    raise "#{generated_xcode_build_settings_path} must exist. If you're running pod install manually, make sure flutter pub get is executed first"
  end

  File.foreach(generated_xcode_build_settings_path) do |line|
    matches = line.match(/FLUTTER_ROOT\=(.*)/)
    return matches[1].strip if matches
  end
  raise "FLUTTER_ROOT not found in #{generated_xcode_build_settings_path}. Try deleting Generated.xcconfig, then run flutter pub get"
end

require File.expand_path(File.join('packages', 'flutter_tools', 'bin', 'podhelper'), flutter_root)

flutter_ios_podfile_setup

pod 'GoogleMobileAdsMediationFacebook'

target 'Runner' do
  use_frameworks!
  use_modular_headers!

  flutter_install_all_ios_pods File.dirname(File.realpath(__FILE__))
end

post_install do |installer|
  installer.pods_project.targets.each do |target|
    flutter_additional_ios_build_settings(target)
    target.build_configurations.each do |config|
          config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '12.0'
          config.build_settings["EXCLUDED_ARCHS[sdk=iphonesimulator*]"] = "arm64"
    end
  end
end

@mrcsilva
It could be happening due to a conflict between pod 'GoogleMobileAdsMediationFacebook' and other pods. Try this solution and see if it works for you.

@darshankawar
It was indeed a conflict with the GoogleMobileAdsMediationFacebook pod.
After executing cd ios && pod cache clean --all && pod deintegrate && pod install from your suggestion and commenting the GoogleMobileAdsMediationFacebook pod it successfully built and ran the app!
Thanks for the help!
However I will need that pod, do you have any advice on what could I do to build the app with it?
I don't understand that much about Podfiles, but maybe moving the pod declaration to another place could work?

After executing cd ios && pod cache clean --all && pod deintegrate && pod install from your suggestion and commenting the GoogleMobileAdsMediationFacebook pod it successfully built and ran the app!

Provided your last message I feel it's safe to close the issue.

However I will need that pod, do you have any advice on what could I do to build the app with it?
I don't understand that much about Podfiles, but maybe moving the pod declaration to another place could work?

I am not really sure about this, You may try asking on StackOverflow and see if you can get some help.


Module 4 currently on Team-3 branch

will move it to Team=4 branch once finalised

sounds good. I think it is cause you and Sonja developed it together in line with the module 3 stuff. no problem :)

yeah because initially then the plan was module3 Sonja code me test and module 4 vice-versa. Now I think we all have an open relationship we are no longer sticking to original pairing

The latest module4 already push to Team-4 branch. Will close issue now.

Thanks


"Morărești" is listed in the drop-down menu

Description:
"Morărești" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Morărești" in the search bar.

Expected results
The location is listed in the drop-down menu as "Morărești, Alba (Ciuruleasa)".


Support JP version RR PSP

Add 2 PSP Ridge Racer.
-ULJS00080
-ULJS00001
This commit changes needs "g" options on rrpsp.

Appreciated 👍


Adding the automated build scripts

this is on 'build' branch.
Merge it with master

Refer to 2018ab7b1a7030e02a1fa52e085b277d7499387b

Merged with master in c22297ffcde00ce583b07c54a5f6a56e0eda1ba9


LLaVA how to replace qwen LLM model？

Hello, may I know how to replace the qwen model in the LLM module of llava? I have tried to replace it, but I encountered many error issues. For example, the bos_token_id is not defined. Could you provide a tutorial or guidance on how to replace the qwen model?

qwen model is so different from other LLMs, since its tokenizer does not have bos_token_id. However, transformers requires bos_token_id when using inputs_embeds as inputs (LLaVA needs this feature).
A quick solution is to configure the tokenizer as follows
# For chat model
tokenizer = dict(
    type=AutoTokenizer.from_pretrained,
    pretrained_model_name_or_path=llm_name_or_path,
    trust_remote_code=True,
    padding_side='right',
    bos_token='<|im_start|>',
    eos_token='<|im_end|>')

This is just a temporary solution, the correct solution is to support bos_token from the upstream qwen model.
Meanwhile, please do not forget to modify EvaluateChatHook's stop_word as
https://github.com/InternLM/xtuner/blob/5962cc87d2893870f5ccdd112a3adfe3883fb14d/xtuner/configs/qwen/qwen_7b_chat/qwen_7b_chat_qlora_alpaca_e3.py#L152

qwen model is so different from other LLMs, since its tokenizer does not have bos_token_id. However, transformers requires bos_token_id when using inputs_embeds as inputs (LLaVA needs this feature).
A quick solution is to configure the tokenizer as follows
# For chat model
tokenizer = dict(
    type=AutoTokenizer.from_pretrained,
    pretrained_model_name_or_path=llm_name_or_path,
    trust_remote_code=True,
    padding_side='right',
    bos_token='<|im_start|>',
    eos_token='<|im_end|>')

This is just a temporary solution, the correct solution is to support bos_token from the upstream qwen model.
Meanwhile, please do not forget to modify EvaluateChatHook's stop_word as
https://github.com/InternLM/xtuner/blob/5962cc87d2893870f5ccdd112a3adfe3883fb14d/xtuner/configs/qwen/qwen_7b_chat/qwen_7b_chat_qlora_alpaca_e3.py#L152

Yes, I tried the same thing yesterday and it's working fine so far.

请问经过Qwen-7B-Chat微调的LLaVA，如何使用xtuner chat进行对话？
顺利微调，但是chat的时候出现如下报错：

@thomas-yanxin
transformers的模型在使用generate()，并传入inputs_embeds，而非input_ids时，必须确保传入 bos_token_id。而 qwen 模型 bos_token_id 为 None，进而会报这个错。
因此问题出在 qwen 模型的实现上，其不支持 inputs_embeds-only 的 generate 输入。

I have trained on qwen and got.iter_xtuner, how do I convert it to offical_llava format


Issue with POST body formatting example.

Hi,
I noticed a small documentation issue when working with the API. The example in the documentation states the POST body should be formatted like so:
{
"sourcesystem": "test",
"value":[
{
However, the API does not accept this and returns an error. The solution is to replace "value" with "indicators":
{
"sourcesystem": "test",
"indicators":[
{
This issue is documented in the following forum post by another user:
https://techcommunity.microsoft.com/t5/microsoft-sentinel/issues-with-threat-intelligence-upload-indicators-api-preview/m-p/3859037

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

ID: 22a27692-7760-d91c-1a2e-cb529e2c4cac
Version Independent ID: 7692c9a5-5c8f-baba-9aff-474e8bd8d166
Content: Import threat intelligence with the upload indicators API - Microsoft Sentinel
Content Source: articles/sentinel/upload-indicators-api.md
Service: microsoft-sentinel
GitHub Login: @austinmccollum
Microsoft Alias: austinmc

@J0shmcl
Thanks for your feedback! We will investigate and update as appropriate.

@J0shmcl
Thank you for bringing this to our attention! We've initiated a pull request (PR) to address this issue. Once the author reviews the changes, they will be merged, and the updates should go live shortly. Your diligence is much appreciated!

#assign:austinmccollum


Make it compatible with DeArrow

DeArrow is an extension that replaces titles with crowdsourced versions. There is a problem with yt-anti-translate writing to DeArrow's custom title element instead of the original element.
It is much easier to fix on yt-anti-translate's side to make sure it writes to the original text element.
Fixes https://github.com/ajayyy/DeArrow/issues/88

Published as 1.5.11


Unable to activate bitfinex-rb-0.0.11, because faraday-0.11.0 conflicts with faraday

Hi
I am doing
~/.software/bitfinex-api-rb/lib> ruby bitfinex-api-rb.rb

and I get
/home/zeno/.rbenv/versions/2.4.0/lib/ruby/2.4.0/rubygems/specification.rb:2288:in `raise_if_conflicts': Unable to activate bitfinex-rb-0.0.11, because faraday-0.11.0 conflicts with faraday (>= 0.9.2, ~> 0.9.2), json-2.0.2 conflicts with json (>= 1.8.3, ~> 1.8.3) (Gem::ConflictError)
        from /home/zeno/.rbenv/versions/2.4.0/lib/ruby/2.4.0/rubygems/specification.rb:1408:in `activate'
        from /home/zeno/.rbenv/versions/2.4.0/lib/ruby/2.4.0/rubygems.rb:220:in `rescue in try_activate'
        from /home/zeno/.rbenv/versions/2.4.0/lib/ruby/2.4.0/rubygems.rb:213:in `try_activate'
        from /home/zeno/.rbenv/versions/2.4.0/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:126:in `rescue in require'
        from /home/zeno/.rbenv/versions/2.4.0/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:40:in `require'
        from /home/zeno/.software/bitfinex-api-rb/lib/bitfinex.rb:7:in `<top (required)>'
        from bitfinex-api-rb.rb:1:in `require_relative'
        from bitfinex-api-rb.rb:1:in `<main>'

Have you tried with bundle exec ? it should solve the conflicts for you.
You should import the gem in your own script, there's an example you can run:
bundle exec ruby example/ticker.rb

Thanks. Doing that now.


Currently <ActionList.Item> registers a handler for the onKeyPress event. keypress events are fired when a key -or- key combination produces a character value. This works fine in most cases, but on Windows for example, Alt+Enter does not produce a character value and an event is not emitted.
Additionally, keypress is now considered an obsolete event and is no longer recommended for use.
Separately, on Mac, the key combination Option+Space results in a non-break space character value, which is different than typical Space resulting in the conditional check for ' ' on line 231 to fail.
Steps to reproduce

Create a new GitHub Project
Ensure there is a table view on the project
Click the view's option button and then choose sort by

Mac:
Use the keyboard to select a secondary sort by using Option+Space and notice selection does not get made.
Windows
Use the keyboard to select a secondary sort by using Alt+Enter and notice selection does not get made.
Version
v36.6.0
Browser
Chrome

Hi there @tmelliottjr! Thanks for taking the time to make the issue 🙏
When going through this during issue triage, we could totally confirm the issue and we added it to our backlog. There isn't an ETA on when this will be picked up so feel free to submit a fix for this or reach out if this is something you'd want to pair on.
Hope this makes sense, let me know if you have any questions!

I've taken a crack at this here: https://github.com/primer/react/pull/4212


HubSpot Backport HBASE-26308

I cherry picked these changes from branch-2, but I can manually apply them if that would be better as well.
HBASE-26308  - ensures the sum of the multipliers is always properly calculated and gives us more details in the balancer log output.

nice! lgtm. I'm not sure what you mean by your first setnence. If you mean git cherry-pick vs manually going line-by-line and making the same changes, I'm definitely ok with cherry-pick.

I'm not sure what you mean by your first setnence.

yeah sorry that wasnt clear you understood correctly.
Good to merge this? Or do we get a couple reviews internally too? Also when I squash and merge do you usually keep HubSpot Backport in the commit message ?


Remove indels_flagged, num_inserts_in_consensus, and num_deletions_in_consensus columns from summary files

From: "Laurent, Louise"
Date: Thursday, March 18, 2021 at 11:21 AM
Subject: Re: Indel flag and Pangolin calls
Hi All,
A few adjustments to the below, based on Kristian's input on this morning's 10 am call -- pending Katie/Amanda checking with Karthik and Al that these fit what Bjorn does:

indels_flagged, num_inserts_in_consensus, and num_deletions_in_consensus columns will be removed from the summary csv files created by the CCBB pipeline

[snip]

These will be left in for now because removing them involves changing the tests etc. Revisit an overhaul of the index system later; there are multiple views about how to do this.


external_deps: minor touchup (almost bikeshedding)

rely more on variables

Pure bikeshedding, just makes the wording more consistent.

linux-i686 cost is null

Now that the toolchain is fully cross-compilation compliant, building the engine for i686 is just a matter of setting CC to i686-linux-gnu-gcc. So the cost of it is null.
There is no change to be done on engine code neither on engine cmake to build a linux i686 engine as we already take care of engine i686 compatibility for Windows.
While the oldest supported amd64 CPU is 21 years old and the oldest supported GPU is 20 years old, Intel introduced new 32-bit-only processors until 2011 included, so the more recent 32-bit only Intel CPU is 11 years old. Also Intel sold amd64 compatible CPUs as 32-bit CPUs hiding the fact they were 64-bit compatible. I myself hosted linux network services for companies I worked for on such hardware, given I was aware of it I ran amd64 distros on them, but other people may run i686 distros on them because the hardware is officially advertised as i686 only. Those would be perfect to run unvanquished servers.
The same way people asked for arm support to host servers, there is no reason a low-end intel CPU can't host a server. On Via side, Via C7 seems to provide all features to run a server. Those kind of Atom/Via CPUs are very common in devices like light clients, nettop, NAS, and things like that, which are perfect as low-consumption servers and cost nothing on second hand market.
Even running the more recent amd64-compatible Atom/Via CPUs as 32-bit may be a wise choice for hosting a server, with hardware just costing 20$ to host a home server.
I myself hosted my Unvanquished server on a low-end Via CPU for years. I assume the only reason why we didn't get any request for this is that our user base is small. The same way our user base is known to not have reached yet less developed countries, or we don't know about it.
We know from SourceForge we have lots of downloads from South-American countries without never seeing the players, except once when some Brazilian people came to troubleshoot problems when hosting LAN servers (so we know we have users we never see online).
We also received reports last year from a French non-profit organization refurbishing old computers to play LAN games with children, including reports for Via GPUs from 2005 and Intel GPUs from 2007, which gives a glance on the kind of hardware they refurbish for playing LAN games.
Given the cost of linux-i686 is null, I see no reason to prevent the building of it.

more wasmtime and wasisdk care

I added more switch/case stuff to correctly report errors on newly supported platforms like arm64. I updated versions so the knowledge baked in the script matches an actual release.
I noticed Wasmtime doesn't provide 32-bit i686 build at all so that would be very problematic when moving to Wasm as this would phase out windows-i686 build, which is believed to still be used a lot (average people don't reinstall their preinstalled Windows). That would also phase out 32-bit arm support which is still the default and recommended download for Raspberry Pi, the first cause of request for arm and rapsberry pi support being servers.
I noticed the Wasi SDK only provides amd64 build, which is similar to the NaCl SDK that only provided amd64 and i686 build if I'm right (no arm NaCl SDK for sure).

For completeness, the dæmon engine can run on x86 processors implementing the NX bit, on AMD side it starts with AMD64, on Intel side it starts with the E0 stepping of Prescott Pentium 4 processor (source).

(I've modified the title to add that it also builds for a new architecture)

Personally I don't like "rely more on variables"

I removed the EXE thing which was just a matter of taste. The other variable change was needed by the following commit so I squashed the other variable change with the following commit.

For the record, I don't think adding support for a new architecture has zero cost: there is the testing and support cost.

@necessarily-equal That's why I don't call this support (I renamed the title to say “do not prevent” instead). It's just I don't think it makes sense to artificially prevent to build something that works. There is no support meant to be provided at all.
That said, one hidden interest of i686 may be emulation. For example the very first person who talked with me about his desire to try to run the Unvanquished client (not the server) on an arm device was asking me if we had a 32-bit build of Unvanquished. The reason was he believed he would get more performance emulating i686 with box32 than emulating amd64 with box64. This need is now completely obsolete as the engine now builds and runs both as arm and arm64, but for legacy reason, there are strong motivations to emulate i686 (same for amd64, but this one has less history). None of this is an argument in favor of supporting such platform, but this contributed to me wondering if that platform was still working or not, it looks like there is nothing incompatible in the code.
For example in the past we had a specific cmake toolchain file for this platform. This was very different to the current status, as there is now nothing specific in our cmake files written for the linux-i686 platform, we don't have to deal with the linux-i686 platform when editing cmake files or the C++ code.

I'm impressed by the growth of arm64:

Also arm64 just outperformed armhf this year, which confirms how much armhf is strong.
Given submission is not enabled by default in Debian as far as I know, those numbers for i686 as the second-most popular Debian platform isn't bad! I would love to get those users on Unvanquished!

Note those Debian numbers include multiarch packages installations. I suspect multiarch installations actually represents the majority of i386 usage, and we don't need to support these IMO because they can also just run the 64bits binary.


IE11 pattern for email error

that's bouncer.js then
On Wed, Nov 21, 2018 at 1:32 AM Tom Awgul<EMAIL_ADDRESS>wrote:

Hey,
When having an email type filed I get this error:
SCRIPT5017: Syntax error in regular expression bouncer.js (199,3)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/WebReflection/url-search-params/issues/43, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAFO9Y2wwW5thQQhuWSninPw9baEO_Hlks5uxJ8MgaJpZM4YsLWx
.

closing since this bug has no content whatsoever.

Yes, I had open 2 pages at once and made a mistake ;)


Multiple entrypoints will generate duplicate module preloads

If the Vite config has multiple entrypoints, the vite_entry_link_tags may generate multiple module preloads for JS files depending on the imports from all the entrypoints.

merged !


Core dat

I'm not sure what you're trying to accomplish here, but this doesn't seem like a valid pull request. For private experiments, please use your own repository.


Updated to SF6.4

Updated to SF6.4. Seems that works fine only changing composer.json.

Thank you!

Just published version 4.1.0


Doubt about Lock

Hello everyone, everything good?
Do you have any predictions for the date of the new version that will have this Lock class?
I'm implementing Lock that is in version 1.3.1, but I couldn't understand how it works, does it lock the entire Redis? Because at no time do I tell you which key to lock.
Thanks

We'll push out version 2.0.0 soon as in hopefully within next week. Closing as this is about 1.3.1 that we won't support.


https://pancakeswap.finance access problem

https://pancakeswap.finance
I can't access https://pancakeswap.finance nor https://pancakeswap.finance/liquidity . Pls help & advise.
Thank You

Same

Done! https://github.com/polkadot-js/phishing/pull/4122


add eth_multicallV1

eth_multicallV1
This PR is a cleaned up version from #383. The #383 is based heavily on #312 from @s1na (eth_batchCall). This spec encompasses some of the ideas presented by @MicahZoltu @OlegJakushkin, @LukaszRozmej, @killariDev, @epheph and others.
Summary
This introduces a new RPC method eth_multicallV1 allows users to make complex RPC calls to Ethereum nodes. Compared to eth_call, eth_multicallV1 has following extra features:

You can encapsulate multiple dependent calls in a single call
The calls happen inside blocks. You can simulate multiple blocks that can be arbitrary far from each other
Block variables can be overridden (e.g. time)
Account state can be overridden for every block (e.g. code and balance)
It is possible to override precompiles (e.g. ecrecover) with arbitrary EVM code
ETH transfers produce logs similar to ERC20 logs
Validation mode. You can choose to do very strict simulation or more relaxed one similar to eth_call

Motivation
The features of eth_multicallV1 allow many interesting simulation use cases such as:

To simulate simple erc20 approval & swap feature in a wallet, we need to be able to send multiple transactions
Searchers need to trigger oracle update and wait a number of blocks
Researchers need to trigger a price change and wait a number of blocks for a TWAP adjustment
Wallets are beginning to provide advanced simulation to the user
Block builders are beginning to explore multi-block MEV
Fake Permit2 or other EIP-712 approvals

Implementation
Geth: https://github.com/s1na/go-ethereum/tree/multicall
Nethermind: https://github.com/NethermindEth/nethermind/tree/feature/eth_multicall

A bit of a nit, but curious why the method is named eth_multicallV1 instead of just eth_multicall? Also seems a bit inconsistent as versioning in eth_signTypedData has an underscore prefix (_v4).
If we were to break this API, can we not just append a version to the parameters, which can be used to distinguish in the implementation?
{
  method: 'eth_multicall',
  params: [
    // ...,
+   "v2"
  ]
}

You are correct, this allows you to run multiple calls against one or more blocks in sequence (all building up the same state).  Maybe eth_simulateTransactions or eth_simulateBlocks would be better?

I'm mostly indifferent to the name, but eth_batchCall or eth_simulateCalls are other alternatives that don't overload the multicall usage.
On this topic, why is the method proposed as eth_multicallV1 instead of eth_multicall? Most RPC methods do not have versioning in their name so this seems to deviate from convention. eth_signTypedData_v4 is the only one I know of with versioning

On this topic, why is the method proposed as eth_multicallV1 instead of eth_multicall? Most RPC methods do not have versioning in their name so this seems to deviate from convention. eth_signTypedData_v4 is the only one I know of with versioning

The lack of versioning in existing JSON-RPC methods has been a thorn in the side of people wanting to make changes to them since essentially the beginning of Ethereum.  Rather than continue to cause our future selves suffering to maintain a naming convention, we felt it would be wise to break the cycle and introduce versioning.
As for the naming convention, it follows the Engine API's naming convention (the communication channel between execution and consensus clients).

but eth_batchCall or eth_simulateCalls

these are great alternative suggestions, would lean towards eth_simulateCalls, because batchCalls could be mistaken as batched eth_call
Using versioning for this sgtm!

but eth_batchCall or eth_simulateCalls

these are great alternative suggestions, would lean towards eth_simulateCalls, because batchCalls could be mistaken as batched eth_call
Using versioning for this sgtm!

I think eth_simulateTransactionsV1 would the best. As you can simulate more than just calls, you can simulate transactions

Hi! I was curious what the current status is here? We're excited to leverage this in the next iteration of the client library for ERC-7412 to simulate multicalls.

@noahlitvin It is implemented in Nethermind, Geth, and Reth.  It should be available in the latest released version of Nethermind and Geth, I'm not sure if it is released in Reth or not yet.


Update README.rst to use correct documentation links

The README used the lowercase format of the documentation URL. It seems like the URLs are now case-sensitive, so this update should fix this.

good catch, thanks!


sap_ha_install_pacemaker: add SBD as fencing method

This PR adds:

make stonith-timeout configurable (900 default)
clarify task names
rename check_properties to check_status
add fencing via SBD

The README is extended to reflect the new feature ans also now gives more context on how to configure the different fencing methods.

@ja9fuchs I understand that you might want to close this for the same reason as #237... and implement this via https://github.com/linux-system-roles/ha_cluster.
ha_cluster has SBD implemented in it but is e.g. missing the code to actually load a watchdog kernel module. Also sap_ha_pacemaker_cluster would need adapted meta/argument_specs.yml to be able to deploy the SBD use case.
Is this something that you're already working on or shall I give it a try?

@yeoldegrove You are correct, SBD can as well be implemented using the ha_cluster native parameters. I had not yet closed this PR because I was taking some time to save some of your good input for the stonith resource config on various platforms.
I also want to highlight that your contribution is very much appreciated!
The deprecation of the original HA roles is not related to your input and is just a case of unfortunate timing and, on our side, a lack of visible clarification at an earlier stage. :)
Regarding the change of meta/argument_specs.yml, are you referring to the ha_cluster dictionary that is listed here? For that variable you are right, and I have planned to adjust the entry for this argument such that any option the ha_cluster role supports can be defined accordingly without causing any argument check issue, plus providing an enhanced example.
Regarding the gap of loading a watchdog kernel module I suggest you try and contribute your code directly to https://github.com/linux-system-roles/ha_cluster.
If you could test a cluster setup with the new sap_ha_pacemaker_cluster role, including the functionality you were missing in the deprecated roles, this would be much appreciated.
Of course, please feel free to add improvements to this role as well, or open GitHub issues to track anything we could follow up on at a later stage. :)