Support MQ - MQTT

Support MQ - MQTT #23

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 53.22581% with 116 lines in your changes missing coverage. Please review.

Project coverage is 49.90%. Comparing base (369f97f) to head (5321bdc).
Report is 243 commits behind head on main.

Files with missing lines
Patch %
Lines

.../io/arex/inst/mqtt/adapter/MessageAdapterImpl.java
52.50%
29 Missing and 9 partials :warning:

...main/java/io/arex/inst/mqtt/MQTTAdapterHelper.java
18.91%
29 Missing and 1 partial :warning:

.../java/io/arex/inst/mqtt/MessageQueueExtractor.java
51.35%
17 Missing and 1 partial :warning:

...httpservlet/convert/HttpMessageConvertFactory.java
40.00%
6 Missing and 3 partials :warning:

...ava/io/arex/inst/mqtt/warp/GenericMessageWarp.java
78.94%
1 Missing and 3 partials :warning:

...java/io/arex/inst/mqtt/warp/MessageHeaderWarp.java
76.47%
1 Missing and 3 partials :warning:

...rex/inst/mqtt/inst/MQGenericInstrumentationV3.java
82.35%
2 Missing and 1 partial :warning:

...let/convert/impl/ApplicationJsonBodyConverter.java
66.66%
0 Missing and 3 partials :warning:

...vlet/convert/impl/DefaultHttpMessageConverter.java
40.00%
3 Missing :warning:

...vlet/convert/impl/ApplicationXmlBodyConverter.java
71.42%
0 Missing and 2 partials :warning:

... and 2 more

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##               main     #174      +/-   ##
============================================
+ Coverage     49.80%   49.90%   +0.09%
- Complexity     1352     1418      +66
============================================
  Files           222      233      +11
  Lines          8435     8683     +248
  Branches        984     1028      +44
============================================
+ Hits           4201     4333     +132
- Misses         3833     3923      +90
- Partials        401      427      +26

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Stack Trace in Usage Docs

Wanted to check out this project, went to the Usage section of the docs, which greets me with this:

I assume some bug in autogenerated docs caused this, I'm on mobile so can't dig into it.

Duplicate of #393


getting clothes back

got my clothes stolen from the laundry room, working on getting them back.

My bad I took them

Great work!

What kind of nerd get his clothes stolen smh my head

Thank you atasevac, very cool 👍


Several extensions are not listed in composer requirements

When installing phpDocumentor2 using Composer, everything seems to be fine until trying to run it.
My PHP build is stripped-back (built with --disable-all and only specific extensions enabled to reduce build size), and does not have several extensions that phpDocumentor expects to be present but does not declare in composer.json.
According to a PhpStorm scan of the project on the develop branch, the missing dependencies are:

ext-dom
ext-simplexml
ext-libxml
ext-xsl
ext-zlib

There may be other dependencies on other branches that I have not checked.
Expected Behavior
Installing phpDocumentor2 with my PHP setup should fail because ext-dom, ext-simplexml and ext-libxml are not found in my PHP build
Actual Behavior
phpDocumentor2 installs successfully and crashes when trying to run.
Steps to Reproduce the Problem

Compile PHP with any of the listed XML extensions missing (simplexml is the first problem I encountered)
Install phpDocumentor in a project
Try to generate documentation and watch it crash.

Your environment

Version used: 2.9
Install method: composer install phpdocumentor/phpdocumentor
php version: 7.2.13
Operating system and version (e.g. Ubuntu 16.04, Windows 7): Windows 10

While reviewing this issue and the composer.json of v3 I noticed some of your suggestions were missing. I have resolved this for v3, because of limited resources we are not able to backport many of these improvements to v2.x. Because of this limitation, I am going to close this item as the issue is resolved in v3.
If you have more suggestions like these we would love to hear more!


how to run script with vscode?

First i type  npm install -g yo in TERMINAL,It's succeed.
Then i use yo minecraft-addon and create file is succeesful.Below is feedback:
? What will be the name of your addon? cdBedRock ? What will your addon do or provide? This is a test ? What namespace will you use? cdbedrock ? What kind of modules will make up the addon? Behaviors, Resources ? Will you be adding scripts? Yes ? What language do you want to script in? JavaScript    create package.json    create gulpfile.js    create packs\resources\manifest.json    create packs\resources\pack_icon.png    create packs\behaviors\manifest.json    create packs\behaviors\pack_icon.png    create packs\behaviors\scripts\client\client.js    create packs\behaviors\scripts\server\server.js I'm all done. Running npm install for you to install the required dependencies. If this fails, try running the command yourself.
Last,the question is when i use C:\Users\pc\Desktop\testadd\cdBedRock> npm run installmod
it's error feedback:
`npm ERR! missing script: installmod
npm ERR!
npm ERR! Did you mean this?
npm ERR!     installaddon
npm ERR!      E:\nodejs\node_cache_logs\2019-03-20T21_13_19_165Z-debug.log`
I search the log but i can't find how to solve it,could you give me some clue?Thanks very much!

try npm run installaddon
early versions of the generator (or more specifically minecraft-addon-toolchain) used the term installmod but addon is more technically correct.

try npm run installaddon
early versions of the generator (or more specifically minecraft-addon-toolchain) used the term installmod but addon is more technically correct.

Thanks,its usefull.


add Z values to crossings / pscis_not_matched_to_streams

crossings:

modelled crossings already have Z values
easy to derive Z values from FWA for everything else on a stream when loading crossings table

pscis_not_matched_to_streams:

overlay with DEM to get elevation

to me, adding Z values to locations that we can't link to the network seems out of scope for this package


PoST: pass logger through to post-rs

Motivation
This integrates the new logging in post (https://github.com/spacemeshos/post/pull/137) into go-spacemesh.
Changes
The logger needs to be passed thorough to some components of post.
Do not merge before

[ ] https://github.com/spacemeshos/post-rs/pull/47
[ ] https://github.com/spacemeshos/post/pull/137
[x] https://github.com/spacemeshos/go-spacemesh/pull/4390

are merged and released
Test Plan
Existing tests pass.
TODO

[x] Explain motivation or link existing issue(s)
[x] Test changes and document test plan
[x] Update documentation as needed

DevOps Notes

[x] This PR does not require configuration changes (e.g., environment variables, GitHub secrets, VM resources)
[x] This PR does not affect public APIs
[x] This PR does not rely on a new version of external services (PoET, elasticsearch, etc.)
[x] This PR does not make changes to log messages (which monitoring infrastructure may rely on)

bors try

bors merge

bors merge

bors merge

bors merge

bors merge

Bors merge

bors merge


wal_craft: cleanup to keep editable

wal_craft had accumulated some trouble by using use anyhow::*;. Fixes that, removes redundant conversions (never need to convert a Path to OsStr), especially at the Process args.
Originally in #4100 but we merged a later PR instead for the fixes.

Visualization of why one should not do use anyhow::*;: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=9558c22a7cf8f34d4c7b31701de1ee69


Many golang links are outdated and don't use https.

Description
Some links to the golang site use http instead of https, and many of them also point to golang.org instead of go.dev.
Screenshots

Gitea Version
1.21
Can you reproduce the bug on the Gitea demo site?
Yes
Operating System
Linux
Browser Version
Firefox 122.0

Closed by #28980


GitHub actions for linting and testing

It'd be nice to automate the testing and linting, to make pull requests validated easier.
These things might be nice to include:

[ ] go fmt
[ ] goimports
[ ] go mod tidy
[ ] go mod verify
[ ] go vet
[ ] staticcheck - see https://staticcheck.io/
[ ] gosec - see https://github.com/securego/gosec
[ ] go test

Would it be preferable to have pre-commit as well?

Personally I'd say yes - but with Go there's (as far as I know) no predefined way of doing so, so I wouldn't really know.
But yes, it makes sense that most things the CI/CD would test (like linting) would be part of the pre-commit.

Good catch @ffrizzo !


Fix TestInformedWatcher sporadically failing on testgrid

See
https://prow.knative.dev/view/gcs/knative-prow/logs/ci-knative-pkg-continuous/1224064360993787904
https://prow.knative.dev/view/gcs/knative-prow/logs/ci-knative-pkg-continuous/1221890045716205568
https://prow.knative.dev/view/gcs/knative-prow/logs/ci-knative-pkg-continuous/1220078144313102336
for more info.

/assign @dprotaso

/assign @mattmoor

/approve

/lgtm


Add FluentBitIdleInputPlugins alert

How to categorize this PR?

/area logging
/kind enhancement
What this PR does / why we need it:
Recently we found that sometimes flued-bit pods stuck. They stops to prosses logs.
It is difficult to catch when this happens because the pods are still using CPU and Memory and looks like other working fluent-bit pods. The only difference is in the metric fluentbit_input_bytes_total which doesn't increase.
The new alert FluentBitIdleInputPlugins warn us when this is happening.
Which issue(s) this PR fixes:
This new alert will help debugging  #94
Special notes for your reviewer:
Release note:

New alert `FluentBitIdleInputPlugins` for idle fluent-bit pods.

Is there an upstream issue about it or are the fluent-bit maintainers aware of it?

I have no evidence whether the cause for he issue is in the fluent-bit itself or in our plugin.
I am making a new plugin release which is using pprof HTTP server to give us information about goroutines, mutexes and so on.


mixed architecture in opensuse tumbleweed images in versions starting from 3.0.9

Kairos version:
NAME="openSUSE Tumbleweed"
# VERSION="20240414"
ID="opensuse-tumbleweed"
ID_LIKE="opensuse suse"
VERSION_ID="20240414"
PRETTY_NAME="openSUSE Tumbleweed"
ANSI_COLOR="0;32"
# CPE 2.3 format, boo#1217921
CPE_NAME="cpe:2.3:o:opensuse:tumbleweed:20240414:*:*:*:*:*:*:*"
#CPE 2.2 format
#CPE_NAME="cpe:/o:opensuse:tumbleweed:20240414"
BUG_REPORT_URL="https://bugzilla.opensuse.org"
SUPPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org"
DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed"
LOGO="distributor-logo-Tumbleweed"
KAIROS_FAMILY="opensuse"
KAIROS_HOME_URL="https://github.com/kairos-io/kairos"
KAIROS_SOFTWARE_VERSION_PREFIX="k3s"
KAIROS_ID="kairos"
KAIROS_PRETTY_NAME="kairos-standard-opensuse-tumbleweed v3.0.6-v1.29.3-k3s1"
KAIROS_IMAGE_REPO="quay.io/kairos/opensuse:tumbleweed-standard-arm64-rpi4-v3.0.6-k3sv1.29.3-k3s1"
KAIROS_IMAGE_LABEL="tumbleweed-standard-arm64-rpi4-v3.0.6-k3sv1.29.3-k3s1"
KAIROS_TARGETARCH="arm64"
KAIROS_VERSION="v3.0.6-v1.29.3-k3s1"
KAIROS_ID_LIKE="kairos-standard-opensuse-tumbleweed"
KAIROS_VERSION_ID="v3.0.6-v1.29.3-k3s1"
KAIROS_FLAVOR_RELEASE="tumbleweed"
KAIROS_BUG_REPORT_URL="https://github.com/kairos-io/kairos/issues"
KAIROS_GITHUB_REPO="kairos-io/kairos"
KAIROS_NAME="kairos-standard-opensuse-tumbleweed"
KAIROS_FLAVOR="opensuse"
KAIROS_VARIANT="standard"
KAIROS_REGISTRY_AND_ORG="quay.io/kairos"
KAIROS_ARTIFACT="kairos-opensuse-tumbleweed-standard-arm64-rpi4-v3.0.6-k3sv1.29.3+k3s1"
KAIROS_MODEL="rpi4"
KAIROS_RELEASE="v3.0.6"
KAIROS_SOFTWARE_VERSION="v1.29.3+k3s1"

CPU architecture, OS, and Version:
Linux 72af8f086b52 6.9.4-arch1-1 #1 SMP PREEMPT_DYNAMIC Wed, 12 Jun 2024 20:17:17 +0000 aarch64 aarch64 aarch64 GNU/Linux
Describe the bug
Upgrade from opensuse-tumbleweed-standard-arm64-rpi4-v3.0.6-k3sv1.29.3-k3s1 to opensuse-tumbleweed-standard-arm64-rpi4-v3.0.9-k3sv1.29.3-k3s1 fails with
/usr/sbin/suc-upgrade: line 15: /usr/bin/kairos-agent: cannot execute binary file: Exec format error
To Reproduce

Have any arm64 opensuse-tumbleweed-standard deployment running with a version <= 3.0.6.
Upgrade to a version >= 3.0.9

Expected behavior
Upgrades to versions >= 3.0.9 are possible on opensuse-tumbleweed-standard
Logs
Log output of the apply job on the first node:
Defaulted container "upgrade" out of: upgrade, drain (init)
+ HOST_DIR=/host
+ '[' '' '!=' true ']'
+ diff /etc/os-release /host/etc/os-release
+ mount --rbind /host/dev /dev
+ mount --rbind /host/run /run
+ kairos-agent upgrade --source dir:/
/usr/sbin/suc-upgrade: line 15: /usr/bin/kairos-agent: cannot execute binary file: Exec format error`

Additional context

I first discovered this phenomenon while trying to upgrade my raspberry pi cluster from opensuse-tumbleweed-standard-arm64-rpi4-v3.0.6-k3sv1.29.3-k3s1 to opensuse-tumbleweed-standard-arm64-rpi4-v3.0.9-k3sv1.29.3-k3s1.
This resulted in the error of the system-upgrade job of the first node with the following error:
Defaulted container "upgrade" out of: upgrade, drain (init)
+ HOST_DIR=/host
+ '[' '' '!=' true ']'
+ diff /etc/os-release /host/etc/os-release
+ mount --rbind /host/dev /dev
+ mount --rbind /host/run /run
+ kairos-agent upgrade --source dir:/
/usr/sbin/suc-upgrade: line 15: /usr/bin/kairos-agent: cannot execute binary file: Exec format error`

Examining the images locally my development machine (amd64)
3.0.9:
Running the 3.0.9 arm64 image with docker run -it quay.io/kairos/opensuse:tumbleweed-standard-arm64-rpi4-v3.0.9-k3sv1.29.3-k3s1@sha256:ff1bf40d1ca19a074510214c9e8aede30efaf089182542a783018e1b3a9c70a8 "/bin/sh"
sh-5.2# file $(which kairos-agent)
/usr/bin/kairos-agent: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, no section header

sh-5.2# file /usr/bin/bash
/usr/bin/bash: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, BuildID[sha1]=5fe3979bcc55347779f7eeb79a2a2f5b17a18ba3, for GNU/Linux 3.7.0, stripped

3.0.6:
Running the 3.0.6 arm64 image with docker run -it quay.io/kairos/opensuse:tumbleweed-standard-arm64-rpi4-v3.0.6-k3sv1.29.3-k3s1@sha256:f725f6cf5a8fd07a141695a416ad918c923606a35cd9fd5fc74f340f14e1e75e "/bin/sh"
sh-5.2# file $(which kairos-agent)
/usr/bin/kairos-agent: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, no section header
sh-5.2# file /usr/bin/bash
/usr/bin/bash: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, BuildID[sha1]=5fe3979bcc55347779f7eeb79a2a2f5b17a18ba3, for GNU/Linux 3.7.0, stripped

This happened because of human error while backporting fixes on 3.0.X. The problem won't exist in 3.1.0 onwards (because CI handles this correctly). We should definitely avoid this happening when we backport but our focus is on getting 3.1.0 stable out. We won't cut a 3.0.X patch release just for this but will make sure it's fixed if we end up cutting a 3.0.X release anyhow.

Fix will be there in 3.1.0 (actually it works fine on 3.1.0-alpha already) : https://github.com/kairos-io/kairos/issues/1792
thus I'm closing this.

Thank you very much for the explanation.

I've added also a notification on all affected releases
@ElKiwos I think v3.0.4 should not have the issue in case you prefer not to consume the alpha release

@ElKiwos we have fixed this issue on v3.0.14

Thank you very much @mauromorales for backporting this
Quick question, I tried looking into this myself before creating the issue and I couldn't find the location where the amd64 binaries are being pulled in the build pipeline for the arm64 images. Still with the backported fix I can't pinpoint it. Could you please point me in the direction where to look?

@ElKiwos sure thing!
The main Kairos repo, has a Dockerfile that is common to all distros, there one of the sources is Kairos' framework image
https://github.com/kairos-io/kairos/blob/b174f3d5178057eceb4575e769ab9a1619d28451/images/Dockerfile.kairos#L2
Normally, this image, includes all the latest versions of the packages, which you can find on https://packages.kairos.io/
Normally, those images are multi-arch https://quay.io/repository/kairos/framework?tab=tags&tag=latest
However, for the backported fixes (most of the 3.0.x releases) we made the mistake to manually copy the backported packages e.g.
https://github.com/kairos-io/kairos-framework/blob/b769ae53a2cd843540b13b8d5a9a8ff26a31e25a/Dockerfile#L9
Which breaks arm because the arm packages live on a different repo https://quay.io/repository/kairos/packages-arm64
So for the latest release all I did is to add targets per targetarch
https://github.com/kairos-io/kairos-framework/blob/821d5f44efb5b09760bed3cd11bea0db09b7d872/Dockerfile#L10-L13
But long term, we should instead find a way to backport that plays well with the traditional way of using the multi-arch images.
I hope I did a good job explaining it, but please don't hesitate to ask any questions because this process is not trivial.


Migrate to the newer twitch API library

https://twurple.js.org/docs/migration/
Will be required as twitch has deprecated sending commands via IRC on 18/02/23.

Closed with 6e2a556


fix: dead code warning

That's weird: The lint apparently partially ignored the #[allow(dead_code)] annotation. :frowning_face: Let's see if I can come up with a different fix.


Fixes CPUParticles2D not making use of AtlasTextures

FYI, the email you used to sign this commit (see https://patch-diff.githubusercontent.com/raw/godotengine/godot/pull/32459.patch) is not affiliated to your GitHub account, which is why it appears as authored by "Bitstoppa" instead of your "@bitstopper" account.
It's not a problem for Git itself, but if you want your GitHub account to be credited as the author, you can amend the commit to change the email, or add this secondary email in your GitHub settings.

The code looks good, but the two commits should be squashed together.

Thanks!

Seems like I merged a bit too fast without waiting for testing/code review. @JFonS found several issues:
09:33 <jfons> Akien: I just tested this last CPUParticles PR and it has a couple issues. One is a crash that should be easy to fix, but the other breaks particle animation. Sorry for not testing before it was merged, I just noticed it now
09:35 <jfons> also, Particles2D don't take atlas textures into account so it's a bit weird to have it supported on one but not the other
09:37 <jfons> bottom line: this should be properly implemented but I can't do it right now :P

I'll revert it for now to fix the regressions and inconsistency.
You're welcome to re-do this PR, which we can review and further work on until it addresses the above issues. Then we can merge again :)

Note: In normal development times I wouldn't revert but wait for a fix PR instead, but now we're in the stabilization period for 3.2, and I plan to release 3.2 alpha 1 today or tomorrow, so I prefer to use the "revert and retry" approach.


Beta calculations

Let's say dt=1/365 and I want beta=0.12 on each day (this for RSV). What would I choose for v in pars['beta']=ss.beta(v)?
Math from time_prob, after inversion, suggests:
v = 1 - np.exp(365*np.log(1 - 0.12))

BUT this returns 1.0, and that's clearly not right. 365-fold compounding is a bear!
if v=0.99, the resulting daily probability is just 0.0125, an order of magnitude too small!

The short answer is that you should never use unit='year' and dt=1/365 -- use unit='day' and dt=1 instead! I don't know if we want to make this throw an exception, but maybe we should :laughing:
If you really want to do this (no!!!!), you can specify self_dt for timepars, e.g. ss.beta(0.12, unit='year', self_dt=1/365). But please don't do this!

8u
On Thu, 17 Oct 2024, 16:03 Cliff Kerr, @.***> wrote:

The short answer is that you should never use unit='year' and dt=1/365
-- use unit='day' and dt=1 instead! I don't know if we want to make this
throw an exception, but maybe we should 😆
If you really want to do this (no!!!!), you can specify self_dt for
timepars, e.g. ss.beta(0.12, unit='year', self_dt=1/365). But please
don't do this!
—
Reply to this email directly, view it on GitHub
https://github.com/starsimhub/starsim/issues/706#issuecomment-2419490502,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADACTVOD4BB6AC4GHE6DB4TZ36YSBAVCNFSM6AAAAABQDAHHR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJZGQ4TANJQGI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thanks @cliffckerr, let me try changing the unit - that's a great suggestion. I don't think we can appropriately raise an exception, but we might be able to raise a warning / suggestion if dt is very small.


[stable-4.4] ci: override GALAXY_NG_COMMIT to use a cached container that works

temporary fix pending a real one or the oci-env switch
(failing in https://github.com/ansible/ansible-hub-ui/pull/2926)

Oh never mind, the failure has resolved itself, no more build errors.


HW3 Submission

Classiq/QWorld assignment HW3 submission

Hello @NoahNzeki ! Please note that you include in the PR few files that you shouldn’t.
Can you please review it and submit only HW files in thew correct location in according to the submission instructions?
You might consider closing this PR and re submit from new and updated branch.


feat: export wallet

Export account feature for proposal:
https://near.social/devgovgigs.near/widget/gigs-board.pages.Post?id=670
https://github.com/NearSocial/VM/assets/14349805/19f81b60-b3b3-427d-bf96-38b2270c7b00

We've discussed this change in the chat. I think this is a custom feature that doesn't belong to the VM.
As I understand, the original intention was to be able to export key from the fastauth account to a different wallet. Since this change introduces custom API that would be available to widgets across all gateways, it's not necessary needed to be able to export keys from the components.
It can also be achieved by providing a generic API to ask users for any transaction, e.g. Near.transaction that takes a list of actions (e.g. in JSON), or multiple transactions. In a discussion, the issue was that it would be much easier to steal user's account if this option becomes available, so the prompt for the custom transaction signature need to be more verbose and protective. I still believe that it's the right approach, but it requires more design considerations.


Multiple Funnels on the same page

This may be a silly question, but how can you display multiple funnel graphs on the same php page.?

You just need multiple DOM containers for D3Funnel to render on. For example:

You then need to create an instance of D3Funnel for each render target:
const studentChart = new D3Funnel('#student-pipeline');
studentChart .draw(studentData, options);

const visitorsChart = new D3Funnel('#web-visitors');
visitorsChart.draw(visitorData, options);


Build error: /usr/bin/ld: skipping incompatible /usr/lib/libgcc_s.so when searching for -lgcc_s etc.

Hi
Target release: lumina-desktop 1.4.0
https://github.com/trueos/lumina/archive/v1.4.0.tar.gz
Compiling ends with error:
/usr/bin/ld: skipping incompatible /usr/lib/libgcc_s.so when searching for -lgcc_s
/usr/bin/ld: skipping incompatible /usr/lib/libgcc_s.so.1 when searching for libgcc_s.so.1
/usr/bin/ld: skipping incompatible /lib/libgcc_s.so.1 when searching for libgcc_s.so.1
/usr/bin/ld: skipping incompatible /usr/lib/libgcc_s.so when searching for -lgcc_s
/usr/bin/ld: skipping incompatible /usr/lib/libgcc_s.so.1 when searching for libgcc_s.so.1
/usr/bin/ld: skipping incompatible /lib/libgcc_s.so.1 when searching for libgcc_s.so.1
Environment:
OS: PCLinuxOS
qmake --version
QMake version 3.1
Using Qt version 5.9.2 in /usr/lib64
GCC:
rpm -qa ^gcc*
gcc-7.2.1-4pclos2017
gccmakedep-1.0.2-4pclos2017
gcc-c++-7.2.1-4pclos2017
gcc-cpp-7.2.1-4pclos2017
I've started with these qmake settings:
qmake \
QMAKE_CFLAGS_ISYSTEM= \
CONFIG+=configure \
PREFIX="/usr" \
LIBPREFIX="/usr/lib64" \
CONFIG+="WITH_I18N" \
QT5LIBDIR="/usr/lib64" \
L_LIBDIR="/usr/lib64"
LDCONFIG:
LC_MESSAGES=C ldconfig -v | grep libgcc
ldconfig: Can't stat /libx32: No such file or directory
ldconfig: Can't stat /usr/libx32: No such file or directory
	libgcc_s.so.1 -> libgcc_s-7.2.1.so.1
	libgcc_s.so.1 -> libgcc_s-7.2.1.so.1
ldconfig: Cannot stat /usr/lib64/libLLVM-3.7.1.so: No such file or directory
	libgcc_s.so.1 -> libgcc_s_32.so
Please give feedback if any rurther information are necessary.

It seems to me, that the libgcc is an 32-bit library, but you want to compile with 64-bit environment / options.

I've played around with "brutal" hack:
sed -i 's|LIBS += -L/usr/local/lib -L/usr/lib -L/lib|LIBS += -L/usr/lib64 -L=/lib64|g' src-qt5/OS-detect.pri
to avoid using 32bit libgcc_s, bu still with no luck. Build log from rpm says nothing ...
Here is the content of libgcc1 package:
rpm -ql libgcc1
/lib/libgcc_s-7.2.1.so.1
/lib/libgcc_s.so.1
/lib64/libgcc_s-7.2.1.so.1
/lib64/libgcc_s.so.1
/usr/lib64/libcc1.so.0
/usr/lib64/libcc1.so.0.0.0

but still with no luck. Build log from rpm says nothing ...

Problem is solved. I've reviewed and completed build requirements.


App crash

The app crash when opening image link from shared.
To avoid that I only can copy image link to "Load image from net" manually.
Another question
The force option in limits resize, it not only convert image, also zoom in image to fit limit. But this is different from my expectation (just force recode).
https://github.com/T8RIN/ImageToolbox/issues/322#issuecomment-1763425750

Is it persists in latest beta?

No crash, bat i got an error message "something went wrong", it is still working abnormally.

At least not a crash 🐸 I'll investigate

Fixed!


How to detect a connection loss?

Hi
I'm using SOCI to connect to a Postgresql database. If the connection is lost (for instance because the database is restarted), a subsequent query attempt causes a segmentation fault. How can I detect that the connection was lost in order to reconnect? I tried setting a failover_callback, overloading all four functions that this interface offers, but none of these functions ever gets called.

Hi again
It was my mistake: the failover_callback went out of scope and was deleted after it was set. Looking into the SOCI source code I realized that only a pointer to this object is stored. Now I make it static and everything works.

Glad to hear that this works for you, but it probably means that it's not necessary to keep this issue open, so closing.


chore(settings): Allow for comma-delimited RESERVED_NAMES

Allow for comma-delimited RESERVED_NAMES.
Hard-coded defaults for that env var are also eliminated from the controller itself.  Defaults will be added to the controller's container spec in the chart, thus cluster admins can modify if they choose.
Relates to https://github.com/deis/controller/issues/657

[Current coverage][cc-pull] is 82.46%

Merging [#662][cc-pull] into [master][cc-base-branch] will increase coverage by +0.15%

@@             master       #662   diff @@
==========================================
  Files            29         29
  Lines          2526       2526
  Methods           0          0
  Messages          0          0
  Branches        388        388
==========================================
+ Hits           2078       2083     +5
+ Misses          320        317     -3
+ Partials        128        126     -2

File ...fs/api/models/app.py (not in diff) was modified. more

Misses -3
Partials -2
Hits +5

[][cc-pull]

Powered by Codecov. Last updated by fcac716
[cc-base-branch]: https://codecov.io/gh/deis/controller/branch/master?src=pr
[cc-pull]: https://codecov.io/gh/deis/controller/pull/662?src=pr

can you please link here the relevant chart change for RESERVED_NAMES once you're done? Thanks!

@bacongobbler complementary chart changes are in https://github.com/deis/charts/pull/241


Fix matrix-static URLs for aliases with hashtags

Only the first hashtag was being replaced, which meant that anything after another hashtag wouldn't be sent to the server.

Looks sane to me
thanks for this


transitions: fix ItemAtDeskToItemOnLoan transition

Changes ItemAtDeskToItemOnLoan transition to inherits from Transition
Adds additional checks on patron_pid for item availability in case of
Item_At_Desk item

Co-Authored-by: Aly Badr<EMAIL_ADDRESS>Co-Authored-by: Olivier DOSSMANN<EMAIL_ADDRESS>

Have been merge here: https://github.com/inveniosoftware/invenio-circulation/pull/130


fix: conditionally add conversion stanza to CRDs in test

Fixes #N/A
Description
Webhook E2Es failed because they were expecting to be able to find references to v1 during smoke test cleanup and could not.
How was this change tested?
Make e2etest
Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[x] No

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

Pull Request Test Coverage Report for Build<PHONE_NUMBER>2
Details

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.01%) to 78.678%

Files with Coverage Reduction
New Missed Lines
%

pkg/providers/amifamily/ami.go
1
90.5%

Totals

Change from base Build<PHONE_NUMBER>6:
-0.01%

Covered Lines:
5893

Relevant Lines:
7490

💛  - Coveralls


Update sf-academy-events.md

@Yonet : Thanks for your contribution! The author(s) have been notified to review your proposed change. @danielescudero

Hi @Yonet, all PRs and GitHub issues should be filed in our private repo: https://github.com/MicrosoftDocs/mixed-reality-pr


fix documentation links broken by OMERO decoupling

Trying to get OMERO-DEV-merge-docs passing. See https://github.com/openmicroscopy/openmicroscopy/pull/5934 and https://trello.com/c/ZVrR6L3F/91-build-system-changes.

Given how much this PR touches I suggest that we merge it promptly and other OMERO 5.5.0 documentation fixes can follow separately.

@joshmoore: If you rearrange the MATLAB stuff happy to do a followup PR: that was by far one of the least painful aspects of this doc-fixing!


Show suggestions drop up instead of drop down

Is there any way suggestions can open up instead of drop down?

Instead of adding a prop for this we should show drop up /down depending on space available in viewport

is it fine to use floating-ui to solve this?


fix: Bump golang libs to resolve CVEs

If your build fails  due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[x] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I am not introducing a new dependency (add notes below if you are)
[ ] I have added unit tests for the new feature or bug fix (if not, why?)
[ ] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[ ] I have opened a PR for the related docs change (if not, why?)

Testing Instructions

New Dependency Instructions (If applicable)

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 41.55%. Comparing base (64231a6) to head (7af2d78).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             napa    #4793   +/-   ##
=======================================
  Coverage   41.55%   41.55%
=======================================
  Files         105      105
  Lines        9834     9834
=======================================
  Hits         4087     4087
  Misses       5395     5395
  Partials      352      352

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Iss 295 validator crashes when defstructure is absent in the definexml

Download the following test files:
define-absent.xml.txt
define-present.xml.txt
rule-send6.json.txt
test-dataset-send.json.txt

Put the files in your local computer such as ./dist/issue295

Remove the file extension .txt from file names

Copy define-absent.xml to define.xml and then run the following commands (only difference is the -vx):
python core.py test -s sdtmig -v 3-4 -dp ./dist/issue295/test-dataset-send.json -r ./dist/issue295/rule-send6.json -dv 2.1  -vx y -l trace
python core.py test -s sdtmig -v 3-4 -dp ./dist/issue295/test-dataset-send.json -r ./dist/issue295/rule-send6.json -dv 2.1  -vx n -l trace
You will get trace information in both commands. The first you will get "SUCCESS" and the second one with "SKIPPED"

Copy define-present.xml to define.xml and then run the following commands:
python core.py test -s sdtmig -v 3-4 -dp ./dist/issue295/test-dataset-send.json -r ./dist/issue295/rule-send6.json -dv 2.1  -vx y -l trace
python core.py test -s sdtmig -v 3-4 -dp ./dist/issue295/test-dataset-send.json -r ./dist/issue295/rule-send6.json -dv 2.1  -vx n -l trace
You should not get any trace information in both commands and both will get "SUCCESS" in the report.

@htu A lot of my original comments are still unresolved. Also there are merge conflicts which should be resolved

More merge conflicts from your other PR. Once fixed I will merge. @htu


Issue 13307

Added new term 'extrasynaptic signaling via GABA', parent 'gamma-aminobutyric acid signaling pathway', which has a new logical definition 'cell-cell signaling' and 'starts with' some GABA receptor activity'.

Looks good!

Hi @raymond91125
While we don't have guidelines about this, I delete my branches once they are merged (locally and on the repo).

will do.


Benchmark and adapt new core resources.

Describe the issue:
Test and change the core resources. Now that we have the entire application in one container these need to be tested and changed in order to keep the same performance.
For this, we want to use the same load as before, and perhaps a good metric contender to use as a reference is the cluster load, so we should aim that both benchmarks process the same number of records while maintaining the same cluster load (given that no other metrics degrade).

@rodrigo-lourenco-lopes it's a bit unclear to me what this issue is about :thinking:
Is it just about making the benchmark chart work with the new changes (that was done with support from @drodriguez-305)
Or is it something else? :thinking:


[FIX] move question conversion nifti

the question was in the general section and not the MRI section
note that this is one of the most frequently asked question on neurostars so we should probably work on improving the answer

@iamdamion @bendhouseart
this is a quick fix so I will merge right away.


⚠ Bofrost.de has degraded performance

In aa857ae, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1385 ms

Resolved: Bofrost.de performance has improved in f07ece8 after 1 hour, 44 minutes.


Update README.md to better show how to use output parameter

Related to the following issue: #560

Thanks!


Documentation needed for Azure Storage blob input bindings

Hello!
My Azure function use case involves an HTTP-triggered function that processes multiple blobs in a specified storage container. However, the available bindings (Python vs model) do not mention supporting such a basic use case.
Could you please update the documentation to confirm whether such a use case is supported? Further, the documentation for bindings is lacking for the v2 programming model. Would really be helpful if that is included as the current docs focus on only triggers.

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

ID: 5e981ef3-8572-23a1-b15b-debf6ef60485
Version Independent ID: 75d38787-8f8a-f948-edeb-a08d980961e4
Content: Python V2 model Azure Functions triggers and bindings
Content Source: articles/azure-functions/functions-bindings-triggers-python.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@samuelsont
Thanks for your feedback! We will investigate and update as appropriate.

I'm also interested in having more output binding examples. My key use case is having an HTTP handler that besides validating the inputs and replying via HttpResponse also inserts an item in a storage queue.


Unable to load configuration wizard

After installing with HACS, rebooting and adding in the integration, it prompts "Unable to load configuration wizard"

Invalid config
The following integrations and platforms could not be set up:
mqtt
Please check your config and logs.

Do you have a working Mqtt setup for your HA? Did you follow the instructions?


[VS Code] Joining collaboration session: The specified hostname isn’t a valid Live Share URL. Please check the link provided by the host and try again.

%0A%0A%23%23 Error:%0AJoining collaboration session: The specified hostname isn’t a valid Live Share URL. Please check the link provided by the host and try again.%0A%0A%23%23 Steps to Reproduce:%0A1.%0A2.%0A%0A||Version Data|%0A|-:|:-|%0A|**extensionName**|VSLS|%0A|**extensionVersion**|1.0.249|%0A|**protocolVersion**|2.2|%0A|**applicationName**|VSCode|%0A|**applicationVersion**|1.34.0|%0A|**platformName**|Windows|%0A|**platformVersion**|10.0.17763|

Not a bug, this is by design, we only accept urls created by liveshare service for starting/joining a session.


Cannot establish wifi connection on pi zero w

Trying to install on a pi zero w using wifi, the install fails after less than 1 minute having failed to establish a connection.
Log (sanitised)
==================================================
raspberrypi-ua-netinst
==================================================
Revision v1.5.1 (bd078c1)
Built on Wed Jan 25 12:41:03 CET 2017
Running on Raspberry Pi version unknown (9000c1)
==================================================
https://github.com/FooDeas/raspberrypi-ua-netinst/
==================================================
Starting HWRNG... OK
Mounting boot partition... OK
Copying boot files... OK
Executing installer-config.txt... OK

Checking if config.txt needs to be modified before starting installation...
OK

Unmounting boot partition... OK

Network configuration:
  ifname = wlan0
  ip_addr = dhcp
  wlan_ssid = layby
  wlan_psk = ok, pass the word.
  online_config =

Waiting for wlan0... 1.. 2.. 3.. 4.. 5.. 6.. 7.. 8.. 9.. FAILED

Oh noes, something went wrong!
You have 10 seconds to hit ENTER to get a shell...

installer-config.txt
packages=apt-transport-https
release=wheezy
username=david
userpw=password
user_is_admin=1
hostname=pie
domainname=dbr
ifname=wlan0
wlan_country=GB
wlan_ssid="layby"
wlan_psk="ok, pass the word."
timezpne="Europe/London"
keyboard_layout=gb
locales=en_GB.UTF-8
system_default_locale=en_GB.UTF-8
gpu_mem=16
rootfstype=ext4
boot_volume_label=pieboot

I suspect that wifi hasn't been exercised very much.  Where it is possible, if wifi fails, most people would plug in a cable and sort out wifi later.  This, of course, isn't possible with the 0w.
I notice that my pi zero w isn't recognised by the install script.  The script isn't up to date with the source quoted.  This may well not matter, but it does indicate that I may be breaking new ground.
I've tried a few times with a few variations and I can't think what to try next.  I even tried an scS script with some debugging before I realised that the failure was before the custom script was loaded.
Help would be most appreciated, whether I've found a bug or I'm just being thick.
(edited to remove duplicate config)

Your config contains every entry twice but I suppose that's a copy/paste error?

Good spot. @thijstriemstra .
Uou're right.  Just checked the file to make sure.

@dinosore
Please test v1.5.2 beta and report.

@FooDeas Just started the install.
I can ping the address I expect to be allocated by dhcp - so it looks like it's past the problem.
Will post again when it has finished.  I may go to bed, so it might not be until tomorrow.
Thanks for your very prompt response.

@FooDeas
The installation finished, but it doesn't boot.
When I checked the pi, I found the activity led out.
Here is the tailof the log I found in /dev/log
  Removing 'diversion of /boot/overlays/w1-gpio-overlay.dtb to /usr/share/rpikernelhack/overlays/w1-gpio-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/w1-gpio-pullup-overlay.dtb to /usr/share/rpikernelhack/overlays/w1-gpio-pullup-overlay.dtb by rpikernelhack'
  Setting up libraspberrypi0 (1.20160315-1) ...
  Setting up libraspberrypi-bin (1.20160315-1) ...
OK
Preserving original config.txt and kernels...
Configuring bootloader to start the installed system...
Creating default cmdline.txt... OK
Fixing non-privileged SSH password warning... not possible!
Removing cdebootstrap-helper-rc.d... OK
Saving current time for fake-hwclock... OK

Installation finished at Tue Apr 25 22:43:09 UTC 2017 and took 16 min 0 sec (960 seconds)

I put the sd card back in the pi and powered up.  The led stayed out. (This is expected behaviour for a pi 0 w if it doesn't boot).  I believe that I found the led out after installation because of a failure to boot.
I couldn't ping the pi.

Weird... Could you please attach the full log file?

On my laptop, parted -l shows
Model: SD ACLCE (sd/mmc)
Disk /dev/mmcblk1: 63.9GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number  Start   End     Size    Type     File system  Flags
 1      4194kB  138MB   134MB   primary  fat16
 2      138MB   63.9GB  63.7GB  primary  ext4

lsblk shows
mmcblk1     179:0    0  59.5G  0 disk
├─mmcblk1p1 179:1    0   128M  0 part /media/david/pieboot
└─mmcblk1p2 179:2    0  59.4G  0 part /media/david/3ccdeab0-4f31-48f7-9c8c-b98314e9f000

ls -lA /media/david/pieboot/
total 19826
-rw-r--r-- 1 david david   14778 Apr 26 15:28 bcm2708-rpi-0-w.dtb
-rw-r--r-- 1 david david   10825 Apr 26 15:47 bcm2708-rpi-b.dtb
-rw-r--r-- 1 david david   11104 Apr 26 15:47 bcm2708-rpi-b-plus.dtb
-rw-r--r-- 1 david david   10855 Apr 26 15:47 bcm2708-rpi-cm.dtb
-rw-r--r-- 1 david david   12092 Apr 26 15:47 bcm2709-rpi-2-b.dtb
-rw-r--r-- 1 david david   12866 Apr 26 15:47 bcm2710-rpi-3-b.dtb
-rw-r--r-- 1 david david   15346 Apr 26 15:28 bcm2710-rpi-cm3.dtb
-rw-r--r-- 1 david david   17920 Apr 26 15:47 bootcode.bin
-rw-r--r-- 1 david david     161 Apr 26 15:48 cmdline.txt
-rw-r--r-- 1 david david    1704 Apr 26 15:48 config.txt
-rw-r--r-- 1 david david   18693 Apr 26 15:47 COPYING.linux
-rw-r--r-- 1 david david    2496 Apr 26 15:47 fixup_cd.dat
-rw-r--r-- 1 david david    6466 Apr 26 15:47 fixup.dat
-rw-r--r-- 1 david david    9709 Apr 26 15:47 fixup_db.dat
-rw-r--r-- 1 david david    9717 Apr 26 15:47 fixup_x.dat
-rw-r--r-- 1 david david 4055172 Apr 26 15:47 kernel7.img
-rw-r--r-- 1 david david 3964404 Apr 26 15:47 kernel.img
-rw-r--r-- 1 david david    1494 Apr 26 15:47 LICENCE.broadcom
drwxr-xr-x 2 david david   14336 Apr 26 15:48 overlays
drwxr-xr-x 4 david david    2048 Apr 26 15:48 raspberrypi-ua-netinst
-rw-r--r-- 1 david david  613624 Apr 26 15:47 start_cd.elf
-rw-r--r-- 1 david david 4889352 Apr 26 15:47 start_db.elf
-rw-r--r-- 1 david david 2740920 Apr 26 15:47 start.elf
-rw-r--r-- 1 david david 3841544 Apr 26 15:47 start_x.elf

 ls -lA /media/david/3ccdeab0-4f31-48f7-9c8c-b98314e9f000/
total 92
drwxrwxr-x  2 root root  4096 Apr 26 16:40 bin
drwxr-xr-x  2 root root  4096 Apr 26 16:28 boot
drwxr-xr-x  3 root root  4096 Apr 26 16:38 dev
drwxr-xr-x 59 root root  4096 Apr 26 16:48 etc
drwxr-xr-x  3 root root  4096 Apr 26 16:43 home
drwxr-xr-x 12 root root  4096 Apr 26 16:48 lib
drwx------  2 root root 16384 Apr 26 16:28 lost+found
drwxr-xr-x  2 root root  4096 Apr 26 16:37 media
drwxr-xr-x  2 root root  4096 Jun 18  2016 mnt
drwxr-xr-x  3 root root  4096 Apr 26 16:47 opt
drwxr-xr-x  2 root root  4096 Jun 18  2016 proc
drwx------  2 root root  4096 Apr 26 16:37 root
drwxr-xr-x  6 root root  4096 Jan  1  1970 run
drwxr-xr-x  2 root root  4096 Apr 26 16:40 sbin
drwxr-xr-x  2 root root  4096 Jun 20  2012 selinux
drwxr-xr-x  2 root root  4096 Apr 26 16:37 srv
drwxr-xr-x  2 root root  4096 Oct 13  2013 sys
drwxrwxrwt  2 root root  4096 Apr 26 16:48 tmp
drwxr-xr-x 10 root root  4096 Apr 26 16:37 usr
drwxr-xr-x 11 root root  4096 Apr 26 16:37 var
ls -lA /media/david/pieboot/
total 19826
-rw-r--r-- 1 david david   14778 Apr 26 15:28 bcm2708-rpi-0-w.dtb
-rw-r--r-- 1 david david   10825 Apr 26 15:47 bcm2708-rpi-b.dtb
-rw-r--r-- 1 david david   11104 Apr 26 15:47 bcm2708-rpi-b-plus.dtb
-rw-r--r-- 1 david david   10855 Apr 26 15:47 bcm2708-rpi-cm.dtb
-rw-r--r-- 1 david david   12092 Apr 26 15:47 bcm2709-rpi-2-b.dtb
-rw-r--r-- 1 david david   12866 Apr 26 15:47 bcm2710-rpi-3-b.dtb
-rw-r--r-- 1 david david   15346 Apr 26 15:28 bcm2710-rpi-cm3.dtb
-rw-r--r-- 1 david david   17920 Apr 26 15:47 bootcode.bin
-rw-r--r-- 1 david david     161 Apr 26 15:48 cmdline.txt
-rw-r--r-- 1 david david    1704 Apr 26 15:48 config.txt
-rw-r--r-- 1 david david   18693 Apr 26 15:47 COPYING.linux
-rw-r--r-- 1 david david    2496 Apr 26 15:47 fixup_cd.dat
-rw-r--r-- 1 david david    6466 Apr 26 15:47 fixup.dat
-rw-r--r-- 1 david david    9709 Apr 26 15:47 fixup_db.dat
-rw-r--r-- 1 david david    9717 Apr 26 15:47 fixup_x.dat
-rw-r--r-- 1 david david 4055172 Apr 26 15:47 kernel7.img
-rw-r--r-- 1 david david 3964404 Apr 26 15:47 kernel.img
-rw-r--r-- 1 david david    1494 Apr 26 15:47 LICENCE.broadcom
drwxr-xr-x 2 david david   14336 Apr 26 15:48 overlays
drwxr-xr-x 4 david david    2048 Apr 26 15:48 raspberrypi-ua-netinst
-rw-r--r-- 1 david david  613624 Apr 26 15:47 start_cd.elf
-rw-r--r-- 1 david david 4889352 Apr 26 15:47 start_db.elf
-rw-r--r-- 1 david david 2740920 Apr 26 15:47 start.elf
-rw-r--r-- 1 david david 3841544 Apr 26 15:47 start_x.elf

 ls -lA /media/david/3ccdeab0-4f31-48f7-9c8c-b98314e9f000/
total 92
drwxrwxr-x  2 root root  4096 Apr 26 16:40 bin
drwxr-xr-x  2 root root  4096 Apr 26 16:28 boot
drwxr-xr-x  3 root root  4096 Apr 26 16:38 dev
drwxr-xr-x 59 root root  4096 Apr 26 16:48 etc
drwxr-xr-x  3 root root  4096 Apr 26 16:43 home
drwxr-xr-x 12 root root  4096 Apr 26 16:48 lib
drwx------  2 root root 16384 Apr 26 16:28 lost+found
drwxr-xr-x  2 root root  4096 Apr 26 16:37 media
drwxr-xr-x  2 root root  4096 Jun 18  2016 mnt
drwxr-xr-x  3 root root  4096 Apr 26 16:47 opt
drwxr-xr-x  2 root root  4096 Jun 18  2016 proc
drwx------  2 root root  4096 Apr 26 16:37 root
drwxr-xr-x  6 root root  4096 Jan  1  1970 run
drwxr-xr-x  2 root root  4096 Apr 26 16:40 sbin
drwxr-xr-x  2 root root  4096 Jun 20  2012 selinux
drwxr-xr-x  2 root root  4096 Apr 26 16:37 srv
drwxr-xr-x  2 root root  4096 Oct 13  2013 sys
drwxrwxrwt  2 root root  4096 Apr 26 16:48 tmp
drwxr-xr-x 10 root root  4096 Apr 26 16:37 usr
drwxr-xr-x 11 root root  4096 Apr 26 16:37 var

Everything seems to work, except that the sd card has been rendered unbootable.
To try again, I had to run the xzcat again.  Both partitions were fine in my laptop, it's just that I couldn't boot the pi (even to try the reinstall process).

==================================================
raspberrypi-ua-netinst
==================================================
Revision __VERSION__
Built on __DATE__
Running on Raspberry Pi version Zero W
==================================================
https://github.com/FooDeas/raspberrypi-ua-netinst/
==================================================
Starting HWRNG... OK
Mounting boot partition... OK
Copying boot files... OK
Executing installer-config.txt... OK

Checking if config.txt needs to be modified before starting installation...
OK

Unmounting boot partition... OK

Network configuration:
  ifname = wlan0
  ip_addr = dhcp
  wlan_ssid = laybay
  wlan_psk = ok, pass the word.
  online_config =

Waiting for wlan0... 1.. OK
Starting wpa_supplicant... OK
Configuring wlan0 with DHCP... <IP_ADDRESS>
Set time using ntpdate... OK

Installation started at Wed Apr 26 15:28:08 UTC 2017 (UTC).

Installer configuration:
  preset = server
  packages = apt-transport-https
  firmware_packages =
  mirror = http://mirrordirector.raspbian.org/raspbian/
  mirror_cache =
  release = wheezy
  hostname = pie
  domainname = dbr
  rootpw = raspbian
  user_ssh_pubkey =
  root_ssh_pubkey =
  root_ssh_pwlogin = 1
  ssh_pwlogin =
  username = david
  userpw = password
  usergpio =
  usergpu =
  usergroups =
  usersysgroups =
  user_is_admin = 1
  cdebootstrap_cmdline = --flavour=minimal --include=locales,console-setup,cpufrequtils,kmod,raspbian-archive-keyring,rng-tools,ifupdown,net-tools,openssh-server,dosfstools,ntp,fake-hwclock,vim-tiny,iputils-ping,wget,ca-certificates,rsyslog,cron,dialog,locales,less,man-db,logrotate,bash-completion,console-setup,apt-utils,isc-dhcp-client,wpasupplicant,crda,sudo
  packages_postinstall = apt-transport-https,raspberrypi-bootloader,firmware-brcm80211,libraspberrypi-bin,raspi-copies-and-fills
  boot_volume_label = pieboot
  bootsize = +128M
  bootoffset = 8192
  rootsize =
  timeserver = time.nist.gov
  timezone = Etc/UTC
  rtc =
  keyboard_layout = gb
  locales = en_GB.UTF-8
  system_default_locale = en_GB.UTF-8
  wlan_country = GB
  cmdline = dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 elevator=deadline fsck.repair=yes
  drivers_to_load =
  gpu_mem = 16
  hdmi_type =
  hdmi_tv_res = 1080p
  hdmi_monitor_res = 1024x768
  hdmi_system_only = 0
  usbroot =
  usbboot =
  rootdev = /dev/mmcblk0
  rootpartition = /dev/mmcblk0p2
  rootfstype = ext4
  rootfs_mkfs_options =
  rootfs_install_mount_options = noatime,data=writeback,nobarrier,noinit_itable
  rootfs_mount_options = errors=remount-ro,noatime
  final_action = reboot
  quiet_boot = 0
  cleanup = 0
  cleanup_logfiles = 0
  spi_enable = 0
  i2c_enable = 0
  i2c_baudrate =
  sound_enable = 0
  camera_enable = 0
  camera_disable_led = 0

OTP dump:
  16:24280000
  17:1020000a
  18:1020000a
  27:00005050
  28:8619abcf
  29:79e65430
  30:009000c1

Waiting 5 seconds.....
Waiting for /dev/mmcblk0...
  Disk /dev/mmcblk0: 59.5 GiB,<PHONE_NUMBER>6 bytes, 124735488 sectors
  Disklabel type: dos
  Disk identifier: 0xd29fad26
OK
Applying new partition table... OK
Initializing /boot as vfat... OK
Copying /boot files in... OK
Initializing / as ext4... OK
Mounting new filesystems... OK

Starting install process...

  Universal Time is now:  Wed Apr 26 15:37:58 UTC 2017.
  Run 'dpkg-reconfigure tzdata' if you wish to change it.

  P: Configuring package man-db
  P: Configuring package net-tools
  P: Configuring package rsyslog
  P: Configuring package vim-common
  P: Configuring package vim-tiny
  P: Configuring package wget
  P: Configuring package less
  Generating locales (this might take a while)...
  Generation complete.
  P: Configuring package locales
  P: Configuring package openssh-client
  P: Configuring package openssl
  P: Configuring package ca-certificates
  P: Configuring package libcpufreq0
  P: Configuring package cpufrequtils
  P: Configuring package wireless-regdb
  P: Configuring package crda
  P: Configuring package dialog
  P: Configuring package dosfstools
  Creating SSH2 RSA key; this may take some time ...
  Creating SSH2 DSA key; this may take some time ...
  Creating SSH2 ECDSA key; this may take some time ...
  invoke-rc.d: policy-rc.d denied execution of restart.
  P: Configuring package openssh-server
  P: Configuring package rng-tools
  P: Configuring package sudo
  P: Configuring package wpasupplicant
  P: Configuring package fake-hwclock
  P: Deconfiguring helper cdebootstrap-helper-apt
  P: Deconfiguring helper cdebootstrap-helper-makedev
  P: Writing apt sources.list
  P: Writing hosts
  P: Writing resolv.conf

Configuring installed system:
mount: mounting /run on /rootfs/run failed: No such file or directory
  Setting root password... OK
  Configuring user 'david':
    Adding user `david' ...
    Adding new group `david' (1000) ...
    Adding new user `david' (1000) with group `david' ...
    Creating home directory `/home/david' ...
    Copying files from `/etc/skel' ...
  Setting password for 'david'... OK
  Adding 'david' to sudo group... OK
  Configuring /etc/fstab... OK
  Configuring hostname... OK
  Configuring hosts... adding pie.dbr... OK
  Configuring network settings... OK
  Configuring tzdata, setting timezone to Etc/UTC... OK
  Enabling locales... en_GB.UTF-8... OK
  Generating locales (this might take a while)...
    en_GB.UTF-8... done
  Generation complete.
  Setting system default locale 'en_GB.UTF-8'... OK
  Setting default keyboard layout 'gb'... OK

Configuring apt:
  Configuring Raspbian repository... OK
  Checking Raspbian repository entry... OK
  Adding raspberrypi.org GPG key to apt-key... OK
  Configuring RaspberryPi repository... OK
  Configuring RaspberryPi preference... OK

Updating package lists... OK

Downloading packages...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  The following extra packages will be installed:
    libcurl3-gnutls libldap-2.4-2 libraspberrypi0 librtmp0 libsasl2-2
    libsasl2-modules libssh2-1
  Suggested packages:
    initramfs-tools libsasl2-modules-otp libsasl2-modules-ldap
    libsasl2-modules-sql libsasl2-modules-gssapi-mit
    libsasl2-modules-gssapi-heimdal
  The following NEW packages will be installed:
    apt-transport-https firmware-brcm80211 libcurl3-gnutls libldap-2.4-2
    libraspberrypi-bin libraspberrypi0 librtmp0 libsasl2-2 libsasl2-modules
    libssh2-1 raspberrypi-bootloader raspi-copies-and-fills
  0 upgraded, 12 newly installed, 0 to remove and 3 not upgraded.
  Need to get 35.8 MB of archives.
  After this operation, 125 MB of additional disk space will be used.
  Get:1 http://archive.raspberrypi.org/debian/ wheezy/main firmware-brcm80211 all 0.43+rpi5 [1678 kB]
  Get:2 http://mirrordirector.raspbian.org/raspbian/ wheezy/main libldap-2.4-2 armhf 2.4.31-2+rpi1 [218 kB]
  Get:3 http://mirrordirector.raspbian.org/raspbian/ wheezy/main libsasl2-2 armhf 2.1.25.dfsg1-6+deb7u1 [110 kB]
  Get:4 http://mirrordirector.raspbian.org/raspbian/ wheezy/main librtmp0 armhf 2.4+20111222.git4e06e21-1+deb7u1 [58.3 kB]
  Get:5 http://mirrordirector.raspbian.org/raspbian/ wheezy/main libssh2-1 armhf 1.4.2-1.1+deb7u2 [125 kB]
  Get:6 http://mirrordirector.raspbian.org/raspbian/ wheezy/main apt-transport-https armhf <IP_ADDRESS>+rpi1+deb7u7 [109 kB]
  Get:7 http://mirrordirector.raspbian.org/raspbian/ wheezy/main libcurl3-gnutls armhf 7.26.0-1+wheezy19 [309 kB]
  Get:8 http://mirrordirector.raspbian.org/raspbian/ wheezy/main libsasl2-modules armhf 2.1.25.dfsg1-6+deb7u1 [105 kB]
  Get:9 http://archive.raspberrypi.org/debian/ wheezy/main raspi-copies-and-fills armhf 0.4-1 [4926 B]
  Get:10 http://archive.raspberrypi.org/debian/ wheezy/main raspberrypi-bootloader armhf 1.20160315-1 [32.1 MB]
  Get:11 http://archive.raspberrypi.org/debian/ wheezy/main libraspberrypi0 armhf 1.20160315-1 [709 kB]
  Get:12 http://archive.raspberrypi.org/debian/ wheezy/main libraspberrypi-bin armhf 1.20160315-1 [254 kB]
  Fetched 35.8 MB in 1min 15s (477 kB/s)
  Download complete and in download only mode
OK

Installing kernel, bootloader (=firmware) and user packages...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  The following extra packages will be installed:
    libcurl3-gnutls libldap-2.4-2 libraspberrypi0 librtmp0 libsasl2-2
    libsasl2-modules libssh2-1
  Suggested packages:
    initramfs-tools libsasl2-modules-otp libsasl2-modules-ldap
    libsasl2-modules-sql libsasl2-modules-gssapi-mit
    libsasl2-modules-gssapi-heimdal
  The following NEW packages will be installed:
    apt-transport-https firmware-brcm80211 libcurl3-gnutls libldap-2.4-2
    libraspberrypi-bin libraspberrypi0 librtmp0 libsasl2-2 libsasl2-modules
    libssh2-1 raspberrypi-bootloader raspi-copies-and-fills
  0 upgraded, 12 newly installed, 0 to remove and 3 not upgraded.
  Need to get 0 B/35.8 MB of archives.
  After this operation, 125 MB of additional disk space will be used.
  Selecting previously unselected package libsasl2-2:armhf.
  (Reading database ...

  Unpacking libsasl2-2:armhf (from .../libsasl2-2_2.1.25.dfsg1-6+deb7u1_armhf.deb) ...
  Selecting previously unselected package libldap-2.4-2:armhf.
  Unpacking libldap-2.4-2:armhf (from .../libldap-2.4-2_2.4.31-2+rpi1_armhf.deb) ...
  Selecting previously unselected package librtmp0:armhf.
  Unpacking librtmp0:armhf (from .../librtmp0_2.4+20111222.git4e06e21-1+deb7u1_armhf.deb) ...
  Selecting previously unselected package libssh2-1:armhf.
  Unpacking libssh2-1:armhf (from .../libssh2-1_1.4.2-1.1+deb7u2_armhf.deb) ...
  Selecting previously unselected package libcurl3-gnutls:armhf.
  Unpacking libcurl3-gnutls:armhf (from .../libcurl3-gnutls_7.26.0-1+wheezy19_armhf.deb) ...
  Selecting previously unselected package apt-transport-https.
  Unpacking apt-transport-https (from .../apt-transport-https_<IP_ADDRESS>+rpi1+deb7u7_armhf.deb) ...
  Selecting previously unselected package firmware-brcm80211.
  Unpacking firmware-brcm80211 (from .../firmware-brcm80211_0.43+rpi5_all.deb) ...
  Selecting previously unselected package libsasl2-modules:armhf.
  Unpacking libsasl2-modules:armhf (from .../libsasl2-modules_2.1.25.dfsg1-6+deb7u1_armhf.deb) ...
  Selecting previously unselected package raspi-copies-and-fills.
  Unpacking raspi-copies-and-fills (from .../raspi-copies-and-fills_0.4-1_armhf.deb) ...
  Selecting previously unselected package raspberrypi-bootloader.
  Unpacking raspberrypi-bootloader (from .../raspberrypi-bootloader_1.20160315-1_armhf.deb) ...
  Adding 'diversion of /boot/COPYING.linux to /usr/share/rpikernelhack/COPYING.linux by rpikernelhack'
  Adding 'diversion of /boot/LICENCE.broadcom to /usr/share/rpikernelhack/LICENCE.broadcom by rpikernelhack'
  Adding 'diversion of /boot/bcm2708-rpi-b-plus.dtb to /usr/share/rpikernelhack/bcm2708-rpi-b-plus.dtb by rpikernelhack'
  Adding 'diversion of /boot/bcm2708-rpi-b.dtb to /usr/share/rpikernelhack/bcm2708-rpi-b.dtb by rpikernelhack'
  Adding 'diversion of /boot/bcm2708-rpi-cm.dtb to /usr/share/rpikernelhack/bcm2708-rpi-cm.dtb by rpikernelhack'
  Adding 'diversion of /boot/bcm2709-rpi-2-b.dtb to /usr/share/rpikernelhack/bcm2709-rpi-2-b.dtb by rpikernelhack'
  Adding 'diversion of /boot/bcm2710-rpi-3-b.dtb to /usr/share/rpikernelhack/bcm2710-rpi-3-b.dtb by rpikernelhack'
  Adding 'diversion of /boot/bootcode.bin to /usr/share/rpikernelhack/bootcode.bin by rpikernelhack'
  Adding 'diversion of /boot/fixup.dat to /usr/share/rpikernelhack/fixup.dat by rpikernelhack'
  Adding 'diversion of /boot/fixup_cd.dat to /usr/share/rpikernelhack/fixup_cd.dat by rpikernelhack'
  Adding 'diversion of /boot/fixup_db.dat to /usr/share/rpikernelhack/fixup_db.dat by rpikernelhack'
  Adding 'diversion of /boot/fixup_x.dat to /usr/share/rpikernelhack/fixup_x.dat by rpikernelhack'
  Adding 'diversion of /boot/kernel.img to /usr/share/rpikernelhack/kernel.img by rpikernelhack'
  Adding 'diversion of /boot/kernel7.img to /usr/share/rpikernelhack/kernel7.img by rpikernelhack'
  Adding 'diversion of /boot/start.elf to /usr/share/rpikernelhack/start.elf by rpikernelhack'
  Adding 'diversion of /boot/start_cd.elf to /usr/share/rpikernelhack/start_cd.elf by rpikernelhack'
  Adding 'diversion of /boot/start_db.elf to /usr/share/rpikernelhack/start_db.elf by rpikernelhack'
  Adding 'diversion of /boot/start_x.elf to /usr/share/rpikernelhack/start_x.elf by rpikernelhack'
  Adding 'diversion of /boot/overlays/README to /usr/share/rpikernelhack/overlays/README by rpikernelhack'
  Adding 'diversion of /boot/overlays/ads7846-overlay.dtb to /usr/share/rpikernelhack/overlays/ads7846-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/at86rf233-overlay.dtb to /usr/share/rpikernelhack/overlays/at86rf233-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/bmp085_i2c-sensor-overlay.dtb to /usr/share/rpikernelhack/overlays/bmp085_i2c-sensor-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/dht11-overlay.dtb to /usr/share/rpikernelhack/overlays/dht11-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/enc28j60-overlay.dtb to /usr/share/rpikernelhack/overlays/enc28j60-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/gpio-ir-overlay.dtb to /usr/share/rpikernelhack/overlays/gpio-ir-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/gpio-poweroff-overlay.dtb to /usr/share/rpikernelhack/overlays/gpio-poweroff-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/hifiberry-amp-overlay.dtb to /usr/share/rpikernelhack/overlays/hifiberry-amp-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/hifiberry-dac-overlay.dtb to /usr/share/rpikernelhack/overlays/hifiberry-dac-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/hifiberry-dacplus-overlay.dtb to /usr/share/rpikernelhack/overlays/hifiberry-dacplus-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/hifiberry-digi-overlay.dtb to /usr/share/rpikernelhack/overlays/hifiberry-digi-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/hy28a-overlay.dtb to /usr/share/rpikernelhack/overlays/hy28a-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/hy28b-overlay.dtb to /usr/share/rpikernelhack/overlays/hy28b-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/i2c-gpio-overlay.dtb to /usr/share/rpikernelhack/overlays/i2c-gpio-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/i2c-rtc-overlay.dtb to /usr/share/rpikernelhack/overlays/i2c-rtc-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/i2c0-bcm2708-overlay.dtb to /usr/share/rpikernelhack/overlays/i2c0-bcm2708-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/i2c1-bcm2708-overlay.dtb to /usr/share/rpikernelhack/overlays/i2c1-bcm2708-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/i2s-mmap-overlay.dtb to /usr/share/rpikernelhack/overlays/i2s-mmap-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/iqaudio-dac-overlay.dtb to /usr/share/rpikernelhack/overlays/iqaudio-dac-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/iqaudio-dacplus-overlay.dtb to /usr/share/rpikernelhack/overlays/iqaudio-dacplus-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/lirc-rpi-overlay.dtb to /usr/share/rpikernelhack/overlays/lirc-rpi-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/mcp2515-can0-overlay.dtb to /usr/share/rpikernelhack/overlays/mcp2515-can0-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/mcp2515-can1-overlay.dtb to /usr/share/rpikernelhack/overlays/mcp2515-can1-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/mmc-overlay.dtb to /usr/share/rpikernelhack/overlays/mmc-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/mz61581-overlay.dtb to /usr/share/rpikernelhack/overlays/mz61581-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/pi3-disable-bt-overlay.dtb to /usr/share/rpikernelhack/overlays/pi3-disable-bt-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/pi3-miniuart-bt-overlay.dtb to /usr/share/rpikernelhack/overlays/pi3-miniuart-bt-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/piscreen-overlay.dtb to /usr/share/rpikernelhack/overlays/piscreen-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/piscreen2r-overlay.dtb to /usr/share/rpikernelhack/overlays/piscreen2r-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/pitft28-capacitive-overlay.dtb to /usr/share/rpikernelhack/overlays/pitft28-capacitive-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/pitft28-resistive-overlay.dtb to /usr/share/rpikernelhack/overlays/pitft28-resistive-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/pps-gpio-overlay.dtb to /usr/share/rpikernelhack/overlays/pps-gpio-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/pwm-2chan-overlay.dtb to /usr/share/rpikernelhack/overlays/pwm-2chan-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/pwm-overlay.dtb to /usr/share/rpikernelhack/overlays/pwm-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/qca7000-overlay.dtb to /usr/share/rpikernelhack/overlays/qca7000-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/raspidac3-overlay.dtb to /usr/share/rpikernelhack/overlays/raspidac3-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/rpi-backlight-overlay.dtb to /usr/share/rpikernelhack/overlays/rpi-backlight-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/rpi-dac-overlay.dtb to /usr/share/rpikernelhack/overlays/rpi-dac-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/rpi-display-overlay.dtb to /usr/share/rpikernelhack/overlays/rpi-display-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/rpi-ft5406-overlay.dtb to /usr/share/rpikernelhack/overlays/rpi-ft5406-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/rpi-proto-overlay.dtb to /usr/share/rpikernelhack/overlays/rpi-proto-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/rpi-sense-overlay.dtb to /usr/share/rpikernelhack/overlays/rpi-sense-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/sdhost-overlay.dtb to /usr/share/rpikernelhack/overlays/sdhost-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/sdio-overlay.dtb to /usr/share/rpikernelhack/overlays/sdio-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/smi-dev-overlay.dtb to /usr/share/rpikernelhack/overlays/smi-dev-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/smi-nand-overlay.dtb to /usr/share/rpikernelhack/overlays/smi-nand-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/smi-overlay.dtb to /usr/share/rpikernelhack/overlays/smi-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/spi-bcm2708-overlay.dtb to /usr/share/rpikernelhack/overlays/spi-bcm2708-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/spi-bcm2835-overlay.dtb to /usr/share/rpikernelhack/overlays/spi-bcm2835-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/spi-dma-overlay.dtb to /usr/share/rpikernelhack/overlays/spi-dma-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/tinylcd35-overlay.dtb to /usr/share/rpikernelhack/overlays/tinylcd35-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/uart1-overlay.dtb to /usr/share/rpikernelhack/overlays/uart1-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/vc4-kms-v3d-overlay.dtb to /usr/share/rpikernelhack/overlays/vc4-kms-v3d-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/vga666-overlay.dtb to /usr/share/rpikernelhack/overlays/vga666-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/w1-gpio-overlay.dtb to /usr/share/rpikernelhack/overlays/w1-gpio-overlay.dtb by rpikernelhack'
  Adding 'diversion of /boot/overlays/w1-gpio-pullup-overlay.dtb to /usr/share/rpikernelhack/overlays/w1-gpio-pullup-overlay.dtb by rpikernelhack'
  Selecting previously unselected package libraspberrypi0.
  Unpacking libraspberrypi0 (from .../libraspberrypi0_1.20160315-1_armhf.deb) ...
  Selecting previously unselected package libraspberrypi-bin.
  Unpacking libraspberrypi-bin (from .../libraspberrypi-bin_1.20160315-1_armhf.deb) ...
  Processing triggers for man-db ...
  Setting up libsasl2-2:armhf (2.1.25.dfsg1-6+deb7u1) ...
  Setting up libldap-2.4-2:armhf (2.4.31-2+rpi1) ...
  Setting up librtmp0:armhf (2.4+20111222.git4e06e21-1+deb7u1) ...
  Setting up libssh2-1:armhf (1.4.2-1.1+deb7u2) ...
  Setting up libcurl3-gnutls:armhf (7.26.0-1+wheezy19) ...
  Setting up apt-transport-https (<IP_ADDRESS>+rpi1+deb7u7) ...
  Setting up firmware-brcm80211 (0.43+rpi5) ...
  Setting up libsasl2-modules:armhf (2.1.25.dfsg1-6+deb7u1) ...
  Setting up raspi-copies-and-fills (0.4-1) ...
  Setting up raspberrypi-bootloader (1.20160315-1) ...
  Removing 'diversion of /boot/COPYING.linux to /usr/share/rpikernelhack/COPYING.linux by rpikernelhack'
  Removing 'diversion of /boot/LICENCE.broadcom to /usr/share/rpikernelhack/LICENCE.broadcom by rpikernelhack'
  Removing 'diversion of /boot/bcm2708-rpi-b-plus.dtb to /usr/share/rpikernelhack/bcm2708-rpi-b-plus.dtb by rpikernelhack'
  Removing 'diversion of /boot/bcm2708-rpi-b.dtb to /usr/share/rpikernelhack/bcm2708-rpi-b.dtb by rpikernelhack'
  Removing 'diversion of /boot/bcm2708-rpi-cm.dtb to /usr/share/rpikernelhack/bcm2708-rpi-cm.dtb by rpikernelhack'
  Removing 'diversion of /boot/bcm2709-rpi-2-b.dtb to /usr/share/rpikernelhack/bcm2709-rpi-2-b.dtb by rpikernelhack'
  Removing 'diversion of /boot/bcm2710-rpi-3-b.dtb to /usr/share/rpikernelhack/bcm2710-rpi-3-b.dtb by rpikernelhack'
  Removing 'diversion of /boot/bootcode.bin to /usr/share/rpikernelhack/bootcode.bin by rpikernelhack'
  Removing 'diversion of /boot/fixup.dat to /usr/share/rpikernelhack/fixup.dat by rpikernelhack'
  Removing 'diversion of /boot/fixup_cd.dat to /usr/share/rpikernelhack/fixup_cd.dat by rpikernelhack'
  Removing 'diversion of /boot/fixup_db.dat to /usr/share/rpikernelhack/fixup_db.dat by rpikernelhack'
  Removing 'diversion of /boot/fixup_x.dat to /usr/share/rpikernelhack/fixup_x.dat by rpikernelhack'
  Removing 'diversion of /boot/kernel.img to /usr/share/rpikernelhack/kernel.img by rpikernelhack'
  Removing 'diversion of /boot/kernel7.img to /usr/share/rpikernelhack/kernel7.img by rpikernelhack'
  Removing 'diversion of /boot/start.elf to /usr/share/rpikernelhack/start.elf by rpikernelhack'
  Removing 'diversion of /boot/start_cd.elf to /usr/share/rpikernelhack/start_cd.elf by rpikernelhack'
  Removing 'diversion of /boot/start_db.elf to /usr/share/rpikernelhack/start_db.elf by rpikernelhack'
  Removing 'diversion of /boot/start_x.elf to /usr/share/rpikernelhack/start_x.elf by rpikernelhack'
  Removing 'diversion of /boot/overlays/README to /usr/share/rpikernelhack/overlays/README by rpikernelhack'
  Removing 'diversion of /boot/overlays/ads7846-overlay.dtb to /usr/share/rpikernelhack/overlays/ads7846-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/at86rf233-overlay.dtb to /usr/share/rpikernelhack/overlays/at86rf233-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/bmp085_i2c-sensor-overlay.dtb to /usr/share/rpikernelhack/overlays/bmp085_i2c-sensor-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/dht11-overlay.dtb to /usr/share/rpikernelhack/overlays/dht11-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/enc28j60-overlay.dtb to /usr/share/rpikernelhack/overlays/enc28j60-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/gpio-ir-overlay.dtb to /usr/share/rpikernelhack/overlays/gpio-ir-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/gpio-poweroff-overlay.dtb to /usr/share/rpikernelhack/overlays/gpio-poweroff-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/hifiberry-amp-overlay.dtb to /usr/share/rpikernelhack/overlays/hifiberry-amp-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/hifiberry-dac-overlay.dtb to /usr/share/rpikernelhack/overlays/hifiberry-dac-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/hifiberry-dacplus-overlay.dtb to /usr/share/rpikernelhack/overlays/hifiberry-dacplus-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/hifiberry-digi-overlay.dtb to /usr/share/rpikernelhack/overlays/hifiberry-digi-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/hy28a-overlay.dtb to /usr/share/rpikernelhack/overlays/hy28a-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/hy28b-overlay.dtb to /usr/share/rpikernelhack/overlays/hy28b-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/i2c-gpio-overlay.dtb to /usr/share/rpikernelhack/overlays/i2c-gpio-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/i2c-rtc-overlay.dtb to /usr/share/rpikernelhack/overlays/i2c-rtc-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/i2c0-bcm2708-overlay.dtb to /usr/share/rpikernelhack/overlays/i2c0-bcm2708-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/i2c1-bcm2708-overlay.dtb to /usr/share/rpikernelhack/overlays/i2c1-bcm2708-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/i2s-mmap-overlay.dtb to /usr/share/rpikernelhack/overlays/i2s-mmap-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/iqaudio-dac-overlay.dtb to /usr/share/rpikernelhack/overlays/iqaudio-dac-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/iqaudio-dacplus-overlay.dtb to /usr/share/rpikernelhack/overlays/iqaudio-dacplus-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/lirc-rpi-overlay.dtb to /usr/share/rpikernelhack/overlays/lirc-rpi-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/mcp2515-can0-overlay.dtb to /usr/share/rpikernelhack/overlays/mcp2515-can0-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/mcp2515-can1-overlay.dtb to /usr/share/rpikernelhack/overlays/mcp2515-can1-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/mmc-overlay.dtb to /usr/share/rpikernelhack/overlays/mmc-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/mz61581-overlay.dtb to /usr/share/rpikernelhack/overlays/mz61581-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/pi3-disable-bt-overlay.dtb to /usr/share/rpikernelhack/overlays/pi3-disable-bt-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/pi3-miniuart-bt-overlay.dtb to /usr/share/rpikernelhack/overlays/pi3-miniuart-bt-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/piscreen-overlay.dtb to /usr/share/rpikernelhack/overlays/piscreen-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/piscreen2r-overlay.dtb to /usr/share/rpikernelhack/overlays/piscreen2r-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/pitft28-capacitive-overlay.dtb to /usr/share/rpikernelhack/overlays/pitft28-capacitive-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/pitft28-resistive-overlay.dtb to /usr/share/rpikernelhack/overlays/pitft28-resistive-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/pps-gpio-overlay.dtb to /usr/share/rpikernelhack/overlays/pps-gpio-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/pwm-2chan-overlay.dtb to /usr/share/rpikernelhack/overlays/pwm-2chan-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/pwm-overlay.dtb to /usr/share/rpikernelhack/overlays/pwm-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/qca7000-overlay.dtb to /usr/share/rpikernelhack/overlays/qca7000-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/raspidac3-overlay.dtb to /usr/share/rpikernelhack/overlays/raspidac3-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/rpi-backlight-overlay.dtb to /usr/share/rpikernelhack/overlays/rpi-backlight-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/rpi-dac-overlay.dtb to /usr/share/rpikernelhack/overlays/rpi-dac-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/rpi-display-overlay.dtb to /usr/share/rpikernelhack/overlays/rpi-display-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/rpi-ft5406-overlay.dtb to /usr/share/rpikernelhack/overlays/rpi-ft5406-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/rpi-proto-overlay.dtb to /usr/share/rpikernelhack/overlays/rpi-proto-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/rpi-sense-overlay.dtb to /usr/share/rpikernelhack/overlays/rpi-sense-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/sdhost-overlay.dtb to /usr/share/rpikernelhack/overlays/sdhost-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/sdio-overlay.dtb to /usr/share/rpikernelhack/overlays/sdio-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/smi-dev-overlay.dtb to /usr/share/rpikernelhack/overlays/smi-dev-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/smi-nand-overlay.dtb to /usr/share/rpikernelhack/overlays/smi-nand-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/smi-overlay.dtb to /usr/share/rpikernelhack/overlays/smi-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/spi-bcm2708-overlay.dtb to /usr/share/rpikernelhack/overlays/spi-bcm2708-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/spi-bcm2835-overlay.dtb to /usr/share/rpikernelhack/overlays/spi-bcm2835-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/spi-dma-overlay.dtb to /usr/share/rpikernelhack/overlays/spi-dma-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/tinylcd35-overlay.dtb to /usr/share/rpikernelhack/overlays/tinylcd35-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/uart1-overlay.dtb to /usr/share/rpikernelhack/overlays/uart1-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/vc4-kms-v3d-overlay.dtb to /usr/share/rpikernelhack/overlays/vc4-kms-v3d-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/vga666-overlay.dtb to /usr/share/rpikernelhack/overlays/vga666-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/w1-gpio-overlay.dtb to /usr/share/rpikernelhack/overlays/w1-gpio-overlay.dtb by rpikernelhack'
  Removing 'diversion of /boot/overlays/w1-gpio-pullup-overlay.dtb to /usr/share/rpikernelhack/overlays/w1-gpio-pullup-overlay.dtb by rpikernelhack'
  Setting up libraspberrypi0 (1.20160315-1) ...
  Setting up libraspberrypi-bin (1.20160315-1) ...
OK
Preserving original config.txt and kernels...
Configuring bootloader to start the installed system...
Creating default cmdline.txt... OK
Fixing non-privileged SSH password warning... not possible!
Removing cdebootstrap-helper-rc.d... OK
Saving current time for fake-hwclock... OK

Installation finished at Wed Apr 26 15:48:15 UTC 2017 and took 20 min 7 sec (1207 seconds)

Please try the following installer-config.txt:
packages=apt-transport-https
username=david
userpw=password
user_is_admin=1
hostname=pie
domainname=dbr
ifname=wlan0
wlan_country=GB
wlan_ssid="layby"
wlan_psk="ok, pass the word."
timezone="Europe/London"
keyboard_layout=gb
locales=en_GB.UTF-8
system_default_locale=en_GB.UTF-8
gpu_mem=16
rootfstype=ext4

Typo in "timezone" is fixed, "release" is left out to install jessie and "boot_volume_label" is left out because I never tested that.
But I'm pretty sure, that wheezy is the problem here...

Now, I'm absolutely sure, that wheezy is the problem:
The raspberry pi bootloader package is version 1.20160315-1. You see the date here. The pi zero w needs a much newer bootloader and, important for you too, jessie kernel to get the wifi module working.

Started running 3 minutes ago with your config edited to fix passwords etc.
Don't understand timezone typo.
Should I be able to do a dist-upgrade to Wheezy?

Typo was "timezpne"
A dist-upgrade from wheezy to jessie would work if you do it on a working RPi (make a backup before). Make sure to have installed raspberrypi-bootloader on the upgraded jessie before switching the card into the zero.

I'm looking forward to your report!

I've just ssh'd into pie (the zerow) as distinct from pi (the model B.
Looks ok.
david@pie:~$ apt search raspberrypi-bootloader
Sorting... Done
Full Text Search... Done
raspberrypi-bootloader/stable,now 1.20170405-1 armhf [installed]
  Raspberry Pi bootloader

raspberrypi-bootloader-nokernel/stable 1.20160523-1~nokernel2 armhf
  Raspberry Pi bootloader

david@pie:~$ apt show raspberrypi-bootloader
Package: raspberrypi-bootloader
Source: raspberrypi-firmware
Version: 1.20170405-1
Maintainer: Serge Schneider<EMAIL_ADDRESS>Installed-Size: 12.5 MB
Recommends: raspberrypi-kernel
Homepage: https://github.com/raspberrypi/firmware
Priority: extra
Section: admin
Download-Size: 3,300 kB
APT-Manual-Installed: yes
APT-Sources: http://archive.raspberrypi.org/debian/ jessie/main armhf Packages
Description: Raspberry Pi bootloader
 This package contains the Raspberry Pi firmware and bootloader.
david@pie:~$ ls /etc/apt/sources.list.d
raspberrypi.org.list

On pi I get
root@pi:~# apt show raspberrypi-bootloader
Package: raspberrypi-bootloader
State: not a real package (virtual)
N: Can't select candidate version from package raspberrypi-bootloader as it has no candidate
N: Can't select versions from package 'raspberrypi-bootloader' as it is purely virtual
N: No packages found
root@pi:~# ls /etc/apt/sources.list.d
syncthing.list  upm.list

pi is alresdy on jessie.  However it doesn't use the raspberrypi.org repository.
Pie is now a working pi! With raspberrypi-nootloader installed.
Can't I just do the dist-upgrade on the pi 0w?
And thanks for getting it working.

Can't I just do the dist-upgrade on the pi 0w?

Theroretically yes. But to use your old pi would be easier (working network connection, no manual bootloader replacement). In both cases, you have to edit your old installation apt sources. Create it if a file doesn't exist.
Content of /etc/apt/sources.list:
deb http://mirrordirector.raspbian.org/raspbian jessie main contrib non-free firmware

Content of /etc/apt/sources.list.d/raspberrypi.org.list:
deb http://archive.raspberrypi.org/debian jessie main

Content of /etc/apt/preferences.d/archive_raspberrypi_org.pref:
Package: *
Pin: origin archive.raspberrypi.org
Pin-Priority: 600

Now you can execute apt-get clean, apt-get update and then apt-get dist-upgrade and hope the best! I'd let follow: apt-get install raspberrypi-bootloader raspberrypi-sys-mods dosfstools

And before you reboot, execute as su:
echo "dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 elevator=deadline fsck.repair=yes root=/dev/mmcblk0p2 rootfstype=ext4 rootwait loglevel=3" > /rootfs/boot/cmdline.txt
(This is one line.)

If I understand you, you suggest I put the sd card from the 0w into the b to do the upgrade mainly to use ethernet rather than wifi.
I'll review your comments tomorrow when I'm more awake.
I've just ordered a faster sd card for the B after noticing how much faster the install this time was than the last one using the installer you forked.  It will let me tidy up things a bit.  It currently runs wheezy.  Will I have to install jessie first, or can I go straight to wheezy?
I realise I'm straying off-topic for an issue.  You can contact me, if you wish, with my github username @dbrsoftware.co.uk

One other thing I noticed, I can ping pi.local but not pie.local.

You missunderstood. Fact is, you can't use wheezy on the zero w if you want to use its wifi module at all. It's definitely not working! No kernel modules available for wheezy.
If I understood you right, you want to use your old system from the Pi B in the zero? Then you have to dist-upgrade its wheezy to jessie (steps described above) and now can use the card in the zero without loosing data.
Now I see: Yes, that's off-topic... :)

(ping pie.dbr or its ip - btw. off-topic, too :))

Thank you for fixing the bug first time.  Please close.
The follow-on was all my fault - I relied on my poor memory for debian/raspbian release names and got it wrong.  I should have checked.  I was thinking wheezy followed jessie. (If only they used numbers - 7, 8, 9, or even oldstable, stable, testing).
I did a dist-upgrade to jessie on the B a year or two ago and it's been running happily ever since (with cron housekeeping) syncing to a usb drive.
The zero is destined for my son's house to provide some off-site backup.
I apologise for wasting your time and thank you for continuing to provide support to an old man who should know better.

Thank you for testing the pi zero w!


Failed to enable dns

I'm on Arch.  I was able to install snap and the microk8s snap ok.  I can enable registry, but when I try to enable dns I get this.
❯ sudo microk8s.enable dns
Enabling DNS
Applying manifest
serviceaccount/coredns created
configmap/coredns created
deployment.apps/coredns created
service/kube-dns created
clusterrole.rbac.authorization.k8s.io/coredns created
clusterrolebinding.rbac.authorization.k8s.io/coredns created
Restarting kubelet
systemctl: /snap/microk8s/1247/usr/lib/x86_64-linux-gnu/libp11-kit.so.0: no version information available (required by /usr/lib/systemd/libsystemd-shared-245.so)
systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-245.so: undefined symbol: p11_kit_uri_get_slot_info, version LIBP11_KIT_1.0
Failed to enable dns

It looks like my systemd libs are mismatched with the libp11-kit libs in the container.  I have arch's p11-kit and libp11-kit packages both installed and up to date.
Please run microk8s.inspect and attach the generated tarball to this issue.

inspection-report-20200316_092834.tar.gz

I'm also getting this error on the same distro.

I'm blocked on this as well. Any workaround or are we just waiting for a fix in the snap?

I've heard kind works, but haven't had a chance to try it yet.

@sagotsky kind uses minikube which is not native and it's a single node solution. microk8s on the other hand is native and you can deploy more than one node.

kind uses minikube

Not sure how you came to that conclusion - it's Kubernetes in Docker - all it needs is a working docker daemon, not a full minikube vm.
FWIW, I am using kind now for local development with reasonable success.
But this is a microk8s issue thread :wink:

Also getting this error on arch with up-to-date libp11 packages.

same for me, also getting this error on an updated arch machine

Not sure how you came to that conclusion - it's Kubernetes in Docker - all it needs is a working docker daemon, not a full minikube vm.
You are right, I'm not sure how I got that wrong.

FWIW, I am using kind now for local development with reasonable success.
Nice, I just started using k3s and it's working great as well :+1:

I have same issue on the Archlinux

Same issue for me on Fedora 32 (installed yesterday). Same issue for v1.18 and v1.17 as well. On Fedora 31 no such issue.

Same issue for me on Fedora 32 (installed yesterday). Same issue for v1.18 and v1.17 as well. On Fedora 31 no such issue.
But when I check status, DNS is enabled.

Exact same.

Likewise seeing this on Arch Linux.
I think unfortunately there's not a lot the microk8s team can do to fix this due to it being a snap. If you check snapcraft.yaml this snap is built off core which is Ubuntu 16.04-based. There is a snap based on Ubuntu 18.04 (core18), but I'm guessing it would take a fair bit of effort to move this snap to it, and I don't know if it would resolve the problem.
The core snaps provide the majority of the system libraries, and I can only imagine that trying to replace them in this snap is a major effort. Similarly, this is a classic snap with system-level interaction, so there's always going to be linking from your host system into the snap.
I'm going to try building the snap locally with snapcraft base on core18, but I'm not a Snap expert and I have no idea if it will work.
TLDR it's the nature of snaps. I would love to see this distributed outside of snaps, but I also get the reason it's not.

Update:
I was able to build the snap with a base of core18 but the problem was not resolved. The error message did change slightly, to this:
systemctl: /snap/microk8s/x1/usr/lib/x86_64-linux-gnu/libp11-kit.so.0: no version information available (required by /usr/lib/systemd/libsystemd-shared-245.so)
/usr/bin/systemd-tty-ask-password-agent: /snap/microk8s/x1/usr/lib/x86_64-linux-gnu/libp11-kit.so.0: no version information available (required by /usr/lib/systemd/libsystemd-shared-245.so)

Based on systemctl and systemd-tty-ask-password-agent appearing in there I installed polkit and wrote custom rules to allow passwordless management of the microk8s services, but still no dice. Curiously, 1.15/stable does work, so I may be way off in regards to the base core being the problem.

OK, the problem lies here:
https://github.com/ubuntu/microk8s/blob/master/microk8s-resources/actions/common/utils.sh#L70
When microk8s is invoking sudo, it's modifying the linker paths to only look in its container. Previously, with versions <= 1.15 the scripts just invoked sudo directly without any wrapper function or environment modification. You can see where it changed the kubelet restart at the end of this file in this commit:
https://github.com/ubuntu/microk8s/blob/36f79886a074167a0972a19cc14b134bef5a1bd8/microk8s-resources/actions/enable.dns.sh
So, the workaround is to simply perform these steps manually:

Copy the microk8s DNS manifest from /var/lib/snapd/snap/microk8s/current/actions/dns.yaml to a temporary location
Edit the manifest, replacing all occurrences of $ARCH with your native architecture (most likely amd64
Apply the manifest with microk8s kubectl or your own kubectl binary with these args: microk8s kubectl --kubeconfig=/var/snap/microk8s/current/credentials/client.config apply -f dns.yaml
Edit the kubelet arguments file located at /var/snap/microk8s/current/args/kubelet, adding these lines:

--cluster-domain=cluster.local
--cluster-dns=<IP_ADDRESS>

Restart kubelet via systemd: sudo systemctl restart snap.microk8s.daemon-kubelet.service
Congratulate yourself for doing microk8s' work for it!

However, you'll still get microk8s status reporting that DNS is not enabled. I found why, but it's 3 AM and I'll open a bug report after some sleep.

@bmoller, do you think it's possible for the snap team to fix it?

Thank you for digging into this.
Would any one be interested in unzipping the snap on the [1] PR, installing it with sudo snap install ./microk8s.snap --classic --dangerous and provide feedback if it fixes the issue at hand?
https://github.com/ubuntu/microk8s/pull/1170/checks?check_run_id=636209186

In addition to the error of enable dns, I found a similar error is happening when running microk8s join:
$ sudo microk8s join 172.xx.yy.zz:25000/xxxxxxxxxxxxxxxxxx

WARNING: can't open config file: /usr/lib/ssl/openssl.cnf
systemctl: /snap/microk8s/1379/usr/lib/x86_64-linux-gnu/libp11-kit.so.0: no version information available (required by /usr/lib/systemd/libsystemd-shared-245.so)
systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-245.so: undefined symbol: p11_kit_uri_get_slot_info, version LIBP11_KIT_1.0
Traceback (most recent call last):
  File "/snap/microk8s/1379/scripts/cluster/join.py", line 398, in <module>
    update_flannel(info["etcd"], master_ip, master_port, token)
  File "/snap/microk8s/1379/scripts/cluster/join.py", line 143, in update_flannel
    subprocess.check_call("systemctl restart snap.microk8s.daemon-flanneld.service".split())
  File "/snap/microk8s/1379/usr/lib/python3.5/subprocess.py", line 581, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['systemctl', 'restart', 'snap.microk8s.daemon-flanneld.service']' returned non-zero exit status 127

Arch Linux + microk8s v1.18.2

Please give me feedback on the microk8s enable dns path and then I (or anyone else wishes) will change all the references of systemctl to snapctl.

Okay, I tried the snap of the PR and the microk8s enable dns path seems to be working:
$ sudo snap install ./microk8s.snap --classic --dangerous
microk8s v1.18.2 installed

$ sudo microk8s enable dns
Enabling DNS
Applying manifest                                                                                serviceaccount/coredns created
configmap/coredns created                                                                                deployment.apps/coredns created
service/kube-dns created                                                                                clusterrole.rbac.authorization.k8s.io/coredns created
clusterrolebinding.rbac.authorization.k8s.io/coredns created                                                                Restarting kubelet
DNS is enabled

Yes, I see the same, but it must be executed with sudo.
Maybe it's semantics, but can it be worked to handle the elevation in the scripting? The docs all indicate that as long as I'm am member of microk8s I should be able to interact with the platform.
Reference examples in docs:
https://microk8s.io/docs/

This is growing outside the scope of this issue, but the apiserver-kicker "daemon" is also doing this at [1] and spamming the system journal.
Should I open a new issue? This seems pretty simple to fix these; I can craft a PR if it helps expedite.
[1] https://github.com/ubuntu/microk8s/blob/master/microk8s-resources/wrappers/apiservice-kicker#L38-L42

@ymyzk, @bmoller, everyone, I think I fixed the systemctl references, could you unzip the artifact of build [1], install with snap install ./microk8s.snap --classic --dangerous and provide me with some feedback if it works for you? Thank you.
[1] https://github.com/ubuntu/microk8s/pull/1170/checks?check_run_id=639349717

Thanks for updates, enable dns is not working this time:
$ microk8s enable dns
Enabling DNS
Applying manifest
serviceaccount/coredns created
configmap/coredns created
deployment.apps/coredns created
service/kube-dns created
clusterrole.rbac.authorization.k8s.io/coredns created
clusterrolebinding.rbac.authorization.k8s.io/coredns created
Restarting kubelet
error: error running snapctl: cannot restart without a context
Failed to enable dns

sudo microk8s enable dns was also the same and I'm in the microk8s group.

Thank you @ymyzk. There is a new snap at https://github.com/ubuntu/microk8s/pull/1170/checks?check_run_id=640405337 . This one is better tested.

So far, I confirmed that microk8s enable dns, microk8s disable dns, and microk8s join work :tada: I'll report if I find an issue.

The PR with the fix is merged. The snap on the edge channel should be available within the next few hours. Try it with:
sudo snap install microk8s --classic --channel=edge

The Patch should reach stable with the 1.18.3 release.

FWIW I'm getting the same error with microk8s enable dns on Fedora 32 with microk8s  18.9:
$
systemctl: /snap/microk8s/1702/usr/lib/x86_64-linux-gnu/libp11-kit.so.0: no version information available (required by /usr/lib/systemd/libsystemd-shared-245.so)
systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-245.so: undefined symbol: p11_kit_uri_get_slot_info, version LIBP11_KIT_1.0

I had to use 18.9 because the latest (19.2) wouldn't start the node and I couldn't figure out why. I worked around this issue in 18.9 by restarting microk8s completely (although I know I probably could have restarted just the affected service, I didn't bother finding out the service name).

I'd like to join the previous commenter in reporting I'm also getting this with v1.18.9 on both Arch Linux and Fedora 32:
systemctl: /snap/microk8s/1702/usr/lib/x86_64-linux-gnu/libp11-kit.so.0: no version information available (required by /usr/lib/systemd/libsystemd-shared-245.so)
systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-245.so: undefined symbol: p11_kit_uri_get_slot_info, version LIBP11_KIT_1.0

@danberindei My guess is this won't get much attention because the issue was previously closed. I will open a brand new issue referencing this one.

Thanks @thibgc, I didn't want to open another issue because I was able to work around it (I think) by running "sudo microk8s". I'm not 100% sure, because then I hit some networking problems and I gave up, installing Ubuntu on a desktop machine instead.


chore: turn off fail-fast behavior to prevent cancellation of jobs

As seen in https://github.com/googleapis/java-bigtable/pull/1497, unit tests (11) gets cancelled if unit tests (7) fails. This PR prevents workflows from getting cancelled at the first failed job.

Running into a flaky test with a Instance and cluster metadata write requests' and limit 'Instance and cluster metadata write requests per day' of service message. Will try again in a few.