WQRM Risk Forecast Services

When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)
If this is your first time submitting to GitHub and you need some help, please sign up for this session.

[X ] I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
[X ] I attest that the connector works and I verified by deploying and testing all the operations.
[X ] I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
[X ] I attest that I have added response schemas to my actions, unless the response schema is dynamic.
[X ] I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
[X ] If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

[ ] I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
[ ] Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
[ ] Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
[ ] If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

@microsoft-github-policy-service agree company="WQRM"

Changes have been made and pushed to WQRM-Previous-Commit.
Chuck0007

From: Amjed Ayoub @.>
Sent: Wednesday, January 4, 2023 5:00 PM
To: microsoft/PowerPlatformConnectors @.>
Cc: Chuck Qi @.>; Mention @.>
Subject: Re: [microsoft/PowerPlatformConnectors] WQRM Risk Forecast Services (PR #2267)
@Amjed-Ayoub requested changes on this pull request.

In certified-connectors/WQRM Risk Forecast Services/apiProperties.jsonhttps://github.com/microsoft/PowerPlatformConnectors/pull/2267#discussion_r1062004507:

   "type": "securestring",

   "uiDefinition": {

     "displayName": "API Key",

     "description": "The API Key for this api",

     "tooltip": "Provide your API Key",

     "constraints": {

       "tabIndex": 2,

       "clearText": false,

       "required": "true"

     }

   }

 }

},
"iconBrandColor": "#3f48cc",
"capabilities": [],
"publisher": "Western QRM"

@Chuck0007https://github.com/Chuck0007 please add the stackOnwer property
"stackOwner": "Name of the owner of the service or product."
In your case should be "stackOwner": "Western QRM"

In certified-connectors/WQRM Risk Forecast Services/apiDefinition.swagger.jsonhttps://github.com/microsoft/PowerPlatformConnectors/pull/2267#discussion_r1062005444:

},

"x-ms-connector-metadata": [
{

 "propertyName": "Website",

 "propertyValue": "https://www.westernqrm.com/"

},
{

 "propertyName": "Privacy policy",

 "propertyValue": "https://www.westernqrm.com/privacy-policy"

},
{

 "propertyName": "Categories",

 "propertyValue": "Business Intelligence"

}
],
"host": "apps.powerapps.com",

@Chuck0007https://github.com/Chuck0007 the host URL should be a valid API host URL in production mode. can you please clarify why you are using powerapps?

In certified-connectors/WQRM Risk Forecast Services/apiDefinition.swagger.jsonhttps://github.com/microsoft/PowerPlatformConnectors/pull/2267#discussion_r1062006421:

 "propertyValue": "Business Intelligence"

}
],
"host": "apps.powerapps.com",
"basePath": "/",
"schemes": [
"https"
],
"consumes": [
"application/json"
],
"produces": [],
"paths": {
"/play/371c4dca-f7af-48b7-8dfa-cd6864969ba5": {

 "post": {

   "responses": {

@Chuck0007https://github.com/Chuck0007 it is not allowed to have a default response only. Please define a proper response. please see herehttps://learn.microsoft.com/en-us/connectors/custom-connectors/coding-standards#responses.

In certified-connectors/WQRM Risk Forecast Services/apiDefinition.swagger.jsonhttps://github.com/microsoft/PowerPlatformConnectors/pull/2267#discussion_r1062006526:

             "description": "CompanyName"

           },

           "Email": {

             "type": "string",

             "description": "Email"

           }

         }

       }

     }

   ]

 }

},
"/play/e5f00dbd-dc28-4b35-8550-1901efa36af7": {

 "post": {

   "responses": {

     "default": {

@Chuck0007https://github.com/Chuck0007 it is not allowed to have a default response only. Please define a proper response. please see herehttps://learn.microsoft.com/en-us/connectors/custom-connectors/coding-standards#responses.

In certified-connectors/WQRM Risk Forecast Services/apiDefinition.swagger.jsonhttps://github.com/microsoft/PowerPlatformConnectors/pull/2267#discussion_r1062006552:

             "description": "CompanyName"

           },

           "Email": {

             "type": "string",

             "description": "Email"

           }

         }

       }

     }

   ]

 }

},
"/play/158ed27b-9e89-45d2-a216-617d0b2d4355": {

 "post": {

   "responses": {

     "default": {

@Chuck0007https://github.com/Chuck0007 it is not allowed to have a default response only. Please define a proper response. please see herehttps://learn.microsoft.com/en-us/connectors/custom-connectors/coding-standards#responses.

In certified-connectors/WQRM Risk Forecast Services/apiDefinition.swagger.jsonhttps://github.com/microsoft/PowerPlatformConnectors/pull/2267#discussion_r1062006569:

             "description": "CompanyName"

           },

           "Email": {

             "type": "string",

             "description": "Email"

           }

         }

       }

     }

   ]

 }

},
"/play/b60262a8-7cf2-4526-8e78-c7fc7bd21ae9": {

 "post": {

   "responses": {

     "default": {

@Chuck0007https://github.com/Chuck0007 it is not allowed to have a default response only. Please define a proper response. please see herehttps://learn.microsoft.com/en-us/connectors/custom-connectors/coding-standards#responses.

In certified-connectors/WQRM Risk Forecast Services/apiDefinition.swagger.jsonhttps://github.com/microsoft/PowerPlatformConnectors/pull/2267#discussion_r1062006779:

"host": "apps.powerapps.com",

"basePath": "/",
"schemes": [
"https"
],
"consumes": [
"application/json"
],
"produces": [],
"paths": {
"/play/371c4dca-f7af-48b7-8dfa-cd6864969ba5": {

 "post": {

   "responses": {

     "default": {

       "description": "default",

       "schema": {}

@Chuck0007https://github.com/Chuck0007 empty schema is not allowed. please remove or define a proper schema.

In certified-connectors/WQRM Risk Forecast Services/apiDefinition.swagger.jsonhttps://github.com/microsoft/PowerPlatformConnectors/pull/2267#discussion_r1062006850:

           "Email": {

             "type": "string",

             "description": "Email"

           }

         }

       }

     }

   ]

 }

},
"/play/e5f00dbd-dc28-4b35-8550-1901efa36af7": {

 "post": {

   "responses": {

     "default": {

       "description": "default",

       "schema": {}

@Chuck0007https://github.com/Chuck0007 empty schema is not allowed. please remove or define a proper schema.

In certified-connectors/WQRM Risk Forecast Services/apiDefinition.swagger.jsonhttps://github.com/microsoft/PowerPlatformConnectors/pull/2267#discussion_r1062006908:

           "Email": {

             "type": "string",

             "description": "Email"

           }

         }

       }

     }

   ]

 }

},
"/play/158ed27b-9e89-45d2-a216-617d0b2d4355": {

 "post": {

   "responses": {

     "default": {

       "description": "default",

       "schema": {}

@Chuck0007https://github.com/Chuck0007 empty schema is not allowed. please remove or define a proper schema.

In certified-connectors/WQRM Risk Forecast Services/apiDefinition.swagger.jsonhttps://github.com/microsoft/PowerPlatformConnectors/pull/2267#discussion_r1062006948:

           "Email": {

             "type": "string",

             "description": "Email"

           }

         }

       }

     }

   ]

 }

},
"/play/b60262a8-7cf2-4526-8e78-c7fc7bd21ae9": {

 "post": {

   "responses": {

     "default": {

       "description": "default",

       "schema": {}

@Chuck0007https://github.com/Chuck0007 empty schema is not allowed. please remove or define a proper schema.

In certified-connectors/WQRM Risk Forecast Services/apiDefinition.swagger.jsonhttps://github.com/microsoft/PowerPlatformConnectors/pull/2267#discussion_r1062005699:

},

"x-ms-connector-metadata": [
{

 "propertyName": "Website",

 "propertyValue": "https://www.westernqrm.com/"

},
{

 "propertyName": "Privacy policy",

 "propertyValue": "https://www.westernqrm.com/privacy-policy"

},
{

 "propertyName": "Categories",

 "propertyValue": "Business Intelligence"

}
],
"host": "apps.powerapps.com",

we don't allow URLs in staging or testing mode.
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/PowerPlatformConnectors/pull/2267#pullrequestreview-1236660904, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A36I5T63TMGOBRCRK6SX5ALWQYMMLANCNFSM6AAAAAATRHRMKU.
You are receiving this because you were mentioned.Message ID: @.***>

@Chuck0007 I don't think you pushed your changed correctly. I don't see them on my end. Please let me know if you need help

Amjed,
I do need your help to do it correctly.. let me know what I need to do. Thank you so much.
Chuck

From: Amjed Ayoub @.>
Sent: Wednesday, January 11, 2023 1:15 PM
To: microsoft/PowerPlatformConnectors @.>
Cc: Chuck Qi @.>; Mention @.>
Subject: Re: [microsoft/PowerPlatformConnectors] WQRM Risk Forecast Services (PR #2267)
@Chuck0007https://github.com/Chuck0007 I don't think you pushed your changed correctly. I don't see them on my end. Please let me know if you need help
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/PowerPlatformConnectors/pull/2267#issuecomment-1379492653, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A36I5TZKDWIG2MFSCRJXDC3WR4PGVANCNFSM6AAAAAATRHRMKU.
You are receiving this because you were mentioned.Message ID: @.***>

Hello @Chuck0007,
I hope you are doing well.
I am following up with you to see how things are going with preparing your connector.
Please let us know if you have any questions.
Thank you.

Amjed,
After our meeting, I tested my connector using the Host URL: https://apps.powerapps.com/play. It worked fine.
However, it may take much longer time to develop and test my own “Host URL”. We need external help on this issue. Currently, we are working on the budget and resources to meet this requirement. It would be appreciated if you have any suggestions. Thank you very much for your help.
Chuck

From: Amjed Ayoub @.>
Sent: Friday, January 27, 2023 1:56 PM
To: microsoft/PowerPlatformConnectors @.>
Cc: Chuck Qi @.>; Mention @.>
Subject: Re: [microsoft/PowerPlatformConnectors] WQRM Risk Forecast Services (PR #2267)
Hello @Chuck0007https://github.com/Chuck0007,
I hope you are doing well.
I am following up with you to see how things are going with preparing your connector.
Please let us know if you have any questions.
Thank you.
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/PowerPlatformConnectors/pull/2267#issuecomment-1407115638, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A36I5TZA6GFB7QMMWC65AALWUQ77JANCNFSM6AAAAAATRHRMKU.
You are receiving this because you were mentioned.Message ID: @.***>

Amjed, After our meeting, I tested my connector using the Host URL: https://apps.powerapps.com/play. It worked fine. However, it may take much longer time to develop and test my own “Host URL”. We need external help on this issue. Currently, we are working on the budget and resources to meet this requirement. It would be appreciated if you have any suggestions. Thank you very much for your help. Chuck
…
________________________________ From: Amjed Ayoub @.> Sent: Friday, January 27, 2023 1:56 PM To: microsoft/PowerPlatformConnectors @.> Cc: Chuck Qi @.>; Mention @.> Subject: Re: [microsoft/PowerPlatformConnectors] WQRM Risk Forecast Services (PR #2267) Hello @Chuck0007https://github.com/Chuck0007, I hope you are doing well. I am following up with you to see how things are going with preparing your connector. Please let us know if you have any questions. Thank you. — Reply to this email directly, view it on GitHub<#2267 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A36I5TZA6GFB7QMMWC65AALWUQ77JANCNFSM6AAAAAATRHRMKU. You are receiving this because you were mentioned.Message ID: @.***>

Thank you so much @Chuck0007 for confirming. Yes we will proceed forward with it as is.

Hello @Chuck0007,
I hope you are doing well.
Congratulations, your pull request is approved and merged. Please submit the files to ISV Studio or update your submission using your latest commit ID, please allow us up to 1-2 weeks to review your submission, and our Engineers will notify you in the “Activity Control” area in ISV Studio. Please make sure that the icon meets all the requirements, that it’s size is 230x230, icon background is not white or transparent and it matches the iconBrandColor property in apiProperties.json file.
After making the submission in ISV Studio, please attach an intro.md file in the activity control section. This file is required and it's different from readme.md. You can find an example of intro.md file on this page at step 6.
Please Create an environment in the Preview region. You will use this environment later to test your connector after Microsoft is done with the functional verification for your connector.
We expect all tests to be completed within 1-2 weeks.
If your connector passes all tests, the deployment process begins, and it typically takes up to 3 to 4 weeks to deploy your connector to all of our regions.
Please let me know if you have any questions or run into any problems while creating or updating your submission.
Thank you very much for working with us.

Amjed,
I am trying to submit the file to ISV Studio and running into a problem:
I couldn't find correct "Full commit ID".
I tried two different ones from GitHub. Both were failed with following message:
...//apiDefinition.swagger.json?ref=... was not found.
Please let me know how find correct "Full commit ID". Thank you for your help.
Chuck

From: Amjed Ayoub @.>
Sent: Monday, January 30, 2023 12:38 PM
To: microsoft/PowerPlatformConnectors @.>
Cc: Chuck Qi @.>; Mention @.>
Subject: Re: [microsoft/PowerPlatformConnectors] WQRM Risk Forecast Services (PR #2267)
Hello @Chuck0007https://github.com/Chuck0007,
I hope you are doing well.
Congratulations, your pull request is approved and merged. Please submit the files to ISV Studiohttps://docs.microsoft.com/en-us/connectors/custom-connectors/submit-for-certification#submit-to-isv-studio or update your submissionhttps://docs.microsoft.com/en-us/connectors/custom-connectors/certification-updates using your latest commit ID, please allow us up to 1-2 weeks to review your submission, and our Engineers will notify you in the “Activity Control” area in ISV Studio. Please make sure that the icon meets all the requirementshttps://docs.microsoft.com/en-us/connectors/custom-connectors/certification-submission#design-an-icon-for-your-connector, that it’s size is 230x230, icon background is not white or transparent and it matches the iconBrandColor property in apiProperties.json file.
After making the submission in ISV Studio, please attach an intro.md file in the activity control section. This file is required and it's different from readme.md. You can find an example of intro.md file on this pagehttps://docs.microsoft.com/en-us/connectors/custom-connectors/submit-for-certification#submit-to-isv-studio at step 6.
Please Create an environment in the Preview regionhttps://docs.microsoft.com/en-us/connectors/custom-connectors/certification-testing#create-an-environment-in-the-preview-region. You will use this environment later to test your connectorhttps://docs.microsoft.com/en-us/connectors/custom-connectors/certification-testing#test-your-connector after Microsoft is done with the functional verification for your connector.
We expect all tests to be completed within 1-2 weeks.
If your connector passes all tests, the deployment process begins, and it typically takes up to 3 to 4 weeks to deploy your connector to all of our regions.
Please let me know if you have any questions or run into any problems while creating or updating your submission.
Thank you very much for working with us.
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/PowerPlatformConnectors/pull/2267#issuecomment-1409301241, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A36I5TYJHPW7YWNZXHDDL3LWVARFJANCNFSM6AAAAAATRHRMKU.
You are receiving this because you were mentioned.Message ID: @.***>

never mind, I successfully submitted it to ISV Studio!
Chuck

From: Amjed Ayoub @.>
Sent: Monday, January 30, 2023 12:38 PM
To: microsoft/PowerPlatformConnectors @.>
Cc: Chuck Qi @.>; Mention @.>
Subject: Re: [microsoft/PowerPlatformConnectors] WQRM Risk Forecast Services (PR #2267)
Merged #2267https://github.com/microsoft/PowerPlatformConnectors/pull/2267 into dev.
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/PowerPlatformConnectors/pull/2267#event-8392302938, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A36I5T7MM7ROR5HZ6T5VEXLWVARFXANCNFSM6AAAAAATRHRMKU.
You are receiving this because you were mentioned.Message ID: @.***>


Sort photos in chronological order

Hi,
your software looks nice, but I missed a function to sort all photos in chronological order.
Thank you

If it is planned why is the issue closed? The issue should remain opened until such feature is implemented!

You're right

@heikobornholdt Does Lychee have such a feature yet? I can't find anything in the UI to change the sorting.

@heikobornholdt You can close this issue again :-)

Yes, it's implemented ;)

:smile:


Typo in main.py line 119

There was a typo - "spnoken" instead of "spoken"

I signed it!

Thanks, will continue the review on #17


docker: 20.10.15 -> 20.10.16

https://docs.docker.com/engine/release-notes/#201016
https://github.com/docker/cli/releases/tag/v20.10.16
https://github.com/moby/moby/releases/tag/v20.10.16

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

The 21.11 backport won't work, which is subpar. Docker also needs bumping in 21.11 to build with go 1.17, and I honestly don't have the will to make it happen right now.


Stop validation process if a rule return false, in checkAsync

I do not know if this is doable currently. I could not find any doc for this. I want the validator to stop immediately when a rule for an attribute fails. It seems the validator continues to execute all the rules for that attribute. This is happening only when using checkAsync.
Example:
const Validator = require('validatorjs');

Validator.registerAsync(
    'unique',
    (value, attribute, req, passes) => {
        console.log('unique called');
        // Pseudo code
        setTimeout(() => {
            passes(false, 'The username already exists');
        }, 500);
    },
    'The :attribute does not exist'
);

let validator = new Validator({username: 1234}, { username: 'required|string|unique' });
validator.checkAsync(
    () => {
        console.log('passes');
    },
    () => {
        console.log('fails');
    }
);

In above code, the unique rule should not be executed (at least, in my use case). But all the rules are being executed and unique called is printed on console.
How can I stop immediately when a rule fails?

Any update on this?

I have not had a chance to review this deeper, but for clarification sake, I am understanding you want this validation to fail at the string rule and stop all remaining validation for the attribute under test, this never hitting unique , but all remaining futS will continue


Add support for emoji skin tones

I am passing the right image
I think I'm passing the right colon'd name

i.e.; :smile::skin-tone-5:

Gonna close as revisit. Not necessary for milestone 1


Event priority error

Describe the bug
Gives error when you try to use event priority with imported event.
To reproduce
You can use the given example on the wiki:
import:
  org.bukkit.event.entity.EnderDragonChangePhaseEvent

on EnderDragonChangePhaseEvent with priority highest:
  # your code

Expected behavior
no errors
Screenshots

Server information

skript-reflect: 2.3
Skript: 2.6.1
Bukkit: 1.18.2 (Purpur)
Minecraft: 1.18.2
Java: 17
OS: Centos 7

Forgot to commit my code for this when https://github.com/SkriptLang/Skript/pull/4502 was merged, should be fixed now, try the latest Actions build


Hamlet can do the wipe brain action on positronic brains

Reproduction
Be hamlet
find active positronic brain
right click
click on wipe brain
Additional context
not sure if all  player controlled mobs/animals can do this or just hamlet.

As a zombified morticia I was able to also wipe a posi-brain (they asked me to kill them and it was after end of round)
So good chance player controlled mobs can just wipe poor borgo brains.

should probably use complex interaction with interaction rework

Fixed by #30149


How about a changelog?

A sample for non-destructive changelog generation that uses
the git-history as a guide.
It can be filled in manually but will pre-fill itself using
git-conventional commit messages.
It also collects all kinds of interesting information, and
can be customized to not include certain auto-generated sections.
What do you think?
You can play around with it yourself using cargo install cargo-smart-release (a gitoxide project).

I forgot to add the rendered version.

Great idea! How about adding it to cd.yml?

With a generated changelog, we might want to enforce conventional commits with CI (I swear I've contributed to a repo that did this, but I can't seem to find it). At the very least, maybe strongly encourage the use of the conventional commit format in our contributing guidelines.

@o2sh cargo changelog isn't meant to be fully automatic, it's merely an aid. It can be imagined as building the scaffolding from the commit history, and optional conventional commit messages help to fill in the actual changes. From there a human would polish the descriptions to their liking - they will not be altered by the tool, it's non-destructive.
For the upcoming release, for example, I didn't use conventional commits to flag all fixes - these would have to be added by hand.
@spenserblack Even though I fully understand that thought, I hope with the above explanation it's also understandable why enforcing conventional commits isn't necessary. As a matter of fact, when creating the tool I considered this an anti-pattern. The reason is that this forces one to put considerable effort into classifying commit messages, which is hard to me, which would then potentially spam the changelog and reduce the actual signal.
Thus I write conventional commits only for the purpose of them showing up in the changelog, and not by default. This also means that contributors don't have to change or be aware of anything in regards to commit messages which I find lowers the bar of contributions and makes interactions less cumbersome.
cargo changelog works best in conjunction with cargo smart-release, which will automatically fill in the version of the upcoming commit, but it's strictly optional.
Note that cargo smart-release/changelog were created to allow me manage changelogs of 30'ish interconnected crates in gitoxide along with their versioning to assure I never break anyone while leaving actually helpful changelogs without ever forgetting to put anything there.
It's kind of a lot to take in, if you are interested I can demo it in a call, you can reach me via keybase to set that up.

Now that I know you are interested in adding a changelog, I have put in the time to actually write it beyond the generation of the scaffolding :D. Here is the rendered version.
I have created the upcoming release as a milestone to help me with collecting the tickets involved - generally this is a nice way of preparing a release even if conventional commits aren't always present, like when PRs are merged that typically don't use conventional commits. The Milestone was merely for my own utility, please feel free to close/delete it. It's maybe just me who likes them as I used them extensively over at GitPython.

Thanks for explaining! I'm actually a bit relieved to hear that it's not fully automated, as I've always preferred "human-written" changelogs. Mainly because a human is often needed to "squash" changes into a summary.
I also like the idea of milestones. I've only used them for major releases (v1, v2), but I could see us creating next milestones that get renamed once we're confident what the version number should be (I think that's what you're getting at, please let me know if I'm wrong).
How do you see the changelog and release notes working together? Many times notes from one are copied to the other, or the changelog simply says "refer to the release notes," or the release notes say "refer to the changelog." Or do you see the changelog and release notes being different "contexts" with different info?

I also like the idea of milestones. I've only used them for major releases (v1, v2), but I could see us creating next milestones that get renamed once we're confident what the version number should be (I think that's what you're getting at, please let me know if I'm wrong).

For me milestones are just a way to not forget anything that could go into the changelog. Indeed, the version number might not have to be set even since it's not perfectly known - typically I just set it to the next version I predict, often just a patch level.
cargo smart-release also uses commit message analysis to pick the version for you, so feat: … triggers a minor version increment, change!: … would be a breaking change that can trigger a major version change. But that's optional, even though opt-out with cargo smart-release.

How do you see the changelog and release notes working together?

Great question, I forgot to mention that cargo smart-release handles this for you, too. It takes the changelog and processes it into a form suitable for github releases (needs the gh tool with login present), and it creates annotated tags too with yet another form of the changelog to look good there. So if consistency between changelog, github releases and git itself (i.e tags) are desired, cargo smart-release is the easiest way to achieve that. gitoxide relies on that heavily.

All sounds good to me! I especially like that git tag annotations are also taken into consideration. It's a personal preference of mine, but I like making/seeing release notes in the repo without needing to open a browser. Maybe onefetch should include some metric on annotated tags 😆
I am curious why you decided that cargo smart-release should execute gh instead of using a library like octocrab, though.

Maybe onefetch should include some metric on annotated tags 😆

Don't give me ideas ;).

I am curious why you decided that cargo smart-release should execute gh instead of using a library like octocrab, though.

It was compile/link times and ease-of-use. bat and gh I already know how to use and calling them is trivial (along with detection of their presence). With libraries one usually has to know more to get them to work similarly to their respective CLI tools. I can imagine that as cargo smart-release is used by more parties, it should become more independent and rather use libraries. I think it even shells out a git command to determine the worktree status, it's about time gitoxide learns how to do that 😅.

Just stumbled on this app that would allow making milestones with a PR. Since a milestone is being "proposed" in this PR, thought there was a chance that this app would be relevant.

Just checking if there is anything I am missing, but from my point of view there is nothing else to be done here.
Is there anything preventing a merge, is an action required?
Thank you

Sure! you can merge it. I forgot to approve the PR  but it LGTM from the start.
I'll make sure to keep the CHANGELOG.md up to date prior to each release.
Thanks @Byron

Great to hear, thank you!
As this requires a slight change in workflow, let me summarize it here once more. A prerequisite is cargo install cargo-smart-release.

run cargo changelog --write prior to releasing
update the changelog and edit what's there at will as long as it is outside of the statistical regions. These are fully generated.

note that there are these csr-id-<hash> markers, which can be used to control whether items coming from the git history show or not.

for fun, you can run cargo changelog --write again to validate that the log is indeed stable and the edits stick like intended. From my experience, this is always the case unless there was some invalid handling of csr-id-<hash> tags which may cause item to re-appear.
run cargo smart-release (implies dry-run) to see what would happen, or append -e to make it happen. Note that if the gh tool is installed it will create a github release as well that contains the changelog for the new release. If bat is installed it will display the changelog as it would be finalized (it will change the version of the Unreleased section and the date for you).

If there are any problems, as unexpected as it would be, please feel free to reach out.


Easy Atomic Data Export Protocol

I just had a really nice brainstorm with @alexmikhalev about importing atomic data #89. He basically said: instead of focussing on writing importers, make sure other projects can more easily export data.
Exporting Atomic Data is quite a big task for most projects, because they need to make sure that all their subjects resolve. That means implementing the accept header, making sure the routing matches...
But a large part of the advantages of Atomic Data are related to its schema. If a data source would not have resolvable URLs, but could still map properties to Atomic Properties, it would still be beneficial.
Design goals

Easy way to publish data as atomic data
Can be represented statically
Ideally can be achieved in a templating language
Simpler, yet more powerful than RSS

Usecases
Let's consider some usecases:
Importing blogposts
Some author hosts a blog. They don't want to implement the entire atomic data protocol, but they do want to add some simple mapping. They share a list of their blogposts, described as Atomic Data resources on a pre-defined URL.
Some reader sees this blog, and sees a subscribe (atomic) button. His atomic server creates a subscription for this URL. The server fetches the URL, parses the data. It creates copies of the articles on the server. It prevents deduplication
Compared to RSS / Atom feeds

JSON over XML
Extensible, not fixed to one document data model like RSS
Type safe, because atomic data

Names:

Atomic publishing
Atom feeds (lol jk)
Atomic lists
Atomic Data Feed (ADF)

to be continued

names: Atomic Simple Syndication (federation) format, Place federation format.
For private data - i.e. bookmarks, we need API auth (OAuth or Passport) or token in the header to authenticate Atomic server importer.
The outstanding questions for research:

what functionality already exists in RDF export/RDF/OWL land to export data in Atomic format?
What functionality already exists in AWS gateway/Apigee/Kong to provide mapping REST/GraphQL to Atomic format?
If we can provide templates even for a few commonly used services it dramatically decreases the complexity of the atomic server import/atomic sync activity. There are at least two layers we can step in: one is the application layer, like template for Zola (blogging) can be variation of this source of idea

makes sense to separate this from atomizer in #89 - the way I picture this is by comparing Atomic Server to a bank:

Atomizer is going into the bank handing over a pile of money and saying "here is my savings, please put them into my account" - where some of the money might be in foreign currency, some invalid (buttons, obsolete Deutchmark, etc.)
Atomic Data Export Protocol is your bank manager suggesting that you subscribe to their cloud service, allowing them to monitor your pockets and warn you if you got some British Punds in there you'd better get converted before UK spirals too far away after brexit

I.e. Atomizer is much simpler but also by design limited, where Atomic Data Export Protocol can efficiently skip already seen data and duplicates, due to much closer bonding.

@joepio to add fuel to the fire:

remember at this point in time you control both sides - atomic server protocol and export protocol, thinking and talking about how other people can use atomic server export protocol may drive changes to the atomic server protocol (hopefully towards simplicity)
machine to machine protocol doesn't have to be human-readable and can be quite condensed - cap&proto for example, although there are a lot of pros/cons for this approach.


After running sls dynamodb table -n , it should show a file is created

After running sls dynamodb table -n
it should show a file is created with a clear message saying that edit the file

fixed


build: rm fstest_nacl.go at end of nacltest.bash

It's created by src/nacltest.bash and left around.

It is not supposed to be in gitignore. You're supposed to remove it.


init err: undefined

First off thanks for all the work you put into here.
I am trying to get this to work with a raspberry pi 3 B with node version 4.2.1 and npm 2.14.7
When I run the example code I am getting an error
init err: undefined
I console logged the error and am getting the message
didnt match any baudrate!
Not quite sure where to go with this

Have you try configuring the GPIO Serial Port On Raspbian yet.

was it look like this
@kimminahm

I am facing the same problem. I had used the example.js code in this repo. It gives the following log:
init err: undefined
didnt match any baudrate!
@SuperCipher Serial Ports have been configured on my RPi .
I am using Raspberry Pi 3.
node -v
v4.2.1
npm -v
v2.14.7

hi @ayushgargdroid
I used R Pi3 and node v4.2.1 too
This error can cause by many things.
Have you ever get the GT-511C3 module to work with python library before? so I can assume that you have done the most of the stuff right.
If not, I recommend you to try this library first.
http://makesensors.botbook.com/code.html

PS. I used to stuck at this error for months. I just want to tell you I have been there and hopefully, we will get through this together.


Large Scale CCSD Calculation Running Out of Memory

I am trying to run large scale CCSD calculations with nmo = 678 orbitals (cc-pvqz basis set), but the calculation is crashing with the following error message: 'No space left on device'
It seems based in Table I of https://arxiv.org/pdf/2002.12531.pdf that PySCF can do CCSD calculations with many more orbitals.
Can anyone help me understand the error message above, and run large-scale CCSD calculations?
Thank you very much in advance for your time and help,
Ieva

Hi Ieva, how many active electrons do you have in that system?

The feasible system sizes also depend on your resources. You're probably
running out of space on disk. The integrals for CCSD with 678 orbitals
might need almost 1 TB of disk space.
On Mon, Feb 14, 2022 at 9:11 PM Verena Neufeld @.***>
wrote:

Hi Ieva, how many active electrons do you have in that system?
—
Reply to this email directly, view it on GitHub
https://github.com/pyscf/pyscf/issues/1188#issuecomment-1039776037, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADGAJC6RCZYT4R66CWRJJBLU3GY63ANCNFSM5ONCNQHQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thank you very much for your responses! I am trying to simulate a 52 electron system. The disk space is going at about 1GB/sec

Thanks for that info! I might be mistaken but I believe what is meant is that you need enough space on your disk to save all the integrals for example, not the speed of saving, but I might have completely missed your point?

I just learned that my machine has more RAM right now (6TB) than disk space. Is there a way to tell pyscf not to use temp files, and to use memory instead?

I'd recommend telling pyscf that you have a lot of memory available by setting max_memory (e.g. see gto/00-input_mole.py in examples and https://pyscf.org/code-rule.html?highlight=max_memory in documentation). There is also the incore_anyway keyword for coupled cluster calculations (e.g. see cc/15-incore_mo_ccsd_t.py in examples).
Does this work?

You can try the AO-direct algorithm cc.direct = True, for example
https://github.com/pyscf/pyscf/blob/master/examples/cc/10-ao_direct_ccsd.py


TrustedHostsNetworkResolver - add charts to README for better visualization

Either using Mermaid or scans.
https://t.me/samdark_blog/109

I think mermaid is more readable.


Add description to methods in build.js

[ ] Geth
[ ] OpenEthereum
[ ] Nethermind
[ ] Besu
[ ] Erigon

@timbeiko @MicahZoltu @vorot93 @lightclient @MariusVanDerWijden @draganrakita @gnidan @rekmarks
Sooo would you all like me to mention you on each PR?

You can exclude me :+1:

Same, I'm not involved in day-to-day maintenance, although this does seem like a good PR!

@timbeiko @MicahZoltu @vorot93 @lightclient @MariusVanDerWijden @draganrakita @gnidan @rekmarks
Sooo would you all like me to mention you on each PR?

I don't think that is necessary.  People interested can subscribe to this repository to get notifications for all PRs.  Definitely mention me on things that may be particularly relevant to me though, as I don't know if I'll have the time to watch everything that flows through this repository.

@timbeiko @MicahZoltu @vorot93 @lightclient @MariusVanDerWijden @draganrakita @gnidan @rekmarks
Sooo would you all like me to mention you on each PR?

I don't think that is necessary. People interested can subscribe to this repository to get notifications for all PRs. Definitely mention me on things that may be particularly relevant to me though, as I don't know if I'll have the time to watch everything that flows through this repository.

@MicahZoltu ideally we want confirmation from all clients on each endpoint. And timing is important (we get paid by the hour), so if mentioning them would speed things up I'd champion for that. (I mentioned people before I saw this, btw)

also cc @MicahZoltu I addressed your comments

timing is important (we get paid by the hour)

I would assume that we aren't paying you to sit and wait for PR approvals, if so we should probably reconsider the arrangement.  😉  I do think there is value in having one person from each client team actively watching this repository though, so we don't get stuck with PRs that are stale because we aren't getting the right eyes on them.

@MicahZoltu @lightclient I am not sure if the edits to the build.js file are still needed, but I know that the rest of this PR is not needed anymore. If not I will close this PR

I haven't been following this PR particularly closely.  If you think a subset of it is worth review/merge then we should get the extraneous pieces removed so the bits that are useful can be reviewed in isolation.  In general, many small PRs are preferable to one large PR anyway.  😄


Uncaught TypeError: Promise.defer is not a function

[Enter steps to reproduce below:]

...
...

Atom Version: 1.1.0
System: Mac OS X 10.11.1
Thrown From: atom-typescript package, v7.7.2
Stack Trace
Uncaught TypeError: Promise.defer is not a function
At /Users/noctis/.atom/packages/atom-typescript/dist/worker/lib/workerLib.js:33

TypeError: Promise.defer is not a function
  at Parent.RequesterResponder.sendToIpcHeart (/Users/noctis/.atom/packages/atom-typescript/dist/worker/lib/workerLib.js:33:33)
  at Object.getProjectFileDetails (/Users/noctis/.atom/packages/atom-typescript/dist/worker/lib/workerLib.js:106:47)
  at /Users/noctis/.atom/packages/atom-typescript/dist/main/atomts.js:50:20
  at Emitter.module.exports.Emitter.emit (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:86:11)
  at /Applications/Atom.app/Contents/Resources/app.asar/src/pane-container.js:333:27
  at Emitter.module.exports.Emitter.emit (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:86:11)
  at Pane.module.exports.Pane.setActiveItem (/Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:247:22)
  at Pane.module.exports.Pane.activateItem (/Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:311:21)
  at Pane.module.exports.Pane.activateItemAtIndex (/Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:305:19)
  at Pane.module.exports.Pane.activatePreviousItem (/Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:276:21)
  at Pane.module.exports.Pane.removeItem (/Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:386:16)
  at Pane.module.exports.Pane.destroyItem (/Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:448:16)
  at HTMLDivElement.<anonymous> (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/tabs/lib/tab-bar-view.js:236:22)
  at space-pen-ul.jQuery.event.dispatch (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/jquery/dist/jquery.js:4435:9)
  at space-pen-ul.elemData.handle (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/jquery/dist/jquery.js:4121:28)

Commands
  2x -1:03.5.0 editor:auto-indent (atom-text-editor.editor.mini)
     -0:33 command-palette:toggle (atom-workspace.workspace.scrollbars-visible-when-scrolling.theme-one-dark-syntax.theme-nucleus-dark-ui)
 45x -0:29.7.0 core:move-down (atom-text-editor.editor.mini.is-focused)
  5x -0:21.6.0 core:move-up (atom-text-editor.editor.mini.is-focused)
     -0:18.6.0 editor:consolidate-selections (atom-text-editor.editor.mini.is-focused)
     -0:18.6.0 git-diff-details:close-git-diff-details (atom-text-editor.editor.mini.is-focused)
     -0:18.6.0 core:cancel (atom-text-editor.editor.mini.is-focused)
     -0:18.4.0 tool-panel:unfocus (button.btn.btn-default.tool-bar-btn.ion.ion-navicon-round)

Config
{
  "core": {
    "projectHome": "/Work/Projects/",
    "disabledPackages": [
      "file-type-icons",
      "tree-view-breadcrumb",
      "language-typescript",
      "filetype-color",
      "compare-files",
      "compare-files",
      "atom-ternjs",
      "git-history",
      "jsformat"
    ],
    "themes": [
      "nucleus-dark-ui",
      "one-dark-syntax"
    ]
  },
  "atom-typescript": {
    "disableCompileOnSave": false,
    "compileOnSave": false
  }
}

Installed Packages
# User
.bin, vundefined
angularjs, v0.3.3
atom-beautify, v0.28.17
atom-jshint, v2.0.0
atom-tsd, v0.9.0
atom-typescript, v7.7.2
atom-yeoman, v0.3.15
autoclose-html, v0.19.0
bottom-dock, v0.3.5
build, v0.48.0
build-grunt, v0.2.0
build-gulp, v0.2.0
color-picker, v2.0.13
compass, v0.9.1
css-comb, v2.4.0
css-snippets, v0.9.0
cucumber, v0.5.0
emmet, v2.3.14
file-icons, v1.6.11
flex-tool-bar, v0.6.0
git-diff-details, v0.21.0
git-log, v0.4.1
gulp-manager, v0.2.13
javascript-snippets, v1.0.0
jshint, v1.8.3
json-schema, v0.1.15
language-SCSS, v0.4.0
language-cshtml, v0.1.1
language-sln, v0.1.0
linter, v1.10.0
local-history, v3.2.3
minimap, v4.16.0
minimap-autohide, v0.10.1
minimap-bookmarks, v0.1.0
minimap-find-and-replace, v4.3.2
minimap-git-diff, v4.1.8
minimap-highlight-selected, v4.3.1
minimap-linter, v1.0.0
minimap-pigments, v0.1.7
minimap-selection, v4.3.1
nucleus-dark-ui, v0.6.7
omnisharp-atom, v0.25.10
pigments, v0.18.1
project-manager, v2.6.5
project-view, v0.2.0
terminal-panel, v1.14.1
tool-bar, v0.1.9
tool-bar-almighty, v0.2.2
tool-bar-main, v0.0.8

# Dev
No dev packages

But it is a function ...

can you open your dev console in atom and type in Promise.defer to confirm :rose: It's provided by v8 (node and chrome)

the error in console

the promise function is define at there , but it is not contain defer() :(

@NoctisHsu The issue is some other package is overriding the Promise library built into node. I'd check where that's coming from, and open an issue there.
@basarat Promise.defer isn't part of the A+ spec either, is it possible to avoid it?

@blakeembrey You are right! The promise function is overridden by 'advanced-open-file' package.
When I remove it ,atom-typescript is working fine.

is it possible to avoid it?

@blakeembrey I was lazy. Feel free to create an issue and mark it as up for grabs :rose:
@NoctisHsu Cheers :rose: Closing as the issue is not in this package.


DRM with certain channels

A&E and History seem to be using DRM and they fail to play now. Just letting you know in case you don't.

yes, they did that in December sometime:
https://community.getchannels.com/t/frndly-tv-for-channels/29078/138?u=matthuisman
(there note there how you can exclude them)


build(uv-cli): Set correct gitdir and head path for worktree

Summary
Resolves #6196 .
Test Plan
Run cargo check multiple times within the worktree and inspect the outputs. There should be no Compiling message after the first check.

Some related info:
:)  tree /Users/eth/workspace/astral-sh -L 1
/Users/eth/workspace/astral-sh/
├── uv/
└── uv-dev/

(devshell) :)  git worktree list
/Users/eth/workspace/astral-sh/uv      20ef94b15 [main]
/Users/eth/workspace/astral-sh/uv-dev  3c313126b [uv-cli-worktree]

content of .git file in worktree:
(devshell) :)  /bin/cat /Users/eth/workspace/astral-sh/uv-dev/.git
gitdir: /Users/eth/workspace/astral-sh/uv/.git/worktrees/uv-dev

content of HEAD of worktree:
(devshell) :)  /bin/cat /Users/eth/workspace/astral-sh/uv/.git/worktrees/uv-dev/HEAD
ref: refs/heads/uv-cli-worktree

content of commondir of worktree:
(devshell) :)  /bin/cat /Users/eth/workspace/astral-sh/uv/.git/worktrees/uv-dev/commondir
../..

cc @charliermarsh can you actually review this since you use worktrees?

Sure, no prob.

@eth3lbert I just merged #6825. I ended up submitting that before realizing this PR or #6196 existed. I merged that one over this one because I liked having the logic split out into a separate function. But this overall looked good too. Apologies for the duplicated effort and thank you for noticing this problem and submitting a fix. :-)

All good, thanks!


Question: built-in toggle_ignore action to grep/live_grep

First of all, thank you for the amazing plugin ❤
I was trying to build my own grep/live_grep version of the toggle_ignore action, but after digging into the code I saw it would not be that trivial since the resume action for these commands is very different from the files picker. I've tried adding the toggle_ignore_flag, changing the rg_opts and then resume, but I couldn't get it right.
Are there any plans on adding a built-in toggle_ignore action to these commands?
Thank you!

First of all, thank you for the amazing plugin ❤

Ty for your kind words.

Are there any plans on adding a built-in toggle_ignore action to these commands?

I'm not sure about adding that, the UI is already loaded with info, perhaps we can make the curren't command work for grep/live_grep too and it can be an optional addition users can add to their actions (as was before I made this the default with files)?

@estacioneto, use:
local fzf_lua = require("fzf-lua")
fzf_lua.setup({
  grep = {
    -- use `ctrl-r` to not override the `ctrl-g` regex toggle
    actions = { ["ctrl-r"] = { fzf_lua.actions.toggle_ignore } },
  }
})

For example :FzfLua grep search=testing debug=true:

After pressing ctrl-r:

Note the rg command added --no-ignore as its first flag as wel as the match in the doc\tags file which is in fzf-lua's .gitignore

After  pressing ctrl-g to switch to live grep, the flag is still respected:

@ibhagwan amazing!

perhaps we can make the curren't command work for grep/live_grep too

That was exactly what I wanted, especially because it will work with the actions descriptions out of the box.
Thank you so much for doing it so fast! 🤩

@ibhagwan amazing!

perhaps we can make the curren't command work for grep/live_grep too

That was exactly what I wanted, especially because it will work with the actions descriptions out of the box.
Thank you so much for doing it so fast! 🤩

Ty @estacioneto, there's just one tiny issue (if you look at my screenshots), the switch to regex header is not displayed properly when toggling gitignore on grep, will be fixed soon too.

@estacioneto, should work as expected on latest.


For test

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 91.33%. Comparing base (0474b25) to head (bdb2099).
Report is 61 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #85      +/-   ##
==========================================
+ Coverage   89.89%   91.33%   +1.44%
==========================================
  Files          83       51      -32
  Lines        1484      923     -561
  Branches      185      130      -55
==========================================
- Hits         1334      843     -491
+ Misses        150       80      -70

Flag
Coverage Δ

backend
?

frontend
91.33% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Update of the ASA quick start guide

Rewrite of current examples and adding SessionWindow, Match_Recognize, UDF and Geospatial

 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.:x: rodrigoamicrosoft sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@rodrigoamicrosoft : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @rodrigoamicrosoft , Microsoft authors and contributors are asked to make content contributions through the private repository so the content can be staged and validated by the current validation rules. It would be best if you do future contributions through the private repo.
For more information, see Should I work in a private or a public repo?.
If you need help getting set up to work in the private repo, see Fork and clone a reposistory.
Thanks.

We will continue these changes in the private repo. #please-close


Revert "[SSADestroyHoisting] Split destroy from copy."

Reverts apple/swift#41497

@swift-ci please smoke test

preset=buildbot_incremental_linux,long_test
@swift-ci Please test with preset Linux Platform


More detailed admonitions

https://www.notion.so/prismaio/DOC-Styles-for-admonitions-bb26c45993e6456a85d5d3ebb5c76811

Tested all three - looks great!


Use specific glance config for octavia kuttl tests

octavia requires a fully functional glance env, use the layout/single config to get a working glance service.

/hold


TypeError: UnstructuredClient.init() got an unexpected keyword argument 'retry_connection_errors'

just trying to use the code from here

But getting this error
TypeError: UnstructuredClient.init() got an unexpected keyword argument 'retry_connection_errors'
My environment
PyMuPDF==1.24.4
unstructured[all-docs]==0.14.0
nltk==3.8.1
pandas==2.2.2
llama-index==0.10.38
llama-parse==0.4.3
PyPDF2==3.0.1
fastapi==0.111.0
minio==7.2.7
uvicorn==0.29.0
psutil==5.9.8
boto3==1.34.109
botocore==1.34.109

Ah, looks like there's a typo in the retries section! The retry_connection_errors is meant to go in the RetryConfig object

Yes. Also there is again the same network issue. Please confirm whether you guys are fixing something or not

I believe the majority of the issues have been resolved, but I can double check your account for you. Can you please send a note to<EMAIL_ADDRESS>with your custom url?

Hi, it worked.


Fixes #56 Copy entity HTML to clipboard

Added copy to clipboard icon on the entity panel. It will copy the HTML for the current component and its children.

Icons and style to-be-defined to match the same style for the component's icons (https://github.com/aframevr/aframe-editor/issues/10)

If the copy icon is on common it seems that you're going to only copy the common section

The icon / label should be better placed on the entity on the scenegraph

Advantage on the component panel is to keep the entity copy action in the same place as component copy action. As well as separating management of scene structure (scene graph) from scene data (components panel).
But I agree the current placement makes it seem like you can only copy the common components.

Code looks good. Just need to address the UX.

Current icon placement looks like it applies for common components.

Possible solutions:

Add text label to the icon. Possibly renaming the Common panel to the Entity panel might help as well.
Move function to scene graph - I don't quite like this as it mixes scene structure with entity data.

Renaming common to entity is misleading as well. All the components below belong to the entity as well. A third solution:
We could make the attributes panel title (and maybe rename to entity) larger to accommodate the copy button. That would break the consistency though with the scenegraph title.

As a side note. I think we still need to visually differentiate the commons section from the rest of the components.

A fourth solution: We can put the copy button next to the <a-entity> label

Third solution addendum, we can make both headers bigger. They do look sort of cramped anyways.

I like the third solution too, I'll make a mockup and we could discuss about it.

What do you think about something like this?
I was thinking that probably we could remove the <a-entity> from common and put it in the panel title, so instead of having, like in the screenshot, entitywe could have <a-entity>, <a-box>, <a-entity #box>...

The top margin at the top of the titles looks too dark in comparison with the lines that separate the component titles. They should be consistent.

@dmarcos I just fixed that, although the menu bar will be remove in the next PR :D

Updated with the last changes regarding the top menu. I've moved the <a-entity> attribute from Common to the title of the sidebar.

@dmarcos @ngokevin what do you think about the new style? ^

Maybe the question mark for the docs is too big. We sould make it match the line height of the component title

Should we make <a-entity> title larger and increase the contrast? We probably need to emphasize that it's the title for the whole components panel

@dmarcos yep, I'll decrease the size of the icon for help.
Re the title, I've made it white and a little bigger, something like this you mean?

Maybe a different color of the title background to make a bigger contrast?

@dmarcos @ngokevin what do you think about adding this functionality as is and then we could create another PR just for style the icons and sidebar title style?

I get: <a-entity id="greenBox" geometry="primitive: box" material="color: #0f0" position="4 2 4" rotation="" scale="" visible=""></a-entity>
Should we trim the null values for default components?

r+wc adjusting style in another PR sounds good.

@ngokevin do you mean converting this
<a-entity id="greenBox" geometry="primitive: box" material="color: #0f0" position="4 2 4" rotation="" scale="" visible=""></a-entity>

into
<a-entity id="greenBox" geometry="primitive: box" material="color: #0f0" position="4 2 4" rotation scale visible></a-entity>

or directly removing them as they're already default components included in any entity?
<a-entity id="greenBox" geometry="primitive: box" material="color: #0f0" position="4 2 4"></a-entity>

I would polish it so it is ready to paste into people's code editors, meaning to remove superfluous stuff that don't matter like rotation="". So yeah, I'd say remove them.

@ngokevin I've implemented removing the default attributes if they've default value, thanks for the idea. the result copy to the clipboard it's more clear now.


Add Drag n' Drop Support to OpenKh.Tools.ImageViewer

Self explanatory. Requested by @Vladabdf.

Nice stuff TK!


are mysql and redis started in advance?

I didn't see any configuration of mysql and redis, are these two services start in advance?

Yes, these two are not placed in docker-compose.yml


Delete jacoco setting in spring modules

As title.
Resolve #26175

Hi, @yiliuTo .
https://dev.azure.com/azure-sdk/public/_build/results?buildId=1268419&view=logs&j=b7e05d34-ff84-5d4f-6be8-71e0852fbae4&t=14ed7cc3-77e0-5c56-7dbf-9a450ffc4d86&l=486
Could you please add more tests for spring-integration-azure-eventhubs and pring-integration-azure-servicebus?

Hi, @moarychan , could you please help to fix the pipeline failure?

/azp run java - spring - tests


"Show Game" mode is blank of shared project

Describe the bug
After switching sort order, selected projects are not selected anymore
Steps to reproduce the behavior

Open shared project  https://arcade.makecode.com/79455-51780-29078-64875
Click "Show Code" -> click "Show Game"

Expect behavior
"Show Game" should not be blank
Actual behavior
"Show Game" mode is blank of shared project

Additional context

OS: Windows(this bug repro on each browser)
Machine build: 17763.1.amd64fre.rs5_release.180914-1434
arcade version: 0.12.13
Microsoft MakeCode version: 5.17.25

Issue is that game is shared from beta, which means it has some things (in this case the SpriteKind changes, but in others new blocks / etc) that are incompatible with the live site. Maybe it should redirect to the version of the editor that the game was created in if created version > live site version?
Re: https://github.com/microsoft/pxt-arcade/issues/303

beta url is not expected to run on live.


NVS Strings and Blobs disappear after reboot (IDFGH-2229)

Hello,
I'm having some trouble with NVS. Basically, I write some variables to it and after that, I can successfully read them from the NVS partition. However, after rebooting the device, Strings and Blobs can't be found anymore.
To make things easier, I have created a repository with a demo of the problem and all the description:
What I have tried so far:

Checked partition sizes and alignments
Checked the NVS read and write process and it seems to be correct
Tried Strings and Blobs with different lengths
Removed from the project all code that is not related to the NVS

@mauriciofarina Thanks for reporting.

Hi @mauriciofarina I could reproduce your issue. But I couldn't without the middleware code. Is there an example which only reads/iterates and writes using IDF code?

It seems like the iterator has problems iterating correctly over string/blob type entries when the iterator type is NVS_TYPE_I32 (and possibly other fixed-length entries, too). It then deletes part of the string/blob entry. I think it has nothing to do with erasing the flash before.
I can reproduce the issue now by 1.) writing a string to nvs, 2.) iterating over the nvs with an iterator which looks for type NVS_TYPE_I32. This works without erasing the flash.

@mauriciofarina Could you please verify whether this patch of the idf repo fixes the issue on your system?
0001-bugfix-iterator-of-non-matching-type-works.patch.zip

Hello @0xjakob !
The problem was indeed the iterator. After removing it from the functions that were using it everything worked just fine.
I also applied the patch and was able to use the iterator successfully!
You can close the issue.
Thank You!

Good to hear! The patch will go to through internal review and will then be deployed on github.

@0xjakob Thanks for the support. @mauriciofarina Thanks for reporting, the fix has been available on GitHub, feel free to reopen if the issue still happens. Thanks.


TEST: DO NOT MERGE

hey @biwano  - can we close this?

https://github.com/OlympusDAO/olympus-frontend/pull/1650 should make this obsolete


class, subclass, and protocol return zero

The class, subclass, and protocol values returned by the list_devices function are all zero, which is considered abnormal. However, when using libsub to read the class, subclass, and protocol of the winus device, the values are 0xFF, 0x42, and 0x03 respectively, which is the expected result.

Hmm. On Windows, these are coming straight from a call to  IOCTL_USB_GET_NODE_CONNECTION_INFORMATION_EX. I believe libusb also uses the same call to get the device descriptor, so I'll have to see if I can reproduce this and see what we're doing differently.

I'm not able to reproduce this. I tested with a few Android phones in normal mode and fastboot mode, and on all of them the class, subclass, and protocol read as zero in nusb and libusb on both Windows and Linux, but this is the correct value from the device descriptor. Zero is the typical value for a composite device and means that the class is defined at the interface level.
However, Android fastboot does return an interface descriptor with class=0xFF, subclass=0x42, and protocol=3. Some Windows tooling, including the Device Manager under Compatible IDs, shows these values for the whole device. Are you sure you are expecting to see these values in the device descriptor, and not the interface descriptor? nusb correctly reads these values from the interface descriptor (see the descriptors example).

https://github.com/kevinmehall/nusb/pull/29 adds DeviceInfo::interfaces to get class, subclass, protocol on each interface, as long as the device is using the composite group parent driver.


devspace dev fails after changes in devspace.yaml and custom helm charts - mainly due to helm errors

What happened?
devspace dev hides the errors from helm deployment. In this specific case, my helm chart failed to install with helm install due to the following error:
❯ helm install sampleapp ./Chart -n develop
Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: ConfigMap "entry2" in namespace "develop" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-name" must equal "sampleapp": current value is "app"

But devspace failed with error:
11:25:00 dev:app Stopped dev app
11:25:00 start_dev: replace pod: couldn't find a matching deployment, statefulset or replica set
11:25:00 fatal exit status 1

What did you expect to happen instead?
Actual helm error should have been reported.
How can we reproduce the bug? (as minimally and precisely as possible)
Create 2 deployment charts with same names for a config map item.
Try to deploy them separately through 2 different devspace.yaml files with Chart location specified in  devspace.yaml like so:
deployments:
  app:
    # This deployment uses `helm` but you can also define `kubectl` deployments or kustomizations
    helm:
      # We are deploying this project with the Helm chart you provided
      chart:
        name: ./Chart

My devspace.yaml:
Doesn't matter. Just ensure that you are using a local helm based deployment
...

Local Environment:

DevSpace Version: 6.1.1
Operating System: mac
ARCH of the OS: AMD64
Kubernetes Cluster:
Cloud Provider: other - used rancher desktop
Kubernetes Version:

clientVersion:
  buildDate: "2022-08-17T18:54:23Z"
  compiler: gc
  gitCommit: 95ee5ab382d64cfe6c28967f36b53970b8374491
  gitTreeState: clean
  gitVersion: v1.24.4
  goVersion: go1.18.5
  major: "1"
  minor: "24"
  platform: darwin/amd64
kustomizeVersion: v4.5.4
serverVersion:
  buildDate: "2022-08-25T03:45:26Z"
  compiler: gc
  gitCommit: c3f830e9b9ed8a4d9d0e2aa663b4591b923a296e
  gitTreeState: clean
  gitVersion: v1.24.4+k3s1
  goVersion: go1.18.1
  major: "1"
  minor: "24"
  platform: linux/amd64

Anything else we need to know?

/kind bug

sorted out in slack channel discussion.


Issue with No Insertion Maths

http://forum.kerbalspaceprogram.com/threads/93115-0-90-Transfer-Window-Planner-v1-2-3-0-(Jan-11)?p=1669093&viewfull=1#post1669093

Can't replicate since update to DateTime code to handle large numbers


Fixed typo with protocol name

Using MMNumberKeyboard on anything except for a UITextField or UITextView was resulting in the error "First responder <***** 0x10142f2c0> does not conform to the UIKeyInput protocol." even though the class did conform to the UIKeyInput protocol. After spending some time trying to work out what I was doing wrong, I discovered a typo in MMNumberKeyboard.

Wow! That's a nice one, thank you @AnthonyMyatt! :)


Add Main in Package.json

Any chance I could get you to add a "main": "./path/to/angular-color-picker.js" in the package.json? This would then allow import for ES6 modules. Packages should typically have a main anyway, so its a good idea regardless.
To be clear also point the main to the uncompressed file as in the user/devs build process he'll be compiling the modules for output and will need it in the uncompressed state.

Fixed in commit 2142f4129c5222a7406934b98ec4add9d599bc31 and released in v0.6.5.

thx @ruhley


Federations APIs: CRUD

[ ] GET /api/$version/cdns/:name/federations
[ ] GET /api/$version/cdns/:name/federations/:fedId
[ ] POST /api/$version/cdns/:name/federations
[ ] PUT /api/$version/cdns/:name/federations/:fedId
[ ] DELETE /api/$version/cdns/:name/federations/:fedId

@moltzaum is working on this


Remove gutters on outside

Would be great to have an option to remove gutters on the outside of the grid. I want the content of the first and last columns to touch the edge of the browser viewport.
Currently it does this but it means you get a horizontal scrollbar on the page. If you set padding to eliminate the scroll bar as suggested in other issues then the gutters of those columns bring the content in from the edge of the page.

realised actually you could just add overflow-x: hidden; to the parent container. Maybe a bit hacky but works :-)

I've thought about this some more and have decided that I think it should be handled in the site's specific styles which is easy enough to target. Thanks for the suggestion.


Add MIDI playback

If an electric drum kit is detected it'd be great if you could make it so that the drum sounds were sent to the drumkit via midi when you press the play button

There's now a setting that lets you playback via a midi device (e.g. electronic drum kit):


Question: background options for transform_image

I was wondering if there is a way to provide continuity to the areas outside the image by replicating the old borders of the image, in a similar way as GL_CLAMP functions work in OpenGL, or as BORDER_REPLICATE in OpenCV.
I haven't seen how can the set_background argument in transform_image can help me do this.
Here is an example to illustrate what I want to do with dlib:
I take the original picture, on the left, and perform an affine transform that aligns it, and crops it with a border. The result, on the right, is an image with the face centred.

Thank you again for your work on dlib, it is a pleasure to work with it!

Unfortunately, there isn't a function that does this in dlib.


update beta.13

done via https://github.com/AngularClass/angular2-webpack-starter/commit/a556f3cf446076ba04951fa41da817876fd01d0b


Suggestion - TCP option?

Very handy script, the only suggestion I have would be adding an option to generate configs that use TCP instead of UDP. (e.g. for disguising traffic as HTTPS via 443/tcp)
It's pretty easy to do manually, just modifying the server and client configs, but it would be nice to have it supported by the script.

This will get closed, @NYR doesn't want to support TCP : see all of these issues

Yeah, TCP support is currently not planned. If you really need it, it's pretty easy to change :)
PS: port 53 UDP often works where 443 TCP is unrestricted, that's what I personally use.

You can use project openvpn-install-advanced by @zabullet - it can configure tcp and udp server


Updating requires for linux to support 32bit build(For Testing)

Description of the Change
Added logic from @progkix to support builds for 32bit linux.
Alternate Designs
N/A
Why Should This Be In Core?
Build scripts are in core.
Benefits
allows people to build on 32bit linux.
Possible Drawbacks
None so far. Will test this change before merging
Applicable Issues
Creating PR off branch on master to trigger travis build.  See https://github.com/atom/atom/pull/13835 of original PR of same change.

In witch release will be this implemented?

I just checked and it's in the 1.16.0-beta0 release that just came out
On 03/10/2017 02:19 AM, Nelson Martell wrote:

In witch release will be this implemented?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/atom/atom/pull/13842#issuecomment-285596465, or
mute the thread
https://github.com/notifications/unsubscribe-auth/AAr8SjvoKpZnXx4deYq59YlRrB8cF2fKks5rkPmegaJpZM4MEm7x.


fixes bug 1287097 - Use Vid.ly API over https

Coverage remained the same at 84.967% when pulling fc100b9de17b2dd91c144140f5eb4a2d7240cf81 on peterbe:bug-1287097-use-vidly-api-over-https into 7708c6187171a40b41411550efe75c3b85a97bb4 on mozilla:master.


Usage in class libraries

There are issues https://github.com/aspnet/Mvc/issues/3199 and https://github.com/aspnet/Mvc/issues/3091, but these deal with rendering views while within the ASP.NET context. I want to be able to use Razor as a templating system external to ASP.NET.
I have used the same techniques as https://github.com/aspnet/Diagnostics/blob/dev/src/PageGenerator/Program.cs, but this only deals with generating a class file based on the Razor file. I also want to be able to compile and run the generated file and use it at runtime. Is this currently possible? Are there are any examples of this?
Also I seem to lose access to the model directive (at least the intellisense). Is this only available in an ASP.NET project, or is there a way to enable it for other project types?

@ajaybhargavb I tried looking for your WIP sample. You could shed light here :smile:

We are currently doing some work on this. But currently it does involve MVC so that the features like layouts, partials and tag helpers can still be supported when a view is rendered to a string even when no request is present. As for the 'Razor as a templating system' scenario, we are still discussing what kind of support we want to provide.

If I only need to support for the bare minimum (i.e. strong typed html rendering) without any of the items you mentioned, is there any quick and dirty example I can look at?

I was able to figure it out by looking more closely at the implementation detailed in the MVC project. Thanks.


Error when testing the trained model for eggbox on LMO

Hi, when I evaluate your trained model for eggbox on LMO,  I encountered the following error. How can I fix this issue? Thanks!

Hi,
I'm not aware of this. Maybe you can try with a different OpenCV version? I used OpenCV 4.5.2

Thanks for your reply! By OpenCV version, you mean the version of OpenCV, not the version of opencv-python, right? From the figure, the OpenCV version is 4.4.0 if I understand it correctly.

Hi,
I'm not aware of this. Maybe you can try with a different OpenCV version? I used OpenCV 4.5.2

Thanks for your reply! By  OpenCV version, you mean the version of OpenCV, not the version of  opencv-python package, right?

Sorry for the unclear answer. I meant the version of opencv-python, which can be installed with pip install opencv-python==<IP_ADDRESS> .

Thanks for your reply! I changed the opencv-python version to <IP_ADDRESS>, but it still did not work. When I changed the parameter minimum_point_number of the function pyprogressivex.find6DPoses from 6 to 4, it worked. I wonder whether this change would affect the model evaluation performance. Thanks!

I think it will not affect the final results.
If the matching is too less, the estimated pose has very less chance of being a correct pose. In other words, even if there is no error report, the estimated pose is bad.


Lspsaga outline got an error after try to jump to a symbol in python.

Describe the bug
Lspsaga outline got an error after try to jump to a symbol in python.
lsp server is pylsp

Steps to reproduce

open python file
Lsp Toggle outline
select func and enter

Expected behavior
correct jump to symbol
Neovim version (nvim -v)
nvim 0.9.1
lspsaga commit
95ec55dfd5355c90f1cee834bd415e1d2b5d9854
Terminal name/version
Alacritty

Can repro when python lsp is pylsp.


NonceVerification: use separate errorcodes for warning vs error

While cleaning up a plugin, I noticed that the issue count for the WordPress.Security.NonceVerification.NoNonceVerification error code was different if I ran phpcs with the -n flag (no warnings).
Error codes should be unique. Having the same error code for something which is mandatory (error) and recommended (warning) is bad practice and does not properly allow for modular disabling of notices.
This PR fixes this.
As the error code is changing anyhow, I figured it made sense to also remove the duplication of the sniff name from the code.
This is a breaking change as <exclude>s for the old errorcode currently in custom rulesets will be invalidated by it, as well as inline annotations using the error code, so this PR should go into WPCS 2.0.0.
N.B.: The ruleset change is only necessary until the deprecated sniffs have been removed.

Rebased. Once the build passes, this one should now be considered ready for review.


Inconsistent behavior

Category
[ ] Rendering issue
Description
[//]: # Application works fine and smooth in web browser but when build is deployed to TV, focus to a component and performance of application is very slow as compared to web browser.
Is there any version dependency for the above mentioned issue?
Environment
[//]:  "@enact/core": "^2.5.1",
"@enact/i18n": "^2.5.1",
"@enact/moonstone": "^2.5.1",
"@enact/spotlight": "^2.0.0",
"@enact/ui": "^2.5.1"
Enact version: 1.2.0
NPM version: 6.4.1
Node version: 10.15.3

For reference, what version of Enact CLI are you using? This can be seen from the enact -v command.

Hi Gabriel, thanks for the report.  Do you have some sample code that demonstrates the issue?  It may be that something in the application is causing unnecessary re-rendering.  On a desktop-class machine, extra renders have little impact.  On an embedded system, extra renders can have a dramatic impact.  Using strategies that reduce renders (shouldComponentUpdate and pure components) are important.  You may want to use some of the tips contained in the Enact performance guide.

One other tip:  Using Chrome DevTools' processor slow-down feature can be useful to approximate the performance of embedded systems when developing.

For reference, what version of Enact CLI are you using? This can be seen from the enact -v command.

Enact version: 1.2.0

Thanks for the reply @webOS101. Let me optimize the code and recheck the performance of application. Meanwhile, could you give a suggestion or a tip to customize moonstone components?

Hi @gabrieljerin , for Enact 2.x you'll want to use CLI 2.x. It includes a wide arrange of improvements over 1.2.0 and may help. Additionally, with 2.x CLI you can target particular versions of browsers using the Browserslist format.
For example, to target LG webOS TV 4.x, you could set env var BROWSERSLIST="Chrome 53" before building, then it will only transpile and polyfill the minimum requirements for Chrome 53 without added bulk/processing.

@gabrieljerin Customization is very easy.  The docs should mention the css classes you can pass in.  I would suggest you visit our Enact gitter chat or open a new issue with a specific question.

Hi @webOS101 , Is there a way to use react life cycle hooks in enact/core/kind ?

@gabrieljerin If this issue has been resolved, can you close this ticket?  If not, please provide more information.  If you found your solution, it would be helpful to share it here.


[AutoRelease] t2-postgresqlflexibleservers-2024-08-26-34171(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/2048
Recording test success

issue link:https://github.com/Azure/sdk-release-request/issues/2048


feat(property-inconsistent-name-and-type): disable rule in default configuration

PR summary
This commit modifies the 'property-inconsistent-name-and-type' rule configuration
so that it is disabled by default.
Signed-off-by: Phil Adams<EMAIL_ADDRESS>PR Checklist
General checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)
[ ] Dependencies have been updated as needed
[ ] .secrets.baseline updated as needed?

Checklist for adding a new validation rule:

[ ] Added new validation rule definition (packages/ruleset/src/rules/*.js, index.js)
[ ] If necessary, added new validation rule implementation (packages/ruleset/src/functions/*.js, updated index.js)
[ ] Added new rule to default configuration (packages/ruleset/src/ibm-oas.js)
[ ] Added tests for new rule (packages/ruleset/test/*.test.js)
[ ] Added docs for new rule (docs/ibm-cloud-rules.md)

Checklist for removing an old validation rule:

[ ] Removed old rule implementation (packages/validator/src/plugins/validation/*.js)
[ ] Removed or adjusted testcases (packages/validator/test)
[ ] Updated default configuration to deprecate old rule (packages/validator/src/.defaultsForValidator.js)
[ ] Removed docs of old rule (docs/ibm-legacy-rules.md)

:tada: This PR is included in version 0.35.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 0.86.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


Use of CoreMotion instead of UIDevice to detect orientation

This improves on the previous orientation detection that was implemented using UIDevice, that will only triggered as long as users haven't locked their screen. CoreMotion will always send these updates regardless if the user have locked the screen or not, which would be the desired behavior for most cases. I haven't done to much performance benchmarking but I believe the frequency of CoreMotion updates checks should be ok.

Thanks for the pull. I will review the changes tonight

Personally, I've found this implementation to be more useful than the notification based solution on master as this implementation will work even if the device orientation is locked.

@Awalz Is this something you still are interested of using? I personally believe using Core Motion is what users expects and prefers, having to unlock their phone rotation to record in landscape is not very user friendly.

I very much would like to use Core Motion instead of the current implementation. I had hoped to rewrite the current rotation handling by now using your PR. If I could go back in time, I would have merged this. Currently the handling is messy and requires to be gutted and replaced.

@Awalz Let me know if you need any help with this!  I'm currently using it in my app [1] so will be continuing to use library, but currently using my own fork since I need the core motion support.
[1] https://itunes.apple.com/app/apple-store/id1021405859?mt=8

Thanks @jonandersen, I would definitely appreciate your help with this! I have added you as a collaborator to the project.
Leap Second looks very cool! I should look into adding a README section for apps currently using SwiftyCam to give visibility to these projects

@Awalz thanks! I'll submit a new updated PR based of the latest master branch!

Sounds great! You should check out the Swift4 branch I just updated. Theres some API breaking changes in it that will be be made into version 3.0.0 once Swift 4 is released


App size is huge

Created blank C# WinUI3 app (packaged)
After compilation app size in 127 mb and package size is 250+ Mb.
I compare it to simple WPF app size of 2-3 Mb.
Why so large size of app and package? How to lower it to 1,2,3 Mb?

@KirillPom is this app size issue specific to the preview1 version of Winui3 or were you noticing it with other Winui apps as well?

@MikeHillberg @Austin-Lamb for FYI

I compare it to simple WPF app size of 2-3 Mb.

You should be comparing with .NET Framework or .NET Core framework dependent application. See https://docs.microsoft.com/en-us/dotnet/core/deploying/ .
Currently the default template creates a self-contained application. It's not related to WinUI.
Total size of WinUI introduced files are about 32MB.

How to lower it to 1,2,3 Mb?

If there is a mechanism to share WinUI components system-wide. This is opposite to the goal of extracting WinUI from the OS.

@huoyaoyuan . Thank you.
But the question is - do you really need 127Mb of binaries just to show simple window with one button.

do you really need 127Mb of binaries just to show simple window with one button

Then the topic comes to that how to delete unused code.
For .NET side, there is trimming tool, but still imperfect for UI applications.
Currently the SDK cannot analyze what you need. It can only grab everything what they support now.
I'd expect the successor of .NET native to trim across managed and native boundary.

The same gallery app is 10 times bigger, despite reduced functionality.
I'll stick with native XAML for now...

App size is a tricky thing to explain because of some cool things that the OS AppxDeploymentServer does.  If you crack open the WinUI 3 Controls Gallery app package, or look at the files it puts on disk after install, you'll see some files like Microsoft.Windows.SDK.NET.dll and Microsoft.WinUI.dll, which are quite large - these are the C#/WinRT projection assemblies for the Windows SDK and WinUI 3.  The good news is that if multiple apps get installed with the same version of these assemblies, the AppxDeploymentServer is smart enough to notice the same files are being deployed multiple times and it will instead link them (I think hardlink?) so they don't exist multiple times on-disk.
This helps when common NuGet libraries are used in apps as you don't pay for multiple copies on disk, but each app can update independently still so it's not the old DLL Hell problem.  It just optimizes disk space automatically as a benefit of being a packaged application.  So you can think of this, in some sense, as a one-time on-disk usage for all of the Windows App SDK, then each app shares these.  The reason the app appears so much larger than using the in-OS version of XAML is that the in-OS XAML version of the app relies on many libraries too (like Windows.UI.Xaml.dll) that are in the system32 folder, instead of coming from a framework package - they still share between processes using the same version of the framework, just like in the WinUI 3 version, but the accounting is different as the OS files aren't counted in the size of the app as seen in Settings.
Internally we are discussing tweaking the deployment model here to possibly put these files in the Windows App SDK Framework Package to make this a bit clearer.  Doing so would not change the disk footprint due to the sharing I mentioned, but it may make it clearer for accounting purposes.
Separately, this thread touched on the topic of IL trimming - currently WinUI 3, like WPF, does not support IL trimming because the XAML markup language and its binary variants (BAML for WPF, XBF for WinUI 3) uses things like Reflection in some cases (such as Binding) to find the right thing to hook up to, or in some cases for type activation entirely.  In the future it may be possible for XAML to inform the IL trimmer about what types/properties it sees as "live" so the trimmer can avoid removing them, but at this time it doesn't so if you trim your WinUI app, you'll very likely find it crashes because things were removed that were only used via markup.  See this similar issue in the WPF repo: https://github.com/dotnet/wpf/issues/3811

I am really concerned about the app size too.
Can someone answer just one question?
What would be my Win UI 3 app size if it were the first app to be installed on a freshly installed Windows 10 OS?

As far as I am aware there are two ways to reduce the size of your WinUI3 app.
If you are creating an unpackaged WinUI app, ensure you do not self-contain the .NET Runtime nor the WinAppSdk Runtime.
If you add the following property to your csproj (https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/use-windows-app-sdk-run-time)
<WindowsAppSDKBootstrapAutoInitializeOptions_OnNoMatch_ShowUI>true</WindowsAppSDKBootstrapAutoInitializeOptions_OnNoMatch_ShowUI>
Your exe will detect if the required WinAppSdk runtime is present on the system, if it isnt, it will prompt the user to download it.
and ensure the following isnt present
true
Your app size will reduce to ~30mb, at least in my testing this is the case

Closing as this appears to have multiple answer comments and has not seen activity since July.

What about publishing to Microsoft Store? Will the MS store download necessary dependency?


Fuzzy Finder continues to search when closed

Not sure if this is possible, but I noticed if I open the fuzzy finder <c-p>, search for something, and then escape before all of the results are returned the search task continues. It would be optimal for it to be cancellable and to do so on exit.

It seems like we can implement an Observable -if we aren’t already- and unsubscribe from the search results by emitting a cancellation event in the case of the fuzzy finder menu exiting or a selection being made. (RxJs or Bluebird)


STORM-1742 More accurate 'complete latency'

PR for 1.x: #1379

Acker computes 'complete latency' and sends back to Spout

start time: Acker receiving ACK_INIT from Spout
end time: Acker receiving ACK message which make the tuple tree completed

When Acker provides complete latency, Spout just uses this value to record that latency

exception case: tuple timed out - Spout doesn't receive failed information from Acker

#1379 contains the result of functional test and performance test. Please refer that pull request.

+1


Adding ilike to model query dsl

Add ilike function in query dsl.
ilike
not_ilike
ilike_starts_with
ilike_ends_with
ilike_contains

@kaplanelad would you mind assigning this ticket to me, please?

Thanks @yinho999, did it.
Please note that like is working only when the engine is postgres. maybe we can add a switch case to support also mysql

Thanks @yinho999, did it. Please note that like is working only when the engine is postgres. maybe we can add a switch case to support also mysql

Should we create a common trait ConditionBuilderTrait which has 3 different implementations of ConditionBuilder (SQLite, MySQL, Postgres)?

@kaplanelad Similar like this file which contains different variant of databases but uses the same trait. Database variant


ERROR Invalid JWT: provided signature is invalid

Hello, I installed a second node on same host and then I start to get the JWT error. I deleted the file, did an etdh update and etdh up but still same error, both showing up on both of my nodes
https://github.com/paradigmxyz/reth/issues/7628

You likely have those in the same docker network. Please make sure you have separate directory names (git clone url dirname); eth-docker dir twice won’t work well.
if you intend for these to be on the same docker network make sure you use different EL_NODE. By default network-execution is available, eg mainnet-execution and holesky-execution.
If you just use “execution” and the two stacks are on the same docker network, docker will round robin, and that’s going to cause failures.
Further discussion on ethstaker Discord please

thanks


[CARBONDATA-2430][SDK] Reshuffling of Columns given by user in SDK.

Reshuffling of Columns given by the user in SDK. Order should be Sort COlumns -> Dimension -> Complex --> Measure

[ ] Any interfaces changed?

[ ] Any backward compatibility impacted?

[ ] Document update required?

[ ] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/5598/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/4437/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/4691/

Retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/5602/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/4441/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/4695/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/4448/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/5609/

It is reorder, not reshuffle. Better to modify the title of PR and commit

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/4702/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/4703/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/5623/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/4463/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/4716/

Retest this please

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/5630/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/4470/

Retest this please

Retest this please

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/4477/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/4480/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/5640/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/4719/

Retest this please

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/5648/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/4488/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/5655/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/5657/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/4732/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/4734/

Retest this please

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/5687/

Retest this please.

@ravipesala Refactoring of Building schema will be done as part of a separate PR as the changes are more and can impact the CarbonTable creation.

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/4532/

LGTM

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/4762/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/4764/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/4770/


Implemented Player Screen for demo

Implemented Player screen and will be adding more functionality

merging being a long pending PR


Update labeler.yml

Change all tags to "demos"
Fix typo in docs-agent config
Description of the change

Motivation

Type of change
Choose one: (Bug fix | Feature request | Documentation | Other)
Checklist

[x] I have performed a self-review of my code.
[x] I have added detailed comments to my code where applicable.
[x] I have verified that my change does not break existing code.
[x] My PR is based on the latest changes of the main branch (if unsure, please run git pull --rebase upstream main).
[x] I am familiar with the Google Style Guide for the language I have coded in.
[x] I have read through the Contributing Guide and signed the Contributor License Agreement.

Do we need to update the list of labels too?
https://github.com/google/generative-ai-docs/labels

Do we need to update the list of labels too?
https://github.com/google/generative-ai-docs/labels

Yes, planned to time the update with the merge, which I'll do now.


[bug]: Mobile sidebar doesn't play nice with Clerk popup

Describe the bug

I place the Clerk signed-in user button on my sidebar, and this button is impossible to click on any screen where the sidebar is an overlay.

This appears to be because the sidebar's interaction area overrides the clerk button.
    <Sidebar variant="floating" collapsible="offcanvas">
      <SidebarHeader>

          Workspace
          <SignedIn>

              <UserButton
                appearance={{
                  baseTheme: darkMode ? dark : undefined,
                }}
              />

          </SignedIn>

      </SidebarHeader>

I've tried using tailwind to adjust the relative z but no luck so far.
Affected component/components
Sidebar
How to reproduce

Add Sidebar
Add Clerk signed in button to sidebar.

Codesandbox/StackBlitz link
No response
Logs
No response
System Info
Chrome 129
macOS 15
Vite 5.4.2

Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues

I found a way to "fix" this issue by adding the following css
.cl-organizationSwitcherPopoverRootBox {
  pointer-events: auto;
}

Also connecting the issue on clerk about that https://github.com/clerk/javascript/issues/4373


Ignore capitalization for alphabetizing streams in the "Move topic" and "Move messages" modals

In the "Move topic" and "Move messages" modals, the streams dropdown is sorted with streams names beginning with capital letters first. Instead, we should alphabetize stream names ignoring capitalization, as we do elsewhere in the app (e.g., the left sidebar).

@zulipbot claim

@alya I am interested in resolving this issue can you please assign me to the issue.

@zulipbot claim

@zulipbot claim

@zulipbot claim

@zulipbot claim

Hii where can i get the code of this ?

@zulipbot where can i get the code of this?


Configuration for rule "react/jsx-handler-names" is invalid

When I add the following part to my .eslintrc.js:
'react/jsx-handler-names': ['error', {
    eventHandlerPrefix: 'handle',
    eventHandlerPropPrefix: 'on',
    checkLocalVariables: false,
}],

The following error gets thrown:
Error: --config:
	Configuration for rule "react/jsx-handler-names" is invalid:
	Value {"eventHandlerPrefix":"handle","eventHandlerPropPrefix":"on","checkLocalVariables":false} should NOT have additional properties.
	Value {"eventHandlerPrefix":"handle","eventHandlerPropPrefix":"on","checkLocalVariables":false} should NOT have additional properties.
	Value {"eventHandlerPrefix":"handle","eventHandlerPropPrefix":"on","checkLocalVariables":false} should NOT have additional properties.
	Value {"eventHandlerPrefix":"handle","eventHandlerPropPrefix":"on","checkLocalVariables":false} should match exactly one schema in oneOf.

ESLint: 6.6.0
ESLint plugin React: 7.16.0
Please let me know if you need any more information.

Seems like you're reading the docs from master, which is unreleased; always check the docs from the proper version tag: https://github.com/yannickcr/eslint-plugin-react/blob/v7.16.0/docs/rules/jsx-handler-names.md

Thanks for the reply @ljharb !


Things You Should Know

FYI @stefsch
I will need a code review for this before I merge it in. Will work with Linux team to get SME coverage

Thanks to @stefsch and @EricSten-MSFT for review comments, I think I have addressed all the feedback. I'm going to wait till Friday to merge this in case anyone else form Linux team can take a pass.