BQ: remove fetch_data and client references from QueryResults

Based on https://github.com/GoogleCloudPlatform/google-cloud-python/pull/4143.
Now QueryResults is just a container for the getQueryResults response.

Coverage failure is for list_partitions. I'll double-check the diff to make sure I didn't delete a test.


Use of setResult

You can use setResult() in the Async class.

Thank you for brining this to my attention, I currently do not have immediate time to apply the changes. Feel free to make a pull request.


Pol 167 update saa s policies for credential service

Description
Update listed SaaS policy to support the credential service. The changes include-
-Replace auth declaration with the credential declaration.
-Remove long_description field and use new info hash for Version, providers and service.
-Update readme to replace credential instructions with instructions to use credential service.
-Update CWF definitions as needed.
Issues Resolved
Added new credential service
###Running template Link
GitHub.com Available Seats
https://governance.rightscale.com/org/1105/projects/60073/applied-policies/5e7c75e1e3ec660001710d59
GitHub.com Repositories without Admin Team
https://governance.rightscale.com/org/1105/projects/60073/applied-policies/5e96f4b7e8dac600012ecbbb
GitHub.com Repository Branches without Protection
https://governance.rightscale.com/org/1105/projects/60073/applied-policies/5e7c76bee3ec660001710d5b
GitHub.com Unpermitted Outside Collaborators
https://governance.rightscale.com/org/1105/projects/60073/applied-policies/5e7c7ae95315750001ddb826
GitHub.com Unpermitted Repository Names
https://governance.rightscale.com/org/1105/projects/60073/applied-policies/5e82e7cb5315750001ddbe17
GitHub.com Unpermitted Sized Repositories
https://governance.rightscale.com/org/1105/projects/60073/applied-policies/5e7c8ef9e3ec660001710d6a
GitHub.com Unpermitted Top-Level Teams
https://governance.rightscale.com/org/1105/projects/60073/applied-policies/5e82e7855315750001ddbe16
Okta Inactive Users
https://governance.rightscale.com/org/1105/projects/60073/applied-policies/5e81954fe3ec6600017111b3
Contribution Check List

[x] All tests pass.
[x] New functionality includes testing.
[x] New functionality has been documented in the README if applicable
[x] New functionality has been documented in CHANGELOG.MD

          9 Errors

:no_entry_sign:
compliance/github/available_seats/README.md:10: MD029 Ordered list item prefix
compliance/github/available_seats/README.md:11: MD029 Ordered list item prefix
compliance/github/available_seats/README.md:12: MD029 Ordered list item prefix
A detailed description of the rules is available at https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md

:no_entry_sign:
compliance/github/outside_collaborators/README.md:10: MD029 Ordered list item prefix
compliance/github/outside_collaborators/README.md:11: MD029 Ordered list item prefix
A detailed description of the rules is available at https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md

:no_entry_sign:
compliance/github/repository_admin_team/README.md:10: MD029 Ordered list item prefix
A detailed description of the rules is available at https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md

:no_entry_sign:
compliance/github/repository_branch_protection/README.md:10: MD029 Ordered list item prefix
compliance/github/repository_branch_protection/README.md:11: MD029 Ordered list item prefix
compliance/github/repository_branch_protection/README.md:12: MD029 Ordered list item prefix
compliance/github/repository_branch_protection/README.md:13: MD029 Ordered list item prefix
compliance/github/repository_branch_protection/README.md:14: MD029 Ordered list item prefix
A detailed description of the rules is available at https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md

:no_entry_sign:
compliance/github/repository_naming/README.md:10: MD029 Ordered list item prefix
compliance/github/repository_naming/README.md:11: MD029 Ordered list item prefix
A detailed description of the rules is available at https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md

:no_entry_sign:
compliance/github/repository_size/README.md:13: MD012 Multiple consecutive blank lines
compliance/github/repository_size/README.md:7: MD022 Headers should be surrounded by blank lines
compliance/github/repository_size/README.md:9: MD029 Ordered list item prefix
compliance/github/repository_size/README.md:10: MD029 Ordered list item prefix
compliance/github/repository_size/README.md:11: MD029 Ordered list item prefix
compliance/github/repository_size/README.md:8: MD032 Lists should be surrounded by blank lines
A detailed description of the rules is available at https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md

:no_entry_sign:
compliance/github/toplevel_teams/README.md:10: MD029 Ordered list item prefix
compliance/github/toplevel_teams/README.md:11: MD029 Ordered list item prefix
A detailed description of the rules is available at https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md

:no_entry_sign:
cost/azure/reserved_instances/recommendations/README.md:3: MD026 Trailing punctuation in header
A detailed description of the rules is available at https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md

:no_entry_sign:
saas/okta/inactive_users/README.md:15: MD034 Bare URL used
A detailed description of the rules is available at https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md

  Generated by :no_entry_sign: Danger


Support multiple tap interfaces in vmwrapper

Do not merge before #490

This change is

Reviewed 1 of 1 files at r3.
Review status: 1 of 14 files reviewed at latest revision, 1 unresolved discussion.

cmd/vmwrapper/vmwrapper.go, line 174 at r3 (raw file):

			}
			if len(tapFds) != len(hwAddrs) {
				glog.Error("Received different number of open tap file descriptors than hardware addresses")

The number of open tap fds is different from the number of hardware addresses

Comments from Reviewable

Reviewed 8 of 14 files at r1, 5 of 5 files at r2.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

Comments from Reviewable

Review status: 7 of 14 files reviewed at latest revision, 1 unresolved discussion.

cmd/vmwrapper/vmwrapper.go, line 174 at r3 (raw file):
Previously, ivan4th (Ivan Shvedunov) wrote…
The number of open tap fds is different from the number of hardware addresses

Done.

Comments from Reviewable

Reviewed 4 of 4 files at r4.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

Comments from Reviewable

Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


fix(meta): correctly persist license key system param in SQL backend

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Follow-up of #17936.
Previously the new_value: String returned by set_system_param is redacted for license_key, which will be further used to persist into the SQL backend. This is not expected. This PR fixes that and adds a unit test to clarify the semantics of the returned String type value.
Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

Seems like #17936 is included in release-2.0, shall we cherry pick this PR as well?


[*.rs] rustfmt

Also found these warnings: rust.log
Some are trivial, like you should remove the license-file from your Cargo.toml

Hi, SamuelMarks.
Thanks for the suggestion.
I hadn't used rustfmt before.
I'll commit to it.


Allow customisation of istanbul instrumentation options

Clear and concise description of the problem
I am trying to combine coverage results from vitest with coverage results from cypress (bundled with vite, instrumented with vite-plugin-istanbul). Merging coverage files does not work correctly because vitest instrumentation skips comments, types etc as requested and implemented in #5423, and vite-plugin-istanbul does not skip coverage of these (and also does not allow overriding this behaviour).
Without control over instrumentation for at least one of these (vitest OR vite-plugin-istanbul) there is no way for me to resolve the conflict.
Suggested solution
Provide some extra options in the coverage block that will override default instrumentation, such as
coverage: {
   include: './src/**',
   instrumentation: {
       preserveComments: true,
   }
}

Alternative
I am also going to raise a ticket for vite-plugin-istanbul to make a similar change, but ideally both packages would implement this change for maximum compatibility.
Additional context
Istanbul instrumentation is configured here: https://github.com/vitest-dev/vitest/blob/01a055261fe5277604e651000c56e3d8e9d288d5/packages/coverage-istanbul/src/provider.ts#L40-L56
For comparison, the equivalent in vite-plugin-istanbul is here. https://github.com/iFaxity/vite-plugin-istanbul/blob/44f780a997cb53956298b39faf6cd2284ea0a151/src/index.ts#L112-L120
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Okay - I've done my best with a repro here: https://github.com/atropos-tech/coverage-merge-fail-repro
When I say "skip coverage of comments", I really mean skipping instrumentation. I don't know enough about the internals to say for sure, but I do know that the statement maps output in each case do not line up. The repro has more detail in the README but I'm thinking it might have something to do with the following block in the JSON output of cypress + vite-istanbul-plugin:
"inputSourceMap": {
  "version": 3,
  "sources": [
    "<REDACTED>/src/UnderTest.tsx"
  ],
  "mappings": "AAAA,OAAO,WAAW;AAUlB,wBAAwB,UAAU,EAAE,MAAM,GAAmB;AACzD,MAAI,MAAO,QAAO,oCAAC,cAAK,UAAQ;AAChC,SAAO,oCAAC,cAAK,UAAQ;AACzB;",
  "names": []
}

I don't understand how this format works and can't find any good reference material anywhere, but this block doesn't appear in vitest output so it's possible the difference in statement maps is due to this. Grateful for any further insight you might provide.

Did you try switching preserveComments value by modifying node_modules/@vitest/coverage-istanbul/**? Does that actually help?

When I say "skip coverage of comments", I really mean skipping instrumentation.

Comments are not instrumented, they cannot be executed in any way. https://github.com/istanbuljs/istanbuljs/blob/main/packages/istanbul-lib-instrument/src/visitor.js

I have not tried modifying the code yet as I though some expert commentary would be more use than blundering about stuff I didn't understand. I did, however, identify that both vitest and vite-plugin-istanbul call istanbul-lib-instrument (see the snippets I linked to above) and that they seem to call it in a very different way. Therefore (so I reasoned) the difference in behaviour is likely to be caused by the difference in the API call. Does that seem like a good inference? Or am I missing something important?


Modal in 2.0.0-beta.9 no longer adds page class name to ion-page element

The element has a class attribute with a generated classname like "user-login" if the page class is named "UserLogin". This is no longer the case for modals.
see #6606

Hello, thanks for opening an issue with us! Would you be able to provide a plunker that demonstrates this issue? Thanks for using Ionic!

Hi @jgw96, I took a closer look and here's what I found:
In<EMAIL_ADDRESS>there is an ion-page element with the corresponding css classname of the javascript component.  I use this to add custom styles like so:

But in beta.9, the ion-page has been replaced with ion-modal-inner.  That's fine, but can we add the css classname for the javascript element to that element?  That will prevent my styles from breaking all over the place.

Thanks for the info! If im not thinking wrong this was part of the change when we added inset modals on bigger screens. I will discuss this with my teammates and see what they think.

Thanks for the issue! This was actually changed recently to use ion-page again, but it was adding the class as PascalCase. I've fixed it for the beta 10 release and created a nightly if you'd like to test it out:
npm install --save<EMAIL_ADDRESS>
Thanks again! :smile:

Thanks @brandyscarney!  I tried out the nightly but it looks like there's a problem with ion-navbar not showing up now.  I'm going to stick with beta.8 until 10 comes out. 😀

@jasonwaters Oh yes we've changed a bit of the structure. We'll have some steps to upgrade to beta 10 in the changelog! 😊

@brandyscarney Heh, the code didn't take long to disappear again I guess. On Jun 28, this commit https://github.com/driftyco/ionic/commit/215c6d846c6eb157b4510e63d863d2fdcf13b9af#diff-7b81c66d6f3e9c4b82c40ee5ecd30e50
deleted your fix (in fact, the whole loadComponent function), and now with Ionic 2 RC0 we are back to no class name in a modal. Would you mind adding it again? :blush:


adding EG4-3000-EHV modbus protocol doc and ignoring the python venv dirs

Added the modbus protocol file and updated gitignore with python venv paths.

looks like a smaller eg4 protocol, utilizing the holding register.
i can implement it in a bit.


Changing per page in remote mode makes two requests to the server.

Issue Type (delete the irrelevant ones)

[x] Bug

Specs
vue-good-table 2.21.8
VueJs 2.6.12
Browser: Version 88.0.4324.190 (Official Build) (64-bit)
Expected Behavior
When per page is changed, only one event is emitted and one request is made to the server.
Actual Behavior
When per page is changed, two requests are made to the server.
Steps to Reproduce the Problem

Use remote mode.
Change per page.
Watch two requests made.

This is from chrome network tab when per page was changed once.

Using a setup right from the docs. Nothing extra going on here. And no, I have absolutely no other listeners/handlers for the per page change event.

methods: {
...,
updateParams(newProps) {
      this.serverParams = Object.assign({}, this.serverParams, newProps);
  },
onPageChange(params) {
    this.updateParams({page: params.currentPage});
    this.loadItems();
},
onPerPageChange(params) {
    this.updateParams({perPage: params.currentPerPage});
    this.loadItems();
},
onSortChange(params) {
    this.updateParams({
        sort: [{
            type: params[0].type,
            field: params[0].field,
        }],
    });
    this.loadItems();
},
loadItems() {
    this.getFromServer(this.serverParams)
        .then(({ data }) => {
            this.totalRecords = data.totalRecords;
            this.rows = data.rows;
        });
},
getFromServer(serverParams) {
    let routeParams = {
        ...,
        ...serverParams,
    };
    return axios.get('https://acme.com', routeParams));
}
}

@xaksis I believe it is because when per page is changed, it is now changing page back to page 1. This emits two events. Thus, two requests are made. Hmmm....

https://github.com/xaksis/vue-good-table/issues/809 went in between 2.21.7 and 2.21.8. I assume that is the cause, also the rows per page keeps resetting to 10 for me, going from 2.21.7 to 2.21.8, and I think that may also be related.

https://github.com/xaksis/vue-good-table/compare/v2.21.7...v2.21.8

any update for this bug ?

try this solution
onPageChange ({ currentPage }) {
if (this.currentPage !== currentPage) {
this.currentPage = currentPage
this.__updateParams({ page: currentPage })
this.loadTransactions()
}
},
onPerPageChange ({ currentPerPage }) {
if (this.transactionTableRowCount !== currentPerPage) {
this.transactionTableRowCount = currentPerPage
this.__updateParams({ limit: currentPerPage, page: 1 })
this.loadTransactions()
}
},


Add optional condition when updating/re-opening Work Items

Summary of the Pull Request
What is this about?
PR Checklist

[ ] Applies to work item: #xxx
[ ] CLA signed. If not, go over here and sign the CLI.
[ ] Tests added/passed
[ ] Requires documentation to be updated
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Info on Pull Request
What does this include?
Validation Steps Performed
How does someone test & validate?

Codecov Report

Merging #3227 (c24a218) into main (512bb07) will decrease coverage by 3.92%.
The diff coverage is 18.18%.

@@            Coverage Diff             @@
##             main    #3227      +/-   ##
==========================================
- Coverage   29.55%   25.63%   -3.92%
==========================================
  Files         332      152     -180
  Lines       39199    16299   -22900
==========================================
- Hits        11584     4178    -7406
+ Misses      27615    12121   -15494

Impacted Files
Coverage Δ

...Service/ApiService/onefuzzlib/notifications/Ado.cs
0.00% <0.00%> (ø)

src/ApiService/ApiService/OneFuzzTypes/Model.cs
72.72% <100.00%> (+0.03%)
:arrow_up:

... and 180 files with indirect coverage changes


SyntaxError - missing comma in function call not handled

def test(a, b):
   pass
test((1, 2) (3, 4))

gives rise to SyntaxError: invalid syntax which gets no hint from friendly-traceback.

For some reason, I can not reproduce this a SyntaxError. This case is (at least now) handled reasonably well.


S3 - Support virtual-hosted style buckets

[WIP] This pull request adds support for S3 virtual-hosted addressing style to rusoto_s3 crate.
Without this change, users of rusoto_s3 crate cannot access Amazon S3 buckets created after September 30, 2020. (Update: AWS has announced that they will delay the deprecation)  This is because AWS has deprecated path-style addressing, which is the only style supported by current rusoto_s3 release. See this blog post from AWS for more details of the path-style deprecation.
Fixes: #1482, #1789
Breaking Changes
This pull request includes breaking changes:

Change the default S3 addressing style to auto, which makes S3Client to use virtual-hosted-style whenever possible and to fall back to path-style when necessary.

This should be the most preferable choice for the users using Amazon S3.
However, other users who use S3 compatible object storages such as Ceph and MinIO may have problem accessing their storages (e.g. by a DNS error; no such host). This is because their storages may not have configured for virtual-hosted-style. For example, they will need to add a DNS entry every time a new bucket is created.
They can fix this by changing the addressing style in S3Client back to path-style.
This will be documented in the following places:

Rustdoc (under rusoto_s3::util::AddressingStyle) (TODO)
https://rusoto.org (TODO).

Change the return type of S3 get_presigned_url() from String
to Result<String, InvalidDnsNameError>.

This change is needed to support different S3 addressing styles in presigned URL.

API Changes
This pull request has the following API additions and changes:

Add an enum rusoto_s3::util::AddressingStyle with variants Auto, Virtual and Path.

The default variant is Auto.
These variants behaves exactly like the options in s3.addressing_style in Boto3.

Add a struct rusoto_s3::util::S3Config, which has only one public field addressing_style.
Add a private filed config: S3Config to rusoto_s3::S3Client.
Add a public field addressing_style to rusoto_s3::util::PreSignedRequestOption.
Add a struct rusoto_core::error::InvalidDnsNameError.

This serves the exact same purpose to InvalidDNSNameError exception in Boto3.

Add a variant to rusoto_core::error::Rusoto
As mentioned above, chang the return type of S3 get_presigned_url() from String
to Result<String, InvalidDnsNameError>.

The Behavior of AddressingStyle
AddressingStyle provides the same behavior to s3.addressing_style in Boto3 (Reference).
Here are some details (copied from an issue comment of #1482)

At first this seemed pretty straight forward, but having a look at how it is implemented in botocore it becomes clear that there is some more logic involved.
Quick write-up of the main points:

A ListAllBuckets request does not have a bucket associated with it so "virtual hosting" style is not possible at all.
bucket names have to comply with valid DNS names, otherwise "path style" will be used. This is the case for:

bucket names containing "."
bucket_name.length < 3 or bucket_name.length > 63
if the bucket name does not match the regex [a-z0-9][a-z0-9\-]*[a-z0-9]

The transformation is skipped if its a GetBucketLocation request to avoid any sigv4 issues (not sure why there are issues)

Automated Testing (CI)
This pull request includes some additional unit tests (IN-PROGRESS).
The existing unit tests are updated to use AddressingStyle::Auto and some unit tests are added for ListAllBuckets and GetBucketLocation, which require AddressingStyle::Path.
The integration tests provided by rusoto_tests crate has the following changes:

Introduced the following environment variables to the test module rusoto_tests::s3:

S3_PROXY to set the HTTP proxy URL to the test S3/HTTP clients.
S3_ADDRESSING_STYLE to set the addressing style in S3 client and presigned URL. (Only value path is recognized for Path variant, otherwise Auto variant is used)

Integration tests using MinIO is changed to tests virtual-hosted-style addressing with AddressingStyle::Auto.

This is done by:

Setting the S3 endpoint http://s3.us-east-1.rusoto.example.com:9000 to MinIO server and also to S3Client.
And setting the IP address of the S3 endpoint http:://<IP_ADDRESS>:9000 as the proxy of the S3Client and, for testing presigned URLs, the proxy of reqwest::Client.

Integration tests using Ceph kept testing path-style addressing with AddressingStyle::Path.

Notes

CI at Semaphore CI is failing due to a commit made by outside this pull request:

https://github.com/rusoto/rusoto/commit/9cc84f2577655b4785413e5dc5f3242e25c8ac1a#diff-e9c12d89c87978a0f70cd8663fd3450dL6

There is an open pull request #1817 to remove regex dependency from rusoto_credential crate.
In this pull request, I have added a regex dependency to rusoto_s3 crate. Maybe I should remove it. The regex matcher here is simple enough and can be easily replaced with some Rust codes.
rusoto/services/s3/src/custom/util.rs
fn is_valid_dns_name(bucket_name: &str) -> bool {
    use lazy_static::lazy_static;
    use regex::Regex;

    // ...

    lazy_static! {
        static ref LABEL_RE: Regex = Regex::new(r"[a-z0-9][a-z0-9\-]*[a-z0-9]").unwrap();
    }
    LABEL_RE.is_match(bucket_name)
}

OK. I removed the regex dependency from this pull request in this commit.

Hello is there any progress on this? 😄

@kennytm – Hi. I am basically done with all coding stuff here. I want to add some test cases and documentation. I will work on them in coming weekend.

Sorry for the big delay. I am planning to work on this in this week.

Sorry for the big delay. I am planning to work on this in this week.

Would this also fix #1823?

This feature is so important but without any update .. 🎱

@tatsuya6502 is there a schedule on reviewing this feature? https://github.com/tikv/rusoto already integrates your patch and push it onto production by https://github.com/tikv/tikv/pull/9425 .
If we can get this feature in upstream, we can brining it to a wider range of developers. Looking forward to your update.

Looks good, @tatsuya6502, can you convert this from a draft to a full PR please? 👍🏻
I'd love for this to get merged.

Hi @iliana. Some users still need virtual hosted style access for S3. I did some work here but it is pretty outdated now, so I will need to rebase it. If I do it, is there any chance that this PR will be merged? I see the followings on the README, so I am curious:
https://github.com/rusoto/rusoto#maintenance-status

⚠ Rusoto is in maintenance mode. ⚠
The current maintainers only have the bandwidth to review dependency bumps and obvious bugfixes. Our bandwidth for reviewing new features is extremely limited.
While you are welcome to submit PRs that implement new features or refactor existing code, they are unlikely to be merged unless we can find more active maintainers.
Please see https://github.com/rusoto/rusoto/issues/1651 for details.

At this point this PR is a bugfix and should get prioritized.
I created a bucket yesterday and the rusoto is no longer capable to access it.

The issue with the AWS Rust SDK is that the project README clearly states that it is not production ready.
I certainly hope that some people interested in Rusoto will take over the project soon as the original maintainers have asked for.

I certainly hope that some people interested in Rusoto will take over the project soon as the original maintainers have asked for.

The official AWS SDK for Rust is that project.

The issue with the AWS Rust SDK is that the project README clearly states that it is not production ready.

Full disclosure: I used to work on the AWS Rust SDK, but haven't for a little bit, so I hope don't think that I'm speaking out of turn for the team that currently works on it. I have shared similar things sentiments with my folks at my current employer with the team's okay, but since this issue might have larger reach, I'll speak in more general terms.
With that out of the way: if you stick with the high-level, vanilla clients in a relatively vanilla way (e.g., using the AWS Rust SDK clients as you would use the Rusoto clients), run cargo update occasionally, and are okay with breaking changes that impact user-configurable, but advanced features such as middleware or updates to pre-1.0 dependencies, then you can comfortably use the official Rust SDK with minimal breaking changes.
For context, AWS has an extremely high bar for what they consider to be "generally available" or "production ready". They consider security backports to older versions and something like a 5+ year stability policy necessary to be labeled "generally available"; the AWS Rust SDK cannot yet commit to such things. If you need those things, then yes: the AWS SDK for Rust isn't ready for you, but if you're commenting on this issue, I strongly suspect that it's not a hard requirement.

FYI. The official AWS SDK S3 for Rust now supports virtual-hosted style bucket. It is enabled by default.

aws-sdk-s3 v0.23.0

https://github.com/awslabs/aws-sdk-rust/releases/tag/release-2023-01-13

⚠🎉 (https://github.com/awslabs/smithy-rs/issues/1784, https://github.com/awslabs/smithy-rs/issues/2074) Integrate Endpoints 2.0 into the Rust SDK. Endpoints 2.0 enables features like S3 virtual addressing & S3 object lambda. As part of this change, there are several breaking changes although efforts have been made to deprecate where possible to smooth the upgrade path.
...

⚠🎉 (https://github.com/awslabs/smithy-rs/issues/1784, https://github.com/awslabs/smithy-rs/issues/2074) Add additional configuration parameters to aws_sdk_s3::Config.
The launch of endpoints 2.0 includes more configuration options for S3. The default behavior for endpoint resolution has been changed. Before, all requests hit the path-style endpoint. Going forward, all requests that can be routed to the virtually hosted bucket will be routed there automatically.

force_path_style: Requests will now default to the virtually-hosted endpoint <bucketname>.s3.<region>.amazonaws.com
use_arn_region: Enables this client to use an ARN’s region when constructing an endpoint instead of the client’s configured region.
accelerate: Enables this client to use S3 Transfer Acceleration endpoints.

Note: the AWS SDK for Rust does not currently support Multi Region Access Points (MRAP).


Management Tool 4.1.3

Used the below command
docker run -it -p 3000:5000
--name arrowhead-react-container
-e REACT_APP_ARROWHEAD_SR_URL=https://localhost:8443
-e REACT_APP_ARROWHEAD_AUTH_URL=https://localhost:8445
-e REACT_APP_ARROWHEAD_ORCH_URL=https://localhost:8441
-e REACT_APP_ARROWHEAD_GK_URL=https://localhost:8449
-e REACT_APP_ARROWHEAD_GW_URL=https://localhost:8453
-e REACT_APP_ARROWHEAD_EH_URL=https://localhost:8455
portus.arrowhead-ci.tmit.bme.hu/tools/management-tool
But unable to save any data under Authorization and Gatekeeper tab in the management tool.
Getting error " Saving is unsuccessful"

Kudos to the successful event and great work!

Hello!
Thanks :)
Could you please click on a request and show me the Headers and the Preview?
Svetlin

Sorry Svetlin, I don't know whether I get your question properly or not. I have provided the information to the best I can.

Thank you!

Hello,
Is there any update regarding it?
Thanks and regards,
Suman

Hello!
Could you please click on a request and show me the Headers and the Preview?

Operating in insecure mode :

Is there any update?
Thanks and regards,
Suman

Hello!
Please provide a screenshot with information. Look at mine. It has HTTP status code, message . And please provide a screenshot from the response tab also.
Best wishes,
Svetlin

Hello,
I don't see any status code in the Header and there is no response data loaded under the response tab as shown in the below screenshots. Let me know what might have gone wrong.

Thanks and regards,
Suman

The problem is, that you don't have a certificate / the proper certificate installed.
What operation system are you using?
You are trying to access the arrowhead.tmit.bme.hu Arrowhead cloud which requires a custom Sysop.p12.
Before you were trying to access Arrowhead running on localhost.
Which one would you like to access?

Operating System: Linux
I would like to access Arrowhead running on localhost.

In your docker run command, which you linked first, you used localhost urls, but in the screenshot you were using the arrowhead.tmit.bme.hu url. This is the issue.

The issue is with the certificates. I need to figure out how to add certificates in chrome for Linux OS. Once I figure out that, I think the rest of the issue will be solved. Thanks for the help and support!


[SMALLFIX] Fix DataPercentageinAlluxio always shows 0%

What changes are proposed in this pull request?
The LsCommand displays DataInAlluxioPercentage, but it always shows 0% which is misleading.
This change changes the DataInAlluxioPercentage column to a fix string FILE in the Lscommand.
Why are the changes needed?
Please clarify why the changes are needed. For instance,
As mentioned above, it fixes the bug that LsCommand always shows 0% for DataInAlluxio.
Does this PR introduce any user facing changes?
Yes, it will change the display of LsCommand.
It will change the output of LsCommand for files but not directories. For files, it will be the follow format
./alluxio fs ls /file_path
          FileSize     PeristenceState    Timestamp    FILE     FilePath

Please list the user-facing changes introduced by your change, including
It changes the percentage of data in Alluxio to a fix string FILE as shown above.

Hi @Zijian-Zhu, I saw another PR is still marked as cla-missing.
How does cla-missing label work? shouldn't all existing and future PRs from me are not marked with cla-missing. Thanks for the help.

Thanks for the contribution! Updating the PR description with what it looks like after the update would be very helpful for us to understand the change easily since it's user-facing.

Thanks @jja725. I updated the description and title.

alluxio-bot, merge this please

alluxio-bot, merge this please

fs ls output before and after this patch:
HuanghuaMacBookPro:alluxio huanghua$ ./bin/alluxio fs ls /
# command-line-arguments
ld: warning: -no_pie is deprecated when targeting new OS versions
-rw-rw-r--  huanghua       supergroup<PHONE_NUMBER>4                 08-15-2023 17:33:09:493   0% /16G_from_fuse
-rw-r--r--  huanghua       supergroup                6334                 08-14-2023 13:43:59:481   0% /DevelopmentWorkflow.md
-rw-r--r--  huanghua       supergroup                6265                 08-14-2023 13:50:26:820   0% /DevelopmentWorkflow.md.2
-rw-r--r--  huanghua       supergroup                6228                 08-14-2023 13:56:10:636   0% /DevelopmentWorkflow.md.3
-rw-r--r--  huanghua       supergroup                6228                 08-10-2023 14:17:03:367   0% /DevelopmentWorkflow.md.4
-rw-r--r--  huanghua       supergroup<PHONE_NUMBER>                 08-11-2023 13:50:55:592   0% /File_8GB
-rw-r--r--  huanghua       supergroup             1048810                 07-07-2023 12:06:00:668   0% /HDFS.txt
-rw-r--r--  huanghua       supergroup                4096                 02-27-2023 11:52:06:116 100% /HDFS2.txt
-rw-rw-rw-  huanghua       supergroup                 240                 08-07-2023 23:35:44:993   0% /README.txt.bak
-rw-rw-r--  huanghua       supergroup                8192                 08-15-2023 11:17:07:119   0% /aaaaa
-rw-rw-r--  huanghua       supergroup               16384                 08-15-2023 11:30:24:486   0% /bbbbb
-rw-rw-r--  huanghua       supergroup                   0                 08-04-2023 22:12:00:048 100% /bigfile4g
drwxr-xr-x  huanghua       supergroup                   0                 01-01-1970 08:00:00:000  DIR /default_tests_files
drwxr-xr-x  huanghua       supergroup                   0                 01-01-1970 08:00:00:000  DIR /dir
-rw-r--r--  huanghua       supergroup               40989                 08-04-2023 21:06:13:491   0% /fio.txt
-rw-rw-r--  huanghua       supergroup                 340                 08-07-2023 16:49:43:847   0% /fuse_read_test.sh
-rw-r--r--  huanghua       supergroup           144188848                 04-11-2023 19:25:47:018   0% /go.pkg
drwxr-xr-x  root           supergroup                   0                 01-01-1970 08:00:00:000  DIR /haha
-rw-r--r--  root           supergroup                1643                 02-23-2023 17:25:21:281   0% /hdfs-site.xml
-rwxr-xr-x  huanghua       supergroup           145609416                 08-04-2023 22:17:32:932   0% /jdk-11.0.18_linux-x64_bin.deb
-rw-r--r--  huanghua       supergroup<PHONE_NUMBER>                 08-03-2023 13:16:18:835   0% /largefile4g
-rw-rw-r--  huanghua       supergroup<PHONE_NUMBER>                 08-04-2023 22:23:58:390   0% /largefile4g.w
-rw-r--r--  huanghua       supergroup                 167                 02-23-2023 23:28:17:431   0% /maven-generate.sh.orig
-rw-rw-r--  huanghua       supergroup                2664                 08-09-2023 16:17:30:662   0% /pom.xml
-rw-r--r--  huanghua       supergroup                 245                 08-07-2023 16:35:58:602   0% /read_loop.sh
drwxr-xr-x  root           supergroup                   0                 01-01-1970 08:00:00:000  DIR /rmstate
drwx------  huanghua       supergroup                   0                 01-01-1970 08:00:00:000  DIR /user
HuanghuaMacBookPro:alluxio huanghua$
HuanghuaMacBookPro:alluxio huanghua$
HuanghuaMacBookPro:alluxio huanghua$
HuanghuaMacBookPro:alluxio huanghua$ ./bin/alluxio fs cat /DevelopmentWorkflow.md > /dev/null
# command-line-arguments
ld: warning: -no_pie is deprecated when targeting new OS versions
HuanghuaMacBookPro:alluxio huanghua$ ./bin/alluxio fs cat /DevelopmentWorkflow.md.2 > /dev/null
# command-line-arguments
ld: warning: -no_pie is deprecated when targeting new OS versions
HuanghuaMacBookPro:alluxio huanghua$
HuanghuaMacBookPro:alluxio huanghua$
HuanghuaMacBookPro:alluxio huanghua$
HuanghuaMacBookPro:alluxio huanghua$ ./bin/alluxio fs ls /
# command-line-arguments
ld: warning: -no_pie is deprecated when targeting new OS versions
-rw-rw-r--  huanghua       supergroup<PHONE_NUMBER>4                 08-15-2023 17:33:09:493   0% /16G_from_fuse
-rw-r--r--  huanghua       supergroup                6334                 08-14-2023 13:43:59:481 100% /DevelopmentWorkflow.md
-rw-r--r--  huanghua       supergroup                6265                 08-14-2023 13:50:26:820 100% /DevelopmentWorkflow.md.2
-rw-r--r--  huanghua       supergroup                6228                 08-14-2023 13:56:10:636   0% /DevelopmentWorkflow.md.3
-rw-r--r--  huanghua       supergroup                6228                 08-10-2023 14:17:03:367   0% /DevelopmentWorkflow.md.4
-rw-r--r--  huanghua       supergroup<PHONE_NUMBER>                 08-11-2023 13:50:55:592   0% /File_8GB
-rw-r--r--  huanghua       supergroup             1048810                 07-07-2023 12:06:00:668   0% /HDFS.txt
-rw-r--r--  huanghua       supergroup                4096                 02-27-2023 11:52:06:116 100% /HDFS2.txt
-rw-rw-rw-  huanghua       supergroup                 240                 08-07-2023 23:35:44:993   0% /README.txt.bak
-rw-rw-r--  huanghua       supergroup                8192                 08-15-2023 11:17:07:119   0% /aaaaa
-rw-rw-r--  huanghua       supergroup               16384                 08-15-2023 11:30:24:486   0% /bbbbb
-rw-rw-r--  huanghua       supergroup                   0                 08-04-2023 22:12:00:048 100% /bigfile4g
drwxr-xr-x  huanghua       supergroup                   0                 01-01-1970 08:00:00:000  DIR /default_tests_files
drwxr-xr-x  huanghua       supergroup                   0                 01-01-1970 08:00:00:000  DIR /dir
-rw-r--r--  huanghua       supergroup               40989                 08-04-2023 21:06:13:491   0% /fio.txt
-rw-rw-r--  huanghua       supergroup                 340                 08-07-2023 16:49:43:847   0% /fuse_read_test.sh
-rw-r--r--  huanghua       supergroup           144188848                 04-11-2023 19:25:47:018   0% /go.pkg
drwxr-xr-x  root           supergroup                   0                 01-01-1970 08:00:00:000  DIR /haha
-rw-r--r--  root           supergroup                1643                 02-23-2023 17:25:21:281   0% /hdfs-site.xml
-rwxr-xr-x  huanghua       supergroup           145609416                 08-04-2023 22:17:32:932   0% /jdk-11.0.18_linux-x64_bin.deb
-rw-r--r--  huanghua       supergroup<PHONE_NUMBER>                 08-03-2023 13:16:18:835   0% /largefile4g
-rw-rw-r--  huanghua       supergroup<PHONE_NUMBER>                 08-04-2023 22:23:58:390   0% /largefile4g.w
-rw-r--r--  huanghua       supergroup                 167                 02-23-2023 23:28:17:431   0% /maven-generate.sh.orig
-rw-rw-r--  huanghua       supergroup                2664                 08-09-2023 16:17:30:662   0% /pom.xml
-rw-r--r--  huanghua       supergroup                 245                 08-07-2023 16:35:58:602   0% /read_loop.sh
drwxr-xr-x  root           supergroup                   0                 01-01-1970 08:00:00:000  DIR /rmstate
drwx------  huanghua       supergroup                   0                 01-01-1970 08:00:00:000  DIR /user
HuanghuaMacBookPro:alluxio huanghua$

==========after this patch=================

HuanghuaMacBookPro:alluxio huanghua$ ./bin/alluxio fs ls /
# command-line-arguments
ld: warning: -no_pie is deprecated when targeting new OS versions
-rw-rw-r--  huanghua       supergroup<PHONE_NUMBER>4                 08-15-2023 17:33:09:493 FILE /16G_from_fuse
-rw-r--r--  huanghua       supergroup                6334                 08-14-2023 13:43:59:481 FILE /DevelopmentWorkflow.md
-rw-r--r--  huanghua       supergroup                6265                 08-14-2023 13:50:26:820 FILE /DevelopmentWorkflow.md.2
-rw-r--r--  huanghua       supergroup                6228                 08-14-2023 13:56:10:636 FILE /DevelopmentWorkflow.md.3
-rw-r--r--  huanghua       supergroup                6228                 08-10-2023 14:17:03:367 FILE /DevelopmentWorkflow.md.4
-rw-r--r--  huanghua       supergroup<PHONE_NUMBER>                 08-11-2023 13:50:55:592 FILE /File_8GB
-rw-r--r--  huanghua       supergroup             1048810                 07-07-2023 12:06:00:668 FILE /HDFS.txt
-rw-r--r--  huanghua       supergroup                4096                 02-27-2023 11:52:06:116 FILE /HDFS2.txt
-rw-rw-rw-  huanghua       supergroup                 240                 08-07-2023 23:35:44:993 FILE /README.txt.bak
-rw-rw-r--  huanghua       supergroup                8192                 08-15-2023 11:17:07:119 FILE /aaaaa
-rw-rw-r--  huanghua       supergroup               16384                 08-15-2023 11:30:24:486 FILE /bbbbb
-rw-rw-r--  huanghua       supergroup                   0                 08-04-2023 22:12:00:048 FILE /bigfile4g
drwxr-xr-x  huanghua       supergroup                   0                 01-01-1970 08:00:00:000  DIR /default_tests_files
drwxr-xr-x  huanghua       supergroup                   0                 01-01-1970 08:00:00:000  DIR /dir
-rw-r--r--  huanghua       supergroup               40989                 08-04-2023 21:06:13:491 FILE /fio.txt
-rw-rw-r--  huanghua       supergroup                 340                 08-07-2023 16:49:43:847 FILE /fuse_read_test.sh
-rw-r--r--  huanghua       supergroup           144188848                 04-11-2023 19:25:47:018 FILE /go.pkg
drwxr-xr-x  root           supergroup                   0                 01-01-1970 08:00:00:000  DIR /haha
-rw-r--r--  root           supergroup                1643                 02-23-2023 17:25:21:281 FILE /hdfs-site.xml
-rwxr-xr-x  huanghua       supergroup           145609416                 08-04-2023 22:17:32:932 FILE /jdk-11.0.18_linux-x64_bin.deb
-rw-r--r--  huanghua       supergroup<PHONE_NUMBER>                 08-03-2023 13:16:18:835 FILE /largefile4g
-rw-rw-r--  huanghua       supergroup<PHONE_NUMBER>                 08-04-2023 22:23:58:390 FILE /largefile4g.w
-rw-r--r--  huanghua       supergroup                 167                 02-23-2023 23:28:17:431 FILE /maven-generate.sh.orig
-rw-rw-r--  huanghua       supergroup                2664                 08-09-2023 16:17:30:662 FILE /pom.xml
-rw-r--r--  huanghua       supergroup                 245                 08-07-2023 16:35:58:602 FILE /read_loop.sh
drwxr-xr-x  root           supergroup                   0                 01-01-1970 08:00:00:000  DIR /rmstate
drwx------  huanghua       supergroup                   0                 01-01-1970 08:00:00:000  DIR /user
HuanghuaMacBookPro:alluxio huanghua$
HuanghuaMacBookPro:alluxio huanghua$

Apparently, the DataInAlluxioPercentage  was working properly.  There is no bug.
After this patch, DataInAlluxioPercentage  is missing. This is wrong.

Thanks @huanghua78 for double-checking this.
@jja725 What do you think? should we revert this PR? thanks

I share the same concern, this pr just removes one field, not actually fix anything. What is the difference between your experiment and hua's? Why his shows the percentage?

I share the same concern, this pr just removes one field, not actually fix anything. What is the difference between your experiment and hua's? Why his shows the percentage?

Thanks @yyongycy. When We ran this command, the percentage always shows 0%.
We consulted with @jja725 and @jja725 mentioned ls right now doesn't support PercentageInAlluxio since it uses listStatus not getStatus.

My concern here is basically because the cache storage is not correct in a global view. This percentage here is basically the percentage on this specific worker and if we run several ls on different paths this would show inconsistent results. And this is misleading to the customer that if we load data into alluxio and we still show a 0% cache rate. And in a big cluster we would probably get mostly 0 value for this field and confuse customers. And I think the recommended way would be using the getStatus command which only points to a specific file and shows the correct in alluxio percentage rate.
I'm happy to discuss more about this and see if we can find a perfect solution to this.


Support Zero-trust architecture

Details in Design Doc

I am interested in this work too.

The list of sub-tasks happening on this:

[ ] Launch SPIRE agent on the VM in a secure way. @mrsabath is looking into this along with the SPIRE community on providing a secure (and standard) way of doing this.
[ ] Deploy SPIRE Server in a reachable point to the VMs where SPIRE agent is deployed. The SPIRE server and the orchestrator share a common root of trust. The SPIRE agent gets the OIDC certificate from this server, periodically.
[ ] Orchestrator to check with SPIRE server on the status of the VMs, their identities, and update the states in the tag service.
[ ] Tag service to maintain the leaf mapping of identity in SPIFFE format to IP address, and this will be validated by the orchestrator periodically, and action taken by orchestrator upon any violation.


LSTM Example please

Nice work. Please make a LSTM - GRU Example...
Μπράβο 👍

Please take a look at the new Chapter 6 examples.  Ευχαριστώ!


feat: use clsx library for className props.

Changes description
Use clsx instead of null operator because it was returning undefined.
As you can see in the followinf snapshot

Context
It brings more clarity in html. We could see sometime undefined and bring questioning.
Checklist

[x] Make sure you are requesting to pull a topic/feature/bugfix branch. Please, don't request directly from your main!
[x] Check commits & PR names matches our requested structure. It must follow the https://www.conventionalcommits.org pattern.
[x] Check your code additions will fail neither code linting checks.
[x] I have reviewed the submitted code.
[x] I have tested on related showcases.
[ ] If it includes design changes, please ask for a review design-system-core-team-design GitHub team.

Does this introduce a breaking change?

No

Other information

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Issue with MemoryModuleType.GOLEM_SPAWN_CONDITIONS mapping

What’s the issue?

https://pastebin.com/BEjZtRKj
I get this crash...
According to one of the guys from discord this is due to mappings (Can't access field or something)
In #user-general

Im not seeing anything wrong with the mappings. this is very little to go off.

Are all your mods for 19w12b?

Yes they are

either way this has nothing to do with yarn, if anything it would be a bug in loom or something so it can be closed here

Please make sure to address this issue though


Refactor: use docker compose

Refactor Dockerfile.lite to install xformers after installing webui
Remove && python webui.py --xformers --listen --enable-insecure-extension-access --gradio-queue to execute them in docker-compose
Create docker-compose.yaml

TODO

[x] Add the Oil_painting model to be downloaded automatically
[ ] Add the model in the docker image
[x] Create empty folder for the models or specify where the models should be

Remember to create the models folder


hotfix: update dataverse to reflect changes in 4.0

Studies are now called datasets
Remove reference to only public datasets as now drafts can be linked

:+1:

fixed! thanks


Fix performance when using retpolines

retpolines are used to harden against speculative load vulnerabilities with indirect function calls.  This can be enabled with the retpoline target feature in Rust.
Performance when branching via static function pointer suffers--in some benchmarks I noticed overhead increasing from <1 cycle to ~20 cycles when enabling retpolines.  Fortunately, branch prediction is very fast for something like multiversioning where the same branch is always taken.  Currently direct branching is used by generic functions, but the dispatcher should be modified to use direct branching for all function types.

Fixed in fba245c


Implement Exec and ExecContext

Merged here: https://github.com/vippsas/go-querysql/commit/b0d712e1f52c0c796263999c51b834d24b8a8a14


Customize your own model tutorial doesn't work as it released

Hi! I try to build my own model following your tutorial https://kashgari.readthedocs.io/en/tf.keras-version/tutorial/sequence_labeling_model.html
and I've met some problems. For example, import problems

I looked at the source code, and there is actually no L in layers. What did you mean by that?
Plus, I don't understand, why BaseLabelingModel is not importing at all - from any path, and from just tasks, and from tasks.labelling
Can you help me a bit?

Yep, this is a version issue. This tutorial is actually for the tf.keras version kashgari-tf. I guess you are using the keras version. Just re-install the kashgari.
pip uninstall kashgari
pip install kashgari-tf

thank you! it helps


ci: l4lb: gather more infos about docker-in-docker issues

Sometimes, the L4LB tests timeout waiting for the docker (in docker) instance to get ready.
+[06:55:18] docker run --privileged --name lb-node -d --network cilium-l4lb -v /lib/modules:/lib/modules docker:dind
ca31f2a72a098bf612d569fee976e7e17779a1546337748dc62b63c99da13271
+[06:55:18] docker exec -t lb-node mount bpffs /sys/fs/bpf -t bpf
+[06:55:18] docker run --name nginx -d --network cilium-l4lb nginx
544abbd0503584c582da50480d5f96eae5ecadb426d48d6fee078558b45451b2
+[06:55:18] docker exec -t lb-node docker ps
+[06:55:18] sleep 1
+[06:55:19] docker exec -t lb-node docker ps
+[06:55:19] sleep 1
+[06:55:20] docker exec -t lb-node docker ps
Error response from daemon: Container ca31f2a72a098bf612d569fee976e7e17779a1546337748dc62b63c99da13271 is not running
+[06:55:20] sleep 1
+[06:55:21] docker exec -t lb-node docker ps
Error response from daemon: Container ca31f2a72a098bf612d569fee976e7e17779a1546337748dc62b63c99da13271 is not running
+[06:55:21] sleep 1
+[06:55:22] docker exec -t lb-node docker ps
Error response from daemon: Container ca31f2a72a098bf612d569fee976e7e17779a1546337748dc62b63c99da13271 is not running
+[06:55:22] sleep 1
+[06:55:23] docker exec -t lb-node docker ps
Error response from daemon: Container ca31f2a72a098bf612d569fee976e7e17779a1546337748dc62b63c99da13271 is not running
+[06:55:20] docker exec -t lb-node docker ps
Error response from daemon: Container ca31f2a72a098bf612d569fee976e7e17779a1546337748dc62b63c99da13271 is not running

Unfortunately, fetching the LB logs after the failed test doesn't help either, as this fails with the same error.
Run docker exec -t lb-node docker logs cilium-lb
  docker exec -t lb-node docker logs cilium-lb
...
Error response from daemon: Container ca31f2a72a098bf612d569fee976e7e17779a1546337748dc62b63c99da13271 is not running

Therefore, this commit adds an additional job step that fetches the status and logs of the docker instance itself.
Examples:

https://github.com/cilium/cilium/actions/runs/9053573212/job/24872468158
https://github.com/cilium/cilium/actions/runs/9067978554/job/24914256383
https://github.com/cilium/cilium/actions/runs/9074981805/job/24934711124
https://github.com/cilium/cilium/actions/runs/9083769577/job/24963174702

/test


Client Allocation Request for: [Personal or Organization Name]

Client Allocation Questions
Core Information

Name: hasheagle
Website / Social Media: https://www.hasheagle.com/
Region:  Asia excl. Greater China / Greater China
DataCap Requested: 50TiB
Addresses to be Notarized: f1w5cddiuvqei74uetfmcaftailvbzut3d7m6v2nq
Notary Requested: 1LISA2

@1LISA2 can you assign yourself to the issue?

@TarGet0ne thanks for the request!
Please answer the following questions giving as much detail as possible.
Please introduce yourself and the organization you represent, what is its name, nature, country of incorporation and date of establishment?
How many employees does the company currently have?
In which region do you plan to use DataCap?
What kind of social media platforms do you have (Github, Twitter, Linkedin handle, Wechat, etc.)? How many followers do you have, please share me the link or screenshot.
How did you hear about the FIL+ project?
What kind of data do you plan to store? Can you share any kind of sample data?
Are you willing to store data outside of Greater China?

@fabriziogianni7  sure, Thank you for your reminder

@fabriziogianni7 honey，I can‘t  assign myself to the issue, can you help me , I found    https://github.com/filecoin-project/filecoin-plus-client-onboarding/invitations.  not invitation to me.

No response. @TarGet0ne please open a new issue if still interested.


Select another account is not working after browser back button was clicked

Core Library
MSAL.js v2 (@azure/msal-browser)
Core Library Version
2.24.0
Wrapper Library
MSAL React (@azure/msal-react)
Wrapper Library Version
1.4.0
Description
Select another account is not working after browser back button was clicked
Error Message
No response
Msal Logs
No response
MSAL Configuration
auth: {
        clientId: "xxx",
        authority: "https://login.microsoftonline.com/xxx",
        redirectUri: "/",
        postLogoutRedirectUri: "/"
    },
    cache: {
        cacheLocation: "localStorage",
        storeAuthStateInCookie: isIE || isEdge || isFirefox
    },

Relevant Code Snippets
Issue can be reproduced using example: samples/msal-react-samples/react-router-sample

Reproduction Steps

Sign in using redirect to any account

Then go back using browser button

Select any other account.

It still shows account that was selected first time.

msalInstance.getAllAccounts() returns only first account.

Expected Behavior
User will be signed in using second account
Identity Provider
Azure AD / MSA
Browsers Affected (Select all that apply)
Chrome
Regression
No response
Source
External (Customer)

@sT0pe Going back into the middle of an already completed sign-in like this is not supported. If you want to switch users you need to call one of the sign in APIs and start the flow from the beginning.

@tnorling understood, thank you


State PMAs that are required for these mappings.

Explicitly state the PMAs required for this set of mappings to allow C
to run on RISC-V.

RVWMO isn't actually a physical memory attribute in the way the others in that bullet list are, so if we do keep some mention of RVWMO/RVTSO, it should probably move somewhere outside that list.  Otherwise LGTM.

I just removed RVWMO from the list.  I don't think we need any additional mention of RVWMO/RVTSO, but if Josh disagrees, my recommendation is to add some non-normative text just below, noting that main memory + coherence implies either RVWMO or RVTSO, and hence implies RVWMO compliance.

I just removed RVWMO from the list. I don't think we need any additional mention of RVWMO/RVTSO, but if Josh disagrees, my recommendation is to add some non-normative text just below, noting that main memory + coherence implies either RVWMO or RVTSO, and hence implies RVWMO compliance.

No problem.  It wasn't essential.


Incorrect routing when using navigationStrategy callback

Currently, I'm looking into dynamic routing in aurelia. To achieve this, I mapped all routes using a wildcard and I'm using the navigationStrategy property to determine the correct module id (as suggested in https://github.com/aurelia/router/issues/129).
configureRouter(config: RouterConfiguration, router: Router): void {
    config.map([
        { route: "**", nav: false, navigationStrategy: this.navigateToModule, settings: this }
    ]);

    router.handleUnknownRoutes(this.unknownRoutes);
}

private navigateToModule(instruction: NavigationInstruction): void {

// some logic to determine a moduleId
instruction.config.moduleId = moduleId; // A valid view-model
}

The first navigation is correct and loads the correct viewmodel, as expected. However, when I now navigate to another route in the same Router (with another moduleId), it always navigates to the current  active viewmodel (instead of the new one). The navigationStrategy callback is called witch each navigation, as expected.
The activate() function of the current (incorrect) viewmodel is called, while the navigationInstruction.config.moduleId in the activate() function contains the new moduleId (as set in the navigateToModule function). When refreshing the site, the correct viewmodel is loaded.
The code is running on the current Aurelia release (beta.1.1.0), using Typescript. I'm encountering this in all browsers. Is this expected behavior?
I also tried to map the routes using the handleUnknownRoutes (as sugested in https://github.com/aurelia/router/issues/15). This is working as expected. However, I prefer to use the described way, since it is possible to use to settings property in the router better (there is no reference to the original class in the handleUnknownRoutes callback) and it is possible to use multiple wildcards and redirect them to other functions.

@WouterOuwens Are you able to provide a plunker or link to a repo that demonstrates the problem?

Closing this issue since it was not reproducible and the OP didn't respond after several months.

@WouterOuwens How did you get around this issue? I am running up against the same problem. I'll see if I can create a reproducible scenario, forked from the TS skeleton, for the team.

OK, I have a reproducible scenario: https://github.com/Roustalski/skeleton-navigation
cd path/to/skeleton-navigation-typescript npm install && jspm install gulp watch
Click on child router, then modify the route URL:
http://localhost:9001/#/child-router/1
http://localhost:9001/#/child-router/2
http://localhost:9001/#/child-router/3
etc...
Breakpoint on child-router.ts::12 shows the module ID being swapped per logic, but the view/vm pair remains on the first module loaded for that instruction.

I was unable to reproduce it in the skeleton. In the end, I used another approach.
For my application, it was easier to route it with a simple custom router. The main navigation is still aurelia, but some "inner navigation" is a custom router. This solution gave me better control over the whole (custom) navigation pipeline.

@EisenbergEffect Can this be reopened? Here is a simple repro - skeleton-esnext. All related code is in app.js.

Ok, so I managed to make it work, in a way. The first time navigationStrategy is called navigationInstruction.config does not have viewPorts set. On subsequent calls viewPorts is set and its moduleId is set to the moduleId from the first call. So viewPorts.default.moduleId also has to be set to the moduleId we want. If this is how it should work, it has to be added to the docs about Dynamically Specify Route Components.

I had the same issue. Based on @StrahilKazlachev's comment, I have added the following line in my navigationStrategy code:
delete instruction.config.viewPorts;
here's my complete code:
private dynamicRouter(instruction: NavigationInstruction) {
  let route = /\/(.*)(\/)?/.exec(instruction.fragment);
  if (!route || !route[1] || route[1].length === 0) return;

  instruction.config.moduleId = `views/${route[1]}/view-${route[1]}`;
  instruction.config.href = instruction.fragment;
  delete instruction.config.viewPorts;
}

I must say, though, this looks like a hack and I would not expect to have to do that.

Our team hit this issue as well. The suggestion delete instruction.config.viewPorts; suggested https://github.com/aurelia/router/issues/289#issuecomment-297816986 does solve the problem for us.

@jonathaneckman Thanks for your repo. Here https://github.com/aurelia/router/blob/9ba6ef338e4e4f5e21758b245d7ebf82fb364982/src/router.ts#L726-L730 is where the issue seems to be.
After evaluating navigationStrategy, current it assumes moduleId is available on config object and continue to process.
Maybe we can do a check for undefined and normalized to null, so that it will ignore the instruction and process the one intended by devs, for example: navigate to home route like in @jonathaneckman 's repro
cc @davismj @fkleuver @jwx

@JamesFenton @jonathaneckman what's going on in navigationStrategy? before we dig into a PR I'm just curious if there's a better or easier way.


cannot search/get content from web

Hi,
I keep getting this error when it tries to search for content on the web:
web_researcher is thinking...
Error fetching or processing https://www.dckap.com/blog/magento-erp-integration/, exception:

Resource punkt_tab not found.
Please use the NLTK Downloader to obtain the resource:

import nltk
nltk.download('punkt_tab')

For more information see: https://www.nltk.org/data.html
Attempted to load tokenizers/punkt_tab/english/
Searched in:
- '/root/nltk_data'
- '/usr/local/nltk_data'
- '/usr/local/share/nltk_data'
- '/usr/local/lib/nltk_data'
- '/usr/share/nltk_data'
- '/usr/local/share/nltk_data'
- '/usr/lib/nltk_data'
- '/usr/local/lib/nltk_data'

up


Anonymous NixOS modules (e.g. from flakes) cannot be disabled

Describe the bug
An anonymous NixOS module (not included in imports by path but as a function/attr set) cannot be disabled, both because on import the module key is not specific to a module but to an import and because filterModules tries to convert all non-string elements of disabledModules to strings, probably expecting them to be paths.
This defeats the standardized nixosModules api of flakes, since one must rely on the file structure for importing and disabling for disabledModules to work.
To Reproduce

add disabledModules = [ {} ]; to configuration.nix
try to nixos-rebuild build
Result:

[root@longitude-j:/etc/nixos]# nixos-rebuild build
building Nix...
error: --- TypeError ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- nix-instantiate
at: (200:81) in file: /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix

   199|         let
   200|           moduleKey = m: if isString m then toString modulesPath + "/" + m else toString m;
      |                                                                                ^
   201|           disabledKeys = map moduleKey disabled;

cannot coerce a set to a string

Expected behavior
If possible, modules should probably get a unique key, regardless of how they are given. This should also be used in disabledModules.

I now that it's quite straightforward but I still think that it's better to rely on a test machine than to rebuild your own config.
import ./make-test-python.nix ({ pkgs, ... }: {
  name = "test";

  nodes.test = { pkgs, ... }: { disabledModules = [ {} ]; };

  testScript = ''
  '';
})```

So surely the answer is don't use anonymous modules?

@bqv: Every module you access over the flake API (the attr nixosModules) is anonymous, as is every module you access over the NUR. To not use it anonymously, you have to utilize the underlying file structure, which defeats one main purpose of flakes, namely a consistent Nix API for different projects.
What do you mean by “manual building”?

Yes. Caring about file structure is not against the flake api imo, hence why flakes can be coerced to paths like any other derivation.
Manual building = the act of building the manual...

It's not against the flake api, but it circumvents it. It doesn't use the flake API, so it defeats the reason for using flakes. You can simply use any fixed-output derivation for fetching or declare a non-flake input to a flake, if you don't want to use a consistent api.
Why are you using Nix in the first place if you can use Linux From Scratch? What do you need Linux for if you can write your own kernel and directly access hardware? Because of abstraction. Imagine a flake whose file tree is littered with modules in 50 different places but exposing the standardized flake API. You have to look at every file to know if it's a module. You don't want to include every single one by path, do you?

You can't be serious...

I've been running into this and it is pretty frustrating. disabledModules becomes very hard to use with flakes. Not really sure how this could be solved though, I don't think it's possible to compare anonymous functions.

You can still override modules by path, but you must rely on the file system structure of the flakes. The store dir of an input flake foo is "${foo}".
The modules aren't necessarily anonymous functions. They can be attrsets, functions or functors (i.e. attrsets containing an attr __functor = self: f for some function f). Functions and functors are treated equally, but functors could carry metadata like a module key. One could e.g. derive the key from an attribute path of a module, but lib.evalModules would have to be adapted to make use of this information.

I think I bumped into this issue, is there a workaround?
Neither
disabledModules = [ "${modulesPath}/services/web-apps/restya-board.nix" ];

disabledModules = [ "services/web-apps/restya-board.nix" ];

seem to work, and there doesn't seem to be any examples or documentation on how to replace a module in a flaked configuration.
Any ideas?

filterModules does not convert all non-string elements. The cause is that since #49401 eval-config.nix passes modulesPath as a string, causing filterModules to always append modulesPath an extra time. You can fix it in your config by turning it back into a path like this.
{ config, pkgs, lib, modulesPath, ... }:

{
  imports = [
    "${modulesPath}/installer/sd-card/sd-image.nix"
  ];

  disabledModules = map (m: /. + "${modulesPath}/${m}") [
    "profiles/all-hardware.nix"
  ];
}

Still important to me as well. Had to reference a flake module by path to get my config to work.


Refactor hs_core > view > init.py

Refactor endpoint functions and supporting functions into separate python files, essentially cleaning out most of init.py
This represents years of tech debt and is inappropriate to undertake, prior to completing CZO work for My Communities preview;  this cleanup work will be attempted after the My Communities feature branch/preview is done.
Working around the pre-existing poor conditions is difficult, but represents the lesser evil, compared to taking risks and changing too much at once.

Consider 2-3 large sections: namely My Resources/Landing Page and Groups. CollaborateView Class can be moved into its own file.

Related to https://github.com/hydroshare/hydroshare/issues/3487

Covered by https://github.com/hydroshare/hydroshare/issues/3929 the person working 3929 should look at the larger picture and see that the file needs to be separated out and cleaned up.

Covered by https://github.com/hydroshare/hydroshare/issues/3929 the person working 3929 should look at the larger picture and see that the file needs to be separated out and cleaned up.


Migration to Gradle Version Catalog

How can I exclude micronaut-bom from mqtt-bom?

Don't use the boms- prefix to declare it in the catalog: this prefix is precisely here to tell "I want to import it in the BOM".

@donbeave Thanks!
@timyates can you review, update if necessary and get ready this PR to be released in the next minor.

Thanks again @donbeave
Switched to the imported micronaut catalog, and cleaned up some dependencies over here https://github.com/micronaut-projects/micronaut-mqtt/pull/183


Initial hardware scaler experiment

This is a first pass at an experiment to use the hardware scalers. It can resize images in BGRA/RGBA linear order.
The details of how the scaling arithmetic gets performed is not understood yet. Also, many other advanced features are not understood, such as

other input/output formats
histograms
color space conversion
chroma subsampling
"ASE"

This experiment uses the "main" block of registers with index 0 in the ADT. There exists a "APIODMA" block that appears to be able to program scaler settings based on a command list, but macOS does not use this, and it is not yet clear whether or not this functionality actually works.

Do we know what the scalers are actually intended for? when would they be used (on linux or macos) instead of scaling on the display controller or GPU? I guess maybe hardware video encoding?

XXX this is a random filter grabbed from a random trace I hope this can be deleted :sweat_smile:

re where the scalers are used: I am not sure, but I saw a small number of uses on boot as the desktop loaded. the hardware seems to generally back "IOSurfaceAccelerator"
re filter coefficients: this is some kind of impulse response function, but I am not sure exactly how the arithmetic is performed or what order the coefficients go in. once that is figured out, this can be replaced with a calculated sinc function or other antialiasing filter
unfortunately I will not be able to do any further testing on this for a while, since my laptop got damaged at May Contain Hardware FailureHackers


Can you provide the command to use neuralangelo on dtu?

Thank you for implementing neuralangelo so quickly.But you didn't give command how to use this new method.So I use the following command to test on the dtu dataset,but I get worse result on dtu24.I think there must be something wrong with my command.
ns-train neuralangelo --vis wandb --experiment-name neuralangelo-dtu-24 --data data/dtu/scan24 --pipeline.model.eval-num-rays-per-chunk 1024

Can you provide the command to use neuralangelo on dtu with mask?
Thanks!

Have you solved this?

@Ice-Tear Sorry for the late reply. The issue here is that the background model is missing and the surface is used to model to white table. I added back the background model. Please try again.
I use the following command
ns-train neuralangelo --vis wandb --experiment-name neuralangelo-dtu24-withbg  sdfstudio-data --data data/dtu/scan24 --load-dtu-highres True

Can you share the Neus dataset?

@niujinshuchong I'm so so sorry for the late reply.I update the code and use your command.It looks worked.Thanks!

Maybe I need to change some hyperparameters to make the model converge.


Alpha

It would be nice if SKAButton's alpha changed when pressing down.

Added colorBlendFactor for state, this will address this issue. There are also shortcuts I added to help make it styled more like a UIButton for quicker setup
Check out:
.setAdjustsSpriteOnHighlight()

and
.setAdjustsSpriteOnDisable()

Fixed in 1047cc5


Ability to use this adapter without a server

Chrome allows you to use its debugging protocol from a plugin without a server by writing an extension:
https://developer.chrome.com/extensions/debugger
It would be very nice to be able to do this using this adapter as well.

@bedney, can you clarify, do you mean, you'd like to be able to write an extension for IE that could work against IE using the protocol?

@danmosemsft - Thanks for the quick reply.
Yes. On Chrome, we leverage this capability by loading a Chrome extension into Chrome and speak the debugging protocol directly to a Chrome task with no server involved. The wireline protocol is the same, but you attach directly to the target. The API is detailed on that page I linked to above.

We don't have plans to extend this to IE extensions yet or enabling extensions of F12.
That being said we are keen for the F12 tools to have a HTML/JS extension model that is highly interoperable with Chrome. No plans yet though and we're going to wait for the Project Spartan extensibility model plans before plans for F12 can be made.

@andysterland - Thanks for the reply! I can't tell you how cool it is to see Microsoft people on GitHub, collaborating with their developer community! :-)
I understand the desire to wait and see how Spartan might change the extensibility model. If you guys could keep a capability like this in mind when that shakes out, that'd be great. Thanks!


Remove dependency on MongoDB Atlas

There are a few things that make Mongo Atlas tough to work with for new users.

You have to create an account and set up a database
If your IP address changes, you get this error: [0] MongooseServerSelectionError: Could not connect to any servers in your MongoDB Atlas cluster. One common reason is that you're trying to access the database from an IP that isn't whitelisted. Make sure your current IP address is on your Atlas cluster's IP whitelist: https://docs.atlas.mongodb.com/security-whitelist/ Which is not easily evident to solve though it can be fixed.
When working with the DB, you need to manage it in Atlas.

I suggest we use a locally hosted instance of mongo with docker-compose or use mongo in memory
Then we have a section in the docs on how to use Atlas if that is what you want. I just think Atlas adds friction for new users.
Thoughts?

Another idea here. What if we have a free instance of the DB that can be shared between all users to just get up and running and all data is deleted in that DB each day?

I meant to reply to this:
I'm agnostic. I find Atlas easiest to use, because I haven't really used Docker prior. And I like the GUI. (Side note, adding <IP_ADDRESS> to just allow public access is fine for test DBs, I usually do that for one-offs)
But, it makes sense to me that we would have some short sections or links out to "Getting started with MongoDB Atlas", "Docker", "Mongo in memory". All that's needed is a working/valid MONGO_URI
RE: the shared DB, I'm not sure how to guard against abuse, since that free DB would need to provision credentialed access.

Ok. Well I think the drawbacks of this is that you have to understand Atlas. This is the largest step for us for new developers that is not related to our code base.
I recommend we change the docs to show two ways of maintaining urls. One is with docker-compose since it takes very few steps and another is with Atlas.
Approved @seanspeaks ?

Sure, we might not even want to go into too much detail for either, just point to the docs for each?

Docs updated. Done.


The problem with RGB lamps

When the state of the RGB lamp changes from RGB color to WW / WC (warm and cool) the color temperature of the lamp. The changes are not visible on the plan, for this you need to refresh the browser page.
https://www.youtube.com/watch?v=X8KZ7-sdJO0

Yes you  are right I do not manage the temperature. I would classify it as a feature request. Are you ok ?

yes, please as a feature request.

Hello I've implemented a management of the temperature that I hope will be compatible with the majority of light devices. I've seen around that the it is somehow complex to take into account all temperature features. So far I'm managing the rgb mode and the color_temp mode as separate indipendent features. Please test release 0.9.17 and tell me if you are ok with the feature

Hello I've implemented a management of the temperature that I hope will be compatible with the majority of light devices. I've seen around that the it is somehow complex to take into account all temperature features. So far I'm managing the rgb mode and the color_temp mode as separate indipendent features. Please test release 0.9.17 and tell me if you are ok with the feature

The light is not updated dynamically, only after reloading the Chrome browser page.

Hello Vring0, please let me know if you have installed the latest version and tested with it. If you need to refresh the page in order to see the change in a light, it may also be due to HA not sending out the event of a state change to the card. I keep that I have some difficult to test all combination of light attributes change as I do not have all type of devices. Please post as much info as possible (console logs from the browser, errors in the core supervisor console, etc.)

I am using the latest version. When I switch the lights, I get this error all the time. In version 0.9.15 there were no problems with this.

Ok,  I can reproduce the bug. Something's still wrong with the temperature management

Can you please upgrade to the latest release v0.9.18 and verify if the bug is corrected ?

If you are not activating the shadow parameter (setting it to 'yes') the performances should not be better or worse than a few weeks ago. There is not a lot I can do to improve performance, the heavy lifting is done by a js module (three.js)  I have no control on (it is considered as one of the best open source project to render and animate 3D models. Of course if your model weighs 100Mb and you bind 100 entities, and you activate the shadows, etc. the performances will suffer....

I also have one last question about another problem. My walls are not transparent. But light passes through them. And some strange glare appeared on objects, even if the light was turned off.
Light passes through walls, example:

Glare of light, example:

Hello Vring0, since version 0.9.12, I  have introduced a Directional Light to complement the ambient light. Without Directional Light the scene was too dark and object details would not appear, also textures were not rendered. I did not find a way to use ambient light to make the scened better defined. I can put a parameter to switch off the directional light so  that you can see the difference.

Sorry I did not answer all your questions. Since versiobn 0.9.18 I have also introduced the shadow parameter.  This prevents the light beam to flood through walls. This makes the scene more realistinc, but it has quite a significant impact on the processing especially with your complex objects this might become quite heavy. Please test it (put shadow to 'yes") and let me know what you think.

ceiling lights stopped shining down

what is the object that is bound to the ceiling light ? If you have put the half sphere, it should project some light down, if not, light may be shaded by parts of the light objects itself. Shadow parameter is still a work in progress

For the test, I use all the objects of the luminaire. I will wait for a stable release. I can attach my model for testing.

Try to bind only the sphere object to the light (not the group of objects) and tell me what is the results. If you attach your model it can help me for the performance test.

I did that too. There is no light down.
my files: livingroom2.zip

I tried with the following code:
type: custom:floor3d-card
entities:
  - entity: light.gateway_light_7811dcb06bfe
    type3d: light
    object_id: Sphere_104_328
    light:
      lumens: '400'
object_groups:
  - object_group: ''
name: vring0
path: /local/test-vring0/livingroom2/
objfile: livingroom.obj
mtlfile: livingroom.mtl
shadow: 'yes'

With only one entity the model is loading fast enough 1.5 sec
this is the result with the light with shadow = 'yes' and using the sphere as object:

I have a problem with these lamps.

Unfortunately my calculation for the positioning of the light is not good for some lights objects as the light source falls inside the object and when you activate the shadow, the object is shadowing the light. If you  build those spotlights by yourself, you may try to do a cilinder open downtowards or with a transparent bottom. Also I suggest you give a look to my new plugin for Sweethome3D that makes the export easier (object_id will be more stable as they are based on object names). You can find it here: https://github.com/adizanni/ExportToHASS

Look at these models: https://www.polantis.com/ikea/hektar-suspension

Please write how to import into Sweet Home 3D?

You download the .obj format unzip it (with the .mtl file0 and you  right click on the futniture section of sweethome3d and do import furniture  -> choose model -> select the obj file and import it to the right Light section. Be careful that dimensio and orientation may be wrong, you need to adjust

I close this issue as it is longstanding and I all feeback are positive about the lights. In case some problem persist please open another issue


Error on Windows

Hi
I have an installation of python + mkl + pypardiso using conda-forge and I cant make pardiso to work on the example.
This is a log to reproduce the problem.
Any ideas???
Thanks
C:\Users\XXXXXXX>mamba create -n PT python=3.9 mkl numpy scipy pypardiso
Looking for: ['python=3.9', 'mkl', 'numpy', 'scipy', 'pypardiso']
conda-forge/noarch                                  85.0MB @   5.9MB/s 14.5s
conda-forge/win-64                                 153.4MB @   5.0MB/s 30.9s
Transaction
Prefix: C:\Users\XXXXXXX\AppData\Local\miniforge3\envs\PT
Updating specs:

python=3.9
mkl
numpy
scipy
pypardiso

Package                 Version  Build                  Channel           Size
Install:

python_abi                3.9  4_cp39                 conda-forge     Cached
ucrt             10.0.22621.0  h57928b3_0             conda-forge     Cached
ca-certificates      2024.2.2  h56e8100_0             conda-forge     Cached
intel-openmp         2024.0.0  h57928b3_49841         conda-forge     Cached
vc14_runtime      14.38.33130  h82b7239_18            conda-forge     Cached
vs2015_runtime    14.38.33130  hcb4865c_18            conda-forge     Cached
vc                       14.3  hcf57466_18            conda-forge     Cached
libiconv                 1.17  hcfcfb64_2             conda-forge     Cached
pthreads-win32          2.9.1  hfa6e2cd_3             conda-forge     Cached
tk                     8.6.13  h5226925_1             conda-forge     Cached
openssl                 3.2.1  hcfcfb64_0             conda-forge     Cached
libsqlite              3.45.1  hcfcfb64_0             conda-forge     Cached
libzlib                1.2.13  hcfcfb64_5             conda-forge     Cached
libffi                  3.4.2  h8ffe710_5             conda-forge     Cached
bzip2                   1.0.8  hcfcfb64_5             conda-forge     Cached
xz                      5.2.6  h8d14728_0             conda-forge     Cached
libxml2                2.12.5  hc3477c8_0             conda-forge     Cached
libhwloc                2.9.3  default_haede6df_1009  conda-forge     Cached
tbb                 2021.11.0  h91493d7_1             conda-forge     Cached
mkl                  2024.0.0  h66d3029_49658         conda-forge     Cached
tzdata                  2024a  h0c530f3_0             conda-forge     Cached
llvm-meta               5.0.0  0                      conda-forge     Cached
python                 3.9.18  h4de0772_1_cpython     conda-forge     Cached
openmp                  5.0.0  vc14_1                 conda-forge     Cached
libflang                5.0.0  h6538335_20180525      conda-forge     Cached
libopenblas            0.3.26  pthreads_hc140b1d_0    conda-forge     Cached
libblas                 3.9.0  21_win64_openblas      conda-forge     Cached
libcblas                3.9.0  21_win64_openblas      conda-forge     Cached
liblapack               3.9.0  21_win64_openblas      conda-forge     Cached
numpy                  1.26.4  py39hddb5d58_0         conda-forge     Cached
scipy                  1.12.0  py39hddb5d58_2         conda-forge     Cached
pypardiso               0.4.3  pyhd8ed1ab_0           conda-forge     Cached

Summary:
Install: 32 packages
Total download: 0 B

Confirm changes: [Y/n] Y
Downloading and Extracting Packages:
Preparing transaction: done
Verifying transaction: done
Executing transaction: done
To activate this environment, use
 $ mamba activate PT

To deactivate an active environment, use
 $ mamba deactivate

C:\Users\XXXXXXX>mamba activate PT
C:\Users\XXXXXXX>python
Python 3.9.18 | packaged by conda-forge | (main, Dec 23 2023, 16:29:04) [MSC v.1929 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.

import pypardiso
import numpy as np
import scipy.sparse as sp
A = sp.rand(10, 10, density=0.5, format='csr')
A
<10x10 sparse matrix of type '<class 'numpy.float64'>'
with 50 stored elements in Compressed Sparse Row format>
b = np.random.rand(10)
x = pypardiso.spsolve(A, b)
Traceback (most recent call last):
File "", line 1, in
File "C:\Users\XXXXXXX\AppData\Local\miniforge3\envs\PT\lib\site-packages\pypardiso\scipy_aliases.py", line 46, in spsolve
solver.factorize(A)
File "C:\Users\XXXXXXX\AppData\Local\miniforge3\envs\PT\lib\site-packages\pypardiso\pardiso_wrapper.py", line 164, in factorize
self._call_pardiso(A, b)
File "C:\Users\XXXXXXX\AppData\Local\miniforge3\envs\PT\lib\site-packages\pypardiso\pardiso_wrapper.py", line 277, in _call_pardiso
self._mkl_pardiso(self.pt.ctypes.data_as(ctypes.POINTER(self._pt_type[0])),  # pt
OSError: [WinError -1066598273] Windows Error 0xc06d007f

Long story short, I believe using MKL version 2023.2.0 or older should solve this problem while we are working in a patch release for the intel-openmp 2024.0.*

Thanks for the hint,
I'm going to try lowering the version of intel-openmp. So this problem also exists on others OS(Linux)?
Thanks for the help

Note that MKL 2024.* requires Intel-openmp 2024.* so you will need to lower the MKL version as well.
The issue happens only on Windows.

Exactly, mamba did the correct job of  keeping my env functional by lowering ihe intel-openmp and the mkl.
Thanks,

I have now also released pypardiso v0.4.4 on conda-forge, which pins MKL to <2024, see https://github.com/conda-forge/pypardiso-feedstock/pull/9


Closes: #232 fix a typo

Updated Firebase_Authentication_Using_Flask/templates/signup.html to fix small typo Changed atleast to at least
Description
A short summary of what is included in your Pull Request.
Fixes #(issue_no)

[ ] Issue_no: <insert your issue no here>
[ ] Not applicable

Type of change
Choosing one or more options from the following as per the nature of your Pull request.

[ ] New project insert
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Documentation Update

Project

Your Project Name:

Short Description: Provide a short desctiption of your Python project

Checklist:
Please tick all the boxes that are fulfilled by your Pull Request.

[x] I have named my files and folder, according to this project's guidelines.
[x] My code follows the style guidelines of this project.
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] I have created a helpful and easy to understand README.md, according to the given README_TEMPLATE.
[x] My changes do not produce any warnings.

This is actually my first ever pull request, so I hope I am doing it the right way, otherwise please let me know!. Thanks in advance!


Allow users to boot other ServiceProviders by adding them to composer…

[ ] Added or updated tests
[X] Documented user facing changes
[X] Updated CHANGELOG.md

Resolves https://github.com/nunomaduro/larastan/issues/831
Changes
Currently larastan supports registering Service Providers only from the first namespace you put in your composer.json autoload object. So if you define:
{
    ...
    "autoload": {
        "psr-4": {
            "A17\\EdgeFlush\\": "src",
            "A17\\EdgeFlush\\Database\\Factories\\": "database/factories"
        }
    },
    "autoload-dev": {
        "psr-4": {
            "Spatie\\ResponseCache\\": "vendor/spatie/laravel-responsecache/src"
        }
    },
    ...
}

It will only register Service Providers from the A17\EdgeFlush namespace. And if you define namespaces on your autoload-dev it will, by design, completely ignore them too. But while developing packages, we usually need all third party Service Providers, we are using, to be registered.
This PR changes it by booting those defined in composer.json. And, if it's running on a package it will also register Service Providers defined in autoload-dev. To enable it developers have to set the Composer type to "library".

Thank you for your PR!
I'm not sure autoload-dev is the right place to store Larastan-specific information.

It's a matter of semantics:

I'm developing (dev) a package for Laravel
I need Laravel to load (autoload) up more Service Providers
The piece of software responsible for registering namespaces and autoloading classes is Composer

Looks to me that Composer's autoload-dev object is the right place to configure them.
But, honestly, I just extended something larastan was already doing, it's just that it was ignoring all except the first namespace.

But, honestly, I just extended something larastan was already doing, it's just that it was ignoring all except the first namespace.

Larastan read the app's namespace.
This PR is putting foreign namespaces in autoload-dev.
This is not my project, I'm only a janitor! 🧹

larastan reads the first namespace, which may not be the app/package namespace. So if I people do
{
    "autoload": {
        "psr-4": {
            "Spatie\\ResponseCache\\": "vendor/spatie/laravel-responsecache/src",
            "A17\\EdgeFlush\\": "src"
        }
    },
}

It will not load the "app namespace". And, as told before, this change will probably really only impact package developers, which have usually other needs.

All I can think of is https://getcomposer.org/doc/04-schema.md#extra
I'm not strong enough to argue. Please wait for someone else.

This should be now fixed in a different way in the latest commits.


flake.lock: Update

NuschtSearch fails to build against the latest nixpkgs.

Thanks for the catch, it seems like a pnpm update resulted in a different hash.
Sadly the hash is therefore now broken with 24.05... @SuperSandro2000 Maybe pnpm should be backported upstream?

>  ERR_PNPM_NO_OFFLINE_TARBALL  A package is missing from the store but cannot download it in offline mode. The missing package may be downloaded from https://registry.npmjs.org/js-yaml/-/js-yaml-4.1.0.tgz.

Yeah, already saw that - it seems like pnpm is not the reason for the different hash. (Our demo instance uses an older version of nixpkgs which generates the old hash bus uses pnpm 9.12.1 too)

The cloudflare pages error is only because you created a fork and therefore don't get access the secrets in the CI.


feat: converting from point to array or tuple and vice versa

this improves and tests the conversions a bit. i replaced the impl Into with impl From (its preferable to implement From and use Into according to Rust docs)

oops i messed up the tuple test


soc2: add MI uptime checks docs

Current dependencies on/for this PR:

main

PR #3453   👈

This comment was auto-generated by Graphite.


no such file or directory: termnames.json

Upon executing TermOpen, I receive the error:
Error executing Lua callback: .../share/nvim/lazy/lazy.nvim/lua/lazy/core/handler/cmd.lua:32: Vim:Error executing Lua callback: ....local/share/nvim/lazy/plenary.nvim/lua/ple
nary/path.lua:738: ENOENT: no such file or directory: /home/zzz/.local/share/nvim/termnames.json

Using the following table to load plugin in lazy:
{
  "aaditeynair/termnames.nvim",
  cmd = {
	  "TermOpen",
	  "TermRename",
	  "TermClose",
  },
  dependencies = {
	  "nvim-lua/plenary.nvim",
	  "famiu/bufdelete.nvim",
  },
},

I still receive the same error.  Does that file need to be created?


WHOIS v1.21: Client doesn't support IP addresses (ERROR - invalid request)

Hi,
Your description isn't correct. The client doesn't support IP addresses.
Have tried the downloaded version 1.21:
$ .\whois.exe <IP_ADDRESS>

Whois v1.21 - Domain information lookup
Copyright (C) 2005-2019 Mark Russinovich
Sysinternals - www.sysinternals.com

Connecting to AT.whois-servers.net...

% Copyright (c)2020 by NIC.AT (1)
%
% Restricted rights.
%
% Except  for  agreed Internet  operational  purposes, no  part  of this
% information  may  be reproduced,  stored  in  a  retrieval  system, or
% transmitted, in  any  form  or by  any means,  electronic, mechanical,
% recording, or otherwise, without prior  permission of NIC.AT on behalf
% of itself and/or the copyright  holders.  Any use of this  material to
% target advertising  or similar activities is explicitly  forbidden and
% can be prosecuted.
%
% It is furthermore strictly forbidden to use the Whois-Database in such
% a  way  that  jeopardizes or  could jeopardize  the  stability  of the
% technical  systems of  NIC.AT  under any circumstances. In particular,
% this includes  any misuse  of the  Whois-Database and  any  use of the
% Whois-Database which disturbs its operation.
%
% Should the  user violate  these points,  NIC.AT reserves  the right to
% deactivate  the  Whois-Database   entirely  or  partly  for  the user.
% Moreover,  the  user  shall be  held liable  for  any  and all  damage
% arising from a violation of these points.

% ERROR - Invalid request

Connecting to )2020 by NIC.AT (1)                                       ...
Der angegebene Host ist unbekannt.

Same with the 64 Bit edition, also with admin privileges.
No issues with the same query on my other used OS'es (Linux, OpenBSD, FreeBSD).
Edit:
Also when using the following command structure:
$ .\whois.exe "<IP_ADDRESS>"

(Tested on Windows 10 Pro Version 1909 - Build 18363.535)

Okay, interesting...
I have captured the query with wireshark. The used IP address is from my ISP. Seems NIC.AT doesn't supports the following query (See screenshot):
62-46-172-92.ADSL.HIGHWAY.TELEKOM.AT\r\n

But it works with the Linux client with the follwoing formated query:
<IP_ADDRESS>\r\n

Anyway, could you please add support for this?


Handle unsigned integer constants greater than u32::MAX in codegen

We were not checking signed-ness and emitting the appropriate types.
Fixes #1040
r? @pepyakin

@bors-servo r+
Awesome!

:pushpin: Commit 0068c1a has been approved by pepyakin

:hourglass: Testing commit 0068c1a79dba1751955d7e732f50f1250a66ee72 with merge 8582a90ee76384df63876c879646da0c1555166b...

:sunny: Test successful - status-travis
Approved by: pepyakin
Pushing 8582a90ee76384df63876c879646da0c1555166b to master...


Add support to read JWKs from local file system

Description:
Need configurations to read JWKs resource from local file system.

This will be closed since there is no requirement for this.


feat: @plasmohq/messaging

Details
Code of Conduct

[x] I agree to follow this project's Code of Conduct
[x] I checked the current PR for duplication.

@louisgv Looking great so far. Are you looking to add typing to the input and output as well?

@louisgv Looking great so far. Are you looking to add typing to the input and output as well?

input and output body are both template for user to provide :d

Improvement:

For window relay, use: https://developer.mozilla.org/en-US/docs/Web/API/MessageChannel
For BGSW messaging, use port: https://developer.chrome.com/docs/extensions/reference/runtime/#type-Port


fix group

Description
Fix group reference error
Fixes # (issue)
Type of change
What is it?

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update
[ ] Refactor

Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I run make pre-commit to check fmt/vet/lint/test-no-fdo

Test results are available in Ibutsu. The test run IDs are:
b43b2b59-659c-4d35-83ce-6b9804173e32


Mark CGo client as deprecated in the documentation

Fixes #14609
Motivation
The CGo client has been deprecated since version 2.7.0, but documentation for it is still there.
Modifications
Stop referring to the documentation for the CGo client internally and state that it has been deprecated.
Verifying this change

[x] Make sure that the change passes the CI checks.

This change is a trivial rework / code cleanup without any test coverage.
Documentation

[x] doc

@Anonymitaet - done, thanks! Added a banner in the CGo client docs saying it has been deprecated.

@Anonymitaet - done, thanks! Added a banner in the CGo client docs saying it has been deprecated.

Great reminder!


[Feature Request] Make Text::Variable work in Chinese

Like now we should use English to make Text::Variable work correctly, but dataview hasn't recognized ChineseText::Variable yet. Is it possible to add the support for Chinese, like 文本::Variable?

Agree, as a Chinese user, this feature is very much needed!
Sincerely thank the author for developing such a great plug-in!

Pull request #207 makes the regexes for finding inline fields respect unicode, which should fix this issue. Will come as part of the next release.

This also helps with German umlauts. I noticed it here and then was able to work around the problem with synomyms. So it's not a purely Chinese problem. ;)

Yeah, it doesn't work for anything other than good old latin A-Z ;). I believe it should work better in this release (0.3.6).

Does this work better for your use-cases?

@blacksmithgu yep, close issue.


ClientRequestProperties transfer parameters by JDK 11 issue

Describe the bug
After execute kql with parameters by client request properties, there is an exception for "com/fasterxml/jackson/core/StreamReadConstraints."
The reason is the current ClientImpl only support Java 8,event the lastest verion(5.0.2).
Expected behavior
upgrade the JDK version to 11.
Screenshots
The issue happend is below:

Desktop (please complete the following information):

OS: [e.g. iOS]
Version [e.g. 22]

Additional context
Cause the HashMap created by Jdk 11, but need to decode by JDK 8.

Hi @zujiaju,
This sounds like a conflict between dependency versions in your environment vs the dependency versions we support. We've tested this with Jackson v2.14.2.

What version of Jackson is maven actually resolving in your project? (try mvn dependency:tree from your project's root)
Have you tried using common ways to ensure your project actually uses Jackson v2.14.1, like mvn exclude, https://maven.apache.org/plugins/maven-shade-plugin/ or https://plugins.jetbrains.com/plugin/7179-maven-helper ?

Add exception message from snapshot: Method threw 'java.lang.NoClassDefFoundError' exception. Cannot evaluate com.microsoft.azure.kusto.data.ClientRequestProperties.toString()

If you are using a newer Jackson version like I am, I have a PR out to upgrade to 2.15.2 but it still needs formatting in order for the build to succeed.

PR #333 fixes this, We'll get out a new version soon

@zujiaju was this issue resolved for you with the Jackson upgrade?

Closing for now, @zujiaju feel free to respond and re-open.


[FLINK-24474] Default rest.bind-address to localhost in flink-conf.yaml

What is the purpose of the change
The purpose of this change is to configure Flink, by default, to bind the web/REST endpoint to localhost rather than an externally facing network interface, for security reasons.
Brief change log

Bound the rest.bind-address in flink-conf.yaml to localhost

Verifying this change
This change is a trivial rework
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

I merged the docker PR; so you could rebase it now. Maybe wait until the azure e2e issues have been resolved though.

@dmvk Thanks! I've removed it, squashed the commits and force pushed up.

@flinkbot run azure

At present, I try to set rest.bind-address to <IP_ADDRESS> on Flink 1.15 and above, and find that external access is not effective. However, the settings are valid in versions below 1.15