Perf regression on crypto.verify

On NodeJS 16.x, crypto.verify made 30k op/s (ref)
But on NodeJS 18.x, crypto.verify downgrade to 6~7k op/s (ref).
I initially discover this on this pr: https://github.com/RafaelGSS/nodejs-bench-operations/pull/31, I already did an initial investigation of the cause, which currently points to validationFunction, but I think we should look on V8 side to see if something change.
It's probable that this slowdown affects crypto.sign too, but I didn't have time yet to benchmark.

Richard Lau gave some hints to see OpenSSL move from 1.1.1 to 3.0.x, if investigation of the JS code didn't bring any hint about the issue, I think it's worth taking a look at this.

That would be my first guess as well. You could build from source before and after https://github.com/nodejs/node/pull/38512 and run the benchmark with the respective binaries to test this hypothesis. Or simply use v17.0.0-nightly2021100135dc3861cd and v18.0.0-nightly2021110186099a375a representing the commit range 35dc3861cd...86099a375a for a less accurate but probably still helpful result.

Hey, I didn't have time to build the nodejs with OpenSSL 1.1 but @NewEraCracker did and it seems to improve the performance accords https://github.com/nodejs/performance/issues/84#issuecomment-1559566272.
Is this problem likely to be related to OpenSSL, if so is there anything that can be done?

Besides fixing it upstream. I don't think so.

I dug into this a little bit on the surface. For testing I used an M1 MacBook Pro, node v16.20.0 and v18.16.0 installed via nvm and the benchmark scripts from https://github.com/nodejs/node/pull/48267
These benchmarks test the oneshot crypto.sign and crypto.verify operations with

different asymmetric key types (rsa, ec, ed25519)
keys passed in different formats (pem, der, jwk, KeyObject and to ensure that its use dont suffer from mutexes also unique KeyObject)
different modes (synchronous, asynchronous callback invoked serially, asynchronous parallel invoked parallel)

I can definitely see a regression across the board for all sign/verify operation throughputs between v16 and v18.
What is interesting though is that the severe regression (e.g. rsa verify 28k ops/s down to 7k ops/s) is only present when the keys are passed as pem or der, when passed as jwk or a KeyObject a much less severe regression is observed.
IIRC the two severely impacted key formats have their own unique code path in ManagedEVPPKey::GetPrivateKeyFromJs ^1 so that to me seems like a prime suspect to look into. A quick blame shows https://github.com/nodejs/node/pull/43202 fixing memory leaks and refactoring to use ByteSource, not sure how relevant to this is but I'll leave that to the next person to judge.
cc @tniessen

My results
// 2048 bit RSASSA-PKCS1-v1_5
keyFormat="pem" mode="sync"
  28,446 down to 7,150
keyFormat="der" mode="sync"
  31,341 down to 7,329
keyFormat="jwk" mode="sync"
  31,043 down to 26,775
keyFormat="keyObject" mode="sync"
  47,087 down to 43,101

keyFormat="pem" mode="async"
  23,111 down to 6,681
keyFormat="der" mode="async"
  23,805 down to 6,885
keyFormat="jwk" mode="async"
  23,562 down to 20,788
keyFormat="keyObject" mode="async"
  34,515 down to 28,409

keyFormat="pem" mode="async-parallel"
  83,863 down to 8,793
keyFormat="der" mode="async-parallel"
  123,438 down to 9,174
keyFormat="jwk" mode="async-parallel"
  124,582 down to 99,207
keyFormat="keyObject" mode="async-parallel"
  167,227 down to 126,255
keyFormat="keyObject-unique" mode="async-parallel"
  121,421 down to 104,601

// ECDSA P-256 w/ SHA-2
keyFormat="pem" mode="sync"
  11,258 down to 5,676
keyFormat="der" mode="sync"
  11,499 down to 5,739
keyFormat="jwk" mode="sync"
  7,187 down to 6,040
keyFormat="keyObject" mode="sync"
  13,842 down to 13,369

keyFormat="pem" mode="async"
  9,878 down to 5,306
keyFormat="der" mode="async"
  10,427 down to 5,466
keyFormat="jwk" mode="async"
  6,782 down to 5,613
keyFormat="keyObject" mode="async"
  11,999 down to 11,519

keyFormat="pem" mode="async-parallel"
  40,404 down to 9,209
keyFormat="der" mode="async-parallel"
  53,853 down to 9,520
keyFormat="jwk" mode="async-parallel"
  14,094 down to 13,161
keyFormat="keyObject" mode="async-parallel"
  52,952 down to 50,455
keyFormat="keyObject-unique" mode="async-parallel"
  53,710 down to 50,282

// Ed25519
keyFormat="pem" mode="sync"
  8,914 down to 5,722
keyFormat="der" mode="sync"
  8,980 down to 5,725
keyFormat="jwk" mode="sync"
  9,078 down to 8,592
keyFormat="keyObject" mode="sync"
  9,379 down to 9,191

keyFormat="pem" mode="async"
  8,467 down to 5,310
keyFormat="der" mode="async"
  8,373 down to 5,260
keyFormat="jwk" mode="async"
  8,195 down to 8,043
keyFormat="keyObject" mode="async"
  8,510 down to 8,311

keyFormat="pem" mode="async-parallel"
  36,037 down to 13,940
keyFormat="der" mode="async-parallel"
  36,288 down to 14,240
keyFormat="jwk" mode="async-parallel"
  35,612 down to 34,852
keyFormat="keyObject" mode="async-parallel"
  35,907 down to 34,888
keyFormat="keyObject-unique" mode="async-parallel"
  35,617 down to 35,398

@panva Did you have a chance to test 18.x against OpenSSL 1.1.1? So far, we have suspected that the difference in performance is due to the different OpenSSL versions.

@panva Did you have a chance to test 18.x against OpenSSL 1.1.1? So far, we have suspected that the difference in performance is due to the different OpenSSL versions.

I have built v18.x with OpenSSL 1.1.1 now, it (OpenSSL 3.x) is indeed the problem at hand for the slowdowns in both pem/der parsing and sign/verify.

ChatGPT did, after massaging the data a bit. The values seem accurate.
There is a noticeable performance drop when moving from OpenSSL 1.1.1 to 3.0.x across all operations. However, there is a small improvement when upgrading from 3.0.x to 3.1.x.
Verify

Version
Average
Minimum
Maximum
Drop from 1.1.1 (%)

v18.16.0 w/ OpenSSL 1.1.1
45,424.446015
9,465.267565
198,067.181219
-

v18.16.0 w/ OpenSSL 3.0.x
14,146.405165
6,960.496267
158,281.067606
68.89%

v18.16.0 w/ OpenSSL 3.1.x
19,824.438734
5,727.334480
173,185.153807
56.38%

Sign

Version
Average
Minimum
Maximum
Drop from 1.1.1 (%)

v18.16.0 w/ OpenSSL 1.1.1
32,115.690019
1,200.833137
169,177.285784
-

v18.16.0 w/ OpenSSL 3.0.x
6,308.925663
954.240964
127,460.919845
80.36%

v18.16.0 w/ OpenSSL 3.1.x
13,688.469062
1,139.313552
141,697.410281
57.37%

createPublicKey / createPrivateKey

Version
Average
Minimum
Maximum
Drop from 1.1.1 (%)

v18.16.0 w/ OpenSSL 1.1.1
108,089.352566
19,092.167438
366,021.090867
-

v18.16.0 w/ OpenSSL 3.0.x
22,107.414041
3,837.090564
315,391.151260
79.57%

v18.16.0 w/ OpenSSL 3.1.x
25,450.048696
10,779.332247
292,761.472590
76.48%

No warranties express or implied.

Maybe we have to upgrade to OpenSSL 3.1?

@Uzlopak That's not an option given the current OpenSSL release strategy.

@tniessen
Then we have to wait for OpenSSL 3.2 to land.

In this case, there are 96 comparisons, you can thus expect the following amount of false-positive results:
  4.80 false positives, when considering a   5% risk acceptance (*, **, ***),
  0.96 false positives, when considering a   1% risk acceptance (**, ***),
  0.10 false positives, when considering a 0.1% risk acceptance (***)

Maybe we should consider to use openssl 3.1, even though that it is only supported till March 2025
@mcollina
@anonrig

Users can already dynamically link against OpenSSL 3.1 if they wish. If we upgrade the statically linked version of OpenSSL to 3.1, then we will be forced to again upgrade (or downgrade) OpenSSL on existing Node.js release lines. I don't know if the OpenSSL team has released information about the 3.2 end of life date, or about backward compatibility of future versions.

I see that openssl released today v3.2.0 beta. Maybe in a month we have stable 3.2.0. Is upgrading to openssl 3.2.0 an acceptable?

Users can already dynamically link against OpenSSL 3.1 if they wish. If we upgrade the statically linked version of OpenSSL to 3.1, then we will be forced to again upgrade (or downgrade) OpenSSL on existing Node.js release lines. I don't know if the OpenSSL team has released information about the 3.2 end of life date, or about backward compatibility of future versions.

AFAIK nothing has been stated yet about 3.2, or what the next LTS after 3.0 will be. https://www.openssl.org/policies/releasestrat.html was last updated in March. They have stated that OpenSSL now follows semver.
For Node.js the current plan is to stick to OpenSSL 3.0 for Node.js 20. We'll have a decision to make next year about what we're going to do for Node.js 22, which has an End-of-Life after the end of support for OpenSSL 3.0.

My understading of OpenSSL is that minor are not ABI stable. Has anything changed on that front? In other terms, we cannot update OpenSSL because we risk breaking addons.

@mcollina
https://www.openssl.org/policies/general/versioning-policy.html
For minor:

A minor release is indicated by changing the second number of the version. A minor release can, and generally will, introduce new features. However both the API and ABI will be preserved.

The same with Patch Releases.

A patch release is indicated by changing the final number of the version. A patch release will only contain bug and security fixes. Both the API and ABI will remain compatible across patch releases.

So according to openssl they will have a stable ABI.

Then if a API/ABI compatible release come out that has a LTS date after our LTS deadline, we can certainly migrate.

I'd like to discuss adding an important topic to the upcoming TSC agenda: our plan for upgrading OpenSSL.
Here's why it's important:
If we don't upgrade OpenSSL, our crypto library will remain slow, and we won't get the new features of the 3.x versions. For example, version 3.2 plans to add argon2, but we won't get it because OpenSSL says they won't add new functionality to existing minor versions.
The OpenSSL developers say that for versions 3 and up, they'll keep the ABI stable when they update minor or patch versions. So, in theory, it shouldn't cause problems for our users.
The only good reason to stick with OpenSSL 3.0 is that it's supposed to be supported for five years as LTS, while 3.x versions only get two years of support. OpenSSL 3.0's end-of-life is in September 2026, while 3.1's is in March 2025. If OpenSSL 3.2 comes out in December 2023, it'll be unsupported by December 2025.
Node 18's security support ends on April 30, 2025, which works fine with OpenSSL 3.2. But Node 20's security support ends on April 30, 2026, which is a problem. We'd have to use OpenSSL 3.0 since the time window for OpenSSL 3.2 is too short and downgrading from OpenSSL 3.2 to 3.0 means removal of additional functionality and thus breaking userland. However, if OpenSSL 3.2 comes out on or after April 30, 2024, we can upgrade to it.
If we release Node 22 with OpenSSL 3.0 and set the security support to end on April 30, 2027, we'll run into the same issue as with Node 16 because OpenSSL 3.0 becomes unsupported in September 2026.
So, the risk here is that our security support might extend beyond the end-of-life of an OpenSSL version with the same ABI as 3.0. For Node 22, we just can hope that OpenSSL releases a 3.x version on or after April 30, 2025, or they declare a 3.x or 4.0 version as LTS before April 30, 2024.
This situation isn't ideal because it ties our support to OpenSSL. But it's something we need to discuss. Maybe we should talk to the OpenSSL developers and work out an agreement to make sure our security support aligns with our security end-of-life. Maybe we have to accept that at some point we need to upgrade OpenSSL with breaking ABI and addons would break and need to adapt accordingly.
My personal preference is to upgrade OpenSSL and force addons to adapt accordingly, as they would run into the same OpenSSL support issues as node core would do.

@nodejs/tsc
I'd like to discuss adding an important topic to the upcoming TSC agenda: our plan for upgrading OpenSSL.
Here's why it's important:
If we don't upgrade OpenSSL, our crypto library will remain slow, and we won't get the new features of the 3.x versions. For example, version 3.2 plans to add argon2, but we won't get it because OpenSSL says they won't add new functionality to existing minor versions.
The OpenSSL developers say that for versions 3 and up, they'll keep the ABI stable when they update minor or patch versions. So, in theory, it shouldn't cause problems for our users.
The only good reason to stick with OpenSSL 3.0 is that it's supposed to be supported for five years as LTS, while 3.x versions only get two years of support. OpenSSL 3.0's end-of-life is in September 2026, while 3.1's is in March 2025. If OpenSSL 3.2 comes out in December 2023, it'll be unsupported by December 2025.
Node 18's security support ends on April 30, 2025, which works fine with OpenSSL 3.2. But Node 20's security support ends on April 30, 2026, which is a problem. We'd have to use OpenSSL 3.0 since the time window for OpenSSL 3.2 is too short and downgrading from OpenSSL 3.2 to 3.0 means removal of additional functionality and thus breaking userland. However, if OpenSSL 3.2 comes out on or after April 30, 2024, we can upgrade to it.
If we release Node 22 with OpenSSL 3.0 and set the security support to end on April 30, 2027, we'll run into the same issue as with Node 16 because OpenSSL 3.0 becomes unsupported in September 2026.
So, the risk here is that our security support might extend beyond the end-of-life of an OpenSSL version with the same ABI as 3.0. For Node 22, we just can hope that OpenSSL releases a 3.x version on or after April 30, 2025, or they declare a 3.x or 4.0 version as LTS before April 30, 2024.
This situation isn't ideal because it ties our support to OpenSSL. But it's something we need to discuss. Maybe we should talk to the OpenSSL developers and work out an agreement to make sure our security support aligns with our security end-of-life. Maybe we have to accept that at some point we need to upgrade OpenSSL with breaking ABI and addons would break and need to adapt accordingly.
My personal preference is to upgrade OpenSSL and force addons to adapt accordingly, as they would run into the same OpenSSL support issues as node core would do.

One elephant in the room is that Node.js doesn't actually bundle openssl -- it bundles the quic fork of openssl from https://github.com/quictls/openssl. While they have a fork for 3.1, there appear to be issues for 3.2 and later: https://github.com/quictls/openssl/issues/138.
We're on that fork because it was a prerequisite for http3/quic support: https://github.com/nodejs/node/issues/38478

I'd like add the following topic to the upcoming TSC agenda: our plan for upgrading OpenSSL.

Why does that need to be on the TSC agenda? GitHub discussions among collaborators and other community members should be the default channel for any decision-making process.

This situation isn't ideal because it ties our support to OpenSSL. But it's something we need to discuss.

That has always been the case, and we've regularly discussed how to deal with OpenSSL's release strategy.

Maybe we should talk to the OpenSSL developers and work out an agreement to make sure our security support aligns with our security end-of-life.

Let's be realistic. Node.js is one of thousands of dependents of OpenSSL and probably not even among the most important ones. We cannot reasonably ask OpenSSL maintainers to change their release schedule for Node.js, nor can we ask them for commercial support that extends beyond the official end of life. We can adjust the release schedule of Node.js to align with OpenSSL if necessary for security reasons, but we try to avoid that.

If we don't upgrade OpenSSL, our crypto library will remain slow, and we won't get the new features of the 3.x versions
(...)
Maybe we have to accept that at some point we need to upgrade OpenSSL with breaking ABI and addons would break and need to adapt accordingly.
My personal preference is to upgrade OpenSSL and force addons to adapt accordingly

From my point or view, a reasonable list of priorities is: security, then reliability/stability, and lastly features/performance. I don't think we should sacrifice the former categories for the latter.
As @richardlau mentions, one complication is that we use a fork of OpenSSL.
And let's not forget about embedders that link against BoringSSL either (e.g., Electron). We don't want to make things too difficult for them either.

What's the reason for preferring OpenSSL over BoringSSL?

Doesn't this deserve an issue in nodejs/node? Neither 3.1 nor 3.2 (likely?) solves the regression. The discussion is important but doesn't belong here.

What's the reason for preferring OpenSSL over BoringSSL?

BoringSSL does not offer LTS.

Doesn't the openssl version deserve an issue in nodejs/node? Neither 3.1 nor 3.2 (likely?) solves the regression at hand for which this issue is. The discussion is important but doesn't belong here.

@panva I'm lost, my reading of https://github.com/nodejs/performance/issues/72#issuecomment-1781211049 was that at least v3.1 mitigated the problem.
Has the root cause of the issue been identified?

@panva I'm lost, my reading of #72 (comment) was that at least v3.1 mitigated the problem.

Have a look at 1.1.1w vs 3.1.3 please. It is still far from or close to mitigated for most common scenarios.

While they have a fork for 3.1, there appear to be issues for 3.2 and later: https://github.com/quictls/openssl/issues/138.

From the mentioned issue:

Note to projects/packagers that depend on this: this is going to be an issue with 3.3 and later. Weigh in please: we know you exist but we don't hear from you!

I'm guessing feedback should be left there too on how to move forward.

Others have deemed OpenSSL v3 as not production ready, because it has this super bad performance regression. E.g. microsoft implemented for this reason msquic based on OpenSSL 1 and 3, which they use for their azure instances.
Also to what @panva wrote:
Yes, OpenSSL 3.1 does not resolve the performance issue to be back to the performance level of OpenSSL 1, but it improves the performance issues significantly.

Others have deemed OpenSSL v3 as not production ready, because it has this super bad performance regression. E.g. microsoft implemented for this reason msquic based on OpenSSL 1 and 3, which they use for their azure instances.

We had no choice but to use OpenSSL 3.x because 1.1.1 is now EOL. We will continue to support linking with 1.1.1 so long as the commercial extended support OpenSSL offers still covers 1.1.1 security releases (privately distributed).


reformat ztests with gopkg.in/yaml.v3

Lay groundwork for automatic transformations on ztests by reformatting
them with gopkg.in/yaml.v3.
Depends on #2909.

Maybe add a lint step that runs this?

After go-yaml/yaml#738 is merged.  Without that, a number of multiline literals are converted to double-quoted style for no good reason, making them hard to read.


why you removed objaverse/xl/thingiverse.py？

It makes scripts/rendering/main.py can't work.

Have you found another way to fix it yet?

right now only objaverse 0.1.5 works, the code base is clearly lack of maintainance.

right now only objaverse 0.1.5 works, the code base is clearly lack of maintainance.

Is rendering with blender also works? I tried 0.1.5 and it said
Traceback (most recent call last):
  File "/Projects/Objaverse/objaverse-xl-0.1.5/scripts/rendering/main.py", line 20, in <module>
    from objaverse import ObjaverseDownloader
ImportError: cannot import name 'ObjaverseDownloader' from 'objaverse' (/Projects/Objaverse/objaverse-xl-0.1.5/objaverse/__init__.py)

I gave up using this repo to render objects, we need to wait for the author to update.

The thingiverse.py code still exists in https://huggingface.co/datasets/allenai/objaverse-xl/blob/08bea20593cb4dccd23887b2256f3cd9d226a3e4/objaverse_xl/thingiverse.py


Global menu

Request from @EugeneMcD to make sure the global nav bar pulls the left hand menu bar items from Wordpress installation.
It was proposed we put a hack into the current file so that we can inject whatever links we want to appear on the right hand side.
Will assign to myself as everyone else has many tasks.

We investigated this while working on our common menu that we rolled out in August, however unfortunately WordPress doesn't have the necessary REST API to do this. There are plugin options, but they aren't optimal (either requiring authentication, or a seldom maintained plugin on top of a big plugin we wouldn't utilise). While it would be nice to have, it's not really priority.
I'll leave this open, since it is something we'd definitely like to do, just wanted to add that info.


This command needs examples

An example would be really helpful for this command.  Multiple examples would be better.  I assume I need to provide an http url for the public repo but its not clear how the service connection is used.  Is that used to import a private repository?  Do I also set requires-authorization in that case to true?  What is the username format if the repo is private?

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

ID: 82ec496e-0aa8-1dcb-93cb-584fa83fdc0d
Version Independent ID: 9151bc57-0eac-bf3a-9110-17908d62eeb6
Content: az repos import
Content Source: latest/docs-ref-autogen/ext/azure-devops/repos/import.yml
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

devops

This will be fixed once the PR is merged.


match quick pick styling

given that a screen reader will have to go line by line, I wonder if we should go with a larger width 🤔 . We can get feedback and for now match the styling of the quickpick, though they have very different functions/content so should be considered separately.
fixes #188838
fixes #186520
https://github.com/microsoft/vscode/assets/29464607/dcf0a381-f706-4853-bc2f-b3eacbcc6d3e

Nice! :)


Add async API for NIO

Includes NIO vectored IO calls.

Since I got no objections, I merged the code.


ui: currently selected items are no longer being retained across browser navigation

@aboodman introduced a feature to retain the current selected items that doesn't seem to be working right now.
Use case:

Select 3 items
Click on a fourth item to make sure it's the one you want
Click the back button
Note the previously selected items are no longer selected

Maybe it was lost with the addition of the 'around' query?

Note for future debugging:
functionality introduced here: 3683a15e05a0b4f658fb9b7ac349ed6353b256a7

Looks like it was broken here:
https://github.com/camlistore/camlistore/commit/b19e836c7bf5d8f5489f507e6a0502931593818b#diff-895405ce6e0f79e2b7b0b0884cb0b913R368
this.setSelection_({});

https://camlistore-review.googlesource.com/#/c/5076/

ACK. I'll check it all out later if @aboodman does not get to it. He did warn us that he wanted to test the left/right navigation change more, but we were in a hurry to merge it at the time.

38f16f6e316e63adac9383b208feb319ad2560e1


When wifi connection fails wristband becomes unusable

Whenever I try to connect to an wifi and i cancel the connection the wristband hangs on updating time... And heats up. The only way to stop this is waiting for the battery to discharge or pressing the reset button on the daughter board

Thanks for letting us know about this.
The solution is to add in a timeout as in wristband-wifi.cpp:
void setupWiFi()
{
  WiFiManager wifiManager;
  wifiManager.setAPCallback(configModeCallback);
  wifiManager.setBreakAfterConfig(true);
  wifiManager.setTimeout(2*60);  // added in
  wifiManager.autoConnect("T-Wristband");
}

I have got a development branch in preparation which includes this and additions, such as ability to set a UTC offset or a DST timezone from the wristband. It is easy to add in up to 100 DST timezones in code to show on the watch with just one extra line line in code per DST timezone.
Hope to have the code ready by tomorrow as well as a binary file.
John Heenan


npm doesn't work with node v0.6.6

As the title reads.  Below is th error you receive.
Error: npm doesn't work with node v0.6.6
Required<EMAIL_ADDRESS>|| 0.5
at /Users/chietala/local/lib/node_modules/npm/bin/npm-cli.js:57:23
at Object. (/Users/chietala/local/lib/node_modules/npm/bin/npm-cli.js:77:2)
at Module._compile (module.js:432:26)
at Object..js (module.js:450:10)
at Module.load (module.js:351:31)
at Function._load (module.js:310:12)
at Array.0 (module.js:470:10)
at EventEmitter._tickCallback (node.js:192:40)

update npm.


[Enhancement] remove unnecessary dcheck in dynmaic cache

remove unnecessary dcheck in dynmaic cache, it could happen in remove.
What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.1
[x] 3.0
[ ] 2.5
[ ] 2.4

@Mergifyio backport branch-3.1

@Mergifyio backport branch-3.0


Typo in DataBindingDemo causing NullReferenceException

Line 20 of MainWindow.cs should be
 _listingDataView = (CollectionViewSource) (Resources["ListingDataView"]);

Currently, the resource name is "listingDataView" which gives an error when checking "Show only bargains"

@NielsUll, this issue was fixed in this PR https://github.com/microsoft/WPF-Samples/pull/105. Hence closing the issue.


Document command-line completion installation

This is a draft based on the same doc for docker-compose. It still needs changes, but will get the thing moving.
I updated and commented out the zsh doc, as docker-machine does not seem to have zsh completion scripts.
I'll need help on the available completions, as I merely created this file by copy-paste-update from docker-compose, after figuring out how to install completion for docker-machine on my system.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "patch-1" git@github.com:davidstosik/machine.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

LGTM so we have a place to start adding completion in.

@davidstosik Can you please rebase?

@dgageot Done. I think.

LGTM


Fix skeleton 3d editor's toolbar ui deleted from wrong container

Fixes #82094
The bug comes from node mismatch: In create_editors, editors like animation_hb are added to topmenu_bar but in the destructor they are removed from Node3DEditor::get_singleton() which is the parent of topmenu_bar.

Thank you for quick bug fix :)

Thanks!


Final changes for Fugue and Savage worlds Sheet

I think I have fixed the issues with the last pulls

Oh no!  The merge of The Beast!  :-)

Why did this get reverted?

https://app.roll20.net/forum/post/1710699/savage-worlds-cs-merge-conflicts-guys#post-1713370

oh.. that makes sense. ty

Can anyone tell me what i need to do about this whole merging and syncing thing?  I really dont know whats going on I have three branches, but I dont know what one i need to work on let alone why they dont seem to want to sync.

Roll20/master seems to be behind but it wont sync.

Do I need to be doing anything here?


Use ActiveRecord::Base.connected? to avoid creating unneeded connections

This PR makes use of ActiveRecord::Base.connected? in the inside_transaction method to avoid the needless creation of extra connections to the primary configured DB.

Which database adapter? Which AR version?
As long as I read the code in 5.2.3, open_transactions takes @stack.size which is just an array.
https://github.com/rails/rails/blob/v5.2.3/activerecord/lib/active_record/connection_adapters/abstract/transaction.rb#L263-L265
      def open_transactions
        @stack.size
      end

In any case, inside_transaction? exists to prevent mistakes and I don't think it's a good idea to just remove the feature without assessment for trade-offs. I'd like to hear your thoughts.

For the example posted in the screenshot I am making use of the console script from the repo which uses AR 3.0.0 and Sqlite adapter
In our app environment where we see this same behavior we are using AR 3.2 with the MySQL adapter.

In any case, inside_transaction? exists to prevent mistakes and I don't think it's a good idea to just remove the feature without assessment for trade-offs. I'd like to hear your thoughts.

This change does not remove any functionality from the inside_transaction method, it just does an early return if there are no existing connections established by AR. This prevents the round trip we were seeing the the DB when connections did not yet exist.

@open_transactions is just an instance variable on AR 3.2 too.
https://github.com/rails/rails/blob/3-2-stable/activerecord/lib/active_record/connection_adapters/abstract_adapter.rb
So it's more likely that ActiveRecord::Base.connection is not reusing the pooled connection and causing the connection leak? I'd appreciate if you could track down what exactly is causing the extra query.

This change does not remove any functionality from the inside_transaction method, it just does an early return if there are no existing connections established by AR. This prevents the round trip we were seeing the the DB when connections did not yet exist.

inside_transaction? should run anytime when it's called, and whether connection is established or not doesn't matter.

Hi Kenn, the open_transactions portion of line 28 is not the problem. It is the preceding call to connection which is causing a new DB connection to happen via the connection holder.
In our case, if a thread had not yet used a DB connection, this call would cause the thread to establish a new connection for no reason. I performed a new test of this today using ActiveRecord 5.2.3 and the MySQL2 adapter
I hope this helps

Kenn, have you had a chance to read my last clarification about this?

@kenn

Trying this in https://github.com/kenn/standby/pull/35.


(maint) Constrain ffi to less than 1.9.9

FFI gem 1.9.9 causes ruby to segfault on windows[1]. This is causing
Windows PRs on appveyor to fail, but not in our internal CI, because we
use our rubygems mirror.
This commit is a temporary measure to allow appveyor testing to pass.
Once the upstream issue is resolved, we can remove the constraint.
[1] https://github.com/ffi/ffi/issues/440

First I was like \o and then I was like o/, but then I was like \o/

And then I was like :panda_face:
bundle install --jobs 4 --retry 2 --without development extra

[!] There was an error parsing `Gemfile`: (C:/projects/puppet/ext/project_data.yaml): did not find expected key while parsing a block mapping at line 31 column 7. Bundler cannot continue.

 #  from C:/projects/puppet/Gemfile:74
 #  -------------------------------------------
 #
 >  # vim:filetype=ruby
 #  source ENV['GEM_SOURCE'] || "https://rubygems.org"
 #  -------------------------------------------
Command exited with code 4
appveyor PushArtifact .\spec_order.txt
Error pushing artifact: File not found: C:\projects\puppet\spec_order.txt
Command exited with code 2

sorry, forgot about our yaml-bundler gem dependencies, should be good, assuming travis & appveyor pass:
C:\work\puppet>bundle install --path .bundle
Fetching gem metadata from https://rubygems.org/.......
...
Installing ffi 1.9.8

@Iristyle @ferventcoder appveyor passed, travis is taking a long time....

CLA signed by all contributors.

Upstream fix was merged and new version pushed, closing this

\0/


K8s control plane logs conversion webhook errors

Describe the bug
After upgrading from Ambassador API gateway 1.13 to Emissary-ingress 2.2.2, the control plane logs have started showing the following errors continuously:
E0519 17:40:52.693825      12 cacher.go:419] cacher (*unstructured.Unstructured): unexpected ListAndWatch error: failed to list getambassador.io/v1, Kind=Mapping: conversion webhook for getambassador.io/v2, Kind=Mapping failed: no kind "Mapping" is registered for version "getambassador.io/v1" in scheme "/go/cmd/apiext/main.go:50"; reinitializing...
E0519 17:40:52.538414      12 cacher.go:419] cacher (*unstructured.Unstructured): unexpected ListAndWatch error: failed to list getambassador.io/v1, Kind=AuthService: conversion webhook for getambassador.io/v2, Kind=AuthService failed: no kind "AuthService" is registered for version "getambassador.io/v1" in scheme "/go/cmd/apiext/main.go:50"; reinitializing...
E0519 17:40:52.332153      12 cacher.go:419] cacher (*unstructured.Unstructured): unexpected ListAndWatch error: failed to list getambassador.io/v1, Kind=RateLimitService: conversion webhook for getambassador.io/v2, Kind=RateLimitService failed: no kind "RateLimitService" is registered for version "getambassador.io/v1" in scheme "/go/cmd/apiext/main.go:50"; reinitializing...
E0519 17:40:52.180641      12 cacher.go:419] cacher (*unstructured.Unstructured): unexpected ListAndWatch error: failed to list getambassador.io/v1, Kind=TCPMapping: conversion webhook for getambassador.io/v2, Kind=TCPMapping failed: no kind "TCPMapping" is registered for version "getambassador.io/v1" in scheme "/go/cmd/apiext/main.go:50"; reinitializing...
E0519 17:40:52.147282      12 cacher.go:419] cacher (*unstructured.Unstructured): unexpected ListAndWatch error: failed to list getambassador.io/v1, Kind=TracingService: conversion webhook for getambassador.io/v2, Kind=TracingService failed: no kind "TracingService" is registered for version "getambassador.io/v1" in scheme "/go/cmd/apiext/main.go:50"; reinitializing...
E0519 17:40:51.746911      12 cacher.go:419] cacher (*unstructured.Unstructured): unexpected ListAndWatch error: failed to list getambassador.io/v1, Kind=KubernetesEndpointResolver: conversion webhook for getambassador.io/v2, Kind=KubernetesEndpointResolver failed: no kind "KubernetesEndpointResolver" is registered for version "getambassador.io/v1" in scheme "/go/cmd/apiext/main.go:50"; reinitializing...

Besides the error logs, everything seems to work correctly.
To Reproduce
I don't know how to reproduce this issue
Expected behavior
I expect the control plane logs to not contain errors for getambassador.io/v1 objects.

First, it was a tracingservice version in v1 as an annotation
apiVersion: v1
kind: Service
metadata:
  name: zipkin
  namespace: monitoring
  annotations:
    getambassador.io/config: |
      ---
      apiVersion: ambassador/v1
      kind: TracingService
      name: tracing
      service: zipkin.monitoring:9411
      driver: zipkin
...

We deleted the annotation and applied to the following v2 custom resource 1 year ago:
apiVersion: getambassador.io/v2
kind: TracingService
metadata:
  name: tracing
  namespace: monitoring
spec:
  ambassador_id:
    - internal
    - public
  driver: zipkin
  service: zipkin.monitoring:9411
  tag_headers:
    - :authority
    - :path

The number of error logs around 10700 log messages per 15 minutes, so its spams a lot.
Kubernetes CLI reports that there are stored versions of the CRD in v1 and v2 (see bottom lines):
$ kubectl get crd tracingservices.getambassador.io -o=yaml

apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
metadata:
  annotations:
    controller-gen.kubebuilder.io/version: v0.6.2
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"apiextensions.k8s.io/v1","kind":"CustomResourceDefinition","metadata":{"annotations":{"controller-gen.kubebuilder.io/version":"v0.6.2"},"labels":{"app.kubernetes.io/instance":"emissary-apiext","app.kubernetes.io/managed-by":"kubectl_apply_-f_emissary-apiext.yaml","app.kubernetes.io/name":"emissary-apiext","app.kubernetes.io/part-of":"emissary-apiext","owner":"team_sre"},"name":"tracingservices.getambassador.io"},"spec":{"conversion":{"strategy":"Webhook","webhook":{"clientConfig":{"service":{"name":"emissary-apiext","namespace":"ambassador"}},"conversionReviewVersions":["v1beta1"]}},"group":"getambassador.io","names":{"categories":["ambassador-crds"],"kind":"TracingService","listKind":"TracingServiceList","plural":"tracingservices","singular":"tracingservice"},"preserveUnknownFields":false,"scope":"Namespaced","versions":[{"name":"v2","schema":{"openAPIV3Schema":{"description":"TracingService is the Schema for the tracingservices API","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"type":"object"},"spec":{"description":"TracingServiceSpec defines the desired state of TracingService","properties":{"config":{"properties":{"access_token_file":{"type":"string"},"collector_cluster":{"type":"string"},"collector_endpoint":{"type":"string"},"collector_endpoint_version":{"enum":["HTTP_JSON_V1","HTTP_JSON","HTTP_PROTO"],"type":"string"},"collector_hostname":{"type":"string"},"service_name":{"type":"string"},"shared_span_context":{"type":"boolean"},"trace_id_128bit":{"type":"boolean"}},"type":"object"},"driver":{"enum":["lightstep","zipkin","datadog"],"type":"string"},"sampling":{"properties":{"client":{"type":"integer"},"overall":{"type":"integer"},"random":{"type":"integer"}},"type":"object"},"service":{"type":"string"},"tag_headers":{"items":{"type":"string"},"type":"array"},"v3StatsName":{"type":"string"}},"required":["driver","service"],"type":"object","x-kubernetes-preserve-unknown-fields":true}},"type":"object"}},"served":true,"storage":true},{"name":"v3alpha1","schema":{"openAPIV3Schema":{"description":"TracingService is the Schema for the tracingservices API","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"type":"object"},"spec":{"description":"TracingServiceSpec defines the desired state of TracingService","properties":{"ambassador_id":{"description":"AmbassadorID declares which Ambassador instances should pay attention to this resource. If no value is provided, the default is: \n    ambassador_id:    - \"default\" \n TODO(lukeshu): In v3alpha2, consider renaming all of the `ambassador_id` (singular) fields to `ambassador_ids` (plural).","items":{"type":"string"},"type":"array"},"config":{"properties":{"access_token_file":{"type":"string"},"collector_cluster":{"type":"string"},"collector_endpoint":{"type":"string"},"collector_endpoint_version":{"enum":["HTTP_JSON_V1","HTTP_JSON","HTTP_PROTO"],"type":"string"},"collector_hostname":{"type":"string"},"service_name":{"type":"string"},"shared_span_context":{"type":"boolean"},"trace_id_128bit":{"type":"boolean"}},"type":"object"},"driver":{"enum":["lightstep","zipkin","datadog"],"type":"string"},"sampling":{"properties":{"client":{"type":"integer"},"overall":{"type":"integer"},"random":{"type":"integer"}},"type":"object"},"service":{"type":"string"},"stats_name":{"type":"string"},"tag_headers":{"items":{"type":"string"},"type":"array"}},"required":["driver","service"],"type":"object"}},"type":"object"}},"served":true,"storage":false},{"name":"v1","schema":{"openAPIV3Schema":{"description":"TracingService is the Schema for the tracingservices API","type":"object","x-kubernetes-preserve-unknown-fields":true}},"served":false,"storage":false}]}}
  creationTimestamp: "2019-09-12T09:15:35Z"
  generation: 12
  labels:
    app.kubernetes.io/instance: emissary-apiext
    app.kubernetes.io/managed-by: kubectl_apply_-f_emissary-apiext.yaml
    app.kubernetes.io/name: emissary-apiext
    app.kubernetes.io/part-of: emissary-apiext
    owner: team_sre
  name: tracingservices.getambassador.io
  resourceVersion: "2436618420"
  selfLink: /apis/apiextensions.k8s.io/v1/customresourcedefinitions/tracingservices.getambassador.io
  uid: e124e532-d53d-11e9-b8d3-0ab5b0c37404
spec:
  conversion:
    strategy: Webhook
    webhook:
      clientConfig:
        caBundle: <redacted>
        service:
          name: emissary-apiext
          namespace: ambassador
          path: /webhooks/crd-convert
          port: 443
      conversionReviewVersions:
      - v1beta1
  group: getambassador.io
  names:
    categories:
    - ambassador-crds
    kind: TracingService
    listKind: TracingServiceList
    plural: tracingservices
    singular: tracingservice
  scope: Namespaced
  versions:
  - name: v2
    schema:
      openAPIV3Schema:
        description: TracingService is the Schema for the tracingservices API
        properties:
          apiVersion:
            description: 'APIVersion defines the versioned schema of this representation
              of an object. Servers should convert recognized schemas to the latest
              internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources'
            type: string
          kind:
            description: 'Kind is a string value representing the REST resource this
              object represents. Servers may infer this from the endpoint the client
              submits requests to. Cannot be updated. In CamelCase.  Servers should convert recognized schemas to the latest
              internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources'
            type: string
          kind:
            description: 'Kind is a string value representing the REST resource this
              object represents. Servers may infer this from the endpoint the client
              submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds'
            type: string
          metadata:
            type: object
          spec:
            description: TracingServiceSpec defines the desired state of TracingService
            properties:
              ambassador_id:
                description: "AmbassadorID declares which Ambassador instances should
                  pay attention to this resource. If no value is provided, the default
                  is: \n    ambassador_id:    - \"default\" \n TODO(lukeshu): In v3alpha2,
                  consider renaming all of the `ambassador_id` (singular) fields to
                  `ambassador_ids` (plural)."
                items:
                  type: string
                type: array
              config:
                properties:
                  access_token_file:
                    type: string
                  collector_cluster:
                    type: string
                  collector_endpoint:
                    type: string
                  collector_endpoint_version:
                    enum:
                    - HTTP_JSON_V1
                    - HTTP_JSON
                    - HTTP_PROTO
                    type: string
                  collector_hostname:
                    type: string
                  service_name:
                    type: string
                  shared_span_context:
                    type: boolean
                  trace_id_128bit:
                    type: boolean
                type: object
              driver:
                enum:
                - lightstep
                - zipkin
                - datadog
                type: string
              sampling:
                properties:
                  client:
                    type: integer
                  overall:
                    type: integer
                  random:
                    type: integer
                type: object
              service:
                type: string
              stats_name:
                type: string
              tag_headers:
                items:
                  type: string
                type: array
            required:
            - driver
            - service
            type: object
        type: object
    served: true
    storage: false
  - name: v1
    schema:
      openAPIV3Schema:
        description: TracingService is the Schema for the tracingservices API
        type: object
        x-kubernetes-preserve-unknown-fields: true
    served: false
    storage: false
status:
  acceptedNames:
    categories:
    - ambassador-crds
    kind: TracingService
    listKind: TracingServiceList
    plural: tracingservices
    singular: tracingservice
  conditions:
  - lastTransitionTime: "2019-09-12T09:15:35Z"
    message: no conflicts found
    reason: NoConflicts
    status: "True"
    type: NamesAccepted
  - lastTransitionTime: null
    message: the initial names have been accepted
    reason: InitialNamesAccepted
    status: "True"
    type: Established
  storedVersions:
  - v1
  - v2

Kubectl only reports a single tracingservice and it is in v2:
$ kubectl get tracingservices.getambassador.io --all-namespaces -o=yaml

apiVersion: v1
items:
- apiVersion: getambassador.io/v2
  kind: TracingService
  metadata:
    annotations:
      kubectl.kubernetes.io/last-applied-configuration: |
        {"apiVersion":"getambassador.io/v2","kind":"TracingService","metadata":{"annotations":{},"name":"tracing","namespace":"monitoring"},"spec":{"ambassador_id":["public"],"driver":"zipkin","service":"zipkin.monitoring:9411","tag_headers":[":authority",":path"]}}
    creationTimestamp: "2021-03-03T22:19:56Z"
    generation: 2
    name: tracing
    namespace: monitoring
    resourceVersion: "791986493"
    selfLink: /apis/getambassador.io/v2/namespaces/monitoring/tracingservices/tracing
    uid: c69f7e0f-d621-4d52-b644-7bca965fba5f
  spec:
    ambassador_id:
    - public
    driver: zipkin
    service: zipkin.monitoring:9411
    tag_headers:
    - :authority
    - :path
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

Did you try to find in managedFields ? I got the same error when still have managedFields with v1.
E.g.
        "managedFields": [
          {
            "apiVersion": "getambassador.io/v1",
            "fieldsType": "FieldsV1",
            "fieldsV1": {
              "f:metadata": {
                "f:annotations": {
                  ".": {},
                  "f:kubectl.kubernetes.io/last-applied-configuration": {}
                }
              },
              "f:spec": {
                ".": {},
                "f:ambassador_id": {},
                "f:host": {},
                "f:precedence": {},
                "f:prefix": {},
                "f:rewrite": {},
                "f:service": {},
                "f:timeout_ms": {}
              }
            },
            "manager": "kubectl",
            "operation": "Update",
            "time": "2021-03-31T12:51:16Z"
          }
        ],

Same issue here, has anyone in this thread managed to resolve it?

Same issue. Got a nice fat logs bill as a reward for upgrading emissary.

Still seeing this issue @LukeShu - just enabled EKS API server logs and getting flooded with these errors. I'm on emissary-ingress-8.3.0 (chart) and 3.3.0 (app version).

@seunggs The commits from the PR that closed this issue were not part of the 3.3.0 release. You'll need to use version 3.4.0 to get the fix from these changes. https://www.getambassador.io/docs/emissary/latest/release-notes

I confirm that release 3.4.0 fix the issue
After to perform the upgrade no more errors on the EKS API server logs


[EventRequest] Report 81 "Import Budget from Excel".SetBudgetDimFilter

Please add new event
procedure SetBudgetDimFilter(DimCode2: Code[20]; DimValCode2: Code[20]; var GLBudgetEntry2: Record "G/L Budget Entry")
begin
    case DimCode2 of
        BusUnitDimCode:
            GLBudgetEntry2.SetRange("Business Unit Code", DimValCode2);
        GlobalDim1Code:
            GLBudgetEntry2.SetRange("Global Dimension 1 Code", DimValCode2);
        GlobalDim2Code:
            GLBudgetEntry2.SetRange("Global Dimension 2 Code", DimValCode2);
        BudgetDim1Code:
            GLBudgetEntry2.SetRange("Budget Dimension 1 Code", DimValCode2);
        BudgetDim2Code:
            GLBudgetEntry2.SetRange("Budget Dimension 2 Code", DimValCode2);
        BudgetDim3Code:
            GLBudgetEntry2.SetRange("Budget Dimension 3 Code", DimValCode2);
        BudgetDim4Code:
            GLBudgetEntry2.SetRange("Budget Dimension 4 Code", DimValCode2);
    end;

    //-------------------------------OnSetBudgetDimFilterOnAfterSetFilter:BEGIN
    OnSetBudgetDimFilterOnAfterSetFilter(GLBudgetEntry2,DimValCode2)
    //-------------------------------OnSetBudgetDimFilterOnAfterSetFilter:END
end;

[IntegrationEvent(false, false)]
local procedure OnSetBudgetDimFilterOnAfterSetFilter(var GLBudgetEntry: Record "G/L Budget Entry"; DimValCode2: Code[20])
begin
end

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Better handle no selectable choices

Hi,
I'm testing this branch
It works better than the actual implementation, but there are still a few issues with "dynamic" fields.
I think it is related to some missing checks after setChoices
v11: https://jsfiddle.net/tagliala/rx8mtbz6/17/

v10: https://jsfiddle.net/tagliala/rx8mtbz6/18/

@tagliala It looks like setChoices didn't clear the cached notice, so the last notice "stuck". That should be fixed.
I think the entire notice system needs a bit of a rework to avoid this ad-hoc matching and to be more centralized (basically making a notice reducer which listens for the relevant add/remove events.
But for now the current code should work

@Xon thanks, can you rebase this branch on master? I would like to take a look


Slow startup

Version
Microsoft Windows [Version 10.0.22622.575]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
No response
Distro Version
Debian Buster
Other Software
No response
Repro Steps
Launch wsl2
Expected Behavior
startup within one or two seconds
Actual Behavior
startup takes three to four seconds. I think possibly on the virtual disk line, so maybe with mounting the vhdx?
Im on a surface pro 8, so an nvme which should be speedy!
Diagnostic Logs
[    0.000000] Linux version <IP_ADDRESS>-microsoft-standard-WSL2 (oe-user@oe-host) (x86_64-msft-linux-gcc (GCC) 9.3.0, GNU ld (GNU Binutils) <IP_ADDRESS>00220) #1 SMP Wed Jul 27 02:20:31 UTC 2022
[    0.000000] Command line: initrd=\initrd.img WSL_ROOT_INIT=1 panic=-1 nr_cpus=8 swiotlb=force console=hvc0 debug pty.legacy_count=0
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Centaur CentaurHauls
[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x020: 'AVX-512 opmask'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x040: 'AVX-512 Hi256'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x080: 'AVX-512 ZMM_Hi256'
[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.000000] x86/fpu: xstate_offset[5]:  832, xstate_sizes[5]:   64
[    0.000000] x86/fpu: xstate_offset[6]:  896, xstate_sizes[6]:  512
[    0.000000] x86/fpu: xstate_offset[7]: 1408, xstate_sizes[7]: 1024
[    0.000000] x86/fpu: Enabled xstate features 0xe7, context size is 2432 bytes, using 'compacted' format.
[    0.000000] signal: max sigframe size: 3632
[    0.000000] BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
[    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000e0fff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000001fffff] ACPI data
[    0.000000] BIOS-e820: [mem 0x0000000000200000-0x00000000f7ffffff] usable
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x0000000402bfffff] usable
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] DMI not present or invalid.
[    0.000000] Hypervisor detected: Microsoft Hyper-V
[    0.000000] Hyper-V: privilege flags low 0xae7f, high 0x3b8030, hints 0xa4e24, misc 0xe4bed7b6
[    0.000000] Hyper-V Host Build:22621-10.0-0-0.575
[    0.000000] Hyper-V: Nested features: 0x3e0101
[    0.000000] Hyper-V: LAPIC Timer Frequency: 0x1e8480
[    0.000000] Hyper-V: Using hypercall for remote TLB flush
[    0.000000] clocksource: hyperv_clocksource_tsc_page: mask: 0xffffffffffffffff max_cycles: 0x24e6a1710, max_idle_ns:<PHONE_NUMBER>20 ns
[    0.000004] tsc: Detected 2995.211 MHz processor
[    0.000023] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[    0.000029] e820: remove [mem 0x000a0000-0x000fffff] usable
[    0.000035] last_pfn = 0x402c00 max_arch_pfn = 0x400000000
[    0.000079] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT
[    0.000096] last_pfn = 0xf8000 max_arch_pfn = 0x400000000
[    0.000112] Using GB pages for direct mapping
[    0.000733] RAMDISK: [mem 0x03a35000-0x03c05fff]
[    0.000739] ACPI: Early table checksum verification disabled
[    0.000762] ACPI: RSDP 0x00000000000E0000 000024 (v02 VRTUAL)
[    0.000769] ACPI: XSDT 0x0000000000100000 000044 (v01 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.000786] ACPI: FACP 0x0000000000101000 000114 (v06 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.000795] ACPI: DSDT 0x00000000001011B8 01E191 (v02 MSFTVM DSDT01   00000001 MSFT 05000000)
[    0.000801] ACPI: FACS 0x0000000000101114 000040
[    0.000806] ACPI: OEM0 0x0000000000101154 000064 (v01 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.000812] ACPI: SRAT 0x000000000011F349 000330 (v02 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.000817] ACPI: APIC 0x000000000011F679 000088 (v04 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.000822] ACPI: Reserving FACP table memory at [mem 0x101000-0x101113]
[    0.000825] ACPI: Reserving DSDT table memory at [mem 0x1011b8-0x11f348]
[    0.000826] ACPI: Reserving FACS table memory at [mem 0x101114-0x101153]
[    0.000828] ACPI: Reserving OEM0 table memory at [mem 0x101154-0x1011b7]
[    0.000830] ACPI: Reserving SRAT table memory at [mem 0x11f349-0x11f678]
[    0.000832] ACPI: Reserving APIC table memory at [mem 0x11f679-0x11f700]
[    0.001144] Zone ranges:
[    0.001147]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
[    0.001150]   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
[    0.001153]   Normal   [mem 0x0000000100000000-0x0000000402bfffff]
[    0.001155]   Device   empty
[    0.001157] Movable zone start for each node
[    0.001159] Early memory node ranges
[    0.001160]   node   0: [mem 0x0000000000001000-0x000000000009ffff]
[    0.001192]   node   0: [mem 0x0000000000200000-0x00000000f7ffffff]
[    0.001196]   node   0: [mem 0x0000000100000000-0x0000000402bfffff]
[    0.001201] Initmem setup node 0 [mem 0x0000000000001000-0x0000000402bfffff]
[    0.003862] On node 0, zone DMA: 1 pages in unavailable ranges
[    0.004005] On node 0, zone DMA: 352 pages in unavailable ranges
[    0.032098] On node 0, zone Normal: 21504 pages in unavailable ranges
[    0.032154] ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
[    0.032444] IOAPIC[0]: apic_id 8, version 17, address 0xfec00000, GSI 0-23
[    0.032450] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.032455] ACPI: Using ACPI (MADT) for SMP configuration information
[    0.032457] TSC deadline timer available
[    0.032458] smpboot: Allowing 8 CPUs, 0 hotplug CPUs
[    0.032469] [mem 0xf8000000-0xffffffff] available for PCI devices
[    0.032470] Booting paravirtualized kernel on Hyper-V
[    0.032472] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:<PHONE_NUMBER>2750000 ns
[    0.039165] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:8 nr_node_ids:1
[    0.039659] percpu: Embedded 53 pages/cpu s177432 r8192 d31464 u262144
[    0.039668] pcpu-alloc: s177432 r8192 d31464 u262144 alloc=1*2097152
[    0.039672] pcpu-alloc: [0] 0 1 2 3 4 5 6 7
[    0.039692] Hyper-V: PV spinlocks enabled
[    0.039695] PV qspinlock hash table entries: 256 (order: 0, 4096 bytes, linear)
[    0.039701] Built 1 zonelists, mobility grouping on.  Total pages: 4106581
[    0.039704] Kernel command line: initrd=\initrd.img WSL_ROOT_INIT=1 panic=-1 nr_cpus=8 swiotlb=force console=hvc0 debug pty.legacy_count=0
[    0.039848] Unknown kernel command line parameters "WSL_ROOT_INIT=1", will be passed to user space.
[    0.042468] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear)
[    0.043982] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear)
[    0.044166] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.071110] Memory: 4081540K/16689788K available (18454K kernel code, 2616K rwdata, 9556K rodata, 2000K init, 2048K bss, 400336K reserved, 0K cma-reserved)
[    0.071151] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[    0.071158] ftrace: allocating 53430 entries in 209 pages
[    0.106826] ftrace: allocated 209 pages with 4 groups
[    0.107329] rcu: Hierarchical RCU implementation.
[    0.107333] rcu: 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=8.
[    0.107337] 	Rude variant of Tasks RCU enabled.
[    0.107338] 	Tracing variant of Tasks RCU enabled.
[    0.107340] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[    0.107342] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
[    0.112480] Using NULL legacy PIC
[    0.112483] NR_IRQS: 16640, nr_irqs: 488, preallocated irqs: 0
[    0.112847] random: crng init done
[    0.112875] Console: colour dummy device 80x25
[    0.112897] ACPI: Core revision 20210730
[    0.112995] Failed to register legacy timer interrupt
[    0.112996] APIC: Switch to symmetric I/O mode setup
[    0.114979] x2apic enabled
[    0.116853] Switched APIC routing to physical x2apic.
[    0.116870] Hyper-V: Using IPI hypercalls
[    0.116932] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x2b2c993ffe9, max_idle_ns:<PHONE_NUMBER>10 ns
[    0.116941] Calibrating delay loop (skipped), value calculated using timer frequency.. 5990.42 BogoMIPS (lpj=29952110)
[    0.116943] pid_max: default: 32768 minimum: 301
[    0.116955] LSM: Security Framework initializing
[    0.116960] landlock: Up and running.
[    0.116998] Mount-cache hash table entries: 32768 (order: 6, 262144 bytes, linear)
[    0.117026] Mountpoint-cache hash table entries: 32768 (order: 6, 262144 bytes, linear)
[    0.117306] x86/cpu: User Mode Instruction Prevention (UMIP) activated
[    0.117321] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
[    0.117322] Last level dTLB entries: 4KB 0, 2MB 0, 4MB 0, 1GB 0
[    0.117327] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
[    0.117329] Spectre V2 : Mitigation: Enhanced IBRS
[    0.117330] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
[    0.117332] RETBleed: Mitigation: Enhanced IBRS
[    0.117333] Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
[    0.117335] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp
[    0.126935] Freeing SMP alternatives memory: 56K
[    0.126935] smpboot: CPU0: 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz (family: 0x6, model: 0x8c, stepping: 0x1)
[    0.126935] Performance Events:  AnyThread deprecated, Icelake events, 32-deep LBR, full-width counters, Intel PMU driver.
[    0.126935] ... version:                5
[    0.126935] ... bit width:              48
[    0.126935] ... generic registers:      8
[    0.126935] ... value mask:             0000ffffffffffff
[    0.126935] ... max period:             00007fffffffffff
[    0.126935] ... fixed-purpose events:   4
[    0.126935] ... event mask:             0001000f000000ff
[    0.126935] rcu: Hierarchical SRCU implementation.
[    0.126935] smp: Bringing up secondary CPUs ...
[    0.126935] x86: Booting SMP configuration:
[    0.126935] .... node  #0, CPUs:      #1 #2 #3 #4 #5 #6 #7
[    0.126935] smp: Brought up 1 node, 8 CPUs
[    0.126935] smpboot: Max logical packages: 1
[    0.126935] smpboot: Total of 8 processors activated (47923.37 BogoMIPS)
[    0.146763] node 0 deferred pages initialised in 20ms
[    0.147678] devtmpfs: initialized
[    0.147678] x86/mm: Memory block size: 128MB
[    0.147678] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:<PHONE_NUMBER>2750000 ns
[    0.147678] futex hash table entries: 2048 (order: 5, 131072 bytes, linear)
[    0.148031] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[    0.148161] thermal_sys: Registered thermal governor 'step_wise'
[    0.148194] cpuidle: using governor menu
[    0.148194] ACPI: bus type PCI registered
[    0.148194] PCI: Fatal: No config space access function found
[    0.148614] Kprobes globally optimized
[    0.148646] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[    0.148646] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.156988] raid6: skip pq benchmark and using algorithm avx512x4
[    0.156988] raid6: using avx512x2 recovery algorithm
[    0.156988] ACPI: Added _OSI(Module Device)
[    0.156988] ACPI: Added _OSI(Processor Device)
[    0.156988] ACPI: Added _OSI(3.0 _SCP Extensions)
[    0.156989] ACPI: Added _OSI(Processor Aggregator Device)
[    0.156991] ACPI: Added _OSI(Linux-Dell-Video)
[    0.156992] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[    0.156993] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
[    0.159600] ACPI: 1 ACPI AML tables successfully acquired and loaded
[    0.160445] ACPI: Interpreter enabled
[    0.160445] ACPI: PM: (supports S0 S5)
[    0.160445] ACPI: Using IOAPIC for interrupt routing
[    0.160445] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.160445] ACPI: Enabled 2 GPEs in block 00 to 0F
[    0.160445] iommu: Default domain type: Translated
[    0.160445] iommu: DMA domain TLB invalidation policy: lazy mode
[    0.160445] SCSI subsystem initialized
[    0.160445] ACPI: bus type USB registered
[    0.160445] usbcore: registered new interface driver usbfs
[    0.160445] usbcore: registered new interface driver hub
[    0.160445] usbcore: registered new device driver usb
[    0.160445] pps_core: LinuxPPS API ver. 1 registered
[    0.160445] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti<EMAIL_ADDRESS>[    0.160445] PTP clock support registered
[    0.166980] hv_vmbus: Vmbus version:5.3
[    0.167144] PCI: Using ACPI for IRQ routing
[    0.167147] PCI: System does not support PCI
[    0.168446] clocksource: Switched to clocksource tsc-early
[    0.168540] hv_vmbus: Unknown GUID: c376c1c3-d276-48d2-90a9-c04748072c60
[    0.168597] hv_vmbus: Unknown GUID: 6e382d18-3336-4f4b-acc4-2b7703d4df4a
[    0.168610] hv_vmbus: Unknown GUID: dde9cbc0-5060-4436-9448-ea1254a5d177
[    0.180393] VFS: Disk quotas dquot_6.6.0
[    0.180406] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.180424] FS-Cache: Loaded
[    0.180449] pnp: PnP ACPI init
[    0.180645] pnp: PnP ACPI: found 1 devices
[    0.186242] NET: Registered PF_INET protocol family
[    0.186665] IP idents hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[    0.187994] tcp_listen_portaddr_hash hash table entries: 8192 (order: 5, 131072 bytes, linear)
[    0.188011] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.188015] TCP established hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[    0.188350] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes, linear)
[    0.188463] TCP: Hash tables configured (established 131072 bind 65536)
[    0.188493] UDP hash table entries: 8192 (order: 6, 262144 bytes, linear)
[    0.188523] UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes, linear)
[    0.188571] NET: Registered PF_UNIX/PF_LOCAL protocol family
[    0.189268] RPC: Registered named UNIX socket transport module.
[    0.189272] RPC: Registered udp transport module.
[    0.189273] RPC: Registered tcp transport module.
[    0.189274] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.189278] PCI: CLS 0 bytes, default 64
[    0.189305] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[    0.189307] software IO TLB: mapped [mem 0x00000000f4000000-0x00000000f8000000] (64MB)
[    0.189339] Trying to unpack rootfs image as initramfs...
[    0.189386] KVM: vmx: using Hyper-V Enlightened VMCS
[    0.190328] Freeing initrd memory: 1860K
[    0.463001] kvm: already loaded the other module
[    0.466799] Initialise system trusted keyrings
[    0.466997] workingset: timestamp_bits=46 max_order=22 bucket_order=0
[    0.467855] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.468187] NFS: Registering the id_resolver key type
[    0.468315] Key type id_resolver registered
[    0.468316] Key type id_legacy registered
[    0.468319] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.468322] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[    0.468323] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    0.469293] Key type cifs.idmap registered
[    0.469456] fuse: init (API version 7.34)
[    0.469629] SGI XFS with ACLs, security attributes, realtime, scrub, repair, quota, no debug enabled
[    0.470182] 9p: Installing v9fs 9p2000 file system support
[    0.470190] FS-Cache: Netfs '9p' registered for caching
[    0.480394] NET: Registered PF_ALG protocol family
[    0.480397] xor: automatically using best checksumming function   avx
[    0.480398] Key type asymmetric registered
[    0.480400] Asymmetric key parser 'x509' registered
[    0.480447] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 248)
[    0.481041] hv_vmbus: registering driver hv_pci
[    0.481712] hv_pci 870bc200-f828-4f53-89cf-46f9318bedf0: PCI VMBus probing: Using version 0x10004
[    0.483156] hv_pci 870bc200-f828-4f53-89cf-46f9318bedf0: PCI host bridge to bus f828:00
[    0.483159] pci_bus f828:00: root bus resource [mem 0x9ffe00000-0x9ffe02fff window]
[    0.483162] pci_bus f828:00: No busn resource found for root bus, will use [bus 00-ff]
[    0.483924] pci f828:00:00.0: [1af4:1043] type 00 class 0x010000
[    0.484853] pci f828:00:00.0: reg 0x10: [mem 0x9ffe00000-0x9ffe00fff 64bit]
[    0.485446] pci f828:00:00.0: reg 0x18: [mem 0x9ffe01000-0x9ffe01fff 64bit]
[    0.486026] pci f828:00:00.0: reg 0x20: [mem 0x9ffe02000-0x9ffe02fff 64bit]
[    0.489003] pci_bus f828:00: busn_res: [bus 00-ff] end is updated to 00
[    0.489009] pci f828:00:00.0: BAR 0: assigned [mem 0x9ffe00000-0x9ffe00fff 64bit]
[    0.489419] pci f828:00:00.0: BAR 2: assigned [mem 0x9ffe01000-0x9ffe01fff 64bit]
[    0.489827] pci f828:00:00.0: BAR 4: assigned [mem 0x9ffe02000-0x9ffe02fff 64bit]
[    0.490808] hv_pci 3533b7ab-edf6-4688-9e59-74652a3d7a0e: PCI VMBus probing: Using version 0x10004
[    0.491784] hv_pci 3533b7ab-edf6-4688-9e59-74652a3d7a0e: PCI host bridge to bus edf6:00
[    0.491788] pci_bus edf6:00: No busn resource found for root bus, will use [bus 00-ff]
[    0.492247] pci edf6:00:00.0: [1414:008e] type 00 class 0x030200
[    0.497289] pci_bus edf6:00: busn_res: [bus 00-ff] end is updated to 00
[    0.498090] hv_pci 941b7727-f207-40ca-9848-4907e2ffb7b2: PCI VMBus probing: Using version 0x10004
[    0.500064] hv_pci 941b7727-f207-40ca-9848-4907e2ffb7b2: PCI host bridge to bus f207:00
[    0.500068] pci_bus f207:00: root bus resource [mem 0x9ffe04000-0x9ffe06fff window]
[    0.500071] pci_bus f207:00: No busn resource found for root bus, will use [bus 00-ff]
[    0.501302] pci f207:00:00.0: [1af4:1049] type 00 class 0x010000
[    0.502585] pci f207:00:00.0: reg 0x10: [mem 0x9ffe04000-0x9ffe04fff 64bit]
[    0.503468] pci f207:00:00.0: reg 0x18: [mem 0x9ffe05000-0x9ffe05fff 64bit]
[    0.504353] pci f207:00:00.0: reg 0x20: [mem 0x9ffe06000-0x9ffe06fff 64bit]
[    0.509676] pci_bus f207:00: busn_res: [bus 00-ff] end is updated to 00
[    0.509684] pci f207:00:00.0: BAR 0: assigned [mem 0x9ffe04000-0x9ffe04fff 64bit]
[    0.510338] pci f207:00:00.0: BAR 2: assigned [mem 0x9ffe05000-0x9ffe05fff 64bit]
[    0.510946] pci f207:00:00.0: BAR 4: assigned [mem 0x9ffe06000-0x9ffe06fff 64bit]
[    0.511736] ACPI: AC: AC Adapter [AC1] (off-line)
[    0.512800] ACPI: battery: Slot [BAT1] (battery present)
[    0.522180] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    0.560153] Non-volatile memory driver v1.3
[    0.560378] [drm] Initialized vgem 1.0.0 20120112 for vgem on minor 0
[    0.562187] printk: console [hvc0] enabled
[    0.565050] brd: module loaded
[    0.567731] loop: module loaded
[    0.568114] hv_vmbus: registering driver hv_storvsc
[    0.569355] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
[    0.569953] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld<EMAIL_ADDRESS>All Rights Reserved.
[    0.570283] scsi host0: storvsc_host_t
[    0.570817] tun: Universal TUN/TAP device driver, 1.6
[    0.571563] PPP generic driver version 2.4.2
[    0.572084] PPP BSD Compression module registered
[    0.572549] PPP Deflate Compression module registered
[    0.572995] PPP MPPE Compression module registered
[    0.573366] NET: Registered PF_PPPOX protocol family
[    0.573741] usbcore: registered new interface driver cdc_ether
[    0.574324] usbcore: registered new interface driver cdc_ncm
[    0.574718] hv_vmbus: registering driver hv_netvsc
[    0.575137] VFIO - User Level meta-driver version: 0.3
[    0.575631] usbcore: registered new interface driver cdc_acm
[    0.576144] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[    0.576741] usbcore: registered new interface driver ch341
[    0.577232] usbserial: USB Serial support registered for ch341-uart
[    0.577712] usbcore: registered new interface driver cp210x
[    0.578066] usbserial: USB Serial support registered for cp210x
[    0.578645] usbcore: registered new interface driver ftdi_sio
[    0.579145] usbserial: USB Serial support registered for FTDI USB Serial Device
[    0.579937] vhci_hcd vhci_hcd.0: USB/IP Virtual Host Controller
[    0.580445] vhci_hcd vhci_hcd.0: new USB bus registered, assigned bus number 1
[    0.580992] vhci_hcd: created sysfs vhci_hcd.0
[    0.581772] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15
[    0.582650] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.583447] usb usb1: Product: USB/IP Virtual Host Controller
[    0.584023] usb usb1: Manufacturer: Linux <IP_ADDRESS>-microsoft-standard-WSL2 vhci_hcd
[    0.584818] usb usb1: SerialNumber: vhci_hcd.0
[    0.585555] hub 1-0:1.0: USB hub found
[    0.585850] hub 1-0:1.0: 8 ports detected
[    0.586910] vhci_hcd vhci_hcd.0: USB/IP Virtual Host Controller
[    0.587382] vhci_hcd vhci_hcd.0: new USB bus registered, assigned bus number 2
[    0.588000] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[    0.589056] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.15
[    0.589821] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.590711] usb usb2: Product: USB/IP Virtual Host Controller
[    0.591363] usb usb2: Manufacturer: Linux <IP_ADDRESS>-microsoft-standard-WSL2 vhci_hcd
[    0.592084] usb usb2: SerialNumber: vhci_hcd.0
[    0.592813] hub 2-0:1.0: USB hub found
[    0.593107] hub 2-0:1.0: 8 ports detected
[    0.593983] hv_vmbus: registering driver hyperv_keyboard
[    0.594605] rtc_cmos 00:00: RTC can wake from S4
[    0.596840] rtc_cmos 00:00: registered as rtc0
[    0.597600] rtc_cmos 00:00: setting system clock to 2022-08-22T08:00:01 UTC<PHONE_NUMBER>)
[    0.598051] rtc_cmos 00:00: alarms up to one month, 114 bytes nvram
[    0.599008] device-mapper: ioctl: 4.45.0-ioctl (2021-03-22) initialised<EMAIL_ADDRESS>[    0.599892] device-mapper: raid: Loading target version 1.15.1
[    0.600321] usbcore: registered new interface driver usbhid
[    0.600607] usbhid: USB HID core driver
[    0.600905] hv_utils: Registering HyperV Utility Driver
[    0.601212] hv_vmbus: registering driver hv_utils
[    0.601529] hv_vmbus: registering driver hv_balloon
[    0.601955] hv_utils: TimeSync IC version 4.0
[    0.602070] hv_vmbus: registering driver dxgkrnl
[    0.602695] hv_balloon: Using Dynamic Memory protocol version 2.0
[    0.602966] (NULL device *): dxgk: dxg_drv_init  Version: 2216
[    0.604083] Free page reporting enabled
[    0.604935] hv_balloon: Cold memory discard hint enabled
[    0.605207] (NULL device *): dxgk: mmio allocated 9ffe10000  200000000 9ffe10000 bffe0ffff
[    0.607204] drop_monitor: Initializing network drop monitor service
[    0.607619] Mirror/redirect action on
[    0.607838] u32 classifier
[    0.607979]     Performance counters on
[    0.608191]     input device check on
[    0.608598]     Actions configured
[    0.610040] IPVS: Registered protocols (TCP, UDP)
[    0.610782] IPVS: Connection hash table configured (size=4096, memory=32Kbytes)
[    0.611723] IPVS: ipvs loaded.
[    0.612175] IPVS: [rr] scheduler registered.
[    0.612726] IPVS: [wrr] scheduler registered.
[    0.613128] IPVS: [sh] scheduler registered.
[    0.613757] ipip: IPv4 and MPLS over IPv4 tunneling driver
[    0.614282] ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully
[    0.615128] Initializing XFRM netlink socket
[    0.615847] NET: Registered PF_INET6 protocol family
[    0.616899] Segment Routing with IPv6
[    0.617223] In-situ OAM (IOAM) with IPv6
[    0.617495] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    0.617956] NET: Registered PF_PACKET protocol family
[    0.618439] Bridge firewalling registered
[    0.618981] 8021q: 802.1Q VLAN Support v1.8
[    0.619413] sctp: Hash tables configured (bind 256/256)
[    0.619964] 9pnet: Installing 9P2000 support
[    0.638729] Key type dns_resolver registered
[    0.639329] NET: Registered PF_VSOCK protocol family
[    0.639679] hv_vmbus: registering driver hv_sock
[    0.640044] IPI shorthand broadcast: enabled
[    0.640353] sched_clock: Marking stable (635206231, 4103200)->(663903900, -24594469)
[    0.641290] registered taskstats version 1
[    0.642227] Loading compiled-in X.509 certificates
[    0.643590] Btrfs loaded, crc32c=crc32c-generic, zoned=no, fsverity=no
[    0.652165] Freeing unused kernel image (initmem) memory: 2000K
[    0.677143] Write protecting the kernel read-only data: 30720k
[    0.679320] Freeing unused kernel image (text/rodata gap) memory: 2024K
[    0.680719] Freeing unused kernel image (rodata/data gap) memory: 684K
[    0.681327] Run /init as init process
[    0.681674]   with arguments:
[    0.682039]     /init
[    0.682297]   with environment:
[    0.682878]     HOME=/
[    0.683221]     TERM=linux
[    0.683490]     WSL_ROOT_INIT=1
[    0.711691] scsi 0:0:0:0: Direct-Access     Msft     Virtual Disk     1.0  PQ: 0 ANSI: 5
[    0.714190] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    0.718191] sd 0:0:0:0: [sda] 751192 512-byte logical blocks: (385 MB/367 MiB)
[    0.720908] sd 0:0:0:0: [sda] Write Protect is on
[    0.724487] sd 0:0:0:0: [sda] Mode Sense: 0f 00 80 00
[    0.726716] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[    1.309858] EXT4-fs (sda): mounted filesystem without journal. Opts: (null). Quota mode: none.
[    1.467164] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x2b2c993ffe9, max_idle_ns:<PHONE_NUMBER>10 ns
[    1.468089] sd 0:0:0:0: [sda] Attached SCSI disk
[    1.472928] clocksource: Switched to clocksource tsc
[    1.493865] hv_pci cec6f92f-4430-41b5-bc11-a2ca4c7ec259: PCI VMBus probing: Using version 0x10004
[    1.497033] hv_pci cec6f92f-4430-41b5-bc11-a2ca4c7ec259: PCI host bridge to bus 4430:00
[    1.497562] pci_bus 4430:00: root bus resource [mem 0xc00000000-0xe00001fff window]
[    1.498058] pci_bus 4430:00: No busn resource found for root bus, will use [bus 00-ff]
[    1.500021] pci 4430:00:00.0: [1af4:105a] type 00 class 0x088000
[    1.502845] pci 4430:00:00.0: reg 0x10: [mem 0xe00000000-0xe00000fff 64bit]
[    1.505389] pci 4430:00:00.0: reg 0x18: [mem 0xe00001000-0xe00001fff 64bit]
[    1.508715] pci 4430:00:00.0: reg 0x20: [mem 0xc00000000-0xdffffffff 64bit]
[    1.514113] pci_bus 4430:00: busn_res: [bus 00-ff] end is updated to 00
[    1.514540] pci 4430:00:00.0: BAR 4: assigned [mem 0xc00000000-0xdffffffff 64bit]
[    1.517059] pci 4430:00:00.0: BAR 0: assigned [mem 0xe00000000-0xe00000fff 64bit]
[    1.519942] pci 4430:00:00.0: BAR 2: assigned [mem 0xe00001000-0xe00001fff 64bit]
[    1.536375] virtiofs virtio2: Cache len: 0x200000000 @ 0xc00000000
[    1.577115] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    1.637472] memmap_init_zone_device initialised 2097152 pages in 60ms
[    1.650338] FS-Cache: Duplicate cookie detected
[    1.651103] FS-Cache: O-cookie c=00000004 [p=00000002 fl=222 nc=0 na=1]
[    1.651935] FS-Cache: O-cookie d=000000002bd5225d{9P.session} n=0000000099698695
[    1.653008] FS-Cache: O-key=[10] '34323934393337343530'
[    1.653475] FS-Cache: N-cookie c=00000005 [p=00000002 fl=2 nc=0 na=1]
[    1.653945] FS-Cache: N-cookie d=000000002bd5225d{9P.session} n=00000000982b3412
[    1.654580] FS-Cache: N-key=[10] '34323934393337343530'
[    2.487873] scsi 0:0:0:1: Direct-Access     Msft     Virtual Disk     1.0  PQ: 0 ANSI: 5
[    2.491248] sd 0:0:0:1: Attached scsi generic sg1 type 0
[    2.493354] scsi 0:0:0:2: Direct-Access     Msft     Virtual Disk     1.0  PQ: 0 ANSI: 5
[    2.495934] sd 0:0:0:2: Attached scsi generic sg2 type 0
[    2.497608] sd 0:0:0:1: [sdb] 8388616 512-byte logical blocks: (4.29 GB/4.00 GiB)
[    2.500577] sd 0:0:0:2: [sdc] 536870912 512-byte logical blocks: (275 GB/256 GiB)
[    2.500604] sd 0:0:0:1: [sdb] 4096-byte physical blocks
[    2.502227] sd 0:0:0:2: [sdc] 4096-byte physical blocks
[    2.503957] sd 0:0:0:2: [sdc] Write Protect is off
[    2.505454] sd 0:0:0:1: [sdb] Write Protect is off
[    2.512054] sd 0:0:0:2: [sdc] Mode Sense: 0f 00 00 00
[    2.514400] sd 0:0:0:2: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.514742] sd 0:0:0:1: [sdb] Mode Sense: 0f 00 00 00
[    2.516870] sd 0:0:0:1: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.533731] sd 0:0:0:2: [sdc] Attached SCSI disk
[    2.535827] sd 0:0:0:1: [sdb] Attached SCSI disk
[    2.563522] EXT4-fs (sdc): recovery complete
[    2.566284] EXT4-fs (sdc): mounted filesystem with ordered data mode. Opts: discard,errors=remount-ro,data=ordered. Quota mode: none.
[    2.611540] Adding 4194304k swap on /dev/sdb.  Priority:-2 extents:1 across:4194304k
[    3.017178] hv_pci 3f065d71-13f6-4084-8acc-2ce36462f266: PCI VMBus probing: Using version 0x10004
[    3.020163] hv_pci 3f065d71-13f6-4084-8acc-2ce36462f266: PCI host bridge to bus 13f6:00
[    3.020873] pci_bus 13f6:00: root bus resource [mem 0x9ffe08000-0x9ffe0afff window]
[    3.021440] pci_bus 13f6:00: No busn resource found for root bus, will use [bus 00-ff]
[    3.022986] pci 13f6:00:00.0: [1af4:1049] type 00 class 0x010000
[    3.024388] pci 13f6:00:00.0: reg 0x10: [mem 0x9ffe08000-0x9ffe08fff 64bit]
[    3.025478] pci 13f6:00:00.0: reg 0x18: [mem 0x9ffe09000-0x9ffe09fff 64bit]
[    3.026583] pci 13f6:00:00.0: reg 0x20: [mem 0x9ffe0a000-0x9ffe0afff 64bit]
[    3.030711] pci_bus 13f6:00: busn_res: [bus 00-ff] end is updated to 00
[    3.031192] pci 13f6:00:00.0: BAR 0: assigned [mem 0x9ffe08000-0x9ffe08fff 64bit]
[    3.032238] pci 13f6:00:00.0: BAR 2: assigned [mem 0x9ffe09000-0x9ffe09fff 64bit]
[    3.033232] pci 13f6:00:00.0: BAR 4: assigned [mem 0x9ffe0a000-0x9ffe0afff 64bit]
[    3.266120] hv_pci e5cfe5d3-45fb-499d-8d56-9d683fba61a5: PCI VMBus probing: Using version 0x10004
[    3.272238] hv_pci e5cfe5d3-45fb-499d-8d56-9d683fba61a5: PCI host bridge to bus 45fb:00
[    3.272999] pci_bus 45fb:00: root bus resource [mem 0x9ffe0c000-0x9ffe0efff window]
[    3.273835] pci_bus 45fb:00: No busn resource found for root bus, will use [bus 00-ff]
[    3.276681] pci 45fb:00:00.0: [1af4:1049] type 00 class 0x010000
[    3.279754] pci 45fb:00:00.0: reg 0x10: [mem 0x9ffe0c000-0x9ffe0cfff 64bit]
[    3.281567] pci 45fb:00:00.0: reg 0x18: [mem 0x9ffe0d000-0x9ffe0dfff 64bit]
[    3.283275] pci 45fb:00:00.0: reg 0x20: [mem 0x9ffe0e000-0x9ffe0efff 64bit]
[    3.291837] pci_bus 45fb:00: busn_res: [bus 00-ff] end is updated to 00
[    3.293380] pci 45fb:00:00.0: BAR 0: assigned [mem 0x9ffe0c000-0x9ffe0cfff 64bit]
[    3.296121] pci 45fb:00:00.0: BAR 2: assigned [mem 0x9ffe0d000-0x9ffe0dfff 64bit]
[    3.298857] pci 45fb:00:00.0: BAR 4: assigned [mem 0x9ffe0e000-0x9ffe0efff 64bit]
[   49.429818] hv_balloon: Max. dynamic memory size: 16300 MB

3-4 seconds is about standard. I'll sync up with the vhdx team to see if there's any way to speed things up more than that.

After today's update, I also encountered the problem of slow startup.

The term "slow" is somewhat relative. I have mainly noticed this phenomenon. In case of WSL from Windows Store, the init binary first mounts system distribution (/dev/sda) then it mounts user distribution (/dev/sdb). Also if swap is enabled it takes another place (/dev/sdc). These mounting procedures may take more time than previous. Moving to SSD or similar may speed things up a little bit.
TW, @Macmee If you can move the log to a file and upload it in OP it may help to scroll less.

I have the exact same issue and similar logs to @senlinding with hv_balloon and hv_pci taking a long time. It is a relatively new phenomenon. Startup used to take 4-5 seconds a few months ago, and now it is around a minute. There has been no major changes to my system either on the Windows or Linux side apart from regular Windows Updates and apt upgrades.

[    4.225021] pci a0fc:00:00.0: BAR 4: assigned [mem 0xbffe16000-0xbffe16fff 64bit]
[   49.732478] hv_balloon: Max. dynamic memory size: 8060 MB
Same with me.  45s startup.  Fresh install of ubunu under windows 11 and everything up to date with patches.

@logularjason, could you perhaps check if the startup is also slow when you start Ubuntu in an admin terminal window?

@logularjason, could you perhaps check if the startup is also slow when you start Ubuntu in an admin terminal window?

Hi @stanmart - thanks for the suggestion.  I can confirm it starts in around 3s-4s when I run "wsl.exe" from cmd as admin.
What are implications for this?  i.e. are you trying to confirm/identify a bug?  I guess this is a work-around until a fix is available, or are you implying startup of ubuntu a different way?

Thanks for checking! I'm just hoping that it might be useful info for WSL maintainers for figuring out what the issue is. Seems peculiar so it might narrow things down a bit.


Fix SELinux label of bootstrap-secrets on non-bootstrapping controllers

There's already a merged PR addressing the same problem on the controller that runs bootstrap service. However, on other controllers, Docker pods kube-apiserver, kube-scheduler, and kube-controller-manager still cannot read files from /etc/kubernetes/bootstrap-secrets (on host) due to the wrong SELinux file label (specifically user field).
On the controller that has run bootstrap service:
[root@ip-10-20-139-198 ~]$ ls -alZ /etc/kubernetes
total 16
drwxr-xr-x.  5 root root system_u:object_r:container_file_t:s0   91 Aug 18 03:16 .
drwxr-xr-x. 80 root root system_u:object_r:etc_t:s0            4096 Aug 18 03:13 ..
drwxr-xr-x.  2 root root system_u:object_r:container_file_t:s0  220 Aug 18 03:16 bootstrap-secrets
-rw-r--r--.  1 root root system_u:object_r:container_file_t:s0 1147 Aug 18 03:13 ca.crt
drwxr-xr-x.  3 root root system_u:object_r:container_file_t:s0   19 Aug 18 03:12 cni
-rw-r--r--.  1 root root system_u:object_r:container_file_t:s0 1815 Aug 18 03:11 kubeconfig
drwxr-xr-x.  2 root root system_u:object_r:container_file_t:s0   96 Aug 18 03:16 manifests

On the controllers that don't run bootstrap service:
[root@ip-10-20-144-57 scoop-ops]# ls -alZ /etc/kubernetes
total 16
drwxr-xr-x.  5 root root system_u:object_r:container_file_t:s0       91 Aug 18 03:16 .
drwxr-xr-x. 80 root root system_u:object_r:etc_t:s0                4096 Aug 18 03:13 ..
drwxr-xr-x.  2 root root unconfined_u:object_r:container_file_t:s0  220 Aug 18 03:16 bootstrap-secrets
-rw-r--r--.  1 root root system_u:object_r:container_file_t:s0     1147 Aug 18 03:13 ca.crt
drwxr-xr-x.  3 root root system_u:object_r:container_file_t:s0       19 Aug 18 03:13 cni
-rw-r--r--.  1 root root system_u:object_r:container_file_t:s0     1815 Aug 18 03:11 kubeconfig
drwxr-xr-x.  2 root root system_u:object_r:container_file_t:s0       96 Aug 18 03:16 manifests

See the difference in user field (system_u vs unconfined_u). This PR updates the user field to system_u on all controllers. On aws/fedora-coreos, I've verified this fixes all the permission denials on files under /etc/kubernetes/secrets (container) from kube-apiserver, kube-scheduler, and kube-controller-manager containers.

I realized I only tested on v1.18.6. So I launched another testing cluster on v1.18.8 and found additional type label needs to be fixed as well.
[scoop-ops@ip-10-20-139-173 ~]$ ls -alZ /etc/kubernetes/bootstrap-secrets
total 44
drwxr-xr-x. 2 root root system_u:object_r:container_file_t:s0  220 Aug 20 00:18 .
drwxr-xr-x. 5 root root system_u:object_r:container_file_t:s0   91 Aug 20 00:18 ..
-rw-r--r--. 1 root root system_u:object_r:container_file_t:s0 1408 Aug 20 00:17 apiserver.crt
-rw-r--r--. 1 root root system_u:object_r:container_file_t:s0 1680 Aug 20 00:17 apiserver.key
-rw-r--r--. 1 root root system_u:object_r:container_file_t:s0 1148 Aug 20 00:17 ca.crt
-rw-r--r--. 1 root root system_u:object_r:container_file_t:s0 1680 Aug 20 00:17 ca.key
-rw-r--r--. 1 root root system_u:object_r:container_file_t:s0 1120 Aug 20 00:17 etcd-client-ca.crt
-rw-r--r--. 1 root root system_u:object_r:container_file_t:s0 1331 Aug 20 00:17 etcd-client.crt
-rw-r--r--. 1 root root system_u:object_r:container_file_t:s0 1680 Aug 20 00:17 etcd-client.key
-rw-r--r--. 1 root root system_u:object_r:container_file_t:s0 5774 Aug 20 00:17 kubeconfig
-rw-r--r--. 1 root root system_u:object_r:container_file_t:s0 1676 Aug 20 00:17 service-account.key
-rw-r--r--. 1 root root system_u:object_r:container_file_t:s0  451 Aug 20 00:17 service-account.pub

On the controllers that don't run bootstrap service:
[scoop-ops@ip-10-20-146-19 ~]$ ls -alZ /etc/kubernetes/bootstrap-secrets
total 44
drwxr-xr-x. 2 root root system_u:object_r:container_file_t:s0  220 Aug 20 00:14 .
drwxr-xr-x. 5 root root system_u:object_r:container_file_t:s0   91 Aug 20 00:14 ..
-rw-r--r--. 1 root root system_u:object_r:user_home_t:s0      1408 Aug 20 00:14 apiserver.crt
-rw-r--r--. 1 root root system_u:object_r:user_home_t:s0      1680 Aug 20 00:14 apiserver.key
-rw-r--r--. 1 root root system_u:object_r:user_home_t:s0      1148 Aug 20 00:14 ca.crt
-rw-r--r--. 1 root root system_u:object_r:user_home_t:s0      1680 Aug 20 00:14 ca.key
-rw-r--r--. 1 root root system_u:object_r:user_home_t:s0      1120 Aug 20 00:14 etcd-client-ca.crt
-rw-r--r--. 1 root root system_u:object_r:user_home_t:s0      1331 Aug 20 00:14 etcd-client.crt
-rw-r--r--. 1 root root system_u:object_r:user_home_t:s0      1680 Aug 20 00:14 etcd-client.key
-rw-r--r--. 1 root root system_u:object_r:user_home_t:s0      5774 Aug 20 00:14 kubeconfig
-rw-r--r--. 1 root root system_u:object_r:user_home_t:s0      1676 Aug 20 00:14 service-account.key
-rw-r--r--. 1 root root system_u:object_r:user_home_t:s0       451 Aug 20 00:14 service-account.pub

This is similar to the race in #708, but more limited. The label has a chance of appearing on non-bootstrap controllers in multi-controller clusters on the first boot from disk. Its also resolved on any restart of the kubelet.service (service, reboot, auto-update) for the duration of a cluster lifecycle. The randomness of appearance stems from the same race with the first kubelet start.
Manually setting the context like this should eliminate its chance of happening during this window. Thanks


Sign In Page UI is not responsive

Now I m gone to change in block check the master branch for that and we will work in clean_architecture branch

Now I m gone to change in block check the master branch for that and we will work in clean_architecture branch


Output colors with say

Games cry out for color / format options. Perhaps use the following API with say:
say(something, fg="red", bg="white")
There is colorama that would help implement this, but if you wanted to keep it so that users could just use adventurelib.py in their own projects, maybe have to implement ourselves?

Working on it, almost done 🙂


Lower OS support

This would require making another OnboardingProvider that uses ObservableObject instead of @Observable.
We would also need to remove the Observable from the protocol.
I would prefer to keep the current solution for apps using the latest OS.

Lower OS support would be great. My app currently has iOS 16/macOS 13 as the minimum version.
Also happy new year 🎉


HiveError: Could not read value from box. Maybe your box is corrupted.

Hi. I'm getting this exception in production, but I can't figure out why it is happening and I haven't been able to reproduce it in dev. Do you have any insights into when this exception is thrown?

It appears it happens when line 49 tries to access my box.

I'd appreciate any tips you think might be relevant.
I've asked the same question to the dio_cache_manager dev, and he thinks you guys might be able to help.

I am also getting similar error while running my test in github ci windows box:
Failed to put vel: [[1691177347124887552]NO₂, [1691177349456920577]NO₂, [1691177350023151616]NO₂] pair in $nitrite_index|Employee|employeeNote.text|Fulltext
 #0      StorageBackendVm.readValue.<anonymous closure> (package:hive/src/backend/vm/storage_backend_vm.dart:114:9)
 <asynchronous suspension>
 #1      StackZoneSpecification._registerUnaryCallback.<anonymous closure> (package:stack_trace/src/stack_zone_specification.dart:124:15)
 <asynchronous suspension>

 Caused by: HiveError: Could not read value from box. Maybe your box is corrupted.

I am using LazyBox to store my data.
This error is intermittent and it is happening only in github ci windows box. In my Windows (x64) dev machine, I am not seeing this issue, also neither in my Ubuntu (x64) or MacOS (m2) machine. Hope this info helps.

I'm also encountering this same issue,  using dio_cache_manager with flutter_map. Did you ever solve this?

We are also seeing this error, here is our stacktrace:
HiveError: HiveError: Could not read value from box. Maybe your box is corrupted.
  File "storage_backend_vm.dart", line 114, in StorageBackendVm.readValue.<fn>
  File "<asynchronous suspension>"
  File "future_impl.dart", line 41, in _AsyncCompleter.complete
  File "<asynchronous suspension>"
  File "lazy_box_impl.dart", line 32, in LazyBoxImpl.get
  File "<asynchronous suspension>"
  File "dio_cache_interceptor.dart", line 186, in DioCacheInterceptor._loadCacheResponse
  File "<asynchronous suspension>"
  File "dio_cache_interceptor.dart", line 47, in DioCacheInterceptor.onRequest

We also use Hive in other parts of our app but the stacktrace is always from the dio_cache_interceptor

same here we only got the issue while using dio_cache_interceptor
and also is always

dio_cache_interceptor_hive_store.dart

I will now try to create the HiveCacheStore from dio_cache_interceptor soon as the app starts. Previously we only created it when we needed it and my theory is that the HiveCacheStore clean() method is still running while it it is already being used, leading to this error as the value is removed and accessed at the same time.

I have the same issue reported via sentry many times

Hive: 2.2.3

Update:
I got the same bug after deleting app, reinstalling it.


aj-snapshot: init 0.9.6

It's a tool to save the jack connections.
I tested it with nix-build -A aj-snapshot
It's my first pull-request to the nixpkgs repository, so I'm very open for improvements.
@magnetophon @henrytill maybe you as musnix can approve or merge the pull-request.
Thanks

Thanks!
I don't have commit rights, but I'm sure @henrytill or @cillianderoiste will ahve a look.

thanks @pSub I've done your changes.
I squashed everything to one commit it that is Ok.

Thanks, looks good now.


Climate bug with graph

Home Assistant release (hass --version): 0.30.1
Python release (python3 --version): 3.4
Component/platform: climate
Description of problem:
Statistic is wrong:

I see that only on auto mode

Duplicate of #3409


Run RuboCop as part of bundle exec rake defaults

This is a prerequisite for being able to move more of our apps to
GitHub Actions. We want one single step bundle exec rake that runs
everything. This ensures parity between local dev and what CI runs
(something that we don't always have now).

https://trello.com/c/5Gob6WUL/147-for-everyone-ensure-that-rubocop-runs-as-part-of-bundle-exec-rake-as-one-of-the-default-tasks

Also, Metrics/BlockLength is a cop that's disabled upstream in the
gem, so we don't need to do so here as well.

This seems to be missing?

This seems to be missing?

Yeah sorry, too much copy pasting between commit messages. This is irrelevant.


Disable 1.10 e2e jobs running by default

They keep failing due to some minikube issue. Disabling for now.

cc @kragniz @wallrj


Minor styling tweaks to plugin search

Changes
No functionality changes; just some minor type hierarchy tweaks and a new icon
Before

After

Testing

Docs

LGTM! Thanks for taking a look


DOC: add RatingStars.jsx

What's wrong with the existing documentation
add RatingStars.jsx to components .
A component to display and handle ratings using star icons. Useful for reviews or rating food items and canteens.
Add ScreenShots
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

We are already having this!


[Feature] Add the ability for a user to have a completely custom button

https://gyazo.com/84d86e15ee93a18ddabc4ac962645fe1
let the user add another button to the presence / allow full customization of this button.

Ability to tell it all states online/idle etc.
Allow it to be enabled when user is working and disabled when the user is not.
Allow a setting to do with buttons when there are ignore repo / organisation / folder. Should it maintenance the two buttons or should it go back to one

gonna plan on hw to put the config and stuff, we need to have a condition where user is in a git project or not, it gonna be a real mess, we need better way to handle config for this.


Document that jQuery is required

I removed jQuery from my app, and got a bunch of errors.

Isn't adding jquery as dependency a cleaner/userfriendly solution for this?

Could be!

Thanks @stubailo for the catch.


Can't rename a model using instructions

I followed the instructions under "Rename a model (API only)", but got the following error:
MlflowException: Method 'rename_registered_model' is unsupported for models in the Unity Catalog. Use the Unity Catalog REST API to rename registered models

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

ID: aff4ad7d-2b12-edcc-5e20-19946ab03d3a
Version Independent ID: aff4ad7d-2b12-edcc-5e20-19946ab03d3a
Content: Manage model lifecycle in Unity Catalog - Azure Databricks
Content Source: databricks/machine-learning/manage-model-lifecycle/index.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

Forgot to include, I'm using mlflow version 2.12.1

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

Thanks for providing feedback that helps improve our documentation. We've created an internal work item (DOC-13751) to address your feedback. The timeline for resolution varies based on resourcing.
#please-close