Additional context would be helpful on this page

It would have saved a customer and I about half an hour of digging if this article mentioned that turning on these flows had the dependency of having the "Helper" cloud flows on before attempting to start these.

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

ID: 0b08b756-8274-5baa-21b0-301930f0aac6
Version Independent ID: 0b08b756-8274-5baa-21b0-301930f0aac6
Content: Set up clean-up for orphaned objects - Power Platform
Content Source: power-platform/guidance/coe/setup-orphan-components.md
Service: power-platform
Sub-service: guidance
GitHub Login: @manuelap-msft
Microsoft Alias: mapichle

Hello,
this page mentions at the top that the assumption is you have the Governance components solution installed and setup:

And that page mentions turning on the child flows - we try not to duplicate info across pages as that's hard for us to maintain
https://docs.microsoft.com/en-us/power-platform/guidance/coe/before-setup-gov#turn-on-child-flows

Agreed.  It wasn't assumed that this included turning on Helper cloud flows once the solution install completed for us anyway.  Probably not a big deal, but thought I'd submit the idea.
@.***
Bart Sneary
MTC Architect |<PHONE_NUMBER> W or<PHONE_NUMBER> M
<EMAIL_ADDRESS>3601 West 76th St, Suite 600, Edina, MN 55435 | www.microsoft.com/mtchttps://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.microsoft.com%2Fmtc&data=01|01|jenmoe%40microsoft.com|ba559a6d6d8544af2e9b08d3386a40e7|72f988bf86f141af91ab2d7cd011db47|1&sdata=unfjA6YUnXyp8itlgzOIVX%2FbvBKncmBwW6d4D9CANmY%3D
[X]
From: Manuela Pichler @.>
Sent: Wednesday, March 9, 2022 12:56 PM
To: MicrosoftDocs/power-platform @.>
Cc: Bart Sneary @.>; Author @.>
Subject: Re: [MicrosoftDocs/power-platform] Additional context would be helpful on this page (Issue #1155)
Hello,
this page mentions at the top that the assumption is you have the Governance components solution installed and setup:
[image]https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F55705669%2F157511121-eca20b5f-0004-4e9d-851e-fb1c9312db4f.png&data=04|01|basneary%40microsoft.com|614459da480d4c61441708da01fe7b6f|72f988bf86f141af91ab2d7cd011db47|1|0|637824489747147432|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=bKzxtEHOzXdlhJqJR7XmWgQ6mKU2lB4uzyswtnFyVHg%3D&reserved=0
And that page mentions turning on the child flows - we try not to duplicate info across pages as that's hard for us to maintain
https://docs.microsoft.com/en-us/power-platform/guidance/coe/before-setup-gov#turn-on-child-flowshttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpower-platform%2Fguidance%2Fcoe%2Fbefore-setup-gov%23turn-on-child-flows&data=04|01|basneary%40microsoft.com|614459da480d4c61441708da01fe7b6f|72f988bf86f141af91ab2d7cd011db47|1|0|637824489747197433|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=8yKrwLvZlU%2BgBFp4xFKwTcheaPJrCJqiuWuIA4BblDY%3D&reserved=0

Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fpower-platform%2Fissues%2F1155%23issuecomment-1063252678&data=04|01|basneary%40microsoft.com|614459da480d4c61441708da01fe7b6f|72f988bf86f141af91ab2d7cd011db47|1|0|637824489747197433|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=gQB%2BDmAui8HN3wYZSXNMCt%2BROc%2FOlPa3GrSpilAd8Q0%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJ645VESZ6QYUYBHNCCHPZLU7DX4ZANCNFSM5QKNAWIQ&data=04|01|basneary%40microsoft.com|614459da480d4c61441708da01fe7b6f|72f988bf86f141af91ab2d7cd011db47|1|0|637824489747197433|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=pOAUIPyBNvpBwYc4RFk2BaZUGypEo79fBt9%2FoeLbniA%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|basneary%40microsoft.com|614459da480d4c61441708da01fe7b6f|72f988bf86f141af91ab2d7cd011db47|1|0|637824489747197433|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=JHavRJLjZcP7%2FXyfCpUuv%2BJsKGcdfOdTVsPt%2F4vCgWo%3D&reserved=0 or Androidhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|basneary%40microsoft.com|614459da480d4c61441708da01fe7b6f|72f988bf86f141af91ab2d7cd011db47|1|0|637824489747197433|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=YwVul6ZMiHgPhE2CEENBHMy0mmgKXROSITMzKFcXS%2FM%3D&reserved=0.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

Thank you! These helper flows are used across all governance components, not just the orphan components which is why we only mention it once. But I'll make an amendment so that the first paragraph says "installed and configured the governance components" with a link to that section. I'll include that with the April release update!

Definitely a minor thing also, but the helpers were turned on by default with the install of the Core Solution, but these 3 helpers in the Audit/Governance solution were turned off by default after install.
@.***
Bart Sneary
MTC Architect |<PHONE_NUMBER> W or<PHONE_NUMBER> M
<EMAIL_ADDRESS>3601 West 76th St, Suite 600, Edina, MN 55435 | www.microsoft.com/mtchttps://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.microsoft.com%2Fmtc&data=01|01|jenmoe%40microsoft.com|ba559a6d6d8544af2e9b08d3386a40e7|72f988bf86f141af91ab2d7cd011db47|1&sdata=unfjA6YUnXyp8itlgzOIVX%2FbvBKncmBwW6d4D9CANmY%3D
[X]
From: Manuela Pichler @.>
Sent: Wednesday, March 9, 2022 1:02 PM
To: MicrosoftDocs/power-platform @.>
Cc: Bart Sneary @.>; Author @.>
Subject: Re: [MicrosoftDocs/power-platform] Additional context would be helpful on this page (Issue #1155)
Thank you! These helper flows are used across all governance components, not just the orphan components which is why we only mention it once. But I'll make an amendment so that the first paragraph says "installed and configured the governance components" with a link to that section. I'll include that with the April release update!

Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fpower-platform%2Fissues%2F1155%23issuecomment-1063257552&data=04|01|basneary%40microsoft.com|90d29c10b67842ecb5e908da01ff4dd0|72f988bf86f141af91ab2d7cd011db47|1|0|637824493287206074|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=y7zHKnDORVhKt2k2Z035JICEcjbSXgJAnpFGQO%2BT2Z4%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJ645VEWTUC5LAQK3GG3SO3U7DYS3ANCNFSM5QKNAWIQ&data=04|01|basneary%40microsoft.com|90d29c10b67842ecb5e908da01ff4dd0|72f988bf86f141af91ab2d7cd011db47|1|0|637824493287206074|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=q0E92NMOjrfuIMiW%2FmpyD8dQChW82A9MxU5PArlTO14%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|basneary%40microsoft.com|90d29c10b67842ecb5e908da01ff4dd0|72f988bf86f141af91ab2d7cd011db47|1|0|637824493287206074|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=ntTqt2fja6%2FiKt%2B5CQVGwcuuXQoC5PTLWBxf%2Fy1zAt0%3D&reserved=0 or Androidhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|basneary%40microsoft.com|90d29c10b67842ecb5e908da01ff4dd0|72f988bf86f141af91ab2d7cd011db47|1|0|637824493287206074|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=oQRk5ckImtQGZCuIemhLJk5qnHhSZFDBxA6pRWPjEVQ%3D&reserved=0.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>


ci: lint all files with Megalinter

Description
This PR makes sure that all files are syntactically valid and adhere to the specific format. This makes it easier to read the files in the repository.
Migrations required
No
Verification
Verified that the job runs and throws an error if a markdown file is not valid.

@npalm What do you think about linting the markdown files (auto generated parts are excluded)? Just to make sure to follow the same schema and have valid markdown only.

Great idea to start linting arkdown. What would you think about using the megalinter (https://megalinter.io/latest/configuration/)? The megalinter could also be enabled only for markdown but can also be used to lint action yml, bash, docker and any other file in the repo excluding terraform. Since for Terraform all kin dof linting is already in place.
What are you thoughts?

Gosh, blocked by my firewall. Have to check later.
Linting all other files would be nice too. Didn't know that there is a Megalinter available. Makes things easier. Up to know I used specific linters for different file types. Good to know that things can be simplified.
Let's change to the one you proposed.

Gosh, blocked by my firewall. Have to check later.
Linting all other files would be nice too. Didn't know that there is a Megalinter available. Makes things easier. Up to know I used specific linters for different file types. Good to know that things can be simplified.
Let's change to the one you proposed.

only drawback is that those all-in-one linter like megalinter or superlinter are heavy packed containers. But i like them for using anything expect the main language in the reposiroty.

Let's merge #553 first which solves the TfSec problems.

@mkalmykov since we have already tfsec and standard terraform linters. I think we should disable all the Terraform checks in the megalinter. What is your thought?

I am not 100% sure that we should disable the Terraform checks in Megalinter. There are some interesting linters here, so may be we should drop the tfsec action.

Gotcha! Megalinter is running. There are 3 false warnings about lines in a markdown file which are too long. But the lines mentioned are ok. So I ignore it for now.

several issues fixed/ignored which were reported by the linters
I disabled some of the linters as explained in the PR.
the Terraform format check has been removed as it is done by Megalinter now
line length for markdown files is set to 132
removed unused locals.tags_string
globally ignored some Terrascan rules as they can't be ignored inline: Lambda function tracing enabled
tidy up Go dependencies
fixed some spelling issues

@npalm Fixed the stuff.

Megalinter needs 4+ minutes. Maybe it's better to use dedicated linters to have a fast workflow.
Tried it here: https://github.com/Hapag-Lloyd/Repository-Templates/blob/main/.github/workflows/linter.yml

@npalm Finished this one. The linters make sure that we follow the industry standard. Let's do it for some weeks and check the total workflow duration. If we are not satisfied, we can split the linters into single workflows.

Nice one, the Ci is stail failing, KICS gives one error. And the PR also has no write access. Maybe enalbling this can solve the 403 https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork

It was green, wasn't it? I wouldn't send the message in case of red pipeline. Strange.
Let me check this.

@npalm Seems to be fine now.

@npalm Need a new approval. Had to solve some conflicts.


[Clarification]: Purpose of each styles folder

There are currently two styles folder. One in the root path, and another one in inside the app/styles.
May I know what these two differs?

oh, nvm


support "SHOW DATABASES LIKE '...'"

This adds support for SHOW DATABASES LIKE '%'

Thanks @erh , but I only find that you just update parser but don't add this feature in code?

Yes, I'm actually just using the parser, and not the rest of the code.


Automatic loading of templates fails after Healthcheck

Expected behavior
As a user, I want to use automatic loading of templates which is suggested by the Healthcheck so that i receive the health status of  CobiGen.
Actual behavior
If there is no CobiGen_Templates project in the workspace, the Healthcheck suggests to download and use the latest templates. The update process results in an NullPointerException.

Steps to reproduce (bug) / Use Case of feature request (enhancement)

Do not import any CobiGen_Templates folder.
Right click on any file. Cobigen -> Health Check -> Update

It looks like there is a part of the logic to download and process the templates jar missing.  (com.devonfw.cobigen.eclipse.common.tools.ResourcesPluginUtil: getGeneratorConfigurationProject())
As a result, getGeneratorConfigurationProject() can not return any project and returns null.
I am implementing the missing logic.


Purge old Rendered Templates

@captncraig Didn't find any problems testing this out, but needs conflicts resolved.


Expose last_insert_id from Ok packet on MySQL

Took a whack at implementing what we discussed in https://github.com/diesel-rs/diesel/discussions/3605 (finally); I'm sure I need to add some documentation at minimum.
Notably, I copied most of the body of execute_returning_id() from execute_returning_count(), not sure if that's how you want to handle that or not
Might have overabstracted; I implemented it using traits for extensibility.
I'll have a follow-up in diesel_async once this is merged.

I don't think that that test failure has anything to do with my changes?


Build benchmark to evaluate text->image models

I think it would be really interesting to collect a list of prompts for each "text->image" task, eg

illustrations
realistic
compositions
many classes
faces/people
etc

and then turn that into a benchmark
so we would know what each model strengths really are

I'm sure I'm not the first one to have this idea, so the first task would be collecting papers that did things on the topic

similar to https://github.com/EleutherAI/lm-evaluation-harness

here’s the plan https://docs.google.com/document/d/18uAhB_99lTsfhKkBd6tiKbMhZcQ9hErLgJqEWuTOcQY/edit

That seems to be a plan for evaluating the retrieval for https://github.com/LAION-AI/project-menu/issues/13
Here is for generative models


Added logout, login to help message

Currently groups() on yargs does not work with Commands. However, bringing logout and login into the help message will still keep continuity between documentation and the CLI.

imo, these should be at the end of the list, they're not commands that'l be called often.

I agree that we should move these three commands lower down. Needs a rebase.


Bring v0.2 down into master

To prevent confusion and speed adoption, bringing v0.2 down into master.

ship it


chore: needs reproduction label name

Description
We have several labels like needs documentation and needs test. Our need reproduction was the only one that wasn't using needs. This PR aligns it to the rest.

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[x] Other

I've renamed the actual label after merging this PR 🙆♂

Thanks @sapphi-red! I was waiting too for it to be merged before doing the same :)


More Performance

Thank you for this Addon! It's easy and Awesome! :-)
A nice Feature would be to replace loaded Components if they are not more displayed because of the User has scrolled down. This helps the Browser-Performance if complex layouts with a lot of Compoents are displayed.

Yes that would be nice feature, but it would limit use cases and kinda break Vaadin layouting logic that this add-on is trying to maintain.


Support for searching in all versions

The current functionality only supports searching within the current page and finding results by turning pages. This PR implements the capability to search across all versions.

Is this normal? Why does 12.x version appear?

Is this normal? Why does 12.x version appear?

I'm still using the original search method and I think the results are correct, but the ordering of the results could be optimized a bit more and I'm working on that!

Before:

After:

@Chance-fyi  Hi, I would like to invite you to join VersionFox as a committer. Are you interested?

@aooohan Yes, I'm interested in joining VersionFox as a committer. Thank you for the invitation!


Catalog apps UI return cannot read property 'displayName' of undefined

Rancher versions: 2.0 master 07/19
Steps to Reproduce:

Go to the Catalog page and view details of any app
the Catalog UI returns cannot read property 'displayName' of undefined

Version - 2.0 master 7/23
Verified fixed


backend: add ExportNeoGo for Groth-16 BLS12-381 curve

Hello, devs!
First of all, thank you for your amazing zk-SNARK packages! Currently we are adapting them to create and verify Groth-16 BLS12-381 proofs on the Neo blockchain.
PR motivation
We (as developers of Neo node implementation written in Go) are about to add Groth-16 verification support for Neo smart contracts in the upcoming 0.102.0 release. We've successfully adapted your libraries to build an example circuit, generate proof for it and build/invoke Verifier Neo smart contract deployed to the Neo blockchain: https://github.com/nspcc-dev/neo-go/pull/3043/commits/5a19f81aff39486e2954a3b1fe95fa10c2045303. However, to create Verifier contract we have to retrieve paramters of groth16.VerifyingKey via its serialized representation (firstly use vk.WriteTo(&buf) and after that deserialise alpha, beta, gamma, delta and Kvks points from the resulted byte slice, take a look at the lines). It's not very convenient, but at the same time we can't use bls12-381-specific VerifyingKey implementation and directly access these parameters since it's located under the internal subdirectory.
At the same time, I've noticed that exported groth-16.VerifyingKey interface has ExportSolidity method that is supported for BN254 and provides the ability to generate Solidity Verifier contract by gnark library itself.
It would be very helpful for Go smart contract developers of Neo ecosystem to have a similar ExportToNeoGo method which is defined for Groth-16 BLS12-381 curve and iss able to generate Go Verifier contract for Neo blockchain. It allows to reduce the number of steps needed to build Verifier contract for contract developers.
PR content
This PR contains a very initial implementation of VerifyingKey.ExportToNeoGo method that was successfully tested with end-to-end test (the idea of the test is same as for ExportSolidity test in https://github.com/Consensys/gnark-tests/blob/main/solidity/solidity_groth16_test.go). There's a large space for improvement in this PR, but if it's OK for you to add this API, then I'll finish it and fix all the review comments.
The question
Is there any chance that this new VerifyingKey.ExportToNeoGo API will be added to your library?
I'll appreciate any comments and opinions on this topic. Thank you for your time!

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

Here's the end-to-end test of the new VerifyingKey.ExportToNeoGo API: https://github.com/Consensys/gnark-tests/pull/3.

hi @AnnaShaleva , thanks for the PR :)
My initial thoughts on that;
The reasons ExportSolidity exists are:

While gnark is blockchain agnostic, lots of gnark users are on EVM based chains.
Originally, curve specific groth16.VerifyingKey impl were not exposed and hidden in internal packages, so it was cumbersome for an external package to access the curve specific VerifyingKeystruct. This is not the case anymore (on develop branch: https://github.com/Consensys/gnark/tree/develop/backend/groth16), you can directly access the VerifyingKey data struct.
(3. Convenience for us, since we are maintaining (fixing audit reports etc) the solidity part too.)

TLDR; with 2., I think ExportToNeoGo should not live in gnark repo (will be more convenient for you to maintain).
We are a bit behind on the new release, couple of bug fixes / api coherence (between Groth16 and PlonK) fixes and v0.9.0 should be released 👍

@gbotrel, thank you for the reply!

This is not the case anymore (on develop branch)

Well, that solves our problem, we'll be glad to meet the v0.9.0 :)

(will be more convenient for you to maintain)

That's also true, thus, I'm closing this PR as not planned.


Recommendation for Inclusion in the Related Works Table

Dear Contributors,
Great job on the survey paper, and thank you for providing a summary page of all related works for the community. We would like to recommend our work on the LoRA-based federated foundation fine-tuning method. Specifically, we revisit FedRA (Su et al., ECCV 2024) with a focus on more realistic GPU memory consumption and propose a knapsack optimization problem to select trainable LoRA layers for each client, considering various memory constraints.
We would greatly appreciate it if you could include our work in the table during your next update to the page.
Thank you!
Zikai Zhang
Link to ArXiv Paper:
https://arxiv.org/abs/2410.10200
Citation Format:
@article{zhang2024fed,
title={Fed-piLot: Optimizing LoRA Assignment for Efficient Federated Foundation Model Fine-Tuning},
author={Zhang, Zikai and Xu, Jiahao and Liu, Ping and Hu, Rui},
journal={arXiv preprint arXiv:2410.10200},
year={2024}
}

Hi,
Thanks for your recommendation. The work is impressive. I have now included it in the table. Please also consider citing our survey in your publication if you think it is relevant.
Best regards,
Shenghui


C2d docker some fixes

Changes proposed in this PR:

increase maxJobDuration - 30 seconds was not enough when I run it in debugger
ensure the image pull completion
fix entrypoint when creating container

why are we opening a PR on another draft PR in progress? :-)

Yeah, I agree... We need to first focus on getting the initial PR merged before improving on it in different branches. @FilipMasar I would suggest that you leave comments and suggestions on https://github.com/oceanprotocol/ocean-node/pull/705

why are we opening a PR on another draft PR in progress? :-)
Because this is nowhere near a Ready PR.   The compute flow was not working until two days ago, and getResults ended with uncaught exception in node.

As regarding security, we have no tests yet

Regarding this containerInfo.Entrypoint = newEntrypoint.split(' ') - without split(' ') it was not working for me. In the docs they say that exec form is preferred

What version of Docker are you running?

why are we opening a PR on another draft PR in progress? :-)

Because this is nowhere near a Ready PR. The compute flow was not working until two days ago, and getResults ended with uncaught exception in node.
As regarding security, we have no tests yet

fair enough, its still draft but we're overlapping work here

Hey @paulo-ocean @jamiehewitt15 , thanks for your comments. I spoke with @alex-ocean23 that I was testing this branch, found some issues and he told me that I can open PR. Let me know if something else works better for you. Sometimes its easier to propose a fix than to explain the issue. Feel free to close this PR.
10 minutes - because when I run it with debugger it already timeouted before I got to running algorithm flow. So probably unnecessary change - just for testing. Is this free compute intended to be available in production?
Regarding this containerInfo.Entrypoint = newEntrypoint.split(' ') - without split(' ') it was not working for me. In the docs they say that exec form is preferred

https://docs.docker.com/reference/dockerfile/#shell-and-exec-form
https://docs.docker.com/reference/dockerfile/#entrypoint

Ok, but it was working for me

Hey @paulo-ocean @jamiehewitt15 , thanks for your comments. I spoke with @alex-ocean23 that I was testing this branch, found some issues and he told me that I can open PR. Let me know if something else works better for you. Sometimes its easier to propose a fix than to explain the issue. Feel free to close this PR.
10 minutes - because when I run it with debugger it already timeouted before I got to running algorithm flow. So probably unnecessary change - just for testing. Is this free compute intended to be available in production?
Regarding this containerInfo.Entrypoint = newEntrypoint.split(' ') - without split(' ') it was not working for me. In the docs they say that exec form is preferred

https://docs.docker.com/reference/dockerfile/#shell-and-exec-form
https://docs.docker.com/reference/dockerfile/#entrypoint

Ok, but it was working for me

@FilipMasar feel free to merge the PR then
btw, i'm curious.. why do we need this syntax?
await new Promise((resolve, reject) => {

lgtm.
Regarding maxJobDuration, we can leave it 10 mins as long as this is a draft PR.
For production, I think we will have an env var

@alexcos20 @FilipMasar The maxJobDuration is already part of the configuration, 30 seconds is just the default value if nothing else is specified. Now the default is 10 minutes

Because this is nowhere near a Ready PR.

@alexcos20 ok yeah, that's fair enough. Let's just make sure that we don't have the same issues fixed in two different PRs

ok, i'm gonna merge the PR. I do have some doubts about some of thh changes made here, specially the entrypoint, since we removed the containerId from the path , and that was the only way it worked for me on Linux

Regarding this containerInfo.Entrypoint = newEntrypoint.split(' ') - without split(' ') it was not working for me. In the docs they say that exec form is preferred

What version of Docker are you running?

Hey, sorry for late response
docker - v27.3.1
docker desktop - 4.35.1

Hey @paulo-ocean @jamiehewitt15 , thanks for your comments. I spoke with @alex-ocean23 that I was testing this branch, found some issues and he told me that I can open PR. Let me know if something else works better for you. Sometimes its easier to propose a fix than to explain the issue. Feel free to close this PR.
10 minutes - because when I run it with debugger it already timeouted before I got to running algorithm flow. So probably unnecessary change - just for testing. Is this free compute intended to be available in production?
Regarding this containerInfo.Entrypoint = newEntrypoint.split(' ') - without split(' ') it was not working for me. In the docs they say that exec form is preferred

https://docs.docker.com/reference/dockerfile/#shell-and-exec-form
https://docs.docker.com/reference/dockerfile/#entrypoint

Ok, but it was working for me

@FilipMasar feel free to merge the PR then btw, i'm curious.. why do we need this syntax? await new Promise((resolve, reject) => {

The followProgress method uses a callback-based approach to handle the progress of the pull operation. To use it with await, it needs to be wrapped in a Promise


Widget Display code does not save

Describe the bug
Clicking Save on a widget does not save the display code.  All other information, like version or general info does save.
To Reproduce
Steps to reproduce the behavior:

Create a new widget
Add Content, fill out the required fields, and add some display code
Save the widget
Open the widget again for editing
Display code will be blank
(this occurs with existing widgets as well)

The Display code was not saving as the html widget was not getting picked up while saving. This issue has now been fixed.


Does anyone have the .json file code for the night green mode?

To be used at the conf/ file.
I just wasn't able to find it anywhere in the files.

Maybe you can find it in src/color-template.ts.
{
    type: 'normal',
    backgroundColor: '#00000f',
    foregroundColor: '#eeeeff',
    strongColor: 'rgb(255,200,55)',
    weakColor: '#aaaaaa',
    radarColor: '#47a042',
    contribColors: ['#444444', '#1B7D28', '#24A736', '#2DD143', '#57DA69'],
}

Appreciate it. I will check


Use tile and fuse upto vector level.

While IREE currently generates reasonable code for GEMM operations through use of multi-level tile and distribute followed by vectorization, it is potentially still leaving some performance on the table based on how the linalg.fill operation (that typically accompanies the linalg.matmul operation) is handled. The dispatch region formation tiles and distributes and fuses the linalg.fill with the linalg.matmul for the first level of tiling. Once it gets to the codegen passes the linalg.fill and linalg.matmul. dont get fused till the vector level.
The goal of the code-generation would be to get to this code form
%fill = vector.splat %zerp : vector<4x4xf32>
%0 = scf.for %iv = %c0 to %k step %c4 iter_args (%acc = %fill) {
   %next = ...
   scf.yield %next
} -> vector<4x4xf32>
vector.transfer_write %0, %result...

This is essentially doing the fusion at the register level. This naturally extends to fusion of GEMMs etc. with elementwise operations as well since you could just do further operations after the reduction loop (k loop above) before writing the result out to memory.
The tileAndFuseLinalgOps utility method allows you to do tile and fuse operations as required by the description above. This is being reworked though to be more modular and controllable.
There is already some option in IREE to fuse GEMMS with its producers. This also suffers from the same problem as above that fusion is limited to a single level of tiling and is also limited in its usage (albeit covers a lot of common cases).
The specific steps involved in getting all of this working is

[x] Have a separate CPU lowering pipeline that goes from Tensors -> Vectors -> bufferization, right now the two are conflated and controlled by an LLVM flag (we should avoid LLVM style flags)
[ ] Use the new approach to fusion being developed in core to tile and fuse until vector level and then vectorize to get the required code structure
[ ] Enable fusion of GEMM with elementwise operations, and vectorize the elementwise operations as well. Since this makes the elementwise operation go through the vector dialect, and not rely on LLVM auto-vectorization (as is done for elementwise operations right now), this can cause regressions due to missing canonicalizations.
[ ] Once prototyped on LLVM CPU, move the SPIR-V pipeline to use tensors -> vectors. This will enable the same fusion on SPIR-V backends. Since mobile hardware in general do not typically benefit from use of scratchpad memory, the tensor -> vectors approach is expected to work well for SPIR-V.
[ ] Deprecate the existing fusion requirements.
[ ] The CUDA backend is slightly different in that the use of scratch pad memory is critical in achieving performance. It is not immediately clear that the modeling promotions in the tensor world give the desired result. This is TBD and a separate question to answer. In any case, the use scratchpad/shared memory means that the one-level of tile + fuse done at the Flow level is good enough to allow the CUDA backend to fuse these operations as well.

Apparently linking an issue closes it :)

Apparently linking an issue closes it :)

¯_(ツ)_/¯

With the CPU backend having moved to tile + fuse + vectorize and the SPIR-V backend having moved to tensors -> vectors -> bufferize. most of the work here is done. We need eventually move the CUDA backend as well to this approach, but thats a harder lift. So closing this bug for now since the main AIs have been resolved.


unpin numpy

NumPy 1.17.0 has now been released, so unpin, see https://github.com/numpy/numpy/releases/tag/v1.17.0
Follow-up from https://github.com/SciTools/cf-units/pull/153

Coverage increased (+2.8%) to 92.308% when pulling 783deedb3adb9d575bd57455c1d68fffbf3bfe9c on bjlittle:unpin-numpy into 8d0274aaf6deacda6bad5eeda44b0c2561ef524e on SciTools:master.


ddg() and ddg_news() return None.

I tried the proposed solution that was provided in the issue that was just closed, but it did not work. I am on the most recent version and am using python 3.10
Please help?

Please run this and show the result
import logging
from duckduckgo_search import ddg

logging.basicConfig(level=logging.DEBUG)

keywords = 'Bella Ciao'
results = ddg(keywords, region='wt-wt', safesearch='Off', time='y')
print(results)

Try using a proxy

Run the Tor browser in the background.
And try this:
import logging
from duckduckgo_search import ddg
from duckduckgo_search.utils import SESSION

logging.basicConfig(level=logging.DEBUG)

SESSION.proxies = {
    "http": f"socks5h://localhost:9150",
    "https": f"socks5h://localhost:9150"
}

keywords = 'Bella Ciao'
results = ddg(keywords, region='wt-wt', safesearch='Off', time='y')
print(results)

What about another proxy?

As far as I can tell, I can't setup a proxy the way you are suggesting if I'm using pythonanywhere. If it DID work when I used a proxy, what would that tell you about the issue?

blocked ip

That makes sense. Why would my IP be blocked? Is there a solution beyond using a different IP via proxy?

not your ip, but this site's python IDE (pythonanywhere)
https://www.google.com/search?q=Why+would+my+IP+be+blocked
Just use a proxy

With frequent requests site used to block ip for a period of about 10 seconds, now the period of blocking is much longer (I do not know exactly, about 10-30 minutes).


update to new variadic rules

Breaking Change to silence warnings, Swift 4

This should be from fix-variadic-rules (or something) into beta.

Yup, mixed that up 👍


socket recv error Connection reset by peer (104)

Updated wallet to commit 77559081a3d3ceeb91ea4d5810fe37f6fa75ee51 and it stopped syncing. All i see in debug.log are lots of socket recv error Connection reset by peer (104)

reverted back to branch 0.16, will stay on this

Hey there,
this bug should be fixed with the codebase ready at "master".
New releases will get uploaded ASAP.
Friendly Regards
Nico


Optimize number of SQL queries whenever possible.

This PR greatly improves the number of SQL queries performed on the frontend side when an adherent is logged in to his\her account. From 21 SQL queries to only 2!
Before

After

The duplicated SQL queries came from two different locations:

the adherent's navigation bar in the top right end corner,
security voters.

All voters now receive the CommitteeManager class that performs SQL queries with Doctrine repositories. This means optimizing can now be done inside the CommitteeManager class directly as everything is centralized. The CommitteeManager object is now able to check an Adherent entity's memberships directly before falling back to repositories to perform SQL queries. This way we can prevent some extra unneeded SQL queries to the database.
Thus, this design also enables us to add a caching layer on top of the committee manager by wrapping the CommitteeManager object in a CachedCommitteeManager object if necessary. The main downside of using a decorator here for this use case will be to reimplement all the methods from CommitteeManager in the decorator object and forward all method calls.

@hhamon isn't this finished then?

@tgalopin it's finished and ready for reviews.

I would like to have a second review as it's a big PR. @mykiwi @rpg600 ?

PR has been updated according to your comments.


Write buffer is failing for large size

I am trying to store parquet file data as buffer in indexeddb, but is failing with no error logged
the file size is around 430mb
"dexie": "^3.2.4",
  const db = new Dexie('duckDB');

  db.version(1).stores({ datasets: 'token,data' });

  const writeStart = performance.now();

  db.table('datasets').put({
    token: `taxi123`,
    data: file.data,
  });

But I can overcome it by removing the field data in schema like below and it works:
  const db = new Dexie('duckDB');

  db.version(1).stores({ datasets: 'token' });

  const writeStart = performance.now();

  db.table('datasets').put({
    token: `taxi123`,
    data: file.data,
  });

Is there any limit set for buffer size ? if yes then why second way was not failing

See https://dexie.org/docs/Version/Version.stores()#warning

Yeah works 👍


Support for REUSE Specification (License Detection)

Feature Description
I think it would be great if Gitea was able to detect multiple licenses under a LICENSES folder based on the SPDX identifier included in the filenames of present in that folder, as described by the Free Software Foundation Europe's REUSE Specification. (https://reuse.software)
That way, it would be possible to include multiple licenses easily without looking for the SPDX headers in every file that is present in the repository, while retaining the ability to include licensing information for binary files.
A "lazier" implementation that does not check for full compliance, but just looks at the contents of the LICENSES folder (unlike re-implementing or somehow integrating https://github.com/fsfe/reuse-tool - which does check every file) could work and that repositories using it could reduce some computational overhead (w.r.t. https://github.com/go-gitea/gitea/pull/24872#discussion_r1410524792) at scale.
I believe that the benefits and overall simplicity of supporting such an extension are highlighted in the review process of this pull request: https://github.com/go-gitea/gitea/pull/24872
Screenshots
No response

My motivation for this issue is also the fact that our project is pivoting towards utilizing that standard for its own projects and wanting to recommend it further to other free and open source developers.
I'd be interested in taking a look, but I already have a few outstanding PRs to circle back to and there is an actively developed PR that changes these very components.


Parallelize git extraction

Made irrelevant by https://github.com/elhmn/waking-git/pull/43#issue-1533929882


tsconfig.js file error

Type: Bug
Argument for '--moduleResolution' option must be: 'node', 'classic', 'node16', 'nodenext'.ts
This results in the typescript intellisense not working for typescript version 4.9.5 even though the option listed in the error is present
tsconfig.json file
{
  "extends"<EMAIL_ADDRESS>  "compilerOptions": {
    "target": "es5",
    "lib": ["dom", "dom.iterable", "esnext"],
    "moduleResolution": "node",
    "module": "Node16"
  },
  "include": ["src"]
}

VS Code version: Code 1.82.2 (abd2f3db4bdb28f9e95536dfa84d8479f1eb312d, 2023-09-14T05:55:25.390Z)
OS version: Windows_NT x64 10.0.22621
Modes:

System Info

Item
Value

CPUs
12th Gen Intel(R) Core(TM) i9-12900HK (20 x 2918)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
31.68GB (14.95GB free)

Process Argv
--crash-reporter-id e7b2c91f-00e9-4267-aba3-4f544436226b

Screen Reader
no

VM
40%

Extensions (1)

Extension
Author (truncated)
Version

ng-template
Ang
16.1.8

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
py29gd2263cf:30792227
vscaat:30438848
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
3biah626:30602489
f6dab269:30613381
a9j8j154:30646983
showlangstatbar:30737416
a2ce3375:30757347
pythonfmttext:30731395
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
pythonnosmt12:30797651
pythonidxpt:30805730
pythonnoceb:30805159
copilotsettingc:30839828
dsvsc013:30795093
dsvsc014:30804076
diffeditorv2:30821572
dsvsc015:30829745

Where do you see the error?
/gifPlease

Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette). Lastly, please attach this file via the GitHub web interface as emailed responses will strip files out from the issue.
Happy coding!

Seems like https://devblogs.microsoft.com/typescript/announcing-typescript-5-2/#module-and-moduleresolution-must-match-under-recent-node-js-settings
Did you switch your workspace TS version to 4.9.5?

I did switch it to 4.9.5 as the project i was using was implementing that version. Is there a setting that will allow that one to work, or will I need to use the newer version and override those values coming from the extended config. listed below for reference
{
  "$schema": "https://json.schemastore.org/tsconfig",
  "display": "Create React App",
  "_version": "2.0.0",

  "compilerOptions": {
    "lib": ["dom", "dom.iterable", "esnext"],
    "module": "esnext",
    "moduleResolution": "Bundler",
    "target": "es2015",

    "allowJs": true,
    "allowSyntheticDefaultImports": true,
    "esModuleInterop": true,
    "forceConsistentCasingInFileNames": true,
    "isolatedModules": true,
    "jsx": "react-jsx",
    "noEmit": true,
    "noFallthroughCasesInSwitch": true,
    "resolveJsonModule": true,
    "skipLibCheck": true,
    "strict": true
  }
}

After switching to TS 4.9.5 in the workspace, I don't see the error anymore

Can you share a small example project that demonstrates this issue

here is a link to a repo that has that project
https://github.com/AnomalyAces/sampleProject193616

Ok looks like that repo has:
    "moduleResolution": "Node16",
    "module": "Node16"

While the original example in the issue used this (which seems fine in 4.9.5):
   "moduleResolution": "node",
    "module": "Node16"

Assuming the repo is the correct one, it looks like there could have been a bug in TS 4.9.5 but it seems fixed in current TS versions. You can follow up in the TS repo but TS generally only supports the current stable release


Factors out build targets for individual QUICHE HTTP/2 libraries.

Signed-off-by: Biren Roy<EMAIL_ADDRESS>This will make it easier to add test targets for individual libraries in an upcoming pull request.
Tested via:
$ bazel build --config=remote @com_github_google_quiche//... test/common/http/http2/...
$ bazel test --config=remote test/common/http/http2/...
Commit Message: Factors out build targets for individual QUICHE HTTP/2 libraries.
Additional Description:
Risk Level: low
Testing: built QUICHE targets, Envoy HTTP/2 targets
Docs Changes: n/a
Release Notes: n/a
Platform Specific Features: n/a

/assign @adisuissa
/cc @diannahu

/assign @RyanTheOptimist

/assign @mattklein123

@mattklein123 for non-google review. (This should be a pretty trivial review)


Add C++14 test case

Includes some test code to verify that C++14 support works correctly and runs it as part of the test phase.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

This is ready for review.


Fix passing the logger through on PostgresConnectionSource

MySQL-kit does it. Looks like this was a typo.

Just following up. Any thoughts @gwynne or @0xTim ?

@joshuawright11 could you push an empty commit to retrigger CI?

@0xTim done. Looks like you need to approve running the workflow.

These changes are now available in 2.3.2


Shell for c2c encryption upstream issue

Placeholder to track work on cloudfoundry/diego-release#587

👋 Hello @pburkholder,
🎉 I get to deliver good news! Yes! We are working on this. I assigned @mariash to this issue to give you more information.

Good news from upstream!

We'll create a separate issue to track documentation and any other follow up that needs to be done.


[v2.0] Split Large Source norm file

Description
Refactor large norm file by splitting it into both vector_norm and matrix_nrom.
Reference: #19688
Checklist
Essentials

[ ] PR's title starts with a category (e.g. [BUGFIX], [MODEL], [TUTORIAL], [FEATURE], [DOC], etc)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage
[ ] Code is well-documented

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@mxnet-bot run ci [centos-gpu, unix-cpu, unix-gpu, windows-cpu]

@mxnet-bot run ci [edge, unix-gpu]

@mxnet-bot run ci [unix-cpu, unix-gpu]


Added docs example for xarray.Dataset.get()

Added example of xarray.Dataset.get method and alternative ds[var_list] syntax.

[ ] Closes #2884

For context: we didn't explicitly implement a .get() method on Dataset, we get it implemented for free because xarray.Dataset inherits from collections.abc.Mapping. So the only practical difference between .get() and [] on Dataset is the same as the difference for a general Python mapping: .get() returns a default value (which defaults to None) instead of raising KeyError.
I'm not sure it's particularly useful to show examples using .get() here, unless we want to show this difference in behavior if a key is not found.

Oh I see. It returns None if any of the keys is not found. That might indeed lead to confusion.
So should I just add an example with multiple variables using ds[['var1', 'var2']]?

So should I just add an example with multiple variables using ds[['var1', 'var2']]?

I think this is probably a better idea.
To be honest, I don't know if .get() if useful for anyone with a list -- it's implementation here was really an accident (based on how Mapping.get works) rather than an intentional choice.

I am still a bit puzzled over the ds[['x', 'temperature']] suggestion. Maybe I am not getting somthing, but x is a dimension and the output of ds[['x', 'temperature']]` is the same as ds[['temperature']]`. I think it would be clearer to add a third variable (maybe in the code block above) and then select two out of three data variables?

Yes, I think it would make more sense to add an example with another variable.

How about this one?

I missed that x is a coordinate.
Thanks @jbusecke


NetMHCpan: False peptide min/max boundaries

The internal boundaries of netmhcpan regarding peptide lengths are 8 - 56. NetMHCpan 4.1 always picks the most relevant Core of the peptide and does prediction on it. That is currently prohibited by the supported length that is inherited by the netmhcpan 2.8 interface.
Regarding NetMHCIIpan there seems to be only a lower limit to 9mers, I can go beyond 100 amino acids, which clearly does not make sense. So we could also say that we restrict it to peptides having max length of 56

I does not lead to wrong results, but class 1 peptides > 14 cannot be predicted by netmhcpan. Also netmhcIIpan is capped to peptides <20, which is a problem if we want to predict 21, 22mers. I think we don't need to change anything in parsing, it's just the boundaries of the peptide lengths.
What I wanted to say is that netmhc gets the most interesting core of the peptide and does the prediction on that:

I am still not sure I understand how the core is related to the problem with not having allowed all possible peptide lengths. The core is always the 9mer that is predicted to be in contact with the HLA molecule. I think the prediction is still done on the whole peptide though but would have to look up the details.

You are right, I checked prediction with the core preptide and the rank is different. So let's allow all possible peptide lengths then?

Sounds good to me, still worth to be changed. Thanks for bringing it up.


Shader starter

The photo below is what I would like to create with sceneform. There are 3 objects, the background, title text and explanation text.
When I understand correctly, shaders could be used to define the alpha fades. For the photo, I guess I could set through a parameter when the alpha fade should start. That could then probably be done in a fragment shader like this:
material.baseColor.a = position.x > materialParams.fadeWidth ? 1. : (position.x / materialParams.fadeWidth);
There is loads of tutorials available to do this with shaders for other platforms. But I don't see how I could apply this shaders for SceneForm.
Would appreciate hints to get this done.

Found it. uv is the value to use.


Breaking: add verbose(), controlled with verbose

in setup() and make debug() controlled with debug in setup.
This will allow writing apps that have a more granular level of verbosity:

quiet (warning-fatal)
normal (info-fatal),
verbose (verbose-fatal),
debug (debug-fatal = all).

I think that this is the way it should be done.
Without this feature I had to do an ugly hack in my GitLabForm app where I used logging.debug() for the "debug" verbosity level and cli_ui.debug() imported as verbose() as the "verbose" level - see https://github.com/gitlabform/gitlabform/commit/4610bd50782239635b49fffe384bc56d28ddaba4.

Wdyt, @dmerejkowsky?

If you are ok with such a change then I would add the appropriate docs and an upgrade guide, @dmerejkowsky.
I think that an image showing the levels and the verbosity levels would help. I prepared a draft of such an image:

On second thought I would like to apply some of the philosophy of a more user-friendly software development process taken from here https://gitlabform.github.io/gitlabform/#stability to python-cli-ui and do this:

introduce a new argument for setup(), f.e. verbosity that will be the sole new way of configuring, well, the verbosity. I would make it an enum accepting: debug, verbose, normal and quiet.
make the old arguments debug and quiet work the same way as they do now did but log a warning when they are used, stating that it is deprecated and that it will go away in the next major version of this library,

@gdubicki  : sorry for the long delay - do you still want to work on this ? - your plan to do it in a non-breaking way looks like a good idea to me

Hi, @dmerejkowsky! Yes, I might want to get back to this.
PS Can you please add my PyPI account (gdubicki) as a maintainer for this project in PyPI? I would like make a 0.18.0 release with what's currently in the main branch. :)

A gentle reminder, @dmerejkowsky :)


Dependency on vulnerable version of send package

Hello,
I'm using serve-static in my project and I noticed that it depends on the send package version 0.18.0, which has a known security vulnerability (see CVE-2024-43799](https://github.com/advisories/GHSA-m6fv-jmcg-4jfg)
The vulnerability is patched in send version 0.19.0. However, the latest version of serve-static still depends on a vulnerable version of send.
Could you please update the send dependency to a secure version to fix this vulnerability?
Thank you for your attention to this matter.
"serve-static": {
"version": "1.16.0",
"resolved": "https://registry.npmjs.org/serve-static/-/serve-static-1.16.0.tgz",
"integrity": "sha512-pDLK8zwl2eKaYrs8mrPZBJua4hMplRWJ1tIFksVC3FtBEBnl8dxgeHtsaMS8DhS9i4fLObaon6ABoc4/hQGdPA==",
"peer": true,
"dependencies": {
"encodeurl": "~1.0.2",
"escape-html": "~1.0.3",
"parseurl": "~1.3.3",
"send": "0.18.0"
}
}

This appears to be fixed as of<EMAIL_ADDRESS>

This appears to be fixed as of<EMAIL_ADDRESS>
yep ^ @DBAKANG-GIT feel free to close if you're happy

Thank you

When will this new version will be released as stable?


Fix DefaultDropHandler.TestCompatibleTypes for any IEditableCollectionView

In the DefaultDropHandler:
TestCompatibleTypes does not consider any IEditableCollectionView:
...
else
{
    return target is IList;
}

This causes CanAcceptData to always reject any targets that are IEditableCollectionView, however Drop is able to handle them.
I simply modified it to:
return target is IList || target is IEditableCollectionView;

I also added some minor cleanups for the same function.

@dauthleikr your changes have been merged, thanks for your contribution 👍


[Bug] Sort lines by subselection

Sort lines by subselection doesn't work
$a = [
  'name'=>2,
  'v2'=>3,
  'va'=>1,
];

Here it the code. I selected 2, 3, 1 in multiple selection mode -> invoked Sort lines by subselection and this just breaks my code.
Result:
$a = [
  'name'=>2,
  'v2'=>3,
  'v2'=>3,
];

P.S. Thanks for the great plugin ;)

Works fine for me. Could you make a video?

ok, i reproduced it now.

@krasa strange. Very strange. I can not reproduce it.
How do you reproduce it ? ))
Another issue.
P.S. You point letter S in Case *S*ensitive and *S*huffle options. Alt+S combination works for the last one.

It is broken when there are foldings somewhere before the selection, a bug in IntelliJ imho. I will work around it.

Fixed, you can update.


1.7 Support Please?

As per your statement from  https://www.spigotmc.org/resources/ezprotector.12663/update?update=111475 I am respectfully requesting a 1.7 compatible version of your plugin.

Hey,
You can download the latest eZProtector version for 1.7.x here:
https://mega.nz/#!JRA2BT6C!MFN6lyzjb98tN-Ps6Gcq4wpaF-WBILGEqaoUGthBfB0
Greetings,
Dan

Hey,
You can download the latest eZProtector version for 1.7.x here:
https://mega.nz/#!JRA2BT6C!MFN6lyzjb98tN-Ps6Gcq4wpaF-WBILGEqaoUGthBfB0
Greetings,
Dan

Also, the latest eZProtector version supports all 1.7-1.12 version 😛


#851 Merge branch 851 into main

The changes from #1240 were merged into branch apache:851 but not into main. This PR merges the changes from apache:851.

thanks @mvolikas


Day168

Resolves #348.

Pull Request Test Coverage Report for Build 649

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 647:
0.0%

Covered Lines:
5

Relevant Lines:
5

💛  - Coveralls


CSSClassApplier crash in Safari & Firefox with range encompassing custom NS elements

From<EMAIL_ADDRESS>on July 29, 2013 03:39:32
In my quest to find exceedingly strange ways to use CSSClassApplier, I discovered the following steps can produce a crash in Safari & Firefox on OSX (not Chrome though...). If step #3 isn't supported, feel free to let me know and I'll see what I can do to work around it. What steps will reproduce the problem? (See attached html file)

Create a text node within a div container
Highlight the region
Append new custom elements within the tail end of the region (Is this step a "user error" by me? Is Rangy expected to play nice if I'm doing this to the DOM behind it?)
Re-apply the highlight to entire div container again. The apply command will crash at this point with the following error in firefox:
[12:26:06.837] TypeError: className is undefined @ http://rangy.googlecode.com/svn/trunk/dev/uncompressed/rangy-cssclassapplier.js:56 What is the expected output? What do you see instead? Hopefully it wouldn't crash What version of the product are you using? On what operating system? Reproducible in current uncompressed output in trunk. Also reproducible against compiled source output as of r790 .

Workarounds:
One possible workaround is to add a null check on line 56, changing the content of "sortClassName" to:
function sortClassName(className) {
return className ? className.split(/\s+/).sort().join(" ") : "";
}
Original issue: http://code.google.com/p/rangy/issues/detail?id=178

Hi. I've made a change (not yet committed) that allows the class applier to work with elements with non-HTML namespaces, such as <svg> elements and elements with custom namespace elements. This changes the behaviour so that these elements are no longer ignored. Would this be a problem for you?

Your solution sounds preferable to me.
As you guessed, I simply took the easiest route to non-throwing. In my specific use-case, I was indifferent to whether the class was applied to the svg elements or not.
Thanks for your work!


sfcollector could use more precise scheduling

After each run sfcollector pauses for 60 seconds which means it runs every 60-something, rather than exactly every 60 seconds (although sfcollector is executed in the background, timestamps are generated in statsd, rather than based on times from SolidFire API).  The other problem is vsphere-graphite runs on its own schedule, and so on.
As a consequence, metrics for short time intervals (2-3 minutes) may not be aligned or accurate.
This could be improved with more precise scheduling.

SolidFire functions can be executed with async main() running async functions in ThreadPoolExecutor.  Executed 60 times, below sequence takes 0:02:05.170056 (2 minutes 5 seconds).
sfe.get_cluster_info().to_json()['clusterInfo']
sfe.get_cluster_info().to_json()['clusterInfo']
time.sleep(2)

Done asynchronously it's 0:02:00.104617, which is a reasonably small drift and a good improvement.
sfcollector calls a lot of functions every time and they run one after another, so drift is very obvious. Using sfcollector v0.7 with SolidFire Demo VM 12.3, run all collector functions 10 times, with to_graphite=False and 10s sleep between each run:

sfcollector v0.7 (1): 0:02:23.272932 (143.3s)
sfcollector v0.7 async with ThreadPoolExecutor (2): 0:01:40.082450 (100.1s)

Executed twice:

sync: 0:00:28.353602
async: 0:00:20.045300

This is just a single node VM cluster with 4 disks, 10-20 volumes, etc. Large clusters with hundreds of objects (volumes, nodes, disks) should benefit from async even more.
1 nohup ./solidfire_graphite_collector.py -u admin -p admin -s <IP_ADDRESS> > sync.log &
2 nohup ./solidfire_graphite_collector_async.py -u admin -p admin -s <IP_ADDRESS> > async.log &


asyncFilter and asyncMap now work in all circumstances, and are more efficient

Also: CircularBuffer can now contain a variable number of items. Application of new technique to async map is coming.

OK this is where it gets really complicated. There's a bug in what I have here, which is that sequencing is lost. If one mapper returns earlier, it can emit its item out of order.

Oh ok scratch what I said

I'm going to deal with that tomorrow though. Staying up til 2 last night working on this was bad idea >_<
I also think there is also likely to be enough overhead involved in all this that it will make sense to special case concurrency one to avoid all this logic

I'd like to understand better how the new buffer and async-map-parallel work. I am sure everything will be clearer with some extra test.
I have so underestimated the complexity of this! :man_facepalming:
Thanks for you efforts.

This should now be pretty much ready to go.

Yeah I had also underestimated how complex it would be, but I don't see any simpler way, and I've spent quite a bit of time thinking about it. The good news is that that means it's a really useful thing for iter-tools to provide. Easy to describe, but clearly quite tricky to implement.

Added some in-depth comments.
Also I forgot to add earlier that there's a bit of a potentially breaking change in cursor: since you're now getting the same cursor instance at every iteration, if you should manage to hold on to a cursor between iterations you must now create a copy of it (with [...cursor]) by hand.

The one outstanding issue is that this PR needs what async-buffer purports to offer. I think I need to either make use of the existing implementation or if I can't, I need to figure out what's wrong with it and how to make it usable

I'm not sure if we want to do this, but I think the change that would need to happen is that the async-buffer api would change: instead of it making a buffer for you, you would pass it a buffer. I like that, because as I've always said I don't see that function as being very useful if you can't get at the buffer, which I believe is why I couldn't use it in this case when I needed what it purports to provide. If you provide it the buffer you definitely have access to it yourself, and in this case it would allow me to pass a subclass of buffer with an overridden push method, like so:
class MappingBuffer extends CircularBuffer {
  push(sourceItem) {
    super.push(sourceItem.then(item => {
       // initiate parallel promise
    })
  }
}

asyncBuffer(new MappingBuffer(), iterable)

The thing is, we'd have to export our circular buffer class if we want to give users that power as well. I don't think it's such a bad idea  -- as we've found it's frequently a pretty useful construct, it is in fact an iterable, and if some of my other changes are accepted we'll be exposing instances of it directly to users anyway.

Let's assume that if that if we do change async-buffer we will do so in a separate PR. I'm ready to merge this.

@conartist6 let me review this before merging. Apologies if it is taking me a bit of time :-)

Realized I was only running the es2015 tests. Oversight when merging the jest diff. Fixed it here. I've configured jest to only run the es2018 tests in CI, where we are sure that node is v10. I anticipate es2018 only bugs will be pretty rare and we still will prevent them getting into our codebase without restricting development to only those with the newest node version.

And no worries. I understand that it's pretty tricky to review.

About the proposed changes to async-buffer. Let's keep them outside this thread. We can discuss them in another ticket

Super bowl time. Obligations of being an american you know. Normal coding
operations will return later
On Sun, Feb 3, 2019, 15:29 Maurizio Lupo<EMAIL_ADDRESS>wrote:

Something similar ?
const func = async (item) => {
const toInclude = await filterFunc(item)
return {item, toInclude}
}for await (const {item, toInclude} of asyncMap(func, iterable)) {
if (toInclude) yield item
}
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sithmel/iter-tools/pull/178#issuecomment-460099237,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAhAad7CCUYOqABm-84C2wrXorG3v3AAks5vJ3DWgaJpZM4ado08
.

I am available to help on this @conartist6. Is that ok if I create a new branch starting with this, and I propose some changes on that ?

In the mean time I merged master into this branch

I wish you would not do that. I'll undo it for now, but it really messes up my workflow when you merge branches into mine. I will rebase my work on master.

OK you were right of course that asyncFilter should just call asyncMap. The diff is updated.

I wish you would not do that. I'll undo it for now, but it really messes up my workflow when you merge branches into mine. I will rebase my work on master.

Sorry, I just wanted to be helpful :-D
@conartist6
In general I am quite happy about this. I have just a few minor things, that I'd like to change.
I can:

merge this and prepare a new PR with some changes
create a branch out of this with the changes
pointing to the changes here in the comments and let you implement them

I'm content for the branch to be merged, even if more changes are planned. Why don't you go ahead and do that, but out of curiosity what are you thinking?

out of curiosity what are you thinking?

Really minor things, you will see soon :-)


Is there any support to AKI-SPT 3.3.0 ?

Is there any support to AKI-SPT 3.3.0 ?

Yes, it is working.


force line through 0

Is there a way to force the linear regression through the origin point?

Have you find some way to force it to origin?

You can use the equation you receive when creating the regression then calculate a point from your x origin.


Can't write Byte or Byte array to client

Description
I have a problem in sending byte array over TCP
componentDidMount() {
    let client;
    client = TcpSocket.createConnection(
      {
        port: Number(24),
        host: '<IP_ADDRESS>',
        // localAddress: '<IP_ADDRESS>',
        // reuseAddress: true,
        // localPort: 20000,
        // interface: "wifi"
      },
      address => {
        this.updateChatter('opened client on ' + JSON.stringify(address));
        //client.write('[101]');
        var myarray = new Uint8Array([101]);
        var buf = Buffer.alloc(1, 101);
        client.write(buf);
      },
    );

I want to send 101 as byte over TCP but my code sends 'e' character and also sending myarray throws in the following error
](http://s7.picofile.com/file/8388794926/err.jpg)
What should I do?
| OS | Android 7  |
| react-native | 0.61.5   |
| react-native-tcp-socket  | ^3.2.6   |

@pouyagholami, could you upgrade to the latest version of the library and check if the issue still persists?

@pouyagholami, I have released a fix version (v.3.2.9) with a fix for the error when sending Uint8Array objects.

I want to send 101 as byte over TCP but my code sends 'e' character

Your client does not send the 'e' character, the TCP client sends a byte array ([101] in this case). However, when you call socket.on('data', (data) => {}), data is a Buffer object containing [101]. So, when you call its toString() method (directly or indirectly by concatenating it to a string), it turns the 101 byte array into the character 'e'.
I hope this fixes your problem. Feel free to reopen this issue if you need any help!


dosfstools: Add patch to fix fsck of boot partition

The boot partition contains some directory entries with bad flags
that were created by mtools. Fix fsck so it clears the flags rather
than destroying the system-connections directory.
Change-type: patch
Changelog-entry: Fix fsck of boot partition with dosfstools
Signed-off-by: Will Newton<EMAIL_ADDRESS>

@resin-jenkins retest this please

@resin-jenkins retest this please

@resin-jenkins retest this please

The patch file is missing the "Upstream status". Is it a backport?

@floion I've added an upstream-status tag. I've opened a PR upstream but had no response so far.

@willnewton can you paste the link to the ml where you submitted this? Maybe also reping them there?

AFAIK there is no mailing list, but the PR is here: https://github.com/dosfstools/dosfstools/pull/61

Thanks


[FR] - Validate CBOR TX Metadata in the CLI

Internal
Currently CLI cardano-cli shelley transaction build-raw is not validating limit on the size of strings in CBOR metadata files.
Example - JSON with string longer than 64 bytes - correct behavior
cardano-cli shelley transaction build-raw \
--tx-in 1a3f2a54067655fe9b7b4f116f4434f770d1f08b93f78a12d99712166bbd2caa#0 \
--tx-out $(cat ../keys/2/payment2.addr)+10000000000 \
--tx-out $(cat ../example/addresses/user1.addr)+90000000000 \
--ttl 267500 \
--fee 0 \
--metadata-json-file metadata.json \
--metadata-json-file metadata2_too_long_string.json \
--metadata-cbor-file metadata3.cbor \
--metadata-cbor-file metadata4.cbor \
--out-file tx001.raw

Error reading metadata at: "metadata.json" Error: JSON string is longer than 64 bytes

Example - CBOR with string longer than 64 bytes - no validation
cardano-cli shelley transaction build-raw \
--tx-in 1a3f2a54067655fe9b7b4f116f4434f770d1f08b93f78a12d99712166bbd2caa#0 \
--tx-out $(cat ../keys/2/payment2.addr)+10000000000 \
--tx-out $(cat ../example/addresses/user1.addr)+90000000000 \
--ttl 267500 \
--fee 0 \
--metadata-json-file metadata.json \
--metadata-json-file metadata2.json \
--metadata-cbor-file metadata3.cbor \
--metadata-cbor-file metadata4_too_long_string.cbor \
--out-file tx001.raw

No CBOR Error informing that string is longer than 64 bytes

The error will appear during TX submission instead:
cardano-cli shelley transaction submit --tx-file tx001.signed --testnet-magic 42

Error while submitting tx: Failed to submit Shelley transaction: ApplyTxError [LedgerFailure (UtxowFailure (UtxoFailure (MaxTxSizeUTxO 59630 16384)))]

Describe the feature you'd like
Add CBOR TX Metadata validation
Describe alternatives you've considered
N/A
Additional context / screenshots
Related to https://github.com/input-output-hk/cardano-node/pull/1406

Where can I find the tx metadata scheme?

@MarcelKlammer - https://hydra.iohk.io/build/3329433/download/1/delegation_design_spec.pdf - E Transaction Metadata, page 53  (repo: https://github.com/input-output-hk/cardano-ledger-specs)

@ArturWieczorek Thank you. What would an example json look like then? I tried some things, but got errors every time.

@MarcelKlammer
Example:
{
   "1": {
           "Name": "TX Metadata Tests",
           "Project": "Cardano-Node"
      },
   "2": {
          "ComplexValue": {
              "Nested": "True"
          }
      },
   "3": [{"CI":"Buildkite"}, {"Language":"Haskell"}]
}

@ArturWieczorek Very helpful, thank you.


Use Rack::Request#params instead of #[]

Looks like they're going to be deprecated in Rack 2.0 (https://github.com/rack/rack/pull/1069/files)

Coverage remained the same at 99.125% when pulling 5875575c24e8b76e1fed24eaea8831614fcad3e6 on frodsan:patch-1 into f9e73a63ec9790acb9d1b95f970041c8ead53596 on hyperoslo:master.

Oh, cool!


can/do we ignore all the doc files

can we exclude docs/locales since they're not much use on the device. I know we do this via the command COPY 01_nodoc /etc/dpkg/dpkg.cfg.d/ in other places I think.
contents of  01_nodoc
path-exclude /usr/share/doc/*
path-exclude /usr/share/man/*
path-exclude /usr/share/groff/*
path-exclude /usr/share/info/*
path-exclude /usr/share/lintian/*
path-exclude /usr/share/linda/*

path-exclude /usr/share/locale/*
path-include /usr/share/locale/en*

Fixed!


updated section on rarefaction/normalization with additional info

Now with 100% fewer stealth merges from master

Closing in favor of https://github.com/biocore/qiita/pull/2561


add Apple universal libraries build configuration.

Automatically determine toolchain location using xcrun.

no asm
only build static libraries
armv7 is deprecated for devices
i386 is deprecated for simulators

Examples
Build for macOS:
./Configure apple-universal-macosx enable-tls1_3 --prefix="$(pwd)/out/macosx" --libdir="$(pwd)/out/macosx/lib"
make clean
make -j
make install_sw

Build for macCatalyst:
./Configure apple-universal-maccatalyst enable-tls1_3 --prefix="$(pwd)/out/maccatalyst" --libdir="$(pwd)/out/maccatalyst/lib"
make clean
make -j
make install_sw

Build for iOS and simulator:
./Configure apple-universal-ios enable-tls1_3 --prefix="$(pwd)/out/ios" --libdir="$(pwd)/out/ios/lib"
make clean
make -j
make install_sw

./Configure apple-universal-iossim enable-tls1_3 --prefix="$(pwd)/out/iossim" --libdir="$(pwd)/out/iossim/lib"
make clean
make -j
make install_sw

Build for tvOS and simulator:
./Configure apple-universal-tvos enable-tls1_3 --prefix="$(pwd)/out/tvos" --libdir="$(pwd)/out/tvos/lib"
make clean
make -j
make install_sw

./Configure apple-universal-tvossim enable-tls1_3 --prefix="$(pwd)/out/tvossim" --libdir="$(pwd)/out/tvossim/lib"
make clean
make -j
make install_sw

Build for watchOS and simulator:
./Configure apple-universal-watchos enable-tls1_3 --prefix="$(pwd)/out/watchos" --libdir="$(pwd)/out/watchos/lib"
make clean
make -j
make install_sw

./Configure apple-universal-watchossim enable-tls1_3 --prefix="$(pwd)/out/watchossim" --libdir="$(pwd)/out/watchossim/lib"
make clean
make -j
make install_sw

Build for visionOS and simulator:
./Configure apple-universal-visionos enable-tls1_3 --prefix="$(pwd)/out/visionos" --libdir="$(pwd)/out/visionos/lib"
make clean
make -j
make install_sw

./Configure apple-universal-visionossim enable-tls1_3 --prefix="$(pwd)/out/visionossim" --libdir="$(pwd)/out/visionossim/lib"
make clean
make -j
make install_sw

CLA: trivial Added.

I am sorry but this change is not acceptable with CLA: trivial. Could you please submit a regular CLA?

This PR is in a state where it requires action by @openssl/otc but the last update was 30 days ago

This PR is in a state where it requires action by @openssl/otc but the last update was 61 days ago

This PR is in a state where it requires action by @openssl/otc but the last update was 92 days ago

This PR has the label 'hold: cla required' and is stale: it has not been updated in 30 days. Note that this PR may be automatically closed in the future if no CLA is provided.  For CLA help see https://www.openssl.org/policies/cla.html

This PR has the label 'hold: cla required' and is stale: it has not been updated in 61 days. Note that this PR may be automatically closed in the future if no CLA is provided.  For CLA help see https://www.openssl.org/policies/cla.html

This PR has been closed.  It was waiting for a CLA for 90 days.


CB-11558 Make windows plugin rm remove ProjectReference items

The issue was that we have been passing a relative path during JsprojManager.addProjectReference and an absolute path during JsprojManager.removeProjectReference so that regexp failed to find and remove it.
The tests were passing as they were also using absolute paths to the dummy plugin (it was not being added to the test project at all).
Initial idea was to use relative paths instead for project sharing: CB-10927 Framework references in plugin.xml file prevent Windows Universal projects from being used on other machines
Also updated the tests to use relative paths to the ProjectReferences.
Jira issue

[Current coverage][cc-pull] is 72.55%

Merging [#185][cc-pull] into [master][cc-base-branch] will increase coverage by 0.05%

@@             master       #185   diff @@
==========================================
  Files            14         14
  Lines          1920       1920
  Methods         356        356
  Messages          0          0
  Branches        386        386
==========================================
+ Hits           1392       1393     +1
+ Misses          528        527     -1
  Partials          0          0

Powered by Codecov. Last updated by [2c3bf8b...ee57003][cc-compare]
[cc-base-branch]: https://codecov.io/gh/apache/cordova-windows/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/apache/cordova-windows/compare/2c3bf8b7627d080af7ea51f6758fbe66be21e74b...ee570036bc8faddc7d63e2830144c3d007d8e904?src=pr
[cc-pull]: https://codecov.io/gh/apache/cordova-windows/pull/185?src=pr

LGTM, :ship: it


Claims missing from ClaimPrinciple when Authorizing a client by scope

This seems like it should be easy but I'm having a difficult time figuring this out.
We have a service using IdentityServer4.AccessTokenValidation.
Startup.cs
app.UseIdentityServerAuthentication(
    new IdentityServerAuthenticationOptions
    {
        Authority = "myIdentityServerUrl",
        RequireHttpsMetadata = false,
        ApiName = "myApi",
       ApiSecret = "myApiSecret"
    });

In that service, is an endpoint which needs to authorize based on the client's scope during a client credential flow.
MyController.cs
[HttpPut]
[Route("{myId}")]
public async Task<IActionResult> Put(string myId, [FromBody] MyObject myObj)
{
    var policy = new AuthorizationPolicyBuilder().RequireAuthenticatedUser().RequireClaim("scope", "foo").Build();
    var isAuthorized = await _authorizationService.AuthorizeAsync(User, policy);

    if (!isAuthorized)
    {
        return new ChallengeResult();
    }
     ...
}

Unfortunately, User (the ClaimsPrinciple) never has any claims. So, the authorization always fails.
I can see that the scope claim is available when I hit the introspection endpoint and it contains the scopes that I expect.
I can also see that the sub claim is available in the ClaimsPrinciple when I use a token obtained from an implicit grant flow. So, I know that some claims are being populated.
I've tried playing around with the several of the properties on the Client and ApiResource but I'm obviously missing something.
What do I need to do to have the scope claim added to the ClaimsPrinciple during a Client Crendentials flow?

Check the logs on the API app - It seems token validation fails in some scenarios.

@leastprivilege Thank you!
I looked at this again with fresh eyes this morning and found that my client credential test in Postman did not have "Bearer" in front of the access token. Once, I sent the correct authorization header, it worked as expected.
I knew it had to be something trivial.  I looked at it longer than I'd like to admit. I suspected my client configuration but it was even more trivial!


Fonts setup

Description
Adds the DS fonts.

@nhsz check the last commit, I removed the display value since the default is already swap. And removed the weight attr from the Inter font to make use of the variable font version of it (which is faster since we need to download only one file/font). The IBM font doesn't offer a variable font type so, in that case, we are forced to specify the weight.


[FutureRequest]Need a method to shutdown network gracefully

Currently, the network worker is a long loop future and cannot be closed gracefully.
Add a shutdown message to ServiceToWorkerMsg, and quit the future gracefully.

Can you explain why you want to shutdown the network?

Can you explain why you want to shutdown the network?

To do some tests or change some network config runtime.

You can not easily restart the network. If you restart the network it would require you to require almost everything else as well.

Please don't add a variant to ServiceToWorkerMsg. The API of sc-network returns a NetworkWorker that can be shut down without needing an intervention of the NetworkWorker itself. If this is done, this should be done in sc-service or wherever you're spawning the network for your testing.


Potential issue with serialized data for conv layers

I'm trying to convert a Flux model to TensorFlow, via onnx. On the tensorflow side the serialized data complains about the dimensions of the convolution layer, as described here https://github.com/onnx/onnx-tensorflow/issues/859#issuecomment-767014381
I'm not sure where the error originates, but this might be a ONNXmutable.jl issue.
The model is the exact same as described in #39

Thanks for the report! I'll look into it tonight.
In the meantime, see if you can get a second opinion from some other framework. ONNXmutable is tested against onnxruntime and in the test directory there is a helper function which might be useful. I'm not 100% this will work, but something like this:
# create model as in #39

julia> cd("test")

(ONNXmutable) pkg> activate .

julia> include("serialize/onnxruntime.jl")

julia> inpt = randn(Float32, 31,54,1);

julia> onnxout = onnxruntime_infer(model, inpt);

julia> onnxout == model(inpt) #Please return true :)

Thanks for the report! I'll look into it tonight.
In the meantime, see if you can get a second opinion from some other framework. ONNXmutable is tested against onnxruntime and in the test directory there is a helper function which might be useful. I'm not 100% this will work, but something like this:
# create model as in #39

julia> cd("test")

(ONNXmutable) pkg> activate .

julia> include("serialize/onnxruntime.jl")

julia> inpt = randn(Float32, 31,54,1);

julia> onnxout = onnxruntime_infer(model, inpt);

julia> onnxout == model(inpt) #Please return true :)

Oh, and after reading the comment in the linked tensorflow issue: Make sure you supply the input dimensions when saving the model. There is a chance that tensorflow checks that they are set and consistent and ONNXmutable can't infer them from a Chain (only from a CompGraph).
julia> onnx("model.onnx", model, (31,54,1))

Oh, and after reading the comment in the linked tensorflow issue: Make sure you supply the input dimensions when saving the model. There is a chance that tensorflow checks that they are set and consistent and ONNXmutable can't infer them from a Chain (only from a CompGraph).
julia> onnx("model.onnx", model, (31,54,1))

Thank you so much. The python package for TensorFlow conversion (onnx_tf) does indeed work when I add the input dimensions!

Thank you so much. The python package for TensorFlow conversion (onnx_tf) does indeed work when I add the input dimensions!

Great!
I keep this open as I think the serialized model is not compliant with the ONNX spec in case of missing input sizes. ONNX says that the shape info shall be missing, but ONNXmutable adds an empty shape info which should be interpreted as a scalar.
I'll also look into improving the shape inference for Chain. Since NaiveNASflux already knows the shapes of all Flux layers one could at least look at the first layer and see if it is something for which the shape is known.

Great!
I keep this open as I think the serialized model is not compliant with the ONNX spec in case of missing input sizes. ONNX says that the shape info shall be missing, but ONNXmutable adds an empty shape info which should be interpreted as a scalar.
I'll also look into improving the shape inference for Chain. Since NaiveNASflux already knows the shapes of all Flux layers one could at least look at the first layer and see if it is something for which the shape is known.

As per the above, exporting with unkown inputshapes (e.g. by omitting them) should now yeild a valid model. If you have the setup to test it easily with onnx_tf I'd appreciate a confirmation that I got it right this time around. :)
Better automatic shape inference for Chains is tracked in #43 and I'll add it as soon as I find the time to do so.

As per the above, exporting with unkown inputshapes (e.g. by omitting them) should now yeild a valid model. If you have the setup to test it easily with onnx_tf I'd appreciate a confirmation that I got it right this time around. :)
Better automatic shape inference for Chains is tracked in #43 and I'll add it as soon as I find the time to do so.

Sure, I will get to it in a couple of days.

Sure, I will get to it in a couple of days.

I just merged the improved shape inference for chains so I'm closing this.
To export a Chain with unkown shape, use missing as shapeinfo: onnx("model.onnx", model, missing)

I just merged the improved shape inference for chains so I'm closing this.
To export a Chain with unkown shape, use missing as shapeinfo: onnx("model.onnx", model, missing)

FWIW, I can confirm that onnxruntime can import and run predictions on a model created without specifying shape.

FWIW, I can confirm that onnxruntime can import and run predictions on a model created without specifying shape.


Update REQ-DCW-06 DICOMWeb STOW-RS

Description
Updates the requirements for REQ-DCW-06 DICOMWeb STOW-RS.
Status
Ready
Types of changes

[x] Non-breaking change (fix or new feature that would not break existing functionality).
[ ] Breaking change (fix or new feature that would cause existing functionality to change).
[ ] New tests added to cover the changes.
[ ] All tests passed locally.
[ ] Documentation comments included/updated.
[ ] User guide updated.
[ ] I have updated the changelog

The changes look good to me


Fix MS MARCO V2.1 repo experiments on segmented doc collection

Proposed fix to https://github.com/castorini/anserini/issues/2480#issuecomment-2085063194
The issue is that '#' may get interpreted as a comment; WSL and Mac might also different on how interpolation, escaping, etc. is handled with ProcessBuilder. This works on my Mac.

This works on both Linux and Mac, so merging in. We can get someone to check Windows via WSL later.


[Suggestion] Don't include bots in list of contributors

@aps120797 your creating is looking wonderful.
I was checking this issue it created https://github.com/aps120797/playground/issues/22 . In it the CONTRIBUTORS section lists the weekly-digest bot as a contributor. I think bots shouldn't be included in the list. Let me know what you think.

Nice catch! I have seen that and have that in my mind to remove it. 😄

I have removed bots and their activities to be published by weekly-digest .
I am closing this issue now. 😄


When TxEndedEvent comes after TxAbortedEvent, it would not be compensated?

I write a test in AlphaIntegrationTest like this,
  @Test
  public void compensateTxEndedEventAfterOtherTxAborted() {
    String sagaGlobalId = UUID.randomUUID().toString();
    String bookingApplicationLocalId = UUID.randomUUID().toString();
    String carServiceLocalId = UUID.randomUUID().toString();
    String hotelServiceLocalId = UUID.randomUUID().toString();

    asyncStub.onConnected(serviceConfig, compensateResponseObserver);

    blockingStub
            .onTxEvent(someGrpcEvent(SagaStartedEvent, sagaGlobalId, bookingApplicationLocalId));

    blockingStub.onTxEvent(someGrpcEvent(TxStartedEvent, sagaGlobalId, carServiceLocalId));
    blockingStub.onTxEvent(someGrpcEvent(TxAbortedEvent, sagaGlobalId, carServiceLocalId));

    blockingStub.onTxEvent(someGrpcEvent(TxStartedEvent, sagaGlobalId, hotelServiceLocalId));
    blockingStub.onTxEvent(someGrpcEvent(TxEndedEvent, sagaGlobalId, hotelServiceLocalId));

    await().atMost(30, SECONDS).until(() -> receivedCommands.size() > 0); //fail here
    assertThat(receivedCommands.size(), is(1));

    GrpcCompensateCommand command = receivedCommands.poll();
    assertThat(command.getGlobalTxId(), is(sagaGlobalId));
    assertThat(command.getLocalTxId(), is(hotelServiceLocalId));
    assertThat(command.getParentTxId(), is(parentTxId));
    assertThat(command.getCompensationMethod(), is(compensationMethod));
    assertThat(command.getPayloads().toByteArray(), is(payload.getBytes()));
  }

is it a valid testcase？

If you have receive a TxAbortEvent, the next TxStartedEvent with same globalTxId will be rejected.
Look at the code in class TxConsistentService.
`
public boolean handle(TxEvent event) {

if (types.contains(event.type()) && isGlobalTxAborted(event)) {

  LOG.info("Transaction event {} rejected, because its parent with globalTxId {} was already aborted",
      event.type(), event.globalTxId());

  return false;

}

eventRepository.save(event);

return true;

 }

`

@HuZheting
but when we have two or more omegas do the job simultaneously, it may occurs.

As @HuZheting said, in current Alpha implementation it rejects the first start event once the abort event is received.
We may need to fix this corn case by updating the Alpha implementation.

@HuZheting @WillemJiang

@HuZheting @WillemJiang
thanks for your reply.
I think I have a wrong testcase.


Terraform Enterprise Support

There should be a way to configure the Terraform extension to use TE instead of only connecting directly to the target environment (AWS for my case). Currently a file must be manually created under the agent account roaming profile to redirect and ignore the TFS connection configuration.

@StephenRSkinner  Can you please ping your skypeId on<EMAIL_ADDRESS>So we can have a quick call to understand it better.

I'm not sure what you're asking for, but maybe I can explain better.
Currently, you can configure the Terraform AWS service connection in TFS 2018 on-premise. I'm asking for support to configure a Terraform Enterprise service connection as well, so we can pick that as an option. Currently, to execute tasks on Terraform Enterprise, a file has to be put into C:\Users{ServiceAccount}\AppData\Roaming folder on every server running the TFS agent where terraform scripts will be executed. This is not a practical approach. The task needs to support calling Terraform Enterprise instead as an option.

Not supported now .We are also encouraging for contribution ..Even you can raise PR and assign to me


create-testnet-data: --testnet-magic should override the template's value

Description
When calling create-testnet-data and specifying both --spec-shelley and --testnet-magic, the value of the latter is ignored (which is surprising to users, as reported to me by @andreabedini):
→ rm out128 -Rf; cabal run cardano-cli -- conway genesis create-testnet-data --spec-shelley genesis.shelley.json --out-dir out128 --testnet-magic 128 # genesis.shelley.json specifies 42 as the magic
→ cat out128/genesis.json | jq .networkMagic
42

whereas if you don't specify a shelley template, --testnet-magic is honored:
→ rm out128 -Rf; cabal run cardano-cli -- conway genesis create-testnet-data --out-dir out128 --testnet-magic 128
→ cat out128/genesis.json | jq .networkMagic
128

The problem lies here: https://github.com/IntersectMBO/cardano-cli/blob/3b70e39299b1279c690ec11cb5aec6c84e13eadc/cardano-cli/src/Cardano/CLI/EraBased/Run/CreateTestnetData.hs#L207
      Just shelleyPath ->
        newExceptT $ readAndDecodeShelleyGenesis shelleyPath
      Nothing -> do
        -- No template given: a default file is created
        pure $ shelleyGenesisDefaults { sgNetworkMagic = unNetworkMagic (toNetworkMagic networkId) }

where the networkId (coming from the --testnet-magic flag) is only applied in the no --spec-shelley case.
Possible additional work
To be tested if create-staked suffer of the same defect.

@CarlosLopezDeLara> assigning you, because it's better to do this one before https://github.com/IntersectMBO/cardano-cli/issues/548 (which we discussed today).


embargo for datasets

Describe the improvement
Can embargo date, date type (of the embargo date) and access level after embargo by added for datasets, as is done for publications?
This info is most probably not available in the DataCite metadata and will have to be added manually by the submitter.
This is needed to decide on which datasets to provide to FRIS at a certain point in time.

is this required by fris or just recommended? we'll ad it to the next milestone if not required

it is required by FRIS.

Added the fields in 3478ad506ba08e35e0b73e710b8992c40045e8ce.
@sdebodt can you tell me what the semantics should be? e.g. an after embargo access level can only be chosen if access level is embargoed, ...

If conditional is possible, then only show fields "Embargo period" and "Access level after embargo period" when "Access level" = Embargoed access.
Access level after embargo can be "Open access" and "Restricted access".

Implemented a conditional.

Default state: "Period" and "Access level" are disabled and empty if the field value isn't "Embargo access".
Selecting "Embargo access" unlocks the fields and allows the user to input values (date, access level).
Selecting any other value (e.g. open access) will disable the fields again.

At no point are any selected values in the fields "Embargo access" or "Period" cleared or removed if any other values ("open access", "restricted access", "closed access") are selected. This caters to the principle of "least surprise": the idea to not surprise users with unexpected behavior.
However, this means that a record can be set to e.g. "restricted access" while the fields "Period" / "Access level" are still set to the values which only carry meaning in an "embargo access" context. If this seems to too confusing, I can change the logic to automatically reset those fields if "embargo access" is changed to another value.

Closing this for now.

Embargo period and future access level are grey but can be edited independent of the access level that is chosen.

I see the same issue. Apparently, I was trying to fight with how browsers process / submit form elements which are set to "disabled".  I've fixed this and changed the behavior somewhat since the clearing the "Period" and "Access level" fields manually when "Embargo access" is selected was unwieldy.

Default state: "Period" and "Access level" are disabled and empty if the field value isn't "Embargo access".
Selecting "Embargo access" unlocks the fields and allows the user to input values (date, access level).
Selecting any other value (e.g. open access) will disable the fields again.
The values of  the "Period" and "Access level" fields are cleared.

perfect!


Initially styling through modules not applied on 8.1.0

Bug report
Describe the bug
Modules (e.g react-grid-system) with styling are not initially loaded when building the production build. With react-grid-system if you resize the window to the mobile break-point it resolves the issue.
I was not sure where to post this issue since it works fine in next (dev)  and on 8.0.3.
Only seems to happen on the build.
To Reproduce

Execute next build
Inspect styling
Execute next
Inspect styling

Expected behavior
Initial styling to be applied.
System information

OS: macOS
Browser (if applies): Chrome
Version of Next.js: 8.1.0

Additional context
next on 8.1.0 doesn't seem to have the problem.
8.0.3 seems unaffected by this issue.
No custom .babelrc and no custom nextjs config.

You can check how it's done in SSR example. You need to provide an initial size of the screen. If still a problem please comment it again.


[Question]modify the initial config

:question: Question

Hi,
We had a question about the config file.
How should I modify the initial epoch batch learnrate and other parameters during training.
which file
Thanks!

Hi @GarryJAY502 ,
If the config.yaml you can find :
defaults:
    - _self_
    - train: retinaunet_hnm_v002

The configuration works by inheriting configuration from retinaunet_hnm_v002.yaml in the train folder. The same way, you can find the configurations retinaunet_hnm_v002.yaml is inheriting from other config files. The trainer-specific configuration is in the trainer_cfg folder, where you can update the learning rate, number of epochs etc.
You can also update the parameters through the command line itself. For example, to update the warm_iterations to 5000 and initial_lr to 0.001, you have to pass -o trainer_cfg.warm_iterations=5000 trainer_cfg.initial_lr=0.001. This way you can update other parameters as well.
Best,
Partha

你好@GarryJAY502， 如果config.yaml您能找到：
defaults:
    - _self_
    - train: retinaunet_hnm_v002

配置通过从文件夹retinaunet_hnm_v002.yaml中继承配置来工作train。同样，您可以发现配置retinaunet_hnm_v002.yaml是从其他配置文件继承的。训练器特定的配置位于trainer_cfg文件夹中，您可以在其中更新学习率、时期数等。
您还可以通过命令行本身更新参数。例如，要将更新warm_iterations为 5000 和initial_lr0.001，您必须传递-o trainer_cfg.warm_iterations=5000 trainer_cfg.initial_lr=0.001。这样您也可以更新其他参数。
最好的， 帕塔

It works，thanks ,Partha


Use postcss-load-config to load plugins

We have to keep consistent behaviour of the both plugins in tandem with https://github.com/lttb/babel-plugin-prejss
It would be great to use https://github.com/michael-ciniawsky/postcss-load-config instead of hard-coded plugins list.
By using this config file we can load and configure all required PostCSS plugins for the project on both sides.

Did it: https://github.com/axept/jss-from-postcss/commit/3ad2af53306d9f6e08ce62fdf07e14e664f46b2e#diff-826cb2fa2d203e19886e359a6722c517


Integrating pytest framework for drift tests with ods-ci

This PR integrates the drift tests in this repo https://github.com/trustyai-explainability/trustyai-tests to run with ods-ci.
The logs are written in a log folder test-output/pytest-logs/drift_test.txt

Verified here: https://opendatascience-jenkins/job/rhods/job/rhods-ci-pr-test/3230/console


acatangiu: retain rank 2 - 2024 Q3

Dear Fellows, please find my rank II retention letter: rendered version here.

You must be eligible for promotion right?

From a formality point of view: not yet: https://collectives.subsquare.io/fellowship/core - still need to serve 2 more months and 17 days at current rank before promotion is allowed (by code/implementation).


Kenney Asteroids. Implement Local Multiplayer

Max Players: 4
Local multiplayer can be done with one keyboard and 3 gamepads or 4 gamepads.

[ ] Add main menu item for multiplayer game
[ ] Add multiplayer config screens (with background) with four slots: the first player hit keyboard will play with keyboard others will need to hit gamepads (like with Broforce game)
[ ] Each player randomly gets its skin on the selection screen
[ ] When the first player was added to the config screen 5 seconds count down starts before game start
[ ] All players start in the middle of the game screen
[ ] Introduce general life pull for all players
[ ] Introduce general score not individual
[ ] In case of victory and high score add leaderboards one item to the general leader board but with mark that it was team of 4 or 3 or 2 etc.
[ ] Player after death return back immediately to the game if life pool has at least one life
[ ] If couple players dead and life pool regains with extra life then the first died player comes back to the game

Add icons for the keyboard/pad when player joins
Add name like player1, player 2, player 3 and player 4 when player joins
Add Leaderboards screens per 1 or 2 or 3 or 4 players
Add local multiplayer settings like friendly fire, friendly collision


Remove Chrome dependency in cyberchef.vm thank to new changes

Details
I think with the changes in https://github.com/mandiant/VM-Packages/pull/1016 we could now remove  the Chrome dependency in Cyberchef and the code to open it with chrome and set the icon (simplifying the installer code). I think we would keep the current behavior if both cyberchef.vm and googlechrome.vm are installed and remove the chrome dependency would allow to have a different browser as default (and to open cyberchef) if only cyberchef.vm is installed. This would need to add googlechrome.vm explicitly in flare-vm.
@emtuls what do you think?

VM-Set-Open-With-Association $exePath ".html" changes the icon but not the default icon, right? I think this is confusing, we should change the icon of html + default browser or remove the icon association. Let's discuss in https://github.com/mandiant/VM-Packages/issues/822 if we can change the default browser.

I may have a working solution for this. 😊 I still need to test how the new shortcut would work if chrome was not installed, but at least for the chrome case...After using VM-Set-Open-With-Association $exePath ".html", we just need to create the following registry key and then restart explorer.exe:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Explorer]
“NoNewAppAlert”=dword:00000001

NOTE: This does not make chrome the default browser still, which also makes the popup asking to make chrome the default browser still appear. I can look into seeing if I can bypass that as well, without actually setting the default browser, but it may not be possible.

Because of the changes in https://github.com/mandiant/VM-Packages/pull/1148, we can't remove the dependency


cmd.run with pipes will not work

In https://github.com/mariodpros/ufw-formula/blob/master/_modules/ufw.py#L6 cmd.run is used with a command containing pipes.
There is a warning about this in the docs:

This means that any shell-specific functionality such as 'echo' or the use of pipes, redirection or &&,  should either be migrated to cmd.shell or have the python_shell=True flag set here.

@ralphvanetten thanks for the bug report.