Support for multiple stores

We are currently migrating a rather large ember app to ember-engines.  One thing that became clear early on was it would be advantageous to have separate stores for each engine.  However, this has a significant drawback for using factory guy in acceptance tests.  (Unit / integration still work just fine since we set up a custom resolver for in-engine tests).
Is there a way for factory guy to support engines with separate stores inside acceptance testing?  I'm not sure how exactly this could work, but it seems like the key issue is that factory guy assumes that any ED models are available in the main container.  Would it be possible to flag certain factories as only available within a specific engine domain?

There is a method  FactoryGuy.setStore(aStore)  which does what you would expect.
You can put your factories in test-support directory within the engine and it will be available to whole application, but if you put it in tests I think it will be limited to engine domain ( I could be wrong )
But for me to asses what is possible and what is required I would have to see your setup.
I would be happy to screen share sometime with you or if you can put up a public repo and show me around I can work on / figure out the details in there.

Actually, now that I think about it I kind of don't get it:
Is there a way for factory guy to support engines with separate stores inside acceptance testing?
Not sure exactly what you mean .. so get in touch if you want to chat about it. I am curious to understand the issue fully.

Hey, I can push up some code if it helps, but the structure is pretty simple:

main app has ember-data
in-repo engine has ember-data, but does not share a store with main app
both apps share some models (from an in-repo addon)
both apps also have unique models

We have factories set up for all models in tests/factories.
Both shared and unique factories work just fine with build and make in unit and integration tests because we use a custom resolver for these tests.  (as described here)
In acceptance tests:

if you try to build a factory for an app-unique model, it works
if you try to build a factory for a shared model, it works
if you try try build a factory for an engine-unique model

This can look something like:
Error: No model was found for 'affiliate-change'

With a stack trace:
testem.js:989 Error
    at Class._modelFactoryFor (store.js:1813)
    at Class._modelFor (store.js:1797)
    at Class.modelFor (store.js:1790)
    at ModelDefinition.isModelAFragment (model-definition.js:52)
    at ModelDefinition.build (model-definition.js:195)
    at FactoryGuy.buildRaw (factory-guy.js:301)
    at FactoryGuy.build (factory-guy.js:286)
    at index-test.js:21
    at Class.andThen (ember.debug.js:38931)
    at ember.debug.js:38874

I was considering usingsetStore in these scenarios, since presumably the only problem is that with acceptance tests factory-guy is automatically plugging in to the main container/store and obviously cannot find the model there.  My thought was to call setStore in any tests that need a factory for an in-engine model with that engine's store.  However, I have not been able to figure out the right way to get the engine's store from a test context. :)
What would be nice is a way to easily flag that specific factories should be looked up on a specific engine (perhaps similar to how you can set up custom resolvers for unit / integration tests).

Actually .. yes, if you can make a skeleton repo, with minimum amount of things ( especially with a nice2
failing test ) I can noodle around and see what I can come up with.
I guess what you are saying is that if certain factories were not looked up then the factory would not blow up trying to find the model it can not find.
I am also guessing that the solution is either to limit the factories loaded ( like you are suggesting ) or including/loading all the model definitions in an acceptance test so they are all available.
I am just still confused as to how the whole thing fits together though, since I am not sure how you are declaring app vs shared vs engine models.  So a specific repo to play with would help.

sounds good.  I'll try to get something up this week.

Here is an example repo.  I left some comments in the test files trying to explain the expected outcome.
Thanks!

Okay .. here is my conclusion ..
There is a good reason that ember-engines talks how you can test you engine specific things in integration and unit tests.
They don't say .. hey .. you can test engine specific stuff in the applicaiton.
So, when you run acceptance test ( in application land ) and you call for /commentator , which goes to commentator engine, that engine knows about it's models.
In an application acceptance test if you want to test the engine you have to go through the routing of the engine. You can not and should not be getting / making instances of  engine models in the application acceptance tests.  (( My opinion. )) There is something very fishy if you are doing that.
Since by design the UNIT testing ( models ) should be done in the engine. Right?
If you dissagree, let me know .. because otherwise this is an issue I or no one should fix. (( My opinion ... until you can convince me otherwise and then I will gladly disagree with myself ))

Hey, thanks for working through this!
I agree you should not be making models as in using make, that clearly seems to be poor practice.  However, a common use case for Factory Guy in acceptance tests is building payload for a stubbed server (such as using Pretender or Factory Guy's own mock helpers.  In these cases it would not be possible to mock an API endpoint in an acceptance test because Factory Guy depends on the model file itself.
(That was the reason I was wondering if it it would be possible just to flag a special resolver on the factory itself, since it really just needs to be able to load the JS file to build a payload, right?)

Now that is a very good point.
If you want to build a payload in the application level that includes engine models ..
BUT I think they assume that the engine routes/templates ( and therefore models) will be tested in acceptance tests FOR THAT engine. ?? ( i am guessing )
There probably is a way to resolve those models in the engine while running application tests ( so factory guy can resolve them too .. but you will probably need serializers and adapters too ) though I not sure how to do that at the moment.
Do you?

Not really :)
It is possible that is assumed, though that sort of defeats the point of an in-repo engine.  (Although maybe the thought is in-repo engines are a temporary step?)
But yeah, seems like the serializers / adapters are the tough point since that would require actually getting the engine's store.  I've done some poking (and posted on the Ember slack), but haven't made much progress.

I know .. it is a bummer.
And good to know you asked on the slack channels because I was thinking of same.
I think for sure there is a way to do it, but I just don't know how right now.
I guess if I were you I would make acceptance tests for the in-repo engines routes.
Is that doable?
Does that cover most of what needs covering?

I have not given up yet :)  I was hoping to get something working where 2 resolvers would be allowed at the same time.  ember-mocha docs alluded to such a thing, but it did not quite work.
This would be the easiest solution ( though easy is still hard ) if I can figure out how to do it

Ok .. I have  now officially given up.
You can't have multiple resolvers in a test, so that settles that.
I will still try and think of a way to do this in the future, but for now I think this is just a limitation of factory guy.

Thanks for being so diligent in trying to solve this!  A new technology like ember-engines often comes with short term limitations like this so while it is a bummer, it is perfectly understandable.  I hope as engines matures there will be increased API tooling that could also help with this.
Just out of curiosity, when you said make acceptance tests for the in-repo engine routes, did you mean add tests within the in-repo addon itself?  AFAIK acceptance tests are always scoped to the main app, and I haven't come across an example where an in-repo addon would have its own test suite.  If we extracted the in-repo engine to a separate repo, in theory it could have its own test suite, but I'm pretty sure that test suite would inherit the same issues: it would have a dummy parent app that mounts the engine.
In any case, the short term solution of just mocking ad hoc JSON for these acceptance tests works.  Honestly the elegance of factory-guy has kind of spoiled us. :)

Sure .. let's close it for now. Thanks for asking. I will just close it now, and if we ever think of how to resolve it we can open again.


Remove IProxyLoader, IProxyLoaderFactory, and their usage from the Loader

IProxyLoader and IProxyLoaderFactory supported the execution-context-loader that I removed in #8050.  With that removed there are no remaining known users/implementers.
Additionally, we've been trying to limit ambient availability to the Loader, as it's not generally appropriate for all DO's etc. to have access to the ability to load containers (instead, the host should explicitly decide whether to provide this access via some other mechanism).  In alignment with that goal, these shouldn't be ambiently available on ILoaderServices (whether proxy or not, access should be deliberately distributed).

I should have marked these deprecated earlier -- I'll create a PR to start with that.

These are now deprecated, and should be removed in vNext.  Might need some staging, though since they are unused should be low risk.


Re-examine how snippets handle child resources

There are a lot of snippets that create child resources without a corresponding parent resource (e.g. many of the Cosmos DB snippets, the Key Vault secret snippet, the NSG rule snippet, the route table route snippet, SQL Database import, and a generic child resource snippet). Currently, they include a placeholder for the qualified name of the child resource and expect it to include a /, e.g. myparent/mychild.
Given we are encouraging people to use the parent property and nested resources (e.g. #3006, #2245). I think we should figure out how we want to migrate these snippets away from the name concatenation approach.
Options might include:

We require that child resource snippets include the parent resource.
We add a parent property to the child resource definition in the snippet without the corresponding parent resource being included. However, this results in test failures today, because the emitted Bicep file is checked for validity.
We add an existing resource to the emitted Bicep file and use that as the parent.

FWIW, I like option 3

+1, option 3 would be very slick.
A semi-related idea would be to support sensible completions for an empty parent property:

e.g. here we could show the following list:

All possible parent candidates (resources of the right type) in the template
Offer to generate and insert an 'existing' parent for you
Offer to generate a resource parameter (once #2246 is done)

If we could build this logic for non-snippet cases, then I think snippets would also benefit from it (we could leave it blank with a tab-stop, and pop up the completions).

Sounds good!
@anthony-c-martin I agree that that completion idea would be great - I assume it'll be a little while before that's ready though? If so, I can have a go at updating the snippets to use option 3 - I'll probably do it in a few batches.

Sounds good!
@anthony-c-martin I agree that that completion idea would be great - I assume it'll be a little while before that's ready though? If so, I can have a go at updating the snippets to use option 3 - I'll probably do it in a few batches.

Yup, sounds good to me!


What is the license for this code?

can you add a license so folks know how ( or if ) they can use this code?

I added a license. Thanks for bringing this up.


Could not compile this on colab

Bug description
When I'm trying to compile it on colab, build fails with error "E: Unable to correct problems, you have held broken packages.", even though there are no broken packages present.
Steps to reproduce
apt update
apt-get install "qtbase5-dev" "qtscript5-dev" "qtmultimedia5-dev" "qtdeclarative5-dev" "qttools5-dev" "qttools5-dev-tools"
mkdir -p /content/
cd /content/
git clone --branch develop https://github.com/Bionus/imgbrd-grabber.git
cd imgbrd-grabber/
./build.sh

Expected behavior
Build finishes successfully
Actual behavior
build fails with error "E: Unable to correct problems, you have held broken packages.".
build.sh output:
Submodule 'cmake/cotire' (https://github.com/sakra/cotire.git) registered for path 'src/cmake/cotire'
Submodule 'cmake/qt-android-cmake' (https://github.com/LaurentGomila/qt-android-cmake.git) registered for path 'src/cmake/qt-android-cmake'
Submodule 'tests/src/vendor/catch' (https://github.com/catchorg/Catch2.git) registered for path 'src/tests/src/vendor/catch'
Cloning into '/content/imgbrd-grabber/src/cmake/cotire'...
Cloning into '/content/imgbrd-grabber/src/cmake/qt-android-cmake'...
Cloning into '/content/imgbrd-grabber/src/tests/src/vendor/catch'...
Submodule path 'src/cmake/cotire': checked out '391bf6b7609e14f5976bd5247b68d63cbf8d4d12'
Submodule path 'src/cmake/qt-android-cmake': checked out '5a62962dbe35e955374688461784ddb7f757a377'
Submodule path 'src/tests/src/vendor/catch': checked out 'f0dc4d9be078d21ccabcb0798f03c332a153f84f'
E: Unable to correct problems, you have held broken packages.

System information

OS: Ubuntu 18.04.5 LTS
Grabber version: 7.5.1

Here's what I'm done so far:
I tried to fo find a reason by using bash verbose mode:
sh -x build.sh
It gave me this output:
+ [[ == root ]]
build.sh: 3: build.sh: [[: not found
+ type sudo
+ permission=sudo
+ git submodule update --init --recursive
Submodule 'cmake/cotire' (https://github.com/sakra/cotire.git) registered for path 'src/cmake/cotire'
Submodule 'cmake/qt-android-cmake' (https://github.com/LaurentGomila/qt-android-cmake.git) registered for path 'src/cmake/qt-android-cmake'
Submodule 'tests/src/vendor/catch' (https://github.com/catchorg/Catch2.git) registered for path 'src/tests/src/vendor/catch'
Cloning into '/content/imgbrd-grabber/src/cmake/cotire'...
Cloning into '/content/imgbrd-grabber/src/cmake/qt-android-cmake'...
Cloning into '/content/imgbrd-grabber/src/tests/src/vendor/catch'...
Submodule path 'src/cmake/cotire': checked out '391bf6b7609e14f5976bd5247b68d63cbf8d4d12'
Submodule path 'src/cmake/qt-android-cmake': checked out '5a62962dbe35e955374688461784ddb7f757a377'
Submodule path 'src/tests/src/vendor/catch': checked out 'f0dc4d9be078d21ccabcb0798f03c332a153f84f'
+ declare -i no_pm=1 installed=0
build.sh: 16: build.sh: declare: not found
+ type pacman
+ type apt-get
+ no_pm=0
+ sudo apt-get install -qq qtbase5-dev qtscript5-dev qtmultimedia5-dev qtdeclarative5-dev qttools5-dev qttools5-dev-tools
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76, <> line 68.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
Selecting previously unselected package libdaemon0:amd64.
(Reading database ... 160983 files and directories currently installed.)
Preparing to unpack .../00-libdaemon0_0.14-6_amd64.deb ...
Unpacking libdaemon0:amd64 (0.14-6) ...
Selecting previously unselected package libqt5script5:amd64.
Preparing to unpack .../01-libqt5script5_5.9.5+dfsg-0ubuntu1_amd64.deb ...
Unpacking libqt5script5:amd64 (5.9.5+dfsg-0ubuntu1) ...
Selecting previously unselected package libqt5scripttools5:amd64.
Preparing to unpack .../02-libqt5scripttools5_5.9.5+dfsg-0ubuntu1_amd64.deb ...
Unpacking libqt5scripttools5:amd64 (5.9.5+dfsg-0ubuntu1) ...
Selecting previously unselected package libcap2-bin.
Preparing to unpack .../03-libcap2-bin_1%3a2.25-1.2_amd64.deb ...
Unpacking libcap2-bin (1:2.25-1.2) ...
Selecting previously unselected package libgstreamer1.0-0:amd64.
Preparing to unpack .../04-libgstreamer1.0-0_1.14.5-0ubuntu1~18.04.1_amd64.deb ...
Unpacking libgstreamer1.0-0:amd64 (1.14.5-0ubuntu1~18.04.1) ...
Selecting previously unselected package liborc-0.4-0:amd64.
Preparing to unpack .../05-liborc-0.4-0_1%3a0.4.28-1_amd64.deb ...
Unpacking liborc-0.4-0:amd64 (1:0.4.28-1) ...
Selecting previously unselected package libgstreamer-plugins-base1.0-0:amd64.
Preparing to unpack .../06-libgstreamer-plugins-base1.0-0_1.14.5-0ubuntu1~18.04.1_amd64.deb ...
Unpacking libgstreamer-plugins-base1.0-0:amd64 (1.14.5-0ubuntu1~18.04.1) ...
Selecting previously unselected package libhyphen0:amd64.
Preparing to unpack .../07-libhyphen0_2.8.8-5_amd64.deb ...
Unpacking libhyphen0:amd64 (2.8.8-5) ...
Selecting previously unselected package libqt5positioning5:amd64.
Preparing to unpack .../08-libqt5positioning5_5.9.5+dfsg-0ubuntu2_amd64.deb ...
Unpacking libqt5positioning5:amd64 (5.9.5+dfsg-0ubuntu2) ...
Selecting previously unselected package libqt5qml5:amd64.
Preparing to unpack .../09-libqt5qml5_5.9.5-0ubuntu1.1_amd64.deb ...
Unpacking libqt5qml5:amd64 (5.9.5-0ubuntu1.1) ...
Selecting previously unselected package libqt5quick5:amd64.
Preparing to unpack .../10-libqt5quick5_5.9.5-0ubuntu1.1_amd64.deb ...
Unpacking libqt5quick5:amd64 (5.9.5-0ubuntu1.1) ...
Selecting previously unselected package libqt5sensors5:amd64.
Preparing to unpack .../11-libqt5sensors5_5.9.5-0ubuntu1_amd64.deb ...
Unpacking libqt5sensors5:amd64 (5.9.5-0ubuntu1) ...
Selecting previously unselected package libqt5webchannel5:amd64.
Preparing to unpack .../12-libqt5webchannel5_5.9.5-0ubuntu1_amd64.deb ...
Unpacking libqt5webchannel5:amd64 (5.9.5-0ubuntu1) ...
Selecting previously unselected package libbrotli1:amd64.
Preparing to unpack .../13-libbrotli1_1.0.3-1ubuntu1.3_amd64.deb ...
Unpacking libbrotli1:amd64 (1.0.3-1ubuntu1.3) ...
Selecting previously unselected package libwoff1:amd64.
Preparing to unpack .../14-libwoff1_1.0.2-1build0.1_amd64.deb ...
Unpacking libwoff1:amd64 (1.0.2-1build0.1) ...
Selecting previously unselected package libqt5webkit5:amd64.
Preparing to unpack .../15-libqt5webkit5_5.212.0~alpha2-7ubuntu1_amd64.deb ...
Unpacking libqt5webkit5:amd64 (5.212.0~alpha2-7ubuntu1) ...
Selecting previously unselected package qtscript5-dev:amd64.
Preparing to unpack .../16-qtscript5-dev_5.9.5+dfsg-0ubuntu1_amd64.deb ...
Unpacking qtscript5-dev:amd64 (5.9.5+dfsg-0ubuntu1) ...
Selecting previously unselected package libpam-cap:amd64.
Preparing to unpack .../17-libpam-cap_1%3a2.25-1.2_amd64.deb ...
Unpacking libpam-cap:amd64 (1:2.25-1.2) ...
Selecting previously unselected package libisc169:amd64.
Preparing to unpack .../18-libisc169_1%3a9.11.3+dfsg-1ubuntu1.14_amd64.deb ...
Unpacking libisc169:amd64 (1:9.11.3+dfsg-1ubuntu1.14) ...
Selecting previously unselected package libgeoip1:amd64.
Preparing to unpack .../19-libgeoip1_1.6.12-1_amd64.deb ...
Unpacking libgeoip1:amd64 (1.6.12-1) ...
Selecting previously unselected package libdns1100:amd64.
Preparing to unpack .../20-libdns1100_1%3a9.11.3+dfsg-1ubuntu1.14_amd64.deb ...
Unpacking libdns1100:amd64 (1:9.11.3+dfsg-1ubuntu1.14) ...
Selecting previously unselected package libisccc160:amd64.
Preparing to unpack .../21-libisccc160_1%3a9.11.3+dfsg-1ubuntu1.14_amd64.deb ...
Unpacking libisccc160:amd64 (1:9.11.3+dfsg-1ubuntu1.14) ...
Selecting previously unselected package libisccfg160:amd64.
Preparing to unpack .../22-libisccfg160_1%3a9.11.3+dfsg-1ubuntu1.14_amd64.deb ...
Unpacking libisccfg160:amd64 (1:9.11.3+dfsg-1ubuntu1.14) ...
Selecting previously unselected package libbind9-160:amd64.
Preparing to unpack .../23-libbind9-160_1%3a9.11.3+dfsg-1ubuntu1.14_amd64.deb ...
Unpacking libbind9-160:amd64 (1:9.11.3+dfsg-1ubuntu1.14) ...
Selecting previously unselected package liblwres160:amd64.
Preparing to unpack .../24-liblwres160_1%3a9.11.3+dfsg-1ubuntu1.14_amd64.deb ...
Unpacking liblwres160:amd64 (1:9.11.3+dfsg-1ubuntu1.14) ...
Selecting previously unselected package bind9-host.
Preparing to unpack .../25-bind9-host_1%3a9.11.3+dfsg-1ubuntu1.14_amd64.deb ...
Unpacking bind9-host (1:9.11.3+dfsg-1ubuntu1.14) ...
Selecting previously unselected package geoip-database.
Preparing to unpack .../26-geoip-database_20180315-1_all.deb ...
Unpacking geoip-database (20180315-1) ...
Selecting previously unselected package libavahi-core7:amd64.
Preparing to unpack .../27-libavahi-core7_0.7-3.1ubuntu1.2_amd64.deb ...
Unpacking libavahi-core7:amd64 (0.7-3.1ubuntu1.2) ...
Selecting previously unselected package avahi-daemon.
Preparing to unpack .../28-avahi-daemon_0.7-3.1ubuntu1.2_amd64.deb ...
Unpacking avahi-daemon (0.7-3.1ubuntu1.2) ...
Selecting previously unselected package libavahi-glib1:amd64.
Preparing to unpack .../29-libavahi-glib1_0.7-3.1ubuntu1.2_amd64.deb ...
Unpacking libavahi-glib1:amd64 (0.7-3.1ubuntu1.2) ...
Selecting previously unselected package libgeoclue-2-0:amd64.
Preparing to unpack .../30-libgeoclue-2-0_2.4.7-1ubuntu1_amd64.deb ...
Unpacking libgeoclue-2-0:amd64 (2.4.7-1ubuntu1) ...
Selecting previously unselected package libmm-glib0:amd64.
Preparing to unpack .../31-libmm-glib0_1.10.0-1~ubuntu18.04.2_amd64.deb ...
Unpacking libmm-glib0:amd64 (1.10.0-1~ubuntu18.04.2) ...
Selecting previously unselected package geoclue-2.0.
Preparing to unpack .../32-geoclue-2.0_2.4.7-1ubuntu1_amd64.deb ...
Unpacking geoclue-2.0 (2.4.7-1ubuntu1) ...
Selecting previously unselected package libcdparanoia0:amd64.
Preparing to unpack .../33-libcdparanoia0_3.10.2+debian-13_amd64.deb ...
Unpacking libcdparanoia0:amd64 (3.10.2+debian-13) ...
Selecting previously unselected package libvisual-0.4-0:amd64.
Preparing to unpack .../34-libvisual-0.4-0_0.4.0-11_amd64.deb ...
Unpacking libvisual-0.4-0:amd64 (0.4.0-11) ...
Selecting previously unselected package gstreamer1.0-plugins-base:amd64.
Preparing to unpack .../35-gstreamer1.0-plugins-base_1.14.5-0ubuntu1~18.04.1_amd64.deb ...
Unpacking gstreamer1.0-plugins-base:amd64 (1.14.5-0ubuntu1~18.04.1) ...
Selecting previously unselected package iio-sensor-proxy.
Preparing to unpack .../36-iio-sensor-proxy_2.4-2_amd64.deb ...
Unpacking iio-sensor-proxy (2.4-2) ...
Selecting previously unselected package libgl1-mesa-glx:amd64.
Preparing to unpack .../37-libgl1-mesa-glx_20.0.8-0ubuntu1~18.04.1_amd64.deb ...
Unpacking libgl1-mesa-glx:amd64 (20.0.8-0ubuntu1~18.04.1) ...
Selecting previously unselected package libmbim-glib4:amd64.
Preparing to unpack .../38-libmbim-glib4_1.18.0-1~ubuntu18.04.1_amd64.deb ...
Unpacking libmbim-glib4:amd64 (1.18.0-1~ubuntu18.04.1) ...
Selecting previously unselected package libmbim-proxy.
Preparing to unpack .../39-libmbim-proxy_1.18.0-1~ubuntu18.04.1_amd64.deb ...
Unpacking libmbim-proxy (1.18.0-1~ubuntu18.04.1) ...
Selecting previously unselected package libnl-genl-3-200:amd64.
Preparing to unpack .../40-libnl-genl-3-200_3.2.29-0ubuntu3_amd64.deb ...
Unpacking libnl-genl-3-200:amd64 (3.2.29-0ubuntu3) ...
Selecting previously unselected package libnss-mdns:amd64.
Preparing to unpack .../41-libnss-mdns_0.10-8ubuntu1_amd64.deb ...
Unpacking libnss-mdns:amd64 (0.10-8ubuntu1) ...
Selecting previously unselected package libpulse-mainloop-glib0:amd64.
Preparing to unpack .../42-libpulse-mainloop-glib0_1%3a11.1-1ubuntu7.11_amd64.deb ...
Unpacking libpulse-mainloop-glib0:amd64 (1:11.1-1ubuntu7.11) ...
Selecting previously unselected package libpulse-dev:amd64.
Preparing to unpack .../43-libpulse-dev_1%3a11.1-1ubuntu7.11_amd64.deb ...
Unpacking libpulse-dev:amd64 (1:11.1-1ubuntu7.11) ...
Selecting previously unselected package libqt5multimedia5:amd64.
Preparing to unpack .../44-libqt5multimedia5_5.9.5-0ubuntu1_amd64.deb ...
Unpacking libqt5multimedia5:amd64 (5.9.5-0ubuntu1) ...
Selecting previously unselected package libqt5opengl5:amd64.
Preparing to unpack .../45-libqt5opengl5_5.9.5+dfsg-0ubuntu2.5_amd64.deb ...
Unpacking libqt5opengl5:amd64 (5.9.5+dfsg-0ubuntu2.5) ...
Selecting previously unselected package libqt5multimediawidgets5:amd64.
Preparing to unpack .../46-libqt5multimediawidgets5_5.9.5-0ubuntu1_amd64.deb ...
Unpacking libqt5multimediawidgets5:amd64 (5.9.5-0ubuntu1) ...
Selecting previously unselected package libqgsttools-p1:amd64.
Preparing to unpack .../47-libqgsttools-p1_5.9.5-0ubuntu1_amd64.deb ...
Unpacking libqgsttools-p1:amd64 (5.9.5-0ubuntu1) ...
Selecting previously unselected package libqmi-glib5:amd64.
Preparing to unpack .../48-libqmi-glib5_1.22.0-1.2~ubuntu18.04.1_amd64.deb ...
Unpacking libqmi-glib5:amd64 (1.22.0-1.2~ubuntu18.04.1) ...
Selecting previously unselected package libqmi-proxy.
Preparing to unpack .../49-libqmi-proxy_1.22.0-1.2~ubuntu18.04.1_amd64.deb ...
Unpacking libqmi-proxy (1.22.0-1.2~ubuntu18.04.1) ...
Selecting previously unselected package libqt5designer5:amd64.
Preparing to unpack .../50-libqt5designer5_5.9.5-0ubuntu1_amd64.deb ...
Unpacking libqt5designer5:amd64 (5.9.5-0ubuntu1) ...
Selecting previously unselected package libqt5designercomponents5:amd64.
Preparing to unpack .../51-libqt5designercomponents5_5.9.5-0ubuntu1_amd64.deb ...
Unpacking libqt5designercomponents5:amd64 (5.9.5-0ubuntu1) ...
Selecting previously unselected package libqt5help5:amd64.
Preparing to unpack .../52-libqt5help5_5.9.5-0ubuntu1_amd64.deb ...
Unpacking libqt5help5:amd64 (5.9.5-0ubuntu1) ...
Selecting previously unselected package libqt5multimediaquick-p5:amd64.
Preparing to unpack .../53-libqt5multimediaquick-p5_5.9.5-0ubuntu1_amd64.deb ...
Unpacking libqt5multimediaquick-p5:amd64 (5.9.5-0ubuntu1) ...
Selecting previously unselected package libqt5quickparticles5:amd64.
Preparing to unpack .../54-libqt5quickparticles5_5.9.5-0ubuntu1.1_amd64.deb ...
Unpacking libqt5quickparticles5:amd64 (5.9.5-0ubuntu1.1) ...
Selecting previously unselected package libqt5quicktest5:amd64.
Preparing to unpack .../55-libqt5quicktest5_5.9.5-0ubuntu1.1_amd64.deb ...
Unpacking libqt5quicktest5:amd64 (5.9.5-0ubuntu1.1) ...
Selecting previously unselected package libqt5quickwidgets5:amd64.
Preparing to unpack .../56-libqt5quickwidgets5_5.9.5-0ubuntu1.1_amd64.deb ...
Unpacking libqt5quickwidgets5:amd64 (5.9.5-0ubuntu1.1) ...
Selecting previously unselected package libqt5sql5-sqlite:amd64.
Preparing to unpack .../57-libqt5sql5-sqlite_5.9.5+dfsg-0ubuntu2.5_amd64.deb ...
Unpacking libqt5sql5-sqlite:amd64 (5.9.5+dfsg-0ubuntu2.5) ...
Selecting previously unselected package modemmanager.
Preparing to unpack .../58-modemmanager_1.10.0-1~ubuntu18.04.2_amd64.deb ...
Unpacking modemmanager (1.10.0-1~ubuntu18.04.2) ...
Selecting previously unselected package qt5-assistant.
Preparing to unpack .../59-qt5-assistant_5.9.5-0ubuntu1_amd64.deb ...
Unpacking qt5-assistant (5.9.5-0ubuntu1) ...
Selecting previously unselected package qt5-qmltooling-plugins:amd64.
Preparing to unpack .../60-qt5-qmltooling-plugins_5.9.5-0ubuntu1.1_amd64.deb ...
Unpacking qt5-qmltooling-plugins:amd64 (5.9.5-0ubuntu1.1) ...
Selecting previously unselected package qtdeclarative5-dev:amd64.
Preparing to unpack .../61-qtdeclarative5-dev_5.9.5-0ubuntu1.1_amd64.deb ...
Unpacking qtdeclarative5-dev:amd64 (5.9.5-0ubuntu1.1) ...
Selecting previously unselected package qtmultimedia5-dev:amd64.
Preparing to unpack .../62-qtmultimedia5-dev_5.9.5-0ubuntu1_amd64.deb ...
Unpacking qtmultimedia5-dev:amd64 (5.9.5-0ubuntu1) ...
Selecting previously unselected package qttools5-dev-tools.
Preparing to unpack .../63-qttools5-dev-tools_5.9.5-0ubuntu1_amd64.deb ...
Unpacking qttools5-dev-tools (5.9.5-0ubuntu1) ...
Selecting previously unselected package qttools5-dev:amd64.
Preparing to unpack .../64-qttools5-dev_5.9.5-0ubuntu1_amd64.deb ...
Unpacking qttools5-dev:amd64 (5.9.5-0ubuntu1) ...
Selecting previously unselected package wpasupplicant.
Preparing to unpack .../65-wpasupplicant_2%3a2.6-15ubuntu2.8_amd64.deb ...
Unpacking wpasupplicant (2:2.6-15ubuntu2.8) ...
Selecting previously unselected package usb-modeswitch-data.
Preparing to unpack .../66-usb-modeswitch-data_20170806-2_all.deb ...
Unpacking usb-modeswitch-data (20170806-2) ...
Selecting previously unselected package usb-modeswitch.
Preparing to unpack .../67-usb-modeswitch_2.5.2+repack0-2ubuntu1_amd64.deb ...
Unpacking usb-modeswitch (2.5.2+repack0-2ubuntu1) ...
Setting up libqt5qml5:amd64 (5.9.5-0ubuntu1.1) ...
Setting up libbrotli1:amd64 (1.0.3-1ubuntu1.3) ...
Setting up libqt5quick5:amd64 (5.9.5-0ubuntu1.1) ...
Setting up libqt5script5:amd64 (5.9.5+dfsg-0ubuntu1) ...
Setting up libisc169:amd64 (1:9.11.3+dfsg-1ubuntu1.14) ...
Setting up libqt5sensors5:amd64 (5.9.5-0ubuntu1) ...
Setting up libdaemon0:amd64 (0.14-6) ...
Setting up libisccc160:amd64 (1:9.11.3+dfsg-1ubuntu1.14) ...
Setting up libqt5quickwidgets5:amd64 (5.9.5-0ubuntu1.1) ...
Setting up libmbim-glib4:amd64 (1.18.0-1~ubuntu18.04.1) ...
Setting up libpulse-mainloop-glib0:amd64 (1:11.1-1ubuntu7.11) ...
Setting up libpam-cap:amd64 (1:2.25-1.2) ...
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.)
debconf: falling back to frontend: Readline
Setting up libpulse-dev:amd64 (1:11.1-1ubuntu7.11) ...
Setting up iio-sensor-proxy (2.4-2) ...
Setting up libwoff1:amd64 (1.0.2-1build0.1) ...
Setting up geoip-database (20180315-1) ...
Setting up libcap2-bin (1:2.25-1.2) ...
Setting up libnl-genl-3-200:amd64 (3.2.29-0ubuntu3) ...
Setting up libgeoip1:amd64 (1.6.12-1) ...
Setting up libcdparanoia0:amd64 (3.10.2+debian-13) ...
Setting up libqt5help5:amd64 (5.9.5-0ubuntu1) ...
Setting up libqt5opengl5:amd64 (5.9.5+dfsg-0ubuntu2.5) ...
Setting up libmbim-proxy (1.18.0-1~ubuntu18.04.1) ...
Setting up libqt5multimedia5:amd64 (5.9.5-0ubuntu1) ...
Setting up usb-modeswitch-data (20170806-2) ...
Setting up libqt5sql5-sqlite:amd64 (5.9.5+dfsg-0ubuntu2.5) ...
Setting up libqt5quickparticles5:amd64 (5.9.5-0ubuntu1.1) ...
Setting up libhyphen0:amd64 (2.8.8-5) ...
Setting up usb-modeswitch (2.5.2+repack0-2ubuntu1) ...
Setting up libqt5quicktest5:amd64 (5.9.5-0ubuntu1.1) ...
Setting up libqt5scripttools5:amd64 (5.9.5+dfsg-0ubuntu1) ...
Setting up libmm-glib0:amd64 (1.10.0-1~ubuntu18.04.2) ...
Setting up libgl1-mesa-glx:amd64 (20.0.8-0ubuntu1~18.04.1) ...
Setting up libqt5positioning5:amd64 (5.9.5+dfsg-0ubuntu2) ...
Setting up libqt5multimediaquick-p5:amd64 (5.9.5-0ubuntu1) ...
Setting up libvisual-0.4-0:amd64 (0.4.0-11) ...
Setting up qtscript5-dev:amd64 (5.9.5+dfsg-0ubuntu1) ...
Setting up liborc-0.4-0:amd64 (1:0.4.28-1) ...
Setting up libavahi-glib1:amd64 (0.7-3.1ubuntu1.2) ...
Setting up libqt5webchannel5:amd64 (5.9.5-0ubuntu1) ...
Setting up libqt5designer5:amd64 (5.9.5-0ubuntu1) ...
Setting up libdns1100:amd64 (1:9.11.3+dfsg-1ubuntu1.14) ...
Setting up liblwres160:amd64 (1:9.11.3+dfsg-1ubuntu1.14) ...
Setting up qt5-qmltooling-plugins:amd64 (5.9.5-0ubuntu1.1) ...
Setting up libavahi-core7:amd64 (0.7-3.1ubuntu1.2) ...
Setting up libqt5multimediawidgets5:amd64 (5.9.5-0ubuntu1) ...
Setting up libgstreamer1.0-0:amd64 (1.14.5-0ubuntu1~18.04.1) ...
Setcap worked! gst-ptp-helper is not suid!
Setting up libqt5designercomponents5:amd64 (5.9.5-0ubuntu1) ...
Setting up wpasupplicant (2:2.6-15ubuntu2.8) ...
Created symlink /etc/systemd/system/dbus-fi.w1.wpa_supplicant1.service → /lib/systemd/system/wpa_supplicant.service.
Created symlink /etc/systemd/system/multi-user.target.wants/wpa_supplicant.service → /lib/systemd/system/wpa_supplicant.service.
Setting up libqmi-glib5:amd64 (1.22.0-1.2~ubuntu18.04.1) ...
Setting up libqmi-proxy (1.22.0-1.2~ubuntu18.04.1) ...
Setting up qtdeclarative5-dev:amd64 (5.9.5-0ubuntu1.1) ...
Setting up libisccfg160:amd64 (1:9.11.3+dfsg-1ubuntu1.14) ...
Setting up libgstreamer-plugins-base1.0-0:amd64 (1.14.5-0ubuntu1~18.04.1) ...
Setting up gstreamer1.0-plugins-base:amd64 (1.14.5-0ubuntu1~18.04.1) ...
Setting up libqgsttools-p1:amd64 (5.9.5-0ubuntu1) ...
Setting up libqt5webkit5:amd64 (5.212.0~alpha2-7ubuntu1) ...
Setting up modemmanager (1.10.0-1~ubuntu18.04.2) ...
Created symlink /etc/systemd/system/dbus-org.freedesktop.ModemManager1.service → /lib/systemd/system/ModemManager.service.
Created symlink /etc/systemd/system/multi-user.target.wants/ModemManager.service → /lib/systemd/system/ModemManager.service.
Setting up libbind9-160:amd64 (1:9.11.3+dfsg-1ubuntu1.14) ...
Setting up qtmultimedia5-dev:amd64 (5.9.5-0ubuntu1) ...
Setting up qt5-assistant (5.9.5-0ubuntu1) ...
Setting up bind9-host (1:9.11.3+dfsg-1ubuntu1.14) ...
Setting up avahi-daemon (0.7-3.1ubuntu1.2) ...
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of force-reload.
Created symlink /etc/systemd/system/dbus-org.freedesktop.Avahi.service → /lib/systemd/system/avahi-daemon.service.
Created symlink /etc/systemd/system/multi-user.target.wants/avahi-daemon.service → /lib/systemd/system/avahi-daemon.service.
Created symlink /etc/systemd/system/sockets.target.wants/avahi-daemon.socket → /lib/systemd/system/avahi-daemon.socket.
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of start.
Setting up qttools5-dev-tools (5.9.5-0ubuntu1) ...
Setting up libnss-mdns:amd64 (0.10-8ubuntu1) ...
First installation detected...
Checking NSS setup...
Setting up qttools5-dev:amd64 (5.9.5-0ubuntu1) ...
Setting up libgeoclue-2-0:amd64 (2.4.7-1ubuntu1) ...
Setting up geoclue-2.0 (2.4.7-1ubuntu1) ...
Processing triggers for libc-bin (2.27-3ubuntu1.2) ...
/sbin/ldconfig.real: /usr/local/lib/python3.7/dist-packages/ideep4py/lib/libmkldnn.so.0 is not a symbolic link

Processing triggers for systemd (237-3ubuntu10.45) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Processing triggers for dbus (1.12.2-1ubuntu1.2) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for mime-support (3.60ubuntu1) ...
+ sudo apt-get install -qq g++ cmake libssl-dev nodejs npm
E: Unable to correct problems, you have held broken packages.
+ installed
build.sh: 37: build.sh: installed: not found
+ type emerge
+ no_pm
build.sh: 40: build.sh: no_pm: not found
+ !installed
build.sh: 44: build.sh: !installed: not found
+ 0
build.sh: 47: build.sh: 0: not found
+ ./scripts/build.sh gui translations
/content/imgbrd-grabber/build /content/imgbrd-grabber
-- The C compiler identification is GNU 7.5.0
-- The CXX compiler identification is GNU 7.5.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring for version '7.5.1'
-- Configuring for platform 'x86' (x86_64)
-- Compiling with SSL support
-- Found OpenSSL: /usr/lib/x86_64-linux-gnu/libcrypto.so (found version "1.1.1")
-- OpenSSL version: 1.1.1
-- OpenSSL include dir: /usr/include
-- OpenSSL libraries: /usr/lib/x86_64-linux-gnu/libssl.so;/usr/lib/x86_64-linux-gnu/libcrypto.so
-- Configuring done
-- Generating done
-- Build files have been written to: /content/imgbrd-grabber/build
Scanning dependencies of target sites_modules
Scanning dependencies of target lib_autogen
[  1%] Installing npm packages...
[  1%] Automatic MOC and UIC for target lib
npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!
[  1%] Built target lib_autogen
Scanning dependencies of target lib
[  1%] Building CXX object lib/CMakeFiles/lib.dir/src/analytics.cpp.o
[  1%] Building CXX object lib/CMakeFiles/lib.dir/src/auth/auth-const-field.cpp.o
[  1%] Building CXX object lib/CMakeFiles/lib.dir/src/auth/auth-field.cpp.o
[  3%] Building CXX object lib/CMakeFiles/lib.dir/src/auth/auth-hash-field.cpp.o
[  3%] Building CXX object lib/CMakeFiles/lib.dir/src/auth/auth.cpp.o
[  3%] Building CXX object lib/CMakeFiles/lib.dir/src/auth/field-auth.cpp.o
[  3%] Building CXX object lib/CMakeFiles/lib.dir/src/auth/http-auth.cpp.o
[  4%] Building CXX object lib/CMakeFiles/lib.dir/src/auth/http-basic-auth.cpp.o
[  4%] Building CXX object lib/CMakeFiles/lib.dir/src/auth/oauth2-auth.cpp.o
[  4%] Building CXX object lib/CMakeFiles/lib.dir/src/auth/url-auth.cpp.o
[  4%] Building CXX object lib/CMakeFiles/lib.dir/src/cli/cli.cpp.o
[  6%] Building CXX object lib/CMakeFiles/lib.dir/src/cli/commands/cli-command.cpp.o
[  6%] Building CXX object lib/CMakeFiles/lib.dir/src/cli/commands/download-images-cli-command.cpp.o
/content/imgbrd-grabber/src/lib/src/cli/cli.cpp: In function ‘int parseAndRunCliArgs(QCoreApplication*, Profile*, bool, QMap<QString, QString>&, QStringList&)’:
/content/imgbrd-grabber/src/lib/src/cli/cli.cpp:160:83: error: ‘SkipEmptyParts’ is not a member of ‘Qt’
  auto sites = profile->getFilteredSites(parser.value(sourceOption).split(" ", Qt::SkipEmptyParts));
                                                                                ^~~~~~~~~~~~~~
/content/imgbrd-grabber/src/lib/src/cli/cli.cpp:162:21: error: unable to deduce ‘auto&&’ from ‘sites’
   for (auto& site : sites) {
                     ^~~~~
/content/imgbrd-grabber/src/lib/src/cli/cli.cpp:183:68: error: ‘SkipEmptyParts’ is not a member of ‘Qt’
   const QStringList tags = parser.value(tagsOption).split(" ", Qt::SkipEmptyParts);
                                                                    ^~~~~~~~~~~~~~
/content/imgbrd-grabber/src/lib/src/cli/cli.cpp:184:86: error: ‘SkipEmptyParts’ is not a member of ‘Qt’
   const QStringList postFiltering = parser.value(postFilteringOption).split(" ", Qt::SkipEmptyParts);
                                                                                ^~~~~~~~~~~~~~
/content/imgbrd-grabber/src/lib/src/cli/cli.cpp:190:68: error: ‘SkipEmptyParts’ is not a member of ‘Qt’
   const QStringList tags = parser.value(tagsOption).split(" ", Qt::SkipEmptyParts);
                                                                    ^~~~~~~~~~~~~~
/content/imgbrd-grabber/src/lib/src/cli/cli.cpp:191:86: error: ‘SkipEmptyParts’ is not a member of ‘Qt’
   const QStringList postFiltering = parser.value(postFilteringOption).split(" ", Qt::SkipEmptyParts);
                                                                                ^~~~~~~~~~~~~~
/content/imgbrd-grabber/src/lib/src/cli/cli.cpp:205:68: error: ‘SkipEmptyParts’ is not a member of ‘Qt’
   const QStringList tags = parser.value(tagsOption).split(" ", Qt::SkipEmptyParts);
                                                                    ^~~~~~~~~~~~~~
/content/imgbrd-grabber/src/lib/src/cli/cli.cpp:206:86: error: ‘SkipEmptyParts’ is not a member of ‘Qt’
   const QStringList postFiltering = parser.value(postFilteringOption).split(" ", Qt::SkipEmptyParts);
                                                                                ^~~~~~~~~~~~~~
/content/imgbrd-grabber/src/lib/src/cli/cli.cpp:219:68: error: ‘SkipEmptyParts’ is not a member of ‘Qt’
   const QStringList tags = parser.value(tagsOption).split(" ", Qt::SkipEmptyParts);
                                                                    ^~~~~~~~~~~~~~
/content/imgbrd-grabber/src/lib/src/cli/cli.cpp:220:86: error: ‘SkipEmptyParts’ is not a member of ‘Qt’
   const QStringList postFiltering = parser.value(postFilteringOption).split(" ", Qt::SkipEmptyParts);
                                                                                ^~~~~~~~~~~~~~
lib/CMakeFiles/lib.dir/build.make:192: recipe for target 'lib/CMakeFiles/lib.dir/src/cli/cli.cpp.o' failed
make[3]: *** [lib/CMakeFiles/lib.dir/src/cli/cli.cpp.o] Error 1
make[3]: *** Waiting for unfinished jobs....
CMakeFiles/Makefile2:124: recipe for target 'lib/CMakeFiles/lib.dir/all' failed
make[2]: *** [lib/CMakeFiles/lib.dir/all] Error 2
make[2]: *** Waiting for unfinished jobs....
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

added 535 packages from 436 contributors and audited 536 packages in 24.055s

24 packages are looking for funding
  run `npm fund` for details

found 18 high severity vulnerabilities
  run `npm audit fix` to fix them, or `npm audit` for details
[  6%] Built target sites_modules
CMakeFiles/Makefile2:226: recipe for target 'gui/CMakeFiles/gui.dir/rule' failed
make[1]: *** [gui/CMakeFiles/gui.dir/rule] Error 2
Makefile:214: recipe for target 'gui' failed
make: *** [gui] Error 2
/content/imgbrd-grabber
+ exit 21

I see there 3 errors:

build.sh: 3: build.sh: [[: not found, build.sh: 16: build.sh: declare: not found and so on. These can be fixed by running /usr/bin/env bash -x build.sh or just /bin/bash -x build.shinstead ofsh -x build.sh`
E: Unable to correct problems, you have held broken packages.. I found that this is problem with installing npm. I fixed this by changing this line in build.sh:

$permission apt-get install -qq "g++" "cmake" "libssl-dev" "nodejs" "npm" && installed=1

into these:
curl -sL https://deb.nodesource.com/setup_12.x | sudo -E bash - || continue
$permission apt-get install -y nodejs || continue
$permission npm install -g npm@latest && installed=1

...error: ‘SkipEmptyParts’ is not a member of ‘Qt’. For this i found soultion here: Change all Qt::SkipEmptyParts to QString::SplitBehavior::SkipEmptyParts. I've done this, and now my output looks like this:

+ [[ '' == \r\o\o\t ]]
+ type sudo
+ permission='sudo '
+ git submodule update --init --recursive
Submodule 'cmake/cotire' (https://github.com/sakra/cotire.git) registered for path 'src/cmake/cotire'
Submodule 'cmake/qt-android-cmake' (https://github.com/LaurentGomila/qt-android-cmake.git) registered for path 'src/cmake/qt-android-cmake'
Submodule 'tests/src/vendor/catch' (https://github.com/catchorg/Catch2.git) registered for path 'src/tests/src/vendor/catch'
Cloning into '/content/imgbrd-grabber/src/cmake/cotire'...
Cloning into '/content/imgbrd-grabber/src/cmake/qt-android-cmake'...
Cloning into '/content/imgbrd-grabber/src/tests/src/vendor/catch'...
Submodule path 'src/cmake/cotire': checked out '391bf6b7609e14f5976bd5247b68d63cbf8d4d12'
Submodule path 'src/cmake/qt-android-cmake': checked out '5a62962dbe35e955374688461784ddb7f757a377'
Submodule path 'src/tests/src/vendor/catch': checked out 'f0dc4d9be078d21ccabcb0798f03c332a153f84f'
+ declare -i no_pm=1 installed=0
+ for pm in pacman apt-get emerge
+ type pacman
+ for pm in pacman apt-get emerge
+ type apt-get
+ no_pm=0
+ case "$pm" in
+ sudo apt-get install -qq qtbase5-dev qtscript5-dev qtmultimedia5-dev qtdeclarative5-dev qttools5-dev qttools5-dev-tools
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76, <> line 68.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
Selecting previously unselected package libdaemon0:amd64.
(Reading database ... 160983 files and directories currently installed.)
Preparing to unpack .../00-libdaemon0_0.14-6_amd64.deb ...
Unpacking libdaemon0:amd64 (0.14-6) ...
Selecting previously unselected package libqt5script5:amd64.
Preparing to unpack .../01-libqt5script5_5.9.5+dfsg-0ubuntu1_amd64.deb ...
Unpacking libqt5script5:amd64 (5.9.5+dfsg-0ubuntu1) ...
Selecting previously unselected package libqt5scripttools5:amd64.
Preparing to unpack .../02-libqt5scripttools5_5.9.5+dfsg-0ubuntu1_amd64.deb ...
Unpacking libqt5scripttools5:amd64 (5.9.5+dfsg-0ubuntu1) ...
Selecting previously unselected package libcap2-bin.
Preparing to unpack .../03-libcap2-bin_1%3a2.25-1.2_amd64.deb ...
Unpacking libcap2-bin (1:2.25-1.2) ...
Selecting previously unselected package libgstreamer1.0-0:amd64.
Preparing to unpack .../04-libgstreamer1.0-0_1.14.5-0ubuntu1~18.04.1_amd64.deb ...
Unpacking libgstreamer1.0-0:amd64 (1.14.5-0ubuntu1~18.04.1) ...
Selecting previously unselected package liborc-0.4-0:amd64.
Preparing to unpack .../05-liborc-0.4-0_1%3a0.4.28-1_amd64.deb ...
Unpacking liborc-0.4-0:amd64 (1:0.4.28-1) ...
Selecting previously unselected package libgstreamer-plugins-base1.0-0:amd64.
Preparing to unpack .../06-libgstreamer-plugins-base1.0-0_1.14.5-0ubuntu1~18.04.1_amd64.deb ...
Unpacking libgstreamer-plugins-base1.0-0:amd64 (1.14.5-0ubuntu1~18.04.1) ...
Selecting previously unselected package libhyphen0:amd64.
Preparing to unpack .../07-libhyphen0_2.8.8-5_amd64.deb ...
Unpacking libhyphen0:amd64 (2.8.8-5) ...
Selecting previously unselected package libqt5positioning5:amd64.
Preparing to unpack .../08-libqt5positioning5_5.9.5+dfsg-0ubuntu2_amd64.deb ...
Unpacking libqt5positioning5:amd64 (5.9.5+dfsg-0ubuntu2) ...
Selecting previously unselected package libqt5qml5:amd64.
Preparing to unpack .../09-libqt5qml5_5.9.5-0ubuntu1.1_amd64.deb ...
Unpacking libqt5qml5:amd64 (5.9.5-0ubuntu1.1) ...
Selecting previously unselected package libqt5quick5:amd64.
Preparing to unpack .../10-libqt5quick5_5.9.5-0ubuntu1.1_amd64.deb ...
Unpacking libqt5quick5:amd64 (5.9.5-0ubuntu1.1) ...
Selecting previously unselected package libqt5sensors5:amd64.
Preparing to unpack .../11-libqt5sensors5_5.9.5-0ubuntu1_amd64.deb ...
Unpacking libqt5sensors5:amd64 (5.9.5-0ubuntu1) ...
Selecting previously unselected package libqt5webchannel5:amd64.
Preparing to unpack .../12-libqt5webchannel5_5.9.5-0ubuntu1_amd64.deb ...
Unpacking libqt5webchannel5:amd64 (5.9.5-0ubuntu1) ...
Selecting previously unselected package libbrotli1:amd64.
Preparing to unpack .../13-libbrotli1_1.0.3-1ubuntu1.3_amd64.deb ...
Unpacking libbrotli1:amd64 (1.0.3-1ubuntu1.3) ...
Selecting previously unselected package libwoff1:amd64.
Preparing to unpack .../14-libwoff1_1.0.2-1build0.1_amd64.deb ...
Unpacking libwoff1:amd64 (1.0.2-1build0.1) ...
Selecting previously unselected package libqt5webkit5:amd64.
Preparing to unpack .../15-libqt5webkit5_5.212.0~alpha2-7ubuntu1_amd64.deb ...
Unpacking libqt5webkit5:amd64 (5.212.0~alpha2-7ubuntu1) ...
Selecting previously unselected package qtscript5-dev:amd64.
Preparing to unpack .../16-qtscript5-dev_5.9.5+dfsg-0ubuntu1_amd64.deb ...
Unpacking qtscript5-dev:amd64 (5.9.5+dfsg-0ubuntu1) ...
Selecting previously unselected package libpam-cap:amd64.
Preparing to unpack .../17-libpam-cap_1%3a2.25-1.2_amd64.deb ...
Unpacking libpam-cap:amd64 (1:2.25-1.2) ...
Selecting previously unselected package libisc169:amd64.
Preparing to unpack .../18-libisc169_1%3a9.11.3+dfsg-1ubuntu1.14_amd64.deb ...
Unpacking libisc169:amd64 (1:9.11.3+dfsg-1ubuntu1.14) ...
Selecting previously unselected package libgeoip1:amd64.
Preparing to unpack .../19-libgeoip1_1.6.12-1_amd64.deb ...
Unpacking libgeoip1:amd64 (1.6.12-1) ...
Selecting previously unselected package libdns1100:amd64.
Preparing to unpack .../20-libdns1100_1%3a9.11.3+dfsg-1ubuntu1.14_amd64.deb ...
Unpacking libdns1100:amd64 (1:9.11.3+dfsg-1ubuntu1.14) ...
Selecting previously unselected package libisccc160:amd64.
Preparing to unpack .../21-libisccc160_1%3a9.11.3+dfsg-1ubuntu1.14_amd64.deb ...
Unpacking libisccc160:amd64 (1:9.11.3+dfsg-1ubuntu1.14) ...
Selecting previously unselected package libisccfg160:amd64.
Preparing to unpack .../22-libisccfg160_1%3a9.11.3+dfsg-1ubuntu1.14_amd64.deb ...
Unpacking libisccfg160:amd64 (1:9.11.3+dfsg-1ubuntu1.14) ...
Selecting previously unselected package libbind9-160:amd64.
Preparing to unpack .../23-libbind9-160_1%3a9.11.3+dfsg-1ubuntu1.14_amd64.deb ...
Unpacking libbind9-160:amd64 (1:9.11.3+dfsg-1ubuntu1.14) ...
Selecting previously unselected package liblwres160:amd64.
Preparing to unpack .../24-liblwres160_1%3a9.11.3+dfsg-1ubuntu1.14_amd64.deb ...
Unpacking liblwres160:amd64 (1:9.11.3+dfsg-1ubuntu1.14) ...
Selecting previously unselected package bind9-host.
Preparing to unpack .../25-bind9-host_1%3a9.11.3+dfsg-1ubuntu1.14_amd64.deb ...
Unpacking bind9-host (1:9.11.3+dfsg-1ubuntu1.14) ...
Selecting previously unselected package geoip-database.
Preparing to unpack .../26-geoip-database_20180315-1_all.deb ...
Unpacking geoip-database (20180315-1) ...
Selecting previously unselected package libavahi-core7:amd64.
Preparing to unpack .../27-libavahi-core7_0.7-3.1ubuntu1.2_amd64.deb ...
Unpacking libavahi-core7:amd64 (0.7-3.1ubuntu1.2) ...
Selecting previously unselected package avahi-daemon.
Preparing to unpack .../28-avahi-daemon_0.7-3.1ubuntu1.2_amd64.deb ...
Unpacking avahi-daemon (0.7-3.1ubuntu1.2) ...
Selecting previously unselected package libavahi-glib1:amd64.
Preparing to unpack .../29-libavahi-glib1_0.7-3.1ubuntu1.2_amd64.deb ...
Unpacking libavahi-glib1:amd64 (0.7-3.1ubuntu1.2) ...
Selecting previously unselected package libgeoclue-2-0:amd64.
Preparing to unpack .../30-libgeoclue-2-0_2.4.7-1ubuntu1_amd64.deb ...
Unpacking libgeoclue-2-0:amd64 (2.4.7-1ubuntu1) ...
Selecting previously unselected package libmm-glib0:amd64.
Preparing to unpack .../31-libmm-glib0_1.10.0-1~ubuntu18.04.2_amd64.deb ...
Unpacking libmm-glib0:amd64 (1.10.0-1~ubuntu18.04.2) ...
Selecting previously unselected package geoclue-2.0.
Preparing to unpack .../32-geoclue-2.0_2.4.7-1ubuntu1_amd64.deb ...
Unpacking geoclue-2.0 (2.4.7-1ubuntu1) ...
Selecting previously unselected package libcdparanoia0:amd64.
Preparing to unpack .../33-libcdparanoia0_3.10.2+debian-13_amd64.deb ...
Unpacking libcdparanoia0:amd64 (3.10.2+debian-13) ...
Selecting previously unselected package libvisual-0.4-0:amd64.
Preparing to unpack .../34-libvisual-0.4-0_0.4.0-11_amd64.deb ...
Unpacking libvisual-0.4-0:amd64 (0.4.0-11) ...
Selecting previously unselected package gstreamer1.0-plugins-base:amd64.
Preparing to unpack .../35-gstreamer1.0-plugins-base_1.14.5-0ubuntu1~18.04.1_amd64.deb ...
Unpacking gstreamer1.0-plugins-base:amd64 (1.14.5-0ubuntu1~18.04.1) ...
Selecting previously unselected package iio-sensor-proxy.
Preparing to unpack .../36-iio-sensor-proxy_2.4-2_amd64.deb ...
Unpacking iio-sensor-proxy (2.4-2) ...
Selecting previously unselected package libgl1-mesa-glx:amd64.
Preparing to unpack .../37-libgl1-mesa-glx_20.0.8-0ubuntu1~18.04.1_amd64.deb ...
Unpacking libgl1-mesa-glx:amd64 (20.0.8-0ubuntu1~18.04.1) ...
Selecting previously unselected package libmbim-glib4:amd64.
Preparing to unpack .../38-libmbim-glib4_1.18.0-1~ubuntu18.04.1_amd64.deb ...
Unpacking libmbim-glib4:amd64 (1.18.0-1~ubuntu18.04.1) ...
Selecting previously unselected package libmbim-proxy.
Preparing to unpack .../39-libmbim-proxy_1.18.0-1~ubuntu18.04.1_amd64.deb ...
Unpacking libmbim-proxy (1.18.0-1~ubuntu18.04.1) ...
Selecting previously unselected package libnl-genl-3-200:amd64.
Preparing to unpack .../40-libnl-genl-3-200_3.2.29-0ubuntu3_amd64.deb ...
Unpacking libnl-genl-3-200:amd64 (3.2.29-0ubuntu3) ...
Selecting previously unselected package libnss-mdns:amd64.
Preparing to unpack .../41-libnss-mdns_0.10-8ubuntu1_amd64.deb ...
Unpacking libnss-mdns:amd64 (0.10-8ubuntu1) ...
Selecting previously unselected package libpulse-mainloop-glib0:amd64.
Preparing to unpack .../42-libpulse-mainloop-glib0_1%3a11.1-1ubuntu7.11_amd64.deb ...
Unpacking libpulse-mainloop-glib0:amd64 (1:11.1-1ubuntu7.11) ...
Selecting previously unselected package libpulse-dev:amd64.
Preparing to unpack .../43-libpulse-dev_1%3a11.1-1ubuntu7.11_amd64.deb ...
Unpacking libpulse-dev:amd64 (1:11.1-1ubuntu7.11) ...
Selecting previously unselected package libqt5multimedia5:amd64.
Preparing to unpack .../44-libqt5multimedia5_5.9.5-0ubuntu1_amd64.deb ...
Unpacking libqt5multimedia5:amd64 (5.9.5-0ubuntu1) ...
Selecting previously unselected package libqt5opengl5:amd64.
Preparing to unpack .../45-libqt5opengl5_5.9.5+dfsg-0ubuntu2.5_amd64.deb ...
Unpacking libqt5opengl5:amd64 (5.9.5+dfsg-0ubuntu2.5) ...
Selecting previously unselected package libqt5multimediawidgets5:amd64.
Preparing to unpack .../46-libqt5multimediawidgets5_5.9.5-0ubuntu1_amd64.deb ...
Unpacking libqt5multimediawidgets5:amd64 (5.9.5-0ubuntu1) ...
Selecting previously unselected package libqgsttools-p1:amd64.
Preparing to unpack .../47-libqgsttools-p1_5.9.5-0ubuntu1_amd64.deb ...
Unpacking libqgsttools-p1:amd64 (5.9.5-0ubuntu1) ...
Selecting previously unselected package libqmi-glib5:amd64.
Preparing to unpack .../48-libqmi-glib5_1.22.0-1.2~ubuntu18.04.1_amd64.deb ...
Unpacking libqmi-glib5:amd64 (1.22.0-1.2~ubuntu18.04.1) ...
Selecting previously unselected package libqmi-proxy.
Preparing to unpack .../49-libqmi-proxy_1.22.0-1.2~ubuntu18.04.1_amd64.deb ...
Unpacking libqmi-proxy (1.22.0-1.2~ubuntu18.04.1) ...
Selecting previously unselected package libqt5designer5:amd64.
Preparing to unpack .../50-libqt5designer5_5.9.5-0ubuntu1_amd64.deb ...
Unpacking libqt5designer5:amd64 (5.9.5-0ubuntu1) ...
Selecting previously unselected package libqt5designercomponents5:amd64.
Preparing to unpack .../51-libqt5designercomponents5_5.9.5-0ubuntu1_amd64.deb ...
Unpacking libqt5designercomponents5:amd64 (5.9.5-0ubuntu1) ...
Selecting previously unselected package libqt5help5:amd64.
Preparing to unpack .../52-libqt5help5_5.9.5-0ubuntu1_amd64.deb ...
Unpacking libqt5help5:amd64 (5.9.5-0ubuntu1) ...
Selecting previously unselected package libqt5multimediaquick-p5:amd64.
Preparing to unpack .../53-libqt5multimediaquick-p5_5.9.5-0ubuntu1_amd64.deb ...
Unpacking libqt5multimediaquick-p5:amd64 (5.9.5-0ubuntu1) ...
Selecting previously unselected package libqt5quickparticles5:amd64.
Preparing to unpack .../54-libqt5quickparticles5_5.9.5-0ubuntu1.1_amd64.deb ...
Unpacking libqt5quickparticles5:amd64 (5.9.5-0ubuntu1.1) ...
Selecting previously unselected package libqt5quicktest5:amd64.
Preparing to unpack .../55-libqt5quicktest5_5.9.5-0ubuntu1.1_amd64.deb ...
Unpacking libqt5quicktest5:amd64 (5.9.5-0ubuntu1.1) ...
Selecting previously unselected package libqt5quickwidgets5:amd64.
Preparing to unpack .../56-libqt5quickwidgets5_5.9.5-0ubuntu1.1_amd64.deb ...
Unpacking libqt5quickwidgets5:amd64 (5.9.5-0ubuntu1.1) ...
Selecting previously unselected package libqt5sql5-sqlite:amd64.
Preparing to unpack .../57-libqt5sql5-sqlite_5.9.5+dfsg-0ubuntu2.5_amd64.deb ...
Unpacking libqt5sql5-sqlite:amd64 (5.9.5+dfsg-0ubuntu2.5) ...
Selecting previously unselected package modemmanager.
Preparing to unpack .../58-modemmanager_1.10.0-1~ubuntu18.04.2_amd64.deb ...
Unpacking modemmanager (1.10.0-1~ubuntu18.04.2) ...
Selecting previously unselected package qt5-assistant.
Preparing to unpack .../59-qt5-assistant_5.9.5-0ubuntu1_amd64.deb ...
Unpacking qt5-assistant (5.9.5-0ubuntu1) ...
Selecting previously unselected package qt5-qmltooling-plugins:amd64.
Preparing to unpack .../60-qt5-qmltooling-plugins_5.9.5-0ubuntu1.1_amd64.deb ...
Unpacking qt5-qmltooling-plugins:amd64 (5.9.5-0ubuntu1.1) ...
Selecting previously unselected package qtdeclarative5-dev:amd64.
Preparing to unpack .../61-qtdeclarative5-dev_5.9.5-0ubuntu1.1_amd64.deb ...
Unpacking qtdeclarative5-dev:amd64 (5.9.5-0ubuntu1.1) ...
Selecting previously unselected package qtmultimedia5-dev:amd64.
Preparing to unpack .../62-qtmultimedia5-dev_5.9.5-0ubuntu1_amd64.deb ...
Unpacking qtmultimedia5-dev:amd64 (5.9.5-0ubuntu1) ...
Selecting previously unselected package qttools5-dev-tools.
Preparing to unpack .../63-qttools5-dev-tools_5.9.5-0ubuntu1_amd64.deb ...
Unpacking qttools5-dev-tools (5.9.5-0ubuntu1) ...
Selecting previously unselected package qttools5-dev:amd64.
Preparing to unpack .../64-qttools5-dev_5.9.5-0ubuntu1_amd64.deb ...
Unpacking qttools5-dev:amd64 (5.9.5-0ubuntu1) ...
Selecting previously unselected package wpasupplicant.
Preparing to unpack .../65-wpasupplicant_2%3a2.6-15ubuntu2.8_amd64.deb ...
Unpacking wpasupplicant (2:2.6-15ubuntu2.8) ...
Selecting previously unselected package usb-modeswitch-data.
Preparing to unpack .../66-usb-modeswitch-data_20170806-2_all.deb ...
Unpacking usb-modeswitch-data (20170806-2) ...
Selecting previously unselected package usb-modeswitch.
Preparing to unpack .../67-usb-modeswitch_2.5.2+repack0-2ubuntu1_amd64.deb ...
Unpacking usb-modeswitch (2.5.2+repack0-2ubuntu1) ...
Setting up libqt5qml5:amd64 (5.9.5-0ubuntu1.1) ...
Setting up libbrotli1:amd64 (1.0.3-1ubuntu1.3) ...
Setting up libqt5quick5:amd64 (5.9.5-0ubuntu1.1) ...
Setting up libqt5script5:amd64 (5.9.5+dfsg-0ubuntu1) ...
Setting up libisc169:amd64 (1:9.11.3+dfsg-1ubuntu1.14) ...
Setting up libqt5sensors5:amd64 (5.9.5-0ubuntu1) ...
Setting up libdaemon0:amd64 (0.14-6) ...
Setting up libisccc160:amd64 (1:9.11.3+dfsg-1ubuntu1.14) ...
Setting up libqt5quickwidgets5:amd64 (5.9.5-0ubuntu1.1) ...
Setting up libmbim-glib4:amd64 (1.18.0-1~ubuntu18.04.1) ...
Setting up libpulse-mainloop-glib0:amd64 (1:11.1-1ubuntu7.11) ...
Setting up libpam-cap:amd64 (1:2.25-1.2) ...
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.)
debconf: falling back to frontend: Readline
Setting up libpulse-dev:amd64 (1:11.1-1ubuntu7.11) ...
Setting up iio-sensor-proxy (2.4-2) ...
Setting up libwoff1:amd64 (1.0.2-1build0.1) ...
Setting up geoip-database (20180315-1) ...
Setting up libcap2-bin (1:2.25-1.2) ...
Setting up libnl-genl-3-200:amd64 (3.2.29-0ubuntu3) ...
Setting up libgeoip1:amd64 (1.6.12-1) ...
Setting up libcdparanoia0:amd64 (3.10.2+debian-13) ...
Setting up libqt5help5:amd64 (5.9.5-0ubuntu1) ...
Setting up libqt5opengl5:amd64 (5.9.5+dfsg-0ubuntu2.5) ...
Setting up libmbim-proxy (1.18.0-1~ubuntu18.04.1) ...
Setting up libqt5multimedia5:amd64 (5.9.5-0ubuntu1) ...
Setting up usb-modeswitch-data (20170806-2) ...
Setting up libqt5sql5-sqlite:amd64 (5.9.5+dfsg-0ubuntu2.5) ...
Setting up libqt5quickparticles5:amd64 (5.9.5-0ubuntu1.1) ...
Setting up libhyphen0:amd64 (2.8.8-5) ...
Setting up usb-modeswitch (2.5.2+repack0-2ubuntu1) ...
Setting up libqt5quicktest5:amd64 (5.9.5-0ubuntu1.1) ...
Setting up libqt5scripttools5:amd64 (5.9.5+dfsg-0ubuntu1) ...
Setting up libmm-glib0:amd64 (1.10.0-1~ubuntu18.04.2) ...
Setting up libgl1-mesa-glx:amd64 (20.0.8-0ubuntu1~18.04.1) ...
Setting up libqt5positioning5:amd64 (5.9.5+dfsg-0ubuntu2) ...
Setting up libqt5multimediaquick-p5:amd64 (5.9.5-0ubuntu1) ...
Setting up libvisual-0.4-0:amd64 (0.4.0-11) ...
Setting up qtscript5-dev:amd64 (5.9.5+dfsg-0ubuntu1) ...
Setting up liborc-0.4-0:amd64 (1:0.4.28-1) ...
Setting up libavahi-glib1:amd64 (0.7-3.1ubuntu1.2) ...
Setting up libqt5webchannel5:amd64 (5.9.5-0ubuntu1) ...
Setting up libqt5designer5:amd64 (5.9.5-0ubuntu1) ...
Setting up libdns1100:amd64 (1:9.11.3+dfsg-1ubuntu1.14) ...
Setting up liblwres160:amd64 (1:9.11.3+dfsg-1ubuntu1.14) ...
Setting up qt5-qmltooling-plugins:amd64 (5.9.5-0ubuntu1.1) ...
Setting up libavahi-core7:amd64 (0.7-3.1ubuntu1.2) ...
Setting up libqt5multimediawidgets5:amd64 (5.9.5-0ubuntu1) ...
Setting up libgstreamer1.0-0:amd64 (1.14.5-0ubuntu1~18.04.1) ...
Setcap worked! gst-ptp-helper is not suid!
Setting up libqt5designercomponents5:amd64 (5.9.5-0ubuntu1) ...
Setting up wpasupplicant (2:2.6-15ubuntu2.8) ...
Created symlink /etc/systemd/system/dbus-fi.w1.wpa_supplicant1.service → /lib/systemd/system/wpa_supplicant.service.
Created symlink /etc/systemd/system/multi-user.target.wants/wpa_supplicant.service → /lib/systemd/system/wpa_supplicant.service.
Setting up libqmi-glib5:amd64 (1.22.0-1.2~ubuntu18.04.1) ...
Setting up libqmi-proxy (1.22.0-1.2~ubuntu18.04.1) ...
Setting up qtdeclarative5-dev:amd64 (5.9.5-0ubuntu1.1) ...
Setting up libisccfg160:amd64 (1:9.11.3+dfsg-1ubuntu1.14) ...
Setting up libgstreamer-plugins-base1.0-0:amd64 (1.14.5-0ubuntu1~18.04.1) ...
Setting up gstreamer1.0-plugins-base:amd64 (1.14.5-0ubuntu1~18.04.1) ...
Setting up libqgsttools-p1:amd64 (5.9.5-0ubuntu1) ...
Setting up libqt5webkit5:amd64 (5.212.0~alpha2-7ubuntu1) ...
Setting up modemmanager (1.10.0-1~ubuntu18.04.2) ...
Created symlink /etc/systemd/system/dbus-org.freedesktop.ModemManager1.service → /lib/systemd/system/ModemManager.service.
Created symlink /etc/systemd/system/multi-user.target.wants/ModemManager.service → /lib/systemd/system/ModemManager.service.
Setting up libbind9-160:amd64 (1:9.11.3+dfsg-1ubuntu1.14) ...
Setting up qtmultimedia5-dev:amd64 (5.9.5-0ubuntu1) ...
Setting up qt5-assistant (5.9.5-0ubuntu1) ...
Setting up bind9-host (1:9.11.3+dfsg-1ubuntu1.14) ...
Setting up avahi-daemon (0.7-3.1ubuntu1.2) ...
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of force-reload.
Created symlink /etc/systemd/system/dbus-org.freedesktop.Avahi.service → /lib/systemd/system/avahi-daemon.service.
Created symlink /etc/systemd/system/multi-user.target.wants/avahi-daemon.service → /lib/systemd/system/avahi-daemon.service.
Created symlink /etc/systemd/system/sockets.target.wants/avahi-daemon.socket → /lib/systemd/system/avahi-daemon.socket.
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of start.
Setting up qttools5-dev-tools (5.9.5-0ubuntu1) ...
Setting up libnss-mdns:amd64 (0.10-8ubuntu1) ...
First installation detected...
Checking NSS setup...
Setting up qttools5-dev:amd64 (5.9.5-0ubuntu1) ...
Setting up libgeoclue-2-0:amd64 (2.4.7-1ubuntu1) ...
Setting up geoclue-2.0 (2.4.7-1ubuntu1) ...
Processing triggers for libc-bin (2.27-3ubuntu1.2) ...
/sbin/ldconfig.real: /usr/local/lib/python3.7/dist-packages/ideep4py/lib/libmkldnn.so.0 is not a symbolic link

Processing triggers for systemd (237-3ubuntu10.45) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Processing triggers for dbus (1.12.2-1ubuntu1.2) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for mime-support (3.60ubuntu1) ...
+ sudo apt-get install -qq g++ cmake libssl-dev nodejs
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76, <> line 3.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
Selecting previously unselected package nodejs-doc.
(Reading database ... 162484 files and directories currently installed.)
Preparing to unpack .../nodejs-doc_8.10.0~dfsg-2ubuntu0.4_all.deb ...
Unpacking nodejs-doc (8.10.0~dfsg-2ubuntu0.4) ...
Selecting previously unselected package libc-ares2:amd64.
Preparing to unpack .../libc-ares2_1.14.0-1_amd64.deb ...
Unpacking libc-ares2:amd64 (1.14.0-1) ...
Selecting previously unselected package nodejs.
Preparing to unpack .../nodejs_8.10.0~dfsg-2ubuntu0.4_amd64.deb ...
Unpacking nodejs (8.10.0~dfsg-2ubuntu0.4) ...
Setting up nodejs-doc (8.10.0~dfsg-2ubuntu0.4) ...
Setting up libc-ares2:amd64 (1.14.0-1) ...
Setting up nodejs (8.10.0~dfsg-2ubuntu0.4) ...
update-alternatives: using /usr/bin/nodejs to provide /usr/bin/js (js) in auto mode
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Processing triggers for libc-bin (2.27-3ubuntu1.2) ...
/sbin/ldconfig.real: /usr/local/lib/python3.7/dist-packages/ideep4py/lib/libmkldnn.so.0 is not a symbolic link

+ curl -sL https://deb.nodesource.com/setup_12.x
+ sudo -E bash -

## Installing the NodeSource Node.js 12.x repo...

## Populating apt-get cache...

+ apt-get update
Hit:1 https://cloud.r-project.org/bin/linux/ubuntu bionic-cran40/ InRelease
Hit:2 http://security.ubuntu.com/ubuntu bionic-security InRelease
Ign:3 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64  InRelease
Hit:4 http://ppa.launchpad.net/c2d4u.team/c2d4u4.0+/ubuntu bionic InRelease
Hit:5 http://archive.ubuntu.com/ubuntu bionic InRelease
Ign:6 https://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64  InRelease
Hit:7 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64  Release
Hit:8 https://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64  Release
Hit:9 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:10 http://ppa.launchpad.net/cran/libgit2/ubuntu bionic InRelease
Hit:11 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
Hit:12 http://ppa.launchpad.net/deadsnakes/ppa/ubuntu bionic InRelease
Hit:14 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic InRelease
Reading package lists... Done

## Confirming "bionic" is supported...

+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_12.x/dists/bionic/Release'

## Adding the NodeSource signing key to your keyring...

+ curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | gpg --dearmor | tee /usr/share/keyrings/nodesource.gpg >/dev/null

## Creating apt sources list file for the NodeSource Node.js 12.x repo...

+ echo 'deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_12.x bionic main' > /etc/apt/sources.list.d/nodesource.list
+ echo 'deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_12.x bionic main' >> /etc/apt/sources.list.d/nodesource.list

## Running `apt-get update` for you...

+ apt-get update
Hit:1 http://security.ubuntu.com/ubuntu bionic-security InRelease
Hit:2 https://cloud.r-project.org/bin/linux/ubuntu bionic-cran40/ InRelease
Get:3 https://deb.nodesource.com/node_12.x bionic InRelease [4,584 B]
Ign:4 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64  InRelease
Hit:5 http://ppa.launchpad.net/c2d4u.team/c2d4u4.0+/ubuntu bionic InRelease
Hit:6 http://archive.ubuntu.com/ubuntu bionic InRelease
Ign:7 https://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64  InRelease
Hit:8 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64  Release
Hit:9 https://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64  Release
Hit:10 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Get:11 https://deb.nodesource.com/node_12.x bionic/main amd64 Packages [766 B]
Hit:12 http://ppa.launchpad.net/cran/libgit2/ubuntu bionic InRelease
Hit:13 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
Hit:14 http://ppa.launchpad.net/deadsnakes/ppa/ubuntu bionic InRelease
Hit:16 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic InRelease
Fetched 5,350 B in 1s (4,618 B/s)
Reading package lists... Done

## Run `sudo apt-get install -y nodejs` to install Node.js 12.x and npm
## You may also need development tools to build native addons:
     sudo apt-get install gcc g++ make
## To install the Yarn package manager, run:
     curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | gpg --dearmor | sudo tee /usr/share/keyrings/yarnkey.gpg >/dev/null
     echo "deb [signed-by=/usr/share/keyrings/yarnkey.gpg] https://dl.yarnpkg.com/debian stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
     sudo apt-get update && sudo apt-get install yarn

+ sudo apt-get install -y nodejs
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libc-ares2 nodejs-doc
Use 'sudo apt autoremove' to remove them.
The following packages will be upgraded:
  nodejs
1 upgraded, 0 newly installed, 0 to remove and 50 not upgraded.
Need to get 18.2 MB of archives.
After this operation, 75.1 MB of additional disk space will be used.
Get:1 https://deb.nodesource.com/node_12.x bionic/main amd64 nodejs amd64 12.22.1-1nodesource1 [18.2 MB]
Fetched 18.2 MB in 0s (63.3 MB/s)
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76, <> line 1.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
(Reading database ... 162613 files and directories currently installed.)
Preparing to unpack .../nodejs_12.22.1-1nodesource1_amd64.deb ...
Unpacking nodejs (12.22.1-1nodesource1) over (8.10.0~dfsg-2ubuntu0.4) ...
Setting up nodejs (12.22.1-1nodesource1) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
+ sudo npm install -g npm@latest
/usr/bin/npm -> /usr/lib/node_modules/npm/bin/npm-cli.js
/usr/bin/npx -> /usr/lib/node_modules/npm/bin/npx-cli.js
+<EMAIL_ADDRESS>added 58 packages from 23 contributors, removed 241 packages and updated 194 packages in 7.324s
+ installed=1
+ (( installed ))
+ break
+ (( no_pm ))
+ (( !installed ))
+ (( 0 ))
+ ./scripts/build.sh gui translations
/content/imgbrd-grabber/build /content/imgbrd-grabber
-- The C compiler identification is GNU 7.5.0
-- The CXX compiler identification is GNU 7.5.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring for version '7.5.1'
-- Configuring for platform 'x86' (x86_64)
-- Compiling with SSL support
-- Found OpenSSL: /usr/lib/x86_64-linux-gnu/libcrypto.so (found version "1.1.1")
-- OpenSSL version: 1.1.1
-- OpenSSL include dir: /usr/include
-- OpenSSL libraries: /usr/lib/x86_64-linux-gnu/libssl.so;/usr/lib/x86_64-linux-gnu/libcrypto.so
-- Configuring done
-- Generating done
-- Build files have been written to: /content/imgbrd-grabber/build
Scanning dependencies of target sites_modules
Scanning dependencies of target lib_autogen
[  1%] Installing npm packages...
[  1%] Automatic MOC and UIC for target lib
[  1%] Built target lib_autogen
Scanning dependencies of target lib
[  1%] Building CXX object lib/CMakeFiles/lib.dir/src/auth/auth-const-field.cpp.o
[  1%] Building CXX object lib/CMakeFiles/lib.dir/src/analytics.cpp.o
[  1%] Building CXX object lib/CMakeFiles/lib.dir/src/auth/auth-field.cpp.o
[  3%] Building CXX object lib/CMakeFiles/lib.dir/src/auth/auth-hash-field.cpp.o
[  3%] Building CXX object lib/CMakeFiles/lib.dir/src/auth/auth.cpp.o
[  3%] Building CXX object lib/CMakeFiles/lib.dir/src/auth/field-auth.cpp.o
[  3%] Building CXX object lib/CMakeFiles/lib.dir/src/auth/http-auth.cpp.o
[  4%] Building CXX object lib/CMakeFiles/lib.dir/src/auth/http-basic-auth.cpp.o
[  4%] Building CXX object lib/CMakeFiles/lib.dir/src/auth/oauth2-auth.cpp.o
[  4%] Building CXX object lib/CMakeFiles/lib.dir/src/auth/url-auth.cpp.o
[  4%] Building CXX object lib/CMakeFiles/lib.dir/src/cli/cli.cpp.o
[  6%] Building CXX object lib/CMakeFiles/lib.dir/src/cli/commands/cli-command.cpp.o
[  6%] Building CXX object lib/CMakeFiles/lib.dir/src/cli/commands/download-images-cli-command.cpp.o
[  6%] Building CXX object lib/CMakeFiles/lib.dir/src/cli/commands/get-details-cli-command.cpp.o
[  6%] Building CXX object lib/CMakeFiles/lib.dir/src/cli/commands/get-images-cli-command.cpp.o
[  8%] Building CXX object lib/CMakeFiles/lib.dir/src/cli/commands/get-page-count-cli-command.cpp.o
[  8%] Building CXX object lib/CMakeFiles/lib.dir/src/cli/commands/get-tags-cli-command.cpp.o
[  8%] Building CXX object lib/CMakeFiles/lib.dir/src/cli/commands/get-page-tags-cli-command.cpp.o
[  9%] Building CXX object lib/CMakeFiles/lib.dir/src/cli/commands/load-tag-database-cli-command.cpp.o
[  9%] Building CXX object lib/CMakeFiles/lib.dir/src/cli/commands/search-cli-command.cpp.o
[  9%] Building CXX object lib/CMakeFiles/lib.dir/src/cli/commands/search-images-cli-command.cpp.o
[  9%] Building CXX object lib/CMakeFiles/lib.dir/src/commands/commands.cpp.o
[ 11%] Building CXX object lib/CMakeFiles/lib.dir/src/commands/sql-worker.cpp.o
[ 11%] Building CXX object lib/CMakeFiles/lib.dir/src/concurrent-multi-queue.cpp.o

added 535 packages, and audited 536 packages in 28s

1 high severity vulnerability

To address all issues, run:
  npm audit fix

Run `npm audit` for details.
[ 11%] Built target sites_modules
[ 11%] Building CXX object lib/CMakeFiles/lib.dir/src/custom-network-access-manager.cpp.o
/content/imgbrd-grabber/src/lib/src/concurrent-multi-queue.cpp: In member function ‘void ConcurrentMultiQueue::append(int, QVariant)’:
/content/imgbrd-grabber/src/lib/src/concurrent-multi-queue.cpp:29:22: error: ‘class QAtomicInt’ has no member named ‘loadRelaxed’
  if (m_activeWorkers.loadRelaxed() < m_globalConcurrency) {
                      ^~~~~~~~~~~
[ 11%] Building CXX object lib/CMakeFiles/lib.dir/src/danbooru-downloader-importer.cpp.o
lib/CMakeFiles/lib.dir/build.make:361: recipe for target 'lib/CMakeFiles/lib.dir/src/concurrent-multi-queue.cpp.o' failed
make[3]: *** [lib/CMakeFiles/lib.dir/src/concurrent-multi-queue.cpp.o] Error 1
make[3]: *** Waiting for unfinished jobs....
Scanning dependencies of target sites
[ 11%] Transpiling TypeScript sources into JavaScript...

> build
> tsc -p tsconfig.json

CMakeFiles/Makefile2:124: recipe for target 'lib/CMakeFiles/lib.dir/all' failed
make[2]: *** [lib/CMakeFiles/lib.dir/all] Error 2
make[2]: *** Waiting for unfinished jobs....
[ 11%] Built target sites
CMakeFiles/Makefile2:226: recipe for target 'gui/CMakeFiles/gui.dir/rule' failed
make[1]: *** [gui/CMakeFiles/gui.dir/rule] Error 2
Makefile:214: recipe for target 'gui' failed
make: *** [gui] Error 2
/content/imgbrd-grabber
+ exit 21

You can test everything there.

Tested it on my local machine (OS: Debian 10 buster). Build fails with same errors.

I got it. According to QT documentation loadRelaxed() function was introduced in Qt 5.14, but default version installed through apt is 5.9.5.

As you guessed, your Qt packages are likely too old. I recommend using the beineri repository for Qt packages on Linux (here for bionic):
sudo add-apt-repository ppa:beineri/opt-qt-5.15.2-bionic
sudo apt-get update
sudo apt install qt515base qt515multimedia qt515script qt515tools qt515translations
source /opt/qt515/bin/qt515-env.sh

I'll update the documentation to add this information.

Thanks for your answer and sorry for late response. I managed to build grabber using QT 5.15.


No icon for device

The problem
Does not show icon next to devices
Your Environment
Home Assistant
Thank

+1

The beta version has not yet uploaded the smartlife icon.


Error "Program Execution Failure - No user tests were run."

Challenge http://www.freecodecamp.com/challenges/waypoint-use-bracket-notation-to-find-the-last-character-in-a-string has an issue. Please describe how to reproduce it, and include links to screenshots if possible.
Got this error "Program Execution Failure - No user tests were run."

Hey thanks for posting this issue!
I'm having trouble replicating it. Can you do a hard refresh of your browser (CMD + R in Mac, CTRL + F5 in Windows)
Your code looks right though, so great job with that!

Scratch that, I see a bug.  Remember that the case of your letters matter in variables.  Check out line 7 and look very closely for the error.

Ahh, I got it, and passed. Thanks for your help!


Add Open3D PyTorch Dockerfile for 3D Deep Learning  - NVIDIA AMD64

Add a new dockerfile for easy training of the DL models with Open3D and PyTorch with nvidia gpu drivers and cuda

Added with the PR #12 .


If you slash at blue bullets in the past, you destroy them

Most apparent in boss fight.


Update README.md

Added Table metrices that will be updated automatically.
fixes: #205

Thankyou for Contributing!

Thankyou for Contributing!

Kindly add the gssoc labels too and level 🙏


Porting of Provider Network Model

Environment

Python version: v3.7
Nautobot version: v1.0.3

Proposed Functionality
Implementation of Provider Networks as a Model to connect multiple circuits to as done in NetBox: https://github.com/netbox-community/netbox/issues/5986

Use Case
Documentation of e.G. Transit Connections, Peering LANs, MPLS Networks with P2MP Connections, etc.

Database Changes

Adding a new table.
extending circuit termination

External Dependencies
None

Shall i submit a PR for implementation of this?

Thanks for offering! If you're willing to do so, it would be quite welcome. :-)

We could also enrich a bit more the original Netbox Model, for instance adding a reference to IPAM Prefixes (optional) could help to model some Provider Networks.

@ChrisDeh have you started with this effort? Definitely, this is something we want to add to Nautobot, so we would like to push it forward.
@glennmatthews , taking as reference the current implementation in Netbox for ProviderNetwork, I would like to ask you if it would make sense to you if we add an extra ManyToMany relationship with ipam.Prefix?
Any other suggestion/consideration before starting?

@chadell I sadly not managed to find any time for starting with this. I've planned to go ahead with this in the second half of december.

I am a colleague of @ChrisDeh and will take care of this 👌🏻

Merged into next.


StickyHeader layout problem by scrolling up and down (SAPUI5 1.84.21)

OpenUI5 version:  1.84.21
Browser/version (+device/version): Windows 10
Any other tested browsers/devices(OK/FAIL):
URL (minimal example if possible):
User/password (if required and possible - do not post any confidential information here):
Steps to reproduce the problem:
Build a Windows Client which is empty and only consists of index.html. (or simplicity does not matter)

Install and start the Windows-App.

Windows Cordova App:
cordovaVersion 9.0.0
kapselSDKVersion <IP_ADDRESS>

Click "F12" and choose the debug target

Open the console, type this and click enter:

window.open ("https://sapui5.hana.ondemand.com/");

Set the version to 1.84.21.

Go to "Samples" and open "Column List Item"

Activate all "Sticky Headers" in the "Table - Columns" example.

Scroll up and down, see how the header jump.

Edge Info: Emulator must be set to "Microsoft Edge (Standard)" for this.

What is the expected result?
Header should stay sticked and fixed while scrolling up and down.
What happens instead?
Header jumps like crazy or disappears.
Any other information? (attach screenshot if possible)

Hey @durukan-iscan , is this bug on the latest version too? Also have you tried other framework to build your desktop app such as Electron or NW.js (i know this is unrelated but i want to help if i can).

Hello @durukan-iscan ,
Thank you for sharing this finding. I've created an internal incident<PHONE_NUMBER>. The status of the issue will be updated here in GitHub.
Regards,
Florian

Hi @durukan-iscan ,
I managed to created a Window client app as guided in the problem description using Visual Studio 2017. (Note: As far as i learnt, higher version of Visual Studio does not support Cordova.)
When i check the sap.ui.Device.browser in the console. The browser was detected as Microsoft Edge browser (version 18.19042).
The sticky feature of the sap.m.Table control is implemented with standard CSS (position: sticky). The mentioned Edge browser has some limitation with the flicking of sticky elements when scrolling. This issue is also observed without UI5 (with plain HTML and CSS). For your reference I have attached a video recording.
Since Edge 18 is no longer supported by Microsoft we cannot provide any solution since this misbehavior is caused by the browser. Perhaps newer versions provide a Chromium Edge client with may resolve this behavior, but I apologize since I do not have much knowledge about the Windows App development.
There are also some similar complaints about position: sticky flickering for MS Edge if you also search for it. One of it is listed below:
https://pretagteam.com/question/position-sticky-flickers-during-scroll-in-microsoft-edge-but-not-in-other-browsers.
Hope the above information helps.
https://user-images.githubusercontent.com/7147878/147709265-d2433145-54db-4692-b1e6-20b893c583a8.mp4
Thanking you.
Best regards,
Jay Barbhaiya


feat(jsii): configure diagnostics in package.json

Diagnostic codes and categories already exist in JSII. This change adds
configurability via package.json.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 4521e3504a385d41a6c0d037fedac9c1a0140479
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: fe4f3eb77ffe9f4a6874c6baa912d926524d0615
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 506d0d697004322c80612dcb8df4060053ddc6b5
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID:<PHONE_NUMBER>a0dfcae947c891af4f998a68dfd775
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: e98acda2c354a551fae15831b856ad78a532c568
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: f98c428eac9a6ead8fdd968c23250a15fce13a81
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@mergifyio refresh


AZ CLI 2.0

Again, classic cli should be replaced with cli 2.0
https://docs.microsoft.com/en-us/cli/azure/hdinsight?view=azure-cli-latest
Instead:
azure hdinsight cluster list
azure hdinsight cluster show <ClusterName>
Could be used
https://docs.microsoft.com/en-us/cli/azure/hdinsight?view=azure-cli-latest#az-hdinsight-show
https://docs.microsoft.com/en-us/cli/azure/hdinsight?view=azure-cli-latest#az-hdinsight-list

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

ID: d780dc73-c74d-a65e-16d9-4244a834a82e
Version Independent ID: 4cdbff46-8377-a51f-0829-f90b91ce7d25
Content: Troubleshoot a slow or failing HDInsight cluster - Azure HDInsight
Content Source: articles/hdinsight/hdinsight-troubleshoot-failed-cluster.md
Service: hdinsight
GitHub Login: @ashishthaps
Microsoft Alias: ashishth

@SychevIgor Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate. @ashishthaps

Thanks @SychevIgor. We have some scheduled work to re-evaluate all of our command line customer scenarios and will be sure that we include az cli 2.0 where appropriate. Given the scope of the update it may take some time, but we are away of the issue. Thanks!

#please-close


[FIX] sap.tnt.SideNavigation: Fix Typo in Sample

'Exapand' should be 'Expand'.

Thanks timo for this fix! I will start the merging process. Will get back to you in a minute :-)

Thanks! The pull request has been merged into the openui5 repository. The change will be in the following UI5 version(s): 1.38


Addresses already created tags

Description
Tags are already present when the release workflow is invoked. This PR addresses it.

Will do a fast merge, since this has zero impact on vital parts / is non-breaking.


For now we only support PHP on 64bit platform

For now we only support PHP on 64bit platform
What should I do?

Install 64-bit version of PHP.

PHP7?
I tryed with XAMPP or EasyPHP, but does not work.
I'm trying with PHP7 from here http://windows.php.net/download/

I cannot execute it, can you help me?

install Wamp 64 bit, it includes php 5.6 and php 7.0
With php 7.0 it works perfectly

Already did! It works!


Provide Definition or Context for "Trusted Orgs"

This article could use some additional context or a link to a related doc as to what "trusted orgs" are and how those can be defined within the meeting host organization.

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

 I'll add a link to this article.

Link was added in https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/commit/5633329d98112da47665b9818fe5623b16caa70c
Thanks @MikePlumleyMSFT


Add queries and query building

Query building reference
Query documentation

@schen22 I don't want us to build a query builder in the sdk. Let's try to keep the models as simple as possible.

@germanattanasio - Sure, that makes probably makes more sense. We could instead just reference the documentation and have users input their query as a string. How does that sound to you?

There needs to be a middle point. We don't want users to write a lot of
code but we don't also want to maintain a lot of custom code.
Can you come up with a class diagram? We can start from there.
On Mon, Dec 12, 2016 at 1:02 PM Sarah Chen<EMAIL_ADDRESS>wrote:

@germanattanasio https://github.com/germanattanasio - Sure, that makes
probably makes more sense. We could instead just reference the
documentation and have users input their query as a string. How does that
sound to you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/watson-developer-cloud/ios-sdk/issues/551#issuecomment-266503806,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AATHRRQv8zyjaroVdXGOVEk-y2boKnLyks5rHYwrgaJpZM4LKMpN
.

Here's a drafted class diagram for a query builder: https://drive.google.com/file/d/0B6_IZDgE6LbhZWpxbVhIRlBBQm8/view?usp=sharing
Across the board, Query, Filter and Aggregation models allow a user to enter an entire query expression. I was thinking of adding error handling methods, but this would take probably the same amount of time to define all the query parameters the Discovery service allows.
To look into the possibility of defining all the query parameters I specify the current methods and properties that the Discovery service currently allows the user to query for. However, this would require more maintenance in the future, as you mentioned.
A few questions that came up while I was mapping out the diagram:

What's a good middle point to take between allowing users to input an entire query string (and implementing error handling/catching), or providing functions that allow for type safety but would require more maintenance in the future?
How detailed have other SDKs been in defining a QueryResponse and the Query method?

As for the other sdks:  they don't define the query response too tightly.  The response is a json object.  If you do aggregations,  you'll get those back in the response too, and that can be pretty hairy.   The query params are also dependent on the FQNs of the data ingested.

Python and node don't need to parse the response like Swift or Java. It's a different world.
I think you went too deep with the request builder. The response needs to be parsed so I agree with that part of the diagram. I guess that matches 1-1 the JSON.
The way we build the query should be more high level. Just use the parameters you see in Swagger and make sure they are strings.
PLEASE, write code like if you were the user and see if you like what you see before start implementing this.
Let's actually move the conversation to be around the code devs will write. Can you write the Swift code that our devs will write to do a simple query with 1 aggregation?

I think if we could start with a playground and define some of this stuff it might be easier/better/kinder than using a class diagram?  Especially since swift isn't especially OOP.
@germanattanasio swift can deal with JSON more cleanly than Java.
@schen22 I would argue an interface similar to NSPredicate would be preferable to the method style.  For example,  Aggregations could be expressed and combined in a similar fashion.  For example (see that attached playground).
DIscoveryQuery.playground.zip

@kognate - Looks good to me! Along similar lines, what do you think about implementing the protocol DiscoveryPredicateQueryString to have a public struct filterAggregation and similar structs for the rest of the aggregate methods?
DIscoveryQuery.playground 2.zip

my concern with filterAggregation is that it might be complicated to express something like this:
nested(entities).filter(entities.type:Person).term(entities.text.raw)
Filters also apply to results as well as aggregations.
DIscoveryQuery 3.zip

In the java sdk we just expect strings. Again, I think we should keep it
simple.
On Tue, Dec 13, 2016 at 5:13 PM Joshua Smith<EMAIL_ADDRESS>wrote:

my concern with filterAggregation is that it might be complicated to
express something like this:
nested(entities).filter(entities.type:Person).term(entities.text.raw)
Filters also apply to results as well as aggregations.
DIscoveryQuery 3.zip
https://github.com/watson-developer-cloud/ios-sdk/files/650331/DIscoveryQuery.3.zip
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/watson-developer-cloud/ios-sdk/issues/551#issuecomment-266878832,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AATHRS3Hb7A8V74wZsXbk04-byca7db2ks5rHxiZgaJpZM4LKMpN
.


Add a small GA job to run the unit tests

Eventually add fuzzing targets too, once we have them.
Pretty much like for cosignerd.

Actually, fuzz tests are not running in CI at the moment, so I'll open again until we merge #27

#27 didn't add fuzzing to the CI?

Mhhh right

I forgot to push :sob: Opening a new PR now, sorry


vlc: Add chromecast support; libmicrodns: Init at 0.0.10

Motivation for this change
VLC normally ships with Chromecast support enabled by default, in the official binaries as well as in other distros (arch, ubuntu, possibly others).
Chromecast support for VLC has been requested on several occasions (https://github.com/NixOS/nixpkgs/pull/35124#issuecomment-385791097, #58365 from me, and a bunch of times on IRC).
This PR adds libmicrodns which is a library written by the VLC team that is required for their Chromecast streaming to function.
It also adds Chromecast support to the VLC build enabled by default, but can be overridden.
Fixes #58365.
This is my first nixpkgs contribution, please be gentle. :blush:
Some notes/questions:

I'm not sure if this is a strict requirement, but enabling hardware acceleration is important for transcoding especially: https://nixos.wiki/wiki/Accelerated_Video_Playback - I needed to add intel-media-driver  to get libva info: va_openDriver() returns -1 errors to stop. Not sure what's a more generalized solution. Is there a good place to document this? (Otherwise VLC spits out a bunch of errors, might fall back or not)
Port 8010 must be open (streaming works by creating a temporary HTTP server on port 8010 which streams the transcoded video, then points the Chromecast to open that local URL). Any suggestions for documenting/enforcing this?

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Also related: https://github.com/NixOS/nixpkgs/pull/53184

@Infinisil Good call, this PR should obsolete #35184, and it also makes scanning/autodetecting work properly (needed libmicrodns).

Port 8010 must be open (streaming works by creating a temporary HTTP server on port 8010 which streams the transcoded video, then points the Chromecast to open that local URL). Any suggestions for documenting/enforcing this?

I'd drop a short comment somewhere in the vlc derivation, and add a longer <para> inside nixos/doc/manual/release-notes/rl-1909.xml, "Other Notable Changes", noting VLC gained Chromecast support, suggesting to set networking.firewall.allowedTCPPorts = [8010].
Does VLC document that port somehwere obvious inside their documentation?

@shazow you might want to add protoc to both buildInputs and nativeBuildInputs, see https://github.com/NixOS/nixpkgs/pull/53184#discussion_r244846577.

Pushed squashed changes.
What's the easiest way to verify that the release notes are rendered properly?

@shazow from your checkout:
⇒  nix-build nixos/release.nix -A manual.x86_64-linux
⇒  cd result
⇒  python3 -m http.server

Access http://localhost:8000/share/doc/nixos/release-notes.html#sec-release-19.09-notable-changes in your browser

@flokli Ah thank you!
Alright, pushed some more minor edits, should be good for another look:

@grahamcofborg build vlc


Refactor: Move Function or Class

I would like to be able to easily move a function or class from one file to another. When moving the class, all the imports in my project should be properly updated with the new location. If other functions or classes depend on the object being moved, I should be prompted to include them in the move.
Before Move
File1.py
def func1():
  pass

def func2(): # We will select this function to move to File2.py
  func1()

def func3():
  func2()

When selecting to Refactor: Move funct2, to File2.py, it should be noted that func1() must also be moved, to prevent creating a circular dependency.
After Move
File1.py
from File2 import func2  # This line was inserted for me after func2() was moved

def func3():
  func2()

File2.py
def func1():  # Dependent functions where also moved
  pass

def func2():  # This function was selected for refactoring
  func1()

dup of https://github.com/microsoft/pylance-release/discussions/2617


will you be ready for V3?

Nope!

@arjes You mentioned in the linked issue that life's kicking your butt, so I'll take a look at this later to try to bring it up to speed. I'm interested in getting the bare bones working (right now it says a response code of 200 is an error :joy: ) and might not worry about getting everything running, but I'll try my best. If there are any pointers you have about things you know are definitely broken I'm all ears.

@arjes You mentioned in the linked issue that life's kicking your butt, so I'll take a look at this later to try to bring it up to speed. I'm interested in getting the bare bones working (right now it says a response code of 200 is an error :joy: ) and might not worry about getting everything running, but I'll try my best. If there are any pointers you have about things you know are definitely broken I'm all ears.

@ArchdukeTim No problem, thank for stepping up.  There is also the issue that this was my first foray into NativeScript :D I have good experience with NG and TS in general, but there is lots of new stuff.
I have not reviewed the 3.0 api, but I expect it is quite different to some fundamental model changes.

@ArchdukeTim No problem, thank for stepping up.  There is also the issue that this was my first foray into NativeScript :D I have good experience with NG and TS in general, but there is lots of new stuff.
I have not reviewed the 3.0 api, but I expect it is quite different to some fundamental model changes.

@ArchdukeTim I've gone ahead and started the start_v3_upgrade branch which allows the code to branch between a v3 and a v2 adapter. As of right now I have not checked any functionality besides the first-time-startup

@ArchdukeTim I've gone ahead and started the start_v3_upgrade branch which allows the code to branch between a v3 and a v2 adapter. As of right now I have not checked any functionality besides the first-time-startup

A working PantryParty should be on all app stores. I'll make a post in /r/grocy tomorrow.


No Request with long Authentication

I have to test a Basic Auth protected system.
Both username and password contain 38 characters. If I enter my authentication data and press "submit" nothing happens. If I remove some characters, the request starts as aspected.
Is there a maximum lenght for username + password? If it is, could you increase it?

This is real as of today. I enter a long login name like "ck_5019ea4aba3865bfe6bc473503360359" and no request gets sent. Just deleting some X number of characters makes the request go.

Hi All, I have the same issue. The problem probably occurs because the wrong base64 encoding is used. It seems that the encoded string is split up at 76 characters (which is common for base64 encoding). But the HTTP RFC tells us that this should not be done for Basic authentication:
http://tools.ietf.org/html/rfc1945#section-11.1
As a workaround you can copy the encoded credentials and enter a custom request header with name "Authorization" and as value "Basic [encoded credentials]". Don't forget to remove the whitespace characters from the encoded credentials :)


More lenient thor versioning

While adding coveralls gem to my project, I encountered issues with the thor dependency versioning. I have a few gems that need thor >= 0.20, but coveralls is locked to < 0.20.
There are no breaking changes in thor version 0.20: https://github.com/erikhuda/thor/blob/master/CHANGELOG.md#0200
This PR "unlocks" coverall version of thor.
One side effect is that this allows version 0.19.0 to be installed, but it doesn't seem like coveralls has a strict requirement on 0.19.4, as the PR that bumped it to 0.19.4 doesn't seem to have any functionality impact: https://github.com/lemurheavy/coveralls-ruby/commit/bcf1f6fa2fc8301d51e71bf9dd858c6a65932353

On a side note, the same can be said for 'simplecov', '~> 0.16.1', as it locks it to < 0.17.

Came here to propose this PR only to find my friend co-worker already did it :) Any chance you can take a look at it please?

Hi @marcotc and @cabello I've merged another PR that includes this and released a new gem version.
Thank you!


Cloud profile version classification dates

This is just a draft.

Todo:

[ ] reconcile of CloudProfile and NamespacedCloudProfile Requeue at next step


idk how to call this one

why does it shows that there are 100k shares sent (my pov) (btw i had 10.2 millions shares with the old version) but when iu check the tiktok its stuck at 10.2 millions, can anyone help please ?

Not every share it counts is actually a hit. The number of "shares" it shows in the console, is just how many requests the script sent, not how many actually worked.

Yeah because of rate limits and bad API

ohhhh


Add method of handling many effects at the same time

The streamer can choose between queueing or applying them directly.

Resolved using cooldowns per effect.