Agenda for 2022-03-09 Meeting

Meeting Link
Wednesday 9 March 2022 at 16:00 EST. Join Teams meeting
Agenda

Review previous meeting minutes
Briefly discuss ()[https://github.com/dotnet-foundation/wg-maintainers/issues/48]
Talk about how we can provide better guidance to maintainers from this thread as well: Centralised information for .NET Foundation operation
Discuss #55 and #56
Other business

@rprouse, could you post previous meetings notes? They're not available. Will the procedure of leaving DNF be discussed?

@oskardudycz have a look at https://github.com/dotnet-foundation/wg-maintainers/pull/58

@nils-a, thank you. I missed that 👍
So am I correct to think that procedure will be discussed?

Meeting notes for every meeting are already posted here. We weren't planning on discussing leaving the foundation again, we've already discussed it in two meetings and it is going back to the Board to finalize the process.

What's the exact plan then? I've read the docs but it's unclear for me what's left and what's the timeline.
Could you (or someone else from the board) post an update with a clear statement in the dedicated GH discussion that we have? https://github.com/dotnet-foundation/Home/discussions/68#discussioncomment-2234319

@rprouse, @devlead, is there a summary from the Board meeting? I'd like to know if the Off-boarding procedure will be discussed today or all was set up.

I'm curious if I can do anything to help @SeanKilleen with his survey, if it "just" needs time that is okay too.

@Lakritzator

I'm curious if I can do anything to help @SeanKilleen with his survey, if it "just" needs time that is okay too.

Thanks for asking! When I previously brought this up in the meeting, there didn't seem to be any takers for specific support beyond amplification, and it didn't seem that the Foundation wanted to do this survey under their umbrella, so I ran it on my own. The survey did not receive many results (35), and I still have a task to analyze and write up the answers which I hope to do any day.

Hi @SeanKilleen  - The board didn't meet last month, that pushed the newsletter out to this coming Monday (14th). Any chance you can hold off on analyzing until the next week?

@nicoleabuhakmeh sure thing -- Thanks for the heads up!

@oskardudycz , the board has approved the offboarding process, we have met with the lawyers and will begin offboarding the projects that have requested to leave very soon.

@rprouse, thabk you for the information. Great that we’re getting closer. I hope that list includes us; if not, I’d be grateful for what steps I shall take to be on it.


0.6.x stretch builds fail to boot on rock64 SD

Hi,
I got a new Rock64 he other week, I want to use it for Open Media Vault. I can successfully get 0.5.15 to run, but have had no success with 0.6.44 or 0.6.51 (those are the only 0.6.x builds I've tried). I have tried both the armhf and arm64 buillds
Also same issue with the stretch-minimal-x.x.xx-rock64-arm64 images.
I have, however, been able to run the bionic-lxde-rock64-0.6.44-239-arm64 image without issue. This leads me to believe it is an issue with the stretch builds?
To reproduce

Download an affected build (e.g., stretch-openmediavault-rock64-0.6.44-239-armhf.img.xz)
Open etcher
2.1 Select image
2.2 Select SD card
2.3 Flash and wait to verify
3 Insert newly flashed SD card into Rock64
4 Power On

Expected

Power leds light up
Machine boots
Console outputs text over HDMI and eventually settles at login prompt
Machine is accessible over network (e.,g. SSH, HTTP, shown in network scans, etc)

Current behavior

Power leds light up
No signal on HDMI
Machine is not visible on network
(i.e, same behaviour as if no SD card was inserted)

I have tried a selection of SD cards. I have tried with HDMI plugged in and not plugged in, and ethernet connected / not connected
Any ideas?
If there is more information that you need, please let me know, although without any access to a console, I'm not sure what else I can tell you!
Further info: I have also tried upgrading from 0.5.15. Whilst on stable channel, apt-get dist-upgrade runs fine and machine is still bootable. However, when I changed /etc/apt/sources.list.d/ayufan-rock64.list to pre-release and tried dist-upgrade again, I then got the above described behaviour (i.e, a brick)
on 0.5.15, my DVB-T usb adaptor (Geniatech T230) was unable to scan channels (with tvheadend or w_scan), which was one of the reasons I want to try a later build, to see if that fixes it. On the bionic build it is scanning fine though (as it dos on my rPi. If I manage to get the strecth builds working, and DVB is still having issues, then I'll raise that as a new issue.
Thanks for your help
PS> I have a Rock64 2GB board, with no eMMC. Using etcher 1.4.4 on Windows 10 to write the image.

Some additional info. I also just tried the rock64Pro builds, just in case. Unsurprisingly, that didn't work. There was one difference though.
On the Rock64 builds, the ethernet link light does come on, and even flashes a few times. On the Rock64Pro builds, the link light stays off though. So that would insinuate something is happening with the Rock64 builds, but it is failing before the graphics card is initialised.

Rockpro64 is for different board.
On Sun, 10 Jun 2018 at 17:20, Toby Bisco<EMAIL_ADDRESS>wrote:

Some additional info. I also just tried the rock64Pro builds, just in
case. Unsurprisingly, that didn't work. There was one difference though.
On the Rock64 builds, the ethernet link light does come on, and even
flashes a few times. On the Rock64Pro builds, the link light stays off
though. So that would insinuate something is happening with the Rock64
builds, but it is failing before the graphics card is initialised.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ayufan-rock64/linux-build/issues/215#issuecomment-396057368,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACTpQUr4JC7CzoN20pnGtinpmYNVgINKks5t7TlEgaJpZM4UhvuH
.

Hi @ayufan - Thanks for the reply. Yes, I knew it was for a different board. I thought I'd just check though in case he Rock64 and Rock64Pro builds had become switched around and that was why the Rock64 images would not boot.
Any idea why the Rock64 stretch images are failing to boot (on the Rock64 board of course)

Hi,
Just had the same thing - thought I'd give the 'omv-release-upgrade' a go as I was already prepared for the worst.... which unsurprisingly happened.
Thought since I was starting over I'd give the 'stretch-openmediavault-rock64-0.6.44-239-arm64.img.xz' a go and just as described on this thread nothing happened, well no HDMI output or network activity at all.
Reverted back to 'jessie-openmediavault-rock64-0.5.15-136-arm64.img.xz' which I was using before and no problems.

I have also just tried 0.6.53 stretch minimal rock64, and still no joy. No ethernet light, no HDMI signal.

Could this be related to #213 ?

Hi. I also got a new Rock64 board recently. I first tried bionic-containers and that worked brilliantly as far as I can tell. But when i tried stretch-openmediavault there is a crash regardless if I try to run arm64 or armhf. Here's a small part of the console log.
Begin: Loading essential drivers ... [    3.042986] md: linear personality registered for level -1
[    3.056265] md: multipath personality registered for level -4
[    3.069222] md: raid0 personality registered for level 0
[    3.077863] md: raid1 personality registered for level 1
[    3.086003] async_tx: api initialized (async)
[    3.094881] md: raid6 personality registered for level 6
[    3.098421] md: raid5 personality registered for level 5
[    3.101830] md: raid4 personality registered for level 4
[    3.115709] md: raid10 personality registered for level 10
done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
[    3.217295] BUG: spinlock bad magic on CPU#1, btrfs/217
[    3.226181]  lock: 0xffffffc0ebf74b28, .magic: deadffad, .owner: /-1, .owner_cpu: -1
[    3.235674] CPU: 1 PID: 217 Comm: btrfs Not tainted 4.4.132-rockchip-ayufan-271 #1
[    3.245267] Hardware name: Pine64 Rock64 (DT)
[    3.254646] Call trace:
[    3.263739] [] dump_backtrace+0x0/0x220
[    3.273226] [] show_stack+0x24/0x30
[    3.282681] [] dump_stack+0x98/0xc0
[    3.292003] [] spin_dump+0x84/0xa4
[    3.301305] [] spin_bug+0x30/0x3c
[    3.310576] [] do_raw_spin_lock+0x40/0x164
[    3.320046] [] _raw_spin_lock+0x20/0x2c
[    3.329543] [] fsnotify_find_inode_mark+0x2c/0x58
[    3.339234] [] dnotify_flush+0x48/0x10c
[    3.348720] [] filp_close+0x7c/0x9c
[    3.358200] [] __close_fd+0xb8/0xd8
[    3.367691] [] SyS_close+0x28/0x5c
[    3.377162] [] el0_svc_naked+0x24/0x28
[    3.629831] BUG: Bad page map in process btrfs  pte:200000f464ffd3 pmd:e33be003

Closing, as this is now very old. I moved to using DietPi


When shutting of a thermostat after it has been in security mode, the thermostat can start up alone

Security mode which have been introduced in release 1.1.0.beta1 has an unwanted side effect.
Conditions or reproduction:

Set a thermostat in security mode with muting temperature sensor,
-> the thermostat is set to hvac-mode = off and security_state= True
send a temperature value (unmuting the sensor),
-> the thermostat turns to On (but security mode stays to True and here is the bug)
Turn off the thermostast manually,
send a temperature value,
-> the thermostat turns to On and this is unwanted because we have shutdown it manually.

Release 1.1.0


Add simple version of angle distribution and distance distribution

The atoms are selected via strings, making a call to select_atoms() neccesary. A great optimisation when doing multiple angle or distance distributions would be to pass previously selected arrays of positions instead.

This closes #34  for now


fix(Docker): Improved directory configuration to make Docker container work out-of-the-box.

Previous versions of running docker-compose up would error out on both IPFS and Tor. Both of these are fixed. The Docker container should work out-of-the-box now.

:tada: This PR is included in version 1.1.2 :tada:
Your semantic-release bot :package::rocket:


sct_process_segmentation producing incorrect line connections in QC figures

Hi, thanks for reporting an issue, please take some time to consider the applicable guidelines:
https://github.com/neuropoly/spinalcordtoolbox/blob/master/CONTRIBUTING.rst#reporting-a-bug-or-requesting-a-feature
(about how to suitably describe issues or requests) prior to deleting this blurb when about to submit the issue.
Description

Something seems wrong in the qc figures when I run program as follow:
sct_process_segmentation -i t2_seg.nii.gz -vert 3:7 -perslice 1 -o t2_csa_slice.csv -qc "/home/zmz/test

Steps to Reproduce

Install SCT <release or git revision and platform, you can use the
first lines of output of sct_check_dependencies>

Expected behavior:
Actual behavior:

Wow! This is definitely a bug. @zgm0407 could you please upload your t2_seg.nii.gz image so I can try to reproduce. You can drag and drop.

[
t2_seg.nii.gz
](url)

t2_seg_labeled.nii.gz
t2_labels_vert.nii.gz

@zgm0407 thank you for the images, I can reproduce the bug using the following command:
sct_process_segmentation -i t2_seg.nii.gz -vert 3:7 -vertfile t2_seg_labeled.nii.gz -perslice 1 -o t2_csa_slice.csv -qc qc

So I think this one is just an ordering bug, the dots appear to be connected in an order that doesn't match the slice index. All the points are in the right place, but the connecting lines are wrong.
I recreated the CSA figure by reading in the csv and plotting:

so I'm going to investigate the plot code and see if perhaps the code (I assume pandas) is reordering the data.

that makes sense, thank you @cfhammill
@zgm0407 unrelated to this bug: the relatively thick slices (3.3mm) makes the segmentation and output CSA unreliable (e.g. abnormally small cord around slices 220). I would strongly suggest you resample your input image to an isotropic resolution (e.g. 0.7mm iso) before running the segmentation and then process seg. You could do it with the following command:
sct_resample -i t2.nii.gz -mm 0.7x0.7x0.7

Sorting the lists into arrays by z coordinate appears to resolve the problem:

Are we ok with this solution or should I try to dig in to why the lists are getting out of order in the first place?

i'm quite confident, so you can go ahead with a PR. Thanks!

that makes sense, thank you @cfhammill
@zgm0407 unrelated to this bug: the relatively thick slices (3.3mm) makes the segmentation and output CSA unreliable (e.g. abnormally small cord around slices 220). I would strongly suggest you resample your input image to an isotropic resolution (e.g. 0.7mm iso) before running the segmentation and then process seg. You could do it with the following command:
sct_resample -i t2.nii.gz -mm 0.7x0.7x0.7

amazing!thanks a lot.


cant load all music files from storage

Configuration
Run react-native info in your project and share the content.
What react-native-track-player version are you using?
Issue

Code
Show us the code you are using

prefix it by file://${yourLocalUrl}


Add some types to Variable, Expression, and performance_utils

@rileyjmurray : This looks like it's passing tests. The errors in the CI appear to be preexisting.

@r-barnes I'll take a look at the test failures.

Error described here: https://stackoverflow.com/questions/52889746/cant-import-annotations-from-future/52890129
Fix might be to pin an older version of pytest for Python 3.6 builds?

@SteveDiamond : I suggest you just drop 3.6 altogether. The Python Foundation is ceasing support for it on 2021-12-23. This is listed on the main Python site here with additional details here.
Using older versions of PyTest to support an EOLed version of Python doesn't seem sustainable.

There were some changes in the conda repo of the package that is causing the error: https://github.com/conda-forge/tomli-feedstock.
Potentially the issue was fixed already, as tests are passing in my recently opened PR.


Upgrade quicksilver to v1.3.0-16402

Thank you for the contribution. It was merged directly as f36b82f7051ef6cc0631079351d2685e4dbc496f to keep commit history cleaner. Your contribution is still credited to you.


Adding an option to rerun static mutants in Incremental Mode

Is your feature request related to a problem? Please describe.
I found that when ignoreStatic is false, once the status of a static mutant becomes "Survived", it does not change to "Killed" in Incremental Mode even if the tests are modified. I have read the documentation.

Static mutants don't have test coverage; thus, Stryker won't detect test changes for them.
https://stryker-mutator.io/docs/stryker-js/incremental/#limitations

I understand that this behavior is not a bug, but if possible, I would like to rerun the static mutants in Incremental Mode.
For example, rerun all static mutants contained in files where there are mutants that need to be rerun.
What do you think about this? I don't want to ignore mutants as much as possible, but is it still best to set ignoreStatic to true?
Describe the solution you'd like
Adding an option to rerun static mutants in Incremental Mode.
Describe alternatives you've considered
I tried --force option. The company project I work for has more than 10,000 mutants, so running with the --force option on CI takes a long time. As a workaround, I am checking the results with the -m option on my local machine. However, in this case, I need to update the saved mutation test results manually.
Additional context
These are the steps to reproduce.
git clone https://github.com/mkizka/stryker-js-static-incremental
cd stryker-js-static-incremental
yarn
yarn stryker run
// add a test in src/greet.test.ts, then
yarn stryker run

I decided to use ignoreStatic.


Feat/mock services

Draft PR with changes:

change to multi-module project, to enable separate Nitric Mocking unit test library
separated out examples into separate module


Fix Vimeo's unload bug

Hey,
This is in response to #318. The issue is that, for some reason, Vimeo's player still tries to send message using the iframe when removing the node. The trick is to unload it properly using .unload(), waiting until everything has been unloaded, and then remove the node. It is cumbersome, unfortunately.

While digging I also tried to fix the destroy method to bring back the original DOM, but this requires more changes that I'm comfortable doing. Both YT and Vimeo are left in somewhat shady states after a .destroy. Here's my thought process / investigation:

I'm assuming that destroy and restore should go in pair — a restore should bring back what has been destroyd.
Plyr changes the actual DOM provided, so the most straightforward way to bring it back to its original state is cloning the node at the start.
The passed in node gets modified outside of Plyr's init method (here and here). This breaks my assumption that destroy and restore should go in pair.

Hey, thanks for this - I've manually merged this into some other refactoring work I've been doing. 👍


[Bug Report] el-table row-click event fired when a button clicked in a row, two events fired per one user action

Element UI version
2.6.1
OS/Browsers version
Chrome 72.0.3626.121 (Resmi Derleme) (64 bit)
Vue version
2.6.9
Reproduction Link
https://jsfiddle.net/4ghose9L/2/
Steps to reproduce

row-click and button click event have different functionality and it is needed to procces only function run per one user action
row-cliked and button clicked event are fired at same time when user clicks the button.

when cliked a button inside a cell el-table fires row clicked event button cliked event at the same time.
What is Expected?
only button clicked event needs to be fired.
What is actually happening?
row clicked and button clicked evens are fired at the same time.

Add @click.stop to the button to prevent bubbles

@wsyxzxs for the comment and it solves my problem.

@wsyxzxs thanks

Hello, I have a similar issue but with a checkbox. The checkbox just uses a value property because the state wether it is checked or not is stored outside. I want to toggle it by clicking the entire row which works fine but when I click directly into the checkbox, I get the row-click event twice which checks and unchecks the checkbox.
          el-table-column(align="right")
            template(#default="{ row }")
              el-checkbox(:value="isSelected(row)")

The solution above does not work for this case. Any ideas?

Hello, I have a similar issue but with a checkbox. The checkbox just uses a value property because the state wether it is checked or not is stored outside. I want to toggle it by clicking the entire row which works fine but when I click directly into the checkbox, I get the row-click event twice which checks and unchecks the checkbox.
          el-table-column(align="right")
            template(#default="{ row }")
              el-checkbox(:value="isSelected(row)")

The solution above does not work for this case. Any ideas?

Same problem I am having now


Add flag to use adjusted value for newIndex in onReorder callback for ReorderableList widgets

Adds an opt-in flag to use the adjusted value for the newIndex in onReorder for ReorderableListView and the underlying SliverReorderableList. Starting off with opt-in since this will be a breaking change (see https://github.com/flutter/flutter/pull/59103)
From gallery reorderable_list_demo.dart:
  void _onReorder(int oldIndex, int newIndex) {
    setState(() {
      // This part becomes unnecessary
      // if (newIndex > oldIndex) {
      //   newIndex -= 1;
      // }
      final _ListItem item = _items.removeAt(oldIndex);
      _items.insert(newIndex, item);
    });
  }

Starts off the breaking change to fix https://github.com/flutter/flutter/issues/24786
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

I haven't done the guide yet, first just let me know if I'm starting this off right since it's my first breaking change.

@markusaksli-nc - the 3 1/2 year old issue that this PR would fix is embarrassing for both its age and the triviality of the obvious remedy.  The original widget (https://github.com/flutter/flutter/pull/18374) had a long gestation period and the onReorder callback problem (https://github.com/flutter/flutter/issues/24786) which was reported about 3 months later, was not dealt with promptly.  The approach you've suggested here, allowing developers to opt-in to the fix, does make sense, but we don't have a way to automatically update code (via FlutterFix) that works around the problem per the original documentation.  That means that we'd have to continue to support the opt-in flag forever, which - IMHO - complicates everything just a little more than the fix is worth.
There are other ways to handle this, e.g. we could add an additional callback, but having two almost identical callbacks doesn't seem like an overall improvement either.

I had this concern back when I looked at this issue (although I didn't think it was that hopeless). At this point is there even a viable way to get this fix in? Nothing comes to mind right away other than the flag (which seems pointless without migration) or another callback.

It's a shame, but I think - at this point in time - it's best to leave this issue as it is.

Personally I think this is like saying that because we accidentally reversed 1 and 0, from henceforth the number line shall be 1, 0, 2, 3, 4, 5, 6, 7, 8, 9. It's a VERY common use item, so it should be corrected for the future of Flutter, which will be much longer than its past, right? I hope? Do you not expect BETTER things to come?
How about advancing the language version just for this, since it's so freaking common a function? Bump it to 2.5, BREAKING, like was done to 2.0. Why is that a problem? Fix this for the future, don't hobble it for the past.

official crutches....


Cannot be derived from xpublic_key

Hi! How are you?
Thank you very much in advance for the work! It is an excellent library.
I report a problem:
You can only make derivations from root_xplublic_key and from root_xprivate_key. You get the error:
"PermissionError: You can't drive this master key."
But not from xpublic_key (BIP32):
Example: BIP32 Derivation Path: m / 44 '/ 0' / 0 '/ 0
as if you can see it on this site:
https://iancoleman.io/bip39/
Thank you very much again. Greetings

Hey @gerag14,  If on your path have hardened keys, it does not work for root xpublic key, it only works for root xprivate key to drive. You can also refer https://github.com/meherett/python-hdwallet/issues/15#issuecomment-864176466 issue.

I understand.
But if the last derivation (using from_index) is unhardened. Shouldn't it allow deriving from xpub?
I even commented on checking if you are root in the hdwallet.py file at line 487 and it works.

It doesn't work because it starts with 44' key, it requires root xprivate key. It also reads one by one, Sir. Use this
m/44/0/0/0 instead of this m/44'/0'/0'/0 derivation. Thanks!

I shouldn't be able to bypass from an xpub if my LAST bypass was hardened. But in the path (m / 44 '/ 0' / 0 '/ 0) the last derivation is not enforced. Therefore (BIP32) should be able to derive from an xpub and the derivations would be:
m / 0/0
m / 0/1
m / 0/2
I attach the photo of the test.
Thank you in advance for all the contribution!

Thanks @gerag14, Attach it again please. let me see it

@gerag14 is correct. Unhardened key derivation works with only the xpub key (also related to issue #15) — that's the very point of derivation in this context.
As a side note, throwing a PermissionError in situations like this is completely incorrect since the meaning of this exception is related to OS-level errors (it inherits from OSError), not general purpose "you can't do it" errors.
@meherett It looks like removing lines https://github.com/meherett/python-hdwallet/blob/cd8c4f536553acbe38a9a1435380d9482ee8178b/hdwallet/hdwallet.py#L487-L488 is sufficient for this to work.

Hey @alecov, Just see both examples for Root XPublic Key derivations and XPublic Key https://github.com/meherett/python-hdwallet/blob/master/examples/from_root_xpublic_key.py and https://github.com/meherett/python-hdwallet/blob/master/examples/from_xpublic_key.py.
For PermissionError, I will change it into ValueError exception.
Thanks.

can you guys explain something. I tried work with private key and i receive same error:
hdwallet = HDWallet(symbol=BTC)
xprev_key="xprv9z7iGvkix69hxkUo44zia4SM8omSDsVgiftMpfFMmnQT4ThsBy4AgfRLgSuygTHsghwoUAPxqY1JyACycDVd2KdXvCDsuoAPch9UuiCXsoq"
hdwallet.from_xprivate_key(
xprivate_key=xprev_key)
    # hdwallet.clean_derivation()
    hdwallet.from_path(path="m/44'/60'/0'/0/0")

===========>>>>>>>>>>>>>>>>>>error
File "/Users/dmitryshlymovich/workspace/PycharmProjects/test1/tests/test_hdWalletProvider.py", line 60, in test_hdwallet
hdwallet.from_path(path="m/44'/60'/0'/0/0")
File "/Users/dmitryshlymovich/workspace/PycharmProjects/test1/venv/lib/python3.8/site-packages/hdwallet/hdwallet.py", line 445, in from_path
self._derive_key_by_index(int(index[:-1]) + BIP32KEY_HARDEN)
File "/Users/dmitryshlymovich/workspace/PycharmProjects/test1/venv/lib/python3.8/site-packages/hdwallet/hdwallet.py", line 488, in _derive_key_by_index
raise PermissionError("You can't drive this master key.")
PermissionError: You can't drive this master key.
as i understand it's should work with hardening with xliv? i miss something?

v2.0.0 bug issues
please check again the error file tests/hdwallet/test_from_xpublic_key.py
root_xpublic_key
It doesn't make sense for address generation tests/values.json
root_xpublic_key modify to bitcoin_account_extended_public_key
bitcoin_account_extended_public_key:"xpub6CnRmcvtuVkmYV7UrPbrrhpJaor6iy5cFLQHdsgYQsfz9338T6Wqy3vHP1MXCEPMKzq1C8fErhrGnzEYarzsF814HnCzNF6vqo9JiGjjvE2"
bitcoin_account_extended_public_key path m/44'/0'/0'
bitcoin_account_extended_public_key Must be obtained through BIP32 Root Key.
My test environment configuration
from bitcoin.mainnet.mnemonic in tests/values.json

key
value

BIP39 Mnemonic
avocado harsh input rack like desert mask nominee left atom original tower shy barely base

BIP32 Root Key
xprv9s21ZrQH143K3nQRmmivfV9RstNXkiuGcp6XCaUQyNeD4Zczidb8K3ue3LCVSA47aRqvbpVj5NKLxv8DJi1adCzPmzXVJiyJ7o5WkRTDuFe

BIP44 Path
m/44'/0'/0'/0/0

BIP44 Path p2pkh
16W7JeQXEzmYKX8UMFMrg6FwNSPduVdYHo

BIP44 Account Extended Public Key
xpub6CnRmcvtuVkmYV7UrPbrrhpJaor6iy5cFLQHdsgYQsfz9338T6Wqy3vHP1MXCEPMKzq1C8fErhrGnzEYarzsF814HnCzNF6vqo9JiGjjvE2

BIP44 Account Extended Public Key Path
m/44'/0'/0'

use BIP44 Account Extended Public Key

    hdwallet.from_xpublic_key(
        xpublic_key="xpub6CnRmcvtuVkmYV7UrPbrrhpJaor6iy5cFLQHdsgYQsfz9338T6Wqy3vHP1MXCEPMKzq1C8fErhrGnzEYarzsF814HnCzNF6vqo9JiGjjvE2"#_["bitcoin"]["mainnet"]["root_xpublic_key"]
        , strict=False
    )
    hdwallet.from_path(
        path="m/0/0"
    )
    assert hdwallet.p2pkh_address() == "16W7JeQXEzmYKX8UMFMrg6FwNSPduVdYHo"

iancoleman Web site for authentication

Hello Guys,
most HD wallet generate wallet like this using the root key:
m/44'/0'/0'/0/0
m/44'/0'/1'/0/0
m/44'/0'/2'/0/0
so there is a need to use the root public key to generate public address in that format, how do we go about this using this library.
kind regards


fsck should support a filter path and/or --store options

Summary
fsck --decrypt should support a filter path and/or --store options
in a big store with a lot of mounts fsck is a bit painfull.
it should support --store to select the mount to run on
it should in addition support a filter by path (was not working for me with --decrypt)
tested with 1.15.4 i think

For me running fsck with a path works as expected. We can add a store option, but once that's in please check if that all works as expected and report back if not.


Cleanup pattern Makefile

We remove the following lines:

ARGO_TARGET_NAMESPACE=xraylab-1 -> unused
$ grep -R ARGO_TARGET_N
Makefile:ARGO_TARGET_NAMESPACE=xraylab-1

COMPONENT=datacenter -> unused
$ grep -R COMPONENT
Makefile:COMPONENT=datacenter

TARGET_REPO
This one is already defined in common/Makefile
(and has a couple of fixes since this was added in the
top-level Makefile)

CHART_OPTS
This is defined in common/Makefile and we can reuse it without
overriding it

SECRET_NAME="argocd-env" -> unused
$ grep -R SECRET_NAME
Makefile:SECRET_NAME="argocd-env"

LGTM, i think a lot of those variables were from earlier iterations anyways and never pulled from chart.


BEGIN probe exit with -1

What reproduces the bug?
bpftrace -e 'BEGIN { printf("Hello eBPF!\n"); }' on Ubuntu 18.04 with 5.4 HWE kernel. bpftrace, bcc, and libbpf are all built from source with LLVM 12.
Can reproduce this issue with the static bpftrace built using the build-static.sh script.
The output
bpftrace -e 'BEGIN { printf("Hello eBPF!\n"); }'
Attaching 1 probe...

echo $?
255

bpftrace commit: 05cfa8e6cde2d16cdaabe4ad16eb7fd4d793b6ec
bcc commit: 0e29f7032897f2ebdd4c617910aa8ade74bc4b23
libbpf commit: 0e43565ad8b4f7bdfa974916e9d7f800157d06ec
Same problem with the END probe.
Other probes seem to work fine, such as bpftrace --unsafe -e 'tracepoint:syscalls:sys_enter_nanosleep { printf("%s is sleeping.\n", comm); }'
bpftrace --info
System
  OS: Linux 5.4.0-105-generic #119~18.04.1-Ubuntu SMP Tue Mar 8 11:21:24 UTC 2022
  Arch: x86_64

Build
  version: v0.15.0-75-g05cf
  LLVM: 12.0.1
  ORC: v2
  foreach_sym: yes
  unsafe uprobe: no
  bfd: yes
  bcc_usdt_addsem: yes
  bcc bpf_attach_uprobe refcount: yes
  bcc library path resolution: yes
  libbpf btf dump: yes
  libbpf btf dump type decl: yes
  libbpf bpf_prog_load: yes
  libbpf bpf_map_create: yes
  libdw (DWARF support): no

Kernel helpers
  probe_read: yes
  probe_read_str: yes
  probe_read_user: no
  probe_read_user_str: no
  probe_read_kernel: no
  probe_read_kernel_str: no
  get_current_cgroup_id: yes
  send_signal: yes
  override_return: yes
  get_boot_ns: no
  dpath: no
  skboutput: no

Kernel features
  Instruction limit: 1000000
  Loop support: yes
  btf: yes
  map batch: no
  uprobe refcount (depends on Build:bcc bpf_attach_uprobe refcount): yes

Map types
  hash: yes
  percpu hash: yes
  array: yes
  percpu array: yes
  stack_trace: yes
  perf_event_array: yes

Probe types
  kprobe: yes
  tracepoint: yes
  perf_event: yes
  kfunc: no
  iter:task: no
  iter:task_file: no
  kprobe_multi: no
  raw_tp_special: yes

I ran strace, and apparently the 5.4 kernel doesn't support bpf_prog_test_run_opts.
However, this symbol is in bpf.h from libbpf, so bpftrace tries to use bpf_prog_test_run_opts like here.
https://github.com/iovisor/bpftrace/blob/05cfa8e6cde2d16cdaabe4ad16eb7fd4d793b6ec/src/bpftrace.cpp#L1029
The current workaround I had is to comment out
https://github.com/iovisor/bpftrace/blob/05cfa8e6cde2d16cdaabe4ad16eb7fd4d793b6ec/cmake/FindLibBpf.cmake#L57

cc @danobi
The problem seems to be that libbpf has bpf_prog_test_run_opts but the kernel doesn't have the BPF_PROG_TEST_RUN command, so we should check for it, too.

@caizixian can you give the linked PR a try please?

@danobi Thanks a lot for the fix. I will test and report back.

ping @caizixian

@danobi thanks for reminding and for the fix. Yes, I can confirm the problem is now fixed.


noncentral t distribution

I have some other minor edits in this one

lint: use should not fully qualify scope
doc: support KaTeX in docs

and I wrote the function signatures out. The motive for adding the rendering with katex is that these formula are getting unruly, the only reason for all the specificity is that the nomenclature isn't completely qualified for most references.
would close #267

the linked word "here", is this link to wikipedia


AutoMapper valueObjectToObj return {} for simple object

Describe the bug
If an entity contains an array of simple objects, the automapper returns an empty object ({}) instead of the object.
To Reproduce
I noticed this issue in the case I am about to describe, but I think that an array of simple objects in an entity must present the same problem.
I have two entities with the following properties:
export interface EntityAProps {
	foo: string;
	entitiesB: EntityB[]
}

export interface EntityBProps {
	bar: string;
	arraySimpleObject: SimpleObject[]
}

export interface SimpleObject {
	value1: string;
	value2: string;
	value3: number;
	value4: Date;
	value5: string[];
}

To summarize, EntityA contains an array of EntityB, which in turn contains an array of simple objects.
If we do a toObject on EntityA, EntityB is correctly transformed into an object, but arraySimpleObject will contain empty objects {}.
The cause is due to valueObjectToObj in AutoMapper. The case described does not fit into any of the handled cases.
let result = {} as { [key in keyof Props]: any }; is never modified, and the function returns return result as any;.
I suggest adding this.validator.isObject(entity) to the possible cases for the isSimpleValue variable (as in the valueObjectToObj method).
After adding this validator, the issue no longer occurs.
I will create a pull request to fix it.
And, of course, we'll need to bump the version of rich-domain for types-ddd!
Lib Version
rich-domain v1.23.3

@GaetanCottrez  Thank you for reporting this issue and for the detailed explanation! I also appreciate your proposed solution and your willingness to create a pull request to address the problem. Contributions like this are incredibly valuable to the continuous improvement of the project. I’ll review your PR as soon as it’s available, and we’ll make sure to bump the rich-domain version as needed.
Thanks again for your support and for helping to make the project more robust!

Thank you @4lessandrodev !
quick and efficient in handling Pull Request !
Do you want me to create an issue and/or a pull request on the types-ddd repository to bump the version of rich-domain as well?

Yes, please feel free to create an issue and/or pull request on the types-ddd repository to bump the rich-domain version. I truly appreciate your help with this.
Also, I’m currently publishing the new version with the fix, 1.23.4. Thanks again for your support!

Yes, please feel free to create an issue and/or pull request on the types-ddd repository to bump the rich-domain version. I truly appreciate your help with this.
Also, I’m currently publishing the new version with the fix, 1.23.4. Thanks again for your support!

Ok, i created a pull request for bump the last version of rich-domain in types-ddd.
I'll let you organize a release of types-ddd because I don't have control over it.


Custom component onChange does not update inputs since v3

Describe the bug
Since version 3.0.0 the inputs are not updated when using onChange in custom components.
Installed libraries and their versions

<EMAIL_ADDRESS>
To Reproduce
Steps to reproduce the behavior:

Clone https://github.com/JSCasts-episodes/ep18-admin-bro-startup-part3
npm i<EMAIL_ADDRESS>Works!
npm i admin.bro@latest
Does not work :(

Expected behavior
Inputs should be updated
Im searching for the code thats responsible and will add it as a comment as soon as I find it.

Maybe its not even the best way how the example does it :) I was wondering if the
record.update({ profilePhotoLocation: /${filePath} });
from the provided example is clean code. I believe its a workaround to retrieve the id which it will get in the database first, but you should store the path without the id or generate one syntheticly...
Still the onChange function is useful.

https://github.com/SoftwareBrothers/admin-bro/commit/82f6db47ec8a5ea18757880a20c00af79659c041#diff-af02091d5e06fb98c84148caf84d2052
this might be the reason why... but its hard to debug bundles packages for me

The onBlur might be responsible since the component is not a casual text input

fixed in 3.1.0


test(uiSelectDirective): Add test when merging ngClass attributes on uiSelect

References PR #1447

Add missing test on uiSelect when merging ngClass attributes between DOM declaration and template
Add one property attrs.ngClass in createUiSelect(attrs) to append a ng-class attribute to the <ui-select> element

Thanks @Magador!


The immutable extra option breaks Set and Map objects defined in templateOptions

Description
When passing a Set or a Map in the templateOptions, with immutable extra option set to true, then the Set/Map is no longer usable.
Minimal Reproduction
https://stackblitz.com/edit/angular-ph6845?file=src%2Fapp%2Fapp.component.html
Your Environment

Angular version: 11.2.5
Formly version: 5.10.19

Additional context
Maybe a check should be added to the clone function.

This issue has been fixed and released as part of v5.10.20 release.
Please let us know, in case you are still encountering a similar issue/problem.
Thank you!


Use uncompressed kernel file to save memory

If you pass an uncompressed kernel file to qemu, it will mmap() it directly into the address space. That can save some memory if the kernel image is used by many qemu processes, because the kernel can share the memory pages for each process.
See https://stefano-garzarella.github.io/posts/2019-12-22-qemu-kernel-initrd-mmapped/
Would be nice to test if that has a measurable effect in our fleet.

Just note. NeonVMs do not share a kernel. Each VM has its own kernel (yes, the same, but placed in different paths in the docker overlay filesystem).


Parsing

Processing all element from Abstract Syntax Tree (AST)

Processing all element from Abstract Syntax Tree (AST)


[WIP] peer reconnection.

:x: Build AElf <IP_ADDRESS>12 failed (commit https://github.com/AElfProject/AElf/commit/dfab2e88d2 by @samfrb)

:x: Build AElf <IP_ADDRESS>49 failed (commit https://github.com/AElfProject/AElf/commit/775d5b197b by @samfrb)

:x: Build AElf <IP_ADDRESS>62 failed (commit https://github.com/AElfProject/AElf/commit/8f5cf20ab4 by @samfrb)

:x: Build AElf <IP_ADDRESS>36 failed (commit https://github.com/AElfProject/AElf/commit/d15c456969 by @samfrb)

:x: Build AElf <IP_ADDRESS>52 failed (commit https://github.com/AElfProject/AElf/commit/99a097fa39 by @samfrb)

:white_check_mark: Build AElf <IP_ADDRESS>81 completed (commit https://github.com/AElfProject/AElf/commit/c6383f5a8d by @samfrb)

:white_check_mark: Build AElf <IP_ADDRESS>11 completed (commit https://github.com/AElfProject/AElf/commit/c33be83f12 by @samfrb)

:white_check_mark: Build AElf <IP_ADDRESS>26 completed (commit https://github.com/AElfProject/AElf/commit/9daf48a4ed by @samfrb)

:white_check_mark: Build AElf <IP_ADDRESS>33 completed (commit https://github.com/AElfProject/AElf/commit/853e5e963d by @samfrb)

:x: Build AElf <IP_ADDRESS>38 failed (commit https://github.com/AElfProject/AElf/commit/789d1038ea by @zhxymh)


Simplified AppCache template. IMHO the timer is unnecessary. Also, do…

potential fix for https://github.com/NekR/offline-plugin/issues/210

removed 5000ms timeout, so that events work all the time
removed interval-polling. AFAIK there is a race condition until the event handlers have been registered, but afterwards there is no need to continue polling. effectively I got all events twice in Chrome
remove "cleanup" code - don't see any need for that (not even for reducing memory footprint), reducing complexity

I might have overlooked something and thus have removed important code. Please bear with me, the original code was not completely clear to me.
Tested successfully with Chrome 58 on Windows (SW disabled) and Safari on OSX.
Please accept and publish if you are okay with this patch; this is much needed, thank you.
Reference: http://labnote.beedesk.com/the-pitfalls-of-html5-applicationcache

Thanks for a PR!
First of all, I want you understand that every line in that AppCache code in on purpose. I have done extensive testing on all browsers and that's a nightmare. So even if we are going to remove something, we have to this very carefully and i won't rush with this by any means.
I for example don't understand why you delete those timer checks if your read the Pitfalls from linked article. All browsers are buggy with AppCache and some of them don't call some of the events (like UDPATEREADY) at all, especially in iframe.
Also, when reading those articles please take a note that in our case everything is in iframe, and that makes things even more complicated. Some browser for example call lifecycle events individually on top frame, other start calling them and updating status in top frame and then calling some of them in the iframe once that is loaded.
Also, some browsers may not set UDPATEREADY/CACHED/OBSOLETE in the iframe at all, but set in only in top frame, that's why 5000 seconds timeout needed -- to not run it forever.
Those are just from the top of my head, there are more quirks which I cannot remember right now.  I'll think what we can do here, but don't expect it be fully fixed or 100% properly implemented. I don't want to spent weeks on testing all the things again.

I don't see where in that article there is a hint that timer checks are needed. There seems to be only this race condition, which is solved by two checks, not a timer:

You might poll the status and if it is not ready, listen to the CACHEREADY event. But, in between the poll and registering of the event you might miss the CACHEREADY event.

Anyway, you obviously did a lot of testing and have reasons for the timers (documented somewhere?).
The main problem with the current design is the 5000ms timeout. In my situation that is never enough to update the application (real world situation). So, all those workarounds are useless because offline-cache is essentially too impatient ;-)
Just removing the cleanup timer would leave a 50ms timer running, which obviously is not a good idea (and the reason you implemented the cleanup in the first place, I guess).
Any idea how to solve this dilemma?
Is the timer also needed for the (most important) "updateReady" event?
I'll try with a new PR soon.

The main problem with the current design is the 5000ms timeout. In my situation that is never enough to update the application (real world situation). So, all those workarounds are useless because offline-cache is essentially too impatient ;-)

Yes, I see the problem, but we should be very careful touching anything in that code.

Any idea how to solve this dilemma?

Now yet, thinking.

Is the timer also needed for the (most important) "updateReady" event?

Yes, I'm pretty sure there are problems with that event.


[wip] ci: fix libssl env

Codecov Report

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

@@           Coverage Diff           @@
##           master       #1   +/-   ##
=======================================
  Coverage   90.15%   90.15%
=======================================
  Files           9        9
  Lines        1067     1067
=======================================
  Hits          962      962
  Misses        105      105

Continue to review full report at Codecov.

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


Add docs to GuildVoiceUpdateEvent

Pull Request Etiquette

[ ] I have checked the PRs for upcoming features/bug fixes.
[x] I have read the contributing guidelines.

Changes

[ ] Internal code
[ ] Library interface (affecting end-user code)
[x] Documentation
[ ] Other: _____

Closes Issue: NaN
Description
Adds some docs to the GuildVoiceUpdateEvent

Any updates on this?


Sternographer needs at least Go 1.6

Using 1.4 causes stenographer to misread client certificate and throw error. At the end whole stenographer was unusable.
Stenographer server:
Jul 21 12:09:49 localhost stenographer[15077]: 2016/07/21 12:09:49 http: TLS handshake error from <IP_ADDRESS>:53398: tls: client's certificate's extended key usage doesn't permit it to be used for client authentication

cURL:
curl: (35) SSL peer was unable to negotiate an acceptable set of security parameters.

Stenocurl debug:
[root@localhost stenographer]# stenocurl /debug -v
* About to connect() to <IP_ADDRESS> port 1234 (#0)
*   Trying <IP_ADDRESS>...
* Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 1234 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
*   CAfile: /etc/stenographer/certs/ca_cert.pem
  CApath: none
* NSS: client certificate from file
*       subject: CN=<IP_ADDRESS>_client,C=XX,O=Stenographer
*       start date: Jul 21 09:11:15 2016 GMT
*       expire date: Dec 06 09:11:15 2043 GMT
*       common name: <IP_ADDRESS>_client
*       issuer: CN=*.steno,O=Stenographer,C=XX
* NSS error -12227 (SSL_ERROR_HANDSHAKE_FAILURE_ALERT)
* SSL peer was unable to negotiate an acceptable set of security parameters.
* Closing connection 0

Additional information about Go restrictions (fixed in Go 1.6): https://github.com/golang/go/issues/11087

I signed it!


Update enable-the-report-phish-add-in.md

Added outlook 2016 for mac or later as the feature is supported in 2019 as well. The Add-in shows support for Outlook 2016 or later on Mac" in the Office store as well.

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/4230


Cannot get KKmoon Reader to work

I have the issue where i cannot see the CardID in the WebUI, but it will be sent to the Console Input directly (just like typing with a keyboard, but not hitting return key). I also changed the Reader.py.kkmoonRFIDreader to Reader.py. The Reader is Configured to read "29 E: work as QUERTY keyboard layout (default setting). " (there is a configuration card which says it has 28 output formats and supports QW/AZ ERTY keyboard layout)

pi@raspberrypi:~/RPi-Jukebox-RFID/scripts $ python3 RegisterDevice.py
Choose the reader from list
0 C-Media Electronics Inc. USB PnP Sound Device
1 HID 413d:2107
Device Number: 1

deviceName.txt
HID 413d:2107

pi@raspberrypi:~/RPi-Jukebox-RFID/scripts $ ls -la /dev/input/by-id/
total 0
drwxr-xr-x 2 root root 80 Jul 31 13:40 .
drwxr-xr-x 4 root root 140 Jul 31 13:40 ..
lrwxrwxrwx 1 root root 9 Jul 31 13:40 usb-413d_2107-event-kbd -> ../event0
lrwxrwxrwx 1 root root 9 Jul 31 13:40 usb-C-Media_Electronics_Inc._USB_PnP_Sound_Device-event-if03 -> ../event1

pi@raspberrypi:~/RPi-Jukebox-RFID/scripts $ lsusb
Bus 001 Device 006: ID 8086:0808 Intel Corp.
Bus 001 Device 007: ID 0781:5571 SanDisk Corp. Cruzer Fit
Bus 001 Device 005: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]
Bus 001 Device 004: ID 413d:2107
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

 pi@raspberrypi:~ $ tail -n 500 /var/log/syslog
Jul 31 13:40:29 raspberrypi kernel: [    1.356070] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
Jul 31 13:40:29 raspberrypi kernel: [    1.356117] io scheduler mq-deadline registered
Jul 31 13:40:29 raspberrypi kernel: [    1.356149] io scheduler kyber registered
Jul 31 13:40:29 raspberrypi kernel: [    1.359524] bcm2708_fb soc:fb: FB found 1 display(s)
Jul 31 13:40:29 raspberrypi kernel: [    1.376232] Console: switching to colour frame buffer device 90x30
Jul 31 13:40:29 raspberrypi kernel: [    1.385979] bcm2708_fb soc:fb: Registered framebuffer for display 0, size 720x480
Jul 31 13:40:29 raspberrypi kernel: [    1.395577] bcm2835-rng 3f104000.rng: hwrng registered
Jul 31 13:40:29 raspberrypi kernel: [    1.399508] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
Jul 31 13:40:29 raspberrypi kernel: [    1.406940] vc-sm: Videocore shared memory driver
Jul 31 13:40:29 raspberrypi kernel: [    1.411065] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
Jul 31 13:40:29 raspberrypi kernel: [    1.431566] brd: module loaded
Jul 31 13:40:29 raspberrypi kernel: [    1.451624] loop: module loaded
Jul 31 13:40:29 raspberrypi kernel: [    1.456964] Loading iSCSI transport class v2.0-870.
Jul 31 13:40:29 raspberrypi kernel: [    1.461737] libphy: Fixed MDIO Bus: probed
Jul 31 13:40:29 raspberrypi kernel: [    1.465371] usbcore: registered new interface driver lan78xx
Jul 31 13:40:29 raspberrypi kernel: [    1.469001] usbcore: registered new interface driver smsc95xx
Jul 31 13:40:29 raspberrypi kernel: [    1.472367] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
Jul 31 13:40:29 raspberrypi kernel: [    2.204039] Core Release: 2.80a
Jul 31 13:40:29 raspberrypi kernel: [    2.207377] Setting default values for core params
Jul 31 13:40:29 raspberrypi kernel: [    2.210882] Finished setting default values for core params
Jul 31 13:40:29 raspberrypi kernel: [    2.414763] Using Buffer DMA mode
Jul 31 13:40:29 raspberrypi kernel: [    2.418136] Periodic Transfer Interrupt Enhancement - disabled
Jul 31 13:40:29 raspberrypi kernel: [    2.421552] Multiprocessor Interrupt Enhancement - disabled
Jul 31 13:40:29 raspberrypi kernel: [    2.424928] OTG VER PARAM: 0, OTG VER FLAG: 0
Jul 31 13:40:29 raspberrypi kernel: [    2.428319] Dedicated Tx FIFOs mode
Jul 31 13:40:29 raspberrypi kernel: [    2.432214] WARN::dwc_otg_hcd_init:1074: FIQ DMA bounce buffers: virt = b7514000 dma = 0xf7514000 len=9024
Jul 31 13:40:29 raspberrypi kernel: [    2.439162] FIQ FSM acceleration enabled for :
Jul 31 13:40:29 raspberrypi kernel: [    2.439162] Non-periodic Split Transactions
Jul 31 13:40:29 raspberrypi kernel: [    2.439162] Periodic Split Transactions
Jul 31 13:40:29 raspberrypi kernel: [    2.439162] High-Speed Isochronous Endpoints
Jul 31 13:40:29 raspberrypi kernel: [    2.439162] Interrupt/Control Split Transaction hack enabled
Jul 31 13:40:29 raspberrypi kernel: [    2.455467] dwc_otg: Microframe scheduler enabled
Jul 31 13:40:29 raspberrypi kernel: [    2.455558] WARN::hcd_init_fiq:457: FIQ on core 1
Jul 31 13:40:29 raspberrypi kernel: [    2.458676] WARN::hcd_init_fiq:458: FIQ ASM at 806bdcbc length 36
Jul 31 13:40:29 raspberrypi kernel: [    2.461725] WARN::hcd_init_fiq:497: MPHI regs_base at bb810000
Jul 31 13:40:29 raspberrypi kernel: [    2.464735] dwc_otg 3f980000.usb: DWC OTG Controller
Jul 31 13:40:29 raspberrypi kernel: [    2.467809] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
Jul 31 13:40:29 raspberrypi kernel: [    2.470946] dwc_otg 3f980000.usb: irq 56, io mem 0x00000000
Jul 31 13:40:29 raspberrypi kernel: [    2.474034] Init: Port Power? op_state=1
Jul 31 13:40:29 raspberrypi kernel: [    2.477026] Init: Power Port (0)
Jul 31 13:40:29 raspberrypi kernel: [    2.480557] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04
Jul 31 13:40:29 raspberrypi kernel: [    2.486786] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 31 13:40:29 raspberrypi kernel: [    2.490152] usb usb1: Product: DWC OTG Controller
Jul 31 13:40:29 raspberrypi kernel: [    2.493432] usb usb1: Manufacturer: Linux 5.4.51-v7+ dwc_otg_hcd
Jul 31 13:40:29 raspberrypi kernel: [    2.496731] usb usb1: SerialNumber: 3f980000.usb
Jul 31 13:40:29 raspberrypi kernel: [    2.500965] hub 1-0:1.0: USB hub found
Jul 31 13:40:29 raspberrypi kernel: [    2.504260] hub 1-0:1.0: 1 port detected
Jul 31 13:40:29 raspberrypi kernel: [    2.508450] dwc_otg: FIQ enabled
Jul 31 13:40:29 raspberrypi kernel: [    2.508464] dwc_otg: NAK holdoff enabled
Jul 31 13:40:29 raspberrypi kernel: [    2.508475] dwc_otg: FIQ split-transaction FSM enabled
Jul 31 13:40:29 raspberrypi kernel: [    2.508494] Module dwc_common_port init
Jul 31 13:40:29 raspberrypi kernel: [    2.508934] usbcore: registered new interface driver usb-storage
Jul 31 13:40:29 raspberrypi kernel: [    2.512482] mousedev: PS/2 mouse device common for all mice
Jul 31 13:40:29 raspberrypi kernel: [    2.517359] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
Jul 31 13:40:29 raspberrypi kernel: [    2.523281] sdhci: Secure Digital Host Controller Interface driver
Jul 31 13:40:29 raspberrypi kernel: [    2.526459] sdhci: Copyright(c) Pierre Ossman
Jul 31 13:40:29 raspberrypi kernel: [    2.530500] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
Jul 31 13:40:29 raspberrypi kernel: [    2.534091] sdhci-pltfm: SDHCI platform and OF driver helper
Jul 31 13:40:29 raspberrypi kernel: [    2.538665] ledtrig-cpu: registered to indicate activity on CPUs
Jul 31 13:40:29 raspberrypi kernel: [    2.542434] hidraw: raw HID events driver (C) Jiri Kosina
Jul 31 13:40:29 raspberrypi kernel: [    2.546048] usbcore: registered new interface driver usbhid
Jul 31 13:40:29 raspberrypi kernel: [    2.549494] usbhid: USB HID core driver
Jul 31 13:40:29 raspberrypi kernel: [    2.554105] vchiq: vchiq_init_state: slot_zero = (ptrval)
Jul 31 13:40:29 raspberrypi kernel: [    2.559739] [vc_sm_connected_init]: start
Jul 31 13:40:29 raspberrypi kernel: [    2.569033] [vc_sm_connected_init]: end - returning 0
Jul 31 13:40:29 raspberrypi kernel: [    2.574954] Initializing XFRM netlink socket
Jul 31 13:40:29 raspberrypi kernel: [    2.578376] NET: Registered protocol family 17
Jul 31 13:40:29 raspberrypi kernel: [    2.581911] Key type dns_resolver registered
Jul 31 13:40:29 raspberrypi kernel: [    2.585801] Registering SWP/SWPB emulation handler
Jul 31 13:40:29 raspberrypi kernel: [    2.589521] registered taskstats version 1
Jul 31 13:40:29 raspberrypi kernel: [    2.592587] Loading compiled-in X.509 certificates
Jul 31 13:40:29 raspberrypi kernel: [    2.596270] Key type ._fscrypt registered
Jul 31 13:40:29 raspberrypi kernel: [    2.599353] Key type .fscrypt registered
Jul 31 13:40:29 raspberrypi kernel: [    2.615576] uart-pl011 3f201000.serial: cts_event_workaround enabled
Jul 31 13:40:29 raspberrypi kernel: [    2.618888] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 81, base_baud = 0) is a PL011 rev2
Jul 31 13:40:29 raspberrypi kernel: [    2.737678] Indeed it is in host mode hprt0 = 00021501
Jul 31 13:40:29 raspberrypi kernel: [    2.738006] printk: console [ttyAMA0] enabled
Jul 31 13:40:29 raspberrypi kernel: [    2.833118] random: fast init done
Jul 31 13:40:29 raspberrypi kernel: [    2.839243] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
Jul 31 13:40:29 raspberrypi kernel: [    2.947477] usb 1-1: new high-speed USB device number 2 using dwc_otg
Jul 31 13:40:29 raspberrypi kernel: [    2.953087] sdhost: log_buf @ (ptrval) (f7513000)
Jul 31 13:40:29 raspberrypi kernel: [    2.955875] Indeed it is in host mode hprt0 = 00001101
Jul 31 13:40:29 raspberrypi kernel: [    3.008646] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
Jul 31 13:40:29 raspberrypi kernel: [    3.247912] usb 1-1: New USB device found, idVendor=0424, idProduct=9514, bcdDevice= 2.00
Jul 31 13:40:29 raspberrypi kernel: [    3.268109] of_cfs_init
Jul 31 13:40:29 raspberrypi kernel: [    3.269897] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 31 13:40:29 raspberrypi kernel: [    3.278555] of_cfs_init: OK
Jul 31 13:40:29 raspberrypi kernel: [    3.283902] hub 1-1:1.0: USB hub found
Jul 31 13:40:29 raspberrypi kernel: [    3.310980] mmc0: host does not support reading read-only switch, assuming write-enable
Jul 31 13:40:29 raspberrypi kernel: [    3.311549] hub 1-1:1.0: 5 ports detected
Jul 31 13:40:29 raspberrypi kernel: [    3.319989] mmc0: new high speed SDHC card at address 0007
Jul 31 13:40:29 raspberrypi kernel: [    3.637493] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
Jul 31 13:40:29 raspberrypi kernel: [    3.641416] mmcblk0: mmc0:0007 SD08G 7.21 GiB
Jul 31 13:40:29 raspberrypi kernel: [    3.759044]  mmcblk0: p1 p2
Jul 31 13:40:29 raspberrypi kernel: [    3.778048] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00, bcdDevice= 2.00
Jul 31 13:40:29 raspberrypi kernel: [    3.782779] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
Jul 31 13:40:29 raspberrypi kernel: [    3.794121] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 31 13:40:29 raspberrypi kernel: [    3.797217] smsc95xx v1.0.6
Jul 31 13:40:29 raspberrypi kernel: [    3.810181] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
Jul 31 13:40:29 raspberrypi kernel: [    3.840648] devtmpfs: mounted
Jul 31 13:40:29 raspberrypi kernel: [    3.855276] Freeing unused kernel memory: 1024K
Jul 31 13:40:29 raspberrypi kernel: [    3.864146] Run /sbin/init as init process
Jul 31 13:40:29 raspberrypi kernel: [    3.923614] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:ee:43:b1
Jul 31 13:40:29 raspberrypi kernel: [    4.237532] usb 1-1.2: new full-speed USB device number 4 using dwc_otg
Jul 31 13:40:29 raspberrypi kernel: [    4.379878] usb 1-1.2: New USB device found, idVendor=413d, idProduct=2107, bcdDevice= 0.00
Jul 31 13:40:29 raspberrypi kernel: [    4.396533] usb 1-1.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 31 13:40:29 raspberrypi kernel: [    4.416169] input: HID 413d:2107 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2:1.0/0003:413D:2107.0001/input/input0
Jul 31 13:40:29 raspberrypi kernel: [    4.498577] hid-generic 0003:413D:2107.0001: input,hidraw0: USB HID v1.11 Keyboard [HID 413d:2107] on usb-3f980000.usb-1.2/input0
Jul 31 13:40:29 raspberrypi kernel: [    4.617579] usb 1-1.3: new high-speed USB device number 5 using dwc_otg
Jul 31 13:40:29 raspberrypi kernel: [    4.772623] usb 1-1.3: New USB device found, idVendor=7392, idProduct=7811, bcdDevice= 2.00
Jul 31 13:40:29 raspberrypi kernel: [    4.790227] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 31 13:40:29 raspberrypi kernel: [    4.806071] usb 1-1.3: SerialNumber: 00e04c000001
Jul 31 13:40:29 raspberrypi kernel: [    4.817752] NET: Registered protocol family 10
Jul 31 13:40:29 raspberrypi kernel: [    4.828748] Segment Routing with IPv6
Jul 31 13:40:29 raspberrypi kernel: [    4.927655] usb 1-1.5: new full-speed USB device number 6 using dwc_otg
Jul 31 13:40:29 raspberrypi kernel: [    5.095880] usb 1-1.5: New USB device found, idVendor=8086, idProduct=0808, bcdDevice= 1.00
Jul 31 13:40:29 raspberrypi kernel: [    5.113489] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jul 31 13:40:29 raspberrypi kernel: [    5.126120] usb 1-1.5: Product: USB PnP Sound Device
Jul 31 13:40:29 raspberrypi kernel: [    5.136828] usb 1-1.5: Manufacturer: C-Media Electronics Inc.
Jul 31 13:40:29 raspberrypi kernel: [    5.160836] input: C-Media Electronics Inc.       USB PnP Sound Device as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.3/0003:8086:0808.0002/input/input1
Jul 31 13:40:29 raspberrypi kernel: [    5.258187] hid-generic 0003:8086:0808.0002: input,hidraw1: USB HID v1.00 Device [C-Media Electronics Inc.       USB PnP Sound Device] on usb-3f980000.usb-1.5/input3
Jul 31 13:40:29 raspberrypi kernel: [    5.352377] uart-pl011 3f201000.serial: no DMA platform data
Jul 31 13:40:29 raspberrypi kernel: [    5.587531] usb 1-1.4: new high-speed USB device number 7 using dwc_otg
Jul 31 13:40:29 raspberrypi kernel: [    5.728514] usb 1-1.4: New USB device found, idVendor=0781, idProduct=5571, bcdDevice= 1.00
Jul 31 13:40:29 raspberrypi kernel: [    5.745345] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 31 13:40:29 raspberrypi kernel: [    5.757120] usb 1-1.4: Product: Cruzer Fit
Jul 31 13:40:29 raspberrypi kernel: [    5.765621] usb 1-1.4: Manufacturer: SanDisk'
Jul 31 13:40:29 raspberrypi kernel: [    5.774275] usb 1-1.4: SerialNumber: 4C530000240428208335
Jul 31 13:40:29 raspberrypi kernel: [    5.785008] usb-storage 1-1.4:1.0: USB Mass Storage device detected
Jul 31 13:40:29 raspberrypi kernel: [    5.796383] scsi host0: usb-storage 1-1.4:1.0
Jul 31 13:40:29 raspberrypi kernel: [    6.478215] random: systemd: uninitialized urandom read (16 bytes read)
Jul 31 13:40:29 raspberrypi kernel: [    6.518273] random: systemd: uninitialized urandom read (16 bytes read)
Jul 31 13:40:29 raspberrypi kernel: [    6.554592] random: systemd: uninitialized urandom read (16 bytes read)
Jul 31 13:40:29 raspberrypi kernel: [    6.880779] scsi 0:0:0:0: Direct-Access     SanDisk' Cruzer Fit       1.00 PQ: 0 ANSI: 6
Jul 31 13:40:29 raspberrypi kernel: [    6.895814] i2c /dev entries driver
Jul 31 13:40:29 raspberrypi kernel: [    6.919035] sd 0:0:0:0: [sda] 123174912 512-byte logical blocks: (63.1 GB/58.7 GiB)
Jul 31 13:40:29 raspberrypi kernel: [    6.935675] sd 0:0:0:0: [sda] Write Protect is off
Jul 31 13:40:29 raspberrypi kernel: [    6.944237] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
Jul 31 13:40:29 raspberrypi kernel: [    6.946676] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Jul 31 13:40:29 raspberrypi kernel: [    7.054137]  sda: sda1
Jul 31 13:40:29 raspberrypi kernel: [    7.087687] sd 0:0:0:0: [sda] Attached SCSI removable disk
Jul 31 13:40:29 raspberrypi kernel: [    7.890891] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
Jul 31 13:40:29 raspberrypi kernel: [    8.632914] sd 0:0:0:0: Attached scsi generic sg0 type 0
Jul 31 13:40:29 raspberrypi kernel: [    8.900255] random: crng init done
Jul 31 13:40:29 raspberrypi kernel: [    8.900281] random: 7 urandom warning(s) missed due to ratelimiting
Jul 31 13:40:29 raspberrypi kernel: [    9.141105] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
Jul 31 13:40:29 raspberrypi kernel: [    9.141441] mc: Linux media interface: v0.10
Jul 31 13:40:29 raspberrypi kernel: [    9.144218] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
Jul 31 13:40:29 raspberrypi kernel: [    9.144261] [vc_sm_connected_init]: start
Jul 31 13:40:29 raspberrypi kernel: [    9.148426] [vc_sm_connected_init]: installed successfully
Jul 31 13:40:29 raspberrypi kernel: [    9.189098] videodev: Linux video capture interface: v2.00
Jul 31 13:40:29 raspberrypi kernel: [    9.232398] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
Jul 31 13:40:29 raspberrypi kernel: [    9.250461] bcm2835_audio bcm2835_audio: card created with 8 channels
Jul 31 13:40:29 raspberrypi kernel: [    9.268461] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
Jul 31 13:40:29 raspberrypi kernel: [    9.272249] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
Jul 31 13:40:29 raspberrypi kernel: [    9.298046] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
Jul 31 13:40:29 raspberrypi kernel: [    9.305417] bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned.
Jul 31 13:40:29 raspberrypi kernel: [    9.330345] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
Jul 31 13:40:29 raspberrypi kernel: [    9.336487] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video13
Jul 31 13:40:29 raspberrypi kernel: [    9.337295] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video14
Jul 31 13:40:29 raspberrypi kernel: [    9.340651] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video15
Jul 31 13:40:29 raspberrypi kernel: [    9.341344] bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video16
Jul 31 13:40:29 raspberrypi kernel: [    9.341452] bcm2835-isp bcm2835-isp: Register output node 0 with media controller
Jul 31 13:40:29 raspberrypi kernel: [    9.341486] bcm2835-isp bcm2835-isp: Register capture node 1 with media controller
Jul 31 13:40:29 raspberrypi kernel: [    9.341549] bcm2835-isp bcm2835-isp: Register capture node 2 with media controller
Jul 31 13:40:29 raspberrypi kernel: [    9.341573] bcm2835-isp bcm2835-isp: Register capture node 3 with media controller
Jul 31 13:40:29 raspberrypi kernel: [    9.344015] bcm2835-isp bcm2835-isp: Loaded V4L2 bcm2835-isp
Jul 31 13:40:29 raspberrypi kernel: [    9.373620] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
Jul 31 13:40:29 raspberrypi kernel: [    9.373734] bcm2835-codec bcm2835-codec: Loaded V4L2 decode
Jul 31 13:40:29 raspberrypi kernel: [    9.386910] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
Jul 31 13:40:29 raspberrypi kernel: [    9.387045] bcm2835-codec bcm2835-codec: Loaded V4L2 encode
Jul 31 13:40:29 raspberrypi kernel: [    9.430568] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
Jul 31 13:40:29 raspberrypi kernel: [    9.430701] bcm2835-codec bcm2835-codec: Loaded V4L2 isp
Jul 31 13:40:29 raspberrypi kernel: [    9.903267] usbcore: registered new interface driver uas
Jul 31 13:40:29 raspberrypi kernel: [   10.115081] usbcore: registered new interface driver snd-usb-audio
Jul 31 13:40:29 raspberrypi kernel: [   10.204908] cfg80211: Loading compiled-in X.509 certificates for regulatory database
Jul 31 13:40:29 raspberrypi kernel: [   10.379610] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
Jul 31 13:40:29 raspberrypi kernel: [   10.840117] rtl8192cu: Chip version 0x10
Jul 31 13:40:29 raspberrypi kernel: [   11.106634] rtl8192cu: Board Type 0
Jul 31 13:40:29 raspberrypi kernel: [   11.106941] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1
Jul 31 13:40:29 raspberrypi kernel: [   11.107163] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
Jul 31 13:40:29 raspberrypi kernel: [   11.110659] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
Jul 31 13:40:29 raspberrypi kernel: [   11.113907] usbcore: registered new interface driver rtl8192cu
Jul 31 13:40:29 raspberrypi mtp-probe: checking bus 1, device 4: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2"
Jul 31 13:40:29 raspberrypi mtp-probe: bus: 1, device: 4 was not an MTP device
Jul 31 13:40:29 raspberrypi mtp-probe: bus: 1, device: 3 was not an MTP device
Jul 31 13:40:29 raspberrypi systemd[1]: Found device /dev/disk/by-partuuid/eb4566cf-01.
Jul 31 13:40:29 raspberrypi systemd-udevd[167]: Using default interface naming scheme 'v240'.
Jul 31 13:40:29 raspberrypi systemd-udevd[171]: Using default interface naming scheme 'v240'.
Jul 31 13:40:29 raspberrypi systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jul 31 13:40:29 raspberrypi systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
Jul 31 13:40:29 raspberrypi systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped.
Jul 31 13:40:29 raspberrypi systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
Jul 31 13:40:29 raspberrypi systemd[1]: Condition check resulted in FUSE Control File System being skipped.
Jul 31 13:40:29 raspberrypi systemd[1]: Condition check resulted in Huge Pages File System being skipped.
Jul 31 13:40:29 raspberrypi systemd[1]: Starting File System Check on /dev/disk/by-partuuid/eb4566cf-01...
Jul 31 13:40:29 raspberrypi systemd[1]: Starting Load/Save RF Kill Switch Status...
Jul 31 13:40:29 raspberrypi systemd[1]: Started Load/Save RF Kill Switch Status.
Jul 31 13:40:29 raspberrypi systemd-udevd[165]: Process '/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev' failed with exit code 1.
Jul 31 13:40:29 raspberrypi systemd-udevd[166]: Process '/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev' failed with exit code 1.
Jul 31 13:40:29 raspberrypi systemd-fsck[254]: fsck.fat 4.1 (2017-01-24)
Jul 31 13:40:29 raspberrypi systemd-fsck[254]: /dev/mmcblk0p1: 241 files, 108919/516190 clusters
Jul 31 13:40:29 raspberrypi systemd[1]: Started File System Check on /dev/disk/by-partuuid/eb4566cf-01.
Jul 31 13:40:29 raspberrypi systemd[1]: Mounting /boot...
Jul 31 13:40:29 raspberrypi systemd[1]: Mounted /boot.
Jul 31 13:40:29 raspberrypi systemd[1]: Reached target Local File Systems.
Jul 31 13:40:29 raspberrypi systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
Jul 31 13:40:29 raspberrypi systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
Jul 31 13:40:29 raspberrypi systemd[1]: Starting Preprocess NFS configuration...
Jul 31 13:40:29 raspberrypi systemd[1]: Starting Create Volatile Files and Directories...
Jul 31 13:40:29 raspberrypi systemd[1]: Starting Set console font and keymap...
Jul 31 13:40:29 raspberrypi systemd[1]: Starting Raise network interfaces...
Jul 31 13:40:29 raspberrypi systemd[1]: plymouth-read-write.service: Succeeded.
Jul 31 13:40:29 raspberrypi systemd[1]: Started Tell Plymouth To Write Out Runtime Data.
Jul 31 13:40:29 raspberrypi systemd[1]: Received SIGRTMIN+20 from PID 174 (plymouthd).
Jul 31 13:40:29 raspberrypi systemd[1]: nfs-config.service: Succeeded.
Jul 31 13:40:29 raspberrypi systemd[1]: Started Preprocess NFS configuration.
Jul 31 13:40:29 raspberrypi systemd[1]: Condition check resulted in RPC security service for NFS server being skipped.
Jul 31 13:40:29 raspberrypi systemd[1]: Condition check resulted in RPC security service for NFS client and server being skipped.
Jul 31 13:40:29 raspberrypi systemd[1]: Reached target NFS client services.
Jul 31 13:40:29 raspberrypi systemd[1]: Reached target Remote File Systems (Pre).
Jul 31 13:40:29 raspberrypi systemd[1]: Reached target Remote File Systems.
Jul 31 13:40:29 raspberrypi systemd[1]: Started Set console font and keymap.
Jul 31 13:40:29 raspberrypi systemd[1]: Started Create Volatile Files and Directories.
Jul 31 13:40:29 raspberrypi systemd[1]: Starting Network Time Synchronization...
Jul 31 13:40:29 raspberrypi systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Jul 31 13:40:29 raspberrypi systemd[1]: Started Update UTMP about System Boot/Shutdown.
Jul 31 13:40:29 raspberrypi systemd[1]: Started Raise network interfaces.
Jul 31 13:40:29 raspberrypi systemd[1]: Started Network Time Synchronization.
Jul 31 13:40:29 raspberrypi systemd[1]: Reached target System Initialization.
Jul 31 13:40:29 raspberrypi systemd[1]: Listening on mpd.socket.
Jul 31 13:40:29 raspberrypi systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
Jul 31 13:40:29 raspberrypi systemd[1]: Listening on D-Bus System Message Bus Socket.
Jul 31 13:40:29 raspberrypi systemd[1]: Listening on triggerhappy.socket.
Jul 31 13:40:29 raspberrypi systemd[1]: Reached target Sockets.
Jul 31 13:40:29 raspberrypi systemd[1]: Reached target Basic System.
Jul 31 13:40:29 raspberrypi systemd[1]: Condition check resulted in getty on tty2-tty6 if dbus and logind are not available being skipped.
Jul 31 13:40:29 raspberrypi systemd[1]: Condition check resulted in Turn on SSH if /boot/ssh is present being skipped.
Jul 31 13:40:29 raspberrypi systemd[1]: Starting Deferred execution scheduler...
Jul 31 13:40:29 raspberrypi systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
Jul 31 13:40:29 raspberrypi systemd[1]: Starting System Logging Service...
Jul 31 13:40:29 raspberrypi systemd[1]: Started D-Bus System Message Bus.
Jul 31 13:40:29 raspberrypi systemd[1]: Starting Check for Raspberry Pi EEPROM updates...
Jul 31 13:40:29 raspberrypi systemd[1]: Starting Login Service...
Jul 31 13:40:29 raspberrypi systemd[1]: Started Regular background program processing daemon.
Jul 31 13:40:29 raspberrypi systemd[1]: Starting Check for v3d driver...
Jul 31 13:40:29 raspberrypi systemd[1]: Started Manage Sound Card State (restore and store).
Jul 31 13:40:29 raspberrypi systemd[1]: Starting Save/Restore Sound Card State...
Jul 31 13:40:29 raspberrypi systemd[1]: Starting rng-tools.service...
Jul 31 13:40:29 raspberrypi alsactl[338]: alsactl 1.1.8 daemon started
Jul 31 13:40:29 raspberrypi systemd[1]: Condition check resulted in Copy user wpa_supplicant.conf being skipped.
Jul 31 13:40:29 raspberrypi cron[336]: (CRON) INFO (pidfile fd = 3)
Jul 31 13:40:29 raspberrypi systemd[1]: Starting dhcpcd on all interfaces...
Jul 31 13:40:29 raspberrypi systemd[1]: Starting dphys-swapfile - set up, mount/unmount, and delete a swap file...
Jul 31 13:40:29 raspberrypi cron[336]: (CRON) INFO (Running @reboot jobs)
Jul 31 13:40:29 raspberrypi systemd[1]: Starting WPA supplicant...
Jul 31 13:40:29 raspberrypi rngd[348]: rngd 2-unofficial-mt.14 starting up...
Jul 31 13:40:29 raspberrypi rng-tools[340]: Starting Hardware RNG entropy gatherer daemon: rngd.
Jul 31 13:40:29 raspberrypi systemd[1]: Started Daily Cleanup of Temporary Directories.
Jul 31 13:40:29 raspberrypi avahi-daemon[329]: Found user 'avahi' (UID 108) and group 'avahi' (GID 113).
Jul 31 13:40:29 raspberrypi systemd[1]: Starting LSB: Switch to ondemand cpu governor (unless shift key is pressed)...
Jul 31 13:40:29 raspberrypi avahi-daemon[329]: Successfully dropped root privileges.
Jul 31 13:40:29 raspberrypi avahi-daemon[329]: avahi-daemon 0.7 starting up.
Jul 31 13:40:29 raspberrypi systemd[1]: Starting triggerhappy global hotkey daemon...
Jul 31 13:40:29 raspberrypi systemd[1]: Reached target System Time Synchronized.
Jul 31 13:40:29 raspberrypi rngd[348]: entropy feed to the kernel ready
Jul 31 13:40:29 raspberrypi rsyslogd: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd.  [v8.1901.0]
Jul 31 13:40:29 raspberrypi rsyslogd:  [origin software="rsyslogd" swVersion="8.1901.0" x-pid="330" x-info="https://www.rsyslog.com"] start
Jul 31 13:40:29 raspberrypi systemd[1]: Started Daily apt download activities.
Jul 31 13:40:29 raspberrypi systemd[1]: Started Daily apt upgrade and clean activities.
Jul 31 13:40:29 raspberrypi systemd[1]: Started Clean PHP session files every 30 mins.
Jul 31 13:40:29 raspberrypi thd[359]: Found socket passed from systemd
Jul 31 13:40:29 raspberrypi systemd[1]: Started Daily man-db regeneration.
Jul 31 13:40:29 raspberrypi systemd[1]: Started Daily rotation of log files.
Jul 31 13:40:29 raspberrypi systemd[1]: Reached target Timers.
Jul 31 13:40:29 raspberrypi systemd[1]: Started System Logging Service.
Jul 31 13:40:29 raspberrypi systemd[1]: Started triggerhappy global hotkey daemon.
Jul 31 13:40:29 raspberrypi dhcpcd[341]: dev: loaded udev
Jul 31 13:40:29 raspberrypi systemd[1]: Started Deferred execution scheduler.
Jul 31 13:40:29 raspberrypi systemd[1]: Started Check for Raspberry Pi EEPROM updates.
Jul 31 13:40:29 raspberrypi systemd[1]: Started Check for v3d driver.
Jul 31 13:40:29 raspberrypi systemd[1]: Started Save/Restore Sound Card State.
Jul 31 13:40:29 raspberrypi systemd[1]: Started rng-tools.service.
Jul 31 13:40:29 raspberrypi systemd[1]: Reached target Sound Card.
Jul 31 13:40:29 raspberrypi kernel: [   13.743721] 8021q: 802.1Q VLAN Support v1.8
Jul 31 13:40:29 raspberrypi dhcpcd[341]: forked to background, child pid 387
Jul 31 13:40:29 raspberrypi dphys-swapfile[344]: want /var/swap=100MByte, checking existing: keeping it
Jul 31 13:40:29 raspberrypi systemd[1]: Started dhcpcd on all interfaces.
Jul 31 13:40:29 raspberrypi wpa_supplicant[345]: Successfully initialized wpa_supplicant
Jul 31 13:40:29 raspberrypi avahi-daemon[329]: Successfully called chroot().
Jul 31 13:40:29 raspberrypi avahi-daemon[329]: Successfully dropped remaining capabilities.
Jul 31 13:40:29 raspberrypi avahi-daemon[329]: No service file found in /etc/avahi/services.
Jul 31 13:40:29 raspberrypi avahi-daemon[329]: Network interface enumeration completed.
Jul 31 13:40:29 raspberrypi avahi-daemon[329]: Server startup complete. Host name is raspberrypi.local. Local service cookie is<PHONE_NUMBER>.
Jul 31 13:40:29 raspberrypi systemd[1]: Started Login Service.
Jul 31 13:40:30 raspberrypi systemd[1]: Started WPA supplicant.
Jul 31 13:40:30 raspberrypi systemd[1]: Started Avahi mDNS/DNS-SD Stack.
Jul 31 13:40:30 raspberrypi systemd[1]: Reached target Network.
Jul 31 13:40:30 raspberrypi systemd[1]: Started Phoniebox Rotary Encoder Service.
Jul 31 13:40:30 raspberrypi kernel: [   14.007667] Adding 102396k swap on /var/swap.  Priority:-2 extents:1 across:102396k SSFS
Jul 31 13:40:30 raspberrypi systemd[404]: phoniebox-rotary-encoder.service: Failed to execute command: No such file or directory
Jul 31 13:40:30 raspberrypi systemd[404]: phoniebox-rotary-encoder.service: Failed at step EXEC spawning /home/pi/RPi-Jukebox-RFID/scripts/rotary-encoder.py: No such file or directory
Jul 31 13:40:30 raspberrypi dhcpcd-run-hooks[407]: wlan0: starting wpa_supplicant
Jul 31 13:40:30 raspberrypi systemd[1]: Starting Permit User Sessions...
Jul 31 13:40:30 raspberrypi systemd[1]: Starting OpenBSD Secure Shell server...
Jul 31 13:40:30 raspberrypi systemd[1]: Starting Music Player Daemon...
Jul 31 13:40:30 raspberrypi systemd[1]: Started Phoniebox RFID-Reader Service.
Jul 31 13:40:30 raspberrypi systemd[1]: Condition check resulted in fast remote file copy program daemon being skipped.
Jul 31 13:40:30 raspberrypi systemd[1]: Started Phoniebox Idle Watchdog Service.
Jul 31 13:40:30 raspberrypi systemd[1]: Started Phoniebox GPIO Buttons Service.
Jul 31 13:40:30 raspberrypi systemd[1]: Reached target Network is Online.
Jul 31 13:40:30 raspberrypi systemd[1]: Starting LSB: exim Mail Transport Agent...
Jul 31 13:40:30 raspberrypi systemd[1]: Starting Samba NMB Daemon...
Jul 31 13:40:30 raspberrypi systemd[1]: Starting /etc/rc.local Compatibility...
Jul 31 13:40:30 raspberrypi systemd[1]: Starting Lighttpd Daemon...
Jul 31 13:40:30 raspberrypi systemd[1]: Started dphys-swapfile - set up, mount/unmount, and delete a swap file.
Jul 31 13:40:30 raspberrypi systemd[1]: phoniebox-rotary-encoder.service: Main process exited, code=exited, status=203/EXEC
Jul 31 13:40:30 raspberrypi systemd[1]: phoniebox-rotary-encoder.service: Failed with result 'exit-code'.
Jul 31 13:40:30 raspberrypi systemd[1]: Started Permit User Sessions.
Jul 31 13:40:30 raspberrypi systemd[1]: Started /etc/rc.local Compatibility.
Jul 31 13:40:30 raspberrypi kernel: [   14.333571] rtl8192cu: MAC auto ON okay!
Jul 31 13:40:30 raspberrypi systemd[1]: Starting Terminate Plymouth Boot Screen...
Jul 31 13:40:30 raspberrypi kernel: [   14.401511] rtl8192cu: Tx queue select: 0x05
Jul 31 13:40:30 raspberrypi systemd[1]: Starting Hold until boot process finishes up...
Jul 31 13:40:30 raspberrypi systemd[1]: phoniebox-rotary-encoder.service: Service RestartSec=100ms expired, scheduling restart.
Jul 31 13:40:30 raspberrypi systemd[1]: phoniebox-rotary-encoder.service: Scheduled restart job, restart counter is at 1.
Jul 31 13:40:30 raspberrypi systemd[1]: Stopped Phoniebox Rotary Encoder Service.
Jul 31 13:40:30 raspberrypi systemd[1]: Started Phoniebox Rotary Encoder Service.
Jul 31 13:40:30 raspberrypi systemd[428]: phoniebox-rotary-encoder.service: Failed to execute command: No such file or directory
Jul 31 13:40:30 raspberrypi systemd[428]: phoniebox-rotary-encoder.service: Failed at step EXEC spawning /home/pi/RPi-Jukebox-RFID/scripts/rotary-encoder.py: No such file or directory
Jul 31 13:40:30 raspberrypi systemd[1]: phoniebox-rotary-encoder.service: Main process exited, code=exited, status=203/EXEC
Jul 31 13:40:30 raspberrypi systemd[1]: phoniebox-rotary-encoder.service: Failed with result 'exit-code'.
Jul 31 13:40:30 raspberrypi systemd[1]: Received SIGRTMIN+21 from PID 174 (plymouthd).
Jul 31 13:40:30 raspberrypi systemd[1]: phoniebox-rotary-encoder.service: Service RestartSec=100ms expired, scheduling restart.
Jul 31 13:40:30 raspberrypi systemd[1]: phoniebox-rotary-encoder.service: Scheduled restart job, restart counter is at 2.
Jul 31 13:40:30 raspberrypi systemd[1]: Stopped Phoniebox Rotary Encoder Service.
Jul 31 13:40:30 raspberrypi systemd[1]: Started Phoniebox Rotary Encoder Service.
Jul 31 13:40:30 raspberrypi systemd[1]: Received SIGRTMIN+21 from PID 174 (plymouthd).
Jul 31 13:40:30 raspberrypi systemd[430]: phoniebox-rotary-encoder.service: Failed to execute command: No such file or directory
Jul 31 13:40:30 raspberrypi systemd[1]: plymouth-start.service: Succeeded.
Jul 31 13:40:30 raspberrypi systemd[430]: phoniebox-rotary-encoder.service: Failed at step EXEC spawning /home/pi/RPi-Jukebox-RFID/scripts/rotary-encoder.py: No such file or directory
Jul 31 13:40:30 raspberrypi systemd[1]: plymouth-quit.service: Succeeded.
Jul 31 13:40:30 raspberrypi systemd[1]: Started Terminate Plymouth Boot Screen.
Jul 31 13:40:30 raspberrypi systemd[1]: plymouth-quit-wait.service: Succeeded.
Jul 31 13:40:30 raspberrypi systemd[1]: Started Hold until boot process finishes up.
Jul 31 13:40:30 raspberrypi systemd[1]: phoniebox-rotary-encoder.service: Main process exited, code=exited, status=203/EXEC
Jul 31 13:40:30 raspberrypi systemd[1]: phoniebox-rotary-encoder.service: Failed with result 'exit-code'.
Jul 31 13:40:30 raspberrypi systemd[1]: Started Serial Getty on ttyAMA0.
Jul 31 13:40:30 raspberrypi systemd[1]: Started Getty on tty1.
Jul 31 13:40:30 raspberrypi systemd[1]: Reached target Login Prompts.
Jul 31 13:40:31 raspberrypi systemd[1]: phoniebox-rotary-encoder.service: Service RestartSec=100ms expired, scheduling restart.
Jul 31 13:40:31 raspberrypi systemd[1]: phoniebox-rotary-encoder.service: Scheduled restart job, restart counter is at 3.
Jul 31 13:40:31 raspberrypi systemd[1]: Stopped Phoniebox Rotary Encoder Service.
Jul 31 13:40:31 raspberrypi systemd[1]: Started Phoniebox Rotary Encoder Service.
Jul 31 13:40:31 raspberrypi systemd[437]: phoniebox-rotary-encoder.service: Failed to execute command: No such file or directory
Jul 31 13:40:31 raspberrypi systemd[437]: phoniebox-rotary-encoder.service: Failed at step EXEC spawning /home/pi/RPi-Jukebox-RFID/scripts/rotary-encoder.py: No such file or directory
Jul 31 13:40:31 raspberrypi systemd[1]: phoniebox-rotary-encoder.service: Main process exited, code=exited, status=203/EXEC
Jul 31 13:40:31 raspberrypi systemd[1]: phoniebox-rotary-encoder.service: Failed with result 'exit-code'.
Jul 31 13:40:31 raspberrypi systemd[1]: phoniebox-rotary-encoder.service: Service RestartSec=100ms expired, scheduling restart.
Jul 31 13:40:31 raspberrypi systemd[1]: phoniebox-rotary-encoder.service: Scheduled restart job, restart counter is at 4.
Jul 31 13:40:31 raspberrypi systemd[1]: Stopped Phoniebox Rotary Encoder Service.
Jul 31 13:40:31 raspberrypi systemd[1]: Started Phoniebox Rotary Encoder Service.
Jul 31 13:40:31 raspberrypi systemd[438]: phoniebox-rotary-encoder.service: Failed to execute command: No such file or directory
Jul 31 13:40:31 raspberrypi systemd[438]: phoniebox-rotary-encoder.service: Failed at step EXEC spawning /home/pi/RPi-Jukebox-RFID/scripts/rotary-encoder.py: No such file or directory
Jul 31 13:40:31 raspberrypi systemd[1]: phoniebox-rotary-encoder.service: Main process exited, code=exited, status=203/EXEC
Jul 31 13:40:31 raspberrypi systemd[1]: phoniebox-rotary-encoder.service: Failed with result 'exit-code'.
Jul 31 13:40:31 raspberrypi systemd[1]: phoniebox-rotary-encoder.service: Service RestartSec=100ms expired, scheduling restart.
Jul 31 13:40:31 raspberrypi systemd[1]: phoniebox-rotary-encoder.service: Scheduled restart job, restart counter is at 5.
Jul 31 13:40:31 raspberrypi systemd[1]: Stopped Phoniebox Rotary Encoder Service.
Jul 31 13:40:31 raspberrypi systemd[1]: phoniebox-rotary-encoder.service: Start request repeated too quickly.
Jul 31 13:40:31 raspberrypi systemd[1]: phoniebox-rotary-encoder.service: Failed with result 'exit-code'.
Jul 31 13:40:31 raspberrypi systemd[1]: Failed to start Phoniebox Rotary Encoder Service.
Jul 31 13:40:32 raspberrypi raspi-config[356]: Checking if shift key is held down: No. Switching to ondemand scaling governor.
Jul 31 13:40:32 raspberrypi systemd[1]: Started LSB: Switch to ondemand cpu governor (unless shift key is pressed).
Jul 31 13:40:32 raspberrypi systemd[1]: systemd-rfkill.service: Succeeded.
Jul 31 13:40:32 raspberrypi systemd[1]: Started OpenBSD Secure Shell server.
Jul 31 13:40:32 raspberrypi dhcpcd[387]: wlan0: connected to Access Point `'
Jul 31 13:40:32 raspberrypi kernel: [   16.465386] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Jul 31 13:40:32 raspberrypi dhcpcd[387]: eth0: waiting for carrier
Jul 31 13:40:32 raspberrypi dhcpcd[387]: wlan0: waiting for carrier
Jul 31 13:40:32 raspberrypi dhcpcd[387]: wlan0: carrier acquired
Jul 31 13:40:32 raspberrypi dhcpcd[387]: DUID 00:01:00:01:26:60:d3:cc:74:da:38:28:a7:36
Jul 31 13:40:32 raspberrypi dhcpcd[387]: wlan0: IAID 38:28:a7:36
Jul 31 13:40:32 raspberrypi dhcpcd[387]: wlan0: adding address fe80::356a:5329:7b56:9e77
Jul 31 13:40:32 raspberrypi avahi-daemon[329]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::356a:5329:7b56:9e77.
Jul 31 13:40:32 raspberrypi dhcpcd[387]: wlan0: carrier lost
Jul 31 13:40:32 raspberrypi avahi-daemon[329]: New relevant interface wlan0.IPv6 for mDNS.
Jul 31 13:40:32 raspberrypi avahi-daemon[329]: Registering new address record for fe80::356a:5329:7b56:9e77 on wlan0.*.
Jul 31 13:40:32 raspberrypi dhcpcd[387]: wlan0: deleting address fe80::356a:5329:7b56:9e77
Jul 31 13:40:32 raspberrypi avahi-daemon[329]: Withdrawing address record for fe80::356a:5329:7b56:9e77 on wlan0.
Jul 31 13:40:32 raspberrypi avahi-daemon[329]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::356a:5329:7b56:9e77.
Jul 31 13:40:32 raspberrypi avahi-daemon[329]: Interface wlan0.IPv6 no longer relevant for mDNS.
Jul 31 13:40:33 raspberrypi kernel: [   17.520636] wlan0: authenticate with c4:ad:34:32:a3:3f
Jul 31 13:40:33 raspberrypi kernel: [   17.555711] wlan0: send auth to c4:ad:34:32:a3:3f (try 1/3)
Jul 31 13:40:33 raspberrypi kernel: [   17.557766] wlan0: authenticated
Jul 31 13:40:33 raspberrypi kernel: [   17.567725] wlan0: associate with c4:ad:34:32:a3:3f (try 1/3)
Jul 31 13:40:33 raspberrypi kernel: [   17.573031] wlan0: RX AssocResp from c4:ad:34:32:a3:3f (capab=0x431 status=0 aid=4)
Jul 31 13:40:33 raspberrypi kernel: [   17.679734] wlan0: associated
Jul 31 13:40:33 raspberrypi kernel: [   17.895281] cryptd: max_cpu_qlen set to 1000
Jul 31 13:40:34 raspberrypi dhcpcd[387]: wlan0: carrier acquired
Jul 31 13:40:34 raspberrypi kernel: [   18.010843] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jul 31 13:40:34 raspberrypi dhcpcd[387]: wlan0: connected to Access Point `502bs'
Jul 31 13:40:34 raspberrypi dhcpcd[387]: wlan0: IAID 38:28:a7:36
Jul 31 13:40:34 raspberrypi dhcpcd[387]: wlan0: adding address fe80::bc5e:766b:b67d:fcd9
Jul 31 13:40:34 raspberrypi avahi-daemon[329]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::bc5e:766b:b67d:fcd9.
Jul 31 13:40:34 raspberrypi avahi-daemon[329]: New relevant interface wlan0.IPv6 for mDNS.
Jul 31 13:40:34 raspberrypi avahi-daemon[329]: Registering new address record for fe80::bc5e:766b:b67d:fcd9 on wlan0.*.
Jul 31 13:40:34 raspberrypi dhcpcd[387]: wlan0: rebinding lease of <IP_ADDRESS>
Jul 31 13:40:34 raspberrypi systemd[1]: Started Lighttpd Daemon.
Jul 31 13:40:35 raspberrypi dhcpcd[387]: wlan0: soliciting an IPv6 router
Jul 31 13:40:35 raspberrypi dhcpcd[387]: wlan0: probing address <IP_ADDRESS>/24
Jul 31 13:40:37 raspberrypi exim4[416]: Starting MTA: exim4.
Jul 31 13:40:37 raspberrypi systemd[1]: Started LSB: exim Mail Transport Agent.
Jul 31 13:40:38 raspberrypi systemd[1]: Created slice User Slice of UID 1000.
Jul 31 13:40:38 raspberrypi systemd[1]: Starting User Runtime Directory /run/user/1000...
Jul 31 13:40:38 raspberrypi daemon_rfid_reader.py[413]: 2020-07-31 13:40:38,532 - root - INFO - Dir_PATH: /home/pi/RPi-Jukebox-RFID/scripts
Jul 31 13:40:38 raspberrypi systemd[1]: Started User Runtime Directory /run/user/1000.
Jul 31 13:40:38 raspberrypi systemd[1]: Starting User Manager for UID 1000...
Jul 31 13:40:39 raspberrypi systemd[803]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jul 31 13:40:39 raspberrypi systemd[803]: Starting D-Bus User Message Bus Socket.
Jul 31 13:40:39 raspberrypi systemd[803]: Reached target Paths.
Jul 31 13:40:39 raspberrypi systemd[803]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Jul 31 13:40:39 raspberrypi systemd[803]: Listening on GnuPG network certificate management daemon.
Jul 31 13:40:39 raspberrypi systemd[803]: Listening on GnuPG cryptographic agent and passphrase cache.
Jul 31 13:40:39 raspberrypi systemd[803]: Reached target Timers.
Jul 31 13:40:39 raspberrypi systemd[803]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Jul 31 13:40:39 raspberrypi systemd[803]: Listening on D-Bus User Message Bus Socket.
Jul 31 13:40:39 raspberrypi systemd[803]: Reached target Sockets.
Jul 31 13:40:39 raspberrypi systemd[803]: Reached target Basic System.
Jul 31 13:40:39 raspberrypi systemd[1]: Started User Manager for UID 1000.
Jul 31 13:40:39 raspberrypi systemd[803]: Starting Music Player Daemon...
Jul 31 13:40:39 raspberrypi systemd[1]: Started Session c1 of user pi.
Jul 31 13:40:39 raspberrypi dhcpcd[387]: wlan0: leased <IP_ADDRESS> for 60000 seconds
Jul 31 13:40:39 raspberrypi avahi-daemon[329]: Joining mDNS multicast group on interface wlan0.IPv4 with address <IP_ADDRESS>.
Jul 31 13:40:39 raspberrypi avahi-daemon[329]: New relevant interface wlan0.IPv4 for mDNS.
Jul 31 13:40:39 raspberrypi avahi-daemon[329]: Registering new address record for <IP_ADDRESS> on wlan0.IPv4.
Jul 31 13:40:39 raspberrypi dhcpcd[387]: wlan0: adding route to <IP_ADDRESS>/24
Jul 31 13:40:39 raspberrypi dhcpcd[387]: wlan0: adding default route via <IP_ADDRESS>
Jul 31 13:40:42 raspberrypi mpd[820]: exception: failed to open log file "/var/log/mpd/mpd.log" (config line 40): Permission denied
Jul 31 13:40:42 raspberrypi systemd[1]: Started Music Player Daemon.
Jul 31 13:40:42 raspberrypi systemd[1]: Starting Phoniebox Startup...
Jul 31 13:40:42 raspberrypi bash[879]: AUDIOFOLDERSPATH="/home/pi/RPi-Jukebox-RFID/shared/audiofolders"
Jul 31 13:40:42 raspberrypi bash[879]: PLAYLISTSFOLDERPATH="/home/pi/RPi-Jukebox-RFID/playlists"
Jul 31 13:40:42 raspberrypi bash[879]: SECONDSWIPE="RESTART"
Jul 31 13:40:42 raspberrypi bash[879]: AUDIOIFACENAME="Headphone"
Jul 31 13:40:42 raspberrypi bash[879]: AUDIOVOLCHANGESTEP="3"
Jul 31 13:40:42 raspberrypi bash[879]: AUDIOVOLMAXLIMIT="100"
Jul 31 13:40:42 raspberrypi bash[879]: AUDIOVOLMINLIMIT="1"
Jul 31 13:40:42 raspberrypi bash[879]: AUDIOVOLSTARTUP="0"
Jul 31 13:40:42 raspberrypi bash[879]: VOLCHANGEIDLE="TRUE"
Jul 31 13:40:42 raspberrypi bash[879]: IDLETIMESHUTDOWN="0"
Jul 31 13:40:42 raspberrypi bash[879]: SHOWCOVER="ON"
Jul 31 13:40:42 raspberrypi bash[879]: READWLANIPYN="OFF"
Jul 31 13:40:42 raspberrypi bash[879]: EDITION="classic"
Jul 31 13:40:42 raspberrypi bash[879]: LANG="en-UK"
Jul 31 13:40:42 raspberrypi bash[879]: VERSION="2.0 - ed888da - master"
Jul 31 13:40:42 raspberrypi bash[879]: 0
Jul 31 13:40:42 raspberrypi systemd[803]: mpd.service: Main process exited, code=exited, status=1/FAILURE
Jul 31 13:40:42 raspberrypi systemd[803]: mpd.service: Failed with result 'exit-code'.
Jul 31 13:40:42 raspberrypi systemd[803]: Failed to start Music Player Daemon.
Jul 31 13:40:42 raspberrypi systemd[803]: Reached target Default.
Jul 31 13:40:42 raspberrypi systemd[803]: Startup finished in 4.189s.
Jul 31 13:40:43 raspberrypi systemd[1]: Started Samba NMB Daemon.
Jul 31 13:40:43 raspberrypi systemd[1]: Starting Samba SMB Daemon...
Jul 31 13:40:44 raspberrypi systemd[1]: Started Samba SMB Daemon.
Jul 31 13:40:45 raspberrypi bash[879]: High Performance MPEG 1.0/2.0/2.5 Audio Player for Layers 1, 2 and 3
Jul 31 13:40:45 raspberrypi bash[879]: #011version 1.25.10; written and copyright by Michael Hipp and others
Jul 31 13:40:45 raspberrypi bash[879]: #011free software (LGPL) without any warranty but with best wishes
Jul 31 13:40:45 raspberrypi bash[879]: Directory: /home/pi/RPi-Jukebox-RFID/shared/
Jul 31 13:40:45 raspberrypi bash[879]: Playing MPEG stream 1 of 1: startupsound.mp3 ...
Jul 31 13:40:45 raspberrypi bash[879]: MPEG 1.0 L III cbr64 44100 j-s
Jul 31 13:40:45 raspberrypi bash[879]: Artist:  Phoniebox
Jul 31 13:40:47 raspberrypi dhcpcd[387]: wlan0: no IPv6 Routers available
Jul 31 13:40:49 raspberrypi bash[879]: [0:04] Decoding of startupsound.mp3 finished.
Jul 31 13:40:49 raspberrypi systemd[1]: Started Phoniebox Startup.
Jul 31 13:40:58 raspberrypi systemd[1]: systemd-fsckd.service: Succeeded.
Jul 31 17:00:11 raspberrypi systemd-timesyncd[283]: Synchronized to time server for the first time <IP_ADDRESS>:123 (2.debian.pool.ntp.org).
Jul 31 17:00:11 raspberrypi systemd[1]: Starting Clean php session files...
Jul 31 17:00:12 raspberrypi systemd[1]: phpsessionclean.service: Succeeded.
Jul 31 17:00:12 raspberrypi systemd[1]: Started Clean php session files.
Jul 31 17:00:44 raspberrypi systemd[1]: phoniebox-idle-watchdog.service: Succeeded.
Jul 31 17:01:04 raspberrypi systemd[1]: dev-serial1.device: Job dev-serial1.device/start timed out.
Jul 31 17:01:04 raspberrypi systemd[1]: Timed out waiting for device /dev/serial1.
Jul 31 17:01:04 raspberrypi systemd[1]: Dependency failed for Configure Bluetooth Modems connected by UART.
Jul 31 17:01:04 raspberrypi systemd[1]: hciuart.service: Job hciuart.service/start failed with result 'dependency'.
Jul 31 17:01:04 raspberrypi systemd[1]: dev-serial1.device: Job dev-serial1.device/start failed with result 'timeout'.
Jul 31 17:01:04 raspberrypi systemd[1]: Reached target Multi-User System.
Jul 31 17:01:04 raspberrypi systemd[1]: Starting Update UTMP about System Runlevel Changes...
Jul 31 17:01:04 raspberrypi systemd[1]: systemd-update-utmp-runlevel.service: Succeeded.
Jul 31 17:01:04 raspberrypi systemd[1]: Started Update UTMP about System Runlevel Changes.
Jul 31 17:01:04 raspberrypi systemd[1]: Startup finished in 4.552s (kernel) + 1min 32.381s (userspace) = 1min 36.933s.
Jul 31 17:02:39 raspberrypi systemd[1]: Started Session c2 of user pi.
Jul 31 17:09:01 raspberrypi CRON[1040]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
Jul 31 17:09:28 raspberrypi systemd[1]: Starting Clean php session files...
Jul 31 17:09:28 raspberrypi systemd[1]: phpsessionclean.service: Succeeded.
Jul 31 17:09:28 raspberrypi systemd[1]: Started Clean php session files.
Jul 31 17:14:56 raspberrypi systemd[1]: Starting Cleanup of Temporary Directories...
Jul 31 17:14:56 raspberrypi systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Jul 31 17:14:56 raspberrypi systemd[1]: Started Cleanup of Temporary Directories.
Jul 31 17:17:01 raspberrypi CRON[1103]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

Output while configuring the card reader:

config card  1
config card  2
config card  3
download manual  www.jatsecuritz.com-easzmfßim.html
format description
1 ß 28  data format
e    qwertz kezboard
f    ayertz kezboard
h    quertz kezboard
config reader ...
when demand format is appeared plug off reader
1 8hß10dße
2 2hß3dß4hß5dße
3 8hße
4 6hße
5 6hß8dße
6 6hß10dße
7 4hß5dß4hß5dße
8 8hß10d
9 2hß3dß4hß5d
10 8h
11 6h
12 6hß8d
13 6hß10d
14 4hß5dß4hß5d
15 8hß10dßrße
16 2hß3dß4hß5dßrße
17 8hßrße
18 6hßrße
19 6hß8dßrße
20 6hß10dßrße
21 4hß5dß4hß5dßrße
22 8hß10dßr
23 2hß3dß4hß5dßr
24 8hßr
25 6hßr
26 6hß8dßr
27 6hß10dßr
28 4hß5dß4hß5dßr
29 e

I set it to Format 1, and voila, it worked. This means out of the box not all KKmoon Readers will work and you have to follow the instructions on your configuration card that comes with the Reader. For a Small recap, you have to (First read all the points and make sure you understand them):

Open some Text-Editor (Notepad, MCEdit, Nano, ... Can be run in different OS Versions like Windows or on the Raspberry)
Swipe your Configuration Card 3 Times in a row. It will display "config card 1", "config card 2" and "config card 3"
You will see the Format Text running through. If you want to set it to Format 1 (as I did), you have to unplug your reader when you see the Line "1 8hß10dße"
Plugin your Reader (beep), then Plug it out again (less than 2 Seconds!)
Plugin your Reader (beep), then Plug it out again (less than 2 Seconds!)
Plugin your Reader (beep), then Plug it out again (less than 2 Seconds!)
Plugin your Reader. It should now be Configured as Format 1. (yes, you have to unplug it 3 times)

Hi @BStramke
thanks for the input. You solved it and closed it fast :) great. I still took the information and added it to the wiki. Is that ok?:
https://github.com/MiczFlor/RPi-Jukebox-RFID/wiki/RFID_Reader_KKMOON_Info

Yep, its fine ;-)


[BUG] Can't backup vm if vm is stopped

Describe the bug

To Reproduce
Steps to reproduce the behavior:

stop a vm
check if vm can backup

Expected behavior

also can backup vm when vm is stopped
Log

Environment:

Harvester ISO version:
Installation Mode: ISO/app-mode
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630):

Additional context
Add any other context about the problem here.

Validation in version master-0008ce84-head
Step

Create a vm successfully and write some data to the vm

stop  vm

check if vm can backup

Restore vm using a backup of stop vm


Don't log input text in automation as it can contain PII

You can ignore the common failure for this.

You can ignore the common failure for this.


Cannot input text when frame docked at top right corner

Hi
First, thanks for your great work !
I met the following issue which is new after recent update (just updated with BRAT).
When tab is on main frame, all is fine, but when I the tab is at top right corner I have no access to the text input form.

Hope it's sufficient to investigate

Hello, sorry about that. I think that happens because I set a fixed size for the conversation view. If you close the calendar below and let Weaver occupy the full height of the screen, then the input box should be displayed. I am going to look into it and solve that in the next update.