List empty of devices simulator with Xcode 10.2

See related #234

Since the update to iOS 12.2 / Xcode 10.2 (after Apple keynote on Monday 25th of March) cordova is not able to find and deploy to a "defined" simulator:

**BUILD SUCCEEDED **
No target specified for emulator. Deploying to undefined simulator
app:cordova-conf Updated Cordova config.xml +2ms

...and nothing happens...
Deploying onto a connected physical iOS device is possible without any problems... strange
I checked this:

ios-sim showdevicetypes shows up all devices as expected
xcrun simctl list shows up all devices as expected
but: cordova run --list shows only empty lists!

Specs:

Xcode 10.2 Build version 10E125
ios-sim/9.0.0-dev.1
node-v10.15.0
darwin-x64
Mac OS X 10.14.3 18D109
Cordova 9.0.0
Quasar Framework 1.0.0-beta.13

Same Problem for me. Here is my ionic info
Ionic:
ionic (Ionic CLI)  : 4.12.0 (/usr/local/lib/node_modules/ionic)
Ionic Framework    : ionic-angular 3.9.4
@ionic/app-scripts : 3.2.3
Cordova:
cordova (Cordova CLI) : 8.0.0
Cordova Platforms     : android 6.4.0, ios 4.5.5
Cordova Plugins       : cordova-plugin-ionic 5.2.1, cordova-plugin-ionic-webview 3.1.0, (and 16 other plugins)
System:
ios-deploy : 2.0.0
NodeJS     : v10.9.0 (/usr/local/bin/node)
npm        : 6.9.0
OS         : macOS Mojave
Xcode      : Xcode 10.2 Build version 10E125

Same problem here, my env is juts yours.

Same issue after updating to Xcode 10.2

@ewwwgiddings Did you tried to update ios-sim by the npm install -g ios-sim@next - to resolve the issue of the empty ios-sim device list.
from https://github.com/ios-control/ios-sim/issues/234#issuecomment-475947845

Has anyone been able to find a work-around until this gets fixed?

@crabbydavis
Run it from Xcode - this is work fine for now.

I'm working on a couple apps right now and one of them works when I run it from Xcode but the other one isn't pulling in any data. The service is throwing 200s as errors. Maybe it's just an issue with my api.
Thanks @valeriy-kovalev

@valeriy-kovalev @crabbydavis I don't think XCode allows for livereload when you run it from there. Maybe I'm wrong but that's my understanding.
Best workaround for me has been to use a device instead of an emulator. Plug device in and use 'run' instead of 'emulate' and this allows livereload if needed.

@bbb81  cordova needs to update to the latest ios-sim. Which is unreleased as of yet until this Xcode 10.2 issue is resolved
@ewwwgiddings can you show your ios-sim version ios-sim --version since you didn't get any listing from showdevicetypes
Workaround, try in the root of your cordova app after each time the ios platform is added:
cd platforms/ios
npm install ios-sim@next

Sorry the workaround will not work, because of: https://github.com/apache/cordova-ios/issues/567

@shazron I'm a bit confused. I thought I've seen you mention to install ios-sim@next in multiple threads on here, but the issue you just linked to you said don't upgrade to ios-sim 9 which is @next
I'll check the --version of ios-sim tomorrow but until then my package.json is at "ios-sim": "^9.0.0-dev.1"
What are you suggesting I do? Sorry I'm confused right now...

I only released ios-sim@next for those that wanted the latest code now. There hasn't been a formal release because it is not ready yet as I already explained in previous comments.

@shazron, so it's done, we can use the<EMAIL_ADDRESS>with cordova CLI 9.0.0 (that will brings the ios-cordova@5.0.0), and xCode 10.2, right?

I tried to open it with a empty new project and I'm having this error message iossim.getdevicetypes is not a function
This my ionic  info output
Ionic:

   ionic (Ionic CLI)  : 4.3.1 (/usr/local/lib/node_modules/ionic)
   Ionic Framework    : ionic-angular 3.9.3
   @ionic/app-scripts : 3.2.1

Cordova:

   cordova (Cordova CLI) : 9.0.0
   Cordova Platforms     : ios 5.0.0
   Cordova Plugins       : cordova-plugin-ionic-keyboard 2.1.3, cordova-plugin-ionic-webview 3.1.2, (and 4 other plugins)

System:

   ios-deploy : 1.9.4
   ios-sim    : ios-sim/9.0.0-dev.1 darwin-x64 node-v11.1.0
   NodeJS     : v11.1.0 (/usr/local/Cellar/node/11.1.0/bin/node)
   npm        : 6.9.0
   OS         : macOS
   Xcode      : Xcode 10.2 Build version 10E125

@mf222 use showdevicetypes not getdevicetypes

@ewwwgiddings thanks, but I think I didn't explain myself well, I wasn't trying to run ios-sim showdevicetypes.   When I make ionic emulate ios with the specs I mentioned, the script fails with the following error: iossim.getdevicetypes is not a function.

@jeansantana yes
@mf222 see my comment previously where I referenced a cordova-ios issue, this is the issue you are getting.

@shazron you're confusing me. You told me not to use 9.0 because the only way to get 9.0 is by using ios-sim@next, but now you have just said to @jeansantana to use 9.0 and it is done? Am I missing something?

@ewwwgiddings I think what jeansantana is saying is "when it's done" at least that's how I read it

@shazron Thanks for your effort to fix this! :)
Your quick fix along with ios-sim 8.0.0 and available_runtimes[ runtime.identifier] = (runtime.availability === '(available)'); seems to resolve issues with console auto starting (emulating) iOS devices.
However I am now experiencing issue that Safari Web inspector does not get debuggable code. Safari recognizes application and ionic web server instance as runnable, however when you click on it you get empty web inspector.
Am I missing something? Thanks for help!

Ok I've published a new ios-sim@next version that is cordova compatible, however cordova run ios --emulator has an error, but you can do cordova run --list
For the workaround, try in the root of your cordova app after each time the ios platform is added:
cd platforms/ios
npm install ios-sim@next

If people can test with that, that will be good.

@Adza93 no idea yet, will get to it after
Others: needless to say this release is not complete yet, I have yet to still debug start, install, launch

@shazron I have managed to understand what is going on with iOS 12.2 and Web debugger in Safari (generally debugging).
It looks like latest Safari 12.0.3 (14606.4.5) is not in sync with iOS 12.2 Web components needed to establish debugger connection to web server.
When I try to debug simulators or real devices with iOS version lower than 12.2 (Tried on iOS 11 and 12.0.X) debugging works.
Current solution for iOS 12.2 is to use Safari Technology Preview, where Web debugging works as it should. Other solution is not to use iOS 12.2 Simulators and stick with Safari.

@shazron I did installed that latest ios-sim@next but I'm not getting any available virtual ios devices when I run cordova run --list. Here's my ionic info
`Ionic:
ionic (Ionic CLI)  : 4.1.1
Ionic Framework    : ionic-angular 3.9.2
@ionic/app-scripts : 3.2.0
Cordova:
cordova (Cordova CLI) : 8.1.2<EMAIL_ADDRESS>Cordova Platforms     : android 8.0.0, ios 5.0.0
Cordova Plugins       : cordova-plugin-ionic-webview 3.1.2, (and 37 other plugins)
System:
ios-deploy : 1.9.4
ios-sim    : ios-sim/9.0.0-dev.2 darwin-x64 node-v10.9.0
NodeJS     : v10.9.0 (/Users/crabbydavis/.nvm/versions/node/v10.9.0/bin/node)
npm        : 6.4.1
OS         : macOS
Xcode      : Xcode 10.2 Build version 10E125`

Hi,
With the workaround install, I was able to get the list of devices by invoking:
`cordova run --list
Available ios devices:
Available ios virtual devices:
ios-sim.getdevicetypes is deprecated, use ShowDeviceTypesCommand instead.

** BUILD SUCCEEDED **
Command finished with error code 0: xcodebuild -workspace,Quizionic4.xcworkspace,-scheme,Quizionic4,-configuration,Debug,-sdk,iphonesimulator,-destination,platform=iOS Simulator,name=iPhone X,build,CONFIGURATION_BUILD_DIR=/Users/flavio/Quizionic4/platforms/ios/build/emulator,SHARED_PRECOMPS_DIR=/Users/flavio/Quizionic4/platforms/ios/build/sharedpch,-UseModernBuildSystem=0
No scripts found for hook "before_deploy".
Error: spawn /Users/flavio/Quizionic4/node_modules/ios-sim/src/bin/ios-sim ENOENT
[ERROR] An error occurred while running subprocess cordova.
    cordova run ios --verbose --target iPhone-X exited with exit code 1.

    Re-running this command with the --verbose flag may provide more information.

ionic:utils-process onBeforeExit handler: process.exit received +0ms
ionic:utils-process onBeforeExit handler: running 2 functions +0ms
ionic:utils-process onBeforeExit handler: exiting (exit code 1) +25ms`
Any idea?

@fpassa can you post your ionic info?

Tried with the npm install ios-sim@next and got the following error:
No target specified for emulator. Deploying to iPhone-XR, 12.2 simulator
Error: spawn /Users/alex/Take5/etraining-vue/src-cordova/node_modules/ios-sim/src/bin/ios-sim ENOENT

Going to the folder i checked that the src doesn't have any bin folder inside. The above folder has a bin in it. I tried to copy it to the src folder and the error was gone, but the emulator never starts.

run from xCode, It takes a few days to fix this :/ (the prev xcode version same problem)

Running on real device is fine, but not on emulator.

@fpassa @alexpvieira yes, i mentioned that starting the emulator will not work in my comment https://github.com/ios-control/ios-sim/issues/253#issuecomment-477923851
I'm writing tests as I go along, so that's why it's taking longer. The previous versions did not have tests.

I don't know if this helps but thee RN community ran into the same issue. I don't know how ios-sim handles this but thought I would share some of their discussion on the issue. https://github.com/react-native-community/react-native-cli/pull/138

... debugging with command line "iOS-sim start -d="iPhone-X" with ios-sim@next
helpers.js line 248:
ret_obj.runtime has value => "iOS 12.2"
list.devices has values starting with com.apple.CoreSimulator...
so it will not match any of those values...

... passing the runtime explicitly in this form seems to do the trick:
ios-sim start -d=iPhone-X,com.apple.CoreSimulator.SimRuntime.iOS-12-2

thanks! - yes there are several places in the code where we need to do fixDeviceGroup, I have been fixing them as I find them

For the people looking for a quick fix :

This works like a charm.

For the people looking for a quick fix to emulate with livereload :
https://forum.ionicframework.com/t/ios-sim-does-not-recognize-devices-after-xcode-10-2-update/160276/2?u=rboutaleb
Works perfect !

This works for me.
cordova emulate ios --debug --target "iPhone-X,com.apple.CoreSimulator.SimRuntime.iOS-12-2" --buildFlag='-UseModernBuildSystem=0'

This works for me. Change the target and debug/release build type to suit your needs.
cordova emulate ios --debug --target "iPhone-X,com.apple.CoreSimulator.SimRuntime.iOS-12-2" --buildFlag='-UseModernBuildSystem=0'

This works for me. Change the target and debug/release build type to suit your needs.
cordova emulate ios --debug --target "iPhone-X,com.apple.CoreSimulator.SimRuntime.iOS-12-2" --buildFlag='-UseModernBuildSystem=0'

Ok I've published a new ios-sim@next version (dev.4) that is fully cordova compatible.
I tried:
$ cordova run --list
$ cordova run ios --emulator --target "iPhone-X, 12.2"

For the workaround, try in the root of your cordova app after each time the ios platform is added:
cd platforms/ios
npm install ios-sim@next

If people can test with that, that will be good. I've tested all the commands with ios-sim stand-alone, seems ok. I still need to complete 100% coverage of the tests.

@shazron it is not working for me. I have updated ios-sim to latest @next.
I get the error message
Device id for device name "iPhone 7" and runtime "iOS 12.2" could not be found, or is not available.
[ERROR] An error occurred while running cordova run ios --target "iPhone-7, 12.2" (exit code 1).
when I run ionic cordova run --list i get empty list
Available ios devices:
But when I try ios-sim showdevicetypes i get regular list
Apple-TV-1080p, tvOS 12.2
Apple-TV-4K-4K, tvOS 12.2
Apple-TV-4K-1080p, tvOS 12.2
iPhone-5s, 11.4

My ionic info
`
@ionic/cli-utils  : 1.19.3
ionic (Ionic CLI) : 3.20.1
global packages:
cordova (Cordova CLI) : 8.1.2<EMAIL_ADDRESS>

local packages:
@ionic/app-scripts : 3.2.0
Cordova Platforms  : android 6.4.0 ios 4.3.1
Ionic Framework    : ionic-angular 3.9.2

System:
Android SDK Tools : 26.1.1
ios-deploy        : 1.9.4
ios-sim           : ios-sim/9.0.0-dev.4 darwin-x64 node-v10.13.0
Node              : v10.13.0
npm               : 6.4.1
OS                : macOS
Xcode             : Xcode 10.2 Build version 10E125

Environment Variables:
`

Based on previous answered, I succeed in launching my app on an iPad with this command
cordova run ios --target="iPad-Air-2,com.apple.CoreSimulator.SimRuntime.iOS-12-2" --buildFlag="-UseModernBuildSystem=0"

with my Ionic 3 project:
 ionic cordova run ios -l -c -s --target="iPhone-X,com.apple.CoreSimulator.SimRuntime.iOS-12-2"  -- --buildFlag="-UseModernBuildSystem=0"
works fine... I'm using ios-sim 8 though

Going down from ios-sim 9.0.0-dev.4 to 8 was the trick to get live reload working for me again. Thanks @leonardomontes !!

... although live-reload seems to work, I'm experiencing issues with live-reload:

Developer Tools Inspector doesn't show any code / html / css...
Livereload doesn't seem to pickup changes after reloading

... anyone else experiencing this?
Going to try and downgrade XCode...

@Adza93 Hmm, I get the right info. Did you install ios-sim according to my instructions, how did you install it? what does xcrun simctl list show?

If it was installed properly for Cordova, the first three lines should be this (assuming you don't have a device connected):
Available ios devices:
Available ios virtual devices:
ios-sim.getdevicetypes is deprecated, use ShowDeviceTypesCommand instead.

@shazron
I did upgrade of ios-sim@next at the root location of the project. After your comment I also did following steps
cd platforms/ios
npm install ios-sim@next
But it did not help.
output for xcrun simctl list --json

aleksandar$ xcrun simctl list --json
{
"devicetypes" : [
{
"name" : "iPhone 4s",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPhone 4s.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-4s"
},
{
"name" : "iPhone 5",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPhone 5.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-5"
},
{
"name" : "iPhone 5s",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPhone 5s.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-5s"
},
{
"name" : "iPhone 6",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPhone 6.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-6"
},
{
"name" : "iPhone 6 Plus",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPhone 6 Plus.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-6-Plus"
},
{
"name" : "iPhone 6s",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPhone 6s.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-6s"
},
{
"name" : "iPhone 6s Plus",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPhone 6s Plus.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-6s-Plus"
},
{
"name" : "iPhone 7",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPhone 7.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-7"
},
{
"name" : "iPhone 7 Plus",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPhone 7 Plus.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-7-Plus"
},
{
"name" : "iPhone 8",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPhone 8.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-8"
},
{
"name" : "iPhone 8 Plus",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPhone 8 Plus.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-8-Plus"
},
{
"name" : "iPhone SE",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPhone SE.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-SE"
},
{
"name" : "iPhone X",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPhone X.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-X"
},
{
"name" : "iPhone Xs",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPhone Xs.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-XS"
},
{
"name" : "iPhone Xs Max",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPhone Xs Max.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-XS-Max"
},
{
"name" : "iPhone Xʀ",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPhone Xʀ.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-XR"
},
{
"name" : "iPad mini (5th generation)",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPad mini (5th generation).simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-mini--5th-generation-"
},
{
"name" : "iPad Air (3rd generation)",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPad Air (3rd generation).simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Air--3rd-generation-"
},
{
"name" : "iPad 2",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPad 2.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-2"
},
{
"name" : "iPad Retina",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPad Retina.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Retina"
},
{
"name" : "iPad Air",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPad Air.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Air"
},
{
"name" : "iPad mini 2",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPad mini 2.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-mini-2"
},
{
"name" : "iPad mini 3",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPad mini 3.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-mini-3"
},
{
"name" : "iPad mini 4",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPad mini 4.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-mini-4"
},
{
"name" : "iPad Air 2",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPad Air 2.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Air-2"
},
{
"name" : "iPad (5th generation)",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPad (5th generation).simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPad--5th-generation-"
},
{
"name" : "iPad Pro (9.7-inch)",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPad Pro (9.7-inch).simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro--9-7-inch-"
},
{
"name" : "iPad Pro (12.9-inch)",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPad Pro (12.9-inch).simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro"
},
{
"name" : "iPad Pro (12.9-inch) (2nd generation)",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPad Pro (12.9-inch) (2nd generation).simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro--12-9-inch---2nd-generation-"
},
{
"name" : "iPad Pro (10.5-inch)",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPad Pro (10.5-inch).simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro--10-5-inch-"
},
{
"name" : "iPad (6th generation)",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPad (6th generation).simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPad--6th-generation-"
},
{
"name" : "iPad Pro (11-inch)",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPad Pro (11-inch).simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro--11-inch-"
},
{
"name" : "iPad Pro (12.9-inch) (3rd generation)",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/iPad Pro (12.9-inch) (3rd generation).simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro--12-9-inch---3rd-generation-"
},
{
"name" : "Apple TV",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/AppleTVOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/Apple TV.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-TV-1080p"
},
{
"name" : "Apple TV 4K",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/AppleTVOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/Apple TV 4K.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-TV-4K-4K"
},
{
"name" : "Apple TV 4K (at 1080p)",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/AppleTVOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/Apple TV 4K (at 1080p).simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-TV-4K-1080p"
},
{
"name" : "Apple Watch - 38mm",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/WatchOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/Apple Watch - 38mm.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-38mm"
},
{
"name" : "Apple Watch - 42mm",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/WatchOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/Apple Watch - 42mm.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-42mm"
},
{
"name" : "Apple Watch Series 2 - 38mm",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/WatchOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/Apple Watch Series 2 - 38mm.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-2-38mm"
},
{
"name" : "Apple Watch Series 2 - 42mm",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/WatchOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/Apple Watch Series 2 - 42mm.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-2-42mm"
},
{
"name" : "Apple Watch Series 3 - 38mm",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/WatchOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/Apple Watch Series 3 - 38mm.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-3-38mm"
},
{
"name" : "Apple Watch Series 3 - 42mm",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/WatchOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/Apple Watch Series 3 - 42mm.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-3-42mm"
},
{
"name" : "Apple Watch Series 4 - 40mm",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/WatchOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/Apple Watch Series 4 - 40mm.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-4-40mm"
},
{
"name" : "Apple Watch Series 4 - 44mm",
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/WatchOS.platform/Developer/Library/CoreSimulator/Profiles/DeviceTypes/Apple Watch Series 4 - 44mm.simdevicetype",
"identifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-4-44mm"
}
],
"runtimes" : [
{
"bundlePath" : "/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 11.4.simruntime",
"availabilityError" : "",
"buildversion" : "15F79",
"availability" : "(available)",
"isAvailable" : true,
"identifier" : "com.apple.CoreSimulator.SimRuntime.iOS-11-4",
"version" : "11.4",
"name" : "iOS 11.4"
},
{
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/Runtimes/iOS.simruntime",
"availabilityError" : "",
"buildversion" : "16E226",
"availability" : "(available)",
"isAvailable" : true,
"identifier" : "com.apple.CoreSimulator.SimRuntime.iOS-12-2",
"version" : "12.2",
"name" : "iOS 12.2"
},
{
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/AppleTVOS.platform/Developer/Library/CoreSimulator/Profiles/Runtimes/tvOS.simruntime",
"availabilityError" : "",
"buildversion" : "16L225",
"availability" : "(available)",
"isAvailable" : true,
"identifier" : "com.apple.CoreSimulator.SimRuntime.tvOS-12-2",
"version" : "12.2",
"name" : "tvOS 12.2"
},
{
"bundlePath" : "/Applications/Xcode.app/Contents/Developer/Platforms/WatchOS.platform/Developer/Library/CoreSimulator/Profiles/Runtimes/watchOS.simruntime",
"availabilityError" : "",
"buildversion" : "16T224",
"availability" : "(available)",
"isAvailable" : true,
"identifier" : "com.apple.CoreSimulator.SimRuntime.watchOS-5-2",
"version" : "5.2",
"name" : "watchOS 5.2"
}
],
"devices" : {
"com.apple.CoreSimulator.SimRuntime.tvOS-12-2" : [
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "Apple TV",
"udid" : "5077B8BB-D341-4581-9012-623F498645A3",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "Apple TV 4K",
"udid" : "02C31044-B231-40B9-B5DC-5E6CDD535155",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "Apple TV 4K (at 1080p)",
"udid" : "2D970F84-55C8-4E6F-8107-BE838ACE360E",
"availabilityError" : ""
}
],
"com.apple.CoreSimulator.SimRuntime.iOS-11-4" : [
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPhone 5s",
"udid" : "D14B5BC1-6B56-46D1-ACF8-7382AE62865F",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPhone 6",
"udid" : "67DC02EE-8430-402A-BA6B-8889243D01FD",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPhone 6 Plus",
"udid" : "5BE62E87-414C-4FB6-A6E9-FB6BE3DA708E",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPhone 6s",
"udid" : "CE701A47-9E62-4A2F-9138-60E300467007",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPhone 6s Plus",
"udid" : "E1434DA4-86DD-490D-BFBE-032B08CC198C",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPhone 7",
"udid" : "E50142B3-0B96-46CD-94D4-379A41FEFC3A",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPhone 7 Plus",
"udid" : "3D1068C1-BA43-4031-A1F6-4695A3376664",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPhone 8",
"udid" : "27B0DE6A-D934-4CFC-B9B1-979AA9AE3B23",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPhone 8 Plus",
"udid" : "8D8AC611-39C6-4D9C-8F23-383E68976057",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPhone SE",
"udid" : "2C5FA1C7-8FD5-484C-A3C4-C65FFD0662A7",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPhone X",
"udid" : "79D2C934-E63B-445D-B2D6-966EE2198410",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPad Air",
"udid" : "6C3553EC-FE6F-4076-9267-702AF7860C00",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPad Air 2",
"udid" : "1EFCC014-2462-4901-885C-F5CCA128BAF4",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPad (5th generation)",
"udid" : "CF05FD6F-5570-4E73-BCB4-0E10E7EFBE46",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPad Pro (9.7-inch)",
"udid" : "DE1FD48C-017F-4580-9F8F-94F8D577B97D",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPad Pro (12.9-inch)",
"udid" : "4E8D37E1-806E-48CF-A4B0-3E260078326F",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPad Pro (12.9-inch) (2nd generation)",
"udid" : "DFAB1558-332A-41E5-95E6-8A472BD84C2B",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPad Pro (10.5-inch)",
"udid" : "A70E541C-C797-4239-97C2-96219BA3622A",
"availabilityError" : ""
}
],
"com.apple.CoreSimulator.SimRuntime.watchOS-5-2" : [
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "Apple Watch Series 2 - 38mm",
"udid" : "7296C512-4612-4E9A-824C-B2924EDA862B",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "Apple Watch Series 2 - 42mm",
"udid" : "CB20D5F5-361C-4E3E-85E4-1826D5087520",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "Apple Watch Series 3 - 38mm",
"udid" : "BF7B87A5-BF08-49EE-A860-28A64F0C5B0A",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "Apple Watch Series 3 - 42mm",
"udid" : "60B74A2B-61C4-45DC-825A-D380072DD6DF",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "Apple Watch Series 4 - 40mm",
"udid" : "1CC0969E-7941-4C59-9831-EBD3E741A4D8",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "Apple Watch Series 4 - 44mm",
"udid" : "679EBA2F-3753-45D4-A16C-D12B6F9208F1",
"availabilityError" : ""
}
],
"com.apple.CoreSimulator.SimRuntime.iOS-12-2" : [
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPhone 5s",
"udid" : "BE2D764F-72C0-401C-8E12-8E32BA502037",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPhone 6",
"udid" : "F07425AE-7712-43B1-B987-8EEEFBE9908F",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPhone 6 Plus",
"udid" : "59B39758-1EC4-4EF6-9A2E-0DD1F87ADC8E",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPhone 6s",
"udid" : "18AB9159-BF51-4846-89A5-5D5A88194297",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPhone 6s Plus",
"udid" : "B557EDB4-15F6-4B7F-AB71-FC5354689954",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPhone 7",
"udid" : "2439EBDD-D458-48B4-B524-DA850C311775",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPhone 7 Plus",
"udid" : "A3739703-A36A-44D9-B82E-62D3666CA853",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPhone 8",
"udid" : "041E4CA5-7C33-4500-9438-119F247173BE",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPhone 8 Plus",
"udid" : "707D8549-EF3E-454E-BC7A-593B3EC0E6D3",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPhone SE",
"udid" : "63BF90ED-E85C-4BC7-B441-AA082C43A83D",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPhone X",
"udid" : "3D7B6980-1783-491A-8F81-09FB3A83519E",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPhone Xs",
"udid" : "C101781E-C0B0-43E4-95F7-C8775B47364A",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPhone Xs Max",
"udid" : "24FF049A-41B2-4D50-BB04-049A0B2E8263",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPhone Xʀ",
"udid" : "F4C441F2-6A0A-4DA4-83E4-59E4ABC9681D",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPad Air (3rd generation)",
"udid" : "7198A0F4-B6A2-4512-BDAC-EA2041F46988",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPad Air",
"udid" : "8FBB55F1-BD4E-402C-A62F-0581DC475068",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPad Air 2",
"udid" : "618CC9E8-8650-48F7-82CA-CA14116B7F5A",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPad (5th generation)",
"udid" : "A63454F5-C9A3-4CA0-9815-97D3DC2BE46B",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPad Pro (9.7-inch)",
"udid" : "0E69CDE8-E3DF-473F-AED1-3A30510D55CD",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPad Pro (12.9-inch)",
"udid" : "BD88CF91-D337-407F-BD39-38E78023E87B",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPad Pro (12.9-inch) (2nd generation)",
"udid" : "85C6DB40-30E9-4C97-BF73-13C5879BBBEC",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPad Pro (10.5-inch)",
"udid" : "33CDC48E-5DA3-4C94-875E-26BAC12B9AF2",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPad (6th generation)",
"udid" : "31C898B4-32EB-4ECD-99FA-E1451F2B691C",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPad Pro (11-inch)",
"udid" : "5CD62E06-A349-4DE0-A31E-2AAB6683CD33",
"availabilityError" : ""
},
{
"availability" : "(available)",
"state" : "Shutdown",
"isAvailable" : true,
"name" : "iPad Pro (12.9-inch) (3rd generation)",
"udid" : "70F10A2E-07A5-45A7-A5B8-4B27BB682544",
"availabilityError" : ""
}
]
},
"pairs" : {
"981506FB-BEA1-4CA0-B26E-AC0E11BF4206" : {
"watch" : {
"name" : "Apple Watch Series 4 - 44mm",
"udid" : "679EBA2F-3753-45D4-A16C-D12B6F9208F1",
"state" : "Shutdown"
},
"phone" : {
"name" : "iPhone Xs Max",
"udid" : "24FF049A-41B2-4D50-BB04-049A0B2E8263",
"state" : "Shutdown"
},
"state" : "(active, disconnected)"
},
"D7CE648D-BC4A-4FE9-86FE-CD5AA60EEE7D" : {
"watch" : {
"name" : "Apple Watch Series 4 - 40mm",
"udid" : "1CC0969E-7941-4C59-9831-EBD3E741A4D8",
"state" : "Shutdown"
},
"phone" : {
"name" : "iPhone Xs",
"udid" : "C101781E-C0B0-43E4-95F7-C8775B47364A",
"state" : "Shutdown"
},
"state" : "(active, disconnected)"
}
}
}

@shazron  one more info, it works when i specify new naming convenction of CoresimulatorRuntime
so this command starts simulator as it should
ionic cordova run ios -l -c -s --target="iPhone-X,com.apple.CoreSimulator.mRuntime.iOS-12-2" -- --buildFlag="-UseModernBuildSystem=0"
but ios-sim showdevicetypes returns old "preffered" naming:
Aleksandars-MacBook-Pro-PETROL:mBillsIonic aleksandaradzic$ ios-sim showdevicetypes Apple-TV-1080p, tvOS 12.2 Apple-TV-4K-4K, tvOS 12.2 Apple-TV-4K-1080p, tvOS 12.2 iPhone-5s, 11.4 iPhone-5s, 12.2 iPhone-6, 11.4 iPhone-6, 12.2 iPhone-6-Plus, 11.4 iPhone-6-Plus, 12.2 iPhone-6s, 11.4 iPhone-6s, 12.2 iPhone-6s-Plus, 11.4 iPhone-6s-Plus, 12.2 iPhone-7, 11.4 iPhone-7, 12.2 iPhone-7-Plus, 11.4
Am I still missing something?

Just to confirm that @leonardomontes workaround did the job for me too, so I can continue using the stable ios-sim version.

@Adza93 yes, the proper @next version of ios-sim was not installed properly. I assure you this issue has been fixed in @next, it's probably an npm issue not installing it properly. Try npm uninstall ios-sim before installing it to see if it makes a difference. You should see the deprecation notice when running cordova run --list if it was installed properly. Try also to verify that the version of ios-sim in platforms/ios/node_modules is correct.
ios-sim showdevicetypes, if you installed ios-sim@next globally using the -g flag, should report the correct values as well.

@Adza93 the issue about Safari debugging not in sync with iOS 12.2 has been resolved by Apple with the latest macOS update 10.14.4 which contains the Safari update to version 12.1

For global install of @next, the version should be:
$ ios-sim --version
ios-sim/9.0.0-dev.4 darwin-x64 node-v8.15.1

I received this error:
Error: ENOENT: no such file or directory, stat '/Users/baothienpham/Library/Logs/CoreSimulator/ACD306CC-304E-47BC-8354-DC397C547C6A/system.log'

I also did install ios-sim@next.

@baotpham context? this happened after running which command

@shazron I ran
cordova emulate ios --debug --target "iPhone-X,com.apple.CoreSimulator.SimRuntime.iOS-12-2" --buildFlag='-UseModernBuildSystem=0'

and
cordova emulate ios --target="iPhone-X"

thanks for the help!

Thank you for your great support @shazron !
Everything is working fine now (as before the Xcode update)
quasar dev -m cordova -T ios opens a default simulator as expected.
Thank you for your hard work @shazron! :)

One snafu -- the ios-sim CLI now requires node 8. cordova supports node 6 and above, so it might be one source of problems. There is one place where I'm using the object spread operator, I'll have to find an alternative for node 6 so it runs in cordova with node 6. The joys of backward compatibility!

Looks like ios-sim 9 will not be compatible for Cordova if you have node 6. Thus I'm also preparing a ios-sim 8.x patch release as well for Cordova.

Preparing an 8.0.1 release. Also I realize that my workaround instructions were faulty. It should be:
For the workaround, try in the root of your cordova app after each time the ios platform is added:
cd platforms/ios/cordova
npm install ios-sim

Note that only do this once I release the 8.0.1 patch

@shazron
No success in 2020.
Please check this one.
ios-sim version
ios-sim/9.0.0 darwin-x64 node-v13.12.0
Cordova version
10.0.0
Cordova iOS platform version
ios 5.1.1
I tried this cmd
sudo cordova emulate ios --debug --target "iPhone-SE--2nd-generation-, 13.5" --buildFlag='-UseModernBuildSystem=0'
Check the attached error image also.

Any hack to get over this error. Just tired of launching the app from Xcode every time : (.
Thanks in advance. Let me know if you need anything.


Feature: Remove a block

Hey guys,
I am looking at the playground and it looks like there is no easy way to remove a block (like an icon on the right side or an even when clicking on the right button). Am I missing something, maybe an additional config or this is the correct behaviour?
Thanks a lot :)
Cheers,
Francesco

What do you mean by removing a block? Does backspace or delete on your keyboard not work?

hey @trueadm thanks for your reply! I made a loom video since I think it's easier to show what I meant
https://www.loom.com/share/859d7152f13340748029a28cbbfbb320

hey @trueadm thanks for your reply! I made a loom video since I think it's easier to show what I meant
https://www.loom.com/share/859d7152f13340748029a28cbbfbb320

I think the confusion here is that Lexical isn’t a block-based editor like notion. It could be used to build such an editor, but I don’t think we need to introduce block management as a first-class concept in the playground. You should be able to do this yourself if you want to.

@acywatson thanks! I am indeed a little bit confused, by scanning the playground code I can see there is a notion of "block" base, when you hit enter for instance you create a new "block" that you can move around.
I am very excited by lexical and plan to use it to build an open-source text editor strongly focused on leverage AI language models and I would like to ask for a little bit of guidance.
It would be great if you can ping point in the right place in the playground code where "block" are handled (I am referring to the icon on the left that let you move around the block). Moreover, I'd love to ask the same thing for the plugin that handles the "/" chars, the feature where you hit "/" and opens the command palette on the text editor.
I hope this is the right place and I don't want to bother you guys too much, I really love lexical philosophy but I am a little intimidate by the amount of code/plugins in the playground section and I think a little bit of guidance will help me a lot

The slash command is otherwise known as the ComponentPickerPlugin  and the drag and drop functionality is in the DraggableBlockPlugin plugin.

Thanks a lot @thegreatercurve

The slash command is otherwise known as the ComponentPickerPlugin and the drag and drop functionality is in the DraggableBlockPlugin plugin.

Is there any documentation for these plugins? I couldn't find these in https://lexical.dev/


Update User Interface.

The user interface is garbage. It is upto your discretion to make it look better.
Some suggestions: (Not binding)

Change background
Incorporate a library similar to Bootstrap to make the User interface look better
Anything else that could make it look good

The bounty points you recieve will depend on the extent of imporvments you make!

i would like to work on it

Hey, I would like to work on this as well


Standard vs. Enterprise AAD application registration.

The script is registered the application as a standard Aad application which does not support user assignment. Need it registered as an Enterprise app.

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

ID: 9ae730e6-5e1e-1ae6-5cbd-9eb6d271690b
Version Independent ID: a79daa4b-e8fb-0ed4-867c-430b3c61ceea
Content: Configuring Azure Integration
Content Source: WindowsServerDocs/manage/windows-admin-center/configure/azure-integration.md
Service: unspecified
Product: windows-server-threshold
GitHub Login: @Haley-Rowland
Microsoft Alias: harowl

This was a mistake. Closing -


Fix #230 Detect hash collisions in rpc registration

consider this case:
[Command]
public void Cmdaa ()
{
}

[Command]
public void CmdbB()
{
}

both have the same hash:  723692803
so only the first one was being registered,  and every time you tried to call the second one the first one got called.
This PR changes it so that mirror detects hash collisions when registering commands and rpc and give the user an error

should fix issue #230

Codecov Report

Merging #231 into master will decrease coverage by 0.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master    #231      +/-   ##
=========================================
- Coverage    6.95%   6.94%   -0.02%
=========================================
  Files          29      29
  Lines        5926    5936      +10
  Branches      828     829       +1
=========================================
  Hits          412     412
- Misses       5501    5511      +10
  Partials       13      13

Impacted Files
Coverage Δ

Mirror/Runtime/NetworkBehaviour.cs
0% <0%> (ø)
:arrow_up:

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 92d35a6...08c630d. Read the comment docs.

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


PC Operating systems 2.0

Closes: https://github.com/privacytools/privacytools.io/issues/1376
https://deploy-preview-1969--privacytools-io.netlify.app/operating-systems/#os

Maybe we should also do something about that microcode section. It looks messy and I think most distributions would do this by default.

Would Parabola not be a better alternative to Arch, seeing as it was mentioned in the old page as a fully open source alternative?

Would Parabola not be a better alternative to Arch, seeing as it was mentioned in the old page as a fully open source alternative?

The reason it was removed was because of maintenance issues iirc.

I think we might swap out Guix for NixOS. We really can't be recommending kernels that have known vulnerabilities for political reasons.

But what is surprising is the "the introduction of binary blobs as arrays of numbers in source code for gen7 i915 gpus." That is actually the Intel Haswell / Ivybridge iGPU Leak mitigation that was worked around for addressing CVE-2019-14615, a.k.a. the Intel iGPU information leakage vulnerability from a few months ago that was corrected promptly for modern Intel Gen graphics but the Gen7/Gen7.5 mitigation took much longer due to working around huge performance penalties initially that occurred.
Those performance issues were resolved and the Intel Ivybridge/Haswell iGPU Leak mitigation was merged in Linux 5.7 to prevent those users on these older generation graphics from potentially being compromised. But GNU Linux-libre 5.7 is unprotected now over the handling of it.

We should have an onion image for this I think:

Then I think it's good to go.

@dngray I just remembered about hyperbola, another open source, Arch alternative. It seems to be getting updates, though from the site it says that they are "planning on implementing a completely new OS derived from several BSD implementations.". Nonetheless, though that it was worth mentioning.

Nonetheless, though that it was worth mentioning.

Thanks, I'll keep an eye on it. At this time it is too young to be added.


HDDS-7178. [Multi-Tenant] Use optimistic read in Ranger background sync

What changes were proposed in this pull request?
Coordination between the background sync and tenant modification requests is currently done through a stamped lock. The background sync currently holds a read lock for a short period every time it runs to fetch a consistent view of OM and Ranger state, however, tenant modifications will be blocked during this time since they need the write lock.
Since this is already a stamped lock, we can use optimistic read with retries instead of a read lock in the background sync. This way it will not conflict with user tenant modifications as long as there is no divergence between OM and Ranger. If there is divergence, the background sync will still need to push updates under a write lock, blocking tenant modifications while it does so.
This PR also adds some logging improvements to the background sync.
What is the link to the Apache JIRA
HDDS-7178
How was this patch tested?

[x] Unit test added
[ ] Test background sync with live requests and a real Ranger instance (TODO)

@smengcl @prashantpogde PTAL when you get a chance for feedback on this approach. This is pending testing with live Ranger as well. If we want to change the default frequency with which the background sync runs (it's currently every 10 minutes) we can do that in this PR too.

@errose28 Would you resolve the conflict and address the comments?

hey @errose28 ~ the CI build step of findbugs failed~ please take a look when you have some time. thanks!

@errose28 can you please rebase?

Thanks @errose28 for the improvement, @prashantpogde, @smengcl for the review.


respect state when receiving commands

This is to fix issue #14.  The check happens both on MQTT message check and on GarageDoor object functions.

Thanks!


Class namings

io.github.stefanbratanov.jvm.openai.Thread class, sharing the same name java.lang.Thread, which is imported by default, causes some issues when using the library. Each time prefixing it with the full package name become a bit tedious. Maybe changing the class names that could potentially cause conflicts could help?
This is also applicable for some other classes like File, Constants etc. But since these classes are not included automatically, it is not that big problem.
thank you

Also, CreateThreadRequest.Message and ChatCompletion.Choice.Message classes are confusing for the people who are not very familiar with the api.
Even if the name changing is not possible, code samples could be updated to specify which one is used. Otherwise, because the imports are not provided, default Eclipse automatic imports cause many compilation errors.

Hi, thanks a lot for raising this. I was thinking about simplifying the nested classes. Would also update the README when done.

For the moment updated the README in https://github.com/StefanBratanov/jvm-openai/commit/694eb6d3ea26f656f19495607ffc976171faabc6 . Will keep this issue open if I come up with namings, reorganization to make usage of classes easier.


implement mocking

This aims to bring in twitch-cli to CI and for users. More changes to be done in future prs
Remaining:

[ ] Add a CI workflow that tries to warn on discrepancies between the library and twitch-cli.
[ ] (this is specific to twitch_oauth2, but use /auth/validate if/when available, see https://github.com/twitchdev/twitch-cli/issues/82

side-note: The issue with wrong status code might explain a lot of the troubles experienced with wrong status codes hehe :) .
https://github.com/Emilgardis/twitch_api2/blob/0a56269b1353e3b138e6724ab31fb6d48bb534b4/src/helix/predictions/create_prediction.rs#L231 for example

merged the fixes in #191

bors r+


API to fetch team logo

Hello
It would be great if there was an API call that will return url to team logo. Something like eg:
var url = nba.getTeamLogo(teamId)

here you go:
const nba = require("nba");
function teamLogoUrl (teamId) {
  const team = nba.teams.find(t => t.teamId === teamId);
  if (team == null) return null;
  return `http://stats.nba.com/media/img/teams/logos/${team.abbreviation}_logo.svg`
}

Great, thanks!


Occasional reboots on android TV during download

Expected Behavior

Current Behavior

I guess i already faced this issue 10 times. Usually during download of one torrent and watching another. Started recently, maybe several weeks ago.
Possible Solution

Steps to Reproduce (for bugs)

Context

Your Environment

Version used:

Environment name and version: spmc 17

Operating System and version: android TV 8 , xiaomi mi box 3

Link to Kodi debug log:

Log before unexpected reboot
https://paste.ubuntu.com/p/ghhcv56c4Z/

To be honest it reproduces very often. Loke every time i download something big (more than 20-30 minutes of download)

Plugin does not interact with a system/OS.
I have no ideas what is the reason for reboots and what can cause them. You can try to debug or something like that.

In version 0.1.35 linux binaries are built statically with use of Musl, instead of dynamically linking to libc.
I'm not sure how android works in that field.
Can you try to run manually linux arm64/admv7 binaries on your android? Will it run or not?

@antonsoroko do reboots still happen with 0.1.38 and later?

can not say for 0.1.38. need more time. with pre-0.1.38 reboots happen from time to time. Usually when several torrent are downloading at the same time (looks like "big" I/O issue, not sure if it is OS, HW or app issue).

@antonsoroko you don't use memory storage and you use android, which does not use musl for builds. So you should not have Out-of-memory errors.
Maybe worth trying to use latest Android NDK to prepare binaries.

looks like this issue is gone. closing. thanks.


Add accept property

I'm not sure this is quite the right type for the property, from the small amount of googling I just did it suggests there might be something about filenames as well as media types that go/can go in here?

Ignore that, seems like MediaType probably is sufficient - there are other ways of specifying the acceptable types, but they seem less good than MediaType, and this is what we have in dom-indexed right now, so let's go with it :smile:
Thanks!


Add a test which mutates data in another library

I would have a working test for this. It is an important use-case.

This is currently impossible. If a library exposes some mutable data, mut foo: usize for instance, it is impossible to modify foo outside of the library without a transmute. I would like to provide an additional data struct DataMut, which uses * pointers rather than * const pointers, eventually. Of course, a mutable reference to the struct would be required to access the data. There is nothing preventing this in the current implementation except that I haven't gotten around to it.


export color options

Hi, would be nice to have the different color options for hair, skin and topTypes also exported like you do with the assetsTypes. That way they could be imported instead of copypasta. Happy to send a pull request if you prefer... thanks again

@dhax Make a pull request, I will merge it :)


Configurable burst of OOK for dumb devices (ENER0002 and MIHO002)

Hi,
I have just switched to your client after using the Energenie gateway. I have managed to integrate it with Home Assistant and all is working well. When sending an on/off signal from the official gateway, it repeatedly sends the command for around 20 seconds to give the end devices a better chance of receiving. Would it be possible to do something similar with your client?
Also, do you use the MIHO008 wall switches in your personal set-up? I assumed they used the same legacy OOK protocol, but I have found them to be very unreliable with the ener314-rt board and your client.
Paul

The current code sends the same message 8 times, which takes about 250ms, and works well for me, so sending for 20s seems a bit excessive.
The longer it transmits, the less time there is available for receiving FSK messages, and the longer you have to wait before a second command is sent.
What I can do is make the number of transmits configurable, to allow for different configurations.
The relevant line is 261 in dev_HRF.c.  If you increase 8 to a larger number, you can experiment yourself.  To allow multiple commands to happen after each other, you also need to alter line 281.
I don't have any MIHO008, but from the website they appear to use the same protocol, so should work in the same way.
I have found adjusting the orientation of the PI slightly can make a difference to the radio communication, so I would suggest that.

Thanks for the response. I am no C dev, but will take a look and see how I get on!
I am thinking my issue now is interference on the 433mhz frequency, so need to get to the bottom of that really!

Added -r option to specify the number of times the ook message is sent.

Brilliant. Thanks for adding that.


fix remove shadow prefix of schema for tablesink

LSC updates tablet's schema in writing. Be optimized adding columns via linked schema change and it distinguishes adding by comparing column name. e.g. if new column's name is not found in old schema, then it is a newly-add column.
When a table is under schema-changing, it adds _doris_shadow prefix in name of columns in shadow index. Then  writes during schema-changing would bring schema with _doris_shadow to be. If schema change request arrives at be after writes, then be do it as a add-column schema change due to _doris_shadow is not in base tablet.
Proposed changes
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run buildall

run buildall


Themes on Website

Pull Request Template
Description
I have implemented some of the changes in the code and used the styled-components library so that user can switch back and forth between light and dark mode.
Fixes #26
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[x] My contribution follows the style guidelines of this project
[x] I have performed a self-review of my own contribution
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have checked my code and corrected any misspellings

Here are two screenshots of dark mode and light mode.

https://user-images.githubusercontent.com/73438023/136393132-0f7e2630-b8d9-460c-8a09-4db3e52faaf3.mp4
Here is the video of the changes @nehakalbande

Hi,
On running the site, dark mode appears first.
I need Light mode to appear first. Please do these changes


sfdx force:org:list does not return active orgs

Summary
When running sfdx force:org:list, sfdx force:org:list --all, sfdx force:org:list --verbose --json no active orgs are returned. I am still able to open the latest org but cannot open any other orgs if I do not know the username.
Steps To Reproduce:
Run sfdx force:org:list
Expected result
I have three active scratch orgs that should be displayed. If I switch to a previous version I am able to get the active orgs:

Actual result
No active scratch orgs found. Specify --all to see all scratch orgs:

System Information
{
"cliVersion": "sfdx-cli/7.160.0",
"architecture": "darwin-x64",
"nodeVersion": "node-v14.17.0",
"pluginVersions": [
"@oclif/plugin-autocomplete 0.3.0 (core)",
"@oclif/plugin-commands 1.3.0 (core)",
"@oclif/plugin-help 3.3.1 (core)",
"@oclif/plugin-not-found 1.2.6 (core)",
"@oclif/plugin-plugins 1.10.11 (core)",
"@oclif/plugin-update 1.5.0 (core)",
"@oclif/plugin-warn-if-update-available 1.7.3 (core)",
"@oclif/plugin-which 1.0.4 (core)",
"@salesforce/sfdx-plugin-lwc-test 1.0.0 (core)",
"alias 2.1.0 (core)",
"apex 1.1.0 (core)",
"auth 2.2.2 (core)",
"community 2.0.0 (core)",
"config 1.4.14 (core)",
"custom-metadata 2.0.0 (core)",
"data 2.0.4 (core)",
"generator 2.0.2 (core)",
"info 2.0.1 (core)",
"limits 2.0.1 (core)",
"org 2.0.3 (core)",
"salesforce-alm 54.6.2 (core)",
"schema 2.1.1 (core)",
"sfdx-cli 7.160.0 (core)",
"signups 1.2.0 (core)",
"source 2.0.7 (core)",
"telemetry 2.0.0 (core)",
"templates 55.0.0 (core)",
"trust 2.0.1 (core)",
"user 2.1.0 (core)"
],
"osVersion": "Darwin 21.1.0"
}

whoa!

Does the devhub that they're related to still show up in your org:list results with a good Connected status?
if you open up one of the auth files for an org you're missing like cat<EMAIL_ADDRESS>can you see

Yes and it does still have a good Connected status
{
"instanceUrl": "https://page-data-8336-dev-ed.my.salesforce.com",
"orgId": "00D1h000000OEIWEA4",
"loginUrl": "https://CS79.salesforce.com",
"clientId": "PlatformCLI",
"isDevHub": false,
"devHubUsername": "etc",
"created": "1658776487000",
"expirationDate": "2022-08-08",
"createdOrgInstance": "CS79",
"instanceApiVersion": "55.0",
"instanceApiVersionLastRetrieved": "7/26/2022, 3:50:36 PM",
"name": "Squivr Development",
"instanceName": "CS79",
"namespacePrefix": "squivr",
"isSandbox": false,
"isScratch": true,
"trailExpirationDate": "2022-08-09T19:15:03.000+0000",
"tracksSource": true,
}%

I also hit this issue. Steps to reproduce against dreamhouse-lwc (gist):

sfdx force:org:create
sfdx force:user:password:generate
sfdx force:user:create

@jstvz thanks for your repo. I have been able to reproduce the issue. @james-hafer can you confirm that the orgs not appearing in the list also have additional users created for them?

@peternhale Yes, the orgs have additional users created for them.

Thanks @james-hafer. I have identified the issue and a fix will be made soon.

fix in version 7.162.0 of sfdx-cli

Can confirm it's working as expected when updated the cli to 7.162.0. Thanks a lot for a quick turnaround!

@peternhale This issue is still present in "sfdx-cli/7.188.1 darwin-x64 node-v18.13.0" for Mac OS Monterey 12.6


Intel 80960

i960 / Intel 80960
I was unable to test with SleighDevTools.  I found 2 compilers, one for COFF and kind of decided that was too much development for me at this time (see #1349) and another for ELF, but was unable to get the pcodetest compiling due to limitations in that version of GCC (it was unable to statically initialize the global array containing the unit tests for each test).
(https://github.com/mumbel/ghidra_i960/tree/coff  has my initial attempt at COFF)

What is the correct way to handle frame pointer and stack pointer (and even previous frame pointer) w/ the decompiler?
On function call the it sets up a stack frame to save old local registers to restore from (similar to push/pop) and then sets the SP = FP + 0x40.  On function entry all local registers are "new" and it will SP+=stack_size, and has local variable references using FP+0x40+offset (where 0<offset<stack_size)
Right now I'm getting confusing results in the decompiler, with the best being
int pcode_memcmp_u4(u4 a, u4 b)
{
    // lots of large unused stack buffers
   int iVar1
   *(u4 *)(fp + 0x40) = a;
   *(u4 *)(fp + 0x44) = b;
   iVar1 = memcmp((void *)(fp+0x40), (void *)(fp + 0x44), 4);
}

Another issue is saving the local registers,  this should just be treated like a push/stm... i've tried multiple macros for registers read/writes and one big store, with the 0x40 read/write looking cleaner (fp is not one of the registers that's in the write/read)
local temp = &pfp;
local alignfp = fp & 0xffffffc0;
*[ram]:0x40 alignfp = *[register]:0x40 temp;

both though add a lot of code to the decompiler, either 16 writes to (fp+N) or a really ulgy CONCAT write to fp.
  *(undefined (*) [64])(fp & 0xffffffc0) =
       CONCAT5212(SUB5652(in_register_00000008 >> 0x20,0),
                  CONCAT48(0x35044,CONCAT44(register0x00000004,unaff_pfp)));

Should I just implement like the other stm/push lwm/pop instructions and have it hit 16 constructors that daisy-chain pushing or popping


Investigate CiRA for split Event Labels

Currently, it seems like split event labels (e.g., two occurrences of Event1) result in multiple nodes in the resulting cause-effect graph. This is not the expected behavior and the source of the error must be located.

This was an issue in the CiRA core, not the user interface.


 It is just a simple wrapper. THe reason I am asking is because in my current refactoring I want to remove that API call because it is a shortcut that makes things more confusing than helping I think.  It is just a simple wrapper. The reason I am asking is because in my current refactoring I want to remove that helper function call because it is a shortcut that makes things more confusing than helping I think. You are anyway half-way there since the main work of wrap_with_form is to add a submit button for standalone forms :D

I think it worked to just exchange the two :)


572 lidar clusters to intermediate

Description
Integrated lidar clusters into the intermediate layer.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

New feature (non-breaking change which adds functionality)

Does this PR introduce a breaking change?
no
Most important changes
Which files functionalities are most important in this PR. On which part should the reviewer be focussed on?
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works (might be obsolete with CI later on)
[x] New and existing unit tests pass locally with my changes (might be obsolete with CI later on)

Summary by CodeRabbit

New Features

Introduced a new mapping package with various functionalities for mapping and visualization.
Added a mapping_visualization package for enhanced visualization capabilities in RViz.
Implemented a filter panel in RViz to manage visualization settings for different entity types.

Bug Fixes

Updated LiDAR and radar processing logic for improved data handling and visualization.

Documentation

Added design documents and README files detailing the structure and functionality of the new mapping system.

Tests

Introduced unit tests for various components, ensuring functionality and data integrity within the mapping framework.

Do not merge yet! Merging depends on #570.


GNOSIS Network Integration | Import validator account keys

Make it possible to import GNO Validator Keys into GNO Validator Clients.
No changes in design flow.

has been completed with #973


Changed HazelcastHealthIndicator to use MemoryStats

This PR chages HazelcastHealthIndicator to reference MemoryStats when reporting capacity and percentFree heap.  The method previously used to calculate capacity(LocalMapStats.total()) is nothing more than a counter for operations performed against the Map and does not relate to heap space.

LGTM. Port to master and we should be set to go!

Working on it.

Also starting hz throttle port


Question about how v4 cache works

hey @micimize, I have a question about how the cache works.
Considering a schema like this:
type Animal {
    name: String
}
type Furniture {
    name: String
}

query {
    animals() : [Animal]
    furnitures() : [Furniture]
}

If I watchQuery animals { name } in one widget and then on another I watchQuery furnitures { name }.
Then I mutate an animal, the query on furniture refreshes as well (even if nothing changed on furniture).
Is that correct?
I mean, shouldn't the cache updates only the queries that are related to the mutation data or even when I query another thing, all queries are refreshed.
On my project, I had added a layer to check if the data is really changing before allowing or processing it.
thank you!

@rwrz right – theoretically we could track the data dependencies of each watched operation, and only update those, that work just hasn't been done. I'm guessing that's what apollo does, I haven't looked carefully in to how though

On my project, I had added a layer to check if the data is really changing before allowing or processing it.
I'm curious as to where you're doing this / why you need to? I did consider doing something like

// loose code
newData = cache.read(query.options.asRequest);
if(!deepEquals(query.lastResult.data, newData)){
  query.addResult(QueryResult(newData))
}

But felt that, since query listeners should be reactive already, and thus shouldn't be doing particularly complicated work with each independent result, the cost of doing the deep equals would be greater than whatever downstream operations are done.
For example, a Query component at the same point in the tree with the same data passed to the builder should return the same widget tree from build, and thus not need to rerender.

For example, a Query component at the same point in the tree with the same data passed to the builder should return the same widget tree from build, and thus not need to rerender.

You are right... but usually, we transform the result.data map into a DTO or something. Or even, do some calculations to transform into a ViewModel somehow. These calculations can be expensive and reduce app performance after a few widgets. And since the GraphQL nature is to have several small widgets, querying the cache simultaneously on the same screen, a little "toggle" instead of the build just the toggleWidget, will be building all widgets on the tree that has Query, which goes against Flutter or Apollo ideas.. rs

But felt that, since query listeners should be reactive already, and thus shouldn't be doing particularly complicated work with each independent result, the cost of doing the deep equals would be greater than whatever downstream operations are done.

I have done some tests here and the cost of a deepEquals (DeepCollectionEquality) on query data maps, totally worth it. Are just a few milliseconds or even nanoseconds... But I can take a look at what Apollo is doing right now, but I believe it is something more related to the Fragments, like subscribing to Query fragments changes... instead of comparing results.

@rwrz well for now, if you have a function for filtering QueryResults based on a deep equal check, then you could add a class extension to ObservableQuery that wraps listen in your deduplicator. A more integrated flag is something we can consider adding after the first beta release

Sure. Great idea.
And thank you for your time! =)


✨ [experimental] Probe support for security policy check

Probe support for security policy check

This was a complete re-review of the PR (not just changed files). Only known blocker to approval is the FileTypeURL scoring change.
I'll also probably point this at some live examples to A/B test the change tomorrow.

done.

Thanks. Quick comment. I did some diff testing of old (main) and new (this PR).

Very cool!

old ossf/scorecard:
"Info: Found linked content in security policy: SECURITY.md",
"Info: Found text in security policy: SECURITY.md",
"Info: Found disclosure, vulnerability, and/or timelines in security policy: SECURITY.md",
"Info: security policy detected in current repo: SECURITY.md"

new ossf/scorecard:
"Info: security policy file detected: SECURITY.md:1",
"Info: URL or email contacts found: SECURITY.md:1",
"Info: Found disclosure, vulnerability, and/or timelines in security policy: SECURITY.md:1",
"Info: Found text in security policy: SECURITY.md:1"

Shall I update " URL or email contacts found" to "Found linked content in security policy?

I think this is a result of how the raw result is setup. But we may want to look at this in the future, as it's not really on line 1:
https://github.com/ossf/scorecard/blob/31bd0eab927ece36053ffecf144e87a2fec2f455/checks/raw/security_policy.go#L123-L131
I picked a random repo from our dataset which wasn't getting a 10: https://github.com/airbnb/hypernova-node
old:
"Info: Found linked content in security policy: github.com/airbnb/.github/SECURITY.md",
"Info: Found text in security policy: github.com/airbnb/.github/SECURITY.md",
"Warn: One or no descriptive hints of disclosure, vulnerability, and/or timelines in security policy: github.com/airbnb/.github/SECURITY.md",
"Info: security policy detected in org repo: github.com/airbnb/.github/SECURITY.md"

new:
"Info: security policy file detected: github.com/airbnb/.github/SECURITY.md:1",
"Info: URL or email contacts found: github.com/airbnb/.github/SECURITY.md:1",
"Warn: One or no descriptive hints of disclosure, vulnerability, and/or timelines in security policy: On GitHub:\nEnable private vulnerability disclosure in your repository settings https://docs.github.com/en/code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository\nAdd a section in your SECURITY.md indicating you have enabled private reporting, and tell them to follow the steps in https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability to report vulnerabilities.\nOn GitLab:\nAdd a section in your SECURITY.md indicating the process to disclose vulnerabilities for your project.\nExamples: https://github.com/ossf/scorecard/blob/main/SECURITY.md, https://github.com/slsa-framework/slsa-github-generator/blob/main/SECURITY.md, https://github.com/sigstore/.github/blob/main/SECURITY.md. (Low effort)",
"Info: Found text in security policy: github.com/airbnb/.github/SECURITY.md:1"

Some of the warnings get a little long with the remediation. Thoughts?

I can remove these lines https://github.com/ossf/scorecard/blob/main/pkg/common.go#L65-L68. At the same time I'd like to be able to show folks the remediation. So maybe we add a --show-remediation to the CLI (not this PR). Wdut?

Shall I update " URL or email contacts found" to "Found linked content in security policy?

Up to you. We obviously cant keep every detail identical, and the line number will be different. This is just a matter of phrasing which I will defer to you.

I can remove these lines https://github.com/ossf/scorecard/blob/main/pkg/common.go#L65-L68. At the same time I'd like to be able to show folks the remediation. So maybe we add a --show-remediation to the CLI (not this PR). Wdut?

Does any of this get easier with a more probe centric output format? (Compared to now when probe results are trying to fit in the existing JSON format).

Shall I update " URL or email contacts found" to "Found linked content in security policy?

Up to you. We obviously cant keep every detail identical, and the line number will be different. This is just a matter of phrasing which I will defer to you.

I can remove these lines https://github.com/ossf/scorecard/blob/main/pkg/common.go#L65-L68. At the same time I'd like to be able to show folks the remediation. So maybe we add a --show-remediation to the CLI (not this PR). Wdut?

Does any of this get easier with a more probe centric output format? (Compared to now when probe results are trying to fit in the existing JSON format).

There is a --format=probe already supported. So shall I remove the remediation part from json format then?

Shall I update " URL or email contacts found" to "Found linked content in security policy?

Up to you. We obviously cant keep every detail identical, and the line number will be different. This is just a matter of phrasing which I will defer to you.

I can remove these lines https://github.com/ossf/scorecard/blob/main/pkg/common.go#L65-L68. At the same time I'd like to be able to show folks the remediation. So maybe we add a --show-remediation to the CLI (not this PR). Wdut?

Does any of this get easier with a more probe centric output format? (Compared to now when probe results are trying to fit in the existing JSON format).

There is a --format=probe already supported. So shall I remove the remediation part from json format then?

Do any of the converted probes have remediation already? I don't think so, so SGTM.


CAPD workload clusters cannot be created  using v0.11.0-rc2

Management cluster creates without issue.
$ CLUSTER_PLAN=dev tanzu mc create -i docker

Validating the pre-requisites...
Identity Provider not configured. Some authentication features won't work.
WARNING: key is not a string: %!s(int=1)WARNING: key is not a string: %!s(int=1)
Setting up management cluster...
Validating configuration...
Using infrastructure provider docker:v1.0.1
Generating cluster configuration...
WARNING: key is not a string: %!s(int=1)WARNING: key is not a string: %!s(int=1)Setting up bootstrapper...
Bootstrapper created. Kubeconfig: /home/josh/.kube-tkg/tmp/config_XlZRr4BS
Installing providers on bootstrapper...
Fetching providers
Installing cert-manager Version="v1.5.3"
Waiting for cert-manager to be available...
Installing Provider="cluster-api" Version="v1.0.1" TargetNamespace="capi-system"
Installing Provider="bootstrap-kubeadm" Version="v1.0.1" TargetNamespace="capi-kubeadm-bootstrap-system"
Installing Provider="control-plane-kubeadm" Version="v1.0.1" TargetNamespace="capi-kubeadm-control-plane-system"
Installing Provider="infrastructure-docker" Version="v1.0.1" TargetNamespace="capd-system"
Start creating management cluster...
[cluster control plane is still being initialized: WaitingForControlPlane, cluster infrastructure is still being provisioned: WaitingForControlPlane]
cluster control plane is still being initialized: WaitingForControlPlane
cluster control plane is still being initialized: ScalingUp
Saving management cluster kubeconfig into /home/josh/.kube/config
Installing providers on management cluster...
Fetching providers
Installing cert-manager Version="v1.5.3"
Waiting for cert-manager to be available...
Installing Provider="cluster-api" Version="v1.0.1" TargetNamespace="capi-system"
I0322 08:23:19.487638   71151 request.go:665] Waited for 1.040847587s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:6443/apis/storage.k8s.io/v1?timeout=30s
Installing Provider="bootstrap-kubeadm" Version="v1.0.1" TargetNamespace="capi-kubeadm-bootstrap-system"
Installing Provider="control-plane-kubeadm" Version="v1.0.1" TargetNamespace="capi-kubeadm-control-plane-system"
Installing Provider="infrastructure-docker" Version="v1.0.1" TargetNamespace="capd-system"
I0322 08:23:29.499331   71151 request.go:665] Waited for 1.33974822s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:6443/apis/infrastructure.cluster.x-k8s.io/v1alpha4?timeout=30s
Waiting for the management cluster to get ready for move...
Waiting for addons installation...
Moving all Cluster API objects from bootstrap cluster to management cluster...
Performing move...
Discovering Cluster API objects
Moving Cluster API objects Clusters=1
Creating objects in the target cluster
Deleting objects from the source cluster
Waiting for additional components to be up and running...
Waiting for packages to be up and running...
You can now access the management cluster tkg-mgmt-docker-20220322081648 by running 'kubectl config use-context tkg-mgmt-docker-20220322081648-admin@tkg-mgmt-docker-20220322081648'

Management cluster created!

You can now create your first workload cluster by running the following:

  tanzu cluster create [name] -f [file]

Some addons might be getting installed! Check their status by running the following:

  kubectl get apps -A

Checking for required plugins...
I0322 08:26:57.387785   71151 request.go:665] Waited for 1.190028879s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:6443/apis/policy/v1beta1?timeout=32s
I0322 08:27:07.388320   71151 request.go:665] Waited for 11.190500667s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:6443/apis/security.antrea.tanzu.vmware.com/v1alpha1?timeout=32s
I0322 08:27:17.394365   71151 request.go:665] Waited for 9.190554524s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:6443/apis/data.packaging.carvel.dev/v1alpha1?timeout=32s
All required plugins are already installed and up-to-date

Note the client-side throttling warnings (info) in the bottom of the log.
After this occurs, all operations with tanzu against the management cluster are slow and produce those messages, for example:
$ tanzu mc get
I0322 08:33:31.829718  125278 request.go:665] Waited for 1.188329834s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:6443/apis/policy/v1beta1?timeout=32s
I0322 08:33:41.830308  125278 request.go:665] Waited for 11.187939128s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:6443/apis/controlplane.antrea.tanzu.vmware.com/v1beta2?timeout=32s
I0322 08:33:51.874911  125278 request.go:665] Waited for 9.187827328s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:6443/apis/coordination.k8s.io/v1?timeout=32s
I0322 08:34:01.936030  125278 request.go:665] Waited for 7.19033453s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:6443/apis/internal.packaging.carvel.dev/v1alpha1?timeout=32s
  NAME                            NAMESPACE   STATUS   CONTROLPLANE  WORKERS  KUBERNETES        ROLES       PLAN
  tkg-mgmt-docker-20220322081648  tkg-system  running  1/1           1/1      v1.22.5+vmware.1  management  dev

Details:

NAME                                                                               READY  SEVERITY  REASON  SINCE  MESSAGE
/tkg-mgmt-docker-20220322081648                                                    True                     10m
├─ClusterInfrastructure - DockerCluster/tkg-mgmt-docker-20220322081648             True                     10m
├─ControlPlane - KubeadmControlPlane/tkg-mgmt-docker-20220322081648-control-plane  True                     10m
│ └─Machine/tkg-mgmt-docker-20220322081648-control-plane-tpkbt                     True                     10m
└─Workers
  └─MachineDeployment/tkg-mgmt-docker-20220322081648-md-0                          True                     10m
    └─Machine/tkg-mgmt-docker-20220322081648-md-0-5f49bbdc5d-k28n8                 True                     10m

Providers:

  NAMESPACE                          NAME                   TYPE                    PROVIDERNAME  VERSION  WATCHNAMESPACE
  capd-system                        infrastructure-docker  InfrastructureProvider  docker        v1.0.1
  capi-kubeadm-bootstrap-system      bootstrap-kubeadm      BootstrapProvider       kubeadm       v1.0.1
  capi-kubeadm-control-plane-system  control-plane-kubeadm  ControlPlaneProvider    kubeadm       v1.0.1
  capi-system                        cluster-api            CoreProvider            cluster-api   v1.0.1

Attempts to create a workload cluster will create errors like:
$ CLUSTER_PLAN=dev tanzu cluster create wrkld
Validating configuration...
I0322 08:34:26.152668  128255 request.go:665] Waited for 1.186437582s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:6443/apis/batch/v1beta1?timeout=32s
I0322 08:34:36.352947  128255 request.go:665] Waited for 11.386668547s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:6443/apis/crd.antrea.io/v1alpha3?timeout=32s
Error: validation failed: unable to get name and namespace of current management cluster: failed to list *v1alpha3.ClusterList: conversion webhook for cluster.x-k8s.io/v1beta1, Kind=Cluster failed: Post "https://capi-webhook-service.capi-system.svc:443/convert?timeout=30s": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Usage:
  tanzu cluster create CLUSTER_NAME [flags]

Flags:
  -d, --dry-run       Does not create cluster, but show the deployment YAML instead
  -f, --file string   Configuration file from which to create a cluster
  -h, --help          help for create
      --tkr string    TanzuKubernetesRelease(TKr) to be used for creating the workload cluster. If TKr name prefix is provided, the latest compatible TKr matching the TKr name prefix would be used

Global Flags:
      --log-file string   Log file path
  -v, --verbose int32     Number for the log level verbosity(0-9)

Error: exit status 1

✖  exit status 1

@stmcginnis will attempt cluster create with kubectl and see if it is successful.

kubectl investigation results:
Created a management cluster with CLUSTER_PLAN=dev tanzu mc create -i docker. Cluster created successfully.
Created a configuration based on https://github.com/kubernetes-sigs/cluster-api/blob/main/test/infrastructure/docker/examples/simple-cluster.yaml and local cluster settings. Used the following for workload cluster definition:
apiVersion: infrastructure.cluster.x-k8s.io/v1beta1
kind: DockerCluster
metadata:
  name: myworkloadclstr
  namespace: tkg-system
---
apiVersion: cluster.x-k8s.io/v1beta1
kind: Cluster
metadata:
  name: myworkloadclstr
  namespace: tkg-system
spec:
  clusterNetwork:
    pods:
      cidrBlocks:
      - <IP_ADDRESS>/11
    services:
      cidrBlocks:
      - <IP_ADDRESS>/16
  controlPlaneRef:
    apiVersion: controlplane.cluster.x-k8s.io/v1beta1
    kind: KubeadmControlPlane
    name: myworkloadclstr-control-plane
    namespace: tkg-system
  infrastructureRef:
    apiVersion: infrastructure.cluster.x-k8s.io/v1beta1
    kind: DockerCluster
    name: myworkloadclstr
    namespace: tkg-system
---
apiVersion: infrastructure.cluster.x-k8s.io/v1beta1
kind: DockerMachineTemplate
metadata:
  name: controlplane
  namespace: tkg-system
spec:
  template:
    spec: {}
---
apiVersion: controlplane.cluster.x-k8s.io/v1beta1
kind: KubeadmControlPlane
metadata:
  name: controlplane
  namespace: tkg-system
spec:
  replicas: 1
  version: v1.23.3
  machineTemplate:
    infrastructureRef:
      apiVersion: infrastructure.cluster.x-k8s.io/v1beta1
      kind: DockerMachineTemplate
      name: controlplane
      namespace: tkg-system
  kubeadmConfigSpec:
    clusterConfiguration:
      apiServer:
        certSANs:
        - localhost
        - <IP_ADDRESS>
        - <IP_ADDRESS>
      controllerManager:
        extraArgs:
          enable-hostpath-provisioner: "true"
    initConfiguration:
      nodeRegistration:
        kubeletExtraArgs:
          # We have to pin the cgroupDriver to cgroupfs as kubeadm >=1.21 defaults to systemd
          # kind will implement systemd support in: https://github.com/kubernetes-sigs/kind/issues/1726
          cgroup-driver: cgroupfs
          eviction-hard: nodefs.available<0%,nodefs.inodesFree<0%,imagefs.available<0%
    joinConfiguration:
      nodeRegistration:
        kubeletExtraArgs:
          # We have to pin the cgroupDriver to cgroupfs as kubeadm >=1.21 defaults to systemd
          # kind will implement systemd support in: https://github.com/kubernetes-sigs/kind/issues/1726
          cgroup-driver: cgroupfs
          eviction-hard: nodefs.available<0%,nodefs.inodesFree<0%,imagefs.available<0%
---
apiVersion: infrastructure.cluster.x-k8s.io/v1beta1
kind: DockerMachineTemplate
metadata:
  name: worker
  namespace: tkg-system
spec:
  template:
    spec: {}
---
apiVersion: bootstrap.cluster.x-k8s.io/v1beta1
kind: KubeadmConfigTemplate
metadata:
  name: worker
spec:
  template:
    spec:
      joinConfiguration:
        nodeRegistration:
          kubeletExtraArgs:
            # We have to pin the cgroupDriver to cgroupfs as kubeadm >=1.21 defaults to systemd
            # kind will implement systemd support in: https://github.com/kubernetes-sigs/kind/issues/1726
            cgroup-driver: cgroupfs
            eviction-hard: nodefs.available<0%,nodefs.inodesFree<0%,imagefs.available<0%
---
apiVersion: cluster.x-k8s.io/v1beta1
kind: MachineDeployment
metadata:
  name: worker-md-0
spec:
  clusterName: myworkloadclstr
  replicas: 1
  selector:
    matchLabels:
      cluster.x-k8s.io/cluster-name: myworkloadclstr
  template:
    spec:
      version: v1.23.3
      clusterName: myworkloadclstr
      bootstrap:
        configRef:
          apiVersion: bootstrap.cluster.x-k8s.io/v1beta1
          kind: KubeadmConfigTemplate
          name: worker
      infrastructureRef:
        apiVersion: infrastructure.cluster.x-k8s.io/v1beta1
        kind: DockerMachineTemplate
        name: worker

Used that to deploy workload cluster:
$ k apply -f cluster.yaml
dockercluster.infrastructure.cluster.x-k8s.io/myworkloadclstr created
cluster.cluster.x-k8s.io/myworkloadclstr created
dockermachinetemplate.infrastructure.cluster.x-k8s.io/controlplane created
kubeadmcontrolplane.controlplane.cluster.x-k8s.io/controlplane created
dockermachinetemplate.infrastructure.cluster.x-k8s.io/worker created
kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/worker created
machinedeployment.cluster.x-k8s.io/worker-md-0 created

No delay, and it appears to have created the cluster:
$ k get clusters -n tkg-system
NAME                             PHASE         AGE   VERSION
myworkloadclstr                  Provisioned   47s
tkg-mgmt-docker-20220322095846   Provisioned   14m

Seems this is a race condition that happens about 50% of the time. There have been 3 observed outcomes:

The cluster creates without issue
The cluster creates with issue but then reconciles to good state
The cluster creates with issue and never reconciles to a good state.

In the case of 3, the following observation has been made showing many components hung up on one another:

We did this validation by making multiple duplicate instances on EC2 and triggering managed clusters (CAPD) at the same time, which the same binary.

We did this validation by making multiple duplicate instances on EC2 and triggering managed clusters (CAPD) at the same time, which the same binary.

@joshrosso I am trying to understand what you meant. Did you create multiple AWS instances and on each of them attempt to create an MC then an WC?

We did this validation by making multiple duplicate instances on EC2 and triggering managed clusters (CAPD) at the same time, which the same binary.

@joshrosso I am trying to understand what you meant. Did you create multiple AWS instances and on each of them attempt to create an MC then an WC?
Also is the belief that in v0.10.0 the CAPD WC creation was more reliable?

@vuil I created multiple AWS instances, then on each, using CAPD, attempted to created a management cluster. In VMs where the cluster got into a bad state, workload creation would always fail, and most operations via tanzu would take almost a minute.

Also is the belief that in v0.10.0 the CAPD WC creation was more reliable?

We did multiple tests with v0.10.0 and this problem does not surface
@vuil let me know what's needed from our team. We can give you an AMI/script with how to reproduce this. We could give an SSH key to an instance in this state? Biggest note is it's intermittent so a consistent/reporoduceable environment and multiple tries is required.
We appreciate your follow-up.

Moving this to at-extreme-risk I don't believe this will make it as we already have our cut of framework.

I'm adding my experience to the issue as I had a similar failure:
This is my attempt to deploy TCE 0.11  on Pop_OS. The local machine is an 11th Gen Intel<EMAIL_ADDRESS>GHz 16 core with 64GB of memory so I don't think it's asphyxiated, This time the deployment of the Management cluster fails, but when I look at the debug information, I don't see any failed Pod and the service that it is complaining about in particular capd-controller-manager  is up and running, though the command seems to have failed due to time out waiting for this service...
`Failed waiting for at least one provider, check logs for more detail.
Failure while deploying management cluster, Here are some steps to investigate the cause:
Debug:
kubectl get po,deploy,cluster,kubeadmcontrolplane,machine,machinedeployment -A --kubeconfig /home/l0r3zz/.kube-tkg/tmp/config_vupVfb7L
kubectl logs deployment.apps/ -n  manager --kubeconfig /home/l0r3zz/.kube-tkg/tmp/config_vupVfb7L
To clean up the resources created by the management cluster:
tanzu management-cluster delete
unable to set up management cluster, : unable to initialize providers on management cluster: error waiting for provider components to be up and running: pods are not yet running for deployment 'capd-controller-manager' in namespace 'capd-system'`
Following the debug suggestions, everything seems to be up and healthy...
And the service is up and seems to be healthy, not even any restarts...
l0r3zz@tarnover:[2022-04-12 23:08:24]-$kubectl get pods -n capd-system --kubeconfig /home/l0r3zz/.kube-tkg/tmp/config_vupVfb7L NAME                                       READY   STATUS    RESTARTS   AGE capd-controller-manager-86b587cf4b-dmtqw   1/1     Running   0          4h59m
I was using tanzu management-cluster create --ui
I've included the debugging session and the log output for capd-controller-manager.
I'm on another mission so don't have time to try again.  But ultimately I'd like to see deploy to docker work as I have a lot of outside Vmware SRE colleagues that I would like to get them to try Tanzu, and it's important that this configuration works as none of them have vSphere clusters and most are willing to run on their laptops or towers but won't waste time debugging.
tce.txt

I did try to deploy to docker on Linux a second time and got a similar failure when it tried to bootstrap the management cluster. After the failure, I examined the management cluster and services seems up and healthy, though of course the additional plug-ins were not loaded

This won't make it for v0.12.0, unfortunately. Moving out to v0.13.0.

@jpmcb is going to attempt to reproduce with a tanzu-framework v0.11.2 build and report results here.

I'm also facing your issue and can reproduce it on a rocky-8 VM - https://gist.github.com/cmoulliard/15ef5640e8235686421e4da3797523d9


HTTP video sources despite HTTPS available

Summary
Change all references to home url in WordPress in web stories content to the current schema.
Relevant Technical Choices
All references to home url to current schema. Set the value on the model so we dont have to do it everywhere.
To-do

User-facing changes

Testing Instructions

Fixes #4928

Feels like this should rather be done on the AMP sanitization level / in Story_Renderer, not in the Model class.

In early version of this, add more of the attributes on the story model replaced with https versions. But I scaled it back. So moving this makes sense.


Opening a workspace may take long time

Actual behavior
A user keeps adding operation steps to a current workflow. Each new step is executed immediately which may take considerable compute time. When user saves workspace, then opens it again, all workflow steps are executed. The overall time to load the workspace is the sum of each operation step's execution time.
Expected behavior
Opening a workspace should be fast. Open action may be split into two phases: (1) actual open, (2) workflow execution. Execution may be accelerated by using a file cache for intermediate/final results.
Steps to reproduce
E.g. try in CLI or GUI use case 9, save it and reopen it:

keeps adding operation steps to current workflow
saves the workflow as
open workflow
==> takes long time to open, no progress shown by progress bar(!)

Specifications
0.8.0rc7.dev1

Implementation ideas
Split open action into two phases

Opening the workspace and all steps (instantaneous)
Executing the workflow (may take some time).

For the latter, show step-by-step progress and allow for cancellation. Cancellation
leave some remaining steps without resources, but that should be fine. If some other
step requires the resource, computation should be triggered automatically.
The disadvantage of this approach is that users may observe unexpected delays / unresponsive UI,
e.g. when visualizing a result. Therefore, resources should be in one of three states
NOT YET COMPUTED, COMPUTING, COMPUTED, IN ERROR. The state should be clearly indicated, e.g. in the GUI.
Options to speed up loading of resources by using a per-workspace file cache:

When saving a workspace, write out an xarray.Dataset resource named <res> from resource cache
to workspace path file resources/<res>.nc.
When opening a workspace, read in all resources/<res>.nc and put an xarray.Dataset resource
named <res> into resource cache.
Behavior may apply only to resources for which a cache property has been set to True.


[ALLUXIO-3246] Fix unit for master client thread pool keep-alive time

@gpang cherry-pick to branch-1.8
https://alluxio.atlassian.net/browse/ALLUXIO-3246

alluxio-bot, check this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/20635/
Test PASSed.


Firefox Port and Version Increase from 0.4.6 --> 0.4.7

I ported over the extension to firefox and it is working fine. I had to change some things in tippy.min.js. My suggestion is to test on chrome on your side to ensure functionality remains unharmed.

Thanks for this! It looks like you've modified the minified tippy library. Is this just a new version (if so, which?), or did you make other changes to it? Do you have a link to the original source?
I understand that submission to the mozilla add-ons store requires the actual source to be available for review, with correct version numbers and links (https://extensionworkshop.com/documentation/publish/third-party-library-usage/), so I think there are a few further changes necessary (or at least details to be researched) for a number of libraries before I can actually submit this for signing.

I am just now seeing this...I'll double check about the versioning and get back with you this weekend!