Basic auth and/or ssh url support for cargo aggregate

Using cargo-vet to aggregate audit sources from private repositories can be quite difficult, as there's no way of accessing an audit file from a private source without doing something like putting basic auth information in the URL itself, which will then result in the username:password pair being spread all over in the form of aggregated-from keys.
The main approaches to addressing this use case I see are:

A command line flag (or two) for specifying basic auth credentials. (Or maybe they could be read from stdin?)
Support fetching audit files via ssh, which would delegate the authentication to the ssh-agent

What are your thoughts on this? I'd be happy to give writing a PR for this functionality a go

SSH sounds a little cleaner to me, though I'm not sure whether this would involve pulling in a bunch of dependencies or if we can lean on what cargo already does. @mystor WDYT?

I don't believe we currently depend on libssh2, which would probably be the easiest way to fetch something with ssh. From a quick check locally this would pull in: ssh2, libssh2-sys, lock_api, openssl-sys, parking_lot, parking_lot_core, and scopeguard.
We could also probably do something without these dependencies if we're fine with just invoking scp on the command line and using temporary files.

Generally speaking I'd rather not take all those dependencies. I think I'm fine with either a command-line scp solution or an HTTP basic auth solution.

In the interim, how about adding support for the file:// URL scheme?
As far as I can tell it's not possible to point cargo vet aggregate or the imports table in config.toml to a local file (please let me know if I'm missing something), which would make it easier to create an external workaround for pulling from private repositories.
I'd be happy to put a PR in if there's interest in the change.

Support just for file URIs would likely be quite difficult to use, as those URIs are absolute, which isn't great for paths in a repository due to it not being cloned in a consistent location. The solution for local paths would probably need to support relative paths, which would involve tracking things like base URIs for what resources we're loading, which is a larger change.
I think the easiest way forward here is probably a PR adding support for the ssh:// protocol by delegating to scp. This would require adding support to the methods in https://github.com/mozilla/cargo-vet/blob/56ebfded2d27d6c28a56832aaae1dc99b41c4311/src/network.rs.

I am also interested in being able to use cargo vet aggregate with non public repos. This would allow us to create a public supply-chain repo that is aggregated from several internal ones.
SSH would work but I could also imagine a solution where the fetcher is using the .netrc file like curl.


Collapse inactive devices by default

and some refactoring to lessen duplicate markup and improve readability.
Before the devices were all expanded when you load the page, which makes you scroll to get to the info you want - like if you are fermenting, and not brewing.
This merge request collapses inactive devices so the active ones are more prominent.

Great suggestion and it also helped me see the iSpindel bug (which I am unable to test). But you are too fast. I saw you had made partial mods so went and made the changes locally. What's the preferred approach - commit your suggestions here, or merge them?

To resolve the "merge checks" either I need to "approve changes" (just did) or you could have "accepted changes" 1 by 1 in a "batch".
Though things look good with your local committed changes. Thank you sir.


ERROR: Unable to extract video info

Good evening !
When I try to download a video : this is the error message I receive :
sab@sab-HP-14-TS-Notebook-PC:~$ youtube-dl http://www.dailymotion.com/video/x221sqs_les-incorruptibles-s-01-e-22-la-dame-aux-oiseaux_shortfilms
[dailymotion] x221sqs: Downloading webpage
[dailymotion] x221sqs: Downloading embed page
ERROR: Unable to extract video info; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
sab@sab-HP-14-TS-Notebook-PC:~$ youtube-dl --version
2016.10.07
sab@sab-HP-14-TS-Notebook-PC:~$

I've purged and removed youtube-dl then I've installed it again but the message still the same :(
OS : Ubuntu 16.04
Have a nice evening !
Bye
Sab

`

youtube-dl -U
youtube-dl is up-to-date (2016.10.07)

youtube-dl --verbose http://www.dailymotion.com/video/k4ZRnWwGOQDIjWk7xkq
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['--verbose', 'http://www.dailymotion.com/video/k4ZRnWwGOQDIjWk7xkq']
[debug] Encodings: locale cp1252, fs mbcs, out cp850, pref cp1252
[debug] youtube-dl version 2016.10.07
[debug] Python version 3.4.4 - Windows-10-10.0.14393
[debug] exe versions: none
[debug] Proxy map: {}
[dailymotion] k4ZRnWwGOQDIjWk7xkq: Downloading webpage
[dailymotion] k4ZRnWwGOQDIjWk7xkq: Downloading embed page
ERROR: Unable to extract video info; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpayz9vyze\build\youtube_dl\YoutubeDL.py", line 694, in extract_info
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpayz9vyze\build\youtube_dl\extractor\common.py", line 356, in extract
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpayz9vyze\build\youtube_dl\extractor\dailymotion.py", line 237, in _real_extract
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpayz9vyze\build\youtube_dl\extractor\common.py", line 659, in _search_regex
youtube_dl.utils.RegexNotFoundError: Unable to extract video info; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

`

same thing here :p

I got the same error:
youtube-dl --verbose -F http://dai.ly/x4x067d
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'--verbose', u'-F', u'http://dai.ly/x4x067d']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2016.10.07
[debug] Python version 2.6.6 - Linux-2.6.32-642.4.2.el6.x86_64-x86_64-with-centos-6.8-Final
[debug] exe versions: ffmpeg 2.6.4, ffprobe 2.6.4
[debug] Proxy map: {}
[generic] x4x067d: Requesting header
[redirect] Following redirect to http://www.dailymotion.com/video/x4x067d_%25E9%2594%25B5%25E9%2594%25B5%25E4%25B8%2589%25E4%25BA%25BA%25E8%25A1%258C-20161011-%25E5%25BC%25A0%25E9%259D%2593%25E9%25A2%2596%25E6%25AF%258D%25E4%25BA%25B2%25E5%258F%2591%25E5%2585%25AC%25E5%25BC%2580%25E4%25BF%25A1-%25E6%2598%258E%25E7%25A1%25AE%25E5%258F%258D%25E5%25AF%25B9%25E5%25A5%25B3%25E5%2584%25BF%25E4%25B8%258E%25E5%2586%25AF%25E8%25BD%25B2%25E5%25A9%259A%25E4%25BA%258B_tv
[dailymotion] x4x067d: Downloading webpage
[dailymotion] x4x067d: Downloading embed page
ERROR: Unable to extract video info; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 694, in extract_info
ie_result = ie.extract(url)
File "/usr/bin/youtube-dl/youtube_dl/extractor/common.py", line 356, in extract
return self._real_extract(url)
File "/usr/bin/youtube-dl/youtube_dl/extractor/dailymotion.py", line 237, in _real_extract
'video info', flags=re.MULTILINE),
File "/usr/bin/youtube-dl/youtube_dl/extractor/common.py", line 659, in _search_regex
raise RegexNotFoundError('Unable to extract %s' % _name)
RegexNotFoundError: Unable to extract video info; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Thanks for the report. Dailymotion support will be back in the next version.


ENOENT error in 14.0.0

ENOENT: no such file or directory, rename 'C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64\stox-win32-x64\electron.exe' -> 'C:\Users<user>\AppData\Local\Temp\electron-packager\win32-x64\stox-win32-x64\stox.exe'
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>package-win: electron-packager . <appname> --platform win32 --arch x64 --out dist/ --overwrite
npm ERR! Exit status 1
npm ERR!

Thanks for filing an issue! In order to help you with your problem, we're going to need more information about it. In particular:

Operating System (Platform and Version) e.g. macOS 10.13.6 / Windows 10 (1803) / Ubuntu 18.04 x64

Last Known Working Electron Packager version (if applicable) e.g. 11.0.0

Console output when you run electron-packager with the environment variable DEBUG=electron-packager (instructions for Windows and non-Windows). Please include the stack trace if one exists.

What does your package.json file look like?

Please provide either a failing minimal testcase (with code) or detailed steps to reproduce your
problem. Using electron-quick-start is a good starting point.

using electron packager 14.0.0, than it crashed. had to downgrade to 13.1.1 then it worked fine. thanks
package
"main": "index.js",
"scripts": {
"start": "electron .",
"package-win": "electron-packager . stox --platform win32 --arch x64 --out dist/ --overwrite  --asar",
From: Mark Lee<EMAIL_ADDRESS>Sent: 01 July 2019 15:40
To: electron-userland/electron-packager<EMAIL_ADDRESS>Cc: Skålevik, Åsmund<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [electron-userland/electron-packager] ENOENT error in 14.0.0 (#1024)
Thanks for filing an issue! In order to help you with your problem, we're going to need more information about it. In particular:
·        Operating System (Platform and Version) e.g. macOS 10.13.6 / Windows 10 (1803) / Ubuntu 18.04 x64
·        Last Known Working Electron Packager version (if applicable) e.g. 11.0.0
·        Console output when you run electron-packager with the environment variable DEBUG=electron-packager (instructions for Windowshttps://github.com/visionmedia/debug#windows-command-prompt-notes and non-Windowshttps://en.wikipedia.org/wiki/Environment_variable#Unix). Please include the stack trace if one exists.
·        What does your package.json file look like?
·        Please provide either a failing minimal testcase (with code) or detailed steps to reproduce your
problem. Using electron-quick-starthttps://github.com/electron/electron-quick-start is a good starting point.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/electron-userland/electron-packager/issues/1024?email_source=notifications&email_token=ACWW3K7AYAEA45SEA2IEFYLP5ICKLA5CNFSM4H4RSAMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY6E5HQ#issuecomment-507268766, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACWW3K34IWMG5CVZOWMVZHTP5ICKLANCNFSM4H4RSAMA.

Can you please provide the following information:

Console output when you run electron-packager with the environment variable DEBUG=electron-packager (instructions for Windows and non-Windows). Please include the stack trace if one exists.

ok,  i have added console output (Using cross-env and DEBUG for electron packager 13.1.1 and <IP_ADDRESS> It crashes in 14.0.0 when renaming the electron.exe. This seems to work o.k in 13.1.1

cross-env DEBUG=electron-packager electron-packager . stox --platform win32 --arch x64 --out dist/ --overwrite  --asar

electron-packager Electron Packager 13.1.1
electron-packager Node v10.16.0
electron-packager Host Operating system: win32 (x64) +0ms
electron-packager Packager Options: {"_":[".","stox"],"deref-symlinks":true,"derefSymlinks":true,"download":{"strictSSL":true,"strict-ssl":true},"prune":true,"platform":"win32","arch":"x64","out":"dist/","overwrite":true,"asar":true,"dir":".","name":"stox","protocols":[]} +4ms
electron-packager Target Platforms: win32 +1ms
electron-packager Target Architectures: x64 +0ms
electron-packager Inferring appVersion from version in E:\Projects\StoxProject\StoX\package.json +0ms
electron-packager Inferring win32metadata.CompanyName from author in E:\Projects\StoxProject\StoX\package.json +1ms
electron-packager Inferring target Electron version from electron in E:\Projects\StoxProject\StoX\package.json +4ms
electron-packager Application name: stox +26ms
electron-packager Target Electron version: 5.0.6 +1ms
electron-packager Ignored path regular expressions: [ '/\.git($|/)', '/node_modules/\.bin($|/)', '\.o(bj)?$' ] +0ms
electron-packager Downloading Electron with options {"strictSSL":true,"strict-ssl":true,"platform":"win32","arch":"x64","version":"5.0.6"} +0ms
electron-packager Removing dist\stox-win32-x64 due to setting overwrite: true +341ms
Packaging app for platform win32 x64 using electron v5.0.6
electron-packager Creating C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64-template +90ms
electron-packager Extracting C:\Users\aasmunds\AppData\Local\electron\Cache\electron-v5.0.6-win32-x64.zip to C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64-template +2ms
electron-packager Initializing app in C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64\stox-win32-x64 from C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64-template template +0ms
electron-packager Ignored paths based on the out param: [ 'E:\Projects\StoxProject\StoX\dist' ] +3s
electron-packager Running asar with the options {} +1m
electron-packager Renaming electron.exe to stox.exe in C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64\stox-win32-x64 +29s
electron-packager Running rcedit with the options {"version-string":{"FileDescription":"stox","InternalName":"stox","OriginalFilename":"stox.exe","ProductName":"stox","CompanyName":"IMR institute"},"file-version":"1.0.0","product-version":"1.0.0"} +0ms
electron-packager Moving C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64\stox-win32-x64 to dist\stox-win32-x64 +2s
Wrote new app to dist\stox-win32-x64

cross-env DEBUG=electron-packager electron-packager . stox --platform win32 --arch x64 --out dist/ --overwrite  --asar

electron-packager Electron Packager 14.0.0
electron-packager Node v10.16.0
electron-packager Host Operating system: win32 (x64) +0ms
electron-packager Packager Options: {"_":[".","stox"],"deref-symlinks":true,"derefSymlinks":true,"download":{"rejectUnauthorized":true,"reject-unauthorized":true},"junk":true,"prune":true,"platform":"win32","arch":"x64","out":"dist/","overwrite":true,"asar":true,"dir":".","name":"stox","protocols":[]} +4ms
electron-packager Target Platforms: win32 +1ms
electron-packager Target Architectures: x64 +0ms
electron-packager Inferring appVersion from version in E:\Projects\StoxProject\StoX\package.json +0ms
electron-packager Inferring win32metadata.CompanyName from author in E:\Projects\StoxProject\StoX\package.json +1ms
electron-packager Inferring target Electron version from electron in E:\Projects\StoxProject\StoX\package.json +4ms
electron-packager Application name: stox +23ms
electron-packager Target Electron version: 5.0.6 +0ms
electron-packager Ignored path regular expressions: [ '/\.git($|/)', '/node_modules/\.bin($|/)', '\.o(bj)?$' ] +0ms
electron-packager Downloading Electron with options {"rejectUnauthorized":true,"reject-unauthorized":true,"platform":"win32","arch":"x64","version":"5.0.6","artifactName":"electron"} +0ms
electron-packager Removing dist\stox-win32-x64 due to setting overwrite: true +10ms
Packaging app for platform win32 x64 using electron v5.0.6
electron-packager Creating C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64-template +140ms
electron-packager Extracting C:\Users\aasmunds\AppData\Local\electron\Cache\electron-v5.0.6-win32-x64.zip to C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64-template +3ms
electron-packager Initializing app in C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64\stox-win32-x64 from C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64-template template +0ms
electron-packager Ignored paths based on the out param: [ 'E:\Projects\StoxProject\StoX\dist' ] +760ms
electron-packager Running asar with the options {} +58s
electron-packager Renaming electron.exe to stox.exe in C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64\stox-win32-x64 +32s
ENOENT: no such file or directory, rename 'C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64\stox-win32-x64\electron.exe' -> 'C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64\stox-win32-x64\stox.exe'
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>package-win: cross-env DEBUG=electron-packager electron-packager . stox --platform win32 --arch x64 --out dist/ --overwrite  --asar
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>package-win script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      C:\Users\aasmunds\AppData\Roaming\npm-cache_logs\2019-07-02T07_07_54_497Z-debug.log
From: Mark Lee<EMAIL_ADDRESS>Sent: 01 July 2019 17:28
To: electron-userland/electron-packager<EMAIL_ADDRESS>Cc: Skålevik, Åsmund<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [electron-userland/electron-packager] ENOENT error in 14.0.0 (#1024)
Can you please provide the following information:

Console output when you run electron-packager with the environment variable DEBUG=electron-packager (instructions for Windowshttps://github.com/visionmedia/debug#windows-command-prompt-notes and non-Windowshttps://en.wikipedia.org/wiki/Environment_variable#Unix). Please include the stack trace if one exists.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/electron-userland/electron-packager/issues/1024?email_source=notifications&email_token=ACWW3KZCGNMO3WBP4WGU57DP5IO6PA5CNFSM4H4RSAMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY6PT2Q#issuecomment-507312618, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACWW3K52CC4GXRI2RW7F6ATP5IO6PANCNFSM4H4RSAMA.

Exactly what version of Windows are you running?

$ cross-env DEBUG=electron-packager electron-packager . stox --overwrite --asar=true --platform=win32 --arch=x64 --out=release-builds --versi
on-string.CompanyName=HI --version-string.FileDescription=HI --version-string.ProductName="StoX"
WARNING: --asar does not take any arguments, it only has sub-properties (see --help)
electron-packager Electron Packager 14.1.1
electron-packager Node v10.16.0
electron-packager Host Operating system: win32 10.0.17763 (x64) +0ms
electron-packager Packager Options: {"_":[".","stox"],"overwrite":true,"asar":true,"platform":"win32","arch":"x64","out":"release-builds","version-string":{"CompanyName":"HI","FileDescription":"HI","ProductName":"StoX"},"versionString":{"companyName":"HI","fileDescription":"HI","productName":"StoX"},"deref-symlinks":true,"derefSymlinks":true,"download":{"rejectUnauthorized":true,"reject-unauthorized":true},"junk":true,"prune":true,"dir":".","name":"stox","protocols":[]} +2ms
electron-packager Target Platforms: win32 +1ms
electron-packager Target Architectures: x64 +1ms
electron-packager Inferring appVersion from version in E:\Projects\TestApp\package.json +0ms
electron-packager Inferring target Electron version from electron in E:\Projects\TestApp\package.json +3ms
electron-packager Application name: stox +14ms
electron-packager Target Electron version: 7.1.2 +1ms
electron-packager Ignored path regular expressions: [ '/\.git($|/)', '/node_modules/\.bin($|/)', '\.o(bj)?$' ] +0ms
electron-packager Downloading Electron with options {"rejectUnauthorized":true,"reject-unauthorized":true,"platform":"win32","arch":"x64","version":"7.1.2","artifactName":"electron"} +0ms
electron-packager Removing release-builds\stox-win32-x64 due to setting overwrite: true +9ms
Packaging app for platform win32 x64 using electron v7.1.2
electron-packager Creating C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64-template +25ms
electron-packager Extracting C:\Users\aasmunds\AppData\Local\electron\Cache\httpsgithub.comelectronelectronreleasesdownloadv7.1.2electron-v7.1.2-win32-x64.zip\electron-v7.1.2-win32-x64.zip to C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64-template +2ms
electron-packager Initializing app in C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64\stox-win32-x64 from C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64-template template +0ms
electron-packager Ignored paths based on the out param: [ 'E:\Projects\TestApp\release-builds' ] +751ms
electron-packager Running asar with the options {} +129ms
electron-packager Renaming electron.exe to stox.exe in C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64\stox-win32-x64 +26msENOENT: no such file or directory, rename 'C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64\stox-win32-x64\electron.exe' -> 'C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64\stox-win32-x64\stox.exe'

The difference output between 13.1.1 and the latest 14 can be shown here:
electron-packager . stox --overwrite --asar=true --platform=win32 --arch=x64 --icon=assets/stox_icon.ico --out=release-builds --version-string.CompanyName=HI --version-string.FileDescription=HI --version-string.ProductName="StoX"
$ cross-env DEBUG=electron-packager electron-packager . stox --overwrite --asar=true --platform=win32 --arch=x64 --out=release-builds --versi
on-string.CompanyName=HI --version-string.FileDescription=HI --version-string.ProductName="StoX"
WARNING: --asar does not take any arguments, it only has sub-properties (see --help)
electron-packager Electron Packager 13.1.1
electron-packager Node v10.16.0
electron-packager Host Operating system: win32 (x64) +0ms
electron-packager Packager Options: {"_":[".","stox"],"deref-symlinks":true,"derefSymlinks":true,"download":{"strictSSL":true,"strict-ssl":true},"prune":true,"overwrite":true,"asar":true,"platform":"win32","arch":"x64","out":"release-builds","version-string":{"CompanyName":"HI","FileDescription":"HI","ProductName":"StoX"},"versionString":{"companyName":"HI","fileDescription":"HI","productName":"StoX"},"dir":".","name":"stox","protocols":[]} +1ms
electron-packager Target Platforms: win32 +1ms
electron-packager Target Architectures: x64 +1ms
electron-packager Inferring appVersion from version in E:\Projects\TestApp\package.json +0ms
electron-packager Inferring target Electron version from electron in E:\Projects\TestApp\package.json +4ms
electron-packager Application name: stox +15ms
electron-packager Target Electron version: 7.1.2 +0ms
electron-packager Ignored path regular expressions: [ '/\.git($|/)', '/node_modules/\.bin($|/)', '\.o(bj)?$' ] +0ms
electron-packager Downloading Electron with options {"strictSSL":true,"strict-ssl":true,"platform":"win32","arch":"x64","version":"7.1.2"} +0ms
electron-packager Removing release-builds\stox-win32-x64 due to setting overwrite: true +312ms
Packaging app for platform win32 x64 using electron v7.1.2
electron-packager Creating C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64-template +26ms
electron-packager Extracting C:\Users\aasmunds\AppData\Local\electron\Cache\electron-v7.1.2-win32-x64.zip to C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64-template +3ms
electron-packager Initializing app in C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64\stox-win32-x64 from C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64-template template +0ms
electron-packager Ignored paths based on the out param: [ 'E:\Projects\TestApp\release-builds' ] +2s
electron-packager Running asar with the options {} +117ms
electron-packager Renaming electron.exe to stox.exe in C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64\stox-win32-x64 +31ms  electron-packager Running rcedit with the options {"version-string":{"FileDescription":"stox","InternalName":"stox","OriginalFilename":"stox.exe","ProductName":"stox"},"file-version":"1.0.0","product-version":"1.0.0"} +0ms
electron-packager Moving C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64\stox-win32-x64 to release-builds\stox-win32-x64 +641ms
Wrote new app to release-builds\stox-win32-x64
$ cross-env DEBUG=electron-packager electron-packager . stox --overwrite --asar=true --platform=win32 --arch=x64 --out=release-builds --versi
on-string.CompanyName=HI --version-string.FileDescription=HI --version-string.ProductName="StoX"
WARNING: --asar does not take any arguments, it only has sub-properties (see --help)
electron-packager Electron Packager 14.1.1
electron-packager Node v10.16.0
electron-packager Host Operating system: win32 10.0.17763 (x64) +0ms
electron-packager Packager Options: {"_":[".","stox"],"overwrite":true,"asar":true,"platform":"win32","arch":"x64","out":"release-builds","version-string":{"CompanyName":"HI","FileDescription":"HI","ProductName":"StoX"},"versionString":{"companyName":"HI","fileDescription":"HI","productName":"StoX"},"deref-symlinks":true,"derefSymlinks":true,"download":{"rejectUnauthorized":true,"reject-unauthorized":true},"junk":true,"prune":true,"dir":".","name":"stox","protocols":[]} +2ms
electron-packager Target Platforms: win32 +1ms
electron-packager Target Architectures: x64 +1ms
electron-packager Inferring appVersion from version in E:\Projects\TestApp\package.json +0ms
electron-packager Inferring target Electron version from electron in E:\Projects\TestApp\package.json +3ms
electron-packager Application name: stox +14ms
electron-packager Target Electron version: 7.1.2 +1ms
electron-packager Ignored path regular expressions: [ '/\.git($|/)', '/node_modules/\.bin($|/)', '\.o(bj)?$' ] +0ms
electron-packager Downloading Electron with options {"rejectUnauthorized":true,"reject-unauthorized":true,"platform":"win32","arch":"x64","version":"7.1.2","artifactName":"electron"} +0ms
electron-packager Removing release-builds\stox-win32-x64 due to setting overwrite: true +9ms
Packaging app for platform win32 x64 using electron v7.1.2
electron-packager Creating C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64-template +25ms
electron-packager Extracting C:\Users\aasmunds\AppData\Local\electron\Cache\httpsgithub.comelectronelectronreleasesdownloadv7.1.2electron-v7.1.2-win32-x64.zip\electron-v7.1.2-win32-x64.zip to C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64-template +2ms
electron-packager Initializing app in C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64\stox-win32-x64 from C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64-template template +0ms
electron-packager Ignored paths based on the out param: [ 'E:\Projects\TestApp\release-builds' ] +751ms
electron-packager Running asar with the options {} +129ms
electron-packager Renaming electron.exe to stox.exe in C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64\stox-win32-x64 +26msENOENT: no such file or directory, rename 'C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64\stox-win32-x64\electron.exe' -> 'C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64\stox-win32-x64\stox.exe'

$ electron-packager --version
Electron Packager 14.1.1
Node v10.16.0
Host Operating system: win32 10.0.17763 (x64)

Can you run the following:
cross-env DEBUG=electron-packager,@electron/get* electron-packager . stox --platform win32 --arch x64 --out dist/ --overwrite  --asar

$ cross-env DEBUG=electron-packager,@electron/get* electron-packager . stox --platform win32 --arch x64 --out dist/ --overwrite  --asar
The result of this is the same, still cannot find or rename the electron.exe file:
electron-packager Electron Packager 14.1.1
electron-packager Node v10.16.0
electron-packager Host Operating system: win32 10.0.17763 (x64) +0ms
electron-packager Packager Options: {"_":[".","stox"],"platform":"win32","arch":"x64","out":"dist/","overwrite":true,"asar":true,"deref-symlinks":true,"derefSymlinks":true,"download":{"rejectUnauthorized":true,"reject-unauthorized":true},"junk":true,"prune":true,"dir":".","name":"stox","protocols":[]} +3ms
electron-packager Target Platforms: win32 +0ms
electron-packager Target Architectures: x64 +1ms
electron-packager Inferring appVersion from version in E:\Projects\TestApp\package.json +0ms
electron-packager Inferring target Electron version from electron in E:\Projects\TestApp\package.json +6ms
electron-packager Application name: stox +22ms
electron-packager Target Electron version: 7.1.2 +0ms
electron-packager Ignored path regular expressions: [ '/\.git($|/)', '/node_modules/\.bin($|/)', '\.o(bj)?$' ] +0ms
electron-packager Downloading Electron with options {"rejectUnauthorized":true,"reject-unauthorized":true,"platform":"win32","arch":"x64","version":"7.1.2","artifactName":"electron"} +0ms
@electron/get:index Checking the cache for electron-v7.1.2-win32-x64.zip (https://github.com/electron/electron/releases/download/v7.1.2/electron-v7.1.2-win32-x64.zip) +0ms
@electron/get:index Cache hit +7ms
Packaging app for platform win32 x64 using electron v7.1.2
electron-packager Creating C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64-template +18ms
electron-packager Extracting C:\Users\aasmunds\AppData\Local\electron\Cache\httpsgithub.comelectronelectronreleasesdownloadv7.1.2electron-v7.1.2-win32-x64.zip\electron-v7.1.2-win32-x64.zip to C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64-template +2ms
electron-packager Initializing app in C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64\stox-win32-x64 from C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64-template template +0ms
electron-packager Ignored paths based on the out param: [ 'E:\Projects\TestApp\dist' ] +1s
electron-packager Running asar with the options {} +331ms
electron-packager Renaming electron.exe to stox.exe in C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64\stox-win32-x64 +38msENOENT: no such file or directory, rename 'C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64\stox-win32-x64\electron.exe' -> 'C:\Users\aasmunds\AppData\Local\Temp\electron-packager\win32-x64\stox-win32-x64\stox.exe'

Can you open C:\Users\aasmunds\AppData\Local\electron\Cache\httpsgithub.comelectronelectronreleasesdownloadv7.1.2electron-v7.1.2-win32-x64.zip\electron-v7.1.2-win32-x64.zip and make sure it contains electron.exe?

yes, it does.

Can you reproduce this on a different Windows 10 machine?

Yes, my colleague has reproduced this on his Windows 10 machine

This does not happen in CI, so I'm very confused as to why this would happen. What sort of anti-malware, anti-virus, etc., sort of software is installed?

No, only UAC (user account control) is enabled by IT (forced) and Windows Defender. But the Event Viewer doesnt report about any app-errors when I build. Can you explain why version 13.1.1 works, but not version 14. Which changes was intoduced in version 14 that made it stop working?

Per the release notes, Packager uses Windows's built-in zip extraction to unzip files. The previous solution is no longer maintained and susceptible to security vulnerabilities.

But that's nor the reason? Or...

Hi. I resolved this by adding uac rules for allowing powershell scripts to be run.
Now it works, brilliant. Thank you...


Deep Dive Information Visualisation

User story

As an engineer & portfolio manager
I want / need to apply different forms of visualization to my query results
So that different needs can be displayed in different ways

Acceptance criteria

No implementation (yet) but research, discussion and specification
Overview over various visualization types

Definition of done

Added only after week 5
The same for all features

Implemented via 98fe3bd6b172bb95a94059f70b55fb30c5d12589


python311Packages.es-client: 8.12.8 -> 8.12.9

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.es-client is: Module for building Elasticsearch client objects
meta.homepage for python311Packages.es-client is: https://github.com/untergeek/es_client
meta.changelog for python311Packages.es-client is: https://github.com/untergeek/es_client/releases/tag/v8.12.8
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 8.12.8 with grep in /nix/store/qv55x3icdwa7zlmrm3zgb1z3svxzrgpw-python3.11-es-client-8.12.8
found 8.12.8 in filename of file in /nix/store/qv55x3icdwa7zlmrm3zgb1z3svxzrgpw-python3.11-es-client-8.12.8

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
elasticsearch-curator
python311Packages.es-client
python312Packages.es-client

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qv55x3icdwa7zlmrm3zgb1z3svxzrgpw-python3.11-es-client-8.12.8 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/7146b11234121000c5d06ab2ad2711911571a593#python311Packages.es-client

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qv55x3icdwa7zlmrm3zgb1z3svxzrgpw-python3.11-es-client-8.12.8
ls -la /nix/store/qv55x3icdwa7zlmrm3zgb1z3svxzrgpw-python3.11-es-client-8.12.8/bin

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

2 packages failed to build:

elasticsearch-curator
elasticsearch-curator.dist

4 packages built:

python311Packages.es-client
python311Packages.es-client.dist
python312Packages.es-client
python312Packages.es-client.dist

Maintainer pings
cc @fabaff for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.es-client is: Module for building Elasticsearch client objects
meta.homepage for python311Packages.es-client is: https://github.com/untergeek/es_client
meta.changelog for python311Packages.es-client is: https://github.com/untergeek/es_client/releases/tag/v8.12.9
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 8.12.9 with grep in /nix/store/4y81p7079w9lkpc4clxf5b08sgr0kpdq-python3.11-es-client-8.12.9
found 8.12.9 in filename of file in /nix/store/4y81p7079w9lkpc4clxf5b08sgr0kpdq-python3.11-es-client-8.12.9

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
elasticsearch-curator
python311Packages.es-client
python312Packages.es-client

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/4y81p7079w9lkpc4clxf5b08sgr0kpdq-python3.11-es-client-8.12.9 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/f5156f8e46c1cf1d37e76fb60e00d7aadf37ff84#python311Packages.es-client

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4y81p7079w9lkpc4clxf5b08sgr0kpdq-python3.11-es-client-8.12.9
ls -la /nix/store/4y81p7079w9lkpc4clxf5b08sgr0kpdq-python3.11-es-client-8.12.9/bin

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

2 packages failed to build:

elasticsearch-curator
elasticsearch-curator.dist

4 packages built:

python311Packages.es-client
python311Packages.es-client.dist
python312Packages.es-client
python312Packages.es-client.dist

Maintainer pings
cc @fabaff for testing.

https://github.com/NixOS/nixpkgs/pull/297668#issuecomment-2040493322

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.es-client is: Module for building Elasticsearch client objects
meta.homepage for python311Packages.es-client is: https://github.com/untergeek/es_client
meta.changelog for python311Packages.es-client is: https://github.com/untergeek/es_client/releases/tag/v8.13.0
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 8.13.0 with grep in /nix/store/wbb9xs3hkgqi6f5jfqvbj33ah2fl5k9w-python3.11-es-client-8.13.0
found 8.13.0 in filename of file in /nix/store/wbb9xs3hkgqi6f5jfqvbj33ah2fl5k9w-python3.11-es-client-8.13.0

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
elasticsearch-curator
python311Packages.es-client
python312Packages.es-client

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/wbb9xs3hkgqi6f5jfqvbj33ah2fl5k9w-python3.11-es-client-8.13.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/48e6ee2caad02791d20134286bb5c3135cc799b4#python311Packages.es-client

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/wbb9xs3hkgqi6f5jfqvbj33ah2fl5k9w-python3.11-es-client-8.13.0
ls -la /nix/store/wbb9xs3hkgqi6f5jfqvbj33ah2fl5k9w-python3.11-es-client-8.13.0/bin

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

2 packages failed to build:

elasticsearch-curator
elasticsearch-curator.dist

4 packages built:

python311Packages.es-client
python311Packages.es-client.dist
python312Packages.es-client
python312Packages.es-client.dist

Maintainer pings
cc @fabaff for testing.


Uncaught TypeError: Cannot read property 'split' of undefined

Set YouTube URL
Check "Play Animation"
Click "Apply"

Atom Version: 1.6.0
System: Microsoft Windows 7 Enterprise
Thrown From: editor-background package, v1.2.17
Stack Trace
Uncaught TypeError: Cannot read property 'split' of undefined
At /C:/Users/mmolnar/.atom/packages/editor-background/lib/youtube.coffee:65

TypeError: Cannot read property 'split' of undefined
    at YouTube.getMap (file:///C:/Users/mmolnar/.atom/packages/editor-background/lib/youtube.coffee:53:20)
    at Request._callback (file:///C:/Users/mmolnar/.atom/packages/editor-background/lib/youtube.coffee:99:27)
    at Request.self.callback (C:\Users\mmolnar\.atom\packages\editor-background\node_modules\request\request.js:198:22)
    at emitTwo (events.js:87:13)
    at Request.emit (events.js:172:7)
    at Request.<anonymous> (C:\Users\mmolnar\.atom\packages\editor-background\node_modules\request\request.js:1035:10)
    at emitOne (events.js:82:20)
    at Request.emit (events.js:169:7)
    at IncomingMessage.<anonymous> (C:\Users\mmolnar\.atom\packages\editor-background\node_modules\request\request.js:962:12)
    at emitNone (events.js:72:20)
    at IncomingMessage.emit (events.js:166:7)
    at endReadableNT (_stream_readable.js:893:12)
    at doNTCallback2 (node.js:441:9)
    at process._tickCallback (node.js:355:17)

Commands
  2x -3:25.4.0 tree-view:toggle (atom-text-editor.editor.is-focused)
     -3:21.9.0 command-palette:toggle (ol.tree-view.full-menu.list-tree.has-collapsable-children.focusable-panel)
  2x -3:17 core:move-down (atom-text-editor.editor.mini.is-focused)
     -3:16.1.0 core:confirm (atom-text-editor.editor.mini.is-focused)
     -3:16.1.0 settings-view:view-installed-packages (ol.tree-view.full-menu.list-tree.has-collapsable-children.focusable-panel)
     -3:01.1.0 editor-background:toggle (atom-text-editor.editor.is-focused)
     -0:58.4.0 settings-view:check-for-package-updates (atom-workspace.workspace.scrollbars-visible-always.seti-ui-no-icons.theme-apathy-theme.theme-one-dark-ui.editor-background)
     -0:36.8.0 editor-background:toggle (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "autoHideMenuBar": true,
    "disabledPackages": [
      "autocomplete",
      "terminal-plus"
    ],
    "themes": [
      "one-dark-ui",
      "apathy-theme"
    ]
  },
  "editor-background": {
    "blurRadius": 0,
    "box3d": {},
    "image": {
      "customOverlayColor": true,
      "opacity": 80,
      "overlayColor": {
        "red": 0,
        "green": 0,
        "blue": 0,
        "alpha": 1
      },
      "url": "C:/Users/Public/Pictures/Sample Pictures/Hydrangeas.jpg"
    },
    "other": {},
    "text": {},
    "video": {
      "playAnimation": true,
      "youTubeURL": "https://www.youtube.com/watch?v=6q36pnzcw70"
    }
  }
}

Installed Packages
# User
apathy-theme, v1.10.3
editor-background, v1.2.17
editorconfig, v1.2.4
file-icons, v1.6.18
fonts, v1.2.0
highlight-line, v0.11.1
highlight-selected, v0.11.2
language-ejs, v0.2.0
minimap, v4.21.0
project-manager, v2.7.6
react, v0.14.2
rulerz, v0.4.1
save-session, v0.16.0
Sublime-Style-Column-Selection, v1.5.1
sync-settings, v0.7.2

# Dev
No dev packages

I had the same problem. Trying another video and enable/disable video animation fixed it (frame importer starts when enabling on a "good" video, e.g. https://www.youtube.com/watch?v=qREKP9oijWI ).

Steps to reproduce:

Enter YouTube URL
Check "Video Play Animation"

Atom: 1.46.0 x64
Electron: 4.2.12
OS: "Manjaro Linux"
Linux Kernel: 5.6.11
Thrown From: editor-background package 1.2.42
Stack Trace
Uncaught TypeError: Cannot read property 'split' of undefined
At /home/vivien/.atom/packages/editor-background/lib/youtube.coffee:53

TypeError: Cannot read property 'split' of undefined
    at YouTube.getMap (/packages/editor-background/lib/youtube.coffee:53:21)
    at Request._callback (/packages/editor-background/lib/youtube.coffee:98:24)
    at Request.self.callback (/usr/lib/atom/node_modules/request/request.js:185:22)
    at Request.emit (events.js:182:13)
    at Request.<anonymous> (/usr/lib/atom/node_modules/request/request.js:1161:10)
    at Request.emit (events.js:182:13)
    at IncomingMessage.<anonymous> (/usr/lib/atom/node_modules/request/request.js:1083:12)
    at Object.onceWrapper (events.js:273:13)
    at IncomingMessage.emit (events.js:187:15)
    at endReadableNT (_stream_readable.js:1092:12)
    at process._tickCallback (internal/process/next_tick.js:63:19)

Commands

Non-Core Packages
atom-browser 1.7.0
atom-ide-terminal 5.0.1
atom-ide-ui 0.13.0
atom-music 0.10.1
atom-ternjs 0.20.0
audio 1.5.7
autocomplete-java 1.2.7
autocomplete-javascript 0.0.2
autocomplete-sql 0.5.0
busy-signal 2.0.1
editor-background 1.2.42
file-icons 2.1.41
highlight-colors 0.9.0
hyperclick 0.0.0
ide-cpp 0.1.0
ide-java 0.9.0
ide-php 0.7.18
intentions 1.1.5
java-generator 2.2.3
language-assembly 0.7.2
language-haskell 1.19.4
language-latex 1.2.0
language-lsl 2.2.0
language-vhdl 0.7.2
latex 0.50.2
latexer 0.3.0
linter-javac 1.10.0
pdf-view 0.72.0
php-ide-serenata 5.2.0
plantuml-toolkit 0.2.0
project-manager 3.3.8
quick-query 1.1.1
quick-query-sqlite 0.3.2
teletype 0.13.4
tree-view-filter 0.5.5
videoplayer 1.5.1
xilinx-unisims 0.1.0
zip-folder 3.3.0

So video support doesn't work at all for me. :-(

I get the same error on NixOS Linux on version 1.2.42, Atom 1.42.0

Shows the same error on Windows 10 too, any updates?

@LakshayK0804 Sorry, none for now. But i plan to fix it later.


[DOC] Onboard expired password identification API documentation

With the feature [1], the password expired users identification API is on-boarded to the product is. Need to improve the official IS-Serve doc space with the new API specification.
Updated yaml: https://github.com/wso2/identity-api-server/blob/master/components/org.wso2.carbon.identity.api.expired.password.identification/org.wso2.carbon.identity.api.expired.password.identification.v1/src/main/resources/ExpiredPasswordIdentification.yaml
[1]. https://github.com/wso2/product-is/issues/16529

It's documented https://is.docs.wso2.com/en/latest/apis/password-expiring-users-identification-rest-api/


[SPARK-9806] [WEB UI] Don't share ReplayListenerBus between multiple applications

Can one of the admins verify this patch?

Jenkins, this is ok to test.

/cc @vanzin

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

Jenkins, retest this please.

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

Jenkins, retest this please.

Jenkins has been really flaky lately :(

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

Yeah, I noticed that in my other PR as well. :-(

LGTM. Ah, jenkins... retest this please.

Merged build triggered.

Merged build started.

Test build #40498 has started for   PR 8088 at commit 972af81.

LGTM2

Test build #40498 has finished for   PR 8088 at commit 972af81.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test build #1455 has started for   PR 8088 at commit 972af81.

Test build #1455 has finished for   PR 8088 at commit 972af81.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

retest this please

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

Wow, this is failing scala style tests on already checked in code... :-/

one last try. retest this please

Merged build triggered.

Merged build started.

Test build #40535 has started for   PR 8088 at commit 972af81.

Test build #40535 timed out     for PR 8088 at commit 972af81     after a configured wait of 175m.

Merged build finished. Test FAILed.

sigh. retest this please

Merged build triggered.

Merged build started.

Test build #40573 has started for   PR 8088 at commit 972af81.

Test build #40573 has finished for   PR 8088 at commit 972af81.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Finally!

Merging into master 1.5.


Add automatic resolution of embedded object constraints during migration

This adds configuration option to enable automatic handling of embedded object constraints during automatic migration through:
class RealmConfiguration {

    class Builder {
        /**
         * Sets the migration to handle schema updates with automatic migration of data.
         *
         * @param migration the [AutomaticSchemaMigration] instance to handle schema and data
         * migration in the event of a schema update.
         * @param resolveEmbeddedObjectConstraints a flag to indicate whether realm should resolve
         * embedded object constraints after migration. If this is `true` then all embedded objects
         * without a parent will be deleted and every embedded object with multiple references to it
         * will be duplicated so that every referencing object will hold its own copy of the
         * embedded object.
         *
         * @see RealmMigration
         * @see AutomaticSchemaMigration
         */
        public fun migration(
            migration: AutomaticSchemaMigration,
            resolveEmbeddedObjectConstraints: Boolean = false
        ): Builder =
            apply {
                this.migration = migration
                this.automaticEmbeddedObjectConstraintsResolution = resolveEmbeddedObjectConstraints
            }
    }
}

The above API was chosen in favor of adding additional properties/methods to the AutomaticSchemaMigration interface, as this would require users to instantiate it as anynomous instances and that seems very tedious compared to the standalone functional interface. Alternative it could also have been wrapped in a completely new type, but that just bloats the name space.
Closes #1464

Ok... well as long as I can enable it I guess it isn't an issue. But people migrating from Java to Kotlin might get a nasty surprise if they are not aware of this difference in implementations.

Nice 🚀 .. I was a bit surprised to see the duplicated method, but I assume it is because we need to constrain it to the AutomaticRealmMigration interface rather than the RealmMigration interface?

Yes. The option will probably only make sense for an automatic migration, so didn't want to add it to the base method.


Chat messages sometime get lost

Sometimes new messages are not sent. It seems more probable to happen on high latency network (like 3g). To be verified.

Fixed by 7f8183d6


Fix incorrect use of AttachStatus

This PR fixes issue #1030
What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:

Closing as this PR, as this will be redundant once, PR #1174 is merged


Add/fix  axel-op/dart-package-analyzer@v3 action to pull_request and publish  workflows

It seems like axel-op/dart-package-analyzer@v3 is not working any more(for us) after the release of this version

It was removed by this pr: https://github.com/Flagsmith/flagsmith-flutter-client/pull/56


When grouped, the last crash is given the same "ago" time as the first crash

Prerequisites:
Settings "Combine same apps" and "Combine same crashes" are both activated.
Whenever crashes are listed from several dates, there's a weird thing happening, that looks like the topmost crash is restacked to the very bottom in that app's group (or a duplicate is made and restacked to bottom? Can't tell yet because of #36).

Oh yeah, I see.

Notes for myself:
What happens is that a new crash comes in and is put at the top of the list. For some reason, the crash at the bottom of the list is given the same "ago" time as the newest crash, even though the crashes are ordered by age (from top to bottom).
When "combine same apps" is disabled, this issue does not manifest (for some reason).

 Turns out...


Type hints?

Related: https://github.com/Toblerity/Shapely/issues/721
This would be a 2.3.x thing.

https://github.com/google/pytype
http://mypy-lang.org/


Dapr CLI should warn about upcoming TLS certificate expiration

Add warning to CLI for upcoming TLS certificate expiration
This is similar to https://github.com/dapr/dapr/issues/3940 which is for the sidecar / runtime only.
I propose that every dapr command targeting Kubernetes, e.g. dapr upgrade -k, or dapr status -k internally perform the dapr mtls expiry command and print a warning message if the TLS expiration is coming up in a set period of days, perhaps 7 days.

/assign

Certificate expiry check can be added for the following commands -
dapr components -k
dapr configurations -k
dapr dashboard -k
dapr list -k
dapr logs -k
dapr mtls -k
dapr mtls export
dapr status -k
dapr upgrade -k

LGTM

This issue needs a  mention in the documentation. Also 7 days is too short, this should be 30 days or less IMO. Usually this takes time to plan for production workloads. If this is 7 days this needs changing.

@pravinpushkar @mukundansundar This issue needs a mention in the documentation. Also 7 days is too short, this should be 30 days or less IMO. Usually this takes time to plan for production workloads. If this is 7 days this needs changing.

@msfussell  It is 30 days in current code implementation. So, I think no change needed on this front.
I will mention this in documentation also.


remove unused dependency org.assertj

please remove unused import 'org.assertj' from imported-packages in MANIFEST.MF.
besides that, the correct import package would need to import 'org.assertj.core.api' or something like that.
see MANIFEST:MF file of

org.assertj
assertj-core
1.7.1

thanks for the fix. can you release a new version!?


Pipette Gen2: Alert User in Modal if Pipette Mismatched

As a Run App user, I would like to be alerted if my pipettes are compatible but mismatched, so I can be aware of any behavioral differences.
Acceptance Criteria

[ ] Alert user in a modal if pipette attached to robot is different than pipette specified in protocol, but will work.
[ ] User should be informed that pipette on robot will perform with the same range as the pipette specified in the protocol
[ ] Recommend that user update the protocol
[ ] If robot and protocol both have two mismatched pipettes, list all pipette names in modal

Compatibility
The following pipettes are compatible

GEN2 P20 instead of GEN1 P10
GEN2 P300 instead of GEN1 P300
GEN2 P1000 instead of GEN1 P1000

Full list of compatibilities here:
https://docs.google.com/spreadsheets/d/1M6azQXZocWTqnEZDQ1Bpp9V1F9Fn86otdd4Go_LTIlQ/edit#gid=0
Design
Single mismatched pipette:
https://app.zeplin.io/project/5aa97729db58a2192f10d0d6/screen/5d0217088ac43c5dd4da8ef9
Two mismatched pipettes:
https://app.zeplin.io/project/5aa97729db58a2192f10d0d6/screen/5d0323f7ade24819ee212941

Merged into release branch, will be going into master and edge after release QA


Matter 1.3 Driver Release

Check all that apply
Type of Change

[ ] WWST Certification Request

If this is your first time contributing code:

[ ] I have reviewed the README.md file
[ ] I have reviewed the CODE_OF_CONDUCT.md file
[ ] I have signed the CLA

[ ] I plan on entering a WWST Certification Request or have entered a request through the WWST Certification console at developer.smartthings.com

[ ] Bug fix
[ ] New feature
[ ] Refactor

Checklist

[ ] I have performed a self-review of my code
[ ] I have commented my code in hard-to-understand areas
[ ] I have verified my changes by testing with a device or have communicated a plan for testing
[ ] I am adding new behavior, such as adding a sub-driver, and have added and run new unit tests to cover the new behavior

Description of Change
New Device Types Included:

Water Valve
Electrical Sensor
Rain Sensor
Leak Detector
Freeze Detector
EVSE
Laundry Dryer
Extractor Hood
Microwave Oven

Also includes:

Embedded Matter 1.3 clusters, cluster utils
Updated .luacov file (CI support)
Small updates to Refrigerator, Dishwasher drivers
Small updates to resolve changes since this PR's creation

See Completed Testing and Updates of Non-driver specific work here:
https://smartthings.atlassian.net/wiki/spaces/CHIP/pages/3434446937/Matter+1.3+Release+Preparations
Summary of Completed Tests

Closing, see this PR which has the same information. Since I closed and re-opened this PR (see the commit history), a PR channel for these drivers can't be created on here, so I've opened that new PR.


[Bug] mTLS doesn't support non-EC private keys

What are you really trying to do?
Using a PEM file beginning with -----BEGIN EC PRIVATE KEY-----:
Traceback
RuntimeError: Failed client connect: Server connection error: tonic::transport::Error(Transport, PrivateKeyParseError)

Temporary remedy
Convert your pkey to pkcs8:
openssl pkcs8 -topk8 -nocrypt -in key.pem -out key-pkcs8.pem

Describe the bug
python-sdk is pointing to an older commit in sdk-core which depends on an older version of tonic.
The key issue has been fixed in this tonic PR.
Minimal Reproduction
def setup_tls_config() -> TLSConfig:
    """Helper func to build TLSConfig struct."""
    with open(os.getenv("TEMPORAL_CLI_TLS_CERT"), "rb") as f:
        client_cert = f.read()
    with open(os.getenv("TEMPORAL_CLI_TLS_KEY"), "rb") as f:
        client_private_key = f.read()
    with open(os.getenv("TEMPORAL_CLI_TLS_CA"), "rb") as f:
        server_root_ca_cert = f.read()
    return TLSConfig(
        client_cert=client_cert,
        client_private_key=client_private_key,
        domain=os.getenv("TEMPORAL_CLI_TLS_SERVER_NAME"),
        server_root_ca_cert=server_root_ca_cert,
    )

Environment/Versions

OS and processor: Linux i7
Temporal Version: temporalio==1.3.0
Are you using Docker or Kubernetes or building Temporal from source? Kubernetes

Additional context
If updating to a more recent core SDK version is fairly straightforward, feel free to throw me some pointers, and I will put together a PR.

:+1: We just overcame a hurdle to going past 0.8 Tonic (OTel libs), so we will be upgrading Tonic and all of these libraries before next release.

Awesome, good to know!


fix(): data order change

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

5 of 5 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.0008%) to 99.721%

Totals

Change from base Build<PHONE_NUMBER>:
0.0008%

Covered Lines:
220

Relevant Lines:
220

💛  - Coveralls


Continue to convert to C# code

@thangchung Please review it

@ngohungphuc Thank you, Phuc for your hard works in this project.


Would it be acceptable to move the efitools to oe-core or meta-oe?

The efitools [1] recipe seems to be a good candidate for the oe-core or meta-oe layer as it is a dependency of more and more bsp's to implement uefi secure boot.
[1] https://github.com/Wind-River/meta-secure-core/tree/master/meta-efi-secure-boot/recipes-bsp/efitools.

I strongly support this suggestion. Mainly because I need the efitools binaries in my image, but without all the dependencies to other recipes in meta-secure-core. So it would be good to move the core of the efitool recipe to oe-core or meta-eo and keep the specifics as bbappend in meta-secure-core.

Proposed in https://github.com/openembedded/meta-openembedded/pull/883


Have Legacy Mode use a Popup Window

Starting with Chrome 94, we can no longer use Ajax requests to
communicate via http with the Companion. We also cannot communicate
with http if we are in a secure context.
This change introduces a Popup window which is loaded from the
Companion itself and can therefore communicate with the Companion. Our
main window (from replmgr.js) will now communicate with this Popup
which will act as a go between. This not only permits Chrome 94+ to
work but also permits us to load App Inventor in a secure context.
This code is both forward and backward compatible. An older Companion
will use Legacy Mode as it always has (and be subject to the
restrictions involved). Similarly the new Companion will work with an
older version of App Inventor.
The new Companion indicates that it can use a popup by sending the
"useproxy" flag to the Rendezvous server which is then queried for in
replmgr.js
Change-Id: I43005b78c190dfb8446308f692dc39dec51befb1

Note: There is still more work to be done here (including rebasing to ucr). In particular, I need to gracefully handle the case where the popup is blocked. I am also experimenting with how old a browser can run the Popup code, given it is using newer Javascript and DOM features (aka async/await and fetch). If necessary I will transpile the code and include the actual source somewhere else in the source hierarchy, perhaps under misc along with the webpack config and package.json to build it (I am currently experimenting with npm/webpack/babel).

Nice to see that you have a solution .  Is there some way we can add a
message that will encourage people not to use an
old companion?
== Hal
Hal Abelson
@.***
Prof. of Comp. Sci. and Eng.
MIT Dept. of Elec. Eng. and Comp. Sci.
On Wed, Nov 24, 2021 at 12:14 PM Jeffrey Schiller @.***>
wrote:

Starting with Chrome 94, we can no longer use Ajax requests to
communicate via http with the Companion. We also cannot communicate
with http if we are in a secure context.
This change introduces a Popup window which is loaded from the
Companion itself and can therefore communicate with the Companion. Our
main window (from replmgr.js) will now communicate with this Popup
which will act as a go between. This not only permits Chrome 94+ to
work but also permits us to load App Inventor in a secure context.
This code is both forward and backward compatible. An older Companion
will use Legacy Mode as it always has (and be subject to the
restrictions involved). Similarly the new Companion will work with an
older version of App Inventor.
The new Companion indicates that it can use a popup by sending the
"useproxy" flag to the Rendezvous server which is then queried for in
replmgr.js
Change-Id: I43005b78c190dfb8446308f692dc39dec51befb1
You can view, comment on, or merge this pull request online at:
https://github.com/mit-cml/appinventor-sources/pull/2611
Commit Summary

c7282b9
https://github.com/mit-cml/appinventor-sources/pull/2611/commits/c7282b9fce109ce7918c7b0f93fbb5682646dfdc
Have Legacy Mode use a Popup Window

File Changes
(6 files https://github.com/mit-cml/appinventor-sources/pull/2611/files)

M
appinventor/aiplayapp/src/edu/mit/appinventor/aicompanion3/Screen1.bky
https://github.com/mit-cml/appinventor-sources/pull/2611/files#diff-fbbf48f71414609d958b607c2e111832ff69f8851bb7d6b57668f95590054f0f
(24)
M
appinventor/aiplayapp/src/edu/mit/appinventor/aicompanion3/Screen1.scm
https://github.com/mit-cml/appinventor-sources/pull/2611/files#diff-44a07f18295c6f5c039cf44e222aed7bf0092fdf9323b7589ee0875a6a57849c
(2)
M
appinventor/aiplayapp/src/edu/mit/appinventor/aicompanion3/Screen1.yail
https://github.com/mit-cml/appinventor-sources/pull/2611/files#diff-4a4bd124bc4a002424b3526203036d36cddb89deb67f5fbab698654d4e7373da
(4)
M appinventor/appengine/src/com/google/appinventor/client/Ode.java
https://github.com/mit-cml/appinventor-sources/pull/2611/files#diff-8fcbd3ff952abc30ba9669440d8f1ed7513a147f60fb1006625aa8e1ba9930fb
(9)
M appinventor/blocklyeditor/src/replmgr.js
https://github.com/mit-cml/appinventor-sources/pull/2611/files#diff-9d4ff6d37d5f23e45441c122c97190387cd0aad6f7929244e42fdfe7a67f9672
(221)
M
appinventor/components/src/com/google/appinventor/components/runtime/util/AppInvHTTPD.java
https://github.com/mit-cml/appinventor-sources/pull/2611/files#diff-5c52f72219bf3b5e4ee46814ccd94fff2132be588e73ecefc41617d6cd9e4e64
(110)

Patch Links:

https://github.com/mit-cml/appinventor-sources/pull/2611.patch
https://github.com/mit-cml/appinventor-sources/pull/2611.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mit-cml/appinventor-sources/pull/2611, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGAXN3YAKVIJ7TKHNI5M3LUNUMN7ANCNFSM5IWS43EA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Testing: The code as is (not transpiled) works at least back to Chrome 50 (4/2016) and Firefox 52 (3/2017)

@halatmit Most people have their Companion auto-updated from the Play Store.
We released version 2.62 on 11/9 and there are already 98,000 unique copies as seen by the Rendezvous server while the previous version (2.61) has 73,000 unique copies as soon by the Rendezvous server since 11/9. Older versions are much fewer.

Good that the autoupdating it doing well.
== Hal
Hal Abelson
@.***
Prof. of Comp. Sci. and Eng.
MIT Dept. of Elec. Eng. and Comp. Sci.
On Wed, Nov 24, 2021 at 1:08 PM Jeffrey Schiller @.***>
wrote:

@halatmit https://github.com/halatmit Most people have their Companion
auto-updated from the Play Store.
We released version 2.62 on 11/9 and there are already 98,000 unique
copies as seen by the Rendezvous server while the previous version (2.61)
has 73,000 unique copies as soon by the Rendezvous server since 11/9. Older
versions are much fewer.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mit-cml/appinventor-sources/pull/2611#issuecomment-978110141,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGAXN5A7N3GRSZOOAZT2DLUNUSPJANCNFSM5IWS43EA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Latest commit message isn't quite right, but the code is good.

Note: I have converted this back to a draft. It is now based on #2664 so should not be merged until after that PR is merged and this one appropriately tested and rebased.

I've just converted this PR to a DRAFT. I'm going to refactor it into two commits. One for master, with just the website side changes, and the other for ucr with the Companion changes.

I'm approving this for now, but we should definitely keep an eye on whether the header will be needed. Ideally it would be nice if we don't have to scramble.


"find: ./.Trash: operation not permitted" appearing when run in home folder

When I run the script in my home folder, I get the following type of output:
find: ./.Trash: Operation not permitted
./repo1: Needs push (main) Uncommitted changes
./repo2: Needs push (master) Uncommitted changes
...

I'm wondering if there's a way to change this behavior so that first line doesn't show up?

Wild guess, but perhaps this is related to this question on Stackoverflow? (Don't use the solution given in that question, it's a bad idea). Can you confirm that you're on mac?

I am on a Mac, yes. And I get the same operation not permitted warning with ls ~/.Trash

I've looked into it, but there doesn't seem to be a POSIX (cross platform / shell) way to exclude such directories. It is possible to exclude the .Trash dir itself, however find will still try to recurse into the directory and still runs into the problem. So I can't fix this in mgitstatus itself.
Unfortunately, I think the only solutions for you are to either create an alias in your shell profile that redirects the error output to /dev/null:
alias mgitstatus="mgitstatus 2>/dev/null"

Or move the Git projects to a sub folder in your home dir like ~/src or ~/projects.


Backport meta: use bundled initramfs instead of initrd on tegra186/194

This is a backport from master branch, tested those changes won't affect TX2/TX2i
Original Commit: af4492634b6e3c0657973cf20418c95a7d8fe0a4
Original comment:
meta: use bundled initramfs instead of initrd on tegra186/194
cboot appears to mangle the initrd at boot time when it
exceeds a couple of MiB in size, but only if it has
been built separately and combined with the kernel using
mkbootimg.  This does not happen when the initrd is
built into the kernel directly, so work around the cboot
issue by switching to bundling the initramfs into the
kernel on the non-u-boot platforms.
Signed-off-by: Daniel Wang<EMAIL_ADDRESS>

@danielwangksu I have manually merged this in after some testing across the different targets and making some additional changes to fix some things.

I've added back in the kernel-bup-payload recipe from the original commit to allow for BUP payload creation when using the bundled initramfs
Some minor changes to ensure compatibility for building without bundling the initramfs
I did leave tegra186 platforms with the old non-bundled settings.
I made some minor changes to the tegra194 flash helper script since I ran into issues with it, but those issues appear unrelated to this change.


Notifications service, remove channel setting when updating to unspecified

I don’t have a good api to “unset” a channel setting.
The RemoveChannelSetting seems unused, wired it up to fire when i post unspecified for a channel.
Does this seem okay? Alternatively I could just keep the change in preferences.go that ignroes the unspecified channel setting.

I don't have a concept of unset, only reset to default, which you've essentially implemented

How do you reset to default? Do you reset everything? Reset a single space?


Add seealso link in using_config

I think #2862 can be closed with this fix, because configuration page contains an example of using_config.

LGTM.


The arguments order is incorrect in 'test_car_logged_when_existing' unit test method. submitted by Joon Joo(J173025)

The arguments in self.assertIn(last_line, "NEW-001") are incorrect unless it is testing for students. The following line has the same issue
Ref:
https://github.com/NM-TAFE/civ-ipriot-in-class-demos/blob/d1d17d06562f77fbdbd54cf1130043450ea48784/assessments/prj/carpark-guide.md?plain=1#L899

sorry, just saw it's part of the testing.


AADAuthorizedClinetRepo for Obo flow

This a pr for AADOAuth2OboAuthorizedClientRepository.
enable current API to call other API via on behalf of flow

https://github.com/Azure/azure-sdk-for-java/issues/18065

/azp run java - spring - tests


[UPSTREAM] chromium no longer works on GCF

Environment

chromium Version: 109
puppeteer / puppeteer-core Version: 19.4.0
Node.js Version:  16
Lambda / GCF Runtime:  GCF nodejs16.x

Expected Behavior

should work
Current Behavior

2022-12-27 15:57:01.428 HKT
function-1gf78lu3116xn Function execution started
2022-12-27 15:57:01.443 HKT
function-1gf78lu3116xn Function execution took 14 ms, finished with status: 'ok'
2022-12-27 15:57:01.466 HKT
function-1gf78lu3116xn Error: spawn EFAULT at ChildProcess.spawn (node:internal/child_process:420:11) at Object.spawn (node:child_process:733:9) at BrowserRunner.start (/workspace/node_modules/puppeteer-core/lib/cjs/puppeteer/node/BrowserRunner.js:120:34) at ChromeLauncher.launch (/workspace/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:74:16) at async main (/workspace/index.js:40:21) {
2022-12-27 15:57:01.466 HKT
function-1gf78lu3116xn errno: -14,
2022-12-27 15:57:01.466 HKT
function-1gf78lu3116xn code: 'EFAULT',
2022-12-27 15:57:01.466 HKT
function-1gf78lu3116xn syscall: 'spawn'
2022-12-27 15:57:01.466 HKT
function-1gf78lu3116xn }

Steps to Reproduce

const puppeteer = require('puppeteer-core');
const chromium = require('@sparticuz/chromium');

exports.helloPubSub = (event, context) => {
  const main = async () => {
  try {

    const browser = await puppeteer.launch({
      args: chromium.args,
      defaultViewport: chromium.defaultViewport,
      executablePath: await chromium.executablePath,
      headless: chromium.headless,
      ignoreHTTPSErrors: true,
    });
...
  }
}

Possible Solution

You should be able to find the output of chromium, the error seems to say there is a problem launching it.

https://pptr.dev/troubleshooting#running-puppeteer-on-google-cloud-functions
It appears that GCF might not work anymore

If someone can figure out what the dependencies are, they can be added as a bin/gcf.tar.br file, similar to what is done for aws.

Possibly related: https://issuetracker.google.com/issues/266279679?pli=1

It looks like the linked issue, [Add libnss3.so to Node 18 runtime so that Puppeteer can work [on GCF]](https://issuetracker.google.com/issues/266279679?pli=1) has now been resolved so this should work now on Google Cloud Functions using the Node 18 runtime.

If someone wants to confirm if it works, we can close this issue.

@Sparticuz Found this issue from running into the EFAULT on the Node 16 runtime on GCF, upgraded to 18 just today and I'm able to run :)

I cannot run on node v23.3.0, getting this error:
Error: spawn EFAULT
at ChildProcess.spawn (node:internal/child_process:420:11)
at Object.spawn (node:child_process:762:9)
at new Process (/workspace/node_modules/puppeteer-core/node_modules/@puppeteer/browsers/lib/cjs/launch.js:103:56)
at launch (/workspace/node_modules/puppeteer-core/node_modules/@puppeteer/browsers/lib/cjs/launch.js:50:12)
at ChromeLauncher.launch (/workspace/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ProductLauncher.js:77:54)


fault: keep fault state for each AFR channel

This....is where I would much rather do something like #87 rather than scattering little bits of state all over the place.


video write seems to be hanging

Hello,
I'm trying to do a video write but it is hanging. I tried to follow the examples: rawsnippet.py and also ran the test suite, which hanged on the skvideo.tests.test_ffmpeg.test_FFmpegWriter ...
I'm using:
Python 2.7.12 :: Anaconda 4.1.1 (x86_64)
Macbook
scikit-video: latest code from github
Appreciate the help.
Thanks,
Carlos

After killing the process with "control + C" the following showed up:
^C^CTraceback (most recent call last):
File "rawsnippet.py", line 17, in
skvideo.io.vwrite(filename_yuv, vid)
File "//anaconda/lib/python2.7/site-packages/sk_video-1.1.6-py2.7.egg/skvideo/io/io.py", line 64, in vwrite
writer.writeFrame(videodata[t])
File "//anaconda/lib/python2.7/site-packages/sk_video-1.1.6-py2.7.egg/skvideo/io/ffmpeg.py", line 439, in writeFrame
self._proc.stdin.write(vid.tostring())
KeyboardInterrupt
Thanks,
Carlos

What version of ffmpeg are you using?


[Bug]: Failing to run OpenRouter AND Ollama

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Describe the bug and reproduction steps
Note: both are using Qwen2.5 coder and all of them failed half way

First run using Ollama https://www.all-hands.dev/share?share_id=42c425c3f217af09aa70986f497fcf1f9473fb3df0989dc07c46cc55cd3defee
Second run using OpenRouter https://www.all-hands.dev/share?share_id=8b6a423ec3b6559f61a845c9f4ef6363090c5db2d3a819ede74145f9642a413b
Third run using OpenRouter: https://www.all-hands.dev/share?share_id=4cbf4c7fe8fd601dc449cb241f4c839ddf750ee26bd6e5a5f6441902757b62f8

OpenHands Installation
Docker command in README
OpenHands Version
Latest Docker image with 0.14
Operating System
WSL on Windows
Logs, Errors, Screenshots, and Additional Context
No response

The issue in trajectory (1) is from a bug in the aci -- I'll make a fix for it soon. Not too sure what happened with the other 2 trajectories

@ryanhoangt how can I solve the other two then? What other info should I give regarding the matter to help debug this?

Can you check the logs in terminal to see what errors happened that caused the state to change? You can also set export DEBUG=1 to have more logs visible.

@ryanhoangt so currently Ollama tool use is meh, and got a few pull requests. Make sense.
But the later 2 trajectories ARE exclusively from OpenRouter, so I am not sure how that would be an issue.
@mamoodi since tool use should be important (not just programming)

maybe I should use this as reference? Test with Gemma 2 and Llama 3.1? https://gorilla.cs.berkeley.edu/leaderboard.html https://rank.opencompass.org.cn/leaderboard-llm/?m=24-09
Currently I am using this instead of the "instruct" or finetunes, so maybe that has an effect? Will move back to using qwen2.5-coder:7b-instruct-q4_K_M to check before playing with Llama or switching to OpenRouter https://ollama.com/library/qwen2.5-coder

Extra note: okay now with a proper instruct model, it pretends that it did something when it did not? https://www.all-hands.dev/share?share_id=c151515f5d38a08393bb2cbf1a9cd1f207fe0dd1c832f238f0ec8ab1e0e15fc6 https://www.all-hands.dev/share?share_id=ec00360072ed24855106caba8749df79fabf93da289edfc76f56a2ec939d7ce3

Switching to Llama3 70B through OpenRouter using the non-advanced settings panels yield the same set of issues https://www.all-hands.dev/share?share_id=cc3af61bf54669abce07879e0bc810bce8bdb815735d0766b2776beb872afc0c
Trying another Ollama model to see how it goes phi3:3.8b-mini-128k-instruct-q4_K_M (not gonna lie even when the conversation goes, it does not use the tools and instead fly off the wheels) https://www.all-hands.dev/share?share_id=ffa8469051ba8178ae33c38a0ec7cbd811b45b408cfbbdc78d57425d0a0bb799 https://www.all-hands.dev/share?share_id=e042acc5afb5c99e069d369c5f5c9317a2a8a69470c0522b9ec0f50eafedba06
Ollama with phi3:14b-medium-128k-instruct-q4_K_M to see if it is an issue with model size but nope apparently Phi3 is really bad at anything above code editing, and gives back even more broken results https://www.all-hands.dev/share?share_id=abf824759491cb5367461cb8beaffe6269933a2b9db0bf2e82ace01aea25b17e
Ollama with OpenCoder to see if another SOTA SLM can do the job, welp it managed to screw with file creation and got stuck on a loop (probably would be useful to add guard rails on long-form outputs) https://www.all-hands.dev/share?share_id=33f618f4bc251656660f93b809a27c190dd14deeacb8b60725a768e770dbe8ee

OpenRouter with Gemma 2 27B (since it is not on the core dashboard) to see if switching models lead to some extra issues when it comes to running the service... https://github.com/All-Hands-AI/OpenHands/issues/4920

With Ollama at least the problem of access management has always been iffy Function 'write_file' not found in available tools: ['execute_bash', 'finish', 'browser', 'execute_ipython_cell', 'str_replace_editor']
Ollama with Qwen2.5 Coder (default) 7B
https://www.all-hands.dev/share?share_id=657429b17f44a5cfd35de4dd96b26de637965ebb1323e02ee0b2164a6f5fad34
https://www.all-hands.dev/share?share_id=1c88536ba50715a54f4945ac78431f5daaf90d2445c4b8a069cc650599215d8b
Ollama with Qwen2.5 Coder Instruct 7B
https://www.all-hands.dev/share?share_id=28d7e26b2083bb23a458f754de035732fceccaf2724707dd804f25a8452b7351
https://www.all-hands.dev/share?share_id=13aecbd25fa9c0d4a72ea53414f7855328341d5ee3e95923f85269399a6a01d8
Ollama with Qwen2.5 Coder Instruct 32B
https://www.all-hands.dev/share?share_id=69579a1363b8a63d197a4b567a092418550e111a2c3d802c22c5faeafc906e0a
https://www.all-hands.dev/share?share_id=1c13d1563191ed529123c0280b3526f9e674f58bec398f682d35a933efc28b6f

Testing 0.15 with Ollama instead, and it is not writing file

Qwen2.5 Coder Instruct 32B can't handle long prompts? https://www.all-hands.dev/share?share_id=8083a76822ec0c9ffb399c668f69616b3764ba403ccd307ba4241b55946a0c6b
Okay it probably has issues creating file in general https://www.all-hands.dev/share?share_id=8958e39ab8d3f078c8d22f3e80ab60cb016b5c7822fce3f0d1e3c43730e06c4e

BTW another issue with OpenRouter that might be related to the issue https://github.com/All-Hands-AI/OpenHands/issues/3435

For reference @ryanhoangt it seems like OpenRouter setup with CodeActAgent as default, will force itself to use Git files that are non-existent. openrouter_fails.txt
@SmartManoj have fun with this log btw

Ran OpenRouter a second time but there is clearly no .gitignore https://pastebin.com/jWaJihyq

@BradKML Thank you for the details reports and logs! Please let me note a couple of things quickly, on the latest:
Re:

Ran OpenRouter a second time but there is (a) clearly no .gitignore (b) uses the default Docker command without specified folders and maybe there is a permissions issues that needs documentation https://pastebin.com/SvBJ8X4c

There is indeed no gitignore; that's a bug frankly, it doesn't affect anything but it's annoying. That's not the agent nor the LLM; it doesn't affect the actions; it's the execution environment wasting time.
In the log, I see what looks like the LLM installed some packages whose versions don't match, and when it got an exception it started editing the site-packages files.
2024-12-06 07:07:15     |python3 /workspace/backtester_sma.py
...
2024-12-06 07:07:15     |22:51:32 - openhands:DEBUG: action_execution_server.py:169 - Action output:
2024-12-06 07:07:15     |**CmdOutputObservation (source=None, exit code=1)**
2024-12-06 07:07:15     |python3 /workspace/backtester_sma.py
2024-12-06 07:07:15     |Traceback (most recent call last):
2024-12-06 07:07:15     |  File "/workspace/backtester_sma.py", line 3, in <module>
2024-12-06 07:07:15     |    import pandas_ta as ta
2024-12-06 07:07:15     |  File "/openhands/poetry/openhands-ai-5O4_aCHf-py3.12/lib/python3.12/site-packages/pandas_ta/__init__.py", line 116, in <module>
2024-12-06 07:07:15     |    from pandas_ta.core import *
2024-12-06 07:07:15     |  File "/openhands/poetry/openhands-ai-5O4_aCHf-py3.12/lib/python3.12/site-packages/pandas_ta/core.py", line 18, in <module>
2024-12-06 07:07:15     |    from pandas_ta.momentum import *
2024-12-06 07:07:15     |  File "/openhands/poetry/openhands-ai-5O4_aCHf-py3.12/lib/python3.12/site-packages/pandas_ta/momentum/__init__.py", line 34, in <module>
2024-12-06 07:07:15     |    from .squeeze_pro import squeeze_pro
2024-12-06 07:07:15     |  File "/openhands/poetry/openhands-ai-5O4_aCHf-py3.12/lib/python3.12/site-packages/pandas_ta/momentum/squeeze_pro.py", line 2, in <module>
2024-12-06 07:07:15     |    from numpy import NaN as npNaN
2024-12-06 07:07:15     |ImportError: cannot import name 'NaN' from 'numpy' (/openhands/poetry/openhands-ai-5O4_aCHf-py3.12/lib/python3.12/site-packages/numpy/__init__.py). Did you mean: 'nan'?
...
2024-12-06 07:07:15     |**CmdRunAction (source=EventSource.AGENT)**
2024-12-06 07:07:15     |THOUGHT: It looks like there's an issue with the import statement in `pandas_ta`. The correct import for `NaN` from `numpy` should be `nan` (lowercase). Let's fix this by editing the `squeeze_pro.py` file in `pandas_ta`.

Re:

Addendum: did another set of test, there is definitely a state changing bug Openrouter_superbug.txt another_round.txt

I'm not sure what you mean by state changing bug? At first sight, what I see in the log seems to be that the LLM didn't include the appropriate indentation, when asking for edits, so edits weren't performed.

Re: function calling
Just to clarify, we introduced relatively recently (a month or two now) function calling, in the sense of using the actual "tool use" or "function calls" APIs offered by some providers. There are only a few models (and their providers) that worked very well with it, and it is enabled only for those.
A number of models tested clearly worked better without this: we fallback instead to define a sort of function calling via prompting, like we always did prior to this feature. (just tell the model what and how to answer if it wants this action done).
More importantly: please see
https://github.com/All-Hands-AI/OpenHands/pull/4711
A lot of models are not capable to follow instructions well enough, or when they sort of do they get confused at some point because of their own multi-step history and starting trying to ask for actions that don't exist etc.

Re:

BTW another issue with OpenRouter that might be related to the issue https://github.com/All-Hands-AI/OpenHands/issues/3435

That issue was fixed a while ago. I updated the issue to make it clear it was actually fixed. Sorry for the confusion.
Re:

why are agents stuck on loop when the errors are unique each time? https://github.com/All-Hands-AI/OpenHands/issues/5355

Sorry, can you elaborate?

Re: docker. I'm not sure, but if you suspect there's an issue with docker (workspace or perms etc), please open another issue for that, so that we can look into it on its own. It's too different to deal with it here.
Re: stuck in loops.
So far, I'm looking at the logs you posted, and I see

some loops are caught by us - we give an error about being stuck in a loop
some logs that look to the human eye like loops, are not caught. This kind of thing, I'll look deeper into it. I'm guessing it might be because the code that was looking for patterns in edits, wasn't updated after some very significant editing changes (introducing edit via "tool use" APIs mentioned above), not sure, it might be missing things it should catch.

Re:

@ryanhoangt if I use DEBUG=1 does it show up in these online links? Or do I really need to redo these in the terminal?

It doesn't show in the trajectories shared via Share feedback. DEBUG=1 shows the debug logging in the console and log file, but the Share feedback sends only the actual events I think; not actual logs.

@enyst thanks for all the replies

For now Qwen 2.5 Coder Instruct is what I will be using as the core FOSS alternative since DeepSeek2.5 and Llama3.1 are harder to use locally (and very pessimistic about QwQ and DeepSeek r1)
Dumping Ollama errrors in the near future might be necessary cus the tool use issue is weird when OpenRouter works just fine
Will use Console Log File from Docker as well for now to skip the shallow-dump with the website, would hope things can be resolved in ways that are easier
Regarding the loop, can't we just raise the temperature a little or adjust Top-P/Top-K/Min-P sampling such that it is willing to switch tactics?
Other bugs like LiteLLM with OpenRouter exceptions (like legit it will stop in the middle, maybe due to some weird throttling) are also a little bit mad

Regarding the loop, can't we just raise the temperature a little or adjust Top-P/Top-K/Min-P sampling such that it is willing to switch tactics?

That's one option, I think. If you want to try, a PR is most welcome. I assume we will evaluate the approach.

@enyst there are a few possible solutions around this

Adaptive Temperature Sampling (makes every model better apparently) https://arxiv.org/html/2309.02772v3 https://github.com/LJ2lijia/AdapT
Min-P and other forms of sampling (e.g. Min-P of 0.02 implies the need for pre-filtered Top-P to be 0.98 or Top-K to be <50) also special thanks to @kalomaze https://arxiv.org/html/2407.01082v2 https://github.com/huggingface/transformers/issues/27670 https://aman.ai/primers/ai/token-sampling/
increasing temperature to break loops (from AppMap, they also recommend Top P to be 0.95 and Temperature to be 0.2 weirdly enough, which matches other places like Moatless) https://github.com/getappmap/navie-benchmark/blob/swe-bench-2/VERIFY.md https://github.com/getappmap/navie-benchmark/blob/swe-bench-2/solver/solve_loop.py
Just avoid large Top-P and low Temperature https://forem.julialang.org/svilupp/is-there-an-optimal-temperature-and-top-p-for-code-generation-with-paid-llm-apis-15am https://www.reddit.com/r/ChatGPT/comments/126sr15/gpt_api_analyzing_which_temperature_and_top_p/

Borrowed writing from "guides" (weirdly enough their Top-P and temperature are correlated so it is suspicious) https://promptengineering.org/prompt-engineering-with-temperature-and-top-p https://dropchat.co/blog/controlling-gpt-4s-creative-thermostat-understanding-temperature-and-top_p-sampling https://community.openai.com/t/cheat-sheet-mastering-temperature-and-top-p-in-chatgpt-api/172683

Boilerplates and docstrings: Top P and Temperature set to 0.1-0.2
New code and alternative algorithms: Top P and Temperature set to 0.3-0.4
Experimentation and dialogue: Top P and Temperature set to 0.4-0.6

Some underlying observations and recommendations:

Default: Bumping up Temperature to be above 0 is probably good for breaking loops (since Top-P does not need to be exactly 1), which is doable here https://github.com/All-Hands-AI/OpenHands/blob/main/config.template.toml
PR Worthy Gently cranking up temperature is likely beneficial just in case classical examples cannot help the situation, so if the system is stuck on a loop N times (even with chat logs), raise the temperature by like 0.05 or 0.1, and let the system break out of its loop creatively, and return the temperature to 0 when the problem is resolved.
Complex Creating a new sampling method requires changes in LiteLLM, so better to start from tweaking params instead.

P.S. about self-repetition in conversation, DRY is seen as an alternative to classical penalty systems. XTC (exclude top choice) also looks interesting but are slightly more forced.

@enyst there are a few possible solutions around this

Adaptive Temperature Sampling (makes every model better apparently) https://arxiv.org/html/2309.02772v3 https://github.com/LJ2lijia/AdapT
Min-P and other forms of sampling (e.g. Min-P of 0.02 implies the need for pre-filtered Top-P to be 0.98 or Top-K to be <50) also special thanks to @kalomaze https://arxiv.org/html/2407.01082v2 https://github.com/huggingface/transformers/issues/27670 https://aman.ai/primers/ai/token-sampling/
increasing temperature to break loops (from AppMap, they also recommend Top P to be 0.95 and Temperature to be 0.2 weirdly enough, which matches other places like Moatless) https://github.com/getappmap/navie-benchmark/blob/swe-bench-2/VERIFY.md https://github.com/getappmap/navie-benchmark/blob/swe-bench-2/solver/solve_loop.py
Just avoid high Top-P and low Temperature https://forem.julialang.org/svilupp/is-there-an-optimal-temperature-and-top-p-for-code-generation-with-paid-llm-apis-15am https://www.reddit.com/r/ChatGPT/comments/126sr15/gpt_api_analyzing_which_temperature_and_top_p/

Borrowed writing from "guides" (weirdly enough their Top-P and temperature are correlated so it is suspicious) https://promptengineering.org/prompt-engineering-with-temperature-and-top-p https://dropchat.co/blog/controlling-gpt-4s-creative-thermostat-understanding-temperature-and-top_p-sampling https://community.openai.com/t/cheat-sheet-mastering-temperature-and-top-p-in-chatgpt-api/172683

Boilerplates and docstrings: Top P and Temperature set to 0.1-0.2
New code and alternative algorithms: Top P and Temperature set to 0.3-0.4
Experimentation and dialogue: Top P and Temperature set to 0.4-0.6

Some underlying observations and recommendations:

Default: Bumping up Temperature to be above 0 is probably good for breaking loops (since Top-P does not need to be exactly 1), which is doable here https://github.com/All-Hands-AI/OpenHands/blob/main/config.template.toml
PR Worthy Gently cranking up temperature is likely beneficial just in case classical examples cannot help the situation, so if the system is stuck on a loop N times (even with chat logs), raise the temperature by like 0.05 or 0.1, and let the system break out of its loop creatively, and return the temperature to 0 when the problem is resolved.
Complex Creating a new sampling method requires changes in LiteLLM, so better to start from tweaking params instead.

P.S. about self-repetition in conversation, DRY is seen as an alternative to classical penalty systems. XTC (exclude top choice) also looks interesting but are slightly more forced.

Ran another round of stress-test @SmartManoj (but for some reason I can't load the whole log)
https://www.all-hands.dev/share?share_id=4dbb93310608f43026c9843cf184ce93240b31565f6eb913fbcda369d43ec639
https://www.all-hands.dev/share?share_id=0d83dac8f7bd373bada71232fd93a29585b8f80e57ee50c45a3bbbd26905c236

The trajectory is 21 MB. So, the browser couldn't handle that. The following script will save that into a file.
import requests
import json

json_data = {
    'feedback_id': '4dbb93310608f43026c9843cf184ce93240b31565f6eb913fbcda369d43ec639',
}

response = requests.post(
    'https://show-od-trajectory-3u9bw9tx.uc.gateway.dev/show-od-trajectory',
    json=json_data,
)

with open('response.json', 'w') as f:
    json.dump(response.json(), f)

@SmartManoj does it look "off" in any way?

The error was not included in this trajectory.


fix to use try-catch touching localStorage

Hi!
Since localStorage sometimes throws an Error, we must use try-catch. 😭
Chrome Incognito mode

Mobile Safari: safari private browsing mode
It only occurs when run setItem()...

setItem — bundle.js:2275QuotaExceededError (DOM Exception 22): The quota has been exceeded

hahaha, oh wow
On Mon, Mar 27, 2017 at 11:24 AM Takashi Fujita<EMAIL_ADDRESS>wrote:

Hi!
Since localStorage sometimes throws an Error, we must use try-catch. 😭
Chrome Incognito mode
[image: 2017-03-27 18 14 28]
https://cloud.githubusercontent.com/assets/2628239/24349269/720687fe-1319-11e7-91ad-400eeb903b32.png
Mobile Safari: safari private browsing mode
It only occurs when run setItem()...
[image: 2017-03-27 17 28 16]
https://cloud.githubusercontent.com/assets/2628239/24349261/685171ce-1319-11e7-80be-4ad96b18b8c2.png
setItem — bundle.js:2275QuotaExceededError (DOM Exception 22): The quota has been exceeded

You can view, comment on, or merge this pull request online at:
https://github.com/yoshuawuyts/choo-persist/pull/38
Commit Summary

fix to use try-catch touching localStorage

File Changes

M index.js
https://github.com/yoshuawuyts/choo-persist/pull/38/files#diff-0
(13)

Patch Links:

https://github.com/yoshuawuyts/choo-persist/pull/38.patch
https://github.com/yoshuawuyts/choo-persist/pull/38.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/yoshuawuyts/choo-persist/pull/38, or mute the thread
https://github.com/notifications/unsubscribe-auth/ACWlenFvMXJ8l5UF8-ZTLGcf8btMkYspks5rp4BBgaJpZM4MqAGj
.

v3.0.1 :sparkles:


Update READ.ME of Service Bus

Update READ.ME of Service Bus

@Matthew-Dong,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

Codecov Report

Merging #68 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #68   +/-   ##
=======================================
  Coverage   52.06%   52.06%
=======================================
  Files          35       35
  Lines         557      557
  Branches       47       47
=======================================
  Hits          290      290
  Misses        244      244
  Partials       23       23

Continue to review full report at Codecov.

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


Add todo tutorial

Coverage remained the same at 95.27% when pulling d4a8487d570146ee2d24afc4072d00ca5debdb28 on add-todo-tutorial into 3a1f6643dd16f513cc855f4f7aadc7629f083537 on master.

Coverage remained the same at 95.27% when pulling d4a8487d570146ee2d24afc4072d00ca5debdb28 on add-todo-tutorial into 3a1f6643dd16f513cc855f4f7aadc7629f083537 on master.


Feature request: "Define entities to show"

Hi, btw awesome card!
I would like to have the option to define what entities to show by default, without the search / add option.
What do you think?

Why don't you just define them manually in the yaml ?

ahh, I see now how to do it, I thought it isn't possible, thanks


Inventory creation from VMs needs heuristics for picking the 'public' address

Production VMs may have multiple interfaces and thus multiple addresses. One such VMs example is VMs that use as Openshift nodes. Except from 'eth0' they have 'docker0' and 'tun0' and possibly more, all of them are type v4. The problem is that a VM can never be reachable by using this inventory if it serves the first ipv4 address it finds, for example the internal docker ip.
We need a way to tell the inventory what device to to choose when adding a host to the inventory. By default we can choose eth0 or ens0 and let the user choose if something is different.
It is required then that we parse all the 'reported_devices' we get by the API and then we match the one from the pattern.
Easy reproducer, create a VM with 2 nics, make one not available, and create a playbook that does something on that VM. It should fail randomly.

Related to openshift-ansible/openshift_ovirt role.