donation: CLA/DCO + retroactive approval from past contributors

discussions about the potential process to get a CLA/DCO and how to do that IF we decide to donate the repo to CNCF (#584).
a bit unknown on the actual process yet without speaking to CNCF. l will update this issue as we know more.
One project that relicensed through github issue checkmarks: https://github.com/gfx-rs/wgpu/issues/1473
Wonder if that approach would be sufficient? People can delete issue comments.
CNCF individual CLA certainly seems like it has more clauses than to just allow re-licensing.
The https://github.com/cla-assistant/cla-assistant from Sönke's comment below seems the most promising.

The easiest way might be to activate a cla assistant on the repo (for example [1]) - this usually generates a link which you could post under this issue, tag all contributors and ask them to sign the CLA.
That would hopefully gather a sizeable initial batch (I hesitate to guess a percentage here).
Give that a week or two and then we can get to work on trying to contact the missing people directly and talking to them.
The number of contributors is not extremely large, so hopefully that should get us across the line or at least very close to it ..
[1] https://github.com/cla-assistant/cla-assistant

I see the CLA-Assistant is actually used by Deislabs. Setup is easy, 2 clicks to authorise with github (read perms on user), then accept with name (might have to fill in if missing in user details) as a user/corp.
(I also see that helm started out with the CNCF CLA but moved on to a DCO (because apparently not needed after handover) - maybe something to keep in mind)
Presumably, the most important aspects of the CLA is that we retroactively get rights as required by the CNCF CLA;

(2,3) grant of copyright license + patent license for all past contributions
(4,5) verification that contributors were legally entitled to grant these licenses, and made by them (but with indemnification for them in clause 6)

The last clause (7; method to submit on behalf of 3rd party) is probably not needed unless someone says so in the big issue. But I guess we can include it in the document.
I think we can take these important bits from CNCF's CLAs, swap out the definitions of "The Foundation" for kube-rs owners and point ownership to us. That way, we still have something out of this after all this is done if kubernetes end up being less cooperative than we thought (in which case we will consider using this new organisation as a home instead)
Interestingly, CLA-Assistant seems to have a drop-down for corp/invididual (at least for Deislabs), whereas CNCF has two documents, so not sure if this is easy to reconcile (haven't checked fully yet). But this is probably at the point where I have to ask them.
I don't know if you have any experience with these particular aspects @soenkeliebau? Does this seem like a sensible course of action to you?

I don't think CLA assistant supports serving different versions of the CLA for individuals and legal entities tbh. We tried solving this by defining "you" based on the selection in the dropdown you mentioned in our CLA [1].
That dropdown is something that can be freely defined when setting up the CLA assistant and also used to gather additional information besides that.
For our case, I think so far we have only gathered individual CLAs via the assistant, all corporate CLAs have been discussed and signed via mail and not the assistant.
Regarding your questions about the content of the CLA while ianal that sounds sensible to me, however my suggestion would be to discuss this with the relevant people up front who need to accept the donation to ensure you don't have to gather consent twice :)
I believe @brendandburns mentioned this in a comment as well, maybe he can put you in contact with the right people?
[1] https://gist.github.com/eff20055a7b40e1a9932e0b4cbd62f78
[2] https://github.com/cla-assistant/cla-assistant#request-more-information-from-the-cla-signer

In the interest of not delaying this any further. I am planning on adding this early next week with CLA-Assistant using CNCF's individual CLA, but with the following non-legal modifications:

removal of mail form starting at paragraph 2, and ending at the E-Mail: _____ line. Because we only let people sign electronically via CLA-assistant. Stackable does a similar modification (although they make other modifications and elaborate that you are electronically signing). Regardless, this is in the header of the document.
replace CNCF with kube-rs Only used in the header
replace The Cloud Native Computing Foundation (the "Foundation") with The kube-rs organisation (the "Organisation")
replace The Foundation with The Organisation everywhere.

(really feels like github ought to standardise something like this in the future, so that people can just read a name like "CNCF CLA")

Full Planned CLA

Thank you for your interest in the kube-rs project (“kube-rs”) of The kube-rs organisation (the "Organisation"). In order to clarify the intellectual property license granted with Contributions from any person or entity, the Organisation must have a Contributor License Agreement ("CLA") on file that has been signed by each Contributor, indicating agreement to the license terms below. This license is for your protection as a Contributor as well as the protection of kube-rs, the Organisation and its users; it does not change your rights to use your own Contributions for any other purpose.
You accept and agree to the following terms and conditions for Your present and future Contributions submitted to the Organisation. In return, the Organisation shall not use Your Contributions in a way that is contrary to the public benefit or inconsistent with its nonprofit status and bylaws in effect at the time of the Contribution. Except for the license granted herein to the Organisation and recipients of software distributed by the Organisation, You reserve all right, title, and interest in and to Your Contributions.

Definitions.

"You" (or "Your") shall mean the copyright owner or legal entity authorized by the copyright owner that is making this Agreement with the Organisation. For legal entities, the entity making a Contribution and all other entities that control, are controlled by, or are under common control with that entity are considered to be a single Contributor. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
"Contribution" shall mean any original work of authorship, including any modifications or additions to an existing work, that is intentionally submitted by You to the Organisation for inclusion in, or documentation of, any of the products owned or managed by the Organisation (the "Work"). For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Organisation or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Organisation for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by You as "Not a Contribution."

Grant of Copyright License. Subject to the terms and conditions of this Agreement, You hereby grant to the Organisation and to recipients of software distributed by the Organisation a perpetual, worldwide, nonexclusive, nocharge, royaltyfree, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Your Contributions and such derivative works.

Grant of Patent License. Subject to the terms and conditions of this Agreement, You hereby grant to the Organisation and to recipients of software distributed by the Organisation a perpetual, worldwide, nonexclusive, nocharge, royaltyfree, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by You that are necessarily infringed by Your Contribution(s) alone or by combination of Your Contribution(s) with the Work to which such Contribution(s) was submitted. If any entity institutes patent litigation against You or any other entity (including a crossclaim or counterclaim in a lawsuit) alleging that your Contribution, or the Work to which you have contributed, constitutes direct or contributory patent infringement, then any patent licenses granted to that entity under this Agreement for that Contribution or Work shall terminate as of the date such litigation is filed.

You represent that you are legally entitled to grant the above license. If your employer(s) has rights to intellectual property that you create that includes your Contributions, you represent that you have received permission to make Contributions on behalf of that employer, that your employer has waived such rights for your Contributions to the Organisation, or that your employer has executed a separate Corporate CLA with the Organisation.

You represent that each of Your Contributions is Your original creation (see section 7 for submissions on behalf of others). You represent that Your Contribution submissions include complete details of any thirdparty license or other restriction (including, but not limited to, related patents and trademarks) of which you are personally aware and which are associated with any part of Your Contributions.

You are not expected to provide support for Your Contributions, except to the extent You desire to provide support. You may provide support for free, for a fee, or not at all. Unless required by applicable law or agreed to in writing, You provide Your Contributions on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NONINFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE.

Should You wish to submit work that is not Your original creation, You may submit it to the Organisation separately from any Contribution, identifying the complete details of its source and of any license or other restriction (including, but not limited to, related patents, trademarks, and license agreements) of which you are personally aware, and conspicuously marking the work as "Submitted on behalf of a thirdparty: [named here]".

You agree to notify the Organisation of any facts or circumstances of which you become aware that would make these representations inaccurate in any respect.

and

Markdown diff with CNCF CLA
diff --git cla-individual.md cla-individual.md
index 8f00ff8..005e5af 100644
--- cla-individual.md
+++ cla-individual.md
@@ -1,23 +1,23 @@
-Thank you for your interest in the Cloud Native Computing Foundation project (“CNCF”) of The Linux Foundation (the "Foundation"). In order to clarify the intellectual property license granted with Contributions from any person or entity, the Foundation must have a Contributor License Agreement ("CLA") on file that has been signed by each Contributor, indicating agreement to the license terms below. This license is for your protection as a Contributor as well as the protection of CNCF, the Foundation and its users; it does not change your rights to use your own Contributions for any other purpose.
+Thank you for your interest in the kube-rs project (“kube-rs”) of The kube-rs organisation (the "Organisation"). In order to clarify the intellectual property license granted with Contributions from any person or entity, the Organisation must have a Contributor License Agreement ("CLA") on file that has been signed by each Contributor, indicating agreement to the license terms below. This license is for your protection as a Contributor as well as the protection of kube-rs, the Organisation and its users; it does not change your rights to use your own Contributions for any other purpose.

-You accept and agree to the following terms and conditions for Your present and future Contributions submitted to the Foundation. In return, the Foundation shall not use Your Contributions in a way that is contrary to the public benefit or inconsistent with its nonprofit status and bylaws in effect at the time of the Contribution. Except for the license granted herein to the Foundation and recipients of software distributed by the Foundation, You reserve all right, title, and interest in and to Your Contributions.
+You accept and agree to the following terms and conditions for Your present and future Contributions submitted to the Organisation. In return, the Organisation shall not use Your Contributions in a way that is contrary to the public benefit or inconsistent with its nonprofit status and bylaws in effect at the time of the Contribution. Except for the license granted herein to the Organisation and recipients of software distributed by the Organisation, You reserve all right, title, and interest in and to Your Contributions.

 1. Definitions.

-"You" (or "Your") shall mean the copyright owner or legal entity authorized by the copyright owner that is making this Agreement with the Foundation. For legal entities, the entity making a Contribution and all other entities that control, are controlled by, or are under common control with that entity are considered to be a single Contributor. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
+"You" (or "Your") shall mean the copyright owner or legal entity authorized by the copyright owner that is making this Agreement with the Organisation. For legal entities, the entity making a Contribution and all other entities that control, are controlled by, or are under common control with that entity are considered to be a single Contributor. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.

-"Contribution" shall mean any original work of authorship, including any modifications or additions to an existing work, that is intentionally submitted by You to the Foundation for inclusion in, or documentation of, any of the products owned or managed by the Foundation (the "Work"). For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Foundation or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Foundation for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by You as "Not a Contribution."
+"Contribution" shall mean any original work of authorship, including any modifications or additions to an existing work, that is intentionally submitted by You to the Organisation for inclusion in, or documentation of, any of the products owned or managed by the Organisation (the "Work"). For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Organisation or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Organisation for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by You as "Not a Contribution."

-2. Grant of Copyright License. Subject to the terms and conditions of this Agreement, You hereby grant to the Foundation and to recipients of software distributed by the Foundation a perpetual, worldwide, nonexclusive, nocharge, royaltyfree, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Your Contributions and such derivative works.
+2. Grant of Copyright License. Subject to the terms and conditions of this Agreement, You hereby grant to the Organisation and to recipients of software distributed by the Organisation a perpetual, worldwide, nonexclusive, nocharge, royaltyfree, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Your Contributions and such derivative works.

-3. Grant of Patent License. Subject to the terms and conditions of this Agreement, You hereby grant to the Foundation and to recipients of software distributed by the Foundation a perpetual, worldwide, nonexclusive, nocharge, royaltyfree, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by You that are necessarily infringed by Your Contribution(s) alone or by combination of Your Contribution(s) with the Work to which such Contribution(s) was submitted. If any entity institutes patent litigation against You or any other entity (including a crossclaim or counterclaim in a lawsuit) alleging that your Contribution, or the Work to which you have contributed, constitutes direct or contributory patent infringement, then any patent licenses granted to that entity under this Agreement for that Contribution or Work shall terminate as of the date such litigation is filed.
+3. Grant of Patent License. Subject to the terms and conditions of this Agreement, You hereby grant to the Organisation and to recipients of software distributed by the Organisation a perpetual, worldwide, nonexclusive, nocharge, royaltyfree, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by You that are necessarily infringed by Your Contribution(s) alone or by combination of Your Contribution(s) with the Work to which such Contribution(s) was submitted. If any entity institutes patent litigation against You or any other entity (including a crossclaim or counterclaim in a lawsuit) alleging that your Contribution, or the Work to which you have contributed, constitutes direct or contributory patent infringement, then any patent licenses granted to that entity under this Agreement for that Contribution or Work shall terminate as of the date such litigation is filed.

-4. You represent that you are legally entitled to grant the above license. If your employer(s) has rights to intellectual property that you create that includes your Contributions, you represent that you have received permission to make Contributions on behalf of that employer, that your employer has waived such rights for your Contributions to the Foundation, or that your employer has executed a separate Corporate CLA with the Foundation.
+4. You represent that you are legally entitled to grant the above license. If your employer(s) has rights to intellectual property that you create that includes your Contributions, you represent that you have received permission to make Contributions on behalf of that employer, that your employer has waived such rights for your Contributions to the Organisation, or that your employer has executed a separate Corporate CLA with the Organisation.

 5. You represent that each of Your Contributions is Your original creation (see section 7 for submissions on behalf of others). You represent that Your Contribution submissions include complete details of any thirdparty license or other restriction (including, but not limited to, related patents and trademarks) of which you are personally aware and which are associated with any part of Your Contributions.

 6. You are not expected to provide support for Your Contributions, except to the extent You desire to provide support. You may provide support for free, for a fee, or not at all. Unless required by applicable law or agreed to in writing, You provide Your Contributions on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NONINFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE.

-7. Should You wish to submit work that is not Your original creation, You may submit it to the Foundation separately from any Contribution, identifying the complete details of its source and of any license or other restriction (including, but not limited to, related patents, trademarks, and license agreements) of which you are personally aware, and conspicuously marking the work as "Submitted on behalf of a thirdparty: [named here]".
+7. Should You wish to submit work that is not Your original creation, You may submit it to the Organisation separately from any Contribution, identifying the complete details of its source and of any license or other restriction (including, but not limited to, related patents, trademarks, and license agreements) of which you are personally aware, and conspicuously marking the work as "Submitted on behalf of a thirdparty: [named here]".

-8. You agree to notify the Foundation of any facts or circumstances of which you become aware that would make these representations inaccurate in any respect.
+8. You agree to notify the Organisation of any facts or circumstances of which you become aware that would make these representations inaccurate in any respect.

Although might also need to make a similar change to @soenkeliebau 's suggestion on the CLA-assistant to define "You" based on a dropdown selection. Might have to try it out on a test project first.

CLA gist here: https://gist.github.com/clux/a4e349e729af96faff044c753edbbdb7

Converted text to have markdown headers like stackable's one and used their metadata.
Listed CNCF CLA clause 4,5 and 7 under a ## 4. Representations header (didn't know what else to summarise them as, and stackable rewrites those bits).

One thing I'm a bit worried about is that kube-rs is not a legal person (natural person, corporation, non-profit, and so on). It might be easier if it's addressed to you (@clux) personally instead?

Yeah, that's a fair point. It looks legally easier to pin it on me temporarily, although the legalese feels pretty heavy handed with that template though :D

Thank you for your interest in the kube-rs project (“kube-rs”) by Eirik clux Albrigtsen (the "Owner").

Updated with me as the legal pin. Also removed the corresponding guarantee that I will "adhere to non-profit bylaws at the time of the contribution" because it doesn't make sense for an individual. Left the "good faith" sentence though:

in return, the Owner shall not use Your Contributions in a way that is contrary to the public benefit

In an unexpected turn of events, we can probably drop our CLA idea for a simple DCO based on CNCF Chris's comments (plus a few comments above) because we use Apache2 out of the box. (A DCO is still necessary)
The guidelines in the official doucment on CNCF are a lot more lightweight:

no copyright headers anywhere, just a generic Copyright The Kube-rs Authors (i need to typo fix that from the license file)
original authors keep their copyrights

AFAIKT the only thing we lose out on is the ability to relicense our code, and if i never have to deal with the legal aspect again, then i'm good :-)
PLAN:

write a contributors guide
install the DCO app in the org
write a file for CERTIFICATE_OF_ORIGIN (if it is required with the DCO app)
update LICENSE line with authors to match req and set the year correctly to 2018 (when we actually started)


Add streamlit demo

Description

Add a streamlit demo to show spacy-llm with OpenAI for NER and Textcat.
Types of change

enhancement to usage examples
Checklist

[x] I confirm that I have the right to submit this contribution under the project's MIT license.
[x] I ran the tests (including the external tests), and all new and existing tests passed.
[x] My changes don't require a change to the documentation, or if they do, I've added all required information.

Note: the tests are failing because sharing env secrets with forks doesn't work (without compromising security to some degree). If you set an OPENAI_API_KEY env secret in your fork repo, this should be fixed.

Note: the tests are failing because sharing env secrets with forks doesn't work (without compromising security to some degree). If you set an OPENAI_API_KEY env secret in your fork repo, this should be fixed.

Setting the env secret didn't seem to work, is there another way?

I think we just agree to ignore the CI here for now because it's not doing anything useful? (Otherwise one possibility is to recreate the PR with a branch in the main repo.)

To go along with v0.2.0 I think it might be nice if this uses the v2 tasks so we can point to it as a demo for the updated prompts right away?

And I think it would make sense to move the prompt to the main column because it's too hard to read in the sidebar. Maybe below the visualization?

Should I add the REL and Spancat tasks added in v0.2.0 as well? Or do we just want to keep it with NER and Textcat for now?

Should I add the REL and Spancat tasks added in v0.2.0 as well? Or do we just want to keep it with NER and Textcat for now?

If it's quick to add them, yes. Otherwise I'd say let's prioritize getting this PR done (we can still open a follow-up PR with more tasks).

All the feedback has been addressed, so unless there's anything more, I think it makes sense to merge this one and make updates as needed.


battery consumtion

general question here!
Is the approach using emulation sound card by software? Does it increase battery consumption?
I use similar commercial app called Boom 3d, and I see it's 10% cpu usage all the time, and activity monitor says "energy impact" is 10

I will always focus on making eqMac a low CPU consuming application. I think Boom3D spend too much power on drawing overly nice UI's and doing some audio analysis in the background.

https://github.com/nodeful/eqMac2/issues/164

Hey everyone. Excuse me for the lack of updates. I have been really busy on the new version of eqMac. I am happy to announce an open beta release.
You can download it here: https://eqmac.app
There are a lot of known bugs that I could not fix just yet:

Driver not installing from the first try. Sometimes need to restart eqMac a couple times.
Complex Device switching logic is not perfect (for example when switching off the device that's currently playing, plugging in new device etc.)
UI takes long to load (a lot can be done to improve that)
UI dimensions are not synching properly
There's a noticeable audio delay in the playback, so not suitable for video yet (I know where the problem lies just haven't had the time to fix yet)
Sometimes the playback doesn't start, in that case please try to switch the output to the device you want and eqMac should try and build the audio pipeline again.

So as you can see there's still some work to be done but at least it's a completely modern tech stack that I am fully willing to work on: 100% Swift, User Space driver and a Web UI, instead of C++, Kernel Drivers. As I said, should work on Catalina and should not have any pesky ear drum blasting volume bugs (at least I didn't come across any).
I'm open to feedback and issue reports here: https://github.com/bitgapp/eqmac
That repo will become the main repo for eqMac and this repo will be archived eventually.
And yes it's called just eqMac, not eqMac3 :) And it will stay that way forever.

Hey everyone 👋
I will be open sourcing the new version of eqMac, therefore, I am closing this issue and repository as I will be transfering nodeful/eqMac2 repo to bitgapp/eqMac
Please bear with me for the next couple of days as I setup that new repo. The eqMac2 code will be living in the old-eqMac2 branch if anyone is interested in referencing it for whatever reason.
Please try out the new version and report bugs to the new repo.
Thanks for using eqMac.

Moving this discussion to #229


Identify FlashLoan from DyDx

Defi-Crawler does not seems to identify flashloan uses from DyDx.
I was looking at this paper only focusing on Aave, because defi-crawler support only this:
https://python.plainenglish.io/flashloan-stats-on-aave-for-2021-e827dd232052
From the paper that extended to DyDx:
Towards A First Step to Understand Flash Loan and Its Applications in DeFi Ecosystem https://arxiv.org/pdf/2010.12252.pdf

I was taking a look at the DyDx subgraph and didn't find a way to locate flashloans. Will try to do talking with the team. If you have a valid query, I'll add it to the library.


e2e test: reimplement with K8s testing framework

Also add a test for the QAT device plugin in kernel mode.
Contributes to #253

Codecov Report

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

@@           Coverage Diff           @@
##           master     #271   +/-   ##
=======================================
  Coverage   70.14%   70.14%
=======================================
  Files          17       17
  Lines        1735     1735
=======================================
  Hits         1217     1217
  Misses        478      478
  Partials       40       40

Continue to review full report at Codecov.

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

rebased on top of #288

resolved merge conflict;
rebased.

@askervin ping. The test is green finally.

lgtm


[WIP] Improve pylint score

Context for changes
Bringing pylint CodeQuality score to A/- levels by refactoring the codebase.
Example usage and tests
< Add some example usage and tests showing how to utilize new features and fixes; otherwise, mark N/A below. >

[ ] Not Applicable

Performance results justifying changes
< If you have improved a feature you should support it with some benchmarking and scaling results, plots, etc.; otherwise, mark N/A below. >

[ ] Not Applicable

Workflow actions and tests
< In most cases, we need a set of unit tests that automatically and comprehensively test for newly added features. Discuss existing CI tests that cover the changes or any updates to the workflow here; otherwise, mark N/A below. >

[ ] Not Applicable

Expected benefits and drawbacks
< Summarize your justifications for the change and its benefits. Is there any drawback that exists today with the changes or may occur in the future? You cannot place N/A here. >
Expected benefits:

text goes here

Possible drawbacks:

text goes here

Related Github issues
< Explicitly, link any corresponding issue and update the status of the relevant GitHub issue here; otherwise, mark N/A below. >

[ ] Not Applicable

Checklist and integration statements

[ ] My Python and C++ codes follow the coding and commenting styles of this project as indicated by existing files. Specifically, the changes conform to given black, docformatter and pylint configurations.
[ ] I have performed a self-review of these changes. I have checked my code and corrected misspellings to the best of my capacity. I have checked the CodeFactor score in the active branch and ensured it is B- or higher. I also confirm that I have already merged other branches into this branch as required.
[ ] I have added context for corresponding changes in documentation and README.md as needed.
[ ] I have added new workflow CI tests for corresponding changes and these pass locally for me.
[ ] I have updated _version.py based on semantic versioning. I recognize that the developers may create a Special Release including my changes.

Similar work is being carried out on PR #11. It'd be good to merge this PR to that branch and keep the work under a single PR.


card-game-war solved

Most of the time it never ends...

I haven't solved it yet, but I was wondering about that, because it does seem the game has potential to run for a long time, and I suspect it can even be looping forever...


[SPARK-42826][PS][DOCS] Add migration notes for update to supported pandas version.

What changes were proposed in this pull request?
This PR proposes to add a migration note for update to supported pandas version.
Why are the changes needed?
Some APIs have been deprecated or removed from SPARK-42593 to follow pandas 2.0.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manual review is required.

Merged to master and branch-3.4.


Create a tree widget

We need tree widgets that:

[x] propagate selection
[x] offer columns
[x] are lazy

Two small issues:
[ ] the tree should not take the first level into account when indenting
[ ] the row padding should be the same as in the list


error[E0609]: no field data on type Cow<'_, [u8]>

Hey, I got below error, any idea about this issue
error[E0609]: no field data on type Cow<'_, [u8]>
--> src\main.rs:23:25
|
23 |           .body(content.data.into_owned()),

Have you tried any of the examples,
https://github.com/pyrossh/rust-embed/blob/master/examples/basic.rs


Exclude private IP addresses

When running bbrf domains --view resolved it includes subdomains which resolve to private IP space. This can be undesirable when working with third party tools because running httpx, etc. on these subdomains is pointless (assuming you have fresh DNS records and you're not working with stale data) and wastes a lot of time and resources.
Additionally we can have false positives. If foo.example.com points to <IP_ADDRESS>, bbrf domains --view resolved | httpx will show foo.example.com as alive, but that's our own couchdb server. A simple --exclude-private flag would help greatly for times where working with truly internal subdomains doesn't make sense.

Hi @nmalcolm - I agree that this would be a nice feature to have. I have been facing similar use cases while using bbrf.
This can probably be achieved by building an additional server view (e.g. domains_resolved_exclude_private in CouchDB with something like:
function (doc) {
  if(doc.type == "domain" && doc.ips.length > 0)
    for(ip in doc.ips)
        if(isPrivateIP(ip)) return;
    emit(doc.program, doc._id);
}

The alternative approach would be to write a filter function on the bbrf-client, which would put the load on the client and therefore probably be less interesting. I'm looking into these options.

Some initial tests on my local installation seem to point to this working:
function (doc) {
  if(doc.type == "domain" && doc.ips.length > 0) {
    for(ip in doc.ips) {
      var i = doc.ips[ip].split(".");
      if(i[0] != "10" && !(i[0] == "192" && i[1] == "168") && !(i[0] === '172' && (parseInt(i[1], 10) >= 16 && i(parts[1], 10) <= 31)) )
         emit(doc.program, doc._id);
    }
  }
}

I will write some tests and add a flag --no-private in the next push of the client.


test-reporter milestone v2

The goal of the v2 reporter is to move to NodeJS 20, upgrade all dependency packages and to support the v4 artifacts.

[ ] #363

Hello! Any update on this?


How to preview word .docx files

I'm trying Files as a replacement for WinExplorer but cannot figure out how to preview Word files.

Not supported. Merging with #4041.


Add Activity TCN classifier node and support

@cameron-a-johnson @hdefazio This is the branch that adds the load/norm/predict functions and ROS node for the TCN activity classifier. PTAL.

Working on resolving the conflict. Since it has to do with the environment, I'm making sure poetry can resolve successfully and re-lock this branch's additions

Also quickly addressed the missing Python dependency and CI config issue that was causing the pytests to fail to collect and run.

I approve this merge btw! Upon successful CI runs let's merge this branch


Update ebus to 3.3.4

Please update my adapter ioBroker.ebus to version 3.3.4.
This pull request was created by https://www.iobroker.dev c0726ff.

RE-CHECK!


Adding a better sample with ES6 on README.MD

At the first time I saw the sample on REAME.MD, I got a little confused about the React.createClass  syntax, so I added a simple sample for better using with ES6 (using extends React.Component instead).

We intentionally use createClass, as it is simpler and doesn't require a transpiler to run the code.


Allow crate to attach uniform initialization behavior to every #[test]

Back when support for logging macros like debug! and what not was more heavily baked into the language and stdlib, I think we were able to see output from such logging macros from the #[test] unit tests.
But now, one cannot, at least not without adding explicit code to initialize the logging subsystem to every unit tests.
See also this StackOverflow Q here: http://stackoverflow.com/questions/30177845/how-to-initialize-the-logger-for-integration-tests
It is a shame that we offer both of these features (integrated unit tests and a logging subsystem), and yet they do not compose as seamlessly as one might hope.

(as a quick counterpoint: this is relatively low priority, since when one is debugging the behavior on a particular test, it is usually a very small cost to add the single line of env_logger initialization code to that test and recompile.  That is, usually tests are cheap to recompile. the exception is when the tests are embedded as unit tests inline within the source code file, because then that usually implies recompiling the whole original source crate, at least for the time being, though presumably incremental compilation will eventually make that "free" too.)

People ask all the time for setup and teardown facilities in the test harness. You can hack it in with a macro but it's not the best and doesn't work for doctests as you said.

In https://github.com/servo/servo/pull/21884 I’ve exploited a loophole in how rustc --test interacts with Cargo in order to override main and run some initialization code before running the test harness. It’d be nice to have a supported way to do this.
I’m aware of https://github.com/rust-lang/rust/issues/50297, but besides it not being implemented I’d prefer to have to write an entire test harness. I like #[test].
CC @rust-lang/libs

This issue’s title says “to every #[test]”, but the issue description suggests something that only runs once per process in order to e.g. initialize static items. The latter is what I’ve implemented for Servo.

This issue’s title says “to every #[test]”, but the issue description suggests something that only runs once per process in order to e.g. initialize static items. The latter is what I’ve implemented for Servo.

Really, the two are related but not identical problems. For my use case, I actually need both.

Code running before all tests (that is, prior to any test running, once), to ensure the environment is correctly set up. No tests should run if the database is unavailable.
Code running after each test, each time, to clean up the database in case of failure.
Code running after all tests are finished to nuke the test database completely.

after each test

(You’re probably aware of this, but in that case you might need to force tests to run on a single thread as that’s not the default. Otherwise a test test might still be running at the time another finishes.)

after each test

(You’re probably aware of this, but in that case you might need to force tests to run on a single thread as that’s not the default. Otherwise a test test might still be running at the time another finishes.)

Yes, that's necessary but unfortunately insufficient.
My current solution is build the test environment, get the data I want to check, perform cleanup, and then assert! my conditions.

@SimonSapin nowadays I think it's also a viable option to have something like:
#[my_test_macro]
fn my_test(with: &MyArgs, and: &GlobalResourceInitializedOnce) {
    // ...
}

Would that work for Servo?

This is still an issue. I agree with what @alexcrichton suggested but slightly different use might be better.
#[my_test_macro]
fn my_test(with: &MyArgs, and: &Box<dyn BeforeAndAfterAll>) {
    // ...
}

Where multiple traits make sense like BeforeAndAfterEach etc. so a trait method might be used later for scheduling the callbacks.

This issue’s title says “to every #[test]”, but the issue description suggests something that only runs once per process in order to e.g. initialize static items. The latter is what I’ve implemented for Servo.

This would be ideal for my use case.
setup()
test1()
test2()
test3()
teardown()

This would allow all tests to be run in parallel  instead of having to run with --test-threads=1
Is this still being considered under this RFC?

That's more likely covered by https://rust-lang.github.io/rfcs/2318-custom-test-frameworks.html


rusty-demo fails to build on windows

I have the required things installed.

nasm (in PATH as well)
rust toolchain nightly-2023-03-15 installed and ready to go (with rust-src component)
rusty-demo lists (as of this current date):

[target.'cfg(target_os = "hermit")'.dependencies]
hermit-sys = "0.4"

The build fails with
error[E0635]: unknown feature `atomic_mut_ptr`
    --> src\lib.rs:12:12
     |
  12 | #![feature(atomic_mut_ptr)]
     |            ^^^^^^^^^^^^^^

Changing rust-demo hermit-sys to the following fixes it.
hermit-sys = { git = "https://github.com/hermitcore/rusty-hermit" }
Don't know where, but something must be going wrong somewhere, but it's fixed in master. Theoretically I don't think this is a problem with the demo itself. if you use the crates.io package at all, this happens.

Oh, we have to update hermit-sys at crated.io. I will do it tomorrow.

Ah, I understand what's going wrong. Apparently, windows does not respect the internal rust-toolchain.toml in libhermit-rs.
You should be able to work around this issue by downgrading to nightly-2022-10-19, while we figure out a proper fix. 🤔

Ah, yes. This sounded familiar. Manually installing the llvm-tools-preview component for that toolchain should work around the issue. (https://github.com/hermitcore/rusty-hermit/issues/374#issuecomment-1289216468)
I don't have a local windows setup, but I'll continue experimenting on what we have to change in the build.rs of hermit-sys, so automatic rust-toolchain.toml detection for the kernel works on windows as well: https://github.com/hermitcore/rusty-demo/pull/26

llvm-tools-preview

Confirmed that llvm-tools-preview fixes the issue!

I fixed the underlying issue in https://github.com/hermitcore/rusty-hermit/pull/431. 🎉

Published as hermit-sys 0.5.1. :)


Variant repr fix

Summary
Not sure from which rails version on this is needed, but to get the right path for the modified image rails_representation_path (or *_url) is to be used.
Thanks to https://www.20spokes.com/blog/using-active-storage-with-active-model-serializers/
Not very well documented elsewhere (at least in my filter-bubble).
Now, for example, when using the content-tag cms:file the url is correct with all (image-magick) processing options and the variant is shown on the page

About the test failing: actually the test at test/lib/content/tags/file_test.rb seems to be wrong using the same function i partially replaced
I can update the test accordingly and PR again if you confirm that

Yeah, that was a bug. Fixed up and merged. Thanks.


CFTools ID

Can you add the function that players also have the possibility to show their stats with their SteamID?

Implemented, I'll create a new release


Updates from Fabio

Hey @mendesfabio , can you please share updates on these points

[ ] #19
[ ] #408
[ ] Adapt v2 subgraph to expose same fields as v3 subgraph (volume, fee per token, not USD)
[ ] #412
[x] Estimate on our monthly spend with the Graph
[ ] #773

The Graph spend is roughly $300/month

speaking of all SG-related topics I'm wrapping up the migration of both gauges and v2 to the subgraphs monorepo - which for v2 includes adapting schema to follow v3's standards, adding fees
https://api.studio.thegraph.com/query/31386/balancer-v2-vault/version/latest
it'd be great if you can just check schema in the playground. If you try to do some queries you'll notice pre-minted BPTs are messing up things but I'm working to fix it.

it'd be great if you can just check schema in the playground. If you try to do some queries you'll notice pre-minted BPTs are messing up things but I'm working to fix it.

I checked the schema for snapshots and pools which look good to me. Best would be to actually integrate the new schema into the API to see how much we can align v2 and v3 transformations. We are working on a big refactor currently, we can do a test integration after that.
Only thing I noticed is that you renamed joinExit to addRemove, right? That would be breaking on our end and I assume for other integrations as well. For us it doesnt matter much as we use deployment IDs and can adapt before moving to the new version. Wonder if we need to support joinExit still for others.

@mendesfabio is it possible to add lifetime values to the pool entity?

do you mean exposing liquidity, volumes, etc, as array in the pool entity? if that's much better for you, happy to make the change, but note the cumulative/lifetime values (volume, total protocol fee, etc) are currently exposed in the pool tokens. btw i've deployed v2 pools and vault subgraph to base for testing of one the production chains.

https://api.studio.thegraph.com/query/31386/balancer-v2-pools-base/version/latest
https://api.studio.thegraph.com/query/31386/balancer-v2-vault-base/version/latest

do you mean exposing liquidity, volumes, etc, as array in the pool entity? if that's much better for you, happy to make the change, but note the cumulative/lifetime values (volume, total protocol fee, etc) are currently exposed in the pool tokens.

Its different on the snapshot. Would be great to align it. Not sure which way is better tbh. I dont think it changes much for us.

btw i've deployed v2 pools and vault subgraph to base for testing of one the production chains.

https://api.studio.thegraph.com/query/31386/balancer-v2-pools-base/version/latest
https://api.studio.thegraph.com/query/31386/balancer-v2-vault-base/version/latest

Nice! We'll check this out!


Add more supported simulator debugging options and improve tests

Add more supported simulator debugging options update tests. Also, add tests for other launch arguments.
Fixes https://github.com/flutter/flutter/issues/52676.
Pre-launch Checklist

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

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Discussed with @jmagman about improving this code by using a single function that returns the list of launch arguments that can then be used for both the iOS simulator and physical iOS. The upside of this would be less repeated code, and if someone wants to add a new flag in the future, they can add to just one place and won't have to remember to add to both simulators.dart and devices.dart.

Also discussed how the simulator version only adds the flags if the debuggingOptions.debuggingEnabled is true
https://github.com/flutter/flutter/blob/d40f6d1e681f17e3b7b7290afb4c9b4175b976e7/packages/flutter_tools/lib/src/ios/simulators.dart#L432-L448
Whereas the device version adds them regardless, and only adds 2 specific ones if debuggingOptions.debuggingEnabled is true.
https://github.com/flutter/flutter/blob/d40f6d1e681f17e3b7b7290afb4c9b4175b976e7/packages/flutter_tools/lib/src/ios/devices.dart#L359-L363
Since the iOS simulator only runs in debug mode (profile and release mode are not supported), we think it's okay to remove the debuggingOptions.debuggingEnabled check for the simulator.

Note about https://github.com/flutter/flutter/pull/114628/commits/cc03fe2d4ad53cc25c0ac6805ac5f2d0baf53a22.
So I've discovered that having the quotes surrounding the --dart-flags launch argument matters and differs between simulator and physical iOS devices.
https://github.com/flutter/flutter/blob/cc03fe2d4ad53cc25c0ac6805ac5f2d0baf53a22/packages/flutter_tools/lib/src/device.dart#L926-L927
I tested this locally by using a single check for the dart flags and tried with and without quotes.
 if (dartVmFlags.isNotEmpty) '--dart-flags="$dartVmFlags"',
Command I ran flutter run -d xxx --dart-flags="--max_profile_depth 255,--foo"
Expected Result: Encountered disallowed Dart VM flag: --foo
Test 3 - with quotes, physical device - PASS
Result: [VERBOSE-3:switches.cc(441)] Encountered disallowed Dart VM flag: --foo
Test 4 - with quotes, simulator device - FAIL
Result: [VERBOSE-3:switches.cc(441)] Encountered disallowed Dart VM flag: "--max_profile_depth 255
Test 1 - without quotes, physical device - FAIL
Result: Runner[781:39983] Ignoring flag: true is an invalid value for flag max_profile_depth
Test 2 - without quotes, simulator device - PASS
Result: [VERBOSE-3:switches.cc(441)] Encountered disallowed Dart VM flag: --foo


[ci] Ubuntu version mismatch between machines causes false cache hits

The recent bump to Ubuntu 20.04 in #14432 caused a version mismatch in glibc (among probably many other things) between the Azure runners and the self-hosted runners. The remote cache is not able to differentiate builds between these to platforms, leading to cache hits where there should not be. This is leading to our self-hosted runners (using Ubuntu 18.04) pulling cached artifacts that were built on Azure runners (using Ubuntu 20.04).
This is a known issue mentioned in the Remote Caching documentation and is tracked in bazelbuild/bazel#4558.
The immediate solution is going to be sharding the cache by including the OS version in the build actions, similarly to what's described here. In the short term, we need to prioritize upgrading the GCP nodes and the FPGA runner to Ubuntu 20.04. In the long term, making the entire build process hermetic will solve this problem entirely.

Example output from a failing ROM E2E Test:
Testing //.../rom/e2e:e2e_bootstrap_entry_fpga_cw310; 0s local
==================== Test output for //sw/device/silicon_creator/rom/e2e:e2e_bootstrap_entry_fpga_cw310:
Invoking test: sw/host/tests/rom/e2e_bootstrap_entry/e2e_bootstrap_entry --cw310-uarts=/dev/ttyACM_CW310_1,/dev/ttyACM_CW310_0 --rcfile= --logging=info --interface=cw310 --rom-kind=rom --bitstream=external/bitstreams/cache/7cbb64c42451e388246c37f46252db1fbd8cd550/lowrisc_systems_chip_earlgrey_cw310_0.1.bit.splice --bootstrap=sw/device/silicon_creator/rom/e2e/e2e_bootstrap_entry_prog_fpga_cw310.bin
sw/host/tests/rom/e2e_bootstrap_entry/e2e_bootstrap_entry: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.29' not found (required by sw/host/tests/rom/e2e_bootstrap_entry/e2e_bootstrap_entry)
sw/host/tests/rom/e2e_bootstrap_entry/e2e_bootstrap_entry: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by sw/host/tests/rom/e2e_bootstrap_entry/e2e_bootstrap_entry)
sw/host/tests/rom/e2e_bootstrap_entry/e2e_bootstrap_entry: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by sw/host/tests/rom/e2e_bootstrap_entry/e2e_bootstrap_entry)
================================================================================


[DOC] Added Deep Learning notebook and images

Reference Issues/PRs
Fixes #406 #370

What does this implement/fix? Explain your changes.
Added a new deep learning notebook.
The notebook shows the usage of InceptionTime for classification as well as the Hybrid version (H-InceptionTime). It also includes the usage of InceptionTime for regression.
It includes as well a tutorial on model saving using FCN as example.
The last part is how to use aeon to take InceptionNetwork and create any task. I used a task that I did in a paper of mine [1], a self-supervised model.
[1] Ismail-Fawaz, Ali, et al. "Enhancing Time Series Classification with Self-Supervised Learning." ICAART (2023).

What should a reviewer concentrate their feedback on?
The presentation of the notebook.

PR checklist

For all contributions

[ ] Optionally, I've updated aeon's CODEOWNERS to receive notifications about future changes to these files.
[x] The PR title starts with either [ENH], [MNT], [DOC], or [BUG] indicating whether the PR topic is related to enhancement, maintenance, documentation, or bug.

I'm trying to structure the notebooks like the code, and I think that deep learning notebooks should go under networks maybe? If you agree, could you create a directory networks in examples and put it there? We also need to add networks to the API, but I can do that subsequently

yeah @TonyBagnall I actually was wondering where to put it ! Makes sense to put it under networks.

looks great, especially like the self supervised section at the end. Made a few suggestions

looks great, especially like the self supervised section at the end. Made a few suggestions

Thanks for the review ! This self supervised at the end is on my to do list (long term) to add it to aeon, but for now found it a perfect way of the 'any task' usage of deep learning. Will take care of the comments, thanks !

The notebook reviewer is pretty neat.
I have a few concerns, i.e. most of the examples don't actually use the deep learning base class, but this is just V1 so not going to go way into depth and demand reworks. I think it's a good start for sure.
Given that this covers deep learning in general for aeon I think it would be good to be as general and accessible as possible.

Not sure what do you mean they don't use deep learning base class, InceptionTime is a warp of Inception models which inherit from the deep base. FCN directly inherits from the deep base class.


Transforms/schemas: add support for loading schemas from other formats

Not sure exactly what this functionality would look like, but some data sources already have schemas:

When loading data from relational databases (or data exported from databases)
Data formats that contain a schema (like ARFF format for Weka)

We should be able to load those data formats, without needing to manually re-define the schema for this data.

Will be handled as part of pending update/rewrite.


cmd/server: sort flags

So that @rhatdan doesn't spend time sorting flags :) (joking)
I've opened https://github.com/urfave/cli/pull/544 upstream also.
@mrunalp @rhatdan PTAL
Signed-off-by: Antonio Murdaca<EMAIL_ADDRESS>

LGTM

LGTM


Setup without Pulse audio using usb DAC

basically this is not an issue. i was able to setup alexa using usb dac and without pulse audio easily, so posting it here hoping that someone might find it useful.
OS used: jessie-lite
After sudo apt-get upgrade
chaqnge the default audio device using
sudo nano /etc/asound.conf
in that paste the following and save, make sure to change "1" acording to your usb dac number
pcm.!default  {
type hw card 1
}
ctl.!default {
type hw card 1
}
restart the system and complete the alexa installation as mentioned in the guide. Then, open the config file using
sudo nano /etc/opt/AlexaPi/config.yaml
change the following
input_device: sysdefault:CARD=Device
output_device: ""
restart and you should have crystal clear audio

@shivasiddharth Could you write this up in a pretty form and put in https://github.com/alexa-pi/AlexaPi/wiki/Audio-setup-&-debugging so we can close this issue? Thank you.

I tried to edit that, but did not know as to how it must be done.


Dutch auction program

A Dutch auction is a type of auction where securities are priced via bids rather than the seller setting the price.
In this scenario, the seller sets a maximum price, which is lowered over time until all of the securities have been bid on.
Citation

A nice mechanism to integrate into Dutch auctions is to release the "lot" to the bidder, and hand over execution to a provided call. Then you only ask for payment at the end of the execution. It basically amounts to flashloaning the full amount to the bidder, which means anybody can participate in discovering the fair market price, even if they are capital constrained. c.f. Makerdao Liq 2.0 auctions : https://docs.makerdao.com/smart-contract-modules/dog-and-clipper-detailed-documentation#flash-lending-of-collateral

A nice mechanism to integrate into Dutch auctions is to first release the "lot" to the bidder, and hand over execution to a provided call. Then you only ask for payment at the end of the execution. It basically amounts to flashloaning the full amount to the bidder, which means anybody can participate in discovering the fair market price, even if they are capital constrained. c.f. Makerdao Liq 2.0 auctions : https://docs.makerdao.com/smart-contract-modules/dog-and-clipper-detailed-documentation#flash-lending-of-collateral

How would I delay asking for payment? Right now im just using msg_amount() to verify payment

The mechanism described above should be possible soon when arbitrary calls become possible (see #22 )


baseUrl and preview

I'm not sure if this has been brought up before, but when previewing with a baseUrl that is set to a website URL (e.g. http://www.ilikedogs.com/), it will start the server using that exact path (i.e. http://localhost:8080/http://www.ilikedogs.com/). I'd love to have my assets permalink'd (so the image will load in RSS feeds) and modifying baseUrl helps. Perhaps there should be two config options (baseUrl and basePath)?

Yeah that option is poorly named, should be basePath... The example blog's rss feed uses locals.url to create a permalink with the domain included.

Ah I see. I was not aware of this article.getHtml(locals.url). Really useful! :) Thanks :+1:


netlogon service will be set to manual but it's needed by windows time sync service (in domain environment)

Describe the bug
netlogon service will be set to manual but it's needed by windows time sync service (in domain environment)
To Reproduce
Steps to reproduce the behavior:

run tweaks (netlogon is set to manual)
Reboot
In windows settings under "Date/Time" you can see a source "CMOS clock" for timesync
time sync from DC is not working

Expected behavior
Not disable netlogon in domain environments
Screenshots
Additional context
It would be nice if there would be an detection, taht the computer is joined to a domain and skip some parts of the tweaks.
PS.: i know that normally you do such tweaks with GPO on the DC, but hey i have local admin rights and want to tweak my PC like i would :-)

Made a commit request to just remove netlogon from being touched by script, as according the script, it should already be manual on clean systems, so it seems redundant to touch it again especially if it may cause an issue...

In my case it was "manual" and not started, when needed by windows time sync service!
I think it was set to manual by the script (on other machines, where the script was not executed, it is on "auto").
After setting it manually to "auto" and started it manually, windows time sync service worked again, against the DC.
So yes, dont touch "netlogon" would be nice.

In my case it was "manual" and not started, when needed by windows time sync service! I think it was set to manual by the script (on other machines, where the script was not executed, it is on "auto"). After setting it manually to "auto" and started it manually, windows time sync service worked again, against the DC.
So yes, dont touch "netlogon" would be nice.
PS.: thx fot the pull request.

all good, it was something i could do with no knowledge of how to code... now to hope i dont get flamed for pulling to main as test branch is non existant

In my case it was "manual" and not started, when needed by windows time sync service! I think it was set to manual by the script (on other machines, where the script was not executed, it is on "auto"). After setting it manually to "auto" and started it manually, windows time sync service worked again, against the DC.
So yes, dont touch "netlogon" would be nice.
PS.: thx fot the pull request.

all good, it was something i could do with no knowledge of how to code... now to hope i dont get flamed for pulling to main as test branch is non existant

That's what I did so we're in the same boat :)

Netlogon has been changed to be set to Automatic in new test branch per PR #1220 being merged


the overflow is messed up in "My Orders"

@gbalabasquer i fix the spaces between, that's how it would look:
about:blank

@apmilen @pimato Ready to be tested on Surge.


Add SVD support for short-and-fat arrays

[X] Tests added / passed
[X] Passes black dask / flake8 dask

This is for https://github.com/dask/dask/issues/6590 and adds support for SVD on short-and-fat arrays by transposing inputs/outputs to/from tsqr.
To do a comparison to np.lingalg.svd, I needed to ensure that the eigenvector signs are always the same.  I lifted svd_flip from scikit-learn for that, but I'm not sure where to put it.  Alternatively, the comparison could look for equality on either sign in each vector as in dask-ml#731.  Any thoughts on that @mrocklin?
EDIT
FYI there were a few changes in here from the current upstream master branch that weren't passing the black formatter check.  This commit bases on https://github.com/dask/dask/commit/0ca1607aa14cb81520ca9526f871b631fe6706fa.  Hm how did that get into master without passing CI?

Hm well I can imagine that many end users don't currently care about sign indeterminacy with SVD, but I can't see any good reason why they shouldn't.
Some options that I had in mind were:

Leave it as a numpy-only testing utility (inline with the current test, as you suggested)
Move it to dask.array.utils since it's pretty essential for downstream library maintainers, but not necessarily something most users need to be aware of
Move it to dask.array.linalg (or maybe still utils?) and use it by default in svd

Option 2 seems like a logical choice now to keep what could be a somewhat unstable piece of code off of such a critical path but still surface the functionality.  If I'm not mistaken, https://github.com/dask/dask-ml/blob/master/dask_ml/utils.py#L26 is pulling the entire array into memory for the sign flip so it would probably take some work to rewrite that as a chunked operation without the nd fancy indexing currently used in sklearn.svd_flip.  I'm also not sure what u_based_decision is getting at, but I'd be happy to figure it out if you guys are on board with making svd_flip a part of the API (even if undocumented).

I'll trust your judgement on the importance of determinacy here. And I'd hate for performance to be the only reason not to do it.
Let's spend a bit of time seeing if we can implement a fast version and just always use it. I don't think the version in dask-ml is a good starting point. I'll look through your suggestion in https://github.com/dask/dask-ml/issues/731#issuecomment-682211742.

Let's spend a bit of time seeing if we can implement a fast version and just always use it

Ok cool, if it's all the same to you then I'll clean up this PR a little but would prefer to use the inline in-memory version of it within the test now and then submit a separate PR for svd_flip https://github.com/dask/dask/issues/6599 (after tinkering with how to do it a bit).

I rebased off your fix for those formatting issues (thanks for that @TomAugspurger) and this is ready to go afaict.  Let me know if there's anything else you think is worth testing or revisiting.

Sounds good to me, thanks!


feat(clipboard): Implement HTML and clear functionality

This PR introduces ability to set and read HTML to/from clipboard, including implementation to trigger clipboard clear.
Currently the added features are locked behind #[cfg(desktop)] as i have no ability to test them for mobile targets.

Looks like you need to run pnpm build and cargo fmt to fix formatting and also remove the extra undeeded read_html function


Emit detailed error messages for 4xx responses

The user-level consumers of the error responses of this application will need to provide detailed errors to uses. This can be supported by, or made possible by, the provision of detailed 4xx response bodies.
Will need to consider how to present machine-readable error detail such that it can act as source for both machine- and human-readable error content.
This will likely then be factored out to a package used by some (all?) services on which the api gateway depends.

Example for empty field:
{
  "type": "invalid_request_field",
  "field": {
    "name": "label",
    "value": ""
  },
  "error": {
    "class": "empty"
  }
}

Duplicate unique value:
{
  "class": "invalid_request_field",
  "type": "duplicate",
  "field": {
    "name": "label",
    "value": "Value must be unique and is already taken"
  }
}

Invalid value data type (400 response):
{
  "class": "invalid_request_field",
  "field": {
    "name": "count",
    "value": "string value",
    "data-type": "string"
  },
  "type": "incorrect-data-type",
  "requirements": {
    "data_type": "int"
  }
}

Fixed by #202


Migrate from awesome-typescript-loader (deprecated) to ts-loader

https://github.com/TypeStrong/ts-loader (use ts-loader 8.x if you need webpack 4 support, which is what we're currently using)

Closing, will be addressed in https://github.com/toddmedema/electrify/pull/77


Chart.js version 2.8.0

Trying to integrate  Chart.js version2.8.0 with prototype library
Getting TypeError: undefined is not an object (evaluating 'ticks.length')
Expected Behavior
Should work and show chart
Current Behavior
Getting TypeError: undefined is not an object (evaluating 'ticks.length')
Possible Solution
Adding if defined checks  for ticks fixed the issue.
I have copied my fix below, not sure why ticks getting undefined here.
Line 10088:
linear: function(tickValue, index, ticks) {
var tickString = '';
if(ticks)) {
// If we have lots of ticks, don't use the ones
var delta = ticks.length > 3 ? ticks[2] - ticks[1] : ticks[1] - ticks[0];
..........
}
Steps to Reproduce (for bugs)
##With the sample code
Tried sample provided : https://www.chartjs.org/docs/latest/getting-started/
Context

Environment

Chart.js version: Version 2.8.0
Browser name and version: Safari Version 12.1 (146<IP_ADDRESS>.4)
Link to your project:

This likely works and is a bug in your code setting it up. However, you did not provide an interactive example per the usage reporting guidelines, so we can't tell what is going wrong. Please feel free to reopen along with an interactive example as requested.


Upgrade to Hibernate ORM 5.4.17.Final

it's available now, and we need it for various improvements.
The upgrade breaks something in ReactiveQueryLoader and ReactiveCustomLoader, I assume @DavideD knows what needs to be done?

Is it related to #207?

Working on it

The problem is that CachingReactiveLoader#bindPreparedStatement scope is in conflict with Loader#bindPreparedStatement
Adding the merhod in Loader was part of this PR: hibernate/hibernate-orm#3420
that was sent during the work to support parameters #197
Renaming the method in CachingReactiveLoader seems the simplest trick for now.

The problem is that CachingReactiveLoader#bindPreparedStatement scope is in conflict with Loader#bindPreparedStatement

I understand, that's because we're going to delete CachingReactiveLoader#bindPreparedStatement :-)

(The relevant discussion)


Datasets currently down - graphql service rejects

Describe the bug
Visualize Browse: No datasets found - turning forever
To Reproduce
Steps to reproduce the behavior:

Go to

https://visualize.admin.ch/browse
https://int.visualize.admin.ch/browse
https://test.visualize.admin.ch/browse

Wait forever

Expected behavior
Show list of datasets
Screenshots

Environment (please complete the following information):

TEST and INT and PROD

Additional context
request
curl 'https://visualize.admin.ch/api/graphql' -X POST --data-raw '{"query":"query DataCubes($locale: String!, $query: String, $order: DataCubeResultOrder, $includeDrafts: Boolean, $filters: [DataCubeSearchFilter!]) {\n  dataCubes(\n    locale: $locale\n    query: $query\n    order: $order\n    includeDrafts: $includeDrafts\n    filters: $filters\n  ) {\n    highlightedTitle\n    highlightedDescription\n    dataCube {\n      iri\n      title\n      creator {\n        iri\n        label\n        __typename\n      }\n      description\n      publicationStatus\n      datePublished\n      themes {\n        iri\n        label\n        __typename\n      }\n      __typename\n    }\n    __typename\n  }\n}\n","operationName":"DataCubes","variables":{"locale":"de","includeDrafts":false,"filters":[]}}'
response
<title>Request Rejected</title>The requested URL was rejected. Please consult with your administrator.

Your support ID is:<PHONE_NUMBER>21991049

[Go Back]
@ptbrowne @bprusinowski

Lessons learnt (draft)

implement some API monitoring? (i.e. pingdom on graphql etc.) similar to https://status.geo.admin.ch/
have alerts to trigger intervention by the responsible providers?

Thanks Thomas for the report. We have https://visualization-tool.status.interactivethings.io/ to monitor status (you can subscribe to get updates).
e've started having problems on Friday afternoon, and we think it's a firewall problem, as locally the site works perfectly. We have contacted the hosting provider to have more information and to tell them to insert firewall exceptions for our requests. Unfortunately at our level, there is not much we can do. I'll keep you posted here.

Fixed, it was a firewall problem.

Thanks for your intervention and for escalating this to the firewall operator.
Wouldn't it be useful to monitor for Request Rejected hence automatically escalating to the operator for 24x7 intervention?
cc @zellersabine @retostoll

@ptbrowne Thanks for your intervention and for escalating this to the firewall operator.
Wouldn't it be useful to monitor for Request Rejected hence automatically escalating to the operator for 24x7 intervention?
cc @ZellerSabine @RetoStoll

We are currently monitoring the firewall rejection, since you have subscribed to the status page, you should have received a notification when the situation was solved (this notification was automated). We could escalate automatically to Jan from Abraxas if needed, but I do not know the contract you have with them for this. Since whitelist rules were added, I do not think the firewall situation will repeat.

👍 Hopefully it will not reoccur too often.
IMHO a direct alert to the ops makes sense (at least for ops related issues like firewall blocking and the like)... but first Vero will clarify the SLA questions on uptime warranties and intervention.
cc @zellersabine


New implementation for Union Find

A new suggestion for implementation of union find data structure.
No need to code 'initialization' in main(), and it makes code debugging and usage easy! Hiding details of implementation much like library like usage.

reflected


Websocket closes and dies

I have a rippled with the following modif on the rippled.cfg:
[server]
port_ws_public
[port_ws_public]
port = 8888
ip = <IP_ADDRESS>
protocol = ws
I have multiple peers (locally) that connect to that ws.
If one host requests lots of data via the ws (for example lots of books), the ws closes with code 1000, but:

It's not technically a code 1000.
I'm not able to reconnect to the ws until I restart rippled.
All other peers that were using that ws are disconnected and can't reconnect until restart of rippled.

The following code (with RippleAPI) can be used to trigger the error:
const RippleAPI = require('ripple-lib').RippleAPI;

var util = require('util');
var fs = require('fs');

var CURRENCIES = [
	{
		currency : 'USD',
		  issuer : 'rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B'
	},
	{
		currency : 'BTC',
		  issuer : 'rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B'
	},
	{
		currency : 'USD',
		  issuer : 'rhub8VRN55s94qWKDv6jmDy1pUykJzF3wq'
	},
	{
		currency : 'EUR',
		  issuer : 'rhub8VRN55s94qWKDv6jmDy1pUykJzF3wq'
	},
	{
		currency : 'BTC',
		  issuer : 'rchGBxcD1A1C2tdxF6papQYZ8kjRKMYcL'
	},
	{
		currency : 'BCH',
		  issuer : 'rchGBxcD1A1C2tdxF6papQYZ8kjRKMYcL'
	},
	{
		currency : 'ETH',
		  issuer : 'rchGBxcD1A1C2tdxF6papQYZ8kjRKMYcL'
	},
	{
		currency : 'ETC',
		  issuer : 'rchGBxcD1A1C2tdxF6papQYZ8kjRKMYcL'
	},
	{
		currency : 'REP',
		  issuer : 'rchGBxcD1A1C2tdxF6papQYZ8kjRKMYcL'
	},
];

api = new RippleAPI({
	//server: 'wss://s-west.ripple.com:443'
	//server: 'wss://s1.ripple.com:443'
	server: 'ws://<IP_ADDRESS>:8888',
	maxFeeXRP: '0.1'
});

//----- RIPPLE API EVENTS ----------------
api.on('error', (errorCode, errorMessage) => {
	console.log('Ripple API error:' + errorCode + ': ' + errorMessage);
});

api.on('connected', () => {
	console.log('Ripple API connected');
});

api.on('disconnected', (code) => {
	console.log('Ripple API disconnected, code:', code);
});

api.on('ledger', ledger => {
	console.log('Ripple API Ledger:' + ledger.ledgerVersion);
	let n_books = 0;
	var promises_book = [];	//Collect promises from all books in parallel
	let t0 = process.hrtime();
	for (var i in CURRENCIES){
		for (var j in CURRENCIES){
			if (i != j){
				let book_requested = {
					base : {
						currency : CURRENCIES[i].currency,
						counterparty : CURRENCIES[i].issuer,
					},
					counter : {
						currency : CURRENCIES[j].currency,
						counterparty : CURRENCIES[j].issuer,
					}
				};
				promises_book.push(api.getOrderbook('rhub8VRN55s94qWKDv6jmDy1pUykJzF3wq',book_requested,{limit : 100}));

				n_books++;
			}
		}
	}
	Promise.all(promises_book).then(function(results) {
		let t = process.hrtime();
		console.log('Time for ' + n_books + ' books ms: ' + ((t[0] - t0[0])*1000 + (t[1] - t0[1])/1000000));
	});
});

api.connect();

https://www.xrpchat.com/topic/30893-rippled-local-ws-disconnects-and-dies/

Hello Tuloski,
I reproduced the issue using your script. The connections you are opening to the server are non-admin privileged and therefore are rate limited. This is a server mechanism meant to protect against client connections demanding too much in a short period of time.
A few running instances of your script consume enough drop fees fast enough to cross a server threshold that will cause the IP to be disconnected. When this happens, all WebSocket connections from that IP will be disconnected and new connections will not be allowed from the same IP for a period of time. If you set your log severity to info, you will see the warnings and disconnects documented in the log file. The rate limitation does not apply to admin connections.
I also noticed that your script (possibly ripple API?) attempts to reconnect immediately after being disconnected. This aggravates the problem as it will extend the waiting period necessary to connect again.
You have two choices, either use admin connections or slow the number of requests per WebSocket. I hope helps.
-M

See screenshot for attached script output. Note updated return code (1008 for "Policy Violation")

Hello Tuloski,
I reproduced the issue using your script. The connections you are opening to the server are non-admin privileged and therefore are rate limited. This is a server mechanism meant to protect against client connections demanding too much in a short period of time.
A few running instances of your script consume enough drop fees fast enough to cross a server threshold that will cause the IP to be disconnected. When this happens, all WebSocket connections from that IP will be disconnected and new connections will not be allowed from the same IP for a period of time. If you set your log severity to info, you will see the warnings and disconnects documented in the log file. The rate limitation does not apply to admin connections.
I also noticed that your script (possibly ripple API?) attempts to reconnect immediately after being disconnected. This aggravates the problem as it will extend the waiting period necessary to connect again.
You have two choices, either use admin connections or slow the number of requests per WebSocket.
-M

How to use admin connections? please

Connect on an admin-only port.

The server will also send you specific warnings to slow down. Backing off a second each time you get that warning should help. Look for RPC error code slowDown and JSON response entry "warning" : "load".


Core dumped while starting hyprland

Hyprland Version
hyprland-git?
Bug or Regression?
Bug
Description
Updated hyprland-git from like 5 mins ago and rebooted but got core dumped error. It's like 3am here so switched to hyprland instead of hyprland-git stable and things are working fie rn.
OS: Arch
Kernel: Linux 6.4.8-zen1-1-zen
Cpu: Intel Core i3-7100
Gpu: integrated
sorry for my rush on the issue but i was going to sleep.
How to reproduce
Using latest hyprland-git?
Crash reports, logs, images, videos
No response

https://github.com/hyprwm/Hyprland/pull/2908

Same here, i had to downgrade to v0.28.0

Seems like already fixed so closing😄


Change entries

This implies that changing entries does not require manually deleting (#10) and then adding (#5) a mofidied entry, nor manually changing the fof file. It should be something like scalp change in format.

Since the release of scalp v1.3, this is possible. However, I am not satisfied with the current interface to change entries, since usually, one wants to change either time or the message, but not both.

The introduction of scalp move should solve this.


ImportError: cannot import name 'urlencode'

I am using Python 3.5.2 in my Django app. When I try to login, it gives me this error

Exception Value: cannot import name 'urlencode'
Exception location: .../site-packages/azure_ad_auth/utils.py in , line 8

There is an update for Python 3 compatibility, but it is not published to Pypi yet. You can install the latest version like pip install  https://github.com/leibowitz/django-azure-ad-auth/archive/dev_1.5.0.zip or add  https://github.com/leibowitz/django-azure-ad-auth/archive/dev_1.5.0.zip to your requirements.txt

@felixschul is right in the sense that python 3 support exists in master since https://github.com/leibowitz/django-azure-ad-auth/pull/2
You can use this fork (from master) or from release, as per @felixschul suggestion


Fix: make version finding relative

This enables importing the module as a submodule

Thanks for this. It was something I recently looked into and made some changes to on my local copy, which I am still experimenting with -- things are still largely experimental at the moment.
I will merge this for now, but it may change when I finish my complete refactor in a few months after the uni semester :)


Install jq in vagrantbox

Jq should be used to extract properties from consul/vault/nomad output. ( not awk/grep )

Passed critical point in installation


docs(migration guide): added a migration guide page

added a migration guide page with coming soon footer and link to GitHub migration guide issue, added
the page to the handbook toc
re #1157

Nice one! Perhaps we should merge that to master too?

Sure.
Maybe this will encourage some people to jump over the edge.
I  can prepare a separate PR with the changes in this commit for master, as this is for main and I assume we don’t want to merge the whole main branch into master, for now (though I barely can await :wink: ).

I've added the 3.x migration guide on master, so will merge it to main from there. Thanks!


Access Token and Refresh Token Secrets being leaked in Github Action Logs and publicly visible to anyone

Because the CLASPRC_JSON_FILE environment variable is not a repository secret it is being leaked during some of the Github Action deployment steps including "Push script to scripts.google.com" and "Deploy Script"
For example, this is what I see in my logs (I've partially redacted with ...):
Run clasp push -f
  clasp push -f
  shell: /usr/bin/bash -e {0}
  env:
    CLASPRC_JSON_FILE: CLASPRC_JSON_FILE: {"token":{"access_token":"ya29.a0AR..........
    CLASPRC_JSON_SECRET: ***

Also, I can currently see secrets in your repository being leaked in the "Save updated CLASPRC_JSON environment variable to CLASPRC_JSON repo secret" deploy step (I've redacted them in this issue with ....):
Run<EMAIL_ADDRESS>  with:
    name: CLASPRC_JSON
    value: {"token":{"access_token":"ya29.a0AR...........................","scope":"https://www.googleapis.com/auth/script.webapp.deploy https://www.googleapis.com/auth/script.projects https://www.googleapis.com/auth/drive.metadata.readonly https://www.googleapis.com/auth/logging.read https://www.googleapis.com/auth/cloud-platform openid https://www.googleapis.com/auth/userinfo.email https://www.googleapis.com/auth/script.deployments https://www.googleapis.com/auth/drive.file https://www.googleapis.com/auth/service.management https://www.googleapis.com/auth/userinfo.profile","token_type":"Bearer","id_token":"***","expiry_date":1634433630178,"refresh_token":"........................"},"oauth2ClientSettings":{"clientId":"1072944905499-vm2v2i5dvn0a0d2o4ca36i1vge8cvbn0.apps.googleusercontent.com","clientSecret":".............","redirectUri":"http://localhost"},"isLocalCreds":false}
    repository: ericanastas/deploy-google-app-script-action
    token: ***
  env:
    CLASPRC_JSON_FILE: {"token":{"access_token":"ya29.a0AR.........","scope":"https://www.googleapis.com/auth/script.webapp.deploy https://www.googleapis.com/auth/script.projects https://www.googleapis.com/auth/drive.metadata.readonly https://www.googleapis.com/auth/logging.read https://www.googleapis.com/auth/cloud-platform openid https://www.googleapis.com/auth/userinfo.email https://www.googleapis.com/auth/script.deployments https://www.googleapis.com/auth/drive.file https://www.googleapis.com/auth/service.management https://www.googleapis.com/auth/userinfo.profile","token_type":"Bearer","id_token":"***","expiry_date":1634433630178,"refresh_token":"................."},"oauth2ClientSettings":{"clientId":"1072944905499-vm2v2i5dvn0a0d2o4ca36i1vge8cvbn0.apps.googleusercontent.com","clientSecret":"..............","redirectUri":"http://localhost"},"isLocalCreds":false}
    CLASPRC_JSON_SECRET: ***

Sorry for the delay, yes that's looking better.  One thing to add, maybe CLASPRC_JSON_FILE with {} as value should be recommended to be added as a repository secret in the README.md so that it is automatically masked in the logs?

@somethingnew2-0
I don't think the automatic masking works by matching the secret names with environment variable names. Creating a CLASPRC_JSON_FILE secret is not going to mask anything unless it is somehow also had the new value.
For example say a repo has a secret named SECRET_A with the value "123" and the following action is run.
name: Test Secret Masking

on:
  workflow_dispatch:
  push:
    branches: [main, develop]
jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - name: Echo Secret
        id: echo-secret
        run: echo "$SECRET_B"
        env:
          SECRET_B: ${{ secrets.SECRET_A }}
          #SECRET_A is set to "123" in repository
      - name: Echo 123
        id: echo-1232
        run: echo "123"

This generates the following log
Echo Secret
Run echo "$SECRET_B"
  echo "$SECRET_B"
  shell: /usr/bin/bash -e {0}
  env:
    SECRET_B: ***
***
Echo ***
Run echo "***"
  echo "***"
  shell: /usr/bin/bash -e {0}
***

The log masks the secret value "123" anywhere it is found. It doesn't matter if my environment variable is named SECRET_B and not SECRET_A. The secret value is identified and masked according it the actual value of the secret.


exclude strings to strings.xml

And allow translations this way

Translation site https://danimahardhika.oneskyapp.com/collaboration/project?id=245866

I can not connect.
How to create an account ?
(It is for the French language, there are some spelling mistakes).

@msay2 You can login with github account

This is good, I just found the page to create an account 😉


[in_app_purchase 3.0.5] Not getting subscription products from console for android

Steps I have followed
Steps to Reproduce
Set up merchant account in PDC
Uploaded signed apk on Close track ( It is active and used by one tester)
Now if checking with same keystore and app id in getting 0 products with same ids created in console
Here is the details

in_app_purchase: ^3.0.5

await _inAppPurchase.isAvailable(); getting true for this but not getting anything in this await _inAppPurchase.queryProductDetails(_kProductIds.toSet());
I have verified appId and product id
Included this in build.gradle:
def billing_version = "5.0.0"
implementation "com.android.billingclient:billing:billing_version"

Expected results:
Actual results:
Here _kProductIds= my subscription product ids

Sample code

 await _inAppPurchase.isAvailable();
 await _inAppPurchase.queryProductDetails(_kProductIds.toSet());

flutter doctor -v
[✓] Flutter (Channel stable, 2.10.4, on macOS 12.1 21C52 darwin-x64, locale en-GB)
    • Flutter version 2.10.4 at /Users/admin/Nidhi/FlutterSDK/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision c860cba910 (3 months ago), 2022-03-25 00:23:12 -0500
    • Engine revision 57d3bac3dd
    • Dart version 2.16.2
    • DevTools version 2.9.2

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/admin/Library/Android/sdk
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7590822)

[✓] VS Code (version 1.66.2)
    • VS Code at /Users/admin/Downloads/Visual Studio Code.app/Contents
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (3 available)
    • RMX1921 (mobile)             • <IP_ADDRESS>:5555 • android-arm64  • Android 11 (API 30)
    • sdk gphone64 x86 64 (mobile) • emulator-5554       • android-x64    • Android 12 (API 31) (emulator)
    • Chrome (web)                 • chrome              • web-javascript • Google Chrome 102.0.5005.61

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

Please let me know If I am missing something.

Hi @nidhi-concetto,
From your flutter doctor -v, I can see you're using old Flutter SDK, please upgrade it to the latest version.
Then provide a completed and minimal reproducible code sample so that we may verify this.
Thank you!

For your information,

def billing_version = "5.0.0"

You're using a new billing_version that isn't supported yet. See https://github.com/flutter/plugins/pull/5405
So I recommend you using the same version as the example here
implementation 'com.android.billingclient:billing:3.0.2'

but not getting anything in this await _inAppPurchase.queryProductDetails(_kProductIds.toSet());

From queryProductDetails API document, this function will return a ProductDetailsResponse object, is it null in your case?

Thanks for the reply @huycozy  this is working now with implementation 'com.android.billingclient:billing:3.0.2' and one more things I have done , I have created new subscriptions after alpha release then I got all new subscriptions somehow old subscriptions which were created before release and payment account integration was not working.


Add docker to systemd sources

I did not regenerate the sources, wanted to see people agree this needs to be added first.
My source was https://github.com/kubernetes/kubernetes/blob/master/cluster/addons/fluentd-gcp/fluentd-gcp-configmap.yaml#L279 as that's what we're already running.

What kind of logs does this retrieve ?


deterministic=True ignored in MultiHeadAttention

I see that deterministic is deprecated, but while Dropout itself handles it and warns, MultiHeadAttention simply ignores it:
from jax import random as jrandom
import equinox as eqx

qk, kk, vk, ak, dk1, dk2 = jrandom.split(jrandom.PRNGKey(0), 6)
attn = eqx.nn.MultiheadAttention(num_heads=1, query_size=1, dropout_p=0.1, key=ak)
q = jrandom.uniform(qk, (5, 1))
k = jrandom.uniform(kk, (5, 1))
v = jrandom.uniform(vk, (5, 1))

assert (
    attn(q, k, v, key=dk1, inference=True) == attn(q, k, v, key=dk2, inference=True)
).all()  # this works

assert (
    attn(q, k, v, key=dk1, deterministic=True) == attn(q, k, v, key=dk2, deterministic=True)
).all(), "Not actually deterministic"

I'm just learning jax and equinox, but if this seems right, should I submit a PR?

Yup, that's a bug. Very happy to take a PR on this, thank you.


skip case when preview feature is not enabled

@squirrelsc there is one concern that, whether the original exception is HttpResponseError type.

@squirrelsc there is one concern that, whether the original exception is HttpResponseError type.

Did you have a chance to repro it? How about the validation service subscription?

@squirrelsc there is one concern that, whether the original exception is HttpResponseError type.

Did you have a chance to repro it? How about the validation service subscription?

I have tried with dev and test, but unregister the feature doesn't take effect, let me try with your suggestion. thanks.

@squirrelsc there is one concern that, whether the original exception is HttpResponseError type.

Did you have a chance to repro it? How about the validation service subscription?

I have tested it.


Update patches (12-10-2021)

See individual commits for details.

do you need to run regen when the series files are removed or created?

No, only when fully dropping series; this PR does not do that. I added a check in check-patches.sh to account for this. ./generate.sh all does not change anything.

Thank you for the review as always!


Premature resolution/validation of optional properties for existing resources with if condition

Bicep version
0.28.1
Describe the bug
It seems like there's some premature/inaccurate validation of optional properties for existing resources with if conditions.
To Reproduce
Take the following code for example. Null-forgiving operator is resolved/executed inside the non-null condition.
// Mod.bicep
type Resource = {
  name: string
  resourceGroupName: string?
}

param storageAccount Resource?

resource StorageAccount 'Microsoft.Storage/storageAccounts@2023-05-01' existing = if (storageAccount != null) {
  name: storageAccount!.name // this fails validation when storageAccount is null
  scope: resourceGroup(storageAccount!.resourceGroupName!) // same thing here
}

output storageAccountId string? = storageAccount == null ? null : StorageAccount.id

As a result, I get an error if the storageAccount parameter is null.
Error Message: Deployment template validation failed: 'The template resource '[parameters('storageAccount').name]' at line '1' and column '527' is not valid: The language expression property 'name' can't be evaluated. Please see https://aka.ms/arm-functions for usage details.'.
If I modify the code and use safe-dereference operator with empty string I get just a different error message.
resource StorageAccount 'Microsoft.Storage/storageAccounts@2023-05-01' existing = if (storageAccount != null) {
  name: storageAccount.?name ?? ''
  scope: resourceGroup(storageAccount.?resourceGroupName ?? '')
}

Error Message: Deployment template validation failed: 'The template resource '' of type 'Microsoft.Storage/storageAccounts' at line '1' and column '527' is not valid. The name property cannot be null or empty. Please see https://aka.ms/arm-syntax-resources for usage details.'.
Workaround
The workaround is to replace empty string with any random value, which is annoying because the null forgiving operator should handle such cases, I suppose.
resource StorageAccount 'Microsoft.Storage/storageAccounts@2023-05-01' existing = if (storageAccount != null) {
  name: storageAccount.?name ?? 'bicep-hack' // anything but an empty string works fine
  scope: resourceGroup(storageAccount.?resourceGroupName ?? 'bicep-hack')
}

Closing as duplicate of #2371


Chromatic support?

~Using this library / tool, how would we auto-switch snapshots for Chromatic to take a snapshot per story per theme?~
Note, after a lot of debugging with the Chromatic team, and build snapshots failing over and over, we narrowed it down to this particular library. Note that this fails Chromatic builds / verification! I don't know why, and they couldn't produce errors that explained it.

@matthew-dean could you share what exactly falls?
Probably we need to add a current theme to the URL so you can open a specific theme. Now it's not supported


Prevent the use of empty user, service, or target names

This PR fixes hwchen/keyring-rs#86.
Since we can't alter the API to prevent the creation of credentials that have empty strings for target, service, or user names, we instead create "always invalid" credentials that, while well-formed, do no support calling get_password or set_password successfully.  (They always return a NoEntry error.)
The docs (both top-level and code-level) have been updated, and tests added to verify this handling.

Unless someone objects, I'm going to merge this weekend and release a new crate. @hwchen any objection?