DBeaver 4.1.0 hangs on auto-complete for large tables

See also "dbeaver hangs on occasion when trying to hint table name after typing '.'  #1699 "
When doing auto-complete on a fieldname: schema.table.  DBeaver will run a query on the database select count(*) from schema.table.
If the table is large (in my case 64Terra records on an IBM Netezza, it will crash the production environment. This is a very high risk for production databases that have very large tables.
Suggest to have the "show row count" feature default turned off or retrieve row count information from the administrative tables of the database. The latter may require having an SQL template on how to do that for each type of database.

You already can disable this:

By the way this option is disabled by default.

It looks like this question was solved. It will be closed. If you think that it is actual just let us know.


Add AlphaMensae's Saturn Mobile Launcher Standalone BDB Version from SpaceDock

This pull request was automatically generated by SpaceDock on behalf of AlphaMensae, to add AlphaMensae's Saturn Mobile Launcher Standalone BDB Version to CKAN.
Mod details:
name = /mod/1706/AlphaMensae%27s%20Saturn%20Mobile%20Launcher%20Standalone%20BDB%20Version
author = AlphaMensae
abstract = The Saturn Mobile Launcher from my Simple Overhaul project, made separate and configured to work with the Saturn V from Bluedog Design Bureau.
license = CC-BY-NC-SA 4.0
Homepage =
description = The Saturn Mobile Launcher from my Simple Overhaul project, made standalone and configured to work with the Saturn V from Bluedog Design Bureau.
The mobile launcher was designed for the Saturn V from my Simple Overhaaul, which is at 64% scale.  It however works rather well with the BDB Saturn V, just needed a few tweaks
and adjustments.
The BDB Saturn V is at a smaller scale, and I didn't rescale the tower, so it's taller than the BDB Saturn V than the real one was.
The launcher can be used with other large rockets, provided they have a free attach node at the bottom of the first or core stage for connecting the launcher base.  The tower and swing arms
can be moved with the offet gizmo for fine-tuning the positioning.
Liftoff demo video:  https://youtu.be/2EDUUWpvTAs
Please direct questions about this pull request to AlphaMensae.

#rebuild


[Help] Respond to incoming event with a result payload?

My server emits an event and is expecting a return value from the receiving client. I see there is emit_with_ack(), but can I somehow send a payload when processing an incoming event?

Yes, looking at the function signature, the parameter event takes an FnMut(Payload, Socket). The Payload is the payload send by the server and the Socket is an instance of the socket. That way you could use the socket inside the Callback, e.g. like that:
let mut socket = SocketBuilder::new("http://localhost:4200")
    .on("foo", |payload: Payload, _| println!("Received: {:#?}", payload))
    .connect()
    .expect("connection failed");

let ack_callback = |message: Payload, my_socket: Socket| {
    match message {
        Payload::String("send me a message!!!") => my_socket.emit("foo", "answer is 42".into()),
        Payload::String(s) => println!("{}", s),
        _ => (),
   }
};

let payload = json!({"token": 123});
socket.emit_with_ack("foo", payload, Duration::from_secs(2), ack_callback).unwrap();

Does this solve your issue? Or did you mean something else?


Moving aliasing special properties of ngRepeat from ngInit to ngRepeat

Currently the only one appropriate use of ngInit is aliasing $index and other special properties of ngRepeat.
I'd like suggest moving this functionality to ngRepeat.
It could look like:
<li ng-repeat="city in cities track by $index, $index as cityIndex, $middle as isCityMiddle">

Pros:

Aliasing is needed for ngRepeat, not ngInit.

Cons:

Will add more functionality to ngRepeat.
Right now it's one of the biggest directives if LoC is concerned.

Also, just to make writing hello-worlds on plunker a little tougher, removing ngInit entirely could be considered.
Yes, I know I'm crazy, but this could be only done if there are really few hackish solutions which employ ngInit.
Just wanted to know that you guys think of this.

I don't think we should be changing or removing ngInit. It is there and it does a few jobs well, even if it can be abused. Moreover, I now agree with @gsklee that we should moderate the tag line in the docs to something not quite so severe.
Regarding ngRepeat, I am torn...

Adding these extra clauses to the ngRepeat expression is adding too much burden to an already overburdened syntax. For now I think we should stick with ngInit and make the note about it in the docs a bit clearer.

Changed the note in the ngInit docs: 010d9b6853a9d2718b095e4c017c9bd5f135e0b0


new migration process

Working draft
Closes https://github.com/influxdata/docs.influxdata.com/issues/2904

@gshif -- worth reviewing this approach. Particularly as we think about ease of migration from OSS 2 to Enterprise 1

moved this PR to the v2 repo


Support tars RPC framework

Is the Tars ready? @pengys5 @ascrutae . If not, we can support it in 3.1, maybe.


Cluster Overview port 8085 and 8586 are unauthenticated

Affected module
Backend
Describe the bug
Asset which is vulnerable is <IP_ADDRESS>. There is an open port 8085 which is http://<IP_ADDRESS>:8085/ui/#. Redirects to presto cluster overview. Also another port is open 8586 which lets me see internal CPU performance, virtual network distributions using cpu contention, internal network I/O metrics and kernel metrics. http://<IP_ADDRESS>:8586/
To Reproduce

Prestor cluster overview can be visited at http://<IP_ADDRESS>:8085/ui/#
No password is required. Provide username admin, and you can also bruteforce the users to see other clusters.
CPU metrics can be see at http://<IP_ADDRESS>:8586/
Just traverse different options to view different data.

Expected behavior
Both the ports should either be available for internal usage or should have authorization implemented.
Let me know if this is eligible for bug bounty.

Also port 9200/Elasticsearch is open
curl -X GET "<IP_ADDRESS>:9200/_cluster/allocation/explain"
Response:
{"index":"read-me-hacked-by-nightlionsecurity-ure4zd","shard":0,"primary":false,"current_state":"unassigned","unassigned_info":{"reason":"INDEX_CREATED","at":"2022-03-03T03:42:23.865Z","last_allocation_status":"no_attempt"},"can_allocate":"no","allocate_explanation":"cannot allocate because allocation is not permitted to any of the nodes","node_allocation_decisions":[{"node_id":"OijEb8tCSWOqANrE3zE-4A","node_name":"elasticsearch","transport_address":"<IP_ADDRESS>:9300","node_attributes":{"ml.machine_memory":"1073741824","xpack.installed":"true","transform.node":"true","ml.max_open_jobs":"20"},"node_decision":"no","weight_ranking":1,"deciders":[{"decider":"same_shard","decision":"NO","explanation":"a copy of this shard is already allocated to this node [[read-me-hacked-by-nightlionsecurity-ure4zd][0], node[OijEb8tCSWOqANrE3zE-4A], [P], s[STARTED], a[id=pisk608MRoOVSl0kZpgWow]]"}]}]}%

Also this kafka stream is unauthenticated at <IP_ADDRESS>:9092
This command: kafka-topics --bootstrap-server <IP_ADDRESS>:9092 --list --exclude-internal
Sample response:
RAY-APIs
_confluent-command
_confluent-controlcenter-6-1-0-1-AlertHistoryStore-changelog
_confluent-controlcenter-6-1-0-1-AlertHistoryStore-repartition
_confluent-controlcenter-6-1-0-1-Group-ONE_MINUTE-changelog
_confluent-controlcenter-6-1-0-1-Group-ONE_MINUTE-repartition
_confluent-controlcenter-6-1-0-1-Group-THREE_HOURS-changelog
_confluent-controlcenter-6-1-0-1-Group-THREE_HOURS-repartition
_confluent-controlcenter-6-1-0-1-KSTREAM-OUTEROTHER-0000000106-store-changelog
_confluent-controlcenter-6-1-0-1-KSTREAM-OUTEROTHER-0000000106-store-repartition
_confluent-controlcenter-6-1-0-1-KSTREAM-OUTERTHIS-0000000105-store-changelog
_confluent-controlcenter-6-1-0-1-KSTREAM-OUTERTHIS-0000000105-store-repartition
_confluent-controlcenter-6-1-0-1-MetricsAggregateStore-changelog
_confluent-controlcenter-6-1-0-1-MetricsAggregateStore-repartition
_confluent-controlcenter-6-1-0-1-MonitoringMessageAggregatorWindows-ONE_MINUTE-changelog
_confluent-controlcenter-6-1-0-1-MonitoringMessageAggregatorWindows-ONE_MINUTE-repartition
_confluent-controlcenter-6-1-0-1-MonitoringMessageAggregatorWindows-THREE_HOURS-changelog
_confluent-controlcenter-6-1-0-1-MonitoringMessageAggregatorWindows-THREE_HOURS-repartition
_confluent-controlcenter-6-1-0-1-MonitoringStream-ONE_MINUTE-changelog
_confluent-controlcenter-6-1-0-1-MonitoringStream-ONE_MINUTE-repartition
_confluent-controlcenter-6-1-0-1-MonitoringStream-THREE_HOURS-changelog
_confluent-controlcenter-6-1-0-1-MonitoringStream-THREE_HOURS-repartition
_confluent-controlcenter-6-1-0-1-MonitoringTriggerStore-changelog
_confluent-controlcenter-6-1-0-1-MonitoringTriggerStore-repartition
_confluent-controlcenter-6-1-0-1-MonitoringVerifierStore-changelog
_confluent-controlcenter-6-1-0-1-MonitoringVerifierStore-repartition
_confluent-controlcenter-6-1-0-1-TriggerActionsStore-changelog
_confluent-controlcenter-6-1-0-1-TriggerActionsStore-repartition
_confluent-controlcenter-6-1-0-1-TriggerEventsStore-changelog
_confluent-controlcenter-6-1-0-1-TriggerEventsStore-repartition
_confluent-controlcenter-6-1-0-1-actual-group-consumption-rekey
_confluent-controlcenter-6-1-0-1-aggregate-topic-partition-store-changelog
_confluent-controlcenter-6-1-0-1-aggregate-topic-partition-store-repartition
_confluent-controlcenter-6-1-0-1-aggregatedTopicPartitionTableWindows-ONE_MINUTE-changelog
_confluent-controlcenter-6-1-0-1-aggregatedTopicPartitionTableWindows-ONE_MINUTE-repartition
_confluent-controlcenter-6-1-0-1-aggregatedTopicPartitionTableWindows-THREE_HOURS-changelog
_confluent-controlcenter-6-1-0-1-aggregatedTopicPartitionTableWindows-THREE_HOURS-repartition
_confluent-controlcenter-6-1-0-1-cluster-rekey
_confluent-controlcenter-6-1-0-1-expected-group-consumption-rekey
_confluent-controlcenter-6-1-0-1-group-aggregate-store-ONE_MINUTE-changelog
_confluent-controlcenter-6-1-0-1-group-aggregate-store-ONE_MINUTE-repartition
_confluent-controlcenter-6-1-0-1-group-aggregate-store-THREE_HOURS-changelog
_confluent-controlcenter-6-1-0-1-group-aggregate-store-THREE_HOURS-repartition
_confluent-controlcenter-6-1-0-1-group-stream-extension-rekey
_confluent-controlcenter-6-1-0-1-metrics-trigger-measurement-rekey
_confluent-controlcenter-6-1-0-1-monitoring-aggregate-rekey-store-changelog
_confluent-controlcenter-6-1-0-1-monitoring-aggregate-rekey-store-repartition
_confluent-controlcenter-6-1-0-1-monitoring-message-rekey-store
_confluent-controlcenter-6-1-0-1-monitoring-trigger-event-rekey
_confluent-ksql-default__command_topic
_confluent-license
_confluent-metrics
_confluent-monitoring
_confluent-telemetry-metrics
_confluent_balancer_api_state
_confluent_balancer_broker_samples
_confluent_balancer_partition_samples
_schemas
com.getray.tribenaija
connect-configs
connect-offsets
connect-statuses
default_ksql_processing_log

@zipponnova we do know these clusters are insecure, they are there for testing only. We are not going to put extra effort mark them secure at this point.


Small optimizations + Some Bugfixes + Read from files with Lock + Deprecation of SleekDB class

[FIXED] bug in join algorithm, removed direct property access.
[UPDATED]
findStoreDocument method to use lock when retrieving file content;
getUseCache to _getUseCache and getDefaultCacheLifetime to _getDefaultCacheLifetime to show that its mainly for internal use.
[DEPRECATED] SleekDB class

@Timu57
🎉 🍻

@Timu57
🎉 🍻


Change owner of /opt/openshift in base image

This will allow to drop the chown from all Dockerfiles (as long as you copy the files in the directory after you drop to USER 1001.
This can be merged without any harm (as the existing images will just do chown anyway. I'll be removing the chown in the other PR (namespace fix). So this should go in before that...

LGTM


why so many deprecated libraries

I apologise if this comes across as a silly question but I am new to react.
This being a starter kit and all, why does it use so many deprecated libraries?
npm WARN deprecated<EMAIL_ADDRESS>This version of React Navigation is no longer supported. Please upgrade to at least React Navigation 4.
npm WARN deprecated<EMAIL_ADDRESS>This version of React Navigation Stack is no longer supported. Please upgrade to 2.x.x. See https://reactnavigation.org/docs/4.x/upgrading-from-3.x#react-navigation-stack for instructions.
npm WARN deprecated<EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated<EMAIL_ADDRESS>this library is no longer supported
npm WARN deprecated<EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated<EMAIL_ADDRESS>fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.

The error messages clearly specify what new libraries to use. Should not a starter template, at least, not have deprecated versions?
(I am not trying to be lazy. I am sure I will update the code to suit my requirements. Just curious why this is how it is in the first place)

Closing as this as no longer necessary. I realize now, armed with more experience with node JS in general, this is not a real issue.

Closing as this as no longer necessary. I realize now, armed with more experience with node JS in general, this is not a real issue.


modify json file for cpu total usage testcase.

modify json file for cpu total usage testcase.

@liangchenye  I have modified the json file according the disscussion result this afternoon.


amplify pull --appId xxx --envName staging gets stuck

I've been following the tutorial
https://aws.amazon.com/getting-started/hands-on/build-react-app-amplify-graphql/module-one/
to letter.
Made it through twice, now stuck on third try.
I do 'ampllify configure'
and create a new user (accepting the default), download the .csv with credentials, copy/paste those in the terminal
and accept the creation of defaul profile (what ever that means).
I the try in terminal to 'amplify pull -'appId ....."
And I get to the browser page (in Chrome/Macos) where I should enter my user name and password.
I enter the user name I just created but where do I get the password?
When I created the user there was no place where to add the password.
I cannot as for password reset because this user has no email.
When I created the password there was no place to add an email?
If I try my root user that does not work here.
From AWS management console I cannot find any place where to enter the password nor the email.
I don't recall what I did different on the previous occasions when it succeeded, perhaps something to do with 'amplify role'.
Anyway, help would be appreciated, stuck here for four hours now. This is getting old.
I see a lot of people having difficulties with this.
There is something wrong or missing with this process or instructions.

Thanks for the quick response. No, not custom domains, have difficulties to get to the starting line ;)
I looked through the FAQ but nothing rang a bell.
But many similar issues can be easily googled for.
I have tried many of the suggestions but no luck so far.
Worked for me two experimental projects, third time was not the charm.

Hi @nyholku, thanks for raising. Make sure to click the Open Admin UI(below in orange) button before you run amplify pull ....  This will authenticate you into the Admin UI so that when the page opens you won't be prompted for those credentials.

Thanks! That did the trick!
My bad, it says that on the instructions, however this might be underlined and bolded in red letters cause this is such a crucial step and it is very difficult to understand because of the confusion with the invite users, missing emails and passwords etc. One goes up the creek without a paddle so fast.
Also it is not clear what to do if one wants to run "amplify configure" without creating a new user, could you throw some light on that ?

Great! I agree that it needs to be called out more and have raised with the team.
If you have an existing user configured on your machine with the correct permissions then you should be able to select that profile when amplify init or amplify pull .... This configuration is usually in the same place where your profile/creds are stored for the AWS SDK.


feat: Added customizable parameter for rowsPerPage

I added some parameters, primarily for adjusting rowsPerPage.

Thanks for the PR. PaginatedDataTable2 is currently bloated with all kinds of properties, I don't think it makes sense to keep it growing. The sort of customisations of pagination are supposed to be done via overriding it completely: https://maxim-saplin.github.io/data_table_2/#/paginated2
What I can offer instead to do is create a sample that uses a custom pagination (which is a clone of standard pagaintor) and has the desired customizations

OK, I understand, thanks for your contribution!


Network security workbook

Hi Team,
Thanks for building such a great workbook aligned to bring the all network security data at one place.
I have one concern, in my environment  we have load balancer inbound NAT rules available however the same rules are not getting reflected in the network security dashboard. Could you help me know this behaviour? Also please help me understand why there is no download/export button available for storage accounts. Is it feasible to build that?
Looking forward to hearing from you.
Thank you,
Regards,
Raju.

Hi mpalagir
These workbooks are editable and you can always customize them as per your requirements.
Edit Workbook -> edit the query -> On the Advanced Settings tab -> Show Export to Excel button when not editing.


LP#1668604: Horizon Direct Upload broken with chrome

Is this a feature or a bug?

[ ] Feature (request for enhancement, new functionality)
[x] Bug (something is broken)

Which version of rpc-openstack does this issue relate to?

[x] master
[x] newton-14.0
[ ] mitaka-13.1
[ ] liberty-12.2

Run git log --pretty=oneline | head -n 1 and provide the output below between
the backtick lines:
This is r14.0.0rc2
c261edad57f143b9cfc17e6abd816aecf0a64972 Merge pull request #2062 from antonym/split_process_checks-newton

What happened?
Chrome blocks direct upload to glance because of protocol mismatch
https://bugs.launchpad.net/horizon/+bug/1668604
What were you doing when it happened?
Uploading an image
What did you expect to happen instead of what actually happened?

Do you think the documentation team wants to know about this?

[ ] Yes, and I submitted an issue to Docs issues
[ ] Yes, and I contributed a documentation patch to docs-rpc
[ ] No documentation required for this change

Does your change require a release note?

[ ] Yes, it's a pretty big deal like I am and I've made a reno note!
[ ] Nope, this change has no major impact.

Setting horizon_endpoint_type: publicURL will overcome this issue, assuming the endpoints are correctly configured (glance in this case) and horizon and glance are both using the right HTTP protocol


How to assign values to a tensor?

Say ten is Tensor<Float16> . how do i assign some values to it?
I tried
ten.storage[0,0,0,0] = 0.0

I get
a.swift:118:35: error: cannot convert value of type 'Int' to expected argument type 'Element.Type'
                  ten.storage[0,0,0,0] = 0.0
                                  ^
a.swift:118:42: error: cannot assign value of type 'Double' to subscript of type 'AnyTensorStorage'
                  ten.storage[0,0,0,0] = 0.0

var ten = xxx
ten[0, 0, 0, 0] = 0

However, because it is a struct, and has "copy-on-write" property, it will only change the values on ten, not the value on xxx. That is the crux why in the reader closure, it won't work as expected (and hence why I probably should change the interface to return the tensor instead).

is there any C function I can call, to change the values of the tensor?
Something like i get the mutable pointer to the location of the data, and I write the data in that location.
althought the data location will be at GPU, so will need some function to write at that memory location.

Or for now, could you give me the snippet of the new read function which takes a closure ( String -> Tensor) , and I will add that locally in the s4nnc code.

If you peek into the implementation, you will likely change the implementation like what you suggested. I won't be able to provide a snippet (it probably a bit more involved) at the moment though:
https://github.com/liuliu/s4nnc/blob/main/nnc/Store.swift#L134
Note that the C-struct tensor is mutable, there is no "copy-on-write" semantics, only when it changed and wrapped into AnyTensor, that becomes the case.

Thanks a lot, I had already gone though these. I could not find any ccv function to copy data from one tensor / buffer to another tensor.
I think you should make a function called ccv_nnc_tensor_copy_data , and call that function from ccv_nnc_tensor_read.
actually rename ccv_nnc_tensor_read to ccv_nnc_tensor_read_sqlite.

Yeah, it is probably not obvious, but any data movement should be done with:
ccv_nnc_exec(CMD_DATA_TRANSFER_FORWARD(), 0, TENSOR_LIST(a), TENSOR_LIST(b), 0); // Or CMD_DATATYPE_CONVERSION, or CMD_FORMAT_TRANSFORM

It is not easier in Swift because there is no macros: https://github.com/liuliu/s4nnc/blob/main/nnc/Tensor.swift#L413
To wrap any data into a tensor, you can use ccv_nnc_tensor_new(, , , dataptr).

Actually i added this method
// use to copy data from swift CPU array to MPS GPU tensor
// use to copy data from swift CPU array to MPS GPU tensor
int ccv_nnc_tensor_read_from_buffer(ccv_nnc_tensor_t** const tensor_out, const void * data , size_t n)
{
	ccv_nnc_tensor_t* tensor = *tensor_out;
	if (!tensor){
		printf("this should not happen because read is being called after compile, so swift will already create a tensor before calling this \n ")
	}
	mpmemcpy(tensor->data.u8, tensor->dataof, tensor->info.type, data, 0, CCV_TENSOR_CPU_MEMORY, n );
}

how do i i call this function from my closure, where i have ten

Wow, i had to change the read function, now it works fine.


Update contribute-icons text

Update Contribution Process section as per issue https://github.ibm.com/brand/bxd/issues/80

@janchild please review. thanks!


TypeScript example

Hi @aeneasr
I'm happy to see this happening.
What would be the right place for a TypeScript sister or brother project of this implementation? Would you put it into a branch or a separate repo?

Hi there, actually I will be writing this in typescript :) Reworked this already locally!

Sounds great! :)


JEP 9 - Boolean expressions

This jep adds improved boolean expressions and filters to JMESPath.
High level summary is it adds:

And expression: a && b
Not expressions: !is_admin
Parens: (a || b) && c

In addition to top level expressions, you can also use them in filter expressions: Users[? is_admin && !new_account]
Will link jmespath.test updates and JEP 9 implementations to the tracking PR.

Last call for feedback.  I think as far changes go, this is a pretty straightforward change that fleshes out the partial boolean support that JMESPath previously had.
If you want something more concrete to look at, here at the proposed compliance tests for this change: https://github.com/jmespath/jmespath.test/commit/f8f678ea9534178cc4ed43c85048b884a8b84c61
Note: I'll update the compliance tests to not use the outdated syntax of:
`foo`

Nice work. :shipit:

Ok, I'll mark this as accepted and merge.


feat: prevent automerging pre-1.0.0 versions

Changes:

Add "matchCurrentVersion": "!/^0/", to our "Automerge non-major updates" rule

Context:
Renovate recently automerged a pre-1.x update:

https://github.com/renovatebot/renovate/pull/23598

I expected us to block updates like these, because of this quote from our docs: [^1]

The matchCurrentVersion setting above is a rule to exclude any dependencies which are pre-1.0.0 because those can make breaking changes at any time according to the SemVer spec.

So I copy/pasted the code into our own config. 🙃 But maybe we have good reasons to keep things as they are?
[^1]: Renovate docs, automerge non-major updates

we don't need that, because we have good tests which will catch any errors.

Are you sure about that? It's probably easy to miss some stuff by accident, and then automerge a broken update.
Or do you think most of our key dependencies are already fully SemVer stable, so the chance of merging in a broken update is low?

as far as I know only the hcl2json is the only dependency which is lower than 1.0

Should I add a special rule just for that one package then?
Or do you want to close this PR, and leave things as they are now?

let's leave as is


Fix schema filter name collision bug

This PR fixes an issue with integrations containing similar names (ie. Google Analytics and Google Analytics 4) having their schema filters applied incorrectly. It updates the filters to compare the schema filter name (which uses the creation name of the integration) with the creationName field in the remote plugin.

[x] I've included a changeset (psst. run yarn changeset. Read about changesets here).

@danieljackins ugh, I see a weird BK error.  Any idea what's going on?

@danieljackins looks good but ugh, I see a weird BK error that seems unrelated to this PR. Any idea what's going on?

I think buildkite is/was having some issues, I saw some others with the same problem


Implement filetop gadget

This PR adds a new new filetop gadget from BCC. In this case only the BPF program is reused the the control plane is reimplemented in golang.
How to test:
Use the CLI with the different options provided. Generate IO operations in the interested pods to see some events.
$ ./kubectl-gadget filetop

TODO:

[x] Better way to clear the screen
[x] How to pass errors back to caller in the tracer package?
[x] Use pkg/types.Event
[x] Add json tags to event
[x] Pass parameters to the tracer (depends on https://github.com/kinvolk/inspektor-gadget/issues/420)

TODO (future PRs):

[ ] Create guide
[ ] Pass mount ns map as map instead of string (once https://github.com/cilium/ebpf/issues/517 and https://github.com/cilium/ebpf/issues/515 are fixed)

It's ready to review. There are still some things that could be improved but it's already a too big PR that I'd like to defer them for another PRs.

I'll implement some more options now that https://github.com/kinvolk/inspektor-gadget/pull/439 is merged.

I implemented support for some options. PR is ready for review again.

CI is finally passing. Can I get a review on this please? @blanquicet @eiffel-fl

Can I get a final review on this please @blanquicet @eiffel-fl ? Thanks!


[Bug] Remove the discord link section in the readme

The link in the discord section of the readme is not the right link for this repo.  Make changes immediately. Add the greeting workflows for the contributors.

@tushargupta1504 hi i am the owner of the discord server mentioned in your readme
Please remove it from your readme as the contributors are getting confused

Made a pr for this issue #547

I would like to work on this issue. Could you please assign me this task

I would like to work on this issue. Could you please assign me this task
This issue has been solved 1 month ago.


Fix bug in<EMAIL_ADDRESS>

fixes bug introduced in #17
hardcode main steps, because steps-parameter defaults can not use parameter values themselfs; see also here

regarding no-/single-/double-quotes:
i dont have a strong opinion nor experience whats best
double quotes does some escaping (e.g. \n becomes newline).
if we have a shared practice i gladly apply it. but it didnt seem to be the case from what i saw


Cannot start kitematic on Manjaro Linux: Error: connect ENOENT /var/run/docker.sock

Expected behavior
Start or give me a useful error message so I can troubleshoot the issue.
Actual behavior
Loading Kitematic gives me a setup error:
We're Sorry!
There seems to have been an unexpected error with Kitematic:
Error: connect ENOENT /var/run/docker.sock

Information about the Issue
Running on Manjaro linux installed through the AUR. Changed .bashrc and .bash_profile to point to docker machine. Both contain:
export DOCKER_TLS_VERIFY="1"
export DOCKER_HOST="tcp://<IP_ADDRESS>:2376"
export DOCKER_CERT_PATH="/home/user/.docker/machine/machines/default"
export DOCKER_MACHINE_NAME="default"

Steps to reproduce the behavior

Install Kitematic with pamac or yaourt
Start Kitematic
See error

Shouldn't you have docker installed natively for Manjaro Linux?
Kitematic assumes that Docker is running locally on Linux and not under a virtualbox setup.

Your correct, natively it works without boot2docker. Problem solved.


POC: maintain only one setup for dev server in angular example

Issue
We currently have a second development pipeline (Webpack based) because the Angular CLI approach was not able to handle path routing. This is not wanted anymore because of the additional maintenance efforts required and the unnecessary complexity for Luigi users and contributors.
ToDo
Use just one development pipeline for the angular example that supports both path and hash routing. We want to keep (if possible) the Angular CLI pipeline and add support for path routing there. It could be that the limitations found in earlier versions of Angular CLI have already been overcome (look here).

Okay, I have to confirm my defeat here :(
I managed to make it working when you are logged-in. If you're not, it does some kind of routing loop.
What I did:
<base href="/"> -> sampleapp.html
providers: [
    LuigiContextService,
    { provide: LocationStrategy, useClass: HashLocationStrategy }
  ],

and necessary imports of course -> app.module.ts
leave useHash: true in app-routing.module.ts

The original problem to solve with Angular CLI was being able to reload the page when using path routing

My findings

PathRewrite proxy didn't work (tried many configs)
Ngx build plus didn't work. I tried it with:

nearly exactly the same webpack.conf.js which we currently use with webpack
only historyApiFallback with different configs
standard webpack config for Angular

Sadly, it was always redirecting to root when I entered any valid url (or refreshed current page).

I accidently created a duplicate of this. Duplicate of #287


ChatBedrockConverse compatibility issue

It's working fine with ChatOpenAI but it seems not compatible with ChatBedrockConverse, any help on that ?
 File "/usr/local/lib/python3.12/site-packages/langgraph/pregel/__init__.py", line 1477, in astream
    async for _ in runner.atick(
  File "/usr/local/lib/python3.12/site-packages/langgraph/pregel/runner.py", line 194, in atick
    _panic_or_proceed(
  File "/usr/local/lib/python3.12/site-packages/langgraph/pregel/runner.py", line 273, in _panic_or_proceed
    raise exc
  File "/usr/local/lib/python3.12/site-packages/langgraph/pregel/retry.py", line 102, in arun_with_retry
    await task.proc.ainvoke(task.input, config)
  File "/usr/local/lib/python3.12/site-packages/langgraph/utils/runnable.py", line 453, in ainvoke
    input = await asyncio.create_task(coro, context=context)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/langgraph/pregel/__init__.py", line 1588, in ainvoke
    async for chunk in self.astream(
  File "/usr/local/lib/python3.12/site-packages/langgraph/pregel/__init__.py", line 1477, in astream
    async for _ in runner.atick(
  File "/usr/local/lib/python3.12/site-packages/langgraph/pregel/runner.py", line 130, in atick
    await arun_with_retry(t, retry_policy, stream=self.use_astream)
  File "/usr/local/lib/python3.12/site-packages/langgraph/pregel/retry.py", line 99, in arun_with_retry
    async for _ in task.proc.astream(task.input, config):
  File "/usr/local/lib/python3.12/site-packages/langgraph/utils/runnable.py", line 576, in astream
    async for chunk in aiterator:
  File "/usr/local/lib/python3.12/site-packages/langchain_core/runnables/base.py", line 1455, in atransform
    async for ichunk in input:
  File "/usr/local/lib/python3.12/site-packages/langchain_core/runnables/base.py", line 1018, in astream
    yield await self.ainvoke(input, config, **kwargs)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/langgraph/utils/runnable.py", line 236, in ainvoke
    ret = await asyncio.create_task(coro, context=context)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/langchain_core/runnables/config.py", line 588, in run_in_executor
    return await asyncio.get_running_loop().run_in_executor(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/langchain_core/runnables/config.py", line 579, in wrapper
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/trustcall/_base.py", line 250, in create_extractor
    _Extract(
  File "/usr/local/lib/python3.12/site-packages/trustcall/_base.py", line 469, in __init__
    self.bound_llm = llm.bind_tools(
                     ^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/langchain_aws/chat_models/bedrock_converse.py", line 546, in bind_tools
    return self.bind(tools=_format_tools(tools), **kwargs)
                           ^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/langchain_aws/chat_models/bedrock_converse.py", line 922, in _format_tools
    spec = convert_to_openai_function(tool)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/langchain_core/utils/function_calling.py", line 398, in convert_to_openai_function
    raise ValueError(msg)

ValueError: Unsupported function

{'type': 'function', 'function': { ... pydantic model definition ...}

Functions must be passed in as Dict, pydantic.BaseModel, or Callable. If they're a dict they must either be in OpenAI function format or valid JSON schema with top-level 'title' and 'description' keys.

Many thks, really appreciate this lib :)

@arthberman
I believe the problem seems to be that trustcall is sending the tool in the open ai function format (with type=function, and function keys), not directly as the base model, which fails the validation in convert_to_openai_function.  Here is the relevant trustcall code.
https://github.com/hinthornw/trustcall/blob/dc5e634beae7f4334dc50f715f0712c75c8cb7c7/trustcall/_base.py#L469-L482
Here is a small change to _format_tools in ChatBedrockConverse, that should fix the error. I still see some keys with 'UNKNOWN' values in response, so we might need to look at this more deeply.
def _format_tools(
    tools: Sequence[Union[Dict[str, Any], TypeBaseModel, Callable, BaseTool],],
) -> List[Dict[Literal["toolSpec"], Dict[str, Union[Dict[str, Any], str]]]]:
    formatted_tools: List = []
    for tool in tools:
        if isinstance(tool, dict) and "toolSpec" in tool:
            formatted_tools.append(tool)
        else:
            if isinstance(tool, dict) and "function" in tool:
                tool = tool["function"]
            spec = convert_to_openai_function(tool)
            if not spec["description"]:
                spec["description"] = spec["name"]
            spec["inputSchema"] = {"json": spec.pop("parameters")}
            formatted_tools.append({"toolSpec": spec})
    return formatted_tools

Here is the output after the change.
pertinent_user_preferences=UserPreferences(communication_preferences=CommunicationPreferences(telegram=TelegramPreferences(preferred_encoding=[OutputFormat(preference='Morse code', sentence_preference_revealed='Customer prefers Morse code for the telegram.')], favorite_telegram_operators=[OutputFormat(preference='<UNKNOWN>', sentence_preference_revealed='No specific favorite telegram operator mentioned.')], preferred_telegram_paper=[OutputFormat(preference='Daredevil', sentence_preference_revealed="Customer agrees to use 'Daredevil' paper for the telegram.")]), morse_code=MorseCode(preferred_key_type=[OutputFormat(preference='straight key', sentence_preference_revealed='Customer loves using a straight key for Morse code.')], favorite_morse_abbreviations=[OutputFormat(preference='<UNKNOWN>', sentence_preference_revealed='No favorite Morse abbreviations mentioned.')]), semaphore=Semaphore(preferred_flag_color=[OutputFormat(preference='<UNKNOWN>', sentence_preference_revealed='No semaphore flag color preference mentioned.')], semaphore_skill_level=[OutputFormat(preference='<UNKNOWN>', sentence_preference_revealed='No semaphore skill level mentioned.')])), trust_fall_preferences=TrustFallPreferences(preferred_fall_height=[OutputFormat(preference='higher', sentence_preference_revealed='Customer is ready for a higher fall.')], trust_level=[OutputFormat(preference='<UNKNOWN>', sentence_preference_revealed='No specific trust level mentioned, but customer seems confident in trying a higher fall.')], preferred_catching_technique=[OutputFormat(preference='diamond formation', sentence_preference_revealed='Customer prefers the diamond formation for catching.')]))

@3coins
Will the update of ChatBedrockConverse be pushed on the next langchain-aws release ? Is it planned to fix the "" fields ?

I use "llama3.2:3b-instruct-fp16" with ChatOllama with provided samples in package , but  there is errors:
AttributeError: 'ExtractionState' object has no attribute 'tool_call_id'
`from trustcall import create_extractor
llm = llm_prodiver(Model_Type.LLAMA32FP16,False)
bound = create_extractor(
llm,
tools=[UserInfo,Preferences],
tool_choice="TelegramAndTrustFallPreferences",
)
msg = "I'm Bob, 25 years old, and I love pizza and sushi"
msg = "Hi, my name is Arthur"
msg = "Hi, my name is Arthur, 47 years old"
msg = "I love pizza"
result = bound.invoke(
{
"messages":[
( "system",
"Extract all the user's information and preferences"
"from the conversation below using parallel tool calling."
),
(
"human",
msg
)
]
}
)
result["responses"]`
could anyone help me?

@3coins
Seems fixed with latest PR aws[patch]: bind tools in openai format #267 on langchain-aws package
Continue to investigate for few hours before closing this issue


Windows 10

I have installed the new version of Windows 10 and I'm having problems getting putio-automator to install.
pip install putio-automator
Collecting pyinotify==0.9.6 (from putio-automator)
Using cached pyinotify-0.9.6.tar.gz
Complete output from command python setup.py egg_info:
inotify is not available on win-amd64
Command "python setup.py egg_info" failed with error code 1 in C:\Users\krash\AppData\Local\Temp\pip-build-n8ast50p\pyinotify\
From what I can find online is that pyinotify-0.9.6 can't be installed in windows? Is there a fix for this or am I screwed? I was planning on using Windows 10 as my main OS now.

Never mind. I found the new Linux Subsystem in Windows 10. It's amazing. Not everything you could hope for but still. I had to go old school and start uploading, downloading with just the putio commands. I can't seem to get docker to start after installing but I'm going to keep trying. In the mean time the putio commands do the job for me.


Rebasing to Optimism Monorepo w/ Parallelized E2E Testing

Rebasing to Optimism Monorepo w/ Parallelized E2E Testing

Fixes Issue N/A
Changes proposed

Updated op-geth, op monorepo, and go-ethereum to most recent versions

Integrated devnet support (i.e, devnet-allocs.sh) from OP Monorepo to support local construction of L1 node genesis resources
Updated go.mod with recent version declarations
Updated E2E tests to reflect updated constructs in op-e2e framework

Updated E2E tests to:

Use event based wait patterns instead of time waiting
Support parallel test execution (overall testing time is now < 60s versus 400s)
Use in-memory alert routing configurations versus file ingestion
Support random port allocations for mock servers and pessimism servers; critical for parallelized execution

Screenshots (Optional)
Note to reviewers

Review Error for adrain-cb @ 2023-10-10 19:40:09 UTC
User failed mfa authentication, see go/mfa-help


Coudn't get balance for some address

Description
I am trying to get the addresses balance using the API /account/address/zrb17mka0cw484es5whq638xkm89msgzczmrwy64dy but this API returns:

www/capnp/zarb.capnp:ZarbServer.getAccount: rpc exception: account not found

Reproduction
How To Reproduce
http://<IP_ADDRESS>:8081/account/address/zrb17mka0cw484es5whq638xkm89msgzczmrwy64dy
What Happened

www/capnp/zarb.capnp:ZarbServer.getAccount: rpc exception: account not found

Expected Behavior
{
  "Address": "zrb17mka0cw484es5whq638xkm89msgzczmrwy64dy",
  "Number": 0,
  "Sequence": 0,
  "Balance":<PHONE_NUMBER>00
}
or at least a catchable JSON error.

@khaninejad
I highly recommend using gRPC service and protofile to have better and smoother API calls which has REST interface available on port 8080 and gRPC service available on port 9090
which returns errors and data in better format even though highly unstable as of PR #223 still is better option for same porpuse
let me know if you gonna switch or how much we need to fix this issue

@khaninejad If an account has not received any transactions yet, it won't be created.
In this case this address probably is the validator address. Validators and accounts are two different objects. A validator might have an account or not and vice versa.
With your permission I closed this issue. Thanks for reporting it.


Implement minecraft direction tweak

#12

It must be merged before being able to use ExtraProperties

This is a fine example of using ExtraProperties

Finally had some time to review it


Bind mounting /mnt/c to /mnt/wsl/c breaks other distros

Environment
Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.20246.0 Microsoft Windows NT 10.0.20246.0

Your Distribution version: Not distribution specific
Whether the issue is on WSL 2 and/or WSL 1: WSL 2

Note also applies to all WSL2 versions (Windows 10 2004 and the backport to 1903 / 1909) - running the test cas in Docker Desktop CI reproduces the issus in all versions.
Steps to reproduce
You need 2 distros to reproduce the issue.
I'll do the repro script with an Ubuntu + Alpine environment

start fresh, with no distro started:

> wsl --shutdown

From Ubuntu bind mount /mnt/c to /mnt/wsl/c: (/mnt/wsl/ prefix is important, it is to make sure it is present in all mount namespaces that mounts the /mnt/wsl shared tmpfs):

> wsl -d Ubuntu -u root mkdir /mnt/wsl/c
> wsl -d Ubuntu -u root mount --bind /mnt/c /mnt/wsl/c

(note that Alpine at this point has not been started, WSL has not initialized its mount namespace)

From Alpine, try to list files from /mnt/c:

> wsl -d Alpine ls /mnt/c

(it is empty)

From Alpine, try to list files from /mnt/wsl/c:

> wsl -d Alpine ls /mnt/wsl/c
ls: /mnt/wsl/c/DumpStack.log.tmp: Permission denied
ls: /mnt/wsl/c/hiberfil.sys: Permission denied
ls: /mnt/wsl/c/pagefile.sys: Permission denied
ls: /mnt/wsl/c/swapfile.sys: Permission denied
$Recycle.Bin               Config.Msi                 Go                         PerfLogs                   Program Files (x86)        System Volume Information  Windows.old                projects
$WinREAgent                Documents and Settings     Intel                      ProcessExplorer            ProgramData                Users                      dell                       temp
Apps                       Drivers                    OneDriveTemp               Program Files              Recovery                   Windows                    dell.sdr                   test-dir

From Alpine, get the actual mountinfo:

> wsl -d Alpine cat /proc/self/mountinfo
165 154 8:32 / / rw,relatime - ext4 /dev/sdc rw,discard,errors=remount-ro,data=ordered
166 165 0:20 /init /init ro,relatime - 9p tools ro,dirsync,aname=tools;fmask=022,loose,access=client,msize=65536,trans=fd,rfd=6,wfd=6
167 165 0:6 / /dev rw,nosuid,relatime - devtmpfs none rw,size=8130228k,nr_inodes=2032557,mode=755
168 167 0:49 / /dev/pts rw,nosuid,noexec,noatime - devpts devpts rw,gid=5,mode=620,ptmxmode=000
169 165 0:16 / /sys rw,nosuid,nodev,noexec,noatime - sysfs sysfs rw
170 169 0:54 / /sys/fs/cgroup rw,nosuid,nodev,noexec,relatime - tmpfs tmpfs rw,mode=755
171 170 0:30 / /sys/fs/cgroup/unified rw,nosuid,nodev,noexec,relatime - cgroup2 cgroup2 rw,nsdelegate
172 170 0:31 / /sys/fs/cgroup/cpuset rw,nosuid,nodev,noexec,relatime - cgroup cgroup rw,cpuset
173 170 0:32 / /sys/fs/cgroup/cpu rw,nosuid,nodev,noexec,relatime - cgroup cgroup rw,cpu
174 170 0:33 / /sys/fs/cgroup/cpuacct rw,nosuid,nodev,noexec,relatime - cgroup cgroup rw,cpuacct
175 170 0:34 / /sys/fs/cgroup/blkio rw,nosuid,nodev,noexec,relatime - cgroup cgroup rw,blkio
176 170 0:18 / /sys/fs/cgroup/memory rw,nosuid,nodev,noexec,relatime - cgroup cgroup rw,memory
177 170 0:35 / /sys/fs/cgroup/devices rw,nosuid,nodev,noexec,relatime - cgroup cgroup rw,devices
178 170 0:36 / /sys/fs/cgroup/freezer rw,nosuid,nodev,noexec,relatime - cgroup cgroup rw,freezer
179 170 0:37 / /sys/fs/cgroup/net_cls rw,nosuid,nodev,noexec,relatime - cgroup cgroup rw,net_cls
180 170 0:38 / /sys/fs/cgroup/perf_event rw,nosuid,nodev,noexec,relatime - cgroup cgroup rw,perf_event
181 170 0:39 / /sys/fs/cgroup/net_prio rw,nosuid,nodev,noexec,relatime - cgroup cgroup rw,net_prio
182 170 0:40 / /sys/fs/cgroup/hugetlb rw,nosuid,nodev,noexec,relatime - cgroup cgroup rw,hugetlb
183 170 0:41 / /sys/fs/cgroup/pids rw,nosuid,nodev,noexec,relatime - cgroup cgroup rw,pids
184 170 0:42 / /sys/fs/cgroup/rdma rw,nosuid,nodev,noexec,relatime - cgroup cgroup rw,rdma
185 165 0:48 / /proc rw,nosuid,nodev,noexec,noatime - proc proc rw
186 185 0:21 / /proc/sys/fs/binfmt_misc rw,relatime - binfmt_misc binfmt_misc rw
187 165 0:50 / /run rw,nosuid,noexec,noatime - tmpfs none rw,mode=755
188 187 0:51 / /run/lock rw,nosuid,nodev,noexec,noatime - tmpfs none rw
189 187 0:52 / /run/shm rw,nosuid,nodev,noatime - tmpfs none rw
190 187 0:53 / /run/user rw,nosuid,nodev,noexec,noatime - tmpfs none rw,mode=755
191 165 0:55 / /usr/lib/wsl/drivers ro,nosuid,nodev,noatime - 9p drivers ro,dirsync,aname=drivers;fmask=333;dmask=222,mmap,access=client,msize=65536,trans=fd,rfd=4,wfd=4
192 165 0:56 / /usr/lib/wsl/lib ro,nosuid,nodev,noatime - 9p lib ro,dirsync,aname=lib;fmask=333;dmask=222,mmap,access=client,msize=65536,trans=fd,rfd=4,wfd=4
193 165 0:19 / /mnt/wsl rw,relatime shared:1 - tmpfs none rw
194 193 0:46 / /mnt/wsl/c rw,noatime shared:2 - 9p drvfsa rw,dirsync,aname=drvfs;path=C:\;uid=1000;gid=1000;metadata;symlinkroot=/mnt/,mmap,access=client,msize=262144,trans=virtio

Note that the c drive is indeed mounted in /mnt/wsl/c but wsl init process "forgot" to mount it into /mnt/c

WSL logs:
Not sure how to grab the /init logs for a given distro (that would really help to know that btw).
Expected behavior
My C drive in Alpine should be accessible from /mnt/c (as well as from /mnt/wsl/c as it has been bind-mounted there from Ubuntu - it is the intended goal of /mnt/wsl: share partial filesystem view accross distros by using bind mounts and shared propagation
Actual behavior
My C drive in Alpine is only accessible from /mnt/wsl/c, not from /mnt/c.
This was discovered by trying to fix https://github.com/docker/for-win/issues/9364

As always, I'm available for any additional info / would gladly help anyway I can

dmesg output:
❯ wsl -d Ubuntu dmesg
[    0.000000] Linux version 4.19.128-microsoft-standard (oe-user@oe-host) (gcc version 8.2.0 (GCC)) #1 SMP Tue Jun 23 12:58:10 UTC 2020
[    0.000000] Command line: initrd=\initrd.img panic=-1 nr_cpus=16 swiotlb=force 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: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
[    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-0x00000003ffffffff] 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: features 0x2e7f, hints 0xa4e24, misc 0xe0bed7b2
[    0.000000] Hyper-V Host Build:20246-10.0-0-0.1
[    0.000000] Hyper-V: LAPIC Timer Frequency: 0x1e8480
[    0.000000] tsc: Marking TSC unstable due to running on Hyper-V
[    0.000000] Hyper-V: Using hypercall for remote TLB flush
[    0.000000] tsc: Detected 2304.008 MHz processor
[    0.000007] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[    0.000008] e820: remove [mem 0x000a0000-0x000fffff] usable
[    0.000010] last_pfn = 0x400000 max_arch_pfn = 0x400000000
[    0.000024] MTRR default type: uncachable
[    0.000024] MTRR fixed ranges disabled:
[    0.000025]   00000-FFFFF uncachable
[    0.000025] MTRR variable ranges disabled:
[    0.000025]   0 disabled
[    0.000025]   1 disabled
[    0.000026]   2 disabled
[    0.000026]   3 disabled
[    0.000026]   4 disabled
[    0.000026]   5 disabled
[    0.000026]   6 disabled
[    0.000027]   7 disabled
[    0.000027] Disabled
[    0.000027] x86/PAT: MTRRs disabled, skipping PAT initialization too.
[    0.000031] CPU MTRRs all blank - virtualized system.
[    0.000032] x86/PAT: Configuration [0-7]: WB  WT  UC- UC  WB  WT  UC- UC
[    0.000034] last_pfn = 0xf8000 max_arch_pfn = 0x400000000
[    0.000043] Using GB pages for direct mapping
[    0.000045] BRK [0x02e00000, 0x02e00fff] PGTABLE
[    0.000045] BRK [0x02e01000, 0x02e01fff] PGTABLE
[    0.000046] BRK [0x02e02000, 0x02e02fff] PGTABLE
[    0.000374] RAMDISK: [mem 0x02e35000-0x02e43fff]
[    0.000376] ACPI: Early table checksum verification disabled
[    0.000421] ACPI: RSDP 0x00000000000E0000 000024 (v02 VRTUAL)
[    0.000424] ACPI: XSDT 0x0000000000100000 000044 (v01 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.000427] ACPI: FACP 0x0000000000101000 000114 (v06 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.000430] ACPI: DSDT 0x00000000001011B8 01E184 (v02 MSFTVM DSDT01   00000001 MSFT 05000000)
[    0.000432] ACPI: FACS 0x0000000000101114 000040
[    0.000433] ACPI: OEM0 0x0000000000101154 000064 (v01 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.000435] ACPI: SRAT 0x000000000011F33C 0003B0 (v02 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.000437] ACPI: APIC 0x000000000011F6EC 0000C8 (v04 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.000442] ACPI: Local APIC address 0xfee00000
[    0.000645] Zone ranges:
[    0.000645]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
[    0.000646]   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
[    0.000647]   Normal   [mem 0x0000000100000000-0x00000003ffffffff]
[    0.000647] Movable zone start for each node
[    0.000648] Early memory node ranges
[    0.000648]   node   0: [mem 0x0000000000001000-0x000000000009ffff]
[    0.000649]   node   0: [mem 0x0000000000200000-0x00000000f7ffffff]
[    0.000649]   node   0: [mem 0x0000000100000000-0x00000003ffffffff]
[    0.000867] Zeroed struct page in unavailable ranges: 353 pages
[    0.000868] Initmem setup node 0 [mem 0x0000000000001000-0x00000003ffffffff]
[    0.000869] On node 0 totalpages: 4161183
[    0.000870]   DMA zone: 59 pages used for memmap
[    0.000871]   DMA zone: 22 pages reserved
[    0.000871]   DMA zone: 3743 pages, LIFO batch:0
[    0.000918]   DMA32 zone: 16320 pages used for memmap
[    0.000919]   DMA32 zone: 1011712 pages, LIFO batch:63
[    0.018887]   Normal zone: 49152 pages used for memmap
[    0.018888]   Normal zone: 3145728 pages, LIFO batch:63
[    0.019460] ACPI: Local APIC address 0xfee00000
[    0.019468] ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
[    0.019683] IOAPIC[0]: apic_id 16, version 17, address 0xfec00000, GSI 0-23
[    0.019686] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.019687] ACPI: IRQ9 used by override.
[    0.019689] Using ACPI (MADT) for SMP configuration information
[    0.019690] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
[    0.019699] [mem 0xf8000000-0xffffffff] available for PCI devices
[    0.019699] Booting paravirtualized kernel on bare hardware
[    0.019701] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:<PHONE_NUMBER>2750000 ns
[    0.113227] random: get_random_bytes called from start_kernel+0x93/0x4be with crng_init=0
[    0.113232] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:1
[    0.113781] percpu: Embedded 42 pages/cpu s133400 r8192 d30440 u262144
[    0.113784] pcpu-alloc: s133400 r8192 d30440 u262144 alloc=1*2097152
[    0.113785] pcpu-alloc: [0] 00 01 02 03 04 05 06 07 [0] 08 09 10 11 12 13 14 15
[    0.113796] Built 1 zonelists, mobility grouping on.  Total pages: 4095630
[    0.113797] Kernel command line: initrd=\initrd.img panic=-1 nr_cpus=16 swiotlb=force pty.legacy_count=0
[    0.115668] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes)
[    0.116589] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes)
[    0.133498] Memory: 4096408K/16644732K available (14360K kernel code, 1575K rwdata, 2856K rodata, 1512K init, 2756K bss, 384316K reserved, 0K cma-reserved)
[    0.133697] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=1
[    0.133701] ftrace: allocating 41883 entries in 164 pages
[    0.144459] rcu: Hierarchical RCU implementation.
[    0.144460] rcu:  RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
[    0.144461]  All grace periods are expedited (rcu_expedited).
[    0.144461] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=16
[    0.146075] Using NULL legacy PIC
[    0.146076] NR_IRQS: 16640, nr_irqs: 552, preallocated irqs: 0
[    0.146314] Console: colour dummy device 80x25
[    0.146316] console [tty0] enabled
[    0.146321] ACPI: Core revision 20180810
[    0.146410] Failed to register legacy timer interrupt
[    0.146411] APIC: Switch to symmetric I/O mode setup
[    0.147737] x2apic: IRQ remapping doesn't support X2APIC mode
[    0.149054] Switched APIC routing to physical flat.
[    0.149070] Hyper-V: Using IPI hypercalls
[    0.149073] clocksource: hyperv_clocksource_tsc_page: mask: 0xffffffffffffffff max_cycles: 0x24e6a1710, max_idle_ns:<PHONE_NUMBER>20 ns
[    0.149124] Calibrating delay loop (skipped), value calculated using timer frequency.. 4608.01 BogoMIPS (lpj=23040080)
[    0.149125] pid_max: default: 32768 minimum: 301
[    0.149141] Security Framework initialized
[    0.149162] Mount-cache hash table entries: 32768 (order: 6, 262144 bytes)
[    0.149177] Mountpoint-cache hash table entries: 32768 (order: 6, 262144 bytes)
[    0.149368] Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8
[    0.149369] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4
[    0.149370] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
[    0.149371] Spectre V2 : Mitigation: Enhanced IBRS
[    0.149371] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
[    0.149376] Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
[    0.149377] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp
[    0.149550] Freeing SMP alternatives memory: 44K
[    0.150233] smpboot: CPU0: Intel(R) Core(TM) i7-10875H CPU @ 2.30GHz (family: 0x6, model: 0xa5, stepping: 0x2)
[    0.150271] Performance Events: unsupported p6 CPU model 165 no PMU driver, software events only.
[    0.150285] rcu: Hierarchical SRCU implementation.
[    0.150329] random: crng done (trusting CPU's manufacturer)
[    0.150381] smp: Bringing up secondary CPUs ...
[    0.150461] x86: Booting SMP configuration:
[    0.150462] .... node  #0, CPUs:        #1  #2  #3  #4  #5  #6  #7  #8  #9 #10 #11 #12 #13 #14 #15
[    0.150821] smp: Brought up 1 node, 16 CPUs
[    0.150821] smpboot: Max logical packages: 1
[    0.150821] smpboot: Total of 16 processors activated (73728.25 BogoMIPS)
[    0.219120] node 0 initialised, 3041002 pages in 70ms
[    0.220698] devtmpfs: initialized
[    0.220698] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:<PHONE_NUMBER>2750000 ns
[    0.220698] futex hash table entries: 4096 (order: 6, 262144 bytes)
[    0.220698] xor: automatically using best checksumming function   avx
[    0.220698] NET: Registered protocol family 16
[    0.220698] ACPI: bus type PCI registered
[    0.220698] PCI: Fatal: No config space access function found
[    0.220698] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.220698] raid6: Forced to use recovery algorithm avx2x2
[    0.220698] raid6: Forced gen() algo avx2x4
[    0.220698] ACPI: Added _OSI(Module Device)
[    0.220698] ACPI: Added _OSI(Processor Device)
[    0.220698] ACPI: Added _OSI(3.0 _SCP Extensions)
[    0.220698] ACPI: Added _OSI(Processor Aggregator Device)
[    0.220698] ACPI: Added _OSI(Linux-Dell-Video)
[    0.220698] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[    0.229604] ACPI: 1 ACPI AML tables successfully acquired and loaded
[    0.230163] ACPI: Interpreter enabled
[    0.230163] ACPI: (supports S0 S5)
[    0.230163] ACPI: Using IOAPIC for interrupt routing
[    0.230163] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.230163] ACPI: Enabled 2 GPEs in block 00 to 0F
[    0.230178] SCSI subsystem initialized
[    0.230178] hv_vmbus: Vmbus version:5.0
[    0.230178] PCI: Using ACPI for IRQ routing
[    0.230178] PCI: System does not support PCI
[    0.230303] clocksource: Switched to clocksource hyperv_clocksource_tsc_page
[    0.230581] hv_vmbus: Unknown GUID: c376c1c3-d276-48d2-90a9-c04748072c60
[    0.230609] hv_vmbus: Unknown GUID: 6e382d18-3336-4f4b-acc4-2b7703d4df4a
[    0.230836] hv_vmbus: Unknown GUID: dde9cbc0-5060-4436-9448-ea1254a5d177
[    0.230854] hv_vmbus: Unknown GUID: 6e382d18-3336-4f4b-acc4-2b7703d4df4a
[    0.240933] VFS: Disk quotas dquot_6.6.0
[    0.240943] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.241006] FS-Cache: Loaded
[    0.241062] pnp: PnP ACPI init
[    0.241213] pnp 00:00: Plug and Play ACPI device, IDs PNP0b00 (active)
[    0.241245] pnp: PnP ACPI: found 1 devices
[    0.245032] NET: Registered protocol family 2
[    0.245279] tcp_listen_portaddr_hash hash table entries: 8192 (order: 5, 131072 bytes)
[    0.245291] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[    0.245545] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[    0.245609] TCP: Hash tables configured (established 131072 bind 65536)
[    0.245630] UDP hash table entries: 8192 (order: 6, 262144 bytes)
[    0.245648] UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes)
[    0.245686] NET: Registered protocol family 1
[    0.246168] RPC: Registered named UNIX socket transport module.
[    0.246168] RPC: Registered udp transport module.
[    0.246168] RPC: Registered tcp transport module.
[    0.246169] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.246170] PCI: CLS 0 bytes, default 64
[    0.246225] Trying to unpack rootfs image as initramfs...
[    0.246350] Freeing initrd memory: 60K
[    0.246388] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[    0.246389] software IO TLB: mapped [mem 0xf4000000-0xf8000000] (64MB)
[    0.246418] KVM: vmx: using Hyper-V Enlightened VMCS
[    0.344945] kvm: already loaded the other module
[    0.345657] Initialise system trusted keyrings
[    0.345752] workingset: timestamp_bits=46 max_order=22 bucket_order=0
[    0.346428] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.346748] NFS: Registering the id_resolver key type
[    0.346752] Key type id_resolver registered
[    0.346752] Key type id_legacy registered
[    0.346771] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    0.347681] Key type cifs.idmap registered
[    0.347733] fuse init (API version 7.27)
[    0.348220] SGI XFS with ACLs, security attributes, realtime, scrub, no debug enabled
[    0.349183] 9p: Installing v9fs 9p2000 file system support
[    0.349192] FS-Cache: Netfs '9p' registered for caching
[    0.349237] FS-Cache: Netfs 'ceph' registered for caching
[    0.349239] ceph: loaded (mds proto 32)
[    0.351840] NET: Registered protocol family 38
[    0.351841] Key type asymmetric registered
[    0.351842] Asymmetric key parser 'x509' registered
[    0.351848] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[    0.351871] io scheduler noop registered (default)
[    0.352520] hv_vmbus: registering driver hv_pci
[    0.352756] hv_pci fdee2603-7675-464b-a64e-7ec0b95d310e: PCI VMBus probing: Using version 0x10002
[    0.353321] hv_pci fdee2603-7675-464b-a64e-7ec0b95d310e: PCI host bridge to bus a64e:00
[    0.353492] pci a64e:00:00.0: [1414:008e] type 00 class 0x030200
[    0.357036] hv_pci 6f74f752-7581-4490-a1a4-b2983557a12c: PCI VMBus probing: Using version 0x10002
[    0.357448] hv_pci 6f74f752-7581-4490-a1a4-b2983557a12c: PCI host bridge to bus a1a4:00
[    0.357608] pci a1a4:00:00.0: [1414:008e] type 00 class 0x030200
[    0.361138] ACPI: AC Adapter [AC1] (on-line)
[    0.361368] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    0.361608] battery: ACPI: Battery Slot [BAT1] (battery present)
[    0.361706] Non-volatile memory driver v1.3
[    0.364295] brd: module loaded
[    0.365032] loop: module loaded
[    0.365232] hv_vmbus: registering driver hv_storvsc
[    0.365268] Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
[    0.365549] tun: Universal TUN/TAP device driver, 1.6
[    0.365615] PPP generic driver version 2.4.2
[    0.365690] PPP BSD Compression module registered
[    0.365690] PPP Deflate Compression module registered
[    0.365694] PPP MPPE Compression module registered
[    0.365695] NET: Registered protocol family 24
[    0.365697] hv_vmbus: registering driver hv_netvsc
[    0.365764] VFIO - User Level meta-driver version: 0.3
[    0.365874] hv_vmbus: registering driver hyperv_keyboard
[    0.366018] rtc_cmos 00:00: RTC can wake from S4
[    0.367075] rtc_cmos 00:00: registered as rtc0
[    0.367082] rtc_cmos 00:00: alarms up to one month, 114 bytes nvram
[    0.367175] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised<EMAIL_ADDRESS>[    0.367518] hv_utils: Registering HyperV Utility Driver
[    0.367518] hv_vmbus: registering driver hv_util
[    0.367538] hv_vmbus: registering driver hv_balloon
[    0.367543] dxgk:err: dxg_drv_init  Version: 1
[    0.367545] hv_vmbus: registering driver dxgkrnl
[    0.367558] hv_utils: cannot register PTP clock: 0
[    0.367689] drop_monitor: Initializing network drop monitor service
[    0.367706] Mirror/redirect action on
[    0.367876] IPVS: Registered protocols (TCP, UDP)
[    0.367887] IPVS: Connection hash table configured (size=4096, memory=64Kbytes)
[    0.368306] hv_utils: TimeSync IC version 4.0
[    0.368376] hv_balloon: Using Dynamic Memory protocol version 2.0
[    0.369673] scsi host0: storvsc_host_t
[    0.369712] hv_balloon: cold memory discard enabled
[    0.369895] IPVS: ipvs loaded.
[    0.369897] IPVS: [rr] scheduler registered.
[    0.369897] IPVS: [wrr] scheduler registered.
[    0.369898] IPVS: [sh] scheduler registered.
[    0.371496] ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully
[    0.371818] Initializing XFRM netlink socket
[    0.371865] NET: Registered protocol family 10
[    0.372434] Segment Routing with IPv6
[    0.374364] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    0.374435] NET: Registered protocol family 17
[    0.374448] Bridge firewalling registered
[    0.374470] 8021q: 802.1Q VLAN Support v1.8
[    0.374488] sctp: Hash tables configured (bind 256/256)
[    0.374520] 9pnet: Installing 9P2000 support
[    0.374528] Key type dns_resolver registered
[    0.374533] Key type ceph registered
[    0.374797] libceph: loaded (mon/osd proto 15/24)
[    0.374798] hv_vmbus: registering driver hv_sock
[    0.374860] NET: Registered protocol family 40
[    0.375075] registered taskstats version 1
[    0.375080] Loading compiled-in X.509 certificates
[    0.375295] Btrfs loaded, crc32c=crc32c-generic
[    0.375900] rtc_cmos 00:00: setting system clock to 2020-11-04 15:48:57 UTC<PHONE_NUMBER>)
[    0.375913] Unstable clock detected, switching default tracing clock to "global"
               If you want to keep using the local clock, then add:
                 "trace_clock=local"
               on the kernel command line
[    0.377346] Freeing unused kernel image memory: 1512K
[    0.459317] Write protecting the kernel read-only data: 20480k
[    0.460316] Freeing unused kernel image memory: 1984K
[    0.460575] Freeing unused kernel image memory: 1240K
[    0.460576] Run /init as init process
[    0.486818] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    0.621744] scsi 0:0:0:0: Direct-Access     Msft     Virtual Disk     1.0  PQ: 0 ANSI: 5
[    0.622169] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    0.623225] sd 0:0:0:0: [sda] 536870912 512-byte logical blocks: (275 GB/256 GiB)
[    0.623226] sd 0:0:0:0: [sda] 4096-byte physical blocks
[    0.623324] sd 0:0:0:0: [sda] Write Protect is off
[    0.623324] sd 0:0:0:0: [sda] Mode Sense: 0f 00 00 00
[    0.623499] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    0.625693] sd 0:0:0:0: [sda] Attached SCSI disk
[    0.634301] scsi 0:0:0:1: Direct-Access     Msft     Virtual Disk     1.0  PQ: 0 ANSI: 5
[    0.634546] sd 0:0:0:1: Attached scsi generic sg1 type 0
[    0.635135] sd 0:0:0:1: [sdb] 536870912 512-byte logical blocks: (275 GB/256 GiB)
[    0.635136] sd 0:0:0:1: [sdb] 4096-byte physical blocks
[    0.635228] sd 0:0:0:1: [sdb] Write Protect is off
[    0.635229] sd 0:0:0:1: [sdb] Mode Sense: 0f 00 00 00
[    0.635371] sd 0:0:0:1: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    0.637552] sd 0:0:0:1: [sdb] Attached SCSI disk
[    0.641169] EXT4-fs (sda): mounted filesystem with ordered data mode. Opts: (null)
[    0.651833] EXT4-fs (sdb): mounted filesystem with ordered data mode. Opts: discard,errors=remount-ro,data=ordered
[    0.661027] hv_pci 8e7052f3-aec1-4c22-bf7f-0331c57a6a72: PCI VMBus probing: Using version 0x10002
[    0.698058] Adding 4194304k swap on /swap/file.  Priority:-2 extents:2 across:4202496k
[    0.701328] hv_pci 8e7052f3-aec1-4c22-bf7f-0331c57a6a72: PCI host bridge to bus bf7f:00
[    0.701329] pci_bus bf7f:00: root bus resource [mem 0xe00000000-0xe00002fff window]
[    0.701687] pci bf7f:00:00.0: [1af4:1049] type 00 class 0x010000
[    0.702645] pci bf7f:00:00.0: reg 0x10: [mem 0xe00000000-0xe00000fff 64bit]
[    0.703445] pci bf7f:00:00.0: reg 0x18: [mem 0xe00001000-0xe00001fff 64bit]
[    0.704106] pci bf7f:00:00.0: reg 0x20: [mem 0xe00002000-0xe00002fff 64bit]
[    0.706770] pci bf7f:00:00.0: BAR 0: assigned [mem 0xe00000000-0xe00000fff 64bit]
[    0.707083] pci bf7f:00:00.0: BAR 2: assigned [mem 0xe00001000-0xe00001fff 64bit]
[    0.707396] pci bf7f:00:00.0: BAR 4: assigned [mem 0xe00002000-0xe00002fff 64bit]
[    0.722312] hv_pci 4009ad46-eda6-4c95-9e8e-063a8aa7f055: PCI VMBus probing: Using version 0x10002
[    0.762302] hv_pci 4009ad46-eda6-4c95-9e8e-063a8aa7f055: PCI host bridge to bus 9e8e:00
[    0.762303] pci_bus 9e8e:00: root bus resource [mem 0xe00004000-0xe00006fff window]
[    0.762705] pci 9e8e:00:00.0: [1af4:1049] type 00 class 0x010000
[    0.763717] pci 9e8e:00:00.0: reg 0x10: [mem 0xe00004000-0xe00004fff 64bit]
[    0.764159] pci 9e8e:00:00.0: reg 0x18: [mem 0xe00005000-0xe00005fff 64bit]
[    0.764658] pci 9e8e:00:00.0: reg 0x20: [mem 0xe00006000-0xe00006fff 64bit]
[    0.767472] pci 9e8e:00:00.0: BAR 0: assigned [mem 0xe00004000-0xe00004fff 64bit]
[    0.767780] pci 9e8e:00:00.0: BAR 2: assigned [mem 0xe00005000-0xe00005fff 64bit]
[    0.768082] pci 9e8e:00:00.0: BAR 4: assigned [mem 0xe00006000-0xe00006fff 64bit]
[    0.780153] FS-Cache: Duplicate cookie detected
[    0.780154] FS-Cache: O-cookie c=00000000cd90a8b7 [p=00000000b9371024 fl=222 nc=0 na=1]
[    0.780155] FS-Cache: O-cookie d=0000000041316fe2 n=000000006a3ee416
[    0.780155] FS-Cache: O-key=[10] '34323934393337333539'
[    0.780157] FS-Cache: N-cookie c=00000000502b8307 [p=00000000b9371024 fl=2 nc=0 na=1]
[    0.780157] FS-Cache: N-cookie d=0000000041316fe2 n=000000004222c9b1
[    0.780157] FS-Cache: N-key=[10] '34323934393337333539'
[    0.875340] hv_pci dcc5fdab-63a0-4540-b004-7b4fbb4728cb: PCI VMBus probing: Using version 0x10002
[    0.913567] hv_pci dcc5fdab-63a0-4540-b004-7b4fbb4728cb: PCI host bridge to bus b004:00
[    0.913568] pci_bus b004:00: root bus resource [mem 0xe00008000-0xe0000afff window]
[    0.913914] pci b004:00:00.0: [1af4:1049] type 00 class 0x010000
[    0.914954] pci b004:00:00.0: reg 0x10: [mem 0xe00008000-0xe00008fff 64bit]
[    0.915383] pci b004:00:00.0: reg 0x18: [mem 0xe00009000-0xe00009fff 64bit]
[    0.915806] pci b004:00:00.0: reg 0x20: [mem 0xe0000a000-0xe0000afff 64bit]
[    0.919636] pci b004:00:00.0: BAR 0: assigned [mem 0xe00008000-0xe00008fff 64bit]
[    0.919997] pci b004:00:00.0: BAR 2: assigned [mem 0xe00009000-0xe00009fff 64bit]
[    0.920340] pci b004:00:00.0: BAR 4: assigned [mem 0xe0000a000-0xe0000afff 64bit]
[    0.929057] hv_pci 0c4ecfee-2f64-4d94-8749-aa7f7c037510: PCI VMBus probing: Using version 0x10002
[    0.967009] hv_pci 0c4ecfee-2f64-4d94-8749-aa7f7c037510: PCI host bridge to bus 8749:00
[    0.967011] pci_bus 8749:00: root bus resource [mem 0xe0000c000-0xe0000efff window]
[    0.967428] pci 8749:00:00.0: [1af4:1049] type 00 class 0x010000
[    0.968614] pci 8749:00:00.0: reg 0x10: [mem 0xe0000c000-0xe0000cfff 64bit]
[    0.969044] pci 8749:00:00.0: reg 0x18: [mem 0xe0000d000-0xe0000dfff 64bit]
[    0.969588] pci 8749:00:00.0: reg 0x20: [mem 0xe0000e000-0xe0000efff 64bit]
[    0.972228] pci 8749:00:00.0: BAR 0: assigned [mem 0xe0000c000-0xe0000cfff 64bit]
[    0.972534] pci 8749:00:00.0: BAR 2: assigned [mem 0xe0000d000-0xe0000dfff 64bit]
[    0.972834] pci 8749:00:00.0: BAR 4: assigned [mem 0xe0000e000-0xe0000efff 64bit]
[    1.429398] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   12.588531] scsi 0:0:0:2: Direct-Access     Msft     Virtual Disk     1.0  PQ: 0 ANSI: 5
[   12.589016] sd 0:0:0:2: Attached scsi generic sg2 type 0
[   12.589772] sd 0:0:0:2: [sdc] 536870912 512-byte logical blocks: (275 GB/256 GiB)
[   12.589773] sd 0:0:0:2: [sdc] 4096-byte physical blocks
[   12.589889] sd 0:0:0:2: [sdc] Write Protect is off
[   12.589890] sd 0:0:0:2: [sdc] Mode Sense: 0f 00 00 00
[   12.590058] sd 0:0:0:2: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   12.591833] sd 0:0:0:2: [sdc] Attached SCSI disk
[   12.606740] EXT4-fs (sdc): mounted filesystem with ordered data mode. Opts: discard,errors=remount-ro,data=ordered
[   12.614387] FS-Cache: Duplicate cookie detected
[   12.614388] FS-Cache: O-cookie c=00000000be8e123d [p=00000000b9371024 fl=222 nc=0 na=1]
[   12.614389] FS-Cache: O-cookie d=0000000041316fe2 n=000000003382fe6f
[   12.614389] FS-Cache: O-key=[10] '34323934393338353432'
[   12.614390] FS-Cache: N-cookie c=0000000017253d7d [p=00000000b9371024 fl=2 nc=0 na=1]
[   12.614391] FS-Cache: N-cookie d=0000000041316fe2 n=00000000b2ab7115
[   12.614391] FS-Cache: N-key=[10] '34323934393338353432'
[   12.614591] init: (1) ERROR: ConfigApplyWindowsLibPath:2299: open /etc/ld.so.conf.d/ld.wsl.conf
[   12.614592]  failed 2
[   12.639549] WARNING: /usr/share/zoneinfo/Europe/Paris not found. Is the tzdata package installed?
[   30.049497] EXT4-fs (sdb): mounted filesystem with ordered data mode. Opts: discard,errors=remount-ro,data=ordered
[   30.065780] FS-Cache: Duplicate cookie detected
[   30.065781] FS-Cache: O-cookie c=0000000017253d7d [p=00000000b9371024 fl=222 nc=0 na=1]
[   30.065782] FS-Cache: O-cookie d=0000000041316fe2 n=0000000080a49fe1
[   30.065782] FS-Cache: O-key=[10] '34323934393430323837'
[   30.065784] FS-Cache: N-cookie c=00000000680959b3 [p=00000000b9371024 fl=2 nc=0 na=1]
[   30.065784] FS-Cache: N-cookie d=0000000041316fe2 n=000000009a966431
[   30.065784] FS-Cache: N-key=[10] '34323934393430323837'

I can't see anything related. ConfigApplyLibPath seem to trigger an error in distros without a /etc/ls.so.conf.d dir (as Alpine which does not ship with a glibc anyway).

ConfigApplyWindowsLibPath function is not related to mounting /mnt/wsl. It mounts /usr/lib/wsl/ and it's directories for d3d12. In the output open /etc/ld.so.conf.d/ld.wsl.conf failed 2, the 2 is ENOENT: No such file or directory. Alpine does not have that folder. Did you play with the automount.crossDistro option?

Thanks for reporting this @simonferquel.
Looking at the commands in the original post, this seems normal as /mnt/c is only bind mounted from the Ubuntu distro and it's not mounted from the Alpine distro.
For context: /mnt/wsl is shared between all distros, but /mnt isn't.
Does that make sense ?

Thanks for reporting this @simonferquel.
Looking at the commands in the original post, this seems normal as /mnt/c is only bind mounted from the Ubuntu distro and it's not mounted from the Alpine distro.
For context: /mnt/wsl is shared between all distros, but /mnt isn't.
Does that make sense ?

@OneBlue automount is enabled on both distros, and automount root is set as /mnt on both as well. Accordingly, WSL should make my C drive available on /mnt/c on both distros.
If I don't manually bind-mount /mnt/c to /mnt/wsl/c in Ubuntu before starting Alpine, I can correctly access /mnt/c on both Ubuntu and Alpine.
To give a little context here, I am working on Docker Desktop. In our setup, we run the docker daemon in a separate distro (that we entirely control) and whenever you want to mount source code from your distro into a container (using docker run -v /source/path/in/my/distro:/path/in/container ... ), we create an intermediate bind mount within /mnt/wsl so that the Docker Desktop distro can access it. If you have some sources living on a Windows volume, it triggers the issue.

@OneBlue automount is enabled on both distros, and automount root is set as /mnt on both as well. Accordingly, WSL should make my C drive available on /mnt/c on both distros.
If I don't manually bind-mount /mnt/c to /mnt/wsl/c in Ubuntu before starting Alpine, I can correctly access /mnt/c on both Ubuntu and Alpine.
To give a little context here, I am working on Docker Desktop. In our setup, we run the docker daemon in a separate distro (that we entirely control) and whenever you want to mount source code from your distro into a container (using docker run -v /source/path/in/my/distro:/path/in/container ... ), we create an intermediate bind mount within /mnt/wsl so that the Docker Desktop distro can access it. If you have some sources living on a Windows volume, it triggers the issue.

@simonferquel: I've had a deeper look, and here's the root cause:
When init is about to mount a drive, it searches /proc/self/mounts  for any existing mount on the same drive. If any is found, then the drive is not mounted (even if the mount point is different).
So when you bind mount /mnt/c to /mnt/wsl/c, this causes /mnt/wsl/c to show up in  /proc/self/mounts when alpine's init starts, and so it skips mounting /mnt/c.
I've made a code change to only skip a mount if the both source drive AND the mount point are the same, which should solve your scenario.

@simonferquel: I've had a deeper look, and here's the root cause:
When init is about to mount a drive, it searches /proc/self/mounts  for any existing mount on the same drive. If any is found, then the drive is not mounted (even if the mount point is different).
So when you bind mount /mnt/c to /mnt/wsl/c, this causes /mnt/wsl/c to show up in  /proc/self/mounts when alpine's init starts, and so it skips mounting /mnt/c.
I've made a code change to only skip a mount if the both source drive AND the mount point are the same, which should solve your scenario.

@OneBlue thanks a lot !
Any chance it gets backported to previous versions of Windows ?

@OneBlue thanks a lot !
Any chance it gets backported to previous versions of Windows ?

@simonferquel: Unfortunately no, we won't be able to backport the fix for this.
The fix has made it to insider so closing this.

@simonferquel: Unfortunately no, we won't be able to backport the fix for this.
The fix has made it to insider so closing this.

What is the justification for not backporting the fix? Is microsoft no longer supporting Windows 10?


Improve take performance on RunEndArray

Currently it calls find_physical_index in a hot loop. For dense takes, this can be quite a lot of overhead.

FWIW I think we should have search_sorted for numerical arrays that just casts to u64/usize and avoids creating scalars

Another thing would be to update our search_sorted to use the algorithm from latest rust std lib which is said to be 20-30% faster. Doubt we will have comparable speed up but likely there will be some gain

This was handled in a combo of #840 + #851


'dart:js_util' is not available on this platform!

Trying to run for my flutter-windows app. But shows brunch of errors. Any solution?
Code:
import 'package:chrome_extension/tabs.dart';

Future<Tab> getActiveTab() async {
  QueryInfo queryInfo = QueryInfo(active: true, lastFocusedWindow: true);
  List<Tab> tabs = await chrome.tabs.query(queryInfo);
  final tab = tabs.singleWhere((tab) => tab.url != null && tab.url!.isNotEmpty);
  return tab;
}

Outpur:
../../AppData/Local/Pub/Cache/hosted/pub.dev/chrome_extension-0.2.0/lib/tabs.dart:5:8: Error: Dart library 'dart:js_util' is not available on this platform.
import 'dart:js_util';
       ^
Context: The unavailable library 'dart:js_util' is imported through these packages:

    package:nextwork => package:chrome_extension => dart:js_util

Detailed import paths for (some of) the these imports:

    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/src/internal_helpers.dart => dart:js_util
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => dart:js_util
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => package:chrome_extension/tabs.dart => dart:js_util
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => package:chrome_extension/tabs.dart => package:chrome_extension/windows.dart => dart:js_util
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/types.dart => dart:js_util
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/types.dart => package:chrome_extension/src/internal_helpers.dart => dart:js_util
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/types.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => dart:js_util
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/types.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => package:chrome_extension/tabs.dart => dart:js_util
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/types.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => package:chrome_extension/tabs.dart => package:chrome_extension/windows.dart => dart:js_util
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/action.dart => dart:js_util
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/action.dart => package:chrome_extension/src/internal_helpers.dart => dart:js_util
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/action.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => dart:js_util
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/action.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => package:chrome_extension/tabs.dart => dart:js_util
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/action.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => package:chrome_extension/tabs.dart => package:chrome_extension/windows.dart => dart:js_util
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/action.dart => package:chrome_extension/tabs.dart => dart:js_util
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/action.dart => package:chrome_extension/tabs.dart => package:chrome_extension/windows.dart => dart:js_util
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/alarms.dart => dart:js_util
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/alarms.dart => package:chrome_extension/src/internal_helpers.dart => dart:js_util
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/alarms.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => dart:js_util
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/alarms.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => package:chrome_extension/tabs.dart => dart:js_util
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/alarms.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => package:chrome_extension/tabs.dart => package:chrome_extension/windows.dart => dart:js_util
    ...

../../AppData/Local/Pub/Cache/hosted/pub.dev/chrome_extension-0.2.0/lib/src/internal_helpers.dart:2:8: Error: Dart library 'dart:js_interop' is not available on this platform.
import 'dart:js_interop';
       ^
Context: The unavailable library 'dart:js_interop' is imported through these packages:

    package:nextwork => package:chrome_extension => dart:js_interop

Detailed import paths for (some of) the these imports:

    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/src/internal_helpers.dart => dart:js_interop
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => package:chrome_extension/src/js/runtime.dart => package:chrome_extension/src/js/chrome.dart => package:chrome_extension/src/chrome_js.dart => package:chrome_extension/src/js/events.dart => dart:js_interop
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => package:chrome_extension/src/js/runtime.dart => package:chrome_extension/src/js/chrome.dart => package:chrome_extension/src/chrome_js.dart => dart:js_interop
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => package:chrome_extension/src/js/runtime.dart => dart:js_interop
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => package:chrome_extension/src/js/runtime.dart => package:chrome_extension/src/js/tabs.dart => package:chrome_extension/src/js/chrome.dart => package:chrome_extension/src/chrome_js.dart => package:chrome_extension/src/js/events.dart => dart:js_interop
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => package:chrome_extension/src/js/runtime.dart => package:chrome_extension/src/js/tabs.dart => package:chrome_extension/src/js/chrome.dart => package:chrome_extension/src/chrome_js.dart => dart:js_interop
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => package:chrome_extension/src/js/runtime.dart => package:chrome_extension/src/js/tabs.dart => dart:js_interop
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => package:chrome_extension/src/js/runtime.dart => package:chrome_extension/src/js/tabs.dart => package:chrome_extension/src/js/extension_types.dart => package:chrome_extension/src/js/chrome.dart => package:chrome_extension/src/chrome_js.dart => package:chrome_extension/src/js/events.dart => dart:js_interop
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => package:chrome_extension/src/js/runtime.dart => package:chrome_extension/src/js/tabs.dart => package:chrome_extension/src/js/extension_types.dart => package:chrome_extension/src/js/chrome.dart => package:chrome_extension/src/chrome_js.dart => dart:js_interop
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => package:chrome_extension/src/js/runtime.dart => package:chrome_extension/src/js/tabs.dart => package:chrome_extension/src/js/extension_types.dart => dart:js_interop
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => package:chrome_extension/tabs.dart => package:chrome_extension/extension_types.dart => package:chrome_extension/src/js/extension_types.dart => package:chrome_extension/src/js/chrome.dart => package:chrome_extension/src/chrome_js.dart => package:chrome_extension/src/js/events.dart => dart:js_interop
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => package:chrome_extension/tabs.dart => package:chrome_extension/extension_types.dart => package:chrome_extension/src/js/extension_types.dart => package:chrome_extension/src/js/chrome.dart => package:chrome_extension/src/chrome_js.dart => dart:js_interop
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => package:chrome_extension/tabs.dart => package:chrome_extension/extension_types.dart => package:chrome_extension/src/js/extension_types.dart => dart:js_interop
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => package:chrome_extension/tabs.dart => package:chrome_extension/src/js/tabs.dart => package:chrome_extension/src/js/chrome.dart => package:chrome_extension/src/chrome_js.dart => package:chrome_extension/src/js/events.dart => dart:js_interop
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => package:chrome_extension/tabs.dart => package:chrome_extension/src/js/tabs.dart => package:chrome_extension/src/js/chrome.dart => package:chrome_extension/src/chrome_js.dart => dart:js_interop
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => package:chrome_extension/tabs.dart => package:chrome_extension/src/js/tabs.dart => dart:js_interop
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => package:chrome_extension/tabs.dart => package:chrome_extension/src/js/tabs.dart => package:chrome_extension/src/js/extension_types.dart => package:chrome_extension/src/js/chrome.dart => package:chrome_extension/src/chrome_js.dart => package:chrome_extension/src/js/events.dart => dart:js_interop
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => package:chrome_extension/tabs.dart => package:chrome_extension/src/js/tabs.dart => package:chrome_extension/src/js/extension_types.dart => package:chrome_extension/src/js/chrome.dart => package:chrome_extension/src/chrome_js.dart => dart:js_interop
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => package:chrome_extension/tabs.dart => package:chrome_extension/src/js/tabs.dart => package:chrome_extension/src/js/extension_types.dart => dart:js_interop
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => package:chrome_extension/tabs.dart => package:chrome_extension/src/js/windows.dart => package:chrome_extension/src/js/chrome.dart => package:chrome_extension/src/chrome_js.dart => package:chrome_extension/src/js/events.dart => dart:js_interop
    package:nextwork/deviceInfo.dart => package:chrome_extension/chrome.dart => package:chrome_extension/accessibility_features.dart => package:chrome_extension/src/internal_helpers.dart => package:chrome_extension/runtime.dart => package:chrome_extension/tabs.dart => package:chrome_extension/src/js/windows.dart => package:chrome_extension/src/js/chrome.dart => package:chrome_extension/src/chrome_js.dart => dart:js_interop
    ...

../../AppData/Local/Pub/Cache/hosted/pub.dev/chrome_extension-0.2.0/lib/action.dart:5:8: Error: Dart library 'dart:js_util' is not available on this platform.
import 'dart:js_util';
       ^
../../AppData/Local/Pub/Cache/hosted/pub.dev/chrome_extension-0.2.0/lib/alarms.dart:5:8: Error: Dart library 'dart:js_util' is not available on this platform.
import 'dart:js_util';
       ^
../../AppData/Local/Pub/Cache/hosted/pub.dev/chrome_extension-0.2.0/lib/audio.dart:5:8: Error: Dart library 'dart:js_util' is not available on this platform.
import 'dart:js_util';
       ^
../../AppData/Local/Pub/Cache/hosted/pub.dev/chrome_extension-0.2.0/lib/bookmarks.dart:5:8: Error: Dart library 'dart:js_util' is not available on this platform.
import 'dart:js_util';
       ^
../../AppData/Local/Pub/Cache/hosted/pub.dev/chrome_extension-0.2.0/lib/browser_action.dart:5:8: Error: Dart library 'dart:js_util' is not available on this platform.
import 'dart:js_util';
       ^
../../AppData/Local/Pub/Cache/hosted/pub.dev/chrome_extension-0.2.0/lib/browsing_data.dart:5:8: Error: Dart library 'dart:js_util' is not available on this platform.
import 'dart:js_util';
       ^

This library is to build Chrome extension (https://developer.chrome.com/docs/extensions/get-started). The Dart code has to be compiled to javascript.
If your goal is to use a Desktop app just for development. Then you need to keep any access to the chrome API behind an abstraction layer as explained briefly in the README: https://github.com/xvrh/chrome_extension.dart?tab=readme-ov-file#tips-to-build-chrome-extensions-with-flutter

I see. Thanks for your quick replay.


exec busybox failed

Hello not sure if we can use this CMD on 2.3.0?
FROM lipanski/docker-static-website:2.3.0
ARG PUBLIC_URL /.
COPY --from=build /tmp/app/httpd.conf .
COPY --from=build /tmp/app/dist/ .$PUBLIC_URL
CMD ["/busybox", "httpd", "-f", "-v", "-p", "80", "-c", "httpd.conf"]
EXPOSE 80

[FATAL tini (7)] exec /busybox failed: No such file or directory
 ELIFECYCLE  Command failed.

add to readme?
CMD ["/busybox_HTTPD", "-f", "-v", "-p", "80", "-c", "httpd.conf"]

Fixed in https://github.com/lipanski/docker-static-website/commit/295afd8720b305239b981c853cc08edf89a28da7 and released as 2.3.1
The new CMD line is:
CMD ["/busybox-httpd", "-f", "-v", "-p", "80", "-c", "httpd.conf"]

@lipanski it would be very nice to update the command in https://lipanski.com/posts/smallest-docker-image-static-website also.


Using PowerMockito to mock System.getent;

Now, I read the document of PowerMockito and find the way to mock system class's static method.
So I remove the reflection code. I think it would be better to use PowerMockito and it can avoid the problem of compatability between difference OS and platform.
see EnvUtilsTest failed

Why submit this pull request?

[X] Bug fix

[ ] New feature provided

[ ] Improve performance

Related issues

Bug fix

Bug description.

How to fix?

New feature or improvement

Describe the details and related test reports.

@liuhaoyang What do you think? Which one do you prefer?

I think you should continue open appveyor to avoid this in next time, no matter which PR you think it is better.

Coverage decreased (-0.02%) to 16.226% when pulling 05eb24a5772fde16f28fd45bf866b5398a73ee95 on flycash:EnvUtilsTest-fix into 683e0483af62eea1520baf18943b19ed5fd81bf6 on apache:master.

It seems that the configuration of appveyor has some mistakes. In fact, I didn't find the config file appveyor.yml int root directory.
Do we need to add the configuration?

@liuhaoyang is working on that, the PR is on the way.

@flycash The appveyor setting file has been merged. Could you open the test in your PR, and let's wait it pass.

I have sync your branch, you should have it now.


the name "vite-error-overlay" has already been used with this registry

⚠ IMPORTANT ⚠ Please do not ignore this template. If you do, your issue will be closed immediately.

[x] Read the docs.
[x] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[ ] This is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

Describe the bug
I can access devServer normall by localhost, but thorw error by ip

It looks like it's redefining some nodes, and it works when I modify it this way
// clinet.js (line:177)
const overlayId = 'vite-error-overlay';
if (!customElements.get(overlayId)) { customElements.define(overlayId, ErrorOverlay); }

System Info

vite version:^2.0.0
Operating System: win10
Node version:v14.15.5
Package manager (npm/yarn/pnpm) and version: yarn v1.22.5

I've been seeing this issue too, using Laravel as a backend.  Looking at the browser's network inspector, it seems it was loading http://localhost:3000/@vite/client twice.
At the bottom of my page when doing dev I had
        <script type="module" src="http://localhost:3000/@vite/client"></script>
        <script type="module" src="http://localhost:3000/resources/js/admin/index.js"></script>

If I take out that first script, then it only loads @vite/client once and everything seems OK.  Tried some digging but I can't find what's triggering the load of the client.
Could it be that the docs on backend integration step 2 are no longer correct?

Actually, I found it.  It seems the Vue SFCs that load each have a line like this injected at the top
import { createHotContext as __vite__createHotContext } from "/static/dist/@vite/client";import.meta.hot = __vite__createHotContext("/resources/js/admin/components/Layout.vue");

So it was actually trying to load two slightly different URLs:
/@vite/client
/static/dist/@vite/client

The static/dist part in the 2nd one is probably coming from my vite.config.js build.outDir
If I change my initial dev script loading to
        <script type="module" src="http://localhost:3000/static/dist/@vite/client"></script>
        <script type="module" src="http://localhost:3000/resources/js/admin/index.js"></script>

It seems happy now and only loads once.