Still necessary?

Hi, I tried your patch, but then I got another error (see above).
Is this patch still necessary or are there other solutions now?
[15:33:29] I/launcher - Running 1 instances of WebDriver
[15:33:29] I/hosted - Using the selenium server at http://localhost:4723/wd/hub
[15:33:37] E/runner - Unable to start a WebDriver session.
[15:33:39] E/launcher - Error: WebDriverError: An unknown server-side error occurred while processing the command. Original error: Invalid timeout 'script'
    at Object.checkLegacyResponse (/Users/work/Projects/mswag/lbo/e2e/node_modules/selenium-webdriver/lib/error.js:505:15)
    at parseHttpResponse (/Users/work/Projects/mswag/lbo/e2e/node_modules/selenium-webdriver/lib/http.js:509:13)
    at doSend.then.response (/Users/work/Projects/mswag/lbo/e2e/node_modules/selenium-webdriver/lib/http.js:440:13)
    at process._tickCallback (internal/process/next_tick.js:109:7)
From: Task: WebDriver.manage().timeouts().setScriptTimeout(11000)
    at WebDriver.schedule (/Users/work/Projects/mswag/lbo/e2e/node_modules/selenium-webdriver/lib/webdriver.js:816:17)
    at Timeouts._scheduleCommand (/Users/work/Projects/mswag/lbo/e2e/node_modules/selenium-webdriver/lib/webdriver.js:1500:25)
    at Timeouts.setScriptTimeout (/Users/work/Projects/mswag/lbo/e2e/node_modules/selenium-webdriver/lib/webdriver.js:1483:17)
    at browser_.ready.browser_.ready.then.then (/Users/work/Projects/mswag/lbo/e2e/node_modules/protractor/lib/runner.ts:281:49)
    at ManagedPromise.invokeCallback_ (/Users/work/Projects/mswag/lbo/e2e/node_modules/selenium-webdriver/lib/promise.js:1366:14)
    at TaskQueue.execute_ (/Users/work/Projects/mswag/lbo/e2e/node_modules/selenium-webdriver/lib/promise.js:2970:14)
    at TaskQueue.executeNext_ (/Users/work/Projects/mswag/lbo/e2e/node_modules/selenium-webdriver/lib/promise.js:2953:27)
    at asyncRun (/Users/work/Projects/mswag/lbo/e2e/node_modules/selenium-webdriver/lib/promise.js:2813:27)
    at /Users/work/Projects/mswag/lbo/e2e/node_modules/selenium-webdriver/lib/promise.js:676:7
    at process._tickCallback (internal/process/next_tick.js:109:7)
Closing report
[15:33:39] E/launcher - Process exited with error code 100

Appium logs
...
[HTTP] <-- POST /wd/hub/session 200 8003 ms - 1154
[HTTP] --> POST /wd/hub/session/9bd0ec13-6078-4aee-971f-5060c7c84e73/timeouts {"type":"script","ms":11000}
[debug] [MJSONWP] Calling AppiumDriver.timeouts() with args: ["script",11000,"9bd0ec13-6078-4aee-971f-5060c7c84e73"]
[MJSONWP] Encountered internal error running command: Error: Invalid timeout 'script'
    at AndroidDriver.callee$0$0$ (../../../../lib/basedriver/commands/timeout.js:23:13)
    at tryCatch (/Users/work/.nvm/versions/node/v7.7.1/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/babel-runtime/regenerator/runtime.js:67:40)
    at GeneratorFunctionPrototype.invoke [as _invoke] (/Users/work/.nvm/versions/node/v7.7.1/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/babel-runtime/regenerator/runtime.js:315:22)
    at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (/Users/work/.nvm/versions/node/v7.7.1/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/babel-runtime/regenerator/runtime.js:100:21)
    at invoke (/Users/work/.nvm/versions/node/v7.7.1/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/babel-runtime/regenerator/runtime.js:136:37)
    at enqueueResult (/Users/work/.nvm/versions/node/v7.7.1/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/babel-runtime/regenerator/runtime.js:185:17)
    at F (/Users/work/.nvm/versions/node/v7.7.1/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/core-js/library/modules/$.export.js:30:36)
    at AsyncIterator.enqueue (/Users/work/.nvm/versions/node/v7.7.1/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/babel-runtime/regenerator/runtime.js:184:12)
    at AsyncIterator.prototype.(anonymous function) [as next] (/Users/work/.nvm/versions/node/v7.7.1/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/babel-runtime/regenerator/runtime.js:100:21)
    at Object.runtime.async (/Users/work/.nvm/versions/node/v7.7.1/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/babel-runtime/regenerator/runtime.js:209:12)
    at AndroidDriver.callee$0$0 [as timeouts] (../../../../lib/basedriver/commands/timeout.js:14:9)
    at ../../../lib/basedriver/driver.js:218:24
    at tryCatcher (/Users/work/.nvm/versions/node/v7.7.1/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/bluebird/js/main/util.js:26:23)
    at Promise._settlePromiseFromHandler (/Users/work/.nvm/versions/node/v7.7.1/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/bluebird/js/main/promise.js:510:31)
    at Promise._settlePromiseAt (/Users/work/.nvm/versions/node/v7.7.1/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/bluebird/js/main/promise.js:584:18)
    at Promise._settlePromiseAtPostResolution (/Users/work/.nvm/versions/node/v7.7.1/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/bluebird/js/main/promise.js:248:10)
    at Async._drainQueue (/Users/work/.nvm/versions/node/v7.7.1/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/bluebird/js/main/async.js:128:12)
    at Async._drainQueues (/Users/work/.nvm/versions/node/v7.7.1/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/bluebird/js/main/async.js:133:10)
    at Immediate.Async.drainQueues (/Users/work/.nvm/versions/node/v7.7.1/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/bluebird/js/main/async.js:15:14)
    at runCallback (timers.js:666:20)
    at tryOnImmediate (timers.js:639:5)
    at processImmediate [as _immediateCallback] (timers.js:611:5)
[HTTP] <-- POST /wd/hub/session/9bd0ec13-6078-4aee-971f-5060c7c84e73/timeouts 500 19 ms - 195
[HTTP] --> DELETE /wd/hub/session/9bd0ec13-6078-4aee-971f-5060c7c84e73 {}
[debug] [MJSONWP] Calling AppiumDriver.deleteSession() with args: ["9bd0ec13-6078-4aee-971f-5060c7c84e73"]
[debug] [AndroidDriver] Shutting down Android driver
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected

...

Environment infos:
$ appium --version
1.6.3

$ node -v
v7.7.1

$ protractor --version
Version 5.1.1

@mwager hi! as far as I know this patch is not compatible with Appium 1.6.x, as it was created for 1.5.3. And afaik original issue is still open: https://github.com/appium/appium/issues/4597
Unfortunately, right now I can only recommend using Appium 1.5.3 with Android and 1.6.3 with iOS (iOS works fine without patch) and wait for issue to be resolved :|

Thanks! Tried with<EMAIL_ADDRESS>but same error
[09:37:11] E/runner - Unable to start a WebDriver session.
[09:37:13] E/launcher - Error: WebDriverError: An unknown server-side error occurred while processing the command. Original error: Invalid timeout 'script'

Appium logs
[debug] [MJSONWP] Calling AppiumDriver.timeouts() with args: ["script",11000,"0fb42528-24d8-4fe3-a463-28d6e6e4d81d"]
[MJSONWP] Encountered internal error running command: Error: Invalid timeout 'script'

I think we will run the tests against the app built without crosswalk for now until the original issue was resolved.
Thanks for your patch & help anyway!

Just FYI, I've also tried your patch with Appium 1.5.3. I'm using Linux 64 (Fedora 24) so I've been using the xwalkdriver64_release from here: https://github.com/crosswalk-project/crosswalk-web-driver/tree/master/bin
Maybe I should be using a different driver? The one at http://www.megafileupload.com/fo3m/chromedriver no longer exists so unsure as to best one for x64 Linux.
Anyway, running with that xwalkdriver64_release and your patch, I end up with WebDriverException: Message: no such session
Been running around in circles with this for a while now. Proper integration of https://codereview.chromium.org/2375613002/ and any subsequent necessary fixes to Appium can't come soon enough. Thanks for patch anyway even if it doesn't work for me.
Can technically switch between contexts but when one tries to do anything (like wait for an element) in the webview then the problems start
[HTTP] --> POST /wd/hub/session {"requiredCapabilities":{},"desiredCapabilities":{"deviceName":"<IP_ADDRESS>:5555","automationName":"Appium","androidDeviceSocket":"com.companyname.AppName_devtools_remote","chromeOptions":{"androidDeviceSocket":"com.companyname.AppName_devtools_remote"},"browserName":"","platformVersion":"4.4.2","appPackage":"com.companyname.AppName","platformName":"Android","appActivity":".AppName"}}
[MJSONWP] Calling AppiumDriver.createSession() with args: [{"deviceName":"10.254.222....
[Appium] Creating new AndroidDriver session
[Appium] Capabilities:
[Appium]   deviceName: '<IP_ADDRESS>:5555'
[Appium]   automationName: 'Appium'
[Appium]   androidDeviceSocket: 'com.companyname.AppName_devtools_remote'
[Appium]   chromeOptions: { androidDeviceSocket: 'com.companyname.AppName_devtools_remote' }
[Appium]   browserName: ''
[Appium]   platformVersion: '4.4.2'
[Appium]   appPackage: 'com.companyname.AppName'
[Appium]   platformName: 'Android'
[Appium]   appActivity: '.AppName'
[BaseDriver] Session created with session id: 0becbc0d-e1b6-4c37-b72d-58570e48285f
[debug] [AndroidDriver] Getting Java version
[AndroidDriver] Java version is: 1.8.0_121
[ADB] Checking whether adb is present
[ADB] Using adb from /home/pandabat/androidSDK/platform-tools/adb
[AndroidDriver] Retrieving device list
[debug] [ADB] Trying to find a connected android device
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[AndroidDriver] Looking for a device with Android 4.4.2
[debug] [ADB] Setting device id to <IP_ADDRESS>:5555
[ADB] Getting device platform version
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /home/pandabat/androidSDK/platform-tools/adb with args: ["-P",5037,"-s","<IP_ADDRESS>:5555","shell","getprop","ro.build.version.release"]
[AndroidDriver] Using device: <IP_ADDRESS>:5555
[ADB] Checking whether adb is present
[ADB] Using adb from /home/pandabat/androidSDK/platform-tools/adb
[debug] [ADB] Setting device id to <IP_ADDRESS>:5555
[AndroidDriver] App file was not listed, instead we're going to run com.companyname.AppName directly on the device
[debug] [AndroidDriver] Checking whether package is present on the device
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /home/pandabat/androidSDK/platform-tools/adb with args: ["-P",5037,"-s","<IP_ADDRESS>:5555","shell","pm","list","packages","com.companyname.AppName"]
[AndroidDriver] Starting Android session
[debug] [ADB] Running /home/pandabat/androidSDK/platform-tools/adb with args: ["-P",5037,"-s","<IP_ADDRESS>:5555","wait-for-device"]
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /home/pandabat/androidSDK/platform-tools/adb with args: ["-P",5037,"-s","<IP_ADDRESS>:5555","shell","echo","ping"]
[debug] [Logcat] Starting logcat capture
[debug] [AndroidDriver] Pushing settings apk to device...
[debug] [ADB] Running /home/pandabat/androidSDK/platform-tools/adb with args: ["-P",5037,"-s","<IP_ADDRESS>:5555","install","/usr/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/io.appium.settings/bin/settings_apk-debug.apk"]
[debug] [AndroidDriver] Pushing unlock helper app to device...
[debug] [ADB] Running /home/pandabat/androidSDK/platform-tools/adb with args: ["-P",5037,"-s","<IP_ADDRESS>:5555","install","/usr/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/appium-unlock/bin/unlock_apk-debug.apk"]
[ADB] Getting device platform version
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /home/pandabat/androidSDK/platform-tools/adb with args: ["-P",5037,"-s","<IP_ADDRESS>:5555","shell","getprop","ro.build.version.release"]
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /home/pandabat/androidSDK/platform-tools/adb with args: ["-P",5037,"-s","<IP_ADDRESS>:5555","shell","dumpsys","window"]
[AndroidDriver] Screen already unlocked, doing nothing
[debug] [AndroidBootstrap] Watching for bootstrap disconnect
[debug] [ADB] Forwarding system: 4724 to device: 4724
[debug] [ADB] Running /home/pandabat/androidSDK/platform-tools/adb with args: ["-P",5037,"-s","<IP_ADDRESS>:5555","forward","tcp:4724","tcp:4724"]
[debug] [UiAutomator] Starting UiAutomator
[debug] [UiAutomator] Moving to state 'starting'
[debug] [UiAutomator] Parsing uiautomator jar
[debug] [UiAutomator] Found jar name: 'AppiumBootstrap.jar'
[debug] [ADB] Running /home/pandabat/androidSDK/platform-tools/adb with args: ["-P",5037,"-s","<IP_ADDRESS>:5555","push","/usr/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/appium-android-bootstrap/bootstrap/bin/AppiumBootstrap.jar","/data/local/tmp/"]
[debug] [ADB] Attempting to kill all uiautomator processes
[debug] [ADB] Getting all processes with uiautomator
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /home/pandabat/androidSDK/platform-tools/adb with args: ["-P",5037,"-s","<IP_ADDRESS>:5555","shell","ps","uiautomator"]
[ADB] No uiautomator process found to kill, continuing...
[debug] [UiAutomator] Starting UIAutomator
[debug] [ADB] Creating ADB subprocess with args: -P, 5037, -s, <IP_ADDRESS>:5555, shell, uiautomator, runtest, AppiumBootstrap.jar, -c, io.appium.android.bootstrap.Bootstrap, -e, pkg, com.companyname.AppName, -e, disableAndroidWatchers, false, -e, acceptSslCerts, false
[debug] [UiAutomator] Moving to state 'online'
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Registered crash watchers.
[AndroidBootstrap] Android bootstrap socket is now connected
[debug] [ADB] Getting connected devices...
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Client connected
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /home/pandabat/androidSDK/platform-tools/adb with args: ["-P",5037,"-s","<IP_ADDRESS>:5555","shell","getprop","ro.build.version.sdk"]
[debug] [ADB] Device API level: 19
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /home/pandabat/androidSDK/platform-tools/adb with args: ["-P",5037,"-s","<IP_ADDRESS>:5555","shell","am","start","-n","com.companyname.AppName/.AppName","-S","-a","android.intent.action.MAIN","-c","android.intent.category.LAUNCHER","-f","0x10200000"]
[Appium] New AndroidDriver session created successfully, session 0becbc0d-e1b6-4c37-b72d-58570e48285f added to master session list
[MJSONWP] Responding to client with driver.createSession() result: {"platform":"LINUX","webSto...
[HTTP] <-- POST /wd/hub/session 200 6927 ms - 972
[HTTP] --> GET /wd/hub/session/0becbc0d-e1b6-4c37-b72d-58570e48285f/contexts {}
[MJSONWP] Calling AppiumDriver.getContexts() with args: ["0becbc0d-e1b6-4c37-b72d-5...
[debug] [AndroidDriver] Getting a list of available webviews
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /home/pandabat/androidSDK/platform-tools/adb with args: ["-P",5037,"-s","<IP_ADDRESS>:5555","shell","cat","/proc/net/unix"]
[debug] [AndroidDriver] Available contexts: ["NATIVE_APP","CHROMIUM"]
[MJSONWP] Responding to client with driver.getContexts() result: ["NATIVE_APP","CHROMIUM"]
[HTTP] <-- GET /wd/hub/session/0becbc0d-e1b6-4c37-b72d-58570e48285f/contexts 200 103 ms - 97
[HTTP] --> GET /wd/hub/session/0becbc0d-e1b6-4c37-b72d-58570e48285f/contexts {}
[MJSONWP] Calling AppiumDriver.getContexts() with args: ["0becbc0d-e1b6-4c37-b72d-5...
[debug] [AndroidDriver] Getting a list of available webviews
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /home/pandabat/androidSDK/platform-tools/adb with args: ["-P",5037,"-s","<IP_ADDRESS>:5555","shell","cat","/proc/net/unix"]
[debug] [AndroidDriver] Available contexts: ["NATIVE_APP","CHROMIUM"]
[MJSONWP] Responding to client with driver.getContexts() result: ["NATIVE_APP","CHROMIUM"]
[HTTP] <-- GET /wd/hub/session/0becbc0d-e1b6-4c37-b72d-58570e48285f/contexts 200 100 ms - 97
[HTTP] --> POST /wd/hub/session/0becbc0d-e1b6-4c37-b72d-58570e48285f/context {"sessionId":"0becbc0d-e1b6-4c37-b72d-58570e48285f","name":"CHROMIUM"}
[MJSONWP] Calling AppiumDriver.setContext() with args: ["CHROMIUM","0becbc0d-e1b6-...
[debug] [AndroidDriver] Getting a list of available webviews
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /home/pandabat/androidSDK/platform-tools/adb with args: ["-P",5037,"-s","<IP_ADDRESS>:5555","shell","cat","/proc/net/unix"]
[debug] [AndroidDriver] Available contexts: ["NATIVE_APP","CHROMIUM"]
[debug] [AndroidDriver] Connecting to chrome-backed webview context 'CHROMIUM'
[debug] [Chromedriver] Changed state to 'starting'
[Chromedriver] Set chromedriver binary as: /usr/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/appium-chromedriver/chromedriver/linux/chromedriver_64
[Chromedriver] Killing any old chromedrivers, running: pkill -15 -f "/usr/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/appium-chromedriver/chromedriver/linux/chromedriver_64.*--port=9515"
[Chromedriver] No old chromedrivers seemed to exist
[Chromedriver] Spawning chromedriver with: /usr/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/appium-chromedriver/chromedriver/linux/chromedriver_64 --url-base=wd/hub --port=9515 --adb-port=5037
[Chromedriver] [STDOUT] Starting XwalkDriver (v2.5.ede663c5c5362a073e538cdabacf85612bc9e16a) on port 9515
Only local connections are allowed.
[debug] [JSONWP Proxy] Proxying [GET /status] to [GET http://<IP_ADDRESS>:9515/wd/hub/status] with no body
[debug] [JSONWP Proxy] Got response with status 200: "{"sessionId":"","status":0,"value":{"build":{"version":"alpha"},"os":{"arch":"x86_64","name":"Linux","version":"4.9.15-100.fc24.x86_64+debug"}}}"
[debug] [JSONWP Proxy] Proxying [POST /session] to [POST http://<IP_ADDRESS>:9515/wd/hub/session] with body: {"desiredCapabilities":{"chromeOptions":{"androidPackage":"com.companyname.AppName","androidUseRunningApp":true,"androidDeviceSocket":"com.companyname.AppName_devtools_remote","androidDeviceSerial":"<IP_ADDRESS>:5555"}}}
[debug] [JSONWP Proxy] Got response with status 200: {"sessionId":"6e3a1e589ed82da3d6323663d61564e5","status":13,"value":{"message":"unknown error: cannot find xwalk binary\n  (Driver info: xwalkdriver=2.5.ede663c5c5362a073e538cdabacf85612bc9e16a,platform=Linux 4.9.15-100.fc24.x86_64+debug x86_64)"}}
[debug] [Chromedriver] Changed state to 'online'
[MJSONWP] Responding to client with driver.setContext() result: null
[HTTP] <-- POST /wd/hub/session/0becbc0d-e1b6-4c37-b72d-58570e48285f/context 200 341 ms - 76
[HTTP] --> POST /wd/hub/session/0becbc0d-e1b6-4c37-b72d-58570e48285f/elements {"using":"css selector","sessionId":"0becbc0d-e1b6-4c37-b72d-58570e48285f","value":"#home-menu"}
[MJSONWP] Driver proxy active, passing request on via HTTP proxy
[debug] [JSONWP Proxy] Proxying [POST /wd/hub/session/0becbc0d-e1b6-4c37-b72d-58570e48285f/elements] to [POST http://<IP_ADDRESS>:9515/wd/hub/session/6e3a1e589ed82da3d6323663d61564e5/elements] with body: {"using":"css selector","sessionId":"0becbc0d-e1b6-4c37-b72d-58570e48285f","value":"#home-menu"}
[debug] [JSONWP Proxy] Got response with status 200: {"sessionId":"6e3a1e589ed82da3d6323663d61564e5","status":6,"value":{"message":"no such session\n  (Driver info: xwalkdriver=2.5.ede663c5c5362a073e538cdabacf85612bc9e16a,platform=Linux 4.9.15-100.fc24.x86_64+debug x86_64)"}}
[JSONWP Proxy] Replacing sessionId 6e3a1e589ed82da3d6323663d61564e5 with 0becbc0d-e1b6-4c37-b72d-58570e48285f
[HTTP] <-- POST /wd/hub/session/0becbc0d-e1b6-4c37-b72d-58570e48285f/elements 200 10 ms - 227
[HTTP] --> GET /wd/hub/session/0becbc0d-e1b6-4c37-b72d-58570e48285f/context {}
[MJSONWP] Calling AppiumDriver.getCurrentContext() with args: ["0becbc0d-e1b6-4c37-b72d-5...
[MJSONWP] Responding to client with driver.getCurrentContext() result: "CHROMIUM"
[HTTP] <-- GET /wd/hub/session/0becbc0d-e1b6-4c37-b72d-58570e48285f/context 200 4 ms - 82
[HTTP] --> POST /wd/hub/session/0becbc0d-e1b6-4c37-b72d-58570e48285f/context {"sessionId":"0becbc0d-e1b6-4c37-b72d-58570e48285f","name":"NATIVE_APP"}
[MJSONWP] Calling AppiumDriver.setContext() with args: ["NATIVE_APP","0becbc0d-e1b...
[debug] [AndroidDriver] Getting a list of available webviews
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /home/pandabat/androidSDK/platform-tools/adb with args: ["-P",5037,"-s","<IP_ADDRESS>:5555","shell","cat","/proc/net/unix"]
[debug] [AndroidDriver] Available contexts: ["NATIVE_APP","CHROMIUM"]
[MJSONWP] Responding to client with driver.setContext() result: null
[HTTP] <-- POST /wd/hub/session/0becbc0d-e1b6-4c37-b72d-58570e48285f/context 200 99 ms - 76
[HTTP] --> GET /wd/hub/session/0becbc0d-e1b6-4c37-b72d-58570e48285f/screenshot {}
[MJSONWP] Calling AppiumDriver.getScreenshot() with args: ["0becbc0d-e1b6-4c37-b72d-5...
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /home/pandabat/androidSDK/platform-tools/adb with args: ["-P",5037,"-s","<IP_ADDRESS>:5555","shell","/system/bin/rm","/data/local/tmp/screenshot.png;","/system/bin/screencap","-p","/data/local/tmp/screenshot.png"]
[debug] [ADB] Running /home/pandabat/androidSDK/platform-tools/adb with args: ["-P",5037,"-s","<IP_ADDRESS>:5555","pull","/data/local/tmp/screenshot.png","/tmp/appium117223-15948-1lgn4qy.png"]
[MJSONWP] Responding to client with driver.getScreenshot() result: "iVBORw0KGgoAAAANSUhEUgAAB4...
[HTTP] <-- GET /wd/hub/session/0becbc0d-e1b6-4c37-b72d-58570e48285f/screenshot 200 4820 ms - 1923826
[HTTP] --> POST /wd/hub/session/0becbc0d-e1b6-4c37-b72d-58570e48285f/context {"sessionId":"0becbc0d-e1b6-4c37-b72d-58570e48285f","name":"CHROMIUM"}
[MJSONWP] Calling AppiumDriver.setContext() with args: ["CHROMIUM","0becbc0d-e1b6-...
[debug] [AndroidDriver] Getting a list of available webviews
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /home/pandabat/androidSDK/platform-tools/adb with args: ["-P",5037,"-s","<IP_ADDRESS>:5555","shell","cat","/proc/net/unix"]
[debug] [AndroidDriver] Available contexts: ["NATIVE_APP","CHROMIUM"]
[debug] [AndroidDriver] Connecting to chrome-backed webview context 'CHROMIUM'
[debug] [AndroidDriver] Found existing Chromedriver for context 'CHROMIUM'. Using it.
[debug] [JSONWP Proxy] Proxying [GET /url] to [GET http://<IP_ADDRESS>:9515/wd/hub/session/6e3a1e589ed82da3d6323663d61564e5/url] with no body
[debug] [JSONWP Proxy] Got response with status 200: "{"sessionId":"6e3a1e589ed82da3d6323663d61564e5","status":6,"value":{"message":"no such session\n  (Driver info: xwalkdriver=2.5.ede663c5c5362a073e538cdabacf85612bc9e16a,platform=Linux 4.9.15-100.fc24.x86_64+debug x86_64)"}}"
[MJSONWP] Responding to client with driver.setContext() result: null
[HTTP] <-- POST /wd/hub/session/0becbc0d-e1b6-4c37-b72d-58570e48285f/context 200 105 ms - 76
[HTTP] --> POST /wd/hub/session/0becbc0d-e1b6-4c37-b72d-58570e48285f/context {"sessionId":"0becbc0d-e1b6-4c37-b72d-58570e48285f","name":"CHROMIUM"}
[MJSONWP] Calling AppiumDriver.setContext() with args: ["CHROMIUM","0becbc0d-e1b6-...
[debug] [AndroidDriver] Getting a list of available webviews
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /home/pandabat/androidSDK/platform-tools/adb with args: ["-P",5037,"-s","<IP_ADDRESS>:5555","shell","cat","/proc/net/unix"]
[debug] [AndroidDriver] Available contexts: ["NATIVE_APP","CHROMIUM"]
[MJSONWP] Responding to client with driver.setContext() result: null
[HTTP] <-- POST /wd/hub/session/0becbc0d-e1b6-4c37-b72d-58570e48285f/context 200 98 ms - 76
[HTTP] --> POST /wd/hub/session/0becbc0d-e1b6-4c37-b72d-58570e48285f/elements {"using":"css selector","sessionId":"0becbc0d-e1b6-4c37-b72d-58570e48285f","value":"#home-time > h1:nth-child(1)"}
[MJSONWP] Driver proxy active, passing request on via HTTP proxy
[debug] [JSONWP Proxy] Proxying [POST /wd/hub/session/0becbc0d-e1b6-4c37-b72d-58570e48285f/elements] to [POST http://<IP_ADDRESS>:9515/wd/hub/session/6e3a1e589ed82da3d6323663d61564e5/elements] with body: {"using":"css selector","sessionId":"0becbc0d-e1b6-4c37-b72d-58570e48285f","value":"#home-time > h1:nth-child(1)"}
[debug] [JSONWP Proxy] Got response with status 200: {"sessionId":"6e3a1e589ed82da3d6323663d61564e5","status":6,"value":{"message":"no such session\n  (Driver info: xwalkdriver=2.5.ede663c5c5362a073e538cdabacf85612bc9e16a,platform=Linux 4.9.15-100.fc24.x86_64+debug x86_64)"}}
[JSONWP Proxy] Replacing sessionId 6e3a1e589ed82da3d6323663d61564e5 with 0becbc0d-e1b6-4c37-b72d-58570e48285f

@pandabat I had this kind of issue ("no such session") when I used un-patched chromedriver
that's unfortunately that patched chromedriver is no longer available, you might want to try and build it yourself, here you can find instructions: https://github.com/piotrekkmt/chromedriver-appium
but I'm not sure how up to date those instructions are

I'm going to try to build it - not sure how it will work out though. Bravely onward! :) THanks

I did build a patched chromedriver myself and it seems to be fairly successful although I think that I have my Appium doctored with your patch so I'm not sure if it works with stock Appium. I'm not going to be able to check that until next week at the earliest. I built on Fedora 24 x64 and this is the rough path that I followed in case it is of use to anyone:
https://sites.google.com/a/chromium.org/chromedriver/contributing
https://chromium.googlesource.com/chromium/src/+/master/docs/linux_build_instructions.md#Build-Chromium     (****FOLLOW THESE ***)
sudo dnf install git python bzip2 tar pkgconfig atk-devel alsa-lib-devel bison binutils brlapi-devel bluez-libs-devel bzip2-devel cairo-devel cups-devel dbus-devel dbus-glib-devel expat-devel fontconfig-devel freetype-devel gcc-c++ GConf2-devel glib2-devel glibc.i686 gperf glib2-devel gtk2-devel gtk3-devel java-1.*.0-openjdk-devel libatomic libcap-devel libffi-devel libgcc.i686 libgnome-keyring-devel libjpeg-devel libstdc++.i686 libX11-devel libXScrnSaver-devel libXtst-devel libxkbcommon-x11-devel ncurses-compat-libs nspr-devel nss-devel pam-devel pango-devel pciutils-devel pulseaudio-libs-devel zlib.i686 httpd mod_ssl php php-cli python-psutil wdiff xfs
Also do these: http://www.fedorafaq.org/#installfonts
https://codereview.chromium.org/2375613002/#ps80001   (*** THEN APPLY THESE as below *** to fix https://bugs.chromium.org/p/chromedriver/issues/detail?id=749)
cp chrome/test/chromedriver/chrome/adb.h chrome/test/chromedriver/chrome/adb.h.bak
patch chrome/test/chromedriver/chrome/adb.h ~/Downloads/chromedriver_patches/issue2375613002_60001_70002.diff
cp  chrome/test/chromedriver/chrome/adb_impl.h  chrome/test/chromedriver/chrome/adb_impl.h.bak
patch  chrome/test/chromedriver/chrome/adb_impl.h ~/Downloads/chromedriver_patches/issue2375613002_60001_70004.diff
cp  chrome/test/chromedriver/chrome/adb_impl.cc  chrome/test/chromedriver/chrome/adb_impl.cc.bak
patch  chrome/test/chromedriver/chrome/adb_impl.cc ~/Downloads/chromedriver_patches/issue2375613002_60001_70003.diff
cp  chrome/test/chromedriver/chrome/device_manager.cc  chrome/test/chromedriver/chrome/device_manager.cc.bak
patch  chrome/test/chromedriver/chrome/device_manager.cc ~/Downloads/chromedriver_patches/issue2375613002_60001_70005.diff
cp  chrome/test/chromedriver/chrome/device_manager_unittest.cc  chrome/test/chromedriver/chrome/device_manager_unittest.cc.bak
patch  chrome/test/chromedriver/chrome/device_manager_unittest.cc ~/Downloads/chromedriver_patches/issue2375613002_60001_70006.diff
/***Change build to non-component, non-debug build (so no extra linked libraries hanging around & size is reduced due to lack of debug) ***/
run
'gn args out/Default'
and add lines to resulting file that appears, save and exit:
is_debug = false
is_component_build = false
symbol_level = 0
/**** compile/build chromedriver ***/
ninja -C out/Default chrome/test/chromedriver:chromedriver
Find output file at out/Default/chromedriver
Run appium/robot - note that some previous patches required "&{chromeOptions}= Create Dictionary	androidDeviceSocket=com.lincor.medialinc_devtools_remote" line and the dictionary be added to chrome launch options. This is NOT required now

This is the patched 2.28 that seems to work for me on Fedora 24 x64
https://www.dropbox.com/s/605wm68iamhisqf/chromedriver_64_2.28_patched_xwalk?dl=0

@pandabat thanks for the info!

I might want to try and update patch to support 1.6.x once https://github.com/appium/appium-desktop is released

Hi all,
My apologies for hijacking this old thread.
Do you guys know if this is still the current status? We've been trying to automate an app based on  cordova-plugin-crosswalk-webview 2.4.0, and when switching to WebView we were getting the same error (with older Appium/ChromeDriver versions) and a different one (Failed to start Chromedriver session: An unknown server-side error occurred while processing the command. (Original error: unknown error: Failed to get sockets matching: @webview_devtools_remote_.*3952  (make sure the app has its WebView configured for debugging).
The only thing very much related to what we have is this repo and the Appium issues that link to it. So is compiling our own ChromeDriver version with the fix still the solution?

hi @diemol,
As of right now, Appium has fixed issued on its side, but ChromeDriver part is still "in review"
See: https://github.com/appium/appium/issues/4597 and https://github.com/appium/appium-android-driver/pull/238
Patched version of ChromeDriver you can find here: https://github.com/blutter/appium-crosswalk-fix (binaries for macOS and Win).
I tested this binaries on macOS with Appium 1.7.2 and it seems to work just fine!

Closing this issue. Patch for Appium is no longer needed (starting from 1.6.x), but patched ChomeDriver is still must. You can find links to patched ChromeDriver binaries for macOS and Windows in the comment above

Chromedriver 2.38 patched for Linux x64 (built on Fedora 27 x64)
https://www.dropbox.com/s/9aaw8dsg913an13/chromedriver_64_2.38_patched_xwalk?dl=0
Seems to work well enough for us. Would be nice to have a properly integrated and supported fix on the Chromedriver side but, seeing as crosswalk usage is probably in decline these days, I'm not sure that that will ever happen

Thanks @pandabat !
Unfortunately, CrossWalk is not only in decline, but CrossWalk Project itself is closed and no longer supported - https://crosswalk-project.org/blog/crosswalk-final-release.html

@letsrokk @pandabat  thanks a lot for the quick answer, this is really helpful!
I was not aware that CrossWalk is closed, that is a great input for us. We are helping a customer stuck in their automation precisely because of this issue, so it also makes sense that they take another approach to build their app.

@letsrokk, nevertheless, do you have a link to track the "but ChromeDriver part is still "in review"" part?
Again, thanks for your help.

@diemol here you can find proposed fix for ChromeDriver https://codereview.chromium.org/2375613002/

Hi all,
Just dropping by to thank you for all the help and sharing my findings since we had to recompile ChromeDriver 2.40 for a customer that is still using CrossWalk (but soon will move out of it).
Current patch that worked for us (in case someone is in the same situation):
diff --git a/chrome/test/chromedriver/chrome/device_manager.cc b/chrome/test/chromedriver/chrome/device_manager.cc
index 2558656d74..d8713d9859 100644
--- a/chrome/test/chromedriver/chrome/device_manager.cc
+++ b/chrome/test/chromedriver/chrome/device_manager.cc
@@ -159,10 +159,20 @@ Status Device::ForwardDevtoolsPort(const std::string& package,
     status = adb_->GetSocketByPattern(serial_, pattern, &socket_name);
     if (status.IsError()) {
       if (socket_name.empty())
+        LOG(WARNING) << "Webview with requited pattern webview_devtools_remote_ not found.";
+    }
+    LOG(WARNING) << "Will try to find a CrossWalk webview...";
+    std::string crosswalk_pattern =
+        base::StringPrintf("@%s_devtools_remote", package.c_str());
+    status = adb_->GetSocketByPattern(serial_, crosswalk_pattern, &socket_name);
+    if (status.IsError()) {
+      if (socket_name.empty()) {
         status.AddDetails(
             "make sure the app has its WebView configured for debugging");
+      }
       return status;
     }
+
     // When used in adb with "localabstract:", the leading '@' is not needed.
     *device_socket = socket_name.substr(1);
   }
diff --git a/chrome/test/chromedriver/chrome/navigation_tracker.cc b/chrome/test/chromedriver/chrome/navigation_tracker.cc
index b4c5b00ad3..7ba1ce3aa2 100644
--- a/chrome/test/chromedriver/chrome/navigation_tracker.cc
+++ b/chrome/test/chromedriver/chrome/navigation_tracker.cc
@@ -320,10 +320,10 @@ Status NavigationTracker::OnEvent(DevToolsClient* client,
     if (!params.GetInteger("context.id", &execution_context_id))
       return Status(kUnknownError, "missing or invalid 'context.id'");
     std::string frame_id;
-    if (!params.GetString("context.auxData.frameId", &frame_id)) {
-      return Status(kUnknownError,
-                    "missing or invalid 'context.auxData.frameId'");
-    }
+//    if (!params.GetString("context.auxData.frameId", &frame_id)) {
+//      return Status(kUnknownError,
+//                    "missing or invalid 'context.auxData.frameId'");
+//    }
     if (frame_id == dummy_frame_id_)
       dummy_execution_context_id_ = execution_context_id;
     else

and a Dockerfile to recompile ChromeDriver based on that patch, a binary for Linux is generated but the same principle can be followed for OSX and Windows
FROM ubuntu:16.04

# Install Chromium build dependencies.
RUN echo "deb http://archive.ubuntu.com/ubuntu trusty multiverse" >> /etc/apt/sources.list # && dpkg --add-architecture i386
RUN apt-get update && apt-get install -qy git build-essential clang curl lsb-release sudo

# Install Chromium's depot_tools.
ENV DEPOT_TOOLS /usr/bin/depot_tools
RUN git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git $DEPOT_TOOLS
ENV PATH $PATH:$DEPOT_TOOLS
RUN echo -e "\n# Add Chromium's depot_tools to the PATH." >> .bashrc
RUN echo "export PATH=\"\$PATH:$DEPOT_TOOLS\"" >> .bashrc

RUN git config --global https.postBuffer<PHONE_NUMBER>

# Download Chromium sources.
RUN fetch --nohooks --no-history chromium

WORKDIR /

RUN gclient runhooks

WORKDIR src

RUN build/install-build-deps.sh --no-prompt

COPY crosswalk.patch crosswalk.patch
RUN git apply crosswalk.patch

RUN gn gen out/Release --args="is_debug=false"
RUN ninja -C out/Release chromedriver

RUN cp out/Release/chromedriver /usr/bin/chromedriver
RUN /usr/bin/chromedriver --version

WORKDIR /

@diemol thank you very much, this is really helpful! I'll add it to repo description


ERR_SEND_MSG_TIMEOUT send message timeout, conversationId: R:10696051448037197

Please make sure you have read the Wechaty Puppet Service: Donut from Wechaty Official Website before you continue writting this issue.
Question
ERR_SEND_MSG_TIMEOUT send message timeout, conversationId: R:10696051448037197

duplicate with #115


If the message to sign is very long for personal_sign, it isn't displayed correctly

Test: https://danfinlay.github.io/js-eth-personal-sign-examples/

@hboon can u send a screenshot with wrong displaying.
i took string from https://danfinlay.github.io/js-eth-personal-sign-examples/ and seems like it displays normal.

@hboon can u send a screenshot with wrong displaying.
i took string from https://danfinlay.github.io/js-eth-personal-sign-examples/ and seems like it displays normal.

@ how can i reproduce this issue?

@ how can i reproduce this issue?

Strange. When I tap "personal_sign" in https://danfinlay.github.io/js-eth-personal-sign-examples/, after a few seconds (which is strange too), I see this (master/3bf7e2794c1820d0dad4383cac1c4eb1e4604f90, iOS 12.4 iPhone X simulator):

Strange. When I tap "personal_sign" in https://danfinlay.github.io/js-eth-personal-sign-examples/, after a few seconds (which is strange too), I see this (master/3bf7e2794c1820d0dad4383cac1c4eb1e4604f90, iOS 12.4 iPhone X simulator):

@hboon hey, maybe i did something wrong, but when i tap personal_sign nothing happens for me

@hboon hey, maybe i did something wrong, but when i tap personal_sign nothing happens for me

It seems to take very long to appear. If you wait for say, a minute, does it?

It seems to take very long to appear. If you wait for say, a minute, does it?

It seems to take very long to appear. If you wait for say, a minute, does it?

it asks to connect with using MetaMask, does it right? and after i succesfully connect with MetaMask, nothing happenswhen i tap on personal_sign

It seems to take very long to appear. If you wait for say, a minute, does it?

it asks to connect with using MetaMask, does it right? and after i succesfully connect with MetaMask, nothing happenswhen i tap on personal_sign

Oh. I mean to load this URL and test it in the dapp browser. But it should work with MetaMask too (look at who wrote it :))

Oh. I mean to load this URL and test it in the dapp browser. But it should work with MetaMask too (look at who wrote it :))

oh, thanks a lot;)
i followed these steps, and for some time application get freezed

oh, thanks a lot;)
i followed these steps, and for some time application get freezed

right after that i received this

right after that i received this

@vladyslav-iosdev  How did you reproduce the issue? Or why were you able to get the message to display earlier?

@vladyslav-iosdev  How did you reproduce the issue? Or why were you able to get the message to display earlier?


Should this project still be working?

I've been trying to get this library working, but no matter what I always get an empty array ([]) as the result, even though json.Marshal works just fine.
Usage between colorjson.Marshal and json.Marshal is identical, and there are no errors, so I'm not sure what's up.

Never mind, looks like I skipped an important step (map[string]interface{}), my bad!


sourcing STM32F030K6T6

Are there any requirements for the type of STM32F being used?
Availability of these chips is still bad. From what I can see, it needs to support the SPI bus and be in 32-LQFP footprint?

Yeah the availability of those chips is still very low, and cost has gone way up, that's why I'm not doing a production run right now.
Anyway, it has to support SPI, in LQFP32, and also has hardware timer PWM output on all cathode pins for smooth dimming. So I STM32F042K6T6 / K4T6 are pretty much the only option. You can also try QFN32 variants, but that would require redesigning the circuit board a bit.


aarch64: correctly pass f32/f64 stack arguments in function calls

Thanks to a particularly argument-heavy Spidermonkey test case, I noticed that f32/f64 stack arguments were incorrectly passed as GPR. Here's a fix.
@cfallin, PTAL.

(Fixes one item in #1519)

Update: the other issue (pre-existing bug) was fixed in your other PR, #1530, as you pointed out. Will resolve :-)


Instructions slightly incorrect for macOS / zsh

macOS Monterey 12.6.1
After brew install:
 % op --version
zsh: command not found: op

I got this same message. I have a New MacBook Pro M1. I've also NEVER used Terminal. Help!?


Meta-feature extractor crashes

This happens for dataset 40499:
{"error":"Quality does not exists: Data quality: Quartile1StdDevOfNumericAtts. Legal Data Qualities: AutoCorrelation, CfsSubsetEval_DecisionStumpAUC, CfsSubsetEval_DecisionStumpErrRate
This makes the extractor crash, and no metafeatures are stored

Added high priority since this seems to affect multiple of the Study 14 datasets


BirdClassifierTest.test_compile_tflite failing in regression tests

https://github.com/google/iree-samples/runs/6727972570?check_suite_focus=true
[  FAILED  ] BirdClassifierTest.test_compile_tflite
======================================================================
FAIL: test_compile_tflite (__main__.BirdClassifierTest)
BirdClassifierTest.test_compile_tflite
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/runner/work/iree-samples/iree-samples/tflitehub/bird_classifier_test.py", line 31, in test_compile_tflite
    self.compile_and_execute()
  File "/home/runner/work/iree-samples/iree-samples/tflitehub/test_util.py", line 1[47](https://github.com/google/iree-samples/runs/6727972570?check_suite_focus=true#step:6:48), in compile_and_execute
    self.compare_results(iree_results, tflite_results, self.output_details)
  File "/home/runner/work/iree-samples/iree-samples/tflitehub/bird_classifier_test.py", line 18, in compare_results
    self.assertTrue(numpy.isclose(iree_results[0], tflite_results[0], atol=1e-3).all())
AssertionError: False is not true

So this is regression in numerical accuracy?

These seem to both be failing since https://github.com/google/iree-samples/commit/38b0bd37f419ad23d07e859e6c217dd8d0ea48c7 (not necessarily related, just when test was run where it failed)

Oh sorry, misread. Failing at
iree-compiler==20220516.140
iree-runtime==20220516.140
iree-tools-tf==20220516.140
iree-tools-tflite==20220516.140
iree-tools-xla==20220516.140
tensorflow==2.9.0
tensorflow-estimator==2.9.0
tensorflow-io-gcs-filesystem==0.25.0
Passing before
iree-compiler==20220516.140
iree-runtime==20220516.140
iree-tools-tf==20220516.140
iree-tools-tflite==20220516.140
iree-tools-xla==20220516.140
tensorflow==2.8.0
tensorflow-io-gcs-filesystem==0.25.0


Netty SSL Handler does not fail the SSL handshake even if the certificate is expired

Expected behavior
SSL handshake should fail if the certificate is expired.
Steps to reproduce
I have a client which uses netty SSL handler. I have used this site to test my SSL client.
https://badssl.com/
I tested it with the HttpSnoopClient which is given as an HTTP example client in Netty. I exported the certificate of https://expired.badssl.com/ and used it for building the SslContext.
Minimal yet complete reproducer code (or URL to code)
SnoopClient class
package io.netty.example.http.snoop;

import io.netty.bootstrap.Bootstrap;
import io.netty.channel.Channel;
import io.netty.channel.EventLoopGroup;
import io.netty.channel.nio.NioEventLoopGroup;
import io.netty.channel.socket.nio.NioSocketChannel;
import io.netty.handler.codec.http.DefaultFullHttpRequest;
import io.netty.handler.codec.http.HttpHeaderNames;
import io.netty.handler.codec.http.HttpHeaderValues;
import io.netty.handler.codec.http.HttpMethod;
import io.netty.handler.codec.http.HttpRequest;
import io.netty.handler.codec.http.HttpVersion;
import io.netty.handler.codec.http.cookie.ClientCookieEncoder;
import io.netty.handler.codec.http.cookie.DefaultCookie;
import io.netty.handler.ssl.SslContext;
import io.netty.handler.ssl.SslContextBuilder;

import java.io.File;
import java.net.URI;

/**
 * A simple HTTP client that prints out the content of the HTTP response to
 * {@link System#out} to test {@link HttpSnoopServer}.
 */
public final class HttpSnoopClient {

    static final String URL = System.getProperty("url", "https://expired.badssl.com/");

    public static void main(String[] args) throws Exception {
        URI uri = new URI(URL);
        String scheme = uri.getScheme() == null? "http" : uri.getScheme();
        String host = uri.getHost() == null? "<IP_ADDRESS>" : uri.getHost();
        int port = uri.getPort();
        if (port == -1) {
            if ("http".equalsIgnoreCase(scheme)) {
                port = 80;
            } else if ("https".equalsIgnoreCase(scheme)) {
                port = 443;
            }
        }

        if (!"http".equalsIgnoreCase(scheme) && !"https".equalsIgnoreCase(scheme)) {
            System.err.println("Only HTTP(S) is supported.");
            return;
        }

        // Configure SSL context if necessary.
        final boolean ssl = "https".equalsIgnoreCase(scheme);
        final SslContext sslCtx;
        if (ssl) {
            // This is the certificate of the https://expired.badssl.com/. I exported it from the site.
            File certificate =  new File("/home/bhashinee/Documents/expiredCert/_.badssl.com");
            sslCtx = SslContextBuilder.forClient().trustManager(certificate).build();
        } else {
            sslCtx = null;
        }

        // Configure the client.
        EventLoopGroup group = new NioEventLoopGroup();
        try {
            Bootstrap b = new Bootstrap();
            b.group(group)
             .channel(NioSocketChannel.class)
             .handler(new HttpSnoopClientInitializer(sslCtx));

            // Make the connection attempt.
            Channel ch = b.connect(host, port).sync().channel();

            // Prepare the HTTP request.
            HttpRequest request = new DefaultFullHttpRequest(
                    HttpVersion.HTTP_1_1, HttpMethod.GET, uri.getRawPath());
            request.headers().set(HttpHeaderNames.HOST, host);
            request.headers().set(HttpHeaderNames.CONNECTION, HttpHeaderValues.CLOSE);
            request.headers().set(HttpHeaderNames.ACCEPT_ENCODING, HttpHeaderValues.GZIP);

            // Set some example cookies.
            request.headers().set(
                    HttpHeaderNames.COOKIE,
                    ClientCookieEncoder.STRICT.encode(
                            new DefaultCookie("my-cookie", "foo"),
                            new DefaultCookie("another-cookie", "bar")));

            // Send the HTTP request.
            ch.writeAndFlush(request);

            // Wait for the server to close the connection.
            ch.closeFuture().sync();
        } finally {
            // Shut down executor threads to exit.
            group.shutdownGracefully();
        }
    }
}

HttpSnoopClientInitializer class
package io.netty.example.http.snoop;

import io.netty.channel.ChannelInitializer;
import io.netty.channel.ChannelPipeline;
import io.netty.channel.socket.SocketChannel;
import io.netty.handler.codec.http.HttpClientCodec;
import io.netty.handler.codec.http.HttpContentDecompressor;
import io.netty.handler.ssl.SslContext;
import io.netty.handler.ssl.SslHandler;

public class HttpSnoopClientInitializer extends ChannelInitializer<SocketChannel> {

    private final SslContext sslCtx;

    public HttpSnoopClientInitializer(SslContext sslCtx) {
        this.sslCtx = sslCtx;
    }

    @Override
    public void initChannel(SocketChannel ch) {
        ChannelPipeline p = ch.pipeline();

        // Enable HTTPS if necessary.
        if (sslCtx != null) {
            SslHandler sslHandler = sslCtx.newHandler(ch.alloc(), "expired.badssl.com", 443);
            p.addLast("ssl", sslHandler);
        }

        p.addLast(new HttpClientCodec());

        // Remove the following line if you don't want automatic content decompression.
        p.addLast(new HttpContentDecompressor());

        // Uncomment the following line if you don't want to handle HttpContents.
        //p.addLast(new HttpObjectAggregator(1048576));

        p.addLast(new HttpSnoopClientHandler());
    }
}

Netty version
4.1.19.Final
JVM version (e.g. java -version)
1.8
OS version (e.g. uname -a)
Ubuntu
This is the same issue I reported in https://github.com/netty/netty/issues/8455. Creating another one as I cannot re-open it.

What happens if you change
sslCtx = SslContextBuilder.forClient().trustManager(certificate).build();

... to ...
sslCtx = SslContextBuilder.forClient().build();

Conceptually though, an expired certificate doesn't mean it can no longer be used. It only means that it cannot be implicitly trusted and it boils down to business logic how you want to handle it. Same deal as with self-signed certificates et al.

@Bhashinee just implement your own TrustManagerFactory or not specify the cert when building ? Doesn't sslCtx = SslContextBuilder.forClient().build() give you exactly what you are asking for ?

@normanmaurer  @rkapsi  Thank you very much for the information. :)
I was looking for a way to achieve that with a given certificate so that the SSL handshake will only happen if the given certificate is valid.

Like I said you can implement your own TrustManagerFactory if you need a custom behaviour.


multi-line highlight problem?

example:
<#assign map = {
   "A" : "1" ,
   "B" : "2" ,
   "C" : "3" ,
    "D" : "4" }
/>
sorry, my English is not good ：）

Thanks for submitting your issue. I'll start working on it as soon as I can.


Duplicates were removed but log says 0 dups removed

Hi @GregoryFaust
We are executing samblaster 0.1.26  using below command
samblaster_0.1.26.simg samblaster --ignoreUnmated  -a -r -i input.sam -o output.sam

samblaster log
samblaster: Version 0.1.26
samblaster: Opening input.sam for read.
samblaster: Opening output.sam for write.
samblaster: Loaded 25 header sequence entries.
samblaster: Found        62867 of    2402373 (2.617%) total read ids are marked paired yet are unmated.
samblaster: Please double check that input file is read-id (QNAME) grouped.
samblaster: Found          838 of    2402373 (0.035%) total read ids with no primary alignment.
samblaster: Please double check that input file is read-id (QNAME) grouped.
samblaster: Removed          0 of    2402373 (0.000%) total read ids as duplicates using 18128k memory in 1.911S CPU seconds and 3S wall time.

Flagstats of input sam
4744272 + 0 in total (QC-passed reads + QC-failed reads)
4423 + 0 secondary
0 + 0 supplementary
2178640 + 0 duplicates
4743484 + 0 mapped (99.98% : N/A)
4739849 + 0 paired in sequencing
2372230 + 0 read1
2367619 + 0 read2
4724503 + 0 properly paired (99.68% : N/A)
4737919 + 0 with itself and mate mapped
1142 + 0 singletons (0.02% : N/A)
3131 + 0 with mate mapped to a different chr
3064 + 0 with mate mapped to a different chr (mapQ>=5)

Flagstats of output sam post executing samblaster
2565632 + 0 in total (QC-passed reads + QC-failed reads)
2740 + 0 secondary
0 + 0 supplementary
0 + 0 duplicates
2564846 + 0 mapped (99.97% : N/A)
2562892 + 0 paired in sequencing
1283161 + 0 read1
1279731 + 0 read2
2551398 + 0 properly paired (99.55% : N/A)
2560969 + 0 with itself and mate mapped
1137 + 0 singletons (0.04% : N/A)
2585 + 0 with mate mapped to a different chr
2525 + 0 with mate mapped to a different chr (mapQ>=5)

Questions

Why does samblaster show this warning ? samblaster: Please double check that input file is read-id (QNAME) grouped. . Our input sam is already  QNAME sorted. We verified that by checking SAM header SO (sort order)
Why does samblaster say that 0 duplicates removed while we can see that duplicates were indeed removed as shown by samtools flagstat

samblaster: Removed          0 of    2402373 (0.000%) total read ids as duplicates using 18128k memory in 1.911S CPU seconds and 3S wall time.

Sorry, I should have responded to this a long time ago.

samblaster outputs the message to double check the input file sort order whenever it finds a read flagged as part of a pair but the mate does not appear next to it in the input SAM file. samblaster does NOT use the SO information in the header of a SAM file because that is not a reliable way to determine if the file is sorted in a particular order or not. All it means is that some tool within your pipeline sorted it that way, but not that it is necessarily still in that sort order. For example, not all the available SAM/BAM sorting tools actually update that field. In addition, some SAM file manipulations essentially require that one process the header and the rest of the file separately leading to the header not being fully up to date. It is far more dependable, especially when received an error that may indicate a possible sorting issue, to look at the first chunk for alignments in the file to see if they are in fact sorted the way you expect.  In this case, I believe the file is properly sorted due to the small percentage of reads without mates (2.6%), but perhaps some unaligned reads have been removed??
Oops, thanks for pointing this out. Currently, samblaster is only counting the number of duplicates when it is marking them itself. As you used the a option, the duplicate marking algorithm has been bypassed. But even in this case, samblaster should still count the number of identified duplicates in the file so that accurate statistics can be output. (Note to self: move lines 1116-1118 down about 8 lines and predicate them on the flag state, not on whether or not the pair is added to the hash table.)


Fix dumping JSON with enum values as dict keys

Summary
Not the ideal way I would like to fix it, but it looks like orjson doesn't want to add support for enums because "would be too confusing" (even tho the fact that it doesn't work is more confusing)
See all the issues opened through the years https://github.com/ijl/orjson/issues?q=str+enum
Checklist

[x] I have run nox and all the pipelines have passed.
[ ] I have made unittests according to the code I have added/modified/deleted.

Related issues
Closes #1955

If anybody knows a nicer fix for this, please do comment here!


not returning only speicfied portion that the scan happen

Hello @shirsh94 , the problem am having with the package is that when the document is scan or for instance an id card is scan that portion where the scan happen is not return but instead the entire picture is return instead of only the portion that edges are return.
my sample code here:
import 'dart:io';
import 'package:camera/camera.dart';
import 'package:flutter/material.dart';
import 'package:flutter/services.dart';
import 'package:flutter_doc_scanner/flutter_doc_scanner.dart';
class CameraScreen extends StatefulWidget {
final CameraDescription camera;
final Function(String path) onImageCaptured;
const CameraScreen({
Key? key,
required this.camera,
required this.onImageCaptured,
}) : super(key: key);
@override
_CameraScreenState createState() => _CameraScreenState();
}
class _CameraScreenState extends State {
late CameraController _controller;
late Future _initializeControllerFuture;
@override
void initState() {
super.initState();
_controller = CameraController(
widget.camera,
ResolutionPreset.medium,
);
_initializeControllerFuture = _controller.initialize();
}
@override
void dispose() {
_controller.dispose();
super.dispose();
}
Future scanDocument(String imagePath) async {
dynamic scannedDocument;
try {
scannedDocument = await FlutterDocScanner().getScanDocuments();
} on PlatformException catch (e) {
print("Error scanning document: $e");
throw Exception("Error scanning document: $e");
}
// The scanned document may contain multiple pages, so you need to handle this accordingly.
// For simplicity, we'll assume only one page is scanned.
List<String>? scannedPages = scannedDocument as List<String>?;

if (scannedPages != null && scannedPages.isNotEmpty) {
  return scannedPages.first;
} else {
  throw Exception("No document scanned or error occurred during scanning.");
}

}
@override
Widget build(BuildContext context) {
return Scaffold(
body: FutureBuilder(
future: _initializeControllerFuture,
builder: (context, snapshot) {
if (snapshot.connectionState == ConnectionState.done) {
return Stack(
children: [
CameraPreview(_controller),
Center(
child: Container(
height: 300,
width: 300,
decoration: BoxDecoration(
border: Border.all(color: Colors.red, width: 3),
),
),
),
],
);
} else {
return Center(child: CircularProgressIndicator());
}
},
),
floatingActionButton: FloatingActionButton(
child: Icon(Icons.camera_alt),
onPressed: () async {
try {
await _initializeControllerFuture;
final image = await _controller.takePicture();
String scannedImagePath = await scanDocument(image.path);
widget.onImageCaptured(scannedImagePath);
Navigator.of(context).pop();
} catch (e) {
print(e);
}
},
),
);
}
}

Could you test it with some other devices? According to your code, it should work correctly."

I did try it with different devices but still to no avail was it solved.


Broadcast does not return Datasets with unified chunks

What happened:
If I broadcast a Dataset with chunked DataArrays, the resulting DataArrays are chunked differently.
What you expected to happen:
If I broadcast a dataset with 2 vectors of chunk size 1, I'd expect to get 2D arrays with chunksize (1, 1), rather than (1, N) and (M, 1).
Minimal Complete Verifiable Example:
import xarray as xr
ds = xr.Dataset({i: xr.DataArray(range(i*10), dims=f"dim_{i}").chunk(1) for i in range(1, 3)})
ds.broadcast_like(ds)

<xarray.Dataset>
Dimensions:  (dim_1: 10, dim_2: 20)
Dimensions without coordinates: dim_1, dim_2
Data variables:
    1        (dim_1, dim_2) int64 dask.array<chunksize=(1, 20), meta=np.ndarray>
    2        (dim_1, dim_2) int64 dask.array<chunksize=(10, 1), meta=np.ndarray>

Anything else we need to know?:

I'm not entirely sure Xarray should always make chunks that same when broadcasting. In some cases this could make a lot of very small chunks, which could lead to a slow-down.
One alternative (discussed in https://github.com/pydata/xarray/issues/3371) would be to make a top-level unify_chunks function, that would unify chunks in multiple Dataset and/or DataArray object, independent of broadcasting/alignment.

So under the hood use dask broadcast_to(..., chunks=None) and users should run unify_chunks before and/or after broadcasting?
In the example above, if my target is chunksize (1, 1), ds.unify_chunks() works. Does it make any difference passing chunks=(1, 1) to dask broadcast_to rather than using chunks=None and then rechunk?

Can we outsource the chunking decision to dask somehow?


Support [Image Name] [variant/version] scheduled for [date]

Depends on [add a reference link here]

[ ] Open a PR
[ ] Create a release
[x] Update templates (if necessary)
[ ] Update https://github.com/devcontainers/images/issues/90
[x] Update Microsoft Artifact Registry docs

Looks like this was created by accident, closing. If needed, feel free to reopen with more details, thank you!


How long does it take to generate the data set? And what is the size of the data set. It took me a day to generate data for only one city.

Our total dataset size is about 150k frames (130k train + 20k val). It took us 2-3 days to generate the data on 8 1080Ti GPUs.

Thanks for your quick reply！
I want to ask by the way how much time does it take to train the various networks in your papers.
I want to find a framework to verify my fusion method, but I don’t seem to be able to afford the computational overhead of your work：）

Geometric Fusion and TransFuser take ~2 days, Late Fusion takes 1 day, CILRS and AIM complete easily within a day and LBC takes 2-3 days since it involves training both the teacher and student models. All these estimates are using a single 1080Ti GPU. The training time can also depend on where you are loading the data from. In our case, all the data was stored on the SSD of the GPU node so dataloading was pretty fast. If your data storage has heavy I/O then that can also affect the training time.

One more point - we used OpenGL to generate all our data. If you use Vulkan then it'll take a lot longer.

To be honest, your work is great. Whether it is an introductory tutorial for novices, or as a baseline for other work.
But the data generation process is really painful for people with only one or two GPUs. It would be best if you can upload a public data set, whether in google drive or dropbox.
More importantly, the same data set can avoid some data misuse problems:)

The main problem is that our dataset size is quite big. I'll try to reduce the data to only contain the essential elements and see if I can release it.

That's great. Thank you so much for your generous contribution to the community!

We have released the data (check readme for further information). Let me know if there is any issue with downloading or using data.

The download is in progress, although the speed is a bit slow.

Thank you very much for your active efforts.

The download script contains 2 datasets so you can also try to download just the 14_weathers_data if it's taking too long.

Thanks for your tips
The download is indeed slower. When I have free time, I should try to delve into the code to see if the data can be generated quickly. Because I'm not sure if the speed is slow due to multiple sensor rendering, or because of the ground truth waypoints (from the expert).

Could you release a Mini version that contains the data used in your paper?
It’s a bit too much for me to continue to ask, but I still ask you to think about it.
This may take you some time to delete some data in the total package, maybe this can compress the data to less than 50G.

I also released a minimal dataset version (63G) which contains only rgb_front, lidar, and measurements data from the 14_weathers_data. This should be sufficient to train all the models in this repo except LBC.

Sorry to reply so late.
In order to run through the code, I made the following changes.（Town*_short->Town*_small ）
Town01_long   Town02_small  Town03_tiny   Town05_long   Town06_small  Town10_small Town01_small  Town02_tiny   Town04_long   Town05_small  Town06_tiny   Town10_tiny Town01_tiny   Town03_long   Town04_small  Town05_tiny   Town07_small Town02_long   Town03_small  Town04_tiny   Town06_long   Town07_tiny
https://github.com/autonomousvision/transfuser/blob/963fe48ca8b9b7eb7896a02f97705a48c038f71c/transfuser/config.py#L13-L17

for town in train_towns:
    train_data.append(os.path.join(root_dir, town+'_tiny'))
    train_data.append(os.path.join(root_dir, town+'_small'))
    if '7' in town or '10' in town:
        continue
    train_data.append(os.path.join(root_dir, town+'_long'))
for town in val_towns:
    val_data.append(os.path.join(root_dir, town+'_small'))

Finally, thank you again for your contribution.：）

Our total dataset size is about 150k frames (130k train + 20k val). It took us 2-3 days to generate the data on 8 1080Ti GPUs.

I'd like to know how to generate the data on multi-GPUs in parallel, like device'0' for Town01, device'1' for Town02......?Could you describe the generating process in details?

We simply ran data generation for each town separately on each GPU, i.e., we ran 8 different data generation scripts, 1 on each GPU. If you want to have a single script, you can use multiprocessing similar to this.


add Molecular Fingerprint conv

Hi, thanks for the great library!
I needed the Molecular Fingerprint convolution and as far as I could tell it is not implemented yet. This is using some improvements from the deepchem library (@rbharath if you are interested).
If there is interest in merging this, I can perhaps add an example and expand the test a bit.
Thanks!

Codecov Report

Merging #1248 into master will decrease coverage by 0.00%.
The diff coverage is 86.04%.

@@            Coverage Diff             @@
##           master    #1248      +/-   ##
==========================================
- Coverage   86.99%   86.98%   -0.01%
==========================================
  Files         160      161       +1
  Lines        6196     6239      +43
==========================================
+ Hits         5390     5427      +37
- Misses        806      812       +6

Impacted Files
Coverage Δ

torch_geometric/nn/conv/mf_conv.py
85.71% <85.71%> (ø)

torch_geometric/nn/conv/__init__.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

Thanks! This looks quite good already. Will try to merge ASAP.

I made a little bit of cleanup (like replacing ModuleDicts with ModuleLists) and renamed arguments to be more in line with other conv operators. Additionally, I removed the min_degree argument as I feel that it is really unnecessary.


IMPL ObjectPattern serialize

Impl SerializeInLoc for Pattern::ObjectPattern .

Thanks for the PR! Looks good to me, would it be too much to add a single unit test for this? :)

Cheers!


bupstash: 0.9.1 -> 0.10.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/andrewchambers/bupstash/releases.
meta.description for bupstash is: "Easy and efficient encrypted backups"
meta.homepage for bupstash is: "https://bupstash.io"
meta.changelog for bupstash is: ""
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/lyva4v73r9pmmvzpjqp1b1cpqja9cwxm-bupstash-0.10.0/bin/bupstash passed the binary check.

1 of 1 passed binary check by having a zero exit code.

1 of 1 passed binary check by having the new version present in output.

found 0.10.0 with grep in /nix/store/lyva4v73r9pmmvzpjqp1b1cpqja9cwxm-bupstash-0.10.0

found 0.10.0 in filename of file in /nix/store/lyva4v73r9pmmvzpjqp1b1cpqja9cwxm-bupstash-0.10.0

directory tree listing: https://gist.github.com/9f703a2f39a39987727dc41f440ea694

du listing: https://gist.github.com/5e0ba665bc299d91599c4abe3e48d067

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
bupstash

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/lyva4v73r9pmmvzpjqp1b1cpqja9cwxm-bupstash-0.10.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bupstash https://github.com/r-ryantm/nixpkgs/archive/b9c66d1b746bf7d707d4469d1ca2e2cf828b4709.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/lyva4v73r9pmmvzpjqp1b1cpqja9cwxm-bupstash-0.10.0
ls -la /nix/store/lyva4v73r9pmmvzpjqp1b1cpqja9cwxm-bupstash-0.10.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

bupstash

Maintainer pings
cc @andrewchambers for testing.

There has been a 0.10.1 release in the meantime, so we should wait for that.

Result of nixpkgs-review pr 132375 run on x86_64-linux 1

1 package built:

bupstash


bin-scripts not packed by pack command

currently installing pe-parser fails. The rock lacks the bin script.
I tried recreating the rock, but it consistently fails to pack the bin scripts as well, rendering the rock created useless, as it fails to install when it cannot find the bin script

pe-parser-0.5.0-1.rockspec uses https://github.com/Tieske/pe-parser/archive/version_0.5.tar.gz which was created in 2013 and lacks bin directory (https://github.com/Tieske/pe-parser/releases).

@Tieske can this be closed? Does it work for you if you point the rockspec to a tarball containing bin/?

@Tieske ping...


Redefinition errors for shader-types-sharing example in release build

As stated at https://github.com/vulkano-rs/vulkano/issues/1730#issuecomment-974712151, compiling the shader-types-sharing example in release mode results in a bunch of errors about redefined types. These errors don't appear in a debug build.
error[E0428]: the name `Data` is defined multiple times
  --> examples/src/bin/shader-types-sharing.rs:83:9
   |
83 |         vulkano_shaders::shader! {
   |         ^^^^^^^^^^^^^^^^^^^^^^^^
   |         |
   |         `Data` redefined here
   |         previous definition of the type `Data` here
   |
   = note: `Data` must be defined only once in the type namespace of this module
   = note: this error originates in the macro `vulkano_shaders::shader` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0428]: the name `SpecializationConstants` is defined multiple times
  --> examples/src/bin/shader-types-sharing.rs:83:9
   |
83 |         vulkano_shaders::shader! {
   |         ^^^^^^^^^^^^^^^^^^^^^^^^
   |         |
   |         `SpecializationConstants` redefined here
   |         previous definition of the type `SpecializationConstants` here
   |
   = note: `SpecializationConstants` must be defined only once in the type namespace of this module
   = note: this error originates in the macro `vulkano_shaders::shader` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0428]: the name `Parameters` is defined multiple times
  --> examples/src/bin/shader-types-sharing.rs:83:9
   |
83 |         vulkano_shaders::shader! {
   |         ^^^^^^^^^^^^^^^^^^^^^^^^
   |         |
   |         `Parameters` redefined here
   |         previous definition of the type `Parameters` here
   |
   = note: `Parameters` must be defined only once in the type namespace of this module
   = note: this error originates in the macro `vulkano_shaders::shader` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0119]: conflicting implementations of trait `std::clone::Clone` for type `main::shaders::ty::Parameters`
  --> examples/src/bin/shader-types-sharing.rs:83:9
   |
83 |         vulkano_shaders::shader! {
   |         ^^^^^^^^^^^^^^^^^^^^^^^^
   |         |
   |         first implementation here
   |         conflicting implementation for `main::shaders::ty::Parameters`
   |
   = note: this error originates in the macro `vulkano_shaders::shader` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0119]: conflicting implementations of trait `std::clone::Clone` for type `main::shaders::SpecializationConstants`
  --> examples/src/bin/shader-types-sharing.rs:83:9
   |
83 |         vulkano_shaders::shader! {
   |         ^^^^^^^^^^^^^^^^^^^^^^^^
   |         |
   |         first implementation here
   |         conflicting implementation for `main::shaders::SpecializationConstants`
   |
   = note: this error originates in the derive macro `Clone` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0119]: conflicting implementations of trait `std::default::Default` for type `main::shaders::SpecializationConstants`
  --> examples/src/bin/shader-types-sharing.rs:83:9
   |
83 |         vulkano_shaders::shader! {
   |         ^^^^^^^^^^^^^^^^^^^^^^^^
   |         |
   |         first implementation here
   |         conflicting implementation for `main::shaders::SpecializationConstants`
   |
   = note: this error originates in the macro `vulkano_shaders::shader` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0119]: conflicting implementations of trait `std::marker::Copy` for type `main::shaders::SpecializationConstants`
  --> examples/src/bin/shader-types-sharing.rs:83:9
   |
83 |         vulkano_shaders::shader! {
   |         ^^^^^^^^^^^^^^^^^^^^^^^^
   |         |
   |         first implementation here
   |         conflicting implementation for `main::shaders::SpecializationConstants`
   |
   = note: this error originates in the derive macro `Copy` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0119]: conflicting implementations of trait `std::marker::Copy` for type `main::shaders::ty::Parameters`
  --> examples/src/bin/shader-types-sharing.rs:83:9
   |
83 |         vulkano_shaders::shader! {
   |         ^^^^^^^^^^^^^^^^^^^^^^^^
   |         |
   |         first implementation here
   |         conflicting implementation for `main::shaders::ty::Parameters`
   |
   = note: this error originates in the derive macro `Copy` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0119]: conflicting implementations of trait `std::fmt::Debug` for type `main::shaders::SpecializationConstants`
  --> examples/src/bin/shader-types-sharing.rs:83:9
   |
83 |         vulkano_shaders::shader! {
   |         ^^^^^^^^^^^^^^^^^^^^^^^^
   |         |
   |         first implementation here
   |         conflicting implementation for `main::shaders::SpecializationConstants`
   |
   = note: this error originates in the derive macro `Debug` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0119]: conflicting implementations of trait `vulkano::shader::SpecializationConstants` for type `main::shaders::SpecializationConstants`
  --> examples/src/bin/shader-types-sharing.rs:83:9
   |
83 |         vulkano_shaders::shader! {
   |         ^^^^^^^^^^^^^^^^^^^^^^^^
   |         |
   |         first implementation here
   |         conflicting implementation for `main::shaders::SpecializationConstants`
   |
   = note: this error originates in the macro `vulkano_shaders::shader` (in Nightly builds, run with -Z macro-backtrace for more info)

@Eliah-Lakhin this looks like it's related to the code that combines shader struct definitions, implemented in #1694.

Thank you for reporting, @Rua and @phelluy!
Strange we didn't detect it before. I'm going to work on it in the nearest time.


Getting {"severity":"WARNING","message":"Warning, FIREBASE_CONFIG and GCLOUD_PROJECT environment variables are missing. Initializing firebase-admin will fail"} {} error

As the title says - when I run $ npx @firebaseextensions/fs-bq-schema-views
--non-interactive
--project=${param:PROJECT_ID}
--dataset=${param:DATASET_ID}
--table-name-prefix=${param:TABLE_ID}
--schema-files=./test_schema.json
I'm getting that error and not sure what to do?

@dackers86 Hey Dacker - I'm wondering if there is a way I can set FIREBASE_CONFIG and GCLOUD_PROJECT environment variables to resolve this error?

Hi @xtxixkx
Are there any other errors that appear in the terminal?
Could you provide a full example of the output? Thanks!

I have been able to create a schema through the gen-schema script.
There is still an unnecessary warning message {"severity":"WARNING","message":"Warning, FIREBASE_CONFIG and GCLOUD_PROJECT environment variables are missing. Initialising firebase-admin will fail"} but this does not seem to stop the schema from generating.

Let me give it another try today and I'll report back!

I ran into exactly the same issue. Wonder if there is any update on this one

After I changed to use relative file path to the json file, it seems generating the view.

Hi! @dackers86
I'm getting a similar error.
Is it possible to solve it?
$ npx @firebaseextensions/fs-bq-import-collection
{"severity":"WARNING","message":"Warning, FIREBASE_CONFIG and GCLOUD_PROJECT environment variables are missing. Initializing firebase-admin will fail"}
Unexpected token '.'

SyntaxError: Unexpected token '.'
    at wrapSafe (internal/modules/cjs/loader.js:915:16)
    at Module._compile (internal/modules/cjs/loader.js:963:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at Object.<anonymous> (/Users/fumitaka_ito/.npm/_npx/d906c8461d95e111/node_modules/@firebaseextensions/firestore-bigquery-change-tracker/lib/bigquery/index.js:30:24)
    at Module._compile (internal/modules/cjs/loader.js:999:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)

Of course, the following command also produces a similar error.
$ npx @firebaseextensions/fs-bq-schema-views
{"severity":"WARNING","message":"Warning, FIREBASE_CONFIG and GCLOUD_PROJECT environment variables are missing. Initializing firebase-admin will fail"}
Unexpected token '.'

Ran into the same issue trying to deploy my API to firebase using firebase functions. Any solutions yet?

I've added this back to our accepted column for further investigation.
From the examples above, I need to clarify the issues we are facing. Separating concerns here will make the issues easier to track.
Am I correct in saying the following are existing issues...

Running the import script produces a warning stating {"severity":"WARNING","message":"Warning, FIREBASE_CONFIG and GCLOUD_PROJECT environment variables are missing. Initializing firebase-admin will fail"}

I receive the error SyntaxError: Unexpected token '.' when running the following command npx @firebaseextensions/fs-bq-schema-views

Running OP's original script will produce the error {}.

Additional information
Could developers provide information including:
Platform: eg. Windows/linux/IOS
Latest Version: Can you confirm that you using the latest version of the import script with the --version flag. 0.1.15 is the latest version.

The latest version 0.4.5 (from NPM) doesn't work at all, you get the OP warning and if you try to pass actual parameters you get this:

error details
 {"code":"app/duplicate-app","message":"The default Firebase app already exists. This means you called initializeApp() more than once without providing an app name as the second argument. In most cases you only need to call initializeApp() once. But if you do want to initialize multiple apps, pass a second argument to initializeApp() to give each app a unique name."}

The default Firebase app already exists. This means you called initializeApp() more than once without providing an app name as the second argument. In most cases you only need to call initializeApp() once. But if you do want to initialize multiple apps, pass a second argument to initializeApp() to give each app a unique name.

I took the source and it seems that the import of RawChangelogViewSchema from "@firebaseextensions/firestore-bigquery-change-tracker"; cause all the issues. I didn't deep dive into what's going on in that package but I have a feeling that it also calls firebase admin init or something of such sort.
take the source, remove the import and paste the type that that import needs and it works.


Include shaders in package

@petterarvidsson I'm not sure about https://github.com/konstructs/client/commit/b2a1df30ce30a4e8530e8b54370ab641e52f7066, I believe that we should not have merged #229. But it's now in master now and I'm not sure what is the best way forward:

Revert it like in this PR, make a 8.1 release and later (when we need it) bump the protocol version.
or
Just do a manual 8.1 release branched from the tag 8 and merge this on top of HEAD
or
Just merge the fix, and ignore the problem and accept that release 8 is broken. Try to get 9 out soon.

Any opinions?

@nsg Maybe we should just make a realease 10, server is also already merged: https://github.com/konstructs/server/pull/149

I mean 9

Like today, and only have it fixing the shader issue and bump up the proto version.

@petterarvidsson works for me.

I killed the revert commit, so this is ready to be reviewed @petterarvidsson


Rather advanced project out of, impressively, Kosovo

https://www.ventcore.health/
I've mentioned this effort to them, and they're happy with me making an introduction via email, too, if that would be useful.

Announcement of product launch:
https://www.linkedin.com/feed/update/urn%3Ali%3Aactivity%3A6650418717819719680/


update scheme validator to raise exception if data is empty

Overview
Please replace this line with full information about your pull request. Make sure that tests pass before publishing it
scheme_validator does not prevent empty dataset. This implementation raise an exception whenever a dataset is empty and also prevent dumping empty dataset to overide the previous dataset

Please preserve this line to notify @akariv (lead of this repository)

Not sure why this is needed - there are many use cases where an empty dataset is valid (e.g. when querying a database and receiving 0 results). You might even say that each empty dataset is always vacuously valid... either way I wouldn't add it as a default behaviour.

Not sure why this is needed - there are many use cases where an empty dataset is valid (e.g. when querying a database and receiving 0 results). You might even say that each empty dataset is always vacuously valid... either way I wouldn't add it as a default behaviour.

maybe.
we currently have issues where our data source has the potential of being outdated. the pipeline accesses them with no errors but no data.
and this always over-ride our initial data. also, the validate function only checks the schema of the incoming data and not compare it with the default scheme (if any). so this meant to resolve saving empty datasets that might over ride our initial ones.
Note: our workflow is active on github actions. hence this to prevent non-valid changes.
But we can decide not to merge this and leave it in this branch for our usecase

Of course you are free to have this on your fork only!
But perhaps, for future compatibility, consider implementing this as a
separate processor.
On Wed, Jul 19, 2023 at 1:47 PM Stephen Oni @.***>
wrote:

Not sure why this is needed - there are many use cases where an empty
dataset is valid (e.g. when querying a database and receiving 0 results).
You might even say that each empty dataset is always vacuously valid...
either way I wouldn't add it as a default behaviour.
maybe.
we currently have issues where our data source has the potential of being
outdated. the pipeline accesses them with no errors but no data.
and this always over-ride our initial data. also, the validate function
only checks the schema of the incoming data and not compare it with the
default scheme (if any). so this meant to resolve saving empty datasets
that might over ride our initial ones.
Note: our workflow is active on github actions. hence this to prevent
non-valid changes.
But we can decide not to merge this and leave it in this branch for our
usecase
—
Reply to this email directly, view it on GitHub
https://github.com/datopian/dataflows/pull/1#issuecomment-1641857184,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACAY5ITTMCIRKSQQ4GUSZ3XQ63NPANCNFSM6AAAAAA2PVBPGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


Adding "Streaming Real-time log to Splunk from Spring boot" | BAEL-8434

Hi @JavierPeris ,
Could you please review the following PR related to BAEL-8434
Article Draft link: https://drafts.baeldung.com/?p=211934&preview=true

Please format the files, so the imports be in the correct order.

Hi @JavierPeris ,
I have reordered imports by following the general Standard order:
Standard Java Packages (java.)
Third-Party Packages (org., com.*)
Project-Specific Packages


Add in-repo unit and integration tests jobs for Misty

For #116

FYI: https://github.com/liu-sheng/misty/pull/4


Notcheatplus stops bots from falling correctly

For some reason when a bot falls it is slower than normal player fall speed so servers with no cheat plus will think the bot is flying, if it falls from 6 blocks or higher it will die from constantly get fall damage when getting teleported up and hitting the ground and die. If the fall is higher the bot will get kicked for flying You should if you have anytime add a new parameter like --nocheatplus or --nocheat i find this a bit annoying but everything else is nice.
Suggestion: If you could add something to stop the bot from attacking the owner or a player when !attackall is being used that would be nice too.
-Glitch

Bot falling is currently linear. Actual acceleration handling is coming in the next major update.

ok.

hows it going on getting the 1.8 protocol? or version 1.8

@GlitchHead coming up after motion handling is added.

https://github.com/DarkStorm652/DarkBot/commit/a5ad4a0d671247c19b21f3498bc68da4f6c2c350

https://github.com/DarkStorm652/DarkBot/commit/67e7898a7eec95684d804d7eeafa8256b4b2f4f5
Patched, will close as soon as the development branch is merged.


feat: Page changed_date added to the Page tree admin actions dropdown template #6701

Rebasing https://github.com/django-cms/django-cms/pull/6701

Original author @kuvandjiev
This PR is just the conflict resolved version of the initial PR


Reorganise files

WHY are these changes introduced?
It's not clear which files are used where.  This PR applies a bit more of a system
WHAT is this pull request doing?

Move billing folder to auth/admin since it's only returned by that API
Add a helpers folder to auth/admin.  Move helpers that are only used by auth/admin to this folder.

How to review this:

Does this system make sense?
Did I miss anything that should also be moved?

Type of change

[x] Patch: Bug (non-breaking change which fixes an issue)
[ ] Minor: New feature (non-breaking change which adds functionality)
[ ] Major: Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

[ ] I have used yarn changeset to create a draft changelog entry (do NOT update the CHANGELOG.md files manually)
[ ] I have added/updated tests for this change
[ ] I have documented new APIs/updated the documentation for modified APIs (for public APIs)

Can't think of any other code that we might want to move.

The only one I could think of was billing.require, but I think we can let the use case prove itself before adding it.


Issue with wildcarded _headers during netlify dev but not when deployed

- Do you want to request a feature or report a bug?
Report a bug
- What is the current behavior?
When I have this in _headers:
/*/payload.json
	Access-Control-Allow-Origin: *

I get this error when running netlify dev:
Error: invalid rule (A path rule cannot contain anything after * token) at line: 1
    /*/payload.json

However, this rule does work in my deploys.  For example, that header rule gets applied to https://netlify-dev-issue.netlify.app/payload.json but https://netlify-dev-issue.netlify.app/ doesn't.
- If the current behavior is a bug, please provide the steps to reproduce.
I set up this test repo https://github.com/weotch/netlify-dev-issue which deploys to https://netlify-dev-issue.netlify.app/
- What is the expected behavior?
I'd expect no errors during netlify dev since that rule works on deploy.
- Local Environment Information
────────────────────┐
 Environment Info   │
────────────────────┘

  System:
    OS: macOS 10.15.6
    CPU: (8) x64 Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
  Binaries:
    Node: 12.13.1 - ~/.nvm/versions/node/v12.13.1/bin/node
    Yarn: 1.21.1 - /usr/local/bin/yarn
    npm: 6.12.1 - ~/.nvm/versions/node/v12.13.1/bin/npm
  Browsers:
    Chrome: 84.0.4147.105
    Firefox: 77.0.1
    Safari: 13.1.2
  npmGlobalPackages:
    netlify-cli: 2.58.0

netlify-cli/2.58.0 darwin-x64 node-v12.13.1

Closing as stale. Please re-open if needed


"save game" as shareable image

Just an idea for the future.
On "win" trigger, dump the canvas image data to an image and let user download it, or even better, share target it.

This is a great idea. We would do this once web share adds support for files

It should be in Canary now. Presence of this ability is tied to the navigator.canShare() API which is part of the same spec.


Disarranged CSS style in raw HTML echoing

Issue summary
display: flex gone and float: right not working when echoing raw HTML content, both seemingly due to an appended width: 100% style.
Expected behaviour
https://codepen.io/suibianp/pen/bGRKeLP
The first should be on a single line, with the embedded div floating to the right.
The second should have the children distributed evenly on a line.
Actual behaviour
The first is broken into two lines.
The second is squeezed together.
Steps to reproduce
https://codepen.io/suibianp/pen/YzQvWwY
Browser and OS
Firefox 92.0 (64-bit), Manjaro Linux

And thanks for reporting the bug.

The fix is in the devel branch, it will be released in the next version.

Thank you very much for the fantastic package and rapid fix!


Fix bug in EnvParams.max_steps type

Thanks @DrJessop! Strange that pyright didn't find this bug....


Mozilla grant report

At https://hackmd.io/Qp743LHJS7qrtRIFqhQ49A?edit

Awesome @Islast! Thank you for writing this!!
I'm a bit brain dead today so I'm going to put this off until later in the week - but please comment here or leave me notes in the hackpad if there are particular points I can help with 👾


Fix issue with cred limit on presentation endpoint

Signed-off-by: Ian Costanzo<EMAIL_ADDRESS>See issue https://github.com/hyperledger/aries-cloudagent-python/issues/1436

Codecov Report

Merging #1437 (7a6a96a) into main (4df6500) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #1437      +/-   ##
==========================================
- Coverage   94.59%   94.59%   -0.01%
==========================================
  Files         483      483
  Lines       29666    29664       -2
==========================================
- Hits        28063    28061       -2
  Misses       1603     1603


Computed annotations dependencies

Add support for dependencies for computed annotations.
Fixes #3299

Per https://github.com/Polymer/polymer/pull/3358#issuecomment-179604592, we're re-considering the approach in https://github.com/Polymer/polymer/pull/3358 as potentially a more robust approach.

We decided to go with #3358 instead.


Make use of current app domain when importing

Found to be significantly quicker than creating a new app domain and
loading assembly content. It is still available as a fallback should the
current app domain not contain the required assembly or fail for any
other reason.

This seems like a worthwhile optimization. I don't like the ignored test that only exists for benchmarking purposes, but that's easy enough to remove. What I'd like to see is, say, a resource DLL that ships with the test project that we could use to verify that resource loading still works via a different App Domain. But given the time this PR has already waited, I guess I can't be too choosy. Maybe I'll write that test myself. :-)
As for potential breakage: the only scenario I can think of where this will change behavior is if you have a running version of the assembly that has different content from the on-disk version. That's a fringe case if I ever saw one, so I think this is safe enough for inclusion. I'll merge it in soon.

I merged this into develop.


Added story for component

Still a work in progress of using storybook with your component 😄
It looks like this:

Awesome.
Exactly what I was looking for.
I'll try to play with it and publish something soon so you can refer to it in your documentation, I think there are a lot of good use cases in this component like mocking the retrieves from the webapi.
I will use this as a recipe for other component storybook as well.
Great library :sparkles:
Thanks.


Improvements for TabView Style Customizations [Issue Collection]

Describe the bug
The TabView style doesn't expose all values and is hard to customize in certain scenarios. There's a been a few specific bugs filed on these topics, but this issue is meant to encapsulate them as a larger set of targeted work to fix these issues together as a single update.
Linked Issues

[ ] TabView Padding isn't bound in Style as expected #3736
[ ] TabViewItem should respect CornerRadius API #3084
[ ] How do you increase the text size in the TabViewItems header? #3047
[ ] TabViewItem should consume Foreground/Background properties #2653
[ ] TabView should get a TabViewItemSeparatorForeground theme resource to style the tab separator #2742

@stmoy as FYI

I also think TabViewItems should support a null ThemeShadow value in case depth is not desired.

Ideally we should be able to set the Z Elevation in Xaml alone, so we could template and style the value, or even animate it.

In case it hasn't been mentioned, TabView should have a customizable tab strip background.


C++/WinRT project template is broken

The C++/WinRT project template is broken in at least 2 spots:

/SharedContent/Templates/UWPSDKSampleCPP/UWPSDKSampleCPP.vstemplate references nonexistent and apparently unneeded Scenario{1,2}_ShortName.idl, but fails to reference Project.idl;
Even if 1. is addressed, when building a project generated by that template MainPage.g.cpp is reported missing.

I'm not familiar with C++/WinRT for UWP apps, and have been trying to fix it myself in vain.  Please help.

Oops, sorry. Don't use those templates for your own UWP apps. Use the ones that come with C++/WinRT. These are templates for new samples in this repo, which are unusually-structured to minimize repo size.

Is that information documented somewhere?

I'll update the installer batch file so it reminds you that these are for developing new samples, not for developing UWP apps in general. In other words, the intended audience for the batch file is people who contribute new samples to this repo.

I am aware that the templates in this repo is for creation of samples only.  I do mean that I encounter difficulty when I try to create and build a new sample.  (I must have stated the problem in an inappropriate tone. 🌚)

Sorry I misunderstood your remark. Why are you trying to create a new sample? As a general rule, samples come from the feature team.

I'm just playing around with this repo, seeing if I can port some samples from CX to C++/WinRT by myself.  However, new projects that I created from the template, as described in SharedContent/Templates/README.md, always fail to build on my computer.  I do believe that indicates some problems with the C++/WinRT template that may not reproduce themselves on your computer.

Okay, fixed templates coming in next refresh. Thanks for pointing them out.


System unavailable: test-ibmcloud-rhel7-x64-1 ran out of storage

Please put the system name in the title of this issue.

Link to any log file showing the problem:

https://ci.adoptium.net/job/Test_openjdk11_hs_sanity.external_x86-64_linux/590/

Please describe the issue:

19:36:25  tee: /home/jenkins/workspace/Test_openjdk11_hs_sanity.external_x86-64_linux/aqa-tests/TKG/../TKG/output_16876286653434/TestTargetResult: No space left on device

Please review the disk usage on this machine, and see if something's preventing the workspace from getting all the space it could reasonably be expected to need.

Having done some investigation, theres currently around 14Gb free,  it doesn't have the largest disk however, so I'll do  a bit of housekeeping and see how much I can free up.

Disk has been housekept, mostly thanks to a "docker builder prune" to clear the dangling docker build cache.
[root@test-ibmcloud-rhel7-x64-1 /]# df -h .
Filesystem      Size  Used Avail Use% Mounted on
/dev/xvda2       98G   46G   48G  49% /
Rerunning failed test job in grinder on the same machine..
https://ci.adoptium.net/job/Grinder/7295/

Thanks @steelhead31 :)


Snap to grid not working

Snap to grid not working
Description

When selected the Snap to grid options is not working.
The error trows an error

TransformControls.js:499 Uncaught TypeError: Cannot read property 'position' of undefined
    at TransformControls.onPointerMove (TransformControls.js:499)
    at TransformControls.update (TransformControls.js:289)
    at SceneEditor.update (SceneEditor.js:804)
    at update (TabElement.js:151)

Platform

Web Version [X]
Windows [X]
Linux [X]

Fixed.


Fix: Proposal to fix deactivated widget issues

The below code stops converting nullable into non-nullable, and also performs checks to avoid deactivated widget errors.
Please verify this works and help to create a new release with these fixes - much appreciated
import 'package:flutter/widgets.dart';

/// Fork of library 'Phoenix'
/// Wrap your root App widget in this widget and call [Phoenix.rebirth] to restart your app.
class Phoenix extends StatefulWidget {
  final Widget child;

  const Phoenix({Key? key, required this.child}) : super(key: key);

  @override
  PhoenixState createState() => PhoenixState();

  static rebirth(BuildContext context) {
    // fix incorrect lookup of widget - to help suppress errors
    final rootAncestorOfPhoenixState =
        context.findRootAncestorStateOfType<PhoenixState>();
    final ancestorOfPhoenixState =
        context.findAncestorStateOfType<PhoenixState>();

    if (rootAncestorOfPhoenixState != null) {
      return rootAncestorOfPhoenixState.restartApp();
    }
    if (ancestorOfPhoenixState != null) {
      return ancestorOfPhoenixState.restartApp();
    }
  }
}

class PhoenixState extends State<Phoenix> {
  Key _key = UniqueKey();

  void restartApp() {
    setState(() {
      _key = UniqueKey();
    });
  }

  @override
  Widget build(BuildContext context) {
    return KeyedSubtree(
      key: _key,
      child: widget.child,
    );
  }
}

Seems like it doesn't help with my code


Small Fixes

2 small fixes:
a) subset notation for regression tasks
b) explanation IC classification task

 IC2 Update

 Update Y = R to subspace notation


After upgrading to 2.05.42 firmware update fails

Hi,
I just upgraded deCONZ to 2.05.42 and now the firmware upgrade fails with the following message:
Enter C for Conbee, R for RaspBee, or press Enter now to exit: C
Listing attached devices...
rmmod: ERROR: Module ftdi_sio is in use
rmmod: ERROR: Module usbserial is in use by: ftdi_sio
GCFFlasher V2_11 (c) dresden elektronik ingenieurtechnik gmbh 2017/12/10
RaspBee: /dev/ttyAMA0 (default)
   1  FTDI device found

device
vendor
product
serial
description

failed to open FTDI device (0) status = 3

Hi there,
I have exactly the same issue. I see this issue is instantly closed. Can the solution be shared?
Thanks!

You need to close or unload any other programs that are using the USB bus - maybe a usb stick for ZWave - so that the flashing program can unload the relevant device drivers, which cannot be unloaded while the bus is in use.

Thanks for your quick response. I'm running HomeAssistant with z-wave dongle indeed. I had already unplugged it and stopped HA.. turned out I had another process running. Firmware in progress now. Thanks again.