Can't download from BBC iPlayer

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2016.05.01. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2016.05.01

Before submitting an issue make sure you have:

[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add -v flag to your command line you run youtube-dl with, copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
>youtube-dl --verbose --write-sub "http://www.bbc.co.uk/iplayer/episode/b03b5kl2/wolfblood-series-2-1-leader-of-the-pack"
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['--verbose', '--write-sub', 'http://www.bbc.co.uk/iplayer/episode/b03b5kl2/wolfblood-series-2-1-leader-of-the-pack']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2016.05.01
[debug] Python version 3.5.1 - Windows-10-10.0.10586-SP0
[debug] exe versions: ffmpeg N-79690-g78baa45, ffprobe N-79690-g78baa45
[debug] Proxy map: {}
[bbc.co.uk] b03b5kl2: Downloading video page
[bbc.co.uk] b03b5hp2: Downloading media selection XML
[bbc.co.uk] b03b5hp2: Downloading m3u8 information
WARNING: Failed to download m3u8 information: HTTP Error 403: Forbidden
[bbc.co.uk] b03b5hp2: Downloading m3u8 information
WARNING: Failed to download m3u8 information: HTTP Error 403: Forbidden
[bbc.co.uk] b03b5hp2: Downloading m3u8 information
WARNING: Failed to download m3u8 information: Remote end closed connection without response
[bbc.co.uk] b03b5hp2: Downloading m3u8 information
WARNING: Failed to download m3u8 information: HTTP Error 403: Forbidden
[bbc.co.uk] b03b5hp2: Downloading m3u8 information
WARNING: Failed to download m3u8 information: HTTP Error 403: Forbidden
[bbc.co.uk] b03b5hp2: Downloading captions
ERROR: No video formats found; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "c:\program files\python35\lib\site-packages\youtube_dl\YoutubeDL.py", line 673, in extract_info
    ie_result = ie.extract(url)
  File "c:\program files\python35\lib\site-packages\youtube_dl\extractor\common.py", line 341, in extract
    return self._real_extract(url)
  File "c:\program files\python35\lib\site-packages\youtube_dl\extractor\bbc.py", line 509, in _real_extract
    self._sort_formats(formats)
  File "c:\program files\python35\lib\site-packages\youtube_dl\extractor\common.py", line 862, in _sort_formats
    raise ExtractorError('No video formats found')
youtube_dl.utils.ExtractorError: No video formats found; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Description of your issue, suggested solution and other information
I can watch videos fine (using Borderless Internet's DNS), but since recently, trying to download them with youtube-dl is giving a 403 error.

Works fine with random UK proxy. Most likely they don't spoof DNS for hostnames where m3u8 playlists are stored (cp401489-vh.akamaihd.net and maybe others). Closing as not a youtube-dl issue.

Thanks for confirming that, I tried to ask a UK friend but they couldn't check at that time.


[FEA] no seriously we should try to just stop using bitwiseMergeAndSetValidity

Is your feature request related to a problem? Please describe.
I filed https://github.com/NVIDIA/spark-rapids/issues/7485 to fix some potentially problematic cases with biwiseMergeAndSetValidity. Originally I wanted to stop using the API wherever possible, but the fix for the operator itself is not that bad, so we decided to go that route. But this is a really dangerous API and I just don't know if the performance savings using it outweigh the inherent danger in it.
Like if the column that is passed in, which will have validity set for it, has nulls in it at all, this API can stomp over the top of it and make it not null. This can result in us using/reading bogus data.
I still think we should try to stop using this API and run some performance tests to see what the impact is of moving away from it.

This is fixed by rapidsai/cudf#13335.
@revans2  can you please confirm?

@razajafri #7485 is fixed by https://github.com/rapidsai/cudf/pull/13335.
It also helped to make the API safer and showed that there is a performance improvement over doing an if/else (20% to 40% better). So it makes me rethink this a bit, but I still don't like bitwiseMergeAndSetValidity as an API.
It it is confusing to use, especially compared to something like if/else. So as an implementation I think  https://github.com/rapidsai/cudf/pull/13335 has addressed my concerns. And an API no it has not.


Calendar dates desync on 02/17/23

Dates are out-of-sync on the calendar component on this current day

In addition, there seems to be a de-sync on sundays too. Apply more unit testing to all days in the week to pinpoint issues.
Example:

Fixed in https://github.com/j-rockwell/kame/pull/19


🐛 [admob? analytics?] console dashboard etc NO tracking

Bug report
Platform
IOS only
Describe the bug
firebase console, Dashboard & Crashlytics > "Latest Release", no tracking on my app which used newest version of admob / crashlytics
ie:
after Oct 2020,
Dashboard, user graph drop 9x% (other % may not upgrade newest version of my app)
Latest Release, no user use newest version of my app
Steps to reproduce
used newest version after Oct 2020

Hi @peterweb2005
There is an open issue regarding this problem #2760
Could you please comment there and if the problem came from updating your dependencies could you include the output of your flutter pub deps -- --style=compact before and after the update that broke it?
Closing this as duplicate of #2760
Thank you


System-tests: webconsole: new test for testFilterConnectionsByEncrypted

create test 'testFilterConnectionsByEncrypted' by following document: https://github.com/EnMasseProject/enmasse/blob/master/documentation/design_docs/systemtests/selenium-tests/scenarios.adoc
if tests steps are not on place then must be defined

test implemented in webconsole-connections-tests branch: https://github.com/EnMasseProject/enmasse/blob/webconsole-connections-tests/systemtests/src/test/java/io/enmasse/systemtest/brokered/web/FirefoxWebConsoleTest.java#L53
temporally disabled for Chrome

merged with master
-> close


Fix alignment of squareroot bar

Before this change:

After this change:

Tested in Chrome and Safari

Did anyone merge this thing since? This thing drives me mad :smile:

There's other rendering issues with \sqrt that we have to address.  See https://github.com/Khan/KaTeX/pull/268#issuecomment-115293652.


pkill electron to handle incomplete crash

Addresses: https://github.com/plotly/streambed/issues/11878
fyi @scjody @mag009

@scjody please review

I need to include the fix of to resolve the test failures here: https://github.com/plotly/orca/issues/154

[x] test on-prem

@antoinerg I see that you resolved: https://github.com/plotly/orca/issues/154 -- do you have any insight into the following CI failure I'm seeing here (I couldn't find a GH issue on this but I can open one as needed)?
svn: E175002: Unexpected HTTP status 504 'Gateway Timeout' on '/plotly/plotly.js.git/!svn/bc/30700/trunk/dist'


Url encoded request body not parsed

Investigative information
Please provide the following:

Timestamp: 2018-11-03T15:26:20.458
Invocation ID: d38cce31-c3d2-49ff-b56a-3f595d5967c5
Region: West-Europe

Repro steps

Generate a starter Function with Azure Core Function tools (2.1.725) with the following settings:

func init -> select 2. node
func new -> select 5. HTTP trigger -> choose default name (HttpTrigger)
Add context.log(req) at the first line of the async function() to see the output of the req object in logging (see below in source).
Deploy to Function App with WEBSITE_NODE_DEFAULT_VERSION=8.11.1 (default)
Perform POST request on function, for instance with curl -v "https://<func name>.azurewebsites.net/api/HttpTrigger?code=<code>" --data 'name=test'

Expected behaviour

After the POST request with body parameter 'name=test' included, I would expect that the Function would output 'Hello test'.

Actual behaviour

'req.body' equals 'name=test' as string instead of object. Therefor the if statement is evaluated as false.

Known workarounds
None
Related information

Programming language used:
Javascript

Bindings used:
HTTP

Tested and found not working with the following Node versions:

8.11.1
8.12.0
10.13.0

Source
module.exports = async function (context, req) {
    context.log(req)
    context.log('JavaScript HTTP trigger function processed a request.');

    if (req.query.name || (req.body && req.body.name)) {
        context.res = {
            // status: 200, /* Defaults to 200 */
            body: "Hello " + (req.query.name || req.body.name)
        };
    }
    else {
        context.res = {
            status: 400,
            body: "Please pass a name on the query string or in the request body"
        };
    }
};

So I looked into this a bit more and it seems that whenever you do a POST with a form (i.e. data is format as: "name=test&hobby=test", it is not parsed. However, when you make a JSON object of it (i.e. '{"name": "test"}', it will pick it up. I found that the way it is parsed in the function is unrelated to the content-type header set in the request (tested both with application/x-www-form-urlencoded).
For me it is unclear in the documentation that the body needs to be submitted as a JSON object and that "normal" formatting (url encoding, not sure what the correct name would be) is not parsed correctly. Are there any plans to also support the url encoded format parsing? Another idea might be to update the documentation to clarify that a Function expects body parameters to be JSON formatted?

Closing in favor of https://github.com/Azure/azure-functions-nodejs-worker/issues/347


chore(logging) add substantial debug logging

Especially in the async query part this is necessary to track
the exact order of events.
Since the messages extensivly use json serialization they are all
in long-comment brackets, which should ease to disable them
in released code. To be manually turned on by the user by doing a
"replace all" on the client code.

Are you leaving them "on by default" intentionally here? (---[[ vs. --[[)


tests

like literally any automated testing configuration at all (github actions, probably)

Got started on this with this PR: https://github.com/glyph/Pomodouroboros/pull/54 -- lots of room to expand this too (including running the non-GUI unit tests here, adding linting and formatting if desired)

Thanks @benchatt !

I'm going to call this "done", since this was just the ticket for bootstrapping. More tests will need to come later, of course.


Upgrade assessments to use the latest Firebase library

Following the upgrade of Admin repo, we need to upgrade the other repos to the latest version.
Useful links
https://firebase.google.com/docs/web/modular-upgrade
[ ] [jac-kit] Upgrade Firebase SDK to latest stable version
[ ] [admin] Upgrade Firebase SDK to latest stable version
[ ] [jac-kit] Update all the import statements from firebase to firebase/compat
[ ] [admin] Update all the import statements from firebase to firebase/compat
[ ] Refactoring Authentication functions to modular APIs
[ ] Refactoring Firestore functions to modular APIs
[ ] Refatoring firestoreAction
[ ] Update Firestore Action in store/*.js files
[ ] Upgrade VuexFire to VueFire

Hey team! Please add your planning poker estimate with Zenhub @drieJAC @HalcyonJAC @tomlovesgithub @warrensearle

Please add your planning poker estimate with Zenhub @KoWeiJAC


Add configurable quick-links page

The page here will need to be customizable. GitHub's wiki pages allow a sidebar built from markdown, as well as a primary markdown area. Something similar could be integrated into YCB.
This probably only needs to be a single page, which should make it easier.

When this is completed, lets clean up the Edmonton YCB quick links page a little.

Closed with #108


Create project does nothing

weex create awesome
when i execute this command it opens users folder from my drive C
then shows me this
? Project name (awesome)
and its end here without creating project
last out put is this :
H:\Vue>weex create awesome
? Project name project22
? Project description (A weex project)
H:\Vue>

is there any way i create project manually ? this command line thing is not working for me i tried everything

@haftado3
Hi,
Firstyle, there has not a manual way to create the official project cause it's dependent on some signal flag, to solve your problem, please tell me what's the platform you are working on and which version of weex-toolkit you are using? Is there any more detail log message? Maybe you can run the command with a --verbose option.
Thanks.

@haftado3  I'm the same as you are.

how can i produce log message? --verbose did nothing ,result is same , cause when you use
weex create whatever
it starts to download some packages or files then it clears screen and asks you for project name("why ?")
if you give it project name its done , no files for you

H:\Vue>npm install -g weex-toolkit
npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but npm-shrinkwrap.json was generated for lockfileVersion@0. I'll try to do my best with it!
npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but npm-shrinkwrap.json was generated for lockfileVersion@0. I'll try to do my best with it!
npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but npm-shrinkwrap.json was generated for lockfileVersion@0. I'll try to do my best with it!
C:\Users\Mahdi Khalili\AppData\Roaming\npm\weex -> C:\Users\Mahdi Khalili\AppData\Roaming\npm\node_modules\weex-toolkit\bin\weex.js
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\weex-toolkit\node_modules\xtoolkit\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\weex-toolkit\node_modules\weex-previewer\node_modules\weex-builder\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\weex-toolkit\node_modules\weex-previewer\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\weex-toolkit\node_modules\weex-builder\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\weex-toolkit\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

   v1.3.8
 - weexpack : v1.2.5
 - weex-builder : v0.4.0
 - weex-previewer : v1.5.1

there is files in C:\Users\Mahdi Khalili\AppData\Roaming\npm\node_modules\weex-toolkit
can we create project using those ?

@haftado3   i have solved this problem.
follow with me :
Uninstall your current NodeJS, and Download NodeJS LTS version (8.11.3)
and then
open CMD
node -v must be v8.11.3
npm -v must be v5.6.0
this way to download LTS
https://nodejs.org/dist/v8.11.3/node-v8.11.3-x64.msi

@haftado3  install NodeJS LTS v8.11.3
when you create WEEX project
maybe have a NOTICE  don't Support npm@4,  please ignore this NOTICE

in windows from C:\Users\Mahdi Khalili\AppData\Roaming\npm folder removed everything then installed from begining solved problem


framework: stop reading record while section header is broken

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Refactor recursive-aggregation feature

Please confirm that this PR has done the following:

[ ] Tests Added
[ ] Documentation Added
[ ] Name of contributors Added to AUTHORS.rst
[ ] Description in RELEASE_NOTES.md Added

Adding to RELEASE_NOTES.md (remove section after adding to RELEASE_NOTES.md)
Please add a single line in the release notes similar to the following:
- (#XX)[http://link-to-pr.com] Added feature which does something

Description of PR
This PR refactors the implementation of the recursive-aggregation feature avoiding calling data.

@tburandt, as far as I know, you are the user that heavily uses the recursive-aggregation feature in a real-word application,. Could you please test this branch whether it yields the same result as the previous implementation, and maybe also report on the speed improvement?

fyi @coroa

@danielhuppmann the recursive aggregation works like a charm even with large(er) data. It seems also faster than before, but I forgot to measure the time (unfortunately)

thanks @tburandt for taking a look!


WebDriverAgentMac will crash when execute "macos: click"

Hi,
I created a driver for Mac2, then executed "macos: click" and found WebDriverAgentMac back to itself teardown
Appium version:Appium v1.22.2
2022-03-17 16:44:17:275 - [debug] [HTTP] Request idempotency key: 219e808f-85f9-49dd-8a37-c189bef8230d
2022-03-17 16:44:17:277 - [HTTP] --> POST /wd/hub/session
2022-03-17 16:44:17:277 - [HTTP] {"desiredCapabilities":{"noReset":true,"createSessionTimeout":30000,"showServerLogs":"true","newCommandTimeout":600,"platformVersion":"12","automationName":"Mac2","bundleId":"comxx.xx","platformName":"Mac","udid":"<IP_ADDRESS>","deviceName":"XMN066","systemPort":8806},"capabilities":{"firstMatch":[{"appium:automationName":"Mac2","appium:bundleId":"comxx.xx","createSessionTimeout":30000,"appium:deviceName":"XMN066","appium:newCommandTimeout":600,"appium:noReset":true,"platformName":"mac","appium:platformVersion":"12","showServerLogs":"true","appium:systemPort":8806,"appium:udid":"<IP_ADDRESS>"}]}}
2022-03-17 16:44:17:278 - [debug] [W3C] Calling AppiumDriver.createSession() with args: [{"noReset":true,"createSessionTimeout":30000,"showServerLogs":"true","newCommandTimeout":600,"platformVersion":"12","automationName":"Mac2","bundleId":"comxx.xx","platformName":"Mac","udid":"<IP_ADDRESS>","deviceName":"XMN066","systemPort":8806},null,{"firstMatch":[{"appium:automationName":"Mac2","appium:bundleId":"comxx.xx","createSessionTimeout":30000,"appium:deviceName":"XMN066","appium:newCommandTimeout":600,"appium:noReset":true,"platformName":"mac","appium:platformVersion":"12","showServerLogs":"true","appium:systemPort":8806,"appium:udid":"<IP_ADDRESS>"}]}]
2022-03-17 16:44:17:278 - [debug] [BaseDriver] Event 'newSessionRequested' logged at<PHONE_NUMBER>278 (16:44:17 GMT+0800 (China Standard Time))
2022-03-17 16:44:17:280 - [BaseDriver] The following capabilities are not standard capabilities and should have an extension prefix:
2022-03-17 16:44:17:280 - [BaseDriver]   createSessionTimeout
2022-03-17 16:44:17:280 - [BaseDriver]   showServerLogs
2022-03-17 16:44:17:282 - [Appium] Appium v1.22.2 creating new Mac2Driver (v0.14.1) session
2022-03-17 16:44:17:284 - [Appium] Explicitly enabling use of insecure features:
2022-03-17 16:44:17:284 - [Appium]     get_server_logs
2022-03-17 16:44:17:284 - [debug] [BaseDriver] W3C capabilities and MJSONWP desired capabilities were provided
2022-03-17 16:44:17:284 - [debug] [BaseDriver] Creating session with W3C capabilities: {
2022-03-17 16:44:17:284 - [debug] [BaseDriver]   "alwaysMatch": {
2022-03-17 16:44:17:284 - [debug] [BaseDriver]     "appium:createSessionTimeout": 30000,
2022-03-17 16:44:17:284 - [debug] [BaseDriver]     "platformName": "mac",
2022-03-17 16:44:17:284 - [debug] [BaseDriver]     "appium:showServerLogs": "true",
2022-03-17 16:44:17:284 - [debug] [BaseDriver]     "appium:automationName": "Mac2",
2022-03-17 16:44:17:284 - [debug] [BaseDriver]     "appium:bundleId": "comxx.xx",
2022-03-17 16:44:17:284 - [debug] [BaseDriver]     "appium:deviceName": "XMN066",
2022-03-17 16:44:17:284 - [debug] [BaseDriver]     "appium:newCommandTimeout": 600,
2022-03-17 16:44:17:284 - [debug] [BaseDriver]     "appium:noReset": true,
2022-03-17 16:44:17:284 - [debug] [BaseDriver]     "appium:platformVersion": "12",
2022-03-17 16:44:17:284 - [debug] [BaseDriver]     "appium:systemPort": 8806,
2022-03-17 16:44:17:284 - [debug] [BaseDriver]     "appium:udid": "<IP_ADDRESS>"
2022-03-17 16:44:17:284 - [debug] [BaseDriver]   },
2022-03-17 16:44:17:284 - [debug] [BaseDriver]   "firstMatch": [
2022-03-17 16:44:17:284 - [debug] [BaseDriver]     {}
2022-03-17 16:44:17:284 - [debug] [BaseDriver]   ]
2022-03-17 16:44:17:285 - [debug] [BaseDriver] }
2022-03-17 16:44:17:286 - [BaseDriver] Capability 'showServerLogs' changed from string to boolean. This may cause unexpected behavior
2022-03-17 16:44:17:286 - [BaseDriver] The following capabilities were provided, but are not recognized by Appium:
2022-03-17 16:44:17:286 - [BaseDriver]   createSessionTimeout
2022-03-17 16:44:17:286 - [BaseDriver] Session created with session id: f7b75c67-d682-49a0-9897-f63bbb951d05
2022-03-17 16:44:17:286 - [debug] [WebDriverAgentMac] Using bootstrap root: /Users/rcadmin/.nvm/versions/node/v12.22.3/lib/node_modules/appium/node_modules/appium-mac2-driver/WebDriverAgentMac
2022-03-17 16:44:17:287 - [debug] [WebDriverAgentMac] Cleaning up 1 obsolete process
2022-03-17 16:44:17:303 - [debug] [WebDriverAgentMac] Using xcodebuild binary at '/usr/bin/xcodebuild'
2022-03-17 16:44:17:305 - [WebDriverAgentMac] WebDriverAgent sources are up to date<PHONE_NUMBER>004 >=<PHONE_NUMBER>004)
2022-03-17 16:44:17:305 - [debug] [WebDriverAgentMac] Using <IP_ADDRESS> as server host
2022-03-17 16:44:17:305 - [debug] [WebDriverAgentMac] Using port 8806
2022-03-17 16:44:17:306 - [WebDriverAgentMac] Starting Mac2Driver host process: xcodebuild build-for-testing test-without-building -project /Users/rcadmin/.nvm/versions/node/v12.22.3/lib/node_modules/appium/node_modules/appium-mac2-driver/WebDriverAgentMac/WebDriverAgentMac.xcodeproj -scheme WebDriverAgentRunner COMPILER_INDEX_STORE_ENABLE=NO
2022-03-17 16:44:17:315 - [debug] [WD Proxy] Matched '/status' to command name 'getStatus'
2022-03-17 16:44:17:315 - [debug] [WD Proxy] Proxying [GET /status] to [GET http://<IP_ADDRESS>:8806/status] with no body
2022-03-17 16:44:17:320 - [WD Proxy] connect ECONNREFUSED <IP_ADDRESS>:8806
2022-03-17 16:44:18:322 - [debug] [WD Proxy] Matched '/status' to command name 'getStatus'
2022-03-17 16:44:18:322 - [debug] [WD Proxy] Proxying [GET /status] to [GET http://<IP_ADDRESS>:8806/status] with no body
2022-03-17 16:44:18:323 - [WD Proxy] connect ECONNREFUSED <IP_ADDRESS>:8806
2022-03-17 16:44:18:356 - [debug] [WebDriverAgentMac] [xcodebuild] Command line invocation:
2022-03-17 16:44:18:357 - [debug] [WebDriverAgentMac] [xcodebuild] /Applications/Xcode13.1.app/Contents/Developer/usr/bin/xcodebuild build-for-testing test-without-building -project /Users/rcadmin/.nvm/versions/node/v12.22.3/lib/node_modules/appium/node_modules/appium-mac2-driver/WebDriverAgentMac/WebDriverAgentMac.xcodeproj -scheme WebDriverAgentRunner COMPILER_INDEX_STORE_ENABLE=NO
2022-03-17 16:44:18:357 - [debug] [WebDriverAgentMac]
2022-03-17 16:44:18:357 - [debug] [WebDriverAgentMac] User defaults from command line:
2022-03-17 16:44:18:358 - [debug] [WebDriverAgentMac]     IDEPackageSupportUseBuiltinSCM = YES
2022-03-17 16:44:18:358 - [debug] [WebDriverAgentMac]
2022-03-17 16:44:18:358 - [debug] [WebDriverAgentMac] Build settings from command line:
2022-03-17 16:44:18:358 - [debug] [WebDriverAgentMac]     COMPILER_INDEX_STORE_ENABLE = NO
2022-03-17 16:44:18:973 - [debug] [WebDriverAgentMac] [xcodebuild] --- xcodebuild: WARNING: Using the first of multiple matching destinations:
2022-03-17 16:44:18:973 - [debug] [WebDriverAgentMac] { platform:macOS, arch:x86_64, id:A27E7F44-00BE-501F-9F34-C98F56ECC3F7 }
2022-03-17 16:44:18:973 - [debug] [WebDriverAgentMac] { platform:macOS, name:Any Mac }
2022-03-17 16:44:18:973 - [debug] [WebDriverAgentMac] [xcodebuild] --- xcodebuild: WARNING: Using the first of multiple matching destinations:
2022-03-17 16:44:18:974 - [debug] [WebDriverAgentMac] { platform:macOS, arch:x86_64, id:A27E7F44-00BE-501F-9F34-C98F56ECC3F7 }
2022-03-17 16:44:18:974 - [debug] [WebDriverAgentMac] { platform:macOS, name:Any Mac }
2022-03-17 16:44:19:007 - [debug] [WebDriverAgentMac] [xcodebuild] note: Using new build system
2022-03-17 16:44:19:020 - [debug] [WebDriverAgentMac] [xcodebuild] note: Planning
2022-03-17 16:44:19:058 - [debug] [WebDriverAgentMac] [xcodebuild] Analyze workspace
2022-03-17 16:44:19:090 - [debug] [WebDriverAgentMac] [xcodebuild] Create build description
2022-03-17 16:44:19:109 - [debug] [WebDriverAgentMac] [xcodebuild] Build description signature: d8832b1c426c67e838dc8443354947ad
2022-03-17 16:44:19:109 - [debug] [WebDriverAgentMac] [xcodebuild] Build description path: /Users/rcadmin/.nvm/versions/node/v12.22.3/lib/node_modules/appium/node_modules/appium-mac2-driver/WebDriverAgentMac/DerivedData/WebDriverAgentMac/Build/Intermediates.noindex/XCBuildData/d8832b1c426c67e838dc8443354947ad-desc.xcbuild
2022-03-17 16:44:19:109 - [debug] [WebDriverAgentMac] [xcodebuild] note: Build preparation complete
2022-03-17 16:44:19:110 - [debug] [WebDriverAgentMac] [xcodebuild] note: Building targets in parallel
2022-03-17 16:44:19:166 - [debug] [WebDriverAgentMac] [xcodebuild] ** TEST BUILD SUCCEEDED **
2022-03-17 16:44:19:324 - [debug] [WD Proxy] Matched '/status' to command name 'getStatus'
2022-03-17 16:44:19:325 - [debug] [WD Proxy] Proxying [GET /status] to [GET http://<IP_ADDRESS>:8806/status] with no body
2022-03-17 16:44:19:325 - [WD Proxy] connect ECONNREFUSED <IP_ADDRESS>:8806
2022-03-17 16:44:19:574 - [debug] [WebDriverAgentMac] [xcodebuild] 2022-03-17 16:44:19.573678+0800 WebDriverAgentRunner-Runner[20201:2077201] Running tests...
2022-03-17 16:44:19:630 - [debug] [WebDriverAgentMac] [xcodebuild] Test Suite 'All tests' started at 2022-03-17 16:44:19.630
2022-03-17 16:44:19:630 - [debug] [WebDriverAgentMac] [xcodebuild] Test Suite 'WebDriverAgentRunner.xctest' started at 2022-03-17 16:44:19.630
2022-03-17 16:44:19:631 - [debug] [WebDriverAgentMac] [xcodebuild] Test Suite 'UITestingUITests' started at 2022-03-17 16:44:19.631
2022-03-17 16:44:19:631 - [debug] [WebDriverAgentMac] [xcodebuild] t =      nans Suite Set Up
2022-03-17 16:44:19:632 - [debug] [WebDriverAgentMac] [xcodebuild] Test Case '-[UITestingUITests testRunner]' started.
2022-03-17 16:44:19:632 - [debug] [WebDriverAgentMac] [xcodebuild] t =     0.00s Start Test at 2022-03-17 16:44:19.632
2022-03-17 16:44:19:656 - [debug] [WebDriverAgentMac] [xcodebuild] t =     0.02s Set Up
2022-03-17 16:44:19:657 - [debug] [WebDriverAgentMac] [xcodebuild] 2022-03-17 16:44:19.657495+0800 WebDriverAgentRunner-Runner[20201:2077201] Built at Mar  9 2022 14:15:01
2022-03-17 16:44:19:667 - [debug] [WebDriverAgentMac] [xcodebuild] 2022-03-17 16:44:19.667189+0800 WebDriverAgentRunner-Runner[20201:2077201] ServerURLHere->http://localhost:8806<-ServerURLHere
2022-03-17 16:44:20:326 - [debug] [WD Proxy] Matched '/status' to command name 'getStatus'
2022-03-17 16:44:20:327 - [debug] [WD Proxy] Proxying [GET /status] to [GET http://<IP_ADDRESS>:8806/status] with no body
2022-03-17 16:44:20:332 - [debug] [WD Proxy] Got response with status 200: {"value":{"message":"WebDriverAgent is ready to accept commands","state":"success","os":{"version":"Version 12.0 (Build 21A5506j)"},"ready":true,"build":{"time":"Mar  9 2022 14:15:01"}},"sessionId":null}
2022-03-17 16:44:20:423 - [WebDriverAgentMac] The host process is ready within 3109ms
2022-03-17 16:44:20:423 - [debug] [WD Proxy] Matched '/session' to command name 'createSession'
2022-03-17 16:44:20:423 - [debug] [WD Proxy] Proxying [POST /session] to [POST http://<IP_ADDRESS>:8806/session] with body: {"capabilities":{"firstMatch":[{}],"alwaysMatch":{"platformName":"mac","createSessionTimeout":30000,"showServerLogs":true,"automationName":"Mac2","bundleId":"comxx.xx","deviceName":"XMN066","newCommandTimeout":600,"noReset":true,"platformVersion":"12","systemPort":8806,"udid":"<IP_ADDRESS>"}}}
2022-03-17 16:44:20:431 - [debug] [WebDriverAgentMac] [xcodebuild] t =     0.80s Open comxx.xx
2022-03-17 16:44:20:432 - [debug] [WebDriverAgentMac] [xcodebuild] t =     0.80s     Activate comxx.xx
2022-03-17 16:44:20:433 - [debug] [WebDriverAgentMac] [xcodebuild] t =     0.80s         Wait for comxx.xx to idle
2022-03-17 16:44:20:446 - [debug] [WD Proxy] Got response with status 200: {"value":{"sessionId":"434BEECD-EBAB-4DE8-8B36-5B7DBFBB6B57","capabilities":{"CFBundleIdentifier":"comxx.xx"}},"sessionId":"434BEECD-EBAB-4DE8-8B36-5B7DBFBB6B57"}
2022-03-17 16:44:20:446 - [WD Proxy] Determined the downstream protocol as 'W3C'
2022-03-17 16:44:20:446 - [Appium] New Mac2Driver session created successfully, session f7b75c67-d682-49a0-9897-f63bbb951d05 added to master session list
2022-03-17 16:44:20:446 - [debug] [BaseDriver] Event 'newSessionStarted' logged at<PHONE_NUMBER>446 (16:44:20 GMT+0800 (China Standard Time))
2022-03-17 16:44:20:446 - [debug] [W3C (f7b75c67)] Cached the protocol value 'W3C' for the new session f7b75c67-d682-49a0-9897-f63bbb951d05
2022-03-17 16:44:20:446 - [debug] [W3C (f7b75c67)] Responding to client with driver.createSession() result: {"capabilities":{"platformName":"mac","createSessionTimeout":30000,"showServerLogs":true,"automationName":"Mac2","bundleId":"comxx.xx","deviceName":"XMN066","newCommandTimeout":600,"noReset":true,"platformVersion":"12","systemPort":8806,"udid":"<IP_ADDRESS>"}}
2022-03-17 16:44:20:448 - [HTTP] <-- POST /wd/hub/session 200 3170 ms - 333
2022-03-17 16:44:20:448 - [HTTP]
2022-03-17 16:46:16:893 - [HTTP] --> POST /wd/hub/session/f7b75c67-d682-49a0-9897-f63bbb951d05/execute/sync
2022-03-17 16:46:16:893 - [HTTP] {"script":"macos: click","args":[{"x":"0","y":"0"}]}
2022-03-17 16:46:16:894 - [debug] [W3C (f7b75c67)] Calling AppiumDriver.execute() with args: ["macos: click",[{"x":"0","y":"0"}],"f7b75c67-d682-49a0-9897-f63bbb951d05"]
2022-03-17 16:46:16:894 - [Mac2Driver] Executing extension command 'macos: click'
2022-03-17 16:46:16:901 - [debug] [WD Proxy] Proxying [POST /wda/click] to [POST http://<IP_ADDRESS>:8806/session/434BEECD-EBAB-4DE8-8B36-5B7DBFBB6B57/wda/click] with body: {"x":"0","y":"0"}
2022-03-17 16:46:16:905 - [debug] [WebDriverAgentMac] [xcodebuild] t =   117.27s Click <XCUIElementProxy: 0x600002bdc2a0>[0.00, 0.00]
2022-03-17 16:46:16:905 - [debug] [WebDriverAgentMac] [xcodebuild] t =   117.27s     Wait for comxx.xx to idle
2022-03-17 16:46:16:906 - [debug] [WebDriverAgentMac] [xcodebuild] t =   117.27s     Find the Application 'comxx.xx'
2022-03-17 16:46:17:928 - [debug] [WebDriverAgentMac] [xcodebuild] t =   118.30s     Retrying Click <XCUIElementProxy: 0x600002bdc2a0>[0.00, 0.00] (attempt #2)
2022-03-17 16:46:17:928 - [debug] [WebDriverAgentMac] [xcodebuild] t =   118.30s         Wait for comxx.xx to idle
2022-03-17 16:46:17:929 - [debug] [WebDriverAgentMac] [xcodebuild] t =   118.30s         Find the Application 'comxx.xx'
2022-03-17 16:46:18:940 - [debug] [WebDriverAgentMac] [xcodebuild] t =   119.31s     Retrying Click <XCUIElementProxy: 0x600002bdc2a0>[0.00, 0.00] (attempt #3)
2022-03-17 16:46:18:940 - [debug] [WebDriverAgentMac] [xcodebuild] t =   119.31s         Wait for comxx.xx to idle
2022-03-17 16:46:18:941 - [debug] [WebDriverAgentMac] [xcodebuild] t =   119.31s         Find the Application 'comxx.xx'
2022-03-17 16:46:18:982 - [debug] [WebDriverAgentMac] [xcodebuild] /Users/rcadmin/.nvm/versions/node/v12.22.3/lib/node_modules/appium/node_modules/appium-mac2-driver/WebDriverAgentMac/WebDriverAgentRunner/WebDriverAgentRunner.m:48: error: -[UITestingUITests testRunner] : Failed to synthesize event: Application for Application 'comxx.xx' is not foreground and does not allow background interaction.
2022-03-17 16:46:18:983 - [debug] [WD Proxy] Got response with status 200: {"value":null,"sessionId":"434BEECD-EBAB-4DE8-8B36-5B7DBFBB6B57"}
2022-03-17 16:46:18:983 - [debug] [W3C (f7b75c67)] Responding to client with driver.execute() result: null
2022-03-17 16:46:18:984 - [HTTP] <-- POST /wd/hub/session/f7b75c67-d682-49a0-9897-f63bbb951d05/execute/sync 200 2090 ms - 14
2022-03-17 16:46:18:984 - [HTTP]
2022-03-17 16:46:18:984 - [debug] [WebDriverAgentMac] [xcodebuild] t =   119.35s Tear Down
2022-03-17 16:46:18:984 - [debug] [WebDriverAgentMac] Test Case '-[UITestingUITests testRunner]' failed (119.352 seconds).
2022-03-17 16:46:18:984 - [debug] [WebDriverAgentMac] Test Suite 'UITestingUITests' failed at 2022-03-17 16:46:18.984.
2022-03-17 16:46:18:984 - [debug] [WebDriverAgentMac] 	 Executed 1 test, with 1 failure (0 unexpected) in 119.352 (119.354) seconds
2022-03-17 16:46:18:985 - [debug] [WebDriverAgentMac] [xcodebuild] Test Suite 'WebDriverAgentRunner.xctest' failed at 2022-03-17 16:46:18.985.
2022-03-17 16:46:18:985 - [debug] [WebDriverAgentMac] 	 Executed 1 test, with 1 failure (0 unexpected) in 119.352 (119.354) seconds
2022-03-17 16:46:18:985 - [debug] [WebDriverAgentMac] [xcodebuild] Test Suite 'All tests' failed at 2022-03-17 16:46:18.985.
2022-03-17 16:46:18:986 - [debug] [WebDriverAgentMac] 	 Executed 1 test, with 1 failure (0 unexpected) in 119.352 (119.355) seconds
2022-03-17 16:46:19:247 - [debug] [WebDriverAgentMac] [xcodebuild] 2022-03-17 16:46:19.247 xcodebuild[20193:2077015] [MT] IDETestOperationsObserverDebug: 119.956 elapsed -- Testing started completed.
2022-03-17 16:46:19:247 - [debug] [WebDriverAgentMac] [xcodebuild] 2022-03-17 16:46:19.247 xcodebuild[20193:2077015] [MT] IDETestOperationsObserverDebug: 0.000 sec, +0.000 sec -- start
2022-03-17 16:46:19:248 - [debug] [WebDriverAgentMac] 2022-03-17 16:46:19.247 xcodebuild[20193:2077015] [MT] IDETestOperationsObserverDebug: 119.956 sec, +119.956 sec -- end
2022-03-17 16:46:19:362 - [debug] [WebDriverAgentMac] [xcodebuild] Test session results, code coverage, and logs:
2022-03-17 16:46:19:362 - [debug] [WebDriverAgentMac] 	/Users/rcadmin/.nvm/versions/node/v12.22.3/lib/node_modules/appium/node_modules/appium-mac2-driver/WebDriverAgentMac/DerivedData/WebDriverAgentMac/Logs/Test/Test-WebDriverAgentRunner-2022.03.17_16-44-18-+0800.xcresult
2022-03-17 16:46:19:362 - [debug] [WebDriverAgentMac] [xcodebuild] Failing tests:
2022-03-17 16:46:19:362 - [debug] [WebDriverAgentMac] 	WebDriverAgentRunner:
2022-03-17 16:46:19:362 - [debug] [WebDriverAgentMac] 		-[UITestingUITests testRunner]
2022-03-17 16:46:19:362 - [debug] [WebDriverAgentMac]
2022-03-17 16:46:19:362 - [debug] [WebDriverAgentMac] ** TEST EXECUTE FAILED **
2022-03-17 16:46:19:362 - [debug] [WebDriverAgentMac] [xcodebuild] Testing started
2022-03-17 16:46:19:386 - [WebDriverAgentMac] Mac2Driver host process has exited with code 65, signal null
2022-03-17 16:46:21:567 - [HTTP] --> GET /wd/hub/session/f7b75c67-d682-49a0-9897-f63bbb951d05/context
2022-03-17 16:46:21:567 - [HTTP] {}
2022-03-17 16:46:21:568 - [W3C (f7b75c67)] Driver proxy active, passing request on via HTTP proxy
2022-03-17 16:46:21:569 - [debug] [W3C (f7b75c67)] Encountered internal error running command: Error: Could not proxy. Proxy error: 'GET /wd/hub/session/f7b75c67-d682-49a0-9897-f63bbb951d05/context' cannot be proxied to Mac2 Driver server because its process is not running (probably crashed). Check the Appium log for more details
2022-03-17 16:46:21:569 - [debug] [W3C (f7b75c67)]     at doJwpProxy (/Users/rcadmin/.nvm/versions/node/v12.22.3/lib/node_modules/appium/node_modules/appium-base-driver/lib/protocol/protocol.js:481:13)
2022-03-17 16:46:21:569 - [debug] [W3C (f7b75c67)]     at asyncHandler (/Users/rcadmin/.nvm/versions/node/v12.22.3/lib/node_modules/appium/node_modules/appium-base-driver/lib/protocol/protocol.js:253:9)
2022-03-17 16:46:21:569 - [HTTP] <-- GET /wd/hub/session/f7b75c67-d682-49a0-9897-f63bbb951d05/context 500 2 ms - 1019
2022-03-17 16:46:21:569 - [HTTP]
2022-03-17 16:46:21:584 - [HTTP] --> POST /wd/hub/session/f7b75c67-d682-49a0-9897-f63bbb951d05/element
2022-03-17 16:46:21:584 - [HTTP] {"using":"-ios class chain","value":"/XCUIElementTypeButton[title == 'Exit']"}
2022-03-17 16:46:21:585 - [debug] [W3C (f7b75c67)] Calling AppiumDriver.findElement() with args: ["-ios class chain","/XCUIElementTypeButton[title == 'Exit']","f7b75c67-d682-49a0-9897-f63bbb951d05"]
2022-03-17 16:46:21:585 - [debug] [BaseDriver] Valid locator strategies for this request: id, name, accessibility id, xpath, class name, -ios predicate string, predicate string, -ios class chain, class chain
2022-03-17 16:46:21:586 - [debug] [W3C (f7b75c67)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to Mac2 Driver server because its process is not running (probably crashed). Check the Appium log for more details
2022-03-17 16:46:21:586 - [debug] [W3C (f7b75c67)]     at WDAMacProxy.command (/Users/rcadmin/.nvm/versions/node/v12.22.3/lib/node_modules/appium/node_modules/appium-base-driver/lib/jsonwp-proxy/proxy.js:274:13)
2022-03-17 16:46:21:586 - [debug] [W3C (f7b75c67)]     at runMicrotasks ()
2022-03-17 16:46:21:586 - [debug] [W3C (f7b75c67)]     at processTicksAndRejections (internal/process/task_queues.js:97:5)
2022-03-17 16:46:21:586 - [HTTP] <-- POST /wd/hub/session/f7b75c67-d682-49a0-9897-f63bbb951d05/element 500 2 ms - 813
2022-03-17 16:46:21:586 - [HTTP]
2022-03-17 16:46:28:721 - [HTTP] --> GET /wd/hub/session/f7b75c67-d682-49a0-9897-f63bbb951d05/screenshot
2022-03-17 16:46:28:721 - [HTTP] {}
2022-03-17 16:46:28:721 - [W3C (f7b75c67)] Driver proxy active, passing request on via HTTP proxy
2022-03-17 16:46:28:722 - [debug] [W3C (f7b75c67)] Encountered internal error running command: Error: Could not proxy. Proxy error: 'GET /wd/hub/session/f7b75c67-d682-49a0-9897-f63bbb951d05/screenshot' cannot be proxied to Mac2 Driver server because its process is not running (probably crashed). Check the Appium log for more details
2022-03-17 16:46:28:722 - [debug] [W3C (f7b75c67)]     at doJwpProxy (/Users/rcadmin/.nvm/versions/node/v12.22.3/lib/node_modules/appium/node_modules/appium-base-driver/lib/protocol/protocol.js:481:13)
2022-03-17 16:46:28:722 - [debug] [W3C (f7b75c67)]     at asyncHandler (/Users/rcadmin/.nvm/versions/node/v12.22.3/lib/node_modules/appium/node_modules/appium-base-driver/lib/protocol/protocol.js:253:9)
2022-03-17 16:46:28:723 - [HTTP] <-- GET /wd/hub/session/f7b75c67-d682-49a0-9897-f63bbb951d05/screenshot 500 2 ms - 1025
2022-03-17 16:46:28:723 - [HTTP]
2022-03-17 16:46:28:731 - [HTTP] --> GET /wd/hub/session/f7b75c67-d682-49a0-9897-f63bbb951d05/source
2022-03-17 16:46:28:731 - [HTTP] {}
2022-03-17 16:46:28:732 - [W3C (f7b75c67)] Driver proxy active, passing request on via HTTP proxy
2022-03-17 16:46:28:733 - [debug] [W3C (f7b75c67)] Encountered internal error running command: Error: Could not proxy. Proxy error: 'GET /wd/hub/session/f7b75c67-d682-49a0-9897-f63bbb951d05/source' cannot be proxied to Mac2 Driver server because its process is not running (probably crashed). Check the Appium log for more details
2022-03-17 16:46:28:733 - [debug] [W3C (f7b75c67)]     at doJwpProxy (/Users/rcadmin/.nvm/versions/node/v12.22.3/lib/node_modules/appium/node_modules/appium-base-driver/lib/protocol/protocol.js:481:13)
2022-03-17 16:46:28:733 - [debug] [W3C (f7b75c67)]     at asyncHandler (/Users/rcadmin/.nvm/versions/node/v12.22.3/lib/node_modules/appium/node_modules/appium-base-driver/lib/protocol/protocol.js:253:9)
2022-03-17 16:46:28:733 - [HTTP] <-- GET /wd/hub/session/f7b75c67-d682-49a0-9897-f63bbb951d05/source 500 2 ms - 1017
2022-03-17 16:46:28:734 - [HTTP]
2022-03-17 16:46:32:115 - [HTTP] --> GET /wd/hub/session/f7b75c67-d682-49a0-9897-f63bbb951d05/screenshot
2022-03-17 16:46:32:115 - [HTTP] {}
2022-03-17 16:46:32:116 - [W3C (f7b75c67)] Driver proxy active, passing request on via HTTP proxy
2022-03-17 16:46:32:117 - [debug] [W3C (f7b75c67)] Encountered internal error running command: Error: Could not proxy. Proxy error: 'GET /wd/hub/session/f7b75c67-d682-49a0-9897-f63bbb951d05/screenshot' cannot be proxied to Mac2 Driver server because its process is not running (probably crashed). Check the Appium log for more details
2022-03-17 16:46:32:117 - [debug] [W3C (f7b75c67)]     at doJwpProxy (/Users/rcadmin/.nvm/versions/node/v12.22.3/lib/node_modules/appium/node_modules/appium-base-driver/lib/protocol/protocol.js:481:13)
2022-03-17 16:46:32:117 - [debug] [W3C (f7b75c67)]     at asyncHandler (/Users/rcadmin/.nvm/versions/node/v12.22.3/lib/node_modules/appium/node_modules/appium-base-driver/lib/protocol/protocol.js:253:9)
2022-03-17 16:46:32:118 - [HTTP] <-- GET /wd/hub/session/f7b75c67-d682-49a0-9897-f63bbb951d05/screenshot 500 3 ms - 1025
2022-03-17 16:46:32:118 - [HTTP]
2022-03-17 16:46:33:117 - [HTTP] --> GET /wd/hub/session/f7b75c67-d682-49a0-9897-f63bbb951d05/screenshot
2022-03-17 16:46:33:118 - [HTTP] {}
2022-03-17 16:46:33:118 - [W3C (f7b75c67)] Driver proxy active, passing request on via HTTP proxy
2022-03-17 16:46:33:119 - [debug] [W3C (f7b75c67)] Encountered internal error running command: Error: Could not proxy. Proxy error: 'GET /wd/hub/session/f7b75c67-d682-49a0-9897-f63bbb951d05/screenshot' cannot be proxied to Mac2 Driver server because its process is not running (probably crashed). Check the Appium log for more details
2022-03-17 16:46:33:119 - [debug] [W3C (f7b75c67)]     at doJwpProxy (/Users/rcadmin/.nvm/versions/node/v12.22.3/lib/node_modules/appium/node_modules/appium-base-driver/lib/protocol/protocol.js:481:13)
2022-03-17 16:46:33:119 - [debug] [W3C (f7b75c67)]     at asyncHandler (/Users/rcadmin/.nvm/versions/node/v12.22.3/lib/node_modules/appium/node_modules/appium-base-driver/lib/protocol/protocol.js:253:9)
2022-03-17 16:46:33:120 - [HTTP] <-- GET /wd/hub/session/f7b75c67-d682-49a0-9897-f63bbb951d05/screenshot 500 2 ms - 1025
2022-03-17 16:46:33:120 - [HTTP]
2022-03-17 16:46:41:914 - [HTTP] --> GET /wd/hub/session/f7b75c67-d682-49a0-9897-f63bbb951d05/context
2022-03-17 16:46:41:915 - [HTTP] {}
2022-03-17 16:46:41:915 - [W3C (f7b75c67)] Driver proxy active, passing request on via HTTP proxy
2022-03-17 16:46:41:916 - [debug] [W3C (f7b75c67)] Encountered internal error running command: Error: Could not proxy. Proxy error: 'GET /wd/hub/session/f7b75c67-d682-49a0-9897-f63bbb951d05/context' cannot be proxied to Mac2 Driver server because its process is not running (probably crashed). Check the Appium log for more details
2022-03-17 16:46:41:916 - [debug] [W3C (f7b75c67)]     at doJwpProxy (/Users/rcadmin/.nvm/versions/node/v12.22.3/lib/node_modules/appium/node_modules/appium-base-driver/lib/protocol/protocol.js:481:13)
2022-03-17 16:46:41:917 - [debug] [W3C (f7b75c67)]     at asyncHandler (/Users/rcadmin/.nvm/versions/node/v12.22.3/lib/node_modules/appium/node_modules/appium-base-driver/lib/protocol/protocol.js:253:9)
2022-03-17 16:46:41:917 - [HTTP] <-- GET /wd/hub/session/f7b75c67-d682-49a0-9897-f63bbb951d05/context 500 3 ms - 1019
2022-03-17 16:46:41:917 - [HTTP]

We have the same issue. Clicking on the macOS full screen button of our app crashes the driver with "Failed to synthesize event: Application for "_XCUI:FullScreenWindow" Button is not foreground and does not allow background interaction." After that message the driver is not reachable anymore:

Is the issue still relevant in the latest driver version?

Yes, still doesn't work in 1.5.2

I am currently testing the patch https://github.com/appium/appium-mac2-driver/pull/194
Please apply it locally and check if it resolves the above issue


Black

#26

Hi @Um9i! 👋
Thank you for this pull-request. I'd rather not remove flake8 from our test environments. Would you mind reverting that specific change?

this is fixable with a rerun of black with the --line-length parameter if that's the preferred way of going about it.

I just updated the flake8 max line length to the black default line length value.
See https://github.com/hackebrot/poyo/blob/master/setup.cfg#L17
Thanks again @Um9i! 🐓


add Colin Griffin to the Platforms WG chairs

🥳 Very excited to help make this official! Per the vote I have added @krumware to the site in all supported languages. Note that I just reordered one list to keep it consistent across all pages.
closes #564

Thank y'all! Looking forward to catching up in person this week!


Upgrade to Flink 1.17.0

Merge once: https://github.com/crate/cratedb-flink-jobs/issues/15 is complete
Checklist

[x] CLA is signed

Thx for ther relase @amotl !


Disallow dangrous parameters in the config file

Right now, the parameters overwrite_key (overwrites* the tower's key and gives it a new identity) and force_update (introduced in #216) are allowed to be set in the configuration file.
Since they are more of a fail-safe and rather dangerous commands, we should assert that the user doesn't set them in the config file and only settable as command line flags.

Concept ACK

Right now, the parameters overwrite_key (overwrites* the tower's key and gives it a new identity) and force_update (introduced in #216) are allowed to be set in the configuration file.
Since they are more of a fail-safe and rather dangerous commands, we should assert that the user doesn't set them in the config file and only settable as command line flags.

So, removing the command from the config file and allowing the user to use it only in cli?

So, removing the command from the config file and allowing the user to use it only in cli?

Yeah something like that. You might only disallow it by sanity checking that it's not set. Not that we have to remove it from the Config struct.

Just noticed there is actually nothing dangerous here because Config::patch_with_options completely ignores the config file value of overwrite_key & force_update and uses the command line options instead (which default to false).
I think we can just note that in a comment in the template config file so that users don't expect something when setting these ignored parameters to true.
Also, write a comment about it in https://github.com/talaia-labs/rust-teos/blob/1a89c5da70278ac5019a3bbb505b1923648a43da/teos/src/config.rs#L206-L207 since we all missed it xD.


feat(mlcache) custom LRU layers

We can now instruct mlcache to cache a given value in user-specified
LRU. One can now namespace entities, and store entities of various
sizes, hit/miss frequency in different Lua-land LRUs. One can also use
the pureffi LRU implementation if desired.
local resty_lru = require "resty.lrucache.pureffi"
local my_lru = resty_lru.new(10e3)

local cache = mlcache.new()

cache:add_lru("my_pureffi_lru", my_lru)

local value, err = cache:get("my_key", { lru = "my_pureffi_lru" }, cb)
if err then
    error(err)
end

-- value is store in the custom lru
print(my_lru:get("my_key")) -- "123"

@tieske @p0pr0ck5 Do you like this approach? Feedback welcome!

@Tieske anything to add here?

I do not get this feature? What am I missing?
If you want a different lru, then you'd call new again, and you'd get a different lru. So why one object with multiple lru's? unnecessary complex? using a ffi based one would be one extra option at create time.
If anything, a Lua land cache should be "named", and any key stored in the lru cache should be stored in the shm as lru_cache_name .. ":" .. key to prevent collisions when using multiple lru caches on top of a single shm.

and additional to that, it should use a named ipc channel as well. Such that an lru cache would only receive a callback for its own cache, not for other ones.

I do not get this feature? What am I missing?

You suggested it at #8, and I thought it was a good idea. I still do.

If you want a different lru, then you'd call new again, and you'd get a different lru. So why one object with multiple lru's? unnecessary complex? using a ffi based one would be one extra option at create time.

That is not how you originally suggested it, and I do prefer the current approach, which is lighter: a single mlcache means only 1 IPC, less channels, less overhead, and more flexibility than just an option for the FFI implementation.

@Tieske I have no idea what your other comments are about, since they are not on the files lines themselves but in the commit.

I will assume where they were intended to be.

and additional to that, it should use a named ipc channel as well. Such that an lru cache would only receive a callback for its own cache, not for other ones.

No, this is by design since the delete() function does not accept the LRU name for user-friendliness. The cost is trivial.

this whole library so far assumes that the data in Lua land cache and in shm are equal. There should be another callback between those two. The Lua land cache is not limited to scalar values and hence should be able to hold other data. But that requires a callback to convert the scalar shm based values to the lua-land presentation.

The Lua land cache indeed holds tables and scalar in their Lua form, I am not sure what this is referring to.

This function is not symmetrical with shmlru_set below. The latter one will never return the cache-miss-sentinel value, while this one does.

Yes, this is by design.

I do not get this feature? What am I missing?

You suggested it at #8, and I thought it was a good idea. I still do.

If you want a different lru, then you'd call new again, and you'd get a different lru. So why one object with multiple lru's? unnecessary complex? using a ffi based one would be one extra option at create time.

That is not how you originally suggested it, and I do prefer the current approach, which is lighter: a single mlcache means only 1 IPC, less channels, less overhead, and more flexibility than just an option for the FFI implementation.

Then I probably expressed myself poorly. I consider the mlcache-objects just a wrapper around an lru cache, with automatic sync added to shm and other workers. So probably I mixed mlcache-objects and lru in that message, as I see them in a 1-on-1 relation.
Because you'd want individual lru caches, but shared shm's, I'd expect something like:
local consumer_cache = mlcache.new("dbcache", { ipc_shm = "ipc_events" })
local api_cache      = mlcache.new("dbcache", { ipc_shm = "ipc_events" })
local plugin_cache   = mlcache.new("dbcache", { ipc_shm = "ipc_events" })

If using this with a 16 worker system, each event will invoke 48 callbacks, where only 16 would be necessary. That is because the channel is just one generic channel, and not lru-cache specific.
So by naming the individual lru-caches, and then assigning individual channels a lot of callback calls will be saved. Additionally, by namespacing in the shm based on the you'll avoid key collisions in the shm (which is an important user expectation criteria imo)
What usecase do you see for the current implementation, with "nested lru's"? eg:
local something = consumer_cache:get(
    key,
    { lru = "another_lru_name" },
    function()
        -- some callback implementation
    end)

This seems rather cumbersome to me. But apparently I haven't figured out your design concept just yet :smile:.

this whole library so far assumes that the data in Lua land cache and in shm are equal. There should be another callback between those two. The Lua land cache is not limited to scalar values and hence should be able to hold other data. But that requires a callback to convert the scalar shm based values to the lua-land presentation.

The Lua land cache indeed holds tables and scalar in their Lua form, I am not sure what this is referring to.

simple example, assume the callback for fetching data from the database is returning an array as a lua table:
    data = { "birds", "cows", "Flying Elephants" }

This data is serialised and stored in the shm. Now I want a second callback between the shm and the lru-cache like this:
-- implement hash-part for case-insensitive lookup
local function shm_to_lua_cb(data)
    if not data then
        return data
    end
    for i, v in ipairs(data) do
        data[v:lower()] = i
    end
    return data
end

The result being:
    -- shm entry
    data = {
        [1] = "birds",
        [2] = "cows",
        [3] = "Flying Elephants",
    }

    -- lru entry
    data = {
        [1] = "birds",
        [2] = "cows",
        [3] = "Flying Elephants",
        ["birds"] = 1,
        ["cows"] = 2,
        ["flying elephants"] = 3,
    }

This is a very simple reverse lookup example, but it could do more complex stuff like deserialising into objects, etc.

#16 turns mlcache into an LRU extension backed up by an shm that can be shared between mlcache instances :)


Workspaces - Unable to launch Whatsapp Store version

Microsoft PowerToys version
0.84.1
Installation method
GitHub
Running as admin
No
Area(s) with issue?
Workspaces
Steps to reproduce
Try to add WhatsApp (Store version) to a workspace, when trying to start the application "Open with"  dialog appears.
✔ Expected Behavior
WhatsApp starting
❌ Actual Behavior
Open With dialog appears
Other Software
N/A

/bugreport

I just tried to reproduce this on build 0.85.1 on which it doesn't repro, so probably fixed by an other code change between 0.85 & 0.85.1
Ticket can be closed.
However when switching Workspaces back to enabled it crashed powertoys; I'll raise a different ticket for this.
CONTEXT:  (.ecxr)
rax=00000077c4779650 rbx=00000077c4779c60 rcx=00000077c4779650
rdx=0000000000000000 rsi=00000201858a2010 rdi=00000077c4779650
rip=00007ffe3e4d3b32 rsp=00000077c4779570 rbp=0000000000000001
 r8=0000000000000000  r9=0000000000000000 r10=000002018cd8e0c0
r11=00000077c4779c60 r12=0000000000000001 r13=0000000000000000
r14=0000000000000002 r15=0000400000000000
iopl=0         nv up ei pl nz na po nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000204
KERNELBASE!RaiseFailFastException+0x152:
00007ffe`3e4d3b32 0f1f440000      nop     dword ptr [rax+rax]
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007ffe3e4d3b32 (KERNELBASE!RaiseFailFastException+0x0000000000000152)
   ExceptionCode: c000027b
  ExceptionFlags: 00000001
NumberParameters: 2
   Parameter[0]:<PHONE_NUMBER>8a2010
   Parameter[1]:<PHONE_NUMBER>000003

PROCESS_NAME:  PowerToys.Settings.exe

ERROR_CODE: (NTSTATUS) 0xc000027b - An application-internal exception has occurred.


Fixes decompression of base64 strings originated from JS compressor i…

The original Python code simply copies the structure of the original JS code.
However, the JS code only works, because at the end of the array, when it increases the data.index value beyond its length, the str.charCodeAt(index) function returns NaN. The not value is in the next iteration combined using bitewise AND operator with data.position to produce numerical 0.
This change reproduces this ingenious /s JS behaviour in Python.
Example:
on the JS console of the lz-string demo page produce this compressed content:
LZString144.compressToBase64("ahoj")
"IYCw9gVkA==="
If you try to decompress this output with the Python version of the lzstring library, you'll get following error:
$ python3 -c 'from lzstring import LZString; lz=LZString(); print(lz.decompressFromBase64("IYCw9gVkA==="))'
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python3.4/dist-packages/lzstring/init.py", line 685, in decompressFromBase64
return self.decompress(output)
File "/usr/local/lib/python3.4/dist-packages/lzstring/init.py", line 563, in decompress
data_val = ord(data_string[data_index])
With the fix introduced here the decompression succeeds:
$ python3 -c 'from lzstring import LZString; lz=LZString(); print(lz.decompressFromBase64("IYCw9gVkA==="))'
ahoj

This patch work for me.


Upgrade Kotlin, Kotlin Poet, and Kotlinter

Upgrading to Kotlin 1.7.0
Upgrade to 'com.squareup:kotlinpoet:1.12.0' and 'com.github.ajalt.clikt:clikt:3.5.0' brought Kotlin 1.7.0 so decided to upgrade the project as well. If we want to revert moving to Kotlin 1.7.0 we will need to pin clickt and kotlinpoet to 3.4.+ and 1.11.+ respectively.
Upgrade to squareup:kotlinpoet 1.12.0
Upgraded Kotlin Poet as part of the effort of having type parameters be expressed as part of the constructor for Kotlin Data Types. Arguably we could try to keep the previous version of kotlinpoet, but I'm hesitant since we will have to reply some of the subtle changes we had to make to have string comparisons for the generated code work.
Upgrading to Kotlinter 3.11.1
Moving to kotlinter 3.11.1 since 3.6.0 was creating problems with tests since, it appeared, that it was taking into account string template blocks as part of the code. This created several changes in this PR that are just related to formatting.
Other Fixes

Make sure we run the CI job on every push and not only when the PR is opened
Remove the .env file, use sdk env instead

Just wanted to confirm - you didn't update all of those test cases by hand, right? You used the flag to regenerate them?

@mbossenbroek ... which flag? 0.o

Oh no! This one... You set this to true, run the tests, and instead of verifying that they match it'll re-generate all of these files with whatever the generator is currently producing. The idea is that you never update them manually, you just toggle this & verify that you like the change. I called that out in the original PR but I wonder if it got buried in a bunch of other comments 😬
https://github.com/Netflix/dgs-codegen/blob/master/graphql-dgs-codegen-core/src/test/kotlin/com/netflix/graphql/dgs/codegen/Kotlin2CodeGenTest.kt#L35-L36

Thanks @mbossenbroek , TIL.  @kilink @mbossenbroek , do you see any risk of having Kotlin 1.7 here where the code will be used in projects with Kotlin 1.6?


Providing multiple packages and versions for each

Currently I notice that Packages input can take a list of packages separated by a semi-colon or comma. But Version input can take only one value for all of those packages. Is that correct? If I have a need where I have 10 packages, each having different versions and I want to promote all, how can I do that?
Also I have considered creating my own task for other reasons for package promotion and I came across "Package Management" artifact source in Azure DevOps. Have you considered that as part of this task development? Just wanted to get your thoughts there.
https://docs.microsoft.com/en-us/azure/devops/pipelines/release/artifacts?view=azure-devops (Search for Package Management)

If I have a need where I have 10 packages, each having different versions and I want to promote all, how can I do that?

You can use the package metadata feature to do that (screenshot). Alternatively, you could add 1 instance of the task per version, which is less flexible.

Also I have considered creating my own task for other reasons for package promotion and I came across "Package Management" artifact source in Azure DevOps. Have you considered that as part of this task development? Just wanted to get your thoughts there.
https://docs.microsoft.com/en-us/azure/devops/pipelines/release/artifacts?view=azure-devops (Search for Package Management)

Could you explain exactly what you had in mind?

So Package Management artifact source let's users add a package and version as an artifact from a particular feed. Say I want to promote 10 package versions, I'll add 10 Package Management artifact sources. After that the custom task will get all the 10 packages and versions specified as artifact source and promote them.

Ping. Any thoughts? Also any plans to support universal packages? As there is no package metadata associated and the only way it to specify the package name and versions explicitly.

Hi! Thanks for your message. Supporting multiple versions is not something we will support for now. I propose multiple tasks or maybe use a task group to make it bit more concise. Universal packages should wor although the documentation still needs to be updated


[Android] ENVFILE set from gradle script is not recognized

👋   Hello, good afternoon!
I'm using Fastlane to build our application and I'm having a hard time trying to set the ENVFILE property when bundling a new release.
Everything works as expected when using ENVFILE at runtime:
ENVFILE=./config/env/.env.prod react-native run-android --variant=release
After adding Fastlane, I'm trying to add our environment variables at build time. Because I must send a .aab file to Play Store, I need these variables injected at compilation time.
What I'm trying to do:
cd android && ENVFILE=../config/env/.prod.env ./gradlew bundleRelease
In the logs, I noticed the env file was read correctly: Reading env from: ../config/env/.prod.env. However, when running the release variant (react-native run-android --variant=release), the env file is not recognized (it outputs *** Missing .env file ****
What I tried

Instead of using bundleRelease, I tried assembleRelease. Same results.
I downloaded the final .apk on an Android device to check if the problem was with the react-native command. Same results.

Notice I didn't mention any Fastlane specifics on this issue. I believe this is happening whenever users try to use the ENVFILE property with gradlew scripts.
Versions
    "react-native-config": "^1.4.1",
    "react-native": "0.63.3"

I ended up using the project.ext.envConfigFiles alternative.
In case it helps, here's the relevant fastlane config:
  # Assembles a release from a custom build type (valid types: debug, release, staging)
  private_lane :build_android do |options|
    build_type = options.fetch(:build_type)
    gradle(task: "bundle#{build_type.capitalize}", project_dir: ANDROID_PATH)
  end

Because of the way react-native-config extracts the build type, I had to capitalize the first letter of it (bundleRelease, bundleStaging and bundleDebug).
I added the following to my build.gradle:
project.ext.envConfigFiles = [
    debug: "./config/env/.dev.env",
    release: "./config/env/.prod.env",
    staging: "./config/env/.staging.env",
]

And on buildTypes, I have:
buildTypes: {
  ...

        /**
         * The `initWith` property allows you to copy configurations from other build types,
         * then configure only the settings you want to change.
        */
        staging {
            initWith buildTypes.release
            applicationIdSuffix ".staging"
            matchingFallbacks = ['release']
        }
}


Added non-ASCII examples; clarify path handling

While working on https://github.com/bsittler/async-cookies-api/pull/24 I noticed some badly worded parts of the explainer and the lack of non-ASCII examples

@domenic @annevk What do you think of these proposed changes? I believe this clarifies path handling for read and write operations and gives examples with non-ASCII cookie values which should better explain the intent

I guess I'm not sure I entirely understand the processing model for the path stuff, but I can wait for precise spec text for that.
Non-ASCII examples are good. Maybe you want to give examples of how writing allows you to read back and get the same values?

I guess I'm not sure I entirely understand the processing model for the path stuff, but I can wait for precise spec text for that.

Yeah, this part needs a spec badly. Existing browser behavior appears to be somewhat inconsistent here.

Non-ASCII examples are good. Maybe you want to give examples of how writing allows you to read back and get the same values?

Done, I think. Does it do what you meant?

Yeah, looks good!


How to use the h264enc.exe and h264dec.exe

I have been trying the following command to encode an image:
>> h264enc.exe sourceImage.jpg encodedImage.h264
and end up getting the following error:
Unable to open source sequence file (), check corresponding path!
Wels SVC Encoder Usage:
Syntax: welsenc.exe -h
Syntax: welsenc.exe welsenc.cfg
Syntax: welsenc.exe welsenc.cfg [options]
Any suggestions on how to get this working? Can I now use the encodedImage.h264 to decode it back to yuv file using: h264dec.exe encode.h264 output.yuv
Thanks in advance!

Wels SVC Encoder Usage:
Syntax: welsenc.exe -h
Syntax: welsenc.exe welsenc.cfg
Syntax: welsenc.exe welsenc.cfg [options]
you can see the welsenc.cfg sample in testbin folder, you can change the configure as you expect.
for decoder usage, you are right.
" h264dec.exe encode.h264 output.yuv"

.cfg.zip
MSR LA - 3495.docx
MSR LA - 3495.docx
MSR LA - 3495.docx


DHCP Scopes for Newbold Revel

Based on the request received from Tariq Mahmood and from the attached doc https://app.zenhub.com/files/285252478/59f6c3ec-3bd6-4730-9a14-c4c73ae61427/download, following scopes are required for Newbold Revel site:

[ ] <IP_ADDRESS>/22
[ ] <IP_ADDRESS>/22

Hi Touhid
Yes I can confirm the subnets provided by Vodafone are correct. please drop me a message once its done. I will keep an eye here too.

Subnets have been created:

Thank you so much Touhid for your help.


malloc(): corrupted top size in iree-compile and iree-opt when building with existing LLVM

What happened?
I am experimenting with using pre-baked distros of LLVM to build IREE (mlir-wheels) and I'm hitting the weirdest heap/malloc/something error:
(iree) mlevental@mlevental-CORSAIR-ONE-PRO-a200:/tmp/iree/build/tools$ ./iree-opt
malloc(): corrupted top size
Aborted (core dumped)

and
(iree) mlevental@mlevental-CORSAIR-ONE-PRO-a200:/tmp/iree/build/tools$ ./iree-compile
malloc(): corrupted top size
Aborted (core dumped)

and only those two. And this only happens if I build IREE in release mode. gdbing the release binaries I get
Program received signal SIGABRT, Aborted.
__pthread_kill_implementation (no_tid=0, signo=6, threadid=140737353580288) at ./nptl/pthread_kill.c:44
44	./nptl/pthread_kill.c: No such file or directory.
(gdb) bt
#0  __pthread_kill_implementation (no_tid=0, signo=6, threadid=140737353580288) at ./nptl/pthread_kill.c:44
#1  __pthread_kill_internal (signo=6, threadid=140737353580288) at ./nptl/pthread_kill.c:78
#2  __GI___pthread_kill (threadid=140737353580288, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#3  0x00007fffeea42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#4  0x00007fffeea287f3 in __GI_abort () at ./stdlib/abort.c:79
#5  0x00007fffeea89676 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fffeebdbb77 "%s\n") at ../sysdeps/posix/libc_fatal.c:155
#6  0x00007fffeeaa0cfc in malloc_printerr (str=str@entry=0x7fffeebd97ec "malloc(): corrupted top size") at ./malloc/malloc.c:5664
#7  0x00007fffeeaa46f2 in _int_malloc (av=av@entry=0x7fffeec1ac80 <main_arena>, bytes=bytes@entry=8) at ./malloc/malloc.c:4373
#8  0x00007fffeeaa5262 in __GI___libc_malloc (bytes=8) at ./malloc/malloc.c:3321
#9  0x00007fffee6ae98c in operator new(unsigned long) () from /lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x00007ffff087e026 in void std::vector<mlir::Pass::Statistic*, std::allocator<mlir::Pass::Statistic*> >::_M_realloc_insert<mlir::Pass::Statistic*>(__gnu_cxx::__normal_iterator<mlir::Pass::Statistic**, std::vector<mlir::Pass::Statistic*, std::allocator<mlir::Pass::Statistic*> > >, mlir::Pass::Statistic*&&) () from /tmp/iree/build/lib/libIREECompiler.so
#11 0x0000000000000000 in ?? ()

which gives me only Pass::Statistic to go off. Luckily this utility is not used anywhere upstream and in only one place in IREE: compiler/src/iree/compiler/Dialect/Util/Transforms/FoldGlobals.cpp#L523-L526. Commenting out the requisite stuff resolves the heap/malloc/error. Reading around llvm/ADT/Statistic.h#L38 I find
#if !defined(NDEBUG) || LLVM_FORCE_ENABLE_STATS
#define LLVM_ENABLE_STATS 1
#else
#define LLVM_ENABLE_STATS 0
#endif

Which might explain why no when building in debug mode? But not really because the heap error is from here I think. So I'm going to try building my wheels with LLVM_FORCE_ENABLE_STATS=ON and see whether that resolves the issue but even if it does, it won't explain it.
Before anyone recommends asan: I had to disable compiler-rt because I haven't yet figured out how to cross compile it (and the wheels are cross-compiled for aarch64/arm64) so no go there currently :(

So I'm going to try building my wheels with LLVM_FORCE_ENABLE_STATS=ON and see whether that resolves the issue but even if it does, it won't explain it.

Indeed this worked but I don't know why.

Mismatched ndebug. LLVM does not have compatible class layouts between ndebug and not.

Mismatched ndebug. LLVM does not have compatible class layouts between ndebug and not.

So when I compile LLVM with LLVM_ENABLE_ASSERTIONS=ON I get NDEBUG un-defined? And thus in IREE I have to do IREE_ENABLE_ASSERTIONS=ON as well?

Yes, the -DNDEBUG compiler flags must match and that cmake setting controls it

Mystery solved. Good work team.


Build python3 by default?

FWIW I don't feel strongly about this and I feel like python2-by-default will be easier because that's what upstream pypy is shipping.  But folks are welcome to weigh in here with alternative opinions :-)
One option is to track the py3k branch of pypy as a separate git submodule, eg. ./deps/py3k, and add targets to the makefile for building both py2 and py3 easily.

I would say the makefile should be the minimum. No reason to actively avoid having builds of py3.
But personally I think py3 should be the default. We have no baggage at present, no reason to hold back. 3.4 :+1: 3.5 with type hints and all the trimmings :+1: ok... maybe just 'latest pypy3' will suffice.

Personally, I don't want to lose python2 support.  I wouldn't mind having a python3 build too, but I mildly dislike python3 as a language, and twisted+nevow (which I have running on pypyjs over top of WebSockets) doesn't support python3; twisted itself is only partially runnable on python3.

Yes to both! PyPy isn't great with Python 3 yet, so maybe it shouldn't be the default here, but Python 3 will happen sooner or later so we might as well jump aboard.

PyPy3 isn't that well supported, and there's a few things like numpy that are... Difficult.
Personally, I love Python 3, and I think support is almost there for most things.
A makefile for both seems the best compromise in my mind.

Cool, sounds like there's a pretty solid argument for building both py2 and py3 as different targets in the makefile.  I'll see about cleaning up the hackery I did to get it building for the pycon talk and commit something.

:+1:

As of https://github.com/pypyjs/pypyjs/commit/073efed7415238f34810db5a23b4b64efbbcebbe there are targets in the Makefile for building a (very experimental) python3 version:
> make release3

I'll probably keep tweaking the process and maybe rename the target if I can think of something better, but wanted to get the initial version of this committed.  Last time I had this working, I carelessly tossed it all away and had to start over...

Is there any way to get access to the pypy3 version without building it yourself?  Any chance someone could package a pypyjs3 npm module?


chore: yaml lint

Ran yamllint and applied linting (https://yamllint.readthedocs.io/en/stable/)

nice! good addition


ARROW-16574: [C++] TSAN failure in arrow-ipc-read-write-test

When reading multiple batches at the same time it was possible for concurrent attempts to increment ReadStats counters.

CI failures appear unrelated (although this is the first time I've seen this Travis error).


Standardizing the LGTM process for docs

The bot is currently running on this repository, performing assignment of PRs, but we haven't turned on the submit-queue yet. We currently have two LGTM labels, Docs LGTM and Tech Review LGTM. This is different from other repositories where we just require a single LGTM label.

Does it make sense to have a different LGTM process for docs as opposed to other repositories?
Can we switch to just a single LGTM label for docs as well?
Would mungedocs completely remove the need for a Docs LGTM, and a separate tech & docs review?

cc @bgrant0607 @lavalamp @pwittrock @jaredbhatti

IMO:
Yes, the different process makes sense here, and we should not switch to a
single LGTM. Mungedocs does not substitute for a human review for writing
quality.
On Thu, Aug 4, 2016 at 1:57 PM, Anirudh Ramanathan<EMAIL_ADDRESS>
wrote:

The bot is currently running on this repository, performing assignment of
PRs, but we haven't turned on the submit-queue yet. We currently have two
LGTM labels, Docs LGTM and Tech Review LGTM. This is different from other
repositories where we just require a single LGTM label.

Does it make sense to have a different LGTM process for docs as
opposed to other repositories?
Can we switch to just a single LGTM label for docs as well?
Would mungedocs completely remove the need for a Docs LGTM?

cc @bgrant0607 https://github.com/bgrant0607 @lavalamp
https://github.com/lavalamp @pwittrock https://github.com/pwittrock
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/kubernetes.github.io/issues/968, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAnglqMsb9miYjPe33Ubon8if-0lrAVDks5qclI9gaJpZM4JdHZd
.

@lavalamp @foxish No, I don't want a different process than other repos, both for a consistent contributor experience and because the previous process was an impediment to progress.
The majority of PRs aren't creating new docs. They fix bugs and update details.
Additionally, we already have 2-phase reviews, LGTM and approval, and @kelseyhightower has suggested an iterative process where we ingest technical content first and then rework it in subsequent PRs.
We could easily create a special process for wholly new documents, where such PRs would be directed to a writer first for high-level guidance. That would be easy to automate.

@foxish +1 to what Brian said.  Stick with the same lgtm process as the main repo (from eng for technical correctness).  The process for introducing a technical editor is TBD, but the former process resulted in docs not getting looked at for 3+ months.

I prefer the two step process for docs.  Tech writers and reviewers should review content on the site.  I'm certainly open to modifying the existing process to improve things, but without content review we'll continue to accrue technical debt and bad organization in our docs.

@jaredbhatti We are implementing a 2-step process for all repositories. I am saying that I don't want a 3-step process, and I don't want a 2-step process that is mechanically different from other repositories.

I prefer the two step process for docs. Tech writers and reviewers should review content on the site. I'm certainly open to modifying the existing process to improve things, but without content review we'll continue to accrue technical debt and bad organization in our docs.

Is there any reason the docs review can't be offline? We could conceivably create a webhook (or a mungegithub hook) that marks a doc as 'dirty/needing-review' when new doc changes are submitted.

bad organization in our docs.

If we can figure out a clear and consistent organization system for our docs, we could encode this as part of md-check. Combined with templating, we enforce invariants on our docs automatically.

We can also automatically categorize PRs, by size (which we do already), by whether they add new files, etc.

I suggest we close this issue for now, and Foxish and I work on the right process to take this on.  I'm standardizing how issues and PRs are being addressed, and I'm very reluctant to automate a process that's still uncertain.
Also, there's been no progress on this issue for over 6 months.


Kubernetes CRD - Headers middleware doesn't work

Do you want to request a feature or report a bug?
Bug
What did you do?
Create a headers middleware:
apiVersion: traefik.containo.us/v1alpha1
kind: Middleware
metadata:
  name: default-headers
  namespace: production
spec:
  headers:
    sslRedirect: true
    sslProxyHeaders: true
---

What did you expect to see?
Should work as documented. Additionally, the whole trafik container has stopped working.
What did you see instead?
error in the traefik container logs:
2020-06-28T13:22:47.927674996Z E0628 13:22:47.927478       1 reflector.go:153] pkg/mod/k8s.io/client-go@v0.17.3/tools/cache/reflector.go:105: Failed to list *v1alpha1.Middleware: v1alpha1.MiddlewareList.Items: []v1alpha1.Middleware: v1alpha1.Middleware.Spec: v1alpha1.MiddlewareSpec.Headers: dynamic.Headers.SSLProxyHeaders: ReadMapCB: expect { or n, but found t, error found in #10 byte of ...|Headers":true,"sslRe|..., bigger context ...|09db9eda0"},"spec":{"headers":{"sslProxyHeaders":true,"sslRedirect":true}}}],"kind":"MiddlewareList"|...

Output of traefik version: (What version of Traefik are you using?)
Traeffik: 2.2.1

What is your environment & configuration (arguments, toml, provider, platform, ...)?
I use no route or ingress, I just added the middleware.

I used the wrong schema. sslProxyHeaders is a map of strings. The error code could be more descriptive :smile:


New version 3.4.0

Type your response on top of this email to respond to this case. Learn Email Commands Here - https://support.desk.com/customer/portal/articles/1191712-reply-via-email-commands
Case Assignment Notification - Case #13953 ( https://affirm.desk.com/web/agent/case/13953 )
Affirm | Apr 25, 2017 08:57PM UTC

Case #13953
Customer: Affirm/Magento_Affirm
Subject: [Affirm/Magento_Affirm] New version 3.4.0 (#26)
Case Information (13953):
Subject: [Affirm/Magento_Affirm] New version 3.4.0 (#26)
Description:
Status: Open
Priority: 4
Assigned Group: MTS

Case History
goatmad  at APR 25, 2017 | 01:57PM PDT:
You can view, comment on, or merge this pull request online at:
https://github.com/Affirm/Magento_Affirm/pull/26
-- Commit Summary --

New Version 3.4.0
Composer support

-- File Changes --
M Makefile (2)
M README.md (34)
M composer.json (1)
A extension/app/code/community/Affirm/Affirm/Block/Product/List.php (75)
M extension/app/code/community/Affirm/Affirm/Block/Promo/AsLowAs/Checkout.php (68)
M extension/app/code/community/Affirm/Affirm/Block/Promo/AsLowAs/Product.php (41)
M extension/app/code/community/Affirm/Affirm/Helper/Data.php (14)
M extension/app/code/community/Affirm/Affirm/Helper/Mfp.php (345)
M extension/app/code/community/Affirm/Affirm/Helper/Promo/AsLowAs.php (87)
M extension/app/code/community/Affirm/Affirm/Helper/Promo/Data.php (13)
M extension/app/code/community/Affirm/Affirm/Model/Credential.php (2)
M extension/app/code/community/Affirm/Affirm/Model/Credential/Production.php (7)
M extension/app/code/community/Affirm/Affirm/Model/Credential/Sandbox.php (7)
M extension/app/code/community/Affirm/Affirm/Model/Order/Observer.php (22)
M extension/app/code/community/Affirm/Affirm/Model/Order/Observer/AfterSaveOrder.php (22)
M extension/app/code/community/Affirm/Affirm/Model/Payment.php (23)
M extension/app/code/community/Affirm/Affirm/controllers/PaymentController.php (6)
M extension/app/code/community/Affirm/Affirm/etc/config.xml (34)
M extension/app/code/community/Affirm/Affirm/etc/system.xml (1096)
A extension/app/code/community/Affirm/Affirm/sql/affirm_setup/mysql4-upgrade-3.3.1-3.3.2.php (109)
A extension/app/code/community/Affirm/Affirm/sql/affirm_setup/mysql4-upgrade-3.3.2-3.3.3.php (100)
A extension/app/code/community/Affirm/Affirm/sql/affirm_setup/mysql4-upgrade-3.3.3-3.3.4.php (81)
A extension/app/code/community/Affirm/Affirm/sql/affirm_setup/mysql4-upgrade-3.3.5-3.3.6.php (39)
M extension/app/design/frontend/base/default/layout/affirm/affirm.xml (42)
M extension/app/design/frontend/base/default/template/affirm/affirm/payment/form/affirm.phtml (7)
M extension/app/design/frontend/base/default/template/affirm/promo/aslowas/checkout.phtml (31)
A extension/app/design/frontend/base/default/template/affirm/promo/aslowas/list.phtml (11)
M extension/app/design/frontend/base/default/template/affirm/promo/aslowas/product.phtml (33)
M extension/package.xml (15)
M extension/skin/frontend/base/default/js/affirm/aslowas.js (7)

-- Patch Links --
https://github.com/Affirm/Magento_Affirm/pull/26.patch
https://github.com/Affirm/Magento_Affirm/pull/26.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/Affirm/Magento_Affirm/pull/26

This message was sent to<EMAIL_ADDRESS>in reference to Case #13953


Start logging a warning for env passed into factories.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1034  👈
#1033
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @rohinb2 and the rest of your teammates on  Graphite

Merge activity

Aug 8, 11:51 AM EDT: @rohinb2 started a stack merge that includes this pull request via Graphite.


[cxx-interop] Mark types with a destructor a non-trivial.

Any C++ type that isn't trivially copyable is now also not a trivial type. This will preserve the destructor (among other things).

@gottesmm to review SILGen changes.

@gribozavr friendly ping. This PR no longer has any SILGen changes.

@swift-ci please smoke test and merge

@swift-ci please smoke test and merge


NO-JIRA: test/e2e: constrain actions to context, timeout

test/e2e: constrain actions to context, timeout
Asynchronous actions that serve to make test assertions, etc, must be
constrained by the test context and/or a timeout - otherwise, even tests
that get interrupted will hang forever on these cases.
Signed-off-by: Steve Kuznetsov<EMAIL_ADDRESS>
test/e2e: explicitly constrain pod streams
Signed-off-by: Steve Kuznetsov<EMAIL_ADDRESS>
/assign @sjenning

/retest

/approve
/lgtm

/test e2e-aws

/retest

/retest
 error: unable to iterate over layer sha256:019f3c6668f3f04466aa081183f5b6fee5b931b3daeae70e60fed011f249144f from registry.build02.ci.openshift.org/ci-op-l8b2jrhb/release:latest: stream error: stream ID 11; INTERNAL_ERROR; received from peer

/retest


migrate from JRDF to JENA library

To fix the #1560

@thadguidry According to this:
Much of the functionality is accessed via the Jena Model API; direct calling of the RIOT subsystem isn't needed.
I tried to remove few of jars and all lead to exception when loading

@jackyq2015 is this an exposed option or not ?
To aid in checking for errors in UTF8-encoded files, there is a utility which reads a file of bytes as UTF8 and checks the encoding.
utf8 -- read bytes as UTF8

@thadguidry I cannot see the RIOT is a exposed option.
For the utf8 part, how is related to this change?

@jackyq2015 forget it.  we can deal with that option later.


update backup e2e test and add cronBackup e2e test

Signed-off-by: Liucw<EMAIL_ADDRESS>
What type of PR is this?
/kind feature

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes https://github.com/kubeclipper/kubeclipper/issues/75
Special notes for reviewers:

Does this PR introduced a user-facing change?

None

Additional documentation, usage docs, etc.:

@lixd @x893675

Codecov Report

Merging #469 (30b5419) into release-1.3 (34aff66) will decrease coverage by 0.02%.
The diff coverage is 0.00%.

@@               Coverage Diff               @@
##           release-1.3     #469      +/-   ##
===============================================
- Coverage        12.30%   12.28%   -0.03%
===============================================
  Files              109      109
  Lines            16767    16801      +34
===============================================
  Hits              2064     2064
- Misses           14456    14490      +34
  Partials           247      247

Impacted Files
Coverage Δ

pkg/simple/client/kc/api.go
0.00% <0.00%> (ø)

pkg/simple/client/kc/scheme.go
0.00% <ø> (ø)

/cc @x893675

/approve


Add extra information for TestNG users

SSIA

I now propose this change be abandoned in favor of #439. That is, let's make our CLI do the right thing for customers, instead of them using our CLI differently when using TestNG.


The values that I'm getting for the weight are multiplied by 2.

The values that the esp32 is obtaining from my scale are simply double the value.
If I measure 80Kg for example on the scale , the value that the esp32 publishes is 160Kg.
I'm not sure if this is the case with the impedance also , as I have not looked at it yet and I don't know what value I should expect.

I have the same problem.

I confirm that fix works.


Added Python interfaces to some Ignition Gazebo methods

Signed-off-by: ahcorde<EMAIL_ADDRESS>🎉 New feature
Summary
Added Python interfaces to same Ignition Gazebo methods with pybind11
Requires https://github.com/ignitionrobotics/ign-math/pull/280
Related with this issue https://github.com/ignitionrobotics/ign-gazebo/issues/789#issuecomment-945612336
Test it
I created an example examples/python/helperFixture.py.
Export your python path:
export PYTHONPATH=$PYTHONPATH:<your workspace>/install/lib/python/

Run the example:
python3 <your workspace>/src/ign-gazebo/examples/python/testFixture.py

Checklist

[x] Signed all commits for DCO
[ ] Added tests
[x] Added example and/or tutorial
[x] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[x] codecheck passed (See contributing)
[x] All tests passed (See test coverage)
[x] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge

I made some changes that might be conflictive.

EventManager: Changed unique_ptr to shared_ptr in a private member to be able to copy the class
TextureFixture: Changed some reference to pointers

some integration tests have some changes: Spherical_coordinates and thruster

I can open a different PRs, these PRs might require to tick-tock some of the methods

I tested this branch against ign-math6.9.3~pre2 debs, and it works well! :tada:

A couple of problems in Jenkins CI.

The test fails (but it passes on GitHub actions)

213: Test command: /usr/bin/python3 "/home/jenkins/workspace/ignition_gazebo-ci-pr_any-ubuntu_auto-amd64/ign-gazebo/python/test/testFixture_TEST.py"
213: Environment variables:
213:  PYTHONPATH=/usr/lib/python/
213:  LD_LIBRARY_PATH=/usr/lib:/usr/local/lib/x86_64-linux-gnu
213: Test timeout computed to be: 1500
213: Traceback (most recent call last):
213:   File "/home/jenkins/workspace/ignition_gazebo-ci-pr_any-ubuntu_auto-amd64/ign-gazebo/python/test/testFixture_TEST.py", line 19, in <module>
213:     from ignition.common import set_verbosity
213: ModuleNotFoundError: No module named 'ignition.common'
213/213 Test #213: testFixture_TEST.py ....................................***Failed    0.23 sec

Jenkins doesn't report the failure (CC @j-rivero )

For packaging, we'll need to do the same as https://github.com/ignition-release/ign-math6-release/pull/6 for ign-gazebo6-release. @j-rivero said he can help in the coming days. The plan is to install the ign-common and sdformat bindings as if they came from those packages, and if we ever move the bindings there, we should be able to flip the switch without affecting users.

This pull request has been mentioned on Gazebo Community. There might be relevant details there:
https://community.gazebosim.org/t/new-ignition-releases-2022-03-25-fortress-edifice-citadel/1343/1


chore: improve code coverage

closes #348

@mabdh @StewartJingga  @scortier any suggestions for further improving the code coverage?? Most of the files with low coverage that I can see at the moment are the ones where we can't test a given set of functions with mocks or may require setting up a service (like bigquery, tableau, etc).

@GrayFlash this is already good enough to have 75 % code coverage.
Have you seen the coverage report here? https://coveralls.io/github/odpf/meteor?branch=improve-code-coverage
apart from plugins files there are several files that could be improved.

@mabdh have worked on increasing the coverage across the agent, registry and recipe package, by adding tests for Validation functions as well. Please check it once.


Rotating while positional tracking.

Preliminary Checks

[x] This issue is not a duplicate. Before opening a new issue, please search existing issues.
[X] This issue is not a question, feature request, or anything other than a bug report directly related to this project.

Description
When using any type of positional tracking samples (c++, python, both in spatial and positional tracking samples) camera thinks, it is rotating or moving. But in real life, camera is stationary. I tried recalibrating cammera and moving to differently lit environments, without any success. Sometimes it moves irradicly, sometimes it performs quite regural spiral/circle:

Steps to Reproduce
1.Keeping camera in real life stationary.
2.Running any type of position-dependent demos.
Expected Result
Position of camera in spatial_mapping/positional tracking is stationary.
Actual Result
Camera in positional tracking moves irradicly/in a spiral
ZED Camera model
ZED2
Environment
OS: Ubuntu 20.04
CPU: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
GPU: NVIDIA GeForce MX450
ZED SDK VERSION: 3.7.0

Tried samples in both Python and c++ variant.

Anything else?
No response

It seems position sensor is broken.

@CreaM129129 have you written an email to<EMAIL_ADDRESS>describing your problem?

Yes, this is why I closed the issue.
After ZED_Calibration --calib_imu  not fixing the problem, I assume position senzor on camera is broken.


installation instruction

In the installation, the step three doesn't work.
 Directory 'tfs' is not installable. File 'setup.py' not found.
I'm using ubuntu 16.04
Thanks

Hi,
Thanks for spotting this.  You can either type "pip install ." in the copy you've got, or pull the latest update from git and use "pip install tfs" as per the instructions.


Enhance the UI of the website and introduce Routing

I can try enhancing the UI with animations and better colourspace
Please assign this to me


Usage of the navigation for controller in Areas

I use Areas in my project. I have the Settings area and inside I have a HomeController. Is that possible to reference like Settings/Home?

I saw one open issue regarding areas so I am closing that.

I admit I have not been using areas so it may not work for areas yet and I'm not that familiar with working with areas yet. I will make a deal with you, if fork this repo and add an area or 2 areas to the existing demo app and do a pull request. then I will implement the support and fix the demo so the areas are included in the navigation.

areas is now supported in version 1.0.2-rc20160901
I have also added an area to the demo app and included it in the navigation.xml file for reference


LMS511

Hello!
System:
ros1 (qt creator)
Ubuntu 18.04.5 LTS (bionic)
sick_scan_xd
LMS511-10100S PRO
Problem: When executing "oslaunch sick_scan sick_lms_5xx.launch hostname:=<IP_ADDRESS>" I get the following error:
### ## ERROR SickScanMessages::parseLIDoutputstateMsg(): received 89 byte with invalid format (/home/soler/sick_scan_ws/src/sick_scan_xd/driver/src/sick_scan_messages.cpp:142): \x02\x02\x02\x02\x00\x00\x00PsSN LIDoutputstate 0 0 0 A 0 A 0 A 0 A 0 A 0 A 2 0 2 0 2 0 2 0 2 0 2 0 2 0 2 0 0w
[ WARN] [1658312043.413417880]: ## ERROR SickScanCommon: parseLIDoutputstateMsg failed, received 89 byte LIDoutputstate \x02\x02\x02\x02\x00\x00\x00PsSN LIDoutputstate 0 0 0 A 0 A 0 A 0 A 0 A 0 A 2 0 2 0 2 0 2 0 2 0 2 0 2 0 2 0 0w
In the launch file  param name="use_binary_protocol" type="bool" value="true"

Thanks for reporting! A very similar issue #13 could be solved by using the most recent sick_scan_xd release. Please update sick_scan_xd sources and rebuild. If the error remains, please let us know.

We update sick_scan_xd sources and rebuild, but the problem remains

Спасибо за отчет! Очень похожая проблема № 13 может быть решена с помощью самой последней версии SCAN_SCAN_XD. Пожалуйста, обновите исходники Scan_scan_xd и пересоберите. Если ошибка остается, сообщите нам об этом.

Обновляем исходники Scan_scan_xd и пересобираем, но проблема остается.
LMS511-10100S PRO V1.30 - 30.08.2012

Thanks for the update. The LIDoutputstate message received from the lidar looks like an incorrect mix of a binary and ascii telegram. This might be caused by old firmware. https://www.sick.com/no/en/detection-and-ranging-solutions/2d-lidar-sensors/lms5xx/lms511-10100-pro/p/p215941 publishes firmware version V2.10. Can you update to the most recent firmware version?

Thanks for the update. The LIDoutputstate message received from the lidar looks like an incorrect mix of a binary and ascii telegram. This might be caused by old firmware. https://www.sick.com/de/en/detection-and-ranging-solutions/2d-lidar-sensors/lms5xx/lms511-10100-pro/p/p215941 publishes firmware version V2.10. Can you update to the most recent firmware version?

We try update to the most recent firmware version, but we get error

Thanks. Can you update the firmware with the more powerful SOPAS Engineering Tool (SOPAS ET)?

Thanks. Can you update the firmware with the more powerful SOPAS Engineering Tool (SOPAS ET)?

Can you help me? How update device firmware with SOPAS ET?

You can find a description e.g. on https://www.manualslib.com/manual/2062950/Sick-Dl100-Pro-Ssi.html?page=46#manual or try the SICK portal https://supportportal.sick.com/

You can find a description e.g. on https://www.manualslib.com/manual/2062950/Sick-Dl100-Pro-Ssi.html?page=46#manual or try the SICK portal https://supportportal.sick.com/

Cannot select boot as described in the manual.

Please contact SICK support. They can help with SOPAS ET and firmware updates.

Please contact SICK support. They can help with SOPAS ET and firmware updates.

Thank you

Closed due to inactivity.