DocuSign Demo Connector (Certified Connector) - Add documents to envelope

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 :)

[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.
[ ] 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.

@ Srikanth:
Thanks for the code review feedback. I will go ahead and add a schema.
Can I add a subset of the API response fields in the schema ?
Basically I want to add only the fields we think the user will care about.
That way if something changes in the API response there is minimal
maintenance that is needed as well.
What are your thoughts on this ?
Thanks
Srihari
On Tue, Nov 2, 2021 at 3:18 PM Srikanth Yenagandhula <
@.***> wrote:

@.**** requested changes on this pull request.
In certified-connectors/DocuSignDemo/apiDefinition.swagger.json
https://urldefense.com/v3/__https://github.com/microsoft/PowerPlatformConnectors/pull/1237*discussion_r741500423__;Iw!!BN3BN5aqUA!r5dcjKDZwdFxpdbnMxIjuza64_XoR_uTVZIx7AaF2710vo7a174O5ZyNBSc0FSAkCweUxO4q$
:

@@ -1005,6 +1005,84 @@
},
"deprecated": false,
"x-ms-visibility": "internal"

 },

 "put": {

   "responses": {

     "default": {

       "description": "default",

       "schema": {}

@sriharip-docusign
https://urldefense.com/v3/__https://github.com/sriharip-docusign__;!!BN3BN5aqUA!r5dcjKDZwdFxpdbnMxIjuza64_XoR_uTVZIx7AaF2710vo7a174O5ZyNBSc0FSAkC3vCuVBH$
Empty response schema is not allowed anymore, which means no dynamic
content will be shown in the output and makers have to use parse JSON to
parse the response. Please provide a valid response schema definition for
all the operations in the swagger.
In certified-connectors/DocuSignDemo/apiDefinition.swagger.json
https://urldefense.com/v3/__https://github.com/microsoft/PowerPlatformConnectors/pull/1237*discussion_r741500517__;Iw!!BN3BN5aqUA!r5dcjKDZwdFxpdbnMxIjuza64_XoR_uTVZIx7AaF2710vo7a174O5ZyNBSc0FSAkC131-FD4$
:

@@ -1005,6 +1005,84 @@
},
"deprecated": false,
"x-ms-visibility": "internal"

 },

 "put": {

   "responses": {

     "default": {

       "description": "default",

@sriharip-docusign
https://urldefense.com/v3/__https://github.com/sriharip-docusign__;!!BN3BN5aqUA!r5dcjKDZwdFxpdbnMxIjuza64_XoR_uTVZIx7AaF2710vo7a174O5ZyNBSc0FSAkC3vCuVBH$
Default responses are not allowed anymore, which means no dynamic content
will be shown in the output and makers have to use parse JSON to parse the
response. Please provide a valid response schema definition for all the
operations in the swagger.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://urldefense.com/v3/__https://github.com/microsoft/PowerPlatformConnectors/pull/1237*pullrequestreview-795964732__;Iw!!BN3BN5aqUA!r5dcjKDZwdFxpdbnMxIjuza64_XoR_uTVZIx7AaF2710vo7a174O5ZyNBSc0FSAkC-HPPkKl$,
or unsubscribe
https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AVRJBQW3VWH5MJTEHKOCAILUKBWTJANCNFSM5HG6LX6A__;!!BN3BN5aqUA!r5dcjKDZwdFxpdbnMxIjuza64_XoR_uTVZIx7AaF2710vo7a174O5ZyNBSc0FSAkC5wZZPDZ$
.
Triage notifications on the go with GitHub Mobile for iOS
https://urldefense.com/v3/__https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675__;!!BN3BN5aqUA!r5dcjKDZwdFxpdbnMxIjuza64_XoR_uTVZIx7AaF2710vo7a174O5ZyNBSc0FSAkC1RgZVsK$
or Android
https://urldefense.com/v3/__https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign*3Dnotification-email*26utm_medium*3Demail*26utm_source*3Dgithub__;JSUlJSU!!BN3BN5aqUA!r5dcjKDZwdFxpdbnMxIjuza64_XoR_uTVZIx7AaF2710vo7a174O5ZyNBSc0FSAkC8ZmTGG9$.

@ Srikanth:
I have added the schema and also made one more change to backport the
changes made in prod connector to demo connector.
On Wed, Nov 3, 2021 at 10:02 AM Srihari Padmanabhan <
@.***> wrote:

@ Srikanth:
Thanks for the code review feedback. I will go ahead and add a schema.
Can I add a subset of the API response fields in the schema ?
Basically I want to add only the fields we think the user will care about.
That way if something changes in the API response there is minimal
maintenance that is needed as well.
What are your thoughts on this ?
Thanks
Srihari
On Tue, Nov 2, 2021 at 3:18 PM Srikanth Yenagandhula <
@.***> wrote:

@.**** requested changes on this pull request.
In certified-connectors/DocuSignDemo/apiDefinition.swagger.json
https://urldefense.com/v3/__https://github.com/microsoft/PowerPlatformConnectors/pull/1237*discussion_r741500423__;Iw!!BN3BN5aqUA!r5dcjKDZwdFxpdbnMxIjuza64_XoR_uTVZIx7AaF2710vo7a174O5ZyNBSc0FSAkCweUxO4q$
:

@@ -1005,6 +1005,84 @@
},
"deprecated": false,
"x-ms-visibility": "internal"

 },

 "put": {

   "responses": {

     "default": {

       "description": "default",

       "schema": {}

@sriharip-docusign
https://urldefense.com/v3/__https://github.com/sriharip-docusign__;!!BN3BN5aqUA!r5dcjKDZwdFxpdbnMxIjuza64_XoR_uTVZIx7AaF2710vo7a174O5ZyNBSc0FSAkC3vCuVBH$
Empty response schema is not allowed anymore, which means no dynamic
content will be shown in the output and makers have to use parse JSON to
parse the response. Please provide a valid response schema definition for
all the operations in the swagger.
In certified-connectors/DocuSignDemo/apiDefinition.swagger.json
https://urldefense.com/v3/__https://github.com/microsoft/PowerPlatformConnectors/pull/1237*discussion_r741500517__;Iw!!BN3BN5aqUA!r5dcjKDZwdFxpdbnMxIjuza64_XoR_uTVZIx7AaF2710vo7a174O5ZyNBSc0FSAkC131-FD4$
:

@@ -1005,6 +1005,84 @@
},
"deprecated": false,
"x-ms-visibility": "internal"

 },

 "put": {

   "responses": {

     "default": {

       "description": "default",

@sriharip-docusign
https://urldefense.com/v3/__https://github.com/sriharip-docusign__;!!BN3BN5aqUA!r5dcjKDZwdFxpdbnMxIjuza64_XoR_uTVZIx7AaF2710vo7a174O5ZyNBSc0FSAkC3vCuVBH$
Default responses are not allowed anymore, which means no dynamic content
will be shown in the output and makers have to use parse JSON to parse the
response. Please provide a valid response schema definition for all the
operations in the swagger.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://urldefense.com/v3/__https://github.com/microsoft/PowerPlatformConnectors/pull/1237*pullrequestreview-795964732__;Iw!!BN3BN5aqUA!r5dcjKDZwdFxpdbnMxIjuza64_XoR_uTVZIx7AaF2710vo7a174O5ZyNBSc0FSAkC-HPPkKl$,
or unsubscribe
https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AVRJBQW3VWH5MJTEHKOCAILUKBWTJANCNFSM5HG6LX6A__;!!BN3BN5aqUA!r5dcjKDZwdFxpdbnMxIjuza64_XoR_uTVZIx7AaF2710vo7a174O5ZyNBSc0FSAkC5wZZPDZ$
.
Triage notifications on the go with GitHub Mobile for iOS
https://urldefense.com/v3/__https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675__;!!BN3BN5aqUA!r5dcjKDZwdFxpdbnMxIjuza64_XoR_uTVZIx7AaF2710vo7a174O5ZyNBSc0FSAkC1RgZVsK$
or Android
https://urldefense.com/v3/__https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign*3Dnotification-email*26utm_medium*3Demail*26utm_source*3Dgithub__;JSUlJSU!!BN3BN5aqUA!r5dcjKDZwdFxpdbnMxIjuza64_XoR_uTVZIx7AaF2710vo7a174O5ZyNBSc0FSAkC8ZmTGG9$.

@ Srikanth: Thanks for the code review feedback. I will go ahead and add a schema. Can I add a subset of the API response fields in the schema ? Basically I want to add only the fields we think the user will care about. That way if something changes in the API response there is minimal maintenance that is needed as well. What are your thoughts on this ? Thanks Srihari
…
On Tue, Nov 2, 2021 at 3:18 PM Srikanth Yenagandhula < @.> wrote: @.* requested changes on this pull request. ------------------------------ In certified-connectors/DocuSignDemo/apiDefinition.swagger.json <https://urldefense.com/v3/https://github.com/microsoft/PowerPlatformConnectors/pull/1237*discussion_r741500423;Iw!!BN3BN5aqUA!r5dcjKDZwdFxpdbnMxIjuza64_XoR_uTVZIx7AaF2710vo7a174O5ZyNBSc0FSAkCweUxO4q$> : > @@ -1005,6 +1005,84 @@ }, "deprecated": false, "x-ms-visibility": "internal" + }, + "put": { + "responses": { + "default": { + "description": "default", + "schema": {} @sriharip-docusign <https://urldefense.com/v3/https://github.com/sriharip-docusign;!!BN3BN5aqUA!r5dcjKDZwdFxpdbnMxIjuza64_XoR_uTVZIx7AaF2710vo7a174O5ZyNBSc0FSAkC3vCuVBH$> Empty response schema is not allowed anymore, which means no dynamic content will be shown in the output and makers have to use parse JSON to parse the response. Please provide a valid response schema definition for all the operations in the swagger. ------------------------------ In certified-connectors/DocuSignDemo/apiDefinition.swagger.json <https://urldefense.com/v3/https://github.com/microsoft/PowerPlatformConnectors/pull/1237*discussion_r741500517;Iw!!BN3BN5aqUA!r5dcjKDZwdFxpdbnMxIjuza64_XoR_uTVZIx7AaF2710vo7a174O5ZyNBSc0FSAkC131-FD4$> : > @@ -1005,6 +1005,84 @@ }, "deprecated": false, "x-ms-visibility": "internal" + }, + "put": { + "responses": { + "default": { + "description": "default", @sriharip-docusign <https://urldefense.com/v3/https://github.com/sriharip-docusign;!!BN3BN5aqUA!r5dcjKDZwdFxpdbnMxIjuza64_XoR_uTVZIx7AaF2710vo7a174O5ZyNBSc0FSAkC3vCuVBH$> Default responses are not allowed anymore, which means no dynamic content will be shown in the output and makers have to use parse JSON to parse the response. Please provide a valid response schema definition for all the operations in the swagger. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://urldefense.com/v3/https://github.com/microsoft/PowerPlatformConnectors/pull/1237*pullrequestreview-795964732;Iw!!BN3BN5aqUA!r5dcjKDZwdFxpdbnMxIjuza64_XoR_uTVZIx7AaF2710vo7a174O5ZyNBSc0FSAkC-HPPkKl$>, or unsubscribe <https://urldefense.com/v3/https://github.com/notifications/unsubscribe-auth/AVRJBQW3VWH5MJTEHKOCAILUKBWTJANCNFSM5HG6LX6A;!!BN3BN5aqUA!r5dcjKDZwdFxpdbnMxIjuza64_XoR_uTVZIx7AaF2710vo7a174O5ZyNBSc0FSAkC5wZZPDZ$> . Triage notifications on the go with GitHub Mobile for iOS <https://urldefense.com/v3/https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675;!!BN3BN5aqUA!r5dcjKDZwdFxpdbnMxIjuza64_XoR_uTVZIx7AaF2710vo7a174O5ZyNBSc0FSAkC1RgZVsK$> or Android <https://urldefense.com/v3/https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign3Dnotification-email26utm_medium3Demail26utm_source*3Dgithub;JSUlJSU!!BN3BN5aqUA!r5dcjKDZwdFxpdbnMxIjuza64_XoR_uTVZIx7AaF2710vo7a174O5ZyNBSc0FSAkC8ZmTGG9$>.

You can add the required fields in the schema, but the schema definition is important to add for all the responses.

Hello PowerAutomate team
I am trying to have a drop down of values with the added ability for users
to enter a custom value.
How do I do that.
Currently I see an error when I specify a custom value that is not part of
the enum values.
Flow save failed with code 'OpenApiOperationParameterValidationFailed' and
message 'Input parameter 'body' validation failed in workflow operation
'Add_documents': The API operation 'AddDocumentsToEnvelope' requires the
property 'body/documents/0/fileExtension' to be set to one of its defined
enum values '["pdf","docx","doc","xlsx","xls","jpg"]' but is set to 'txt'.'.
[image: image.png]
[image: image.png]
Thanks
Sri

Hi Shyam
If you could answer my previous question when you find time.
Also , Is openapi 3.0.0 supported for the apiDefinition.swagger.json ? Do
you guys have any deprecation plan for 2.0 version
Thanks
On Wed, Jan 5, 2022 at 2:00 PM Srihari Padmanabhan <
@.***> wrote:

Hello PowerAutomate team
I am trying to have a drop down of values with the added ability for users
to enter a custom value.
How do I do that.
Currently I see an error when I specify a custom value that is not part of
the enum values.
Flow save failed with code 'OpenApiOperationParameterValidationFailed' and
message 'Input parameter 'body' validation failed in workflow operation
'Add_documents': The API operation 'AddDocumentsToEnvelope' requires the
property 'body/documents/0/fileExtension' to be set to one of its defined
enum values '["pdf","docx","doc","xlsx","xls","jpg"]' but is set to 'txt'.'.
[image: image.png]
[image: image.png]
Thanks
Sri


Bug: TOC inlinecode items not clickable on initial load unless you scroll down

Context:
https://prisma-company.slack.com/archives/C5Z9TH6N9/p1630530197025600

This now works (more) as expected and is properly clickable 👍


[BUG] screen displaying categories shouldn't be scrollable

Description

This is the starting screen.

It is slightly scrollable.

Which shouldn't happen at all, since there is weird styling at the bottom, and removing ability to scroll would improve UX.
Screenshots
No response
Any additional information?
@rupali-codes  @CBID2
What do you think?
Please don't unlock the conversation, unless it is decided. Then we can make it open for others to grab.
What browser are you seeing the problem on?
Chrome
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[ ] I am willing to work on this issue (optional)

@Anmol-Baranwal i think we can go for it :)

Hey @rupali-codes i want to work on this issue. Can you please assign it to me so i can get started ? Thanks.

Hi @rupali-codes   I am really interested to work on this issue, I am currently a fullstack developer pursuing undergrad at IIT's , Could you please assign me this issue.

Hi @rupali-codes I am really interested to work on this issue, I am currently a fullstack developer pursuing undergrad at IIT's , Could you please assign me this issue.

Ketansaresa asked first, so I'm assigning this issue to him.
@ketansaresa
I have assigned you the issue. Please proceed with it, and don't hesitate to tag me @Anmol-Baranwal or @CBID2 if you require any assistance.

Thank you @Anmol-Baranwal


MSID: 89493 Version: 1 DOI: 2<IP_ADDRESS>6936

"msas": "Chromosomes and Gene Expression", "Genetics and Genomics"
"msid": "89493"
"preprintDoi": "10.1101/2<IP_ADDRESS>6936"
"Reviewed Preprint posted": "2023-09-05"
"Sent for peer review": "2023-07-11"
"Posted to bioRxiv": "2023-08-20" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>6936v2/")
[PLACE PDF URL HERE WHEN AVAILABLE] See step 7
Step 1. Inform bioRxiv
Who can help: @QueenKraken, @nlisgo, @scottaubrey

[x] Manuscript is in data hub index (https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v1/by-publisher/elife/get-by-manuscript-id?manuscript_id=89493)

Step 2. Create preview of manuscript
Who can help: @fred-atherden, @nlisgo, @scottaubrey

[ ] Manuscript is available for preview (https://prod--epp.elifesciences.org/preview/89493/v1)

[ ] Trigger import for staging: https://prod--epp.elifesciences.org/import
[ ] Sync data folder with s3://prod-elife-epp-data/data
[ ] Trigger import for staging: https://staging--epp.elifesciences.org/import
[ ] Sync data folder with s3://staging-elife-epp-data/data
[ ] Pull request created to enhanced-preprint-data
[ ] Post link to pull request below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-manuscript
Step 3: Awaiting public reviews and QC
Who can help: Production team

[ ] QC passed or QC not needed

Who can help: Editorial team

[x] Public reviews available on sciety (https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>6936)
[x] Manuscript and editor details at the top of this issue (Supplied by Editorial team)
[x] Reviews returned by EPP - https://prod--epp.elifesciences.org/api/reviewed-preprints/89493/v1/reviews

Example
"msas": "Genetics and Genomics", "Neuroscience"
"msid": "84628"
"version": "1"
"preprintDoi": "10.1101/2<IP_ADDRESS>4241"
"articleType": "Reviewed Preprint"
"status": "Published from the original preprint after peer review and assessment by eLife."

"Reviewed Preprint posted": "2023-01-02"
"Sent for peer review": "2022-10-28"
"Posted to bioRxiv": "2022-11-21" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>4241v1")

Editors:
Reviewing Editor
Michael B Eisen
University of California, Berkeley, United States
Senior Editor
Michael B Eisen
University of California, Berkeley, United States

Step 4: Modify manuscripts.json (no PDF)

[ ] Reviewed preprint is published to EPP (https://elifesciences.org/reviewed-preprints/89493)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[ ] Request that a doi be registered

[ ] Post link to #enhanced-preprint comment below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]

Instructions to modify manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/publish-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/334/files
Once the pull request is merged in it should be available a few minutes later.

Request that a doi
Post the following in #enhanced-preprint:
@Fred can you register a doi for https://elifesciences.org/reviewed-preprints/89493

Step 5: Awaiting search reindex

[ ] Reviewed preprint is avaliable on journal homepage (https://elifesciences.org)

The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.

Additional info
If needed, the jenkins pipeline to reindex search can be triggered sooner.
https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 6: Published! Request PDF generation

[ ] Post the link to the PDF url at the top of the issue

[ ] Post link to #enhanced-preprint comment below

#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]
Post the following to the #enhanced-preprint on slack:
@Ryan Dix-Peek please can you generate a PDF for https://elifesciences.org/reviewed-preprints/89493

Step 7: Introduce PDF to data folder and git repo

[ ] PDF is avaliable at https://github.com/elifesciences/enhanced-preprints-data/raw/master/data/89493/v1/89493-v1.pdf

Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-pdf
Step 8: Add PDF url to manuscripts.json

[ ] Reviewed preprint PDF is available for download (https://prod--epp.elifesciences.org/reviewed-preprints/89493)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[PLACE LINK TO PULL REQUEST HERE]

Instructions to add PDF url to manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/add-pdf-url-to-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/397/files
Once the pull request is merged in it should be available a few minutes later.

Step 9: Done!

[ ] Kettle is on!

Extended data figures images are missing. Going to proceed with this v1 with this issue.
@acollings do you think this something we could address with the next version? I see the authors have an R2 but it's marked as Halted Manuscript Deleted in eJP, so not sure what stage they are at. If they are about to post a new version, I don't want to confuse things by asking them to correct this version.

Hi @fred-atherden yes, I think we'll receive a revised version in due course. I think they started a revised version too early, so we've reset it. Not sure when we're expecting the revised version.

OK thanks


Repo-wide prettier formating configuration

We use prettier plugins to format files across the whole repo. Especially we want to format toml and sh files.
This PR contains the configuration of prettier plugins in the root directory.
Directories like solidity and stakers-rewards were excluded from this global formatting check as they have their own configuration based on eslint and prettier.
The check was included in pre-commit-hooks and GitHub Actions. After merging this PR to master we can make code-format job required in the branch protection rules.
We've run the auto-formatter and committed a fixed code as well.
We also removed GO111MODULE=on env variable from Dockerfile as it's no longer necessary with Go 1.13 (ref).

Also, if we can reference prettier-config-keep from eslint-config-keep that'd be awesome. If not, let's see if we can make prettier-config-keep rooted in the same rules eslint-config-keep applies for prettier (based on the Google style guide I guess?).

I was able to reference the prettier rules in eslint-config-keep in https://github.com/keep-network/eslint-config-keep/pull/9 :tada:

In keeping with convention, let's clean up the git history and separate out all of the changes-to-linting from changes-from-the-linter. Then, we slap the changes-from-the-linter commits with the .git-blame-ignore-revs treatment: https://www.moxio.com/blog/43/ignoring-bulk-change-commits-with-git-blame

@beaushinkle It's ready.


Change mentions of system to QPU

I ran a ripgrep search and these are the files to check:

[ ] transpile/transpiler-plugins.ipynb
[ ] run/retired-systems.mdx
[ ] run/execution-modes-faq.mdx
[ ] run/fair-share-queue.mdx
[ ] run/max-execution-time.mdx
[ ] run/primitives-get-started.mdx
[ ] run/visualize-results.ipynb
[ ] run/circuit-execution.mdx
[ ] run/configure-error-mitigation.mdx
[ ] run/estimate-job-run-time.mdx
[ ] run/advanced-runtime-options.mdx
[ ] run/index.mdx
[ ] run/manage-cost.mdx
[ ] run/sessions.mdx
[ ] run/_toc.json
[ ] run/execution-modes.mdx
[ ] build/pulse.ipynb
[ ] run/quantum-serverless.mdx
[ ] build/introduction-to-qasm.mdx
[ ] run/native-gates.mdx
[ ] build/unitary-synthesis.mdx
[ ] run/primitives-examples.mdx
[ ] run/monitor-job.mdx
[ ] run/processor-types.mdx
[ ] run/instances.mdx
[ ] build/operator-class.ipynb
[ ] build/qasm-feature-table.mdx
[ ] run/dynamic-circuits-considerations.ipynb
[ ] run/run-jobs-in-session.mdx
[ ] run/system-information.mdx
[ ] run/primitives.mdx
[ ] build/circuit-library.ipynb
[ ] build/operators-overview.ipynb
[ ] run/run-jobs-batch.mdx
[ ] transpile/defaults-and-configuration-options.ipynb
[ ] transpile/index.mdx
[ ] transpile/transpiler-stages.ipynb
[ ] run/configure-runtime-compilation.mdx
[ ] transpile/representing_quantum_computers.ipynb
[ ] support.mdx
[ ] build/specify-observables-pauli.mdx
[ ] transpile/custom-transpiler-pass.ipynb
[ ] transpile/create-a-transpiler-plugin.ipynb
[ ] start/hello-world.ipynb
[ ] verify/simulate-with-qiskit-primitives.mdx
[ ] verify/stabilizer-circuit-simulation.ipynb
[ ] verify/local-testing-mode.ipynb
[ ] verify/index.mdx
[ ] verify/plot-quantum-states.ipynb
[ ] verify/simulate-with-qiskit-aer.ipynb
[ ] start/install.mdx
[ ] start/setup-channel.mdx
[ ] verify/building_noise_models.ipynb
[ ] start/install-qiskit-source.mdx
[ ] start/index.mdx
[ ] start/configure-qiskit-local.mdx

Migration guides:

[ ] qiskit-runtime.mdx
[ ] qiskit-1.0-installation.mdx - all instances do not need changing
[ ] v2-primitives.mdx
[ ] local-simulators.mdx
[ ] qiskit-runtime-use-case.mdx
[ ] qiskit-quantum-instance.mdx
[ ] qiskit-1.0-features.mdx
[ ] sessions.mdx
[ ] qiskit-runtime-examples.mdx
[ ] qiskit-runtime-options.mdx
[ ] qiskit-opflow-module.mdx
[ ] qiskit-algorithms-module.mdx

Keep "system" as-is in this sentence?: ...when trying to discover the extremal energy of a system (found in /api/migration-guides/qiskit-runtime)

Do we change "quantum systems" to QPUs here?: Simulators are valuable for understanding small-scale quantum systems (seen in api/migration-guides/local-simulators)

The merge conflicts post-reorg are such that it will be less work to simply open a new PR. Closing this one.


GUI not showing

Hi! This project looks great, but I haven't been able to make things work. I've tried showing a data frame on a notebook, as in the tutorials/demos, and also the command mk demo tutorial-image-gallery --copy. In both cases (the notebook and the browser), all I see is an image with the meerkat logo, not the data frame or the gallery that I was expecting.

Might I be doing something obviously wrong?

@fepegar thanks for the note! could you share a few specifics about your setup:

OS

if you are using windows, you may have to use the windows subsystem for linux

Is the program running on remote or local machine?
is there any error on the browser console? on chrome you can access this via View -> Developer -> Javascript Console

Possible solutions
Remote machines require port forwarding
If you are using a remote machine, you'll need to forward the frontend and api ports (8000 and 5000 by default)
Change the api/frontend ports
you can change the ports you are forwarding with mk demo tutorial-image-gallery --api-port XXXX --frontend-port XXXX

Hi, @ad12. Thanks for your quick response. I was trying on Linux, remotely. I did forward the ports: I guess that's why I could see the logo.
I did quickly check the browser console and I think something was off. Let me confirm that and also try things locally.

The browser issue was my mistake: I was going to http://localhost:8001/ instead of http://localhost:8001/?id=gallery.
I'll try the notebook again. I guess I don't need to forward ports for that, right?

You will need to forward the api/frontend ports from the notebook as well. By default the ports are 5000 and 8000


File system scheme '[local]' not implemented on TPU

Hello, I have a task to train a model with millions of images using TPU, so I plan to load local data batch by batch when training. The main function to load data is shown below.
`def batch_processing(image):
image1 = tf.image.decode_jpeg(tf.io.read_file(image), 3)
return tf.image.resize(image1, [IMGSIZE, IMGSIZE])/255.
def data_loading(path, data, batch, buffer=1000, training=False):
img1, start1 = [], 0
while start1 < len(data):
    path1 = data['image_id'][start1:start1+buffer]
    img1 += path1.apply(lambda x: path+'train/'+x[0]+'/'+x[1]+'/'+x[2]+'/'+x+'.png').tolist()
    start1 += buffer

set1 = tf.data.Dataset.from_tensor_slices((img1))
set1 = set1.map(batch_processing, num_parallel_calls=AUTOTUNE)
set1 = set1.shuffle(buffer).batch(batch) if training else set1.batch(batch)
set1 = set1.prefetch(buffer_size=AUTOTUNE)
return tpu_strategy.experimental_distribute_datasets_from_function(lambda _: set1)`

However, I have got an error "File system scheme '[local]' not implemented". Since this code works on GPU, I think such local file scheme isn't supported on TPU currently. Could you please tell me how to deal with this problem, when I have too many local images to load?
Thank you!

Instead of using something like tf.io use os or PIL
https://stackoverflow.com/questions/62870656/file-system-scheme-local-not-implemented-in-google-colab-tpu

Instead of using something like tf.io use os or PIL
https://stackoverflow.com/questions/62870656/file-system-scheme-local-not-implemented-in-google-colab-tpu

I see, thank you.

See also https://github.com/google-research/language/issues/54


How to do the bulk update .?

I have to do one POC and that to be update/delete operation on bulk . I have done same kind of POC on DeltaLake , which went well , but due to some unavoidable circumstances I have to look    Hudi is my next course of action. It will be rally helpful ,If you could guide me to do this operation . I did not find and suitable documentation which  help me .
Will be great help if somebody help me to understand this.

@sanjiv1980 are you looking to bulk convert an existing data set? Not sure I completely follow along. If you can help clarify, happy to help out..
Some resources
https://hudi.apache.org/migration_guide.html
https://cwiki.apache.org/confluence/display/HUDI/FAQ#FAQ-HowdoImigratemydatatoHudi

@vinothchandar Thanks for prompt reply , Actually we have existing  data-lake which contains around 5-years of historical data (near about in petabytes) , on top of that so many existing jobs are running, recently I have one use case where I need to update/delete existing user data based on their unique identification.
For that I did one POC on Delta-Lake( I formed delta-lake (for one month data) and then run the delta lake API to perform update/delete operation) , which went well , but somehow we are not satisfy with timeline which has been taken by delta-lake.(compaction is one of the concern) , which I saw in your documentation, like It has handled significantly well. So I wanted to evaluate the same thing on HUDI.
My job nature is to either update/delete those records. after that same data can be sharable with other job to do the further evaluation .
Hope you understand my job nature.

that helps!  So I would suggest the following concrete steps

Do a first bulk import for the same one month of data.. spark.read.parquet("your_data_set/path/to/month").write.format("org.apache.hudi"), but use the BULK_INSERT operatoin as shown here. https://hudi.apache.org/quickstart.html#inserts . But seems like you may need merge_on_read storage type?

Then you can proceed to upsert the dataset as documented again in quickstart.. You can either schedule compaction as a background job or for now use CLI to trigger the compactions manually to play around.. @bvaradar this is worth FAQing.. do you have links for docs to follow here?

Added a FAQ entry : https://cwiki.apache.org/confluence/display/HUDI/FAQ#FAQ-IhaveanexistingdatasetandwanttoevaluateHudiusingportionofthatdata?


Changed the labels and placeholder

PR Description 📜
Fixes #170

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have changed Row input. Label to No of Rows and the placeholder for the input should be "Enter no of rows".
[x] I have changed Column input, Label to No of Columns and the placeholder for the input should be "Enter no of columns".
[x] I have changed Players Input Label to No of Players and the placeholder for the input should be "Enter no of players"
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for review.

Add your screenshots(Optional) 📸

Also, I just found out that there was already labels in each input before. You can revert the labels to the previous ones but change the color so that it can become more noticable

The Label Text color should be the same color and font size of the span element that says (between 5 and 30) Also the placeholder should only show id there is no default value in the input element.

Yes I understood and changed it, but can you clarify that do I have to change the font size of span element that says (between 5 and 30)?

Yes, I made the labels more noticable and reverted the labels to the previous ones.
Also only if the inputs are empty that's when the placeholder shown and added a CSS styling to the placeholder font.
Is there any other changes required?

Yes, I made the labels more noticable and reverted the labels to the previous ones.
Also only if the inputs are empty that's when the placeholder shown and added a CSS styling to the placeholder font.
Is there any other changes required?

Can you include a screenshot. I’ll do a proper review soon

Yes, I made the labels more noticable and reverted the labels to the previous ones.
Also only if the inputs are empty that's when the placeholder shown and added a CSS styling to the placeholder font.
Is there any other changes required?

Can you include a screenshot. I’ll do a proper review soon

When the game is started, there is a default value in each input

When the inputs are empty that's when the placeholder is shown

It's already being 2 days please review it soon

Yes, I made the labels more noticable and reverted the labels to the previous ones.
Also only if the inputs are empty that's when the placeholder shown and added a CSS styling to the placeholder font.
Is there any other changes required?

Can you include a screenshot. I’ll do a proper review soon

It's already being 2 days please review it soon...

This is perfect
I’ll review it today
Will drop comments if it’s needed

Why the changes are not reflecting in the webpage? @Lovelyfin00


No option to allow concurrent job templates (allow_simultaneous) when created via the CLI

There is a Tower option via the UI and API to allow the same job to be run concurrently (allow_simultaneous is the API field). This would be really handy.
Thanks!

Thanks for finding these things!


Multiple values for subnets=, securitygroups=. How to use them?

I'd like to create load-balancer with multiple subnets attached, but can't. Scanning the tests I've found some templates, but they didn't work for me. Also I have no clear understanding how wordpress-ha template is deploying, because of lack of variables like {wordpress.subnets}. Could you kindly help me with this?
subnet_1 = create subnet cidr={subnet1.cidr} vpc=$vpc availabilityzone={subnet1.az} name={subnet1.name}
subnet_2 = create subnet cidr={subnet2.cidr} vpc=$vpc availabilityzone={subnet2.az} name={subnet2.name}
...
lbservice = create loadbalancer name={lb.name} subnets=[$subnet_1, $subnet_2] securitygroups=$lbsecgroup

The error log:
[error]   error parsing template at line 28 (char 55):
...
-> lbservice = create loadbalancer name={lb.name} subnets=
...

$ awless version
awless version=v0.1.2, commit=eba3785ddc894b116cf0762e1759c26c459f8077, build-date=2017-08-17T11:20:20+02:00, build-arch=amd64, build-os=linux, build-for=targz

Hi, thanks the feedback.
As you can see in the CHANGELOG, we just implemented a better support for lists in the templating language. This will be in next release (v0.1.3) but is already available on master.
Starting with v0.1.3, you can create lists in template with, for example, subnets = [$subnet1, $subnet2].
Note that before releasing this new version, we will also update templates of awless-templates with this new way to provide lists, which is much more convenient as the previous one.

I have compiled binary from master and able to run my template, thank you. BTW is it possible to import file's content into a variable? Use case is Route53 TXT-record for DKIM, which should contain RSA public-key

Thanks for the suggestion, that's a good use case. I created a new issue for this suggestion (#137).
As this question seems answered, I close this issue.


[numerics] separate out solver steps and collapse into one while loop

Has one extra while loop dedicated to the most common case, but dispenses with having a different loop for every possible combination of options.
Wanted to check at least with @vacary before pushing this one since it might affect current work.  I thought it might help to clean up all those separate loops and avoid having to copy-paste changes all over the file, but let me know if you think it's a bad idea..

ps. if accepted i'll see about porting the openmp branch.. hopefully doesn't cause too much trouble there, but I suppose the openmp for loops would have to remain a separate case.

In fact, I was the author of the splitting to avoid the use of a sensible of switches, conditional statements and declarations on the stack and on the heap.
@bremond told me several times that it was useless to multiply the cases.
If you are sure that the cost of doing the conditional statements in each loop rather than one time is the same or taken into account by optimization. let us merge.

Actually I would say the patch has two goals:

To break the loop up into small pieces so that it is easily understandable and avoids code copying, but still reconfigurable.

A result of the above is that we can compress each while into smaller space, my goal was to be able to see the whole logic in one screen.
I used static functions purposely to make it dead easy for the compiler to inline things.

Secondly, we can still specialise for specific cases as before.  However, I prefer to have all the booleans in one place at the top of each case instead of multiple nested if statements, as I think it's much more clear.

The remaining cases are still taken care of by embedded if statements, which honestly I think have minimal impact for rare cases.  Otherwise there is really a combinatorial explosion of specialisation cases, without C++ templates this is difficult to handle succinctly.

Anyways, mostly trying to reduce space for making mistakes..
All open to opinion of course!

Rebased in c83e92f12f5b69f9d2c2b1b4275c44eee45f0178


Some fields in symbols details request fixed

Fixed a typo, tests and new field added.

thank you.  moving to 'review' category.  will work with bitfinex on merging.


Scout invisibility fixes

add scout effects
fix marine icons appearing when cloaked
fix cloak sounds mispredicting
fix marine icons appearing inside containers

https://github.com/user-attachments/assets/060e21a5-f833-4435-84d3-d87d7fcc3d9b
:cl:

add: Added scout invisibility effects
fix: Fixed scout cloak sound playing more than once

added video


publishPlugin: Any way to publish multiple?

For Rider/ReSharper plugins a build should upload both plugin archives (nupkg + zip). Is there any way to get there?
This is the general repository structure: https://github.com/matkoch/resharper-cognitivecomplexity

all rider plugins require that? Where should it be uploaded and why?

No, not all of them. Let's say it's for ReSharper plugins that also got ported to Rider. You may call them "ReSharper+Rider": they release their builds for both R# and Rider simultaneously.

And they'll go to https://resharper-plugins.jetbrains.com/ Afaik, the endpoint is the same.

AFAIK, the plugin doesn't fit for developing resharper plugins. If you want to upload something, I don't think it should be part of gradle-intellij-plugin. I think creating your own task for that or creating a separate gradle-resharper-uploader plugin are better solutions.

@zolotov it's already there... the only thing missing is the upload: https://github.com/matkoch/resharper-cognitivecomplexity/blob/master/build.gradle#L55-L63

And from user perspective, I only want to call for publishing once.

And from user perspective, I only want to call for publishing once.

It's your build script, you free to configure in any way you want
Publishing code is already shared via org.jetbrains.intellij:plugin-repository-rest-client library, feel free to use
def repoClient = PluginRepositoryFactory.create(host, getToken())
repoClient.uploader.uploadPlugin(pluginId, distributionFile, channel && 'default' != channel ? channel : null, null)

Resolution is the following:

multiple uploads are possible as gradle allows to create as many tasks you need of particular type (e.g. PublishTask)
gradle-intellij-plugin doesn't fit for uploading arbitrary file to plugins.jetbrains.com. There is a dedicated library for that

won't fix


TakeDown Request

@darkestentropy I have Changed The License Of TBomb
So regarding it I am requesting you to Take bombcrack down
Hope that You will understand and not take it in a negative way
I was not actually bothered about this making you to take down till I got heavy request on my server and overloading it which was due to exposed API which might be the effect of this repo
So i kindly request you to take it down...

Negative, @TheSpeedX.
See response of #1.


Simply Dependency Installation

This will drastically reduce the amount of duplicated code for our installs now that we're performing all of them one at a time. The previous approach had required two separate conditionals due to hashes. Since we can apply require hashes on a package-by-package basis now, this division is no longer needed.
It's possible we can remove this all the way up into the Pipfile, but I haven't confirmed that yet. This patch will allow us to fix #377 and we work towards further removal in a future patch.

I'm all for removing code :)

Alright, let's do this then :)


Remove forced text transformation

So for some reason, PlatformText forcefully 'uppercases' any string inputted when used on Material mode.
I fixed this for my use case and I can submit a pull request if needed, but I would like to understand the rationale behind that decision.

That is exactly what PlatformText is meant to do. In some cases you would want to render all uppercase for Android and not for iOS, particularly around buttons. So this widget just makes that easy to achieve without conditionals
If you don't want to uppercase for android then just use the standard Text widget,

Oh, I see. Makes sense, thank you ^^

Would there be a possibility to add a flag useUppercase to PlatformText?
In my use case I need to use PlatformText in order for the PlatformApp's theme to apply, but I still want the text to be the original string and not all uppercase.

Would there be a possibility to add a flag useUppercase to PlatformText?
In my use case I need to use PlatformText in order for the PlatformApp's theme to apply, but I still want the text to be the original string and not all uppercase.

I am not sure why you can't just use Text. There is nothing special about PlatformText other than make the string uppercase for android. Theming should work either way

I don't know either, but on iOS Text is not applying the font family that I set in CupertinoThemeData. PlatformText does apply the text theme.


Fix cloud project toast message not appearing

Pull Request Description

Closes https://github.com/enso-org/cloud-v2/issues/744

Important Notes
None
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] The documentation has been updated, if necessary.
[x] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[x] All code follows the
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[x] Unit tests have been written where possible.
[x] If GUI codebase was changed, the GUI was tested when built using ./run ide build.

tested to check that the fix works - but merged without QA as this one-line change should not be able to affect any other logic apart from the display of the toast notification


Input tiff images

Can we input tiff images?

Yes, you can load the bands manually and pass them directly to the "core engine".
That is explained in the tutorial (https://towardsdatascience.com/water-detection-in-high-resolution-satellite-images-using-the-waterdetect-python-package-7c5a031e3d16) , under the section: Running without GDAL


ErrorException in Builder.php line 1185:

count(): Parameter must be an array or an object that implements Countable

@shammas123  Hi there. Check your PHP version, this error usually happens in PHP 7.2, that's why it isn't supported (yet). Try using PHP 7.1

This error is caused by the PHP version.
Modify line 1185 of the Builder.php file
$originalWhereCount = count ($ query-> wheres);
to
$originalWhereCount = 0;
        if (is_array ($ query-> wheres) || is_object ($ query-> wheres)) {
$originalWhereCount = count ($ query-> wheres);
}


Update export format

Is your feature request related to a problem? Please describe.
Initially we envisioned offering both "Simple" and "Full" data exports; usage suggests just one export format is necessary. Currently the Simple format fails to capture useful information for experiments with multiple decision points, those that use a within-subjects design, and other useful information for analysis.
Describe the solution you'd like
The data export should be updated to reflect the new format here: https://docs.google.com/spreadsheets/d/1qAy7SNklPBWTtJed0Bqc8IppZn5DsQ4nBRsjtP-wtm0/edit#gid=1887655424
Dependencies
Before updating the export format, we should make sure that the new format doesn't result in overly-large file sizes when exporting data with hundreds of thousands of records.

First assumption is that the new format should be a reasonable file size and go from there. If it fails, we'll have to rethink the format and what we want from the export.

@amurphy-cl So, should we go ahead and update the format as per the above attached csv format? Later we can check if the file size is good to handle or not?

@ppratikcr7 That sounds good, thanks

@amurphy-cl So, we want to store each mark details for a user for the same decision point of an experiment?
I tried to check and with the above format we can store around 1 Lakh row data within 40mb file approx.
Do we have a rough idea of what maximum number of mark calls can we have?

@amurphy-cl So, we want to store each mark details for a user for the same decision point of an experiment? I tried to check and with the above format we can store around 1 Lakh row data within 40mb file approx. Do we have a rough idea of what maximum number of mark calls can we have? Note: In this estimate, I haven't added the experiment state sheet. Will we be emailing a xlsx file instead of a csv with the main data sheet and the experiment state sheet?

@amurphy-cl ?


all: Go 1.17.9 release status

Issue tracking the go1.17.9 release by releasebot.

Log
2022/04/12 10:55:24 starting
2022/04/12 10:55:24 working in /Users/dmitshur/go-releasebot-work/go1.17.9
2022/04/12 10:55:24 $ git fetch origin master
2022/04/12 10:55:24 $ git fetch origin release-branch.go1.17
2022/04/12 10:55:33 $ git clone --reference /Users/dmitshur/go-releasebot-work/go1.17.9/gitmirror -b release-branch.go1.17 https://go.googlesource.com/go /Users/dmitshur/go-releasebot-work/go1.17.9/gitwork
2022/04/12 10:55:37 $ git codereview change relwork
2022/04/12 10:55:38 $ git config gc.auto 0
2022/04/12 10:55:38 $ git rev-parse go1.17.9
2022/04/12 10:55:38 Release status issue title: "all: Go 1.17.9 release status"
2022/04/12 10:55:38 Release status issue: https://golang.org/issue/52304
2022/04/12 10:55:38 $ git add VERSION
2022/04/12 10:55:38 $ git commit -m go1.17.9

Change-Id: Id2437003673e7eb1c514f15e6266b93308b7d5e8
 VERSION
2022/04/12 10:55:39 $ git codereview mail -trybot
2022/04/12 10:55:42 $ go clean -modcache
2022/04/12 10:55:42 $ go install golang.org/x/build/cmd/release@latest
2022/04/12 10:56:25 $ /Users/dmitshur/go-releasebot-work/go1.17.9/gopath/bin/release -target linux-386 -user dmitshur -version go1.17.9 -staging_dir /Users/dmitshur/go-releasebot-work/go1.17.9/release-staging/8c5f7011ef5482f8744863934355acf83179095a_1452246591 -rev 8c5f7011ef5482f8744863934355acf83179095a
2022/04/12 10:56:25 $ /Users/dmitshur/go-releasebot-work/go1.17.9/gopath/bin/release -target linux-armv6l -user dmitshur -version go1.17.9 -staging_dir /Users/dmitshur/go-releasebot-work/go1.17.9/release-staging/8c5f7011ef5482f8744863934355acf83179095a_1452246591 -rev 8c5f7011ef5482f8744863934355acf83179095a
2022/04/12 10:56:25 $ /Users/dmitshur/go-releasebot-work/go1.17.9/gopath/bin/release -target windows-amd64-longtest -user dmitshur -version go1.17.9 -staging_dir /Users/dmitshur/go-releasebot-work/go1.17.9/release-staging/8c5f7011ef5482f8744863934355acf83179095a_1452246591 -rev 8c5f7011ef5482f8744863934355acf83179095a
2022/04/12 10:56:25 $ /Users/dmitshur/go-releasebot-work/go1.17.9/gopath/bin/release -target src -user dmitshur -version go1.17.9 -staging_dir /Users/dmitshur/go-releasebot-work/go1.17.9/release-staging/8c5f7011ef5482f8744863934355acf83179095a_1452246591 -rev 8c5f7011ef5482f8744863934355acf83179095a
2022/04/12 10:56:25 $ /Users/dmitshur/go-releasebot-work/go1.17.9/gopath/bin/release -target linux-arm64 -user dmitshur -version go1.17.9 -staging_dir /Users/dmitshur/go-releasebot-work/go1.17.9/release-staging/8c5f7011ef5482f8744863934355acf83179095a_1452246591 -rev 8c5f7011ef5482f8744863934355acf83179095a
2022/04/12 10:56:25 $ /Users/dmitshur/go-releasebot-work/go1.17.9/gopath/bin/release -target freebsd-386 -user dmitshur -version go1.17.9 -staging_dir /Users/dmitshur/go-releasebot-work/go1.17.9/release-staging/8c5f7011ef5482f8744863934355acf83179095a_1452246591 -rev 8c5f7011ef5482f8744863934355acf83179095a
2022/04/12 10:56:25 $ /Users/dmitshur/go-releasebot-work/go1.17.9/gopath/bin/release -target linux-amd64 -user dmitshur -version go1.17.9 -staging_dir /Users/dmitshur/go-releasebot-work/go1.17.9/release-staging/8c5f7011ef5482f8744863934355acf83179095a_1452246591 -rev 8c5f7011ef5482f8744863934355acf83179095a
2022/04/12 10:56:25 $ /Users/dmitshur/go-releasebot-work/go1.17.9/gopath/bin/release -target windows-arm64 -user dmitshur -version go1.17.9 -staging_dir /Users/dmitshur/go-releasebot-work/go1.17.9/release-staging/8c5f7011ef5482f8744863934355acf83179095a_1452246591 -rev 8c5f7011ef5482f8744863934355acf83179095a
2022/04/12 10:56:25 $ /Users/dmitshur/go-releasebot-work/go1.17.9/gopath/bin/release -target windows-386 -user dmitshur -version go1.17.9 -staging_dir /Users/dmitshur/go-releasebot-work/go1.17.9/release-staging/8c5f7011ef5482f8744863934355acf83179095a_1452246591 -rev 8c5f7011ef5482f8744863934355acf83179095a
2022/04/12 10:56:25 $ /Users/dmitshur/go-releasebot-work/go1.17.9/gopath/bin/release -target windows-amd64 -user dmitshur -version go1.17.9 -staging_dir /Users/dmitshur/go-releasebot-work/go1.17.9/release-staging/8c5f7011ef5482f8744863934355acf83179095a_1452246591 -rev 8c5f7011ef5482f8744863934355acf83179095a
2022/04/12 10:56:25 $ /Users/dmitshur/go-releasebot-work/go1.17.9/gopath/bin/release -target darwin-amd64 -user dmitshur -version go1.17.9 -staging_dir /Users/dmitshur/go-releasebot-work/go1.17.9/release-staging/8c5f7011ef5482f8744863934355acf83179095a_1452246591 -rev 8c5f7011ef5482f8744863934355acf83179095a
2022/04/12 10:56:25 $ /Users/dmitshur/go-releasebot-work/go1.17.9/gopath/bin/release -target freebsd-amd64 -user dmitshur -version go1.17.9 -staging_dir /Users/dmitshur/go-releasebot-work/go1.17.9/release-staging/8c5f7011ef5482f8744863934355acf83179095a_1452246591 -rev 8c5f7011ef5482f8744863934355acf83179095a
2022/04/12 10:56:25 $ /Users/dmitshur/go-releasebot-work/go1.17.9/gopath/bin/release -target linux-ppc64le -user dmitshur -version go1.17.9 -staging_dir /Users/dmitshur/go-releasebot-work/go1.17.9/release-staging/8c5f7011ef5482f8744863934355acf83179095a_1452246591 -rev 8c5f7011ef5482f8744863934355acf83179095a
2022/04/12 10:56:25 $ /Users/dmitshur/go-releasebot-work/go1.17.9/gopath/bin/release -target darwin-arm64 -user dmitshur -version go1.17.9 -staging_dir /Users/dmitshur/go-releasebot-work/go1.17.9/release-staging/8c5f7011ef5482f8744863934355acf83179095a_1452246591 -rev 8c5f7011ef5482f8744863934355acf83179095a
2022/04/12 10:56:25 $ /Users/dmitshur/go-releasebot-work/go1.17.9/gopath/bin/release -target linux-s390x -user dmitshur -version go1.17.9 -staging_dir /Users/dmitshur/go-releasebot-work/go1.17.9/release-staging/8c5f7011ef5482f8744863934355acf83179095a_1452246591 -rev 8c5f7011ef5482f8744863934355acf83179095a
2022/04/12 10:56:25 $ /Users/dmitshur/go-releasebot-work/go1.17.9/gopath/bin/release -target linux-amd64-longtest -user dmitshur -version go1.17.9 -staging_dir /Users/dmitshur/go-releasebot-work/go1.17.9/release-staging/8c5f7011ef5482f8744863934355acf83179095a_1452246591 -rev 8c5f7011ef5482f8744863934355acf83179095a
2022/04/12 10:56:25 $ /Users/dmitshur/go-releasebot-work/go1.17.9/gopath/bin/release -target linux-386-longtest -user dmitshur -version go1.17.9 -staging_dir /Users/dmitshur/go-releasebot-work/go1.17.9/release-staging/8c5f7011ef5482f8744863934355acf83179095a_1452246591 -rev 8c5f7011ef5482f8744863934355acf83179095a
2022/04/12 10:56:40 release -target="src": build succeeded (after 0 retries)
2022/04/12 11:00:31 release -target="linux-s390x": build succeeded (after 0 retries)
2022/04/12 11:01:23 release -target="linux-ppc64le": build succeeded (after 0 retries)
2022/04/12 11:07:51 release -target="linux-arm64": build succeeded (after 0 retries)
2022/04/12 11:10:52 release -target="linux-armv6l": build succeeded (after 0 retries)
2022/04/12 11:11:57 release -target="linux-amd64": build succeeded (after 0 retries)
2022/04/12 11:13:41 release -target="darwin-arm64": build succeeded (after 0 retries)
2022/04/12 11:15:24 release -target="freebsd-amd64": build succeeded (after 0 retries)
2022/04/12 11:16:21 release -target="windows-arm64" did not produce expected output files [go1.17.9.windows-arm64.zip go1.17.9.windows-arm64.msi]:
error from cmd/release binary = <nil>
output from cmd/release binary:
2022/04/12 10:56:26 windows-arm64: Start.
2022/04/12 10:56:26 windows-arm64: Creating buildlet.
2022/04/12 11:01:53 windows-arm64: Pushing source to buildlet.
2022/04/12 11:02:04 windows-arm64: Installing go1.4.
2022/04/12 11:02:16 windows-arm64: Writing VERSION file.
2022/04/12 11:02:16 windows-arm64: Cleaning goroot (pre-build).
2022/04/12 11:02:16 windows-arm64: Building (make.bash only).
2022/04/12 11:03:46 windows-arm64: Cleaning goroot (post-build).
2022/04/12 11:03:47 windows-arm64: Pushing and running releaselet.
2022/04/12 11:06:53 windows-arm64: Downloading file from "msi".
2022/04/12 11:07:07 windows-arm64: Wrote "/Users/dmitshur/go-releasebot-work/go1.17.9/release-staging/8c5f7011ef5482f8744863934355acf83179095a_1452246591/go1.17.9.windows-arm64.msi.untested".
2022/04/12 11:07:07 windows-arm64: Cleaning workdir.
2022/04/12 11:07:19 windows-arm64: Downloading tarball and re-compressing as zip.
2022/04/12 11:07:39 windows-arm64: Wrote "/Users/dmitshur/go-releasebot-work/go1.17.9/release-staging/8c5f7011ef5482f8744863934355acf83179095a_1452246591/go1.17.9.windows-arm64.zip.untested".
2022/04/12 11:07:39 windows-arm64: Installing go1.4 (second time, for all.bash).
2022/04/12 11:07:47 windows-arm64: Building (all.bash to ensure tests pass).
2022/04/12 11:16:21 windows-arm64: Error: Build failed: exit status 1
Output:
Building Go cmd/dist using C:\workdir\go1.4
Building Go toolchain1 using C:\workdir\go1.4.

Building Go toolchain2 using go_bootstrap and Go toolchain1.
Building Go toolchain3 using go_bootstrap and Go toolchain2.
Building packages and commands for windows/arm64.

##### Testing packages.
ok  	archive/tar	0.823s
ok  	archive/zip	1.533s
ok  	bufio	0.851s
ok  	bytes	2.890s
ok  	compress/bzip2	0.617s
ok  	compress/flate	2.777s
ok  	compress/gzip	0.992s
ok  	compress/lzw	0.779s
ok  	compress/zlib	1.624s
ok  	container/heap	0.438s
ok  	container/list	0.402s
ok  	container/ring	0.411s
ok  	context	0.362s
ok  	crypto	0.284s
ok  	crypto/aes	0.322s
ok  	crypto/cipher	0.420s
ok  	crypto/des	0.359s
ok  	crypto/dsa	0.388s
ok  	crypto/ecdsa	0.840s
ok  	crypto/ed25519	0.897s
ok  	crypto/ed25519/internal/edwards25519	7.040s
ok  	crypto/ed25519/internal/edwards25519/field	3.611s
ok  	crypto/elliptic	0.752s
ok  	crypto/elliptic/internal/fiat	0.537s
ok  	crypto/hmac	0.570s
ok  	crypto/internal/subtle	0.439s
ok  	crypto/md5	0.526s
ok  	crypto/rand	0.531s
ok  	crypto/rc4	0.418s
ok  	crypto/rsa	0.965s
ok  	crypto/sha1	0.538s
ok  	crypto/sha256	0.597s
ok  	crypto/sha512	0.592s
ok  	crypto/subtle	0.561s
ok  	crypto/tls	3.263s
ok  	crypto/x509	1.620s
ok  	database/sql	1.569s
ok  	database/sql/driver	0.424s
ok  	debug/dwarf	0.651s
ok  	debug/elf	0.517s
ok  	debug/gosym	0.361s
ok  	debug/macho	0.293s
ok  	debug/pe	16.257s
ok  	debug/plan9obj	0.742s
ok  	embed/internal/embedtest	0.769s
ok  	encoding/ascii85	0.551s
ok  	encoding/asn1	0.650s
ok  	encoding/base32	0.637s
ok  	encoding/base64	0.484s
ok  	encoding/binary	0.588s
ok  	encoding/csv	0.425s
ok  	encoding/gob	0.727s
ok  	encoding/hex	0.533s
ok  	encoding/json	1.732s
ok  	encoding/pem	2.082s
ok  	encoding/xml	0.816s
ok  	errors	0.557s
ok  	expvar	0.805s
ok  	flag	0.783s
ok  	fmt	0.744s
ok  	go/ast	0.671s
ok  	go/build	3.212s
ok  	go/build/constraint	0.500s
ok  	go/constant	0.505s
ok  	go/doc	1.277s
ok  	go/format	0.659s
ok  	go/importer	1.107s
ok  	go/internal/gccgoimporter	0.693s
ok  	go/internal/gcimporter	4.561s
ok  	go/internal/srcimporter	13.012s
ok  	go/parser	0.871s
ok  	go/printer	1.031s
ok  	go/scanner	0.415s
ok  	go/token	0.687s
ok  	go/types	14.182s
ok  	hash	0.587s
ok  	hash/adler32	0.540s
ok  	hash/crc32	0.313s
ok  	hash/crc64	0.249s
ok  	hash/fnv	0.466s
ok  	hash/maphash	0.771s
ok  	html	0.601s
ok  	html/template	1.277s
ok  	image	0.749s
ok  	image/color	0.543s
ok  	image/draw	0.620s
ok  	image/gif	1.621s
ok  	image/jpeg	0.838s
ok  	image/png	0.677s
ok  	index/suffixarray	0.812s
ok  	internal/abi	0.757s
ok  	internal/cpu	0.277s
ok  	internal/execabs	0.505s
ok  	internal/fmtsort	0.365s
ok  	internal/itoa	0.506s
ok  	internal/poll	0.465s
ok  	internal/profile	0.474s
ok  	internal/reflectlite	0.564s
ok  	internal/singleflight	0.330s
ok  	internal/syscall/windows	0.472s
ok  	internal/syscall/windows/registry	0.465s
ok  	internal/trace	0.500s
ok  	internal/unsafeheader	0.311s
ok  	internal/xcoff	0.514s
ok  	io	0.656s
ok  	io/fs	0.319s
ok  	io/ioutil	0.638s
ok  	log	0.610s
ok  	math	0.355s
ok  	math/big	2.332s
ok  	math/bits	0.733s
ok  	math/cmplx	0.371s
ok  	math/rand	0.729s
ok  	mime	0.486s
ok  	mime/multipart	0.696s
ok  	mime/quotedprintable	0.839s
ok  	net	156.473s
ok  	net/http	18.219s
ok  	net/http/cgi	2.174s
ok  	net/http/cookiejar	0.941s
ok  	net/http/fcgi	0.801s
ok  	net/http/httptest	5.905s
ok  	net/http/httptrace	0.678s
ok  	net/http/httputil	1.791s
ok  	net/http/internal	0.430s
ok  	net/http/internal/ascii	0.627s
ok  	net/http/pprof	5.922s
ok  	net/internal/socktest	0.221s
ok  	net/mail	0.223s
ok  	net/rpc	0.834s
ok  	net/rpc/jsonrpc	0.433s
ok  	net/smtp	0.625s
ok  	net/textproto	0.581s
ok  	net/url	0.430s
ok  	os	11.079s
ok  	os/exec	19.750s
ok  	os/signal	3.621s
ok  	os/user	0.645s
ok  	path	0.632s
ok  	path/filepath	4.369s
ok  	plugin	0.491s
ok  	reflect	1.887s
ok  	regexp	0.571s
ok  	regexp/syntax	0.819s
ok  	runtime	111.230s
ok  	runtime/cgo	0.322s
ok  	runtime/debug	0.964s
ok  	runtime/internal/atomic	0.598s
ok  	runtime/internal/math	0.482s
ok  	runtime/internal/sys	0.533s
ok  	runtime/metrics	0.306s
ok  	runtime/pprof	20.248s
ok  	runtime/trace	4.993s
ok  	sort	0.523s
ok  	strconv	1.072s
ok  	strings	1.788s
--- FAIL: TestWaitGroupMisuse2 (5.90s)
    waitgroup_test.go:133: Should panic
    waitgroup_test.go:96: Unexpected panic: <nil>
FAIL
FAIL	sync	8.531s
ok  	sync/atomic	4.586s
ok  	syscall	10.477s
ok  	testing	5.791s
ok  	testing/fstest	0.615s
ok  	testing/iotest	0.502s
ok  	testing/quick	0.841s
ok  	text/scanner	0.644s
ok  	text/tabwriter	0.458s
ok  	text/template	0.956s
ok  	text/template/parse	0.553s
ok  	time	4.597s
ok  	unicode	0.440s
ok  	unicode/utf16	0.243s
ok  	unicode/utf8	0.511s
ok  	cmd/addr2line	13.984s
ok  	cmd/api	88.172s
ok  	cmd/asm/internal/asm	1.981s
ok  	cmd/asm/internal/lex	0.570s
ok  	cmd/compile/internal/dwarfgen	10.915s
ok  	cmd/compile/internal/importer	18.305s
ok  	cmd/compile/internal/ir	0.650s
ok  	cmd/compile/internal/logopt	2.099s
ok  	cmd/compile/internal/noder	0.548s
ok  	cmd/compile/internal/ssa	1.945s
ok  	cmd/compile/internal/ssagen	0.681s
ok  	cmd/compile/internal/syntax	0.915s
ok  	cmd/compile/internal/test	56.737s
ok  	cmd/compile/internal/typecheck	9.184s
ok  	cmd/compile/internal/types	0.559s
ok  	cmd/compile/internal/types2	34.944s
ok  	cmd/cover	34.497s
ok  	cmd/doc	9.589s
ok  	cmd/fix	17.385s
ok  	cmd/go	219.945s
ok  	cmd/go/internal/auth	0.803s
ok  	cmd/go/internal/cache	8.257s
ok  	cmd/go/internal/fsys	2.650s
ok  	cmd/go/internal/generate	0.977s
ok  	cmd/go/internal/get	0.649s
ok  	cmd/go/internal/imports	0.490s
ok  	cmd/go/internal/load	1.348s
ok  	cmd/go/internal/lockedfile	3.398s
ok  	cmd/go/internal/lockedfile/internal/filelock	0.647s
ok  	cmd/go/internal/modconv	0.516s
ok  	cmd/go/internal/modfetch	0.592s
ok  	cmd/go/internal/modfetch/codehost	0.602s
ok  	cmd/go/internal/modfetch/zip_sum_test	0.786s
ok  	cmd/go/internal/modload	1.144s
ok  	cmd/go/internal/mvs	0.612s
ok  	cmd/go/internal/par	0.636s
ok  	cmd/go/internal/search	0.569s
ok  	cmd/go/internal/str	0.518s
ok  	cmd/go/internal/test	1.514s
ok  	cmd/go/internal/txtar	0.579s
ok  	cmd/go/internal/vcs	1.328s
ok  	cmd/go/internal/web	1.084s
ok  	cmd/go/internal/work	1.692s
ok  	cmd/gofmt	0.756s
ok  	cmd/internal/archive	7.739s
ok  	cmd/internal/buildid	1.162s
ok  	cmd/internal/dwarf	0.477s
ok  	cmd/internal/edit	0.521s
ok  	cmd/internal/goobj	0.728s
ok  	cmd/internal/moddeps	49.598s
ok  	cmd/internal/obj	0.803s
ok  	cmd/internal/obj/arm64	1.525s
ok  	cmd/internal/obj/ppc64	1.178s
ok  	cmd/internal/obj/riscv	0.873s
ok  	cmd/internal/obj/s390x	0.379s
ok  	cmd/internal/obj/x86	12.680s
ok  	cmd/internal/objabi	0.460s
ok  	cmd/internal/pkgpath	0.975s
ok  	cmd/internal/src	0.441s
ok  	cmd/internal/sys	0.342s
ok  	cmd/internal/test2json	0.767s
ok  	cmd/link	44.654s
ok  	cmd/link/internal/benchmark	0.675s
ok  	cmd/link/internal/ld	52.409s
ok  	cmd/link/internal/loader	0.354s
ok  	cmd/nm	26.510s
ok  	cmd/objdump	44.660s
ok  	cmd/pack	43.230s
ok  	cmd/pprof	13.655s
ok  	cmd/trace	1.283s
ok  	cmd/vet	32.696s
FAIL
go tool dist: Failed: exit status 1
2022/04/12 11:16:21 release -target="windows-arm64": waiting a bit and trying again
2022/04/12 11:16:26 release -target="linux-386": build succeeded (after 0 retries)
2022/04/12 11:17:21 $ /Users/dmitshur/go-releasebot-work/go1.17.9/gopath/bin/release -target windows-arm64 -user dmitshur -version go1.17.9 -staging_dir /Users/dmitshur/go-releasebot-work/go1.17.9/release-staging/8c5f7011ef5482f8744863934355acf83179095a_1452246591 -rev 8c5f7011ef5482f8744863934355acf83179095a
2022/04/12 11:17:33 release -target="darwin-amd64": build succeeded (after 0 retries)
2022/04/12 11:20:48 release -target="freebsd-386": build succeeded (after 0 retries)
2022/04/12 11:21:16 release -target="linux-amd64-longtest": build succeeded (after 0 retries)
2022/04/12 11:25:10 release -target="linux-386-longtest": build succeeded (after 0 retries)
2022/04/12 11:26:35 release -target="windows-386": build succeeded (after 0 retries)
2022/04/12 11:26:43 release -target="windows-amd64": build succeeded (after 0 retries)
2022/04/12 11:28:36 release -target="windows-amd64-longtest": build succeeded (after 0 retries)
2022/04/12 11:39:32 release -target="windows-arm64": build succeeded (after 1 retries)
2022/04/12 11:39:32

The prepare stage has completed.

Please review and submit https://go-review.googlesource.com/q/Id2437003673e7eb1c514f15e6266b93308b7d5e8
and then run the release stage.

Latest build: go1.17.9

src (tar.gz)
linux-386 (tar.gz)
linux-armv6l (tar.gz)
linux-amd64 (tar.gz)
linux-arm64 (tar.gz)
freebsd-386 (tar.gz)
freebsd-amd64 (tar.gz)
windows-386 (zip) (msi)
windows-amd64 (zip) (msi)
windows-arm64 (zip) (msi)
darwin-amd64 (tar.gz)
darwin-arm64 (tar.gz)
linux-s390x (tar.gz)
linux-ppc64le (tar.gz)
linux-386-longtest (test only) - ok
linux-amd64-longtest (test only) - ok
windows-amd64-longtest (test only) - ok

Log
2022/04/12 12:42:16 starting
2022/04/12 12:42:16 working in /Users/dmitshur/go-releasebot-work/go1.17.9
2022/04/12 12:42:16 $ git fetch origin master
2022/04/12 12:42:17 $ git fetch origin release-branch.go1.17
2022/04/12 12:42:24 $ git clone --reference /Users/dmitshur/go-releasebot-work/go1.17.9/gitmirror -b release-branch.go1.17 https://go.googlesource.com/go /Users/dmitshur/go-releasebot-work/go1.17.9/gitwork
2022/04/12 12:42:28 $ git codereview change relwork
2022/04/12 12:42:29 $ git config gc.auto 0
2022/04/12 12:42:29 Release status issue title: "all: Go 1.17.9 release status"
2022/04/12 12:42:29 Release status issue: https://golang.org/issue/52304
2022/04/12 12:42:29 $ git rev-parse go1.17.9
2022/04/12 12:42:29 Git tag already exists (346b18ee9d15410ab08dd583787c64dbed0666d2), resuming release.
2022/04/12 12:42:29 $ go clean -modcache
2022/04/12 12:42:39 $ go install golang.org/x/build/cmd/release@latest
2022/04/12 12:42:58 release -target="windows-amd64-longtest": already have [go1.17.9.windows-amd64-longtest.test-only]; not rebuilding files
2022/04/12 12:42:58 release -target="linux-armv6l": already have [go1.17.9.linux-armv6l.tar.gz]; not rebuilding files
2022/04/12 12:42:58 release -target="freebsd-amd64": already have [go1.17.9.freebsd-amd64.tar.gz]; not rebuilding files
2022/04/12 12:42:58 release -target="linux-386": already have [go1.17.9.linux-386.tar.gz]; not rebuilding files
2022/04/12 12:42:58 release -target="windows-386": already have [go1.17.9.windows-386.zip go1.17.9.windows-386.msi]; not rebuilding files
2022/04/12 12:42:58 release -target="freebsd-386": already have [go1.17.9.freebsd-386.tar.gz]; not rebuilding files
2022/04/12 12:42:58 release -target="linux-amd64": already have [go1.17.9.linux-amd64.tar.gz]; not rebuilding files
2022/04/12 12:42:58 release -target="linux-ppc64le": already have [go1.17.9.linux-ppc64le.tar.gz]; not rebuilding files
2022/04/12 12:42:58 release -target="darwin-amd64": already have [go1.17.9.darwin-amd64.tar.gz]; not rebuilding files
2022/04/12 12:42:58 release -target="src": already have [go1.17.9.src.tar.gz]; not rebuilding files
2022/04/12 12:42:58 release -target="linux-arm64": already have [go1.17.9.linux-arm64.tar.gz]; not rebuilding files
2022/04/12 12:42:58 release -target="windows-amd64": already have [go1.17.9.windows-amd64.zip go1.17.9.windows-amd64.msi]; not rebuilding files
2022/04/12 12:42:58 release -target="linux-386-longtest": already have [go1.17.9.linux-386-longtest.test-only]; not rebuilding files
2022/04/12 12:42:58 release -target="linux-amd64-longtest": already have [go1.17.9.linux-amd64-longtest.test-only]; not rebuilding files
2022/04/12 12:42:58 release -target="windows-arm64": already have [go1.17.9.windows-arm64.zip go1.17.9.windows-arm64.msi]; not rebuilding files
2022/04/12 12:42:58 release -target="darwin-arm64": already have [go1.17.9.darwin-arm64.tar.gz]; not rebuilding files
2022/04/12 12:42:58 release -target="linux-s390x": already have [go1.17.9.linux-s390x.tar.gz]; not rebuilding files
2022/04/12 12:51:38 creating milestone titled "Go1.17.10"
2022/04/12 12:51:38 changing milestone of issue 51351 to Go1.17.10
2022/04/12 12:51:39 changing milestone of issue 51858 to Go1.17.10
2022/04/12 12:51:39 changing milestone of issue 52095 to Go1.17.10
2022/04/12 12:51:40 changing milestone of issue 52148 to Go1.17.10
2022/04/12 12:51:41 changing milestone of issue 52306 to Go1.17.10
2022/04/12 12:51:41 closing milestone Go1.17.9
2022/04/12 12:51:41

The release stage has completed. Thanks for riding with releasebot today!

Please refer to the playbook for the next steps.

This release is complete.


Update version: james.james version 2.1.2

Pull request has been created with WinGet Automation :rocket:
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/114990&drop=dogfoodAlpha

@wingetbot run


Drop upload-button feature

The feature is currently broken. It was initially added because we hide this bar via CSS:

However now we have two reasons why this is not useful:

upload-button now also takes care of hiding the bar; i.e. the feature can be disabled altogether and the bar reappears
we now also offer a CSS field to restore the bar

Additionally:

We have a related feature that drops the Upload files button from file lists and does not add an alternative. Likewise, people can just upload files via drag-drop or disable the feature.

Therefore we can either:

👎 Keep the feature as JS, but not add the alternative button
👍 Drop the JS feature and just hide the bar via CSS (who doesn't want it can undo it easily in the custom CSS field)

who doesn't want it can undo it easily in the custom CSS field

How can I undo this? I cannot use drag-and-drop so I need to be able to click this button to get a file selector up and it's not clear to me what I can do to get it back.

Probably
.drag-and-drop {
	display: block !important;
}

I finally got it working with
/* Restore upload message on comment box */
body file-attachment.is-default .drag-and-drop {
	display: flex !important;
}

I had to add body to add extra specificity since the stylesheet overrides in the settings are loaded before the stylesheet, so it didn't win the specificity war.

!important doesn’t care about specificity, the last important wins 😅

I'm pretty sure it still counts, it's just that it's sorted "important,
specificity". So important always wins over non-important, but among
important the specificity still wins.
I'm not sure how else the trick would have fixed it.
Den lör 1 juni 2019 04:52Federico Brigante<EMAIL_ADDRESS>skrev:

!important doesn’t care about specificity, the last important wins 😅
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/sindresorhus/refined-github/issues/2014?email_source=notifications&email_token=AAAAMPYUU6YP2BPMN5NYFU3PYHP6NA5CNFSM4HK6VPO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWWXGEA#issuecomment-497906448,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAAMPZN465S3STRCTDR7ELPYHP6NANCNFSM4HK6VPOQ
.

An update for any future searchonauts:
Since #2086, you need to use this override in the CSS:
/* Restore upload message on comment box */
body file-attachment.js-upload-markdown-image.is-default .drag-and-drop {
	display: flex !important;
}

Can we add an option for this?

Should the hidden bar for uploading a file be displayed by default?
Basically forcing users to always use drag & drop provides no advantage whatsoever to me.

The option is the CSS

https://github.com/sindresorhus/refined-github/issues/2155


Fix typo for image

Description

Image not loaded on the website due to a typo for the image path

LGTM


Deteriorating Sound Quality

I apologize, but it doesn't seem to let me add a label like you requested in your bug submit instructions....
So I run a 27" iMac with Sierra. Audio goes to a Focusrite 212 connected to Tannoy reference monitors. The sound is fins for about 45 mins or so and then it starts to slowly get distorted. Now, I can "reset" it by opening Sound prefs and just clicking on the Focusrite again. It goes right back to highlighting eqMac2, but for some reason clicking the other interface temporarily suspends the distortion. This happens regardless of audio source, browser, app, etc.

#

#36 #47 #79

+1 happening to me.  restarting 2.0.6 build resolves this for another 30 minutes

Build 2.1 has just been released. You can download it from https://bitgapp.com/eqmac
Could you please update and report if the issue is still relevant. Thanks :)

It wont install the new driver during update even with recommended "Allow from store and identified..."

@Satori83 try restarting your Mac before running eqMac

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

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

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

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


Extra svg text that causes scrollbar to appear on

https://github.com/williaster/data-ui/blob/c30330ad2f57a1ba853ad17876c8538eacc51db4/packages/xy-chart/package.json#L38
The @vx/text util function is fixed but here we might want to reference @vx/xy-chart: ^0.0.175 to pick up the fix from @vx/text 0.0.175 and above.
Thanks!

@bluekvirus this should now be fixed in<EMAIL_ADDRESS>

Awesome! Thanks :))
On Mon, Jun 17, 2019 at 12:06 PM Chris Williams<EMAIL_ADDRESS>wrote:

@bluekvirus https://github.com/bluekvirus this should now be fixed in
<EMAIL_ADDRESS>—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/williaster/data-ui/issues/180?email_source=notifications&email_token=AANO266IRVDJNX4EFA7LFRLP27OFFA5CNFSM4HQGKEHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX4E2JA#issuecomment-502811940,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AANO266ZTY3DQANN3A44VTDP27OFFANCNFSM4HQGKEHA
.


Forward Tasks From Past

updated to 0.1.11 and am finding the "Forward Tasks From Past" option is not working correctly anymore. Currently it is forward the tasks as expected however it is also leaving them in the original date.

Hi @toasterknight , this is as expected for now, the behavior is showing those overdue tasks on both the original date and today.

Would it be possible to get a setting to revert the behavior to the pre 0.1.11 behavior.
On May 20, 2023 7:41 PM, zhuwenq @.***> wrote:
Hi @toasterknighthttps://github.com/toasterknight , this is as expected for now, the behavior is showing those overdue tasks on both the original date and today.
—
Reply to this email directly, view it on GitHubhttps://github.com/Leonezz/obsidian-tasks-calendar-wrapper/issues/22#issuecomment-1556068312, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMUPL7TV3HDWE7ISOJPA2KDXHF6G5ANCNFSM6AAAAAAYJCGHZU.
You are receiving this because you were mentioned.Message ID: @.***>

How would you like the behavior, would it be good to you if the overdue tasks only show on today?

That would be the preference. That is how it was functioning when I installed 0.1.10. It still flagged the due date in red if they were overdue and forwarded.
On May 20, 2023 8:17 PM, zhuwenq @.***> wrote:
How would you like the behavior, would it be good to you if the overdue tasks only show on today?
—
Reply to this email directly, view it on GitHubhttps://github.com/Leonezz/obsidian-tasks-calendar-wrapper/issues/22#issuecomment-1556072050, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMUPL7VDP4NS5R67ENLHN2DXHGCKRANCNFSM6AAAAAAYJCGHZU.
You are receiving this because you were mentioned.Message ID: @.***>

That would be the preference. That is how it was functioning when I installed 0.1.10. It still flagged the due date in red if they were overdue and forwarded. On May 20, 2023 8:17 PM, zhuwenq @.> wrote: How would you like the behavior, would it be good to you if the overdue tasks only show on today? — Reply to this email directly, view it on GitHub<#22 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMUPL7VDP4NS5R67ENLHN2DXHGCKRANCNFSM6AAAAAAYJCGHZU. You are receiving this because you were mentioned.Message ID: @.>

Are you sure that is how it works in the previous versions? cause from what I thought, the forward should be not working for overdue tasks, that's said no matter you enable the option or not, the overdue tasks only show on the original date.
The today only behavior would be good I believe, I will make it happen in the next release.

I wonder if I was experiencing a bug in what I was seeing before. That is exactly how it was functioning. I also have a taskido manual created note that functions that way.
await dv.view("_resources/taskido", {
 pages: '"dailyNotes"',
 options: "noYear noDone noFile noQuickEntry",
 forward: true,
 dateFormat: "dddd, MMM, D"
})

On May 20, 2023 8:37 PM, zhuwenq @.***> wrote:
That would be the preference. That is how it was functioning when I installed 0.1.10. It still flagged the due date in red if they were overdue and forwarded. On May 20, 2023 8:17 PM, zhuwenq @.> wrote: How would you like the behavior, would it be good to you if the overdue tasks only show on today? — Reply to this email directly, view it on GitHub<#22 (comment)https://github.com/Leonezz/obsidian-tasks-calendar-wrapper/issues/22#issuecomment-1556072050>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMUPL7VDP4NS5R67ENLHN2DXHGCKRANCNFSM6AAAAAAYJCGHZU. You are receiving this because you were mentioned.Message ID: @.>
Are you sure that is how it works in the previous versions? cause from what I thought, the forward should be not working for overdue tasks, that's said no matter you enable the option or not, the overdue tasks only show on the original date.
The today only behavior would be good I believe, I will make it happen in the next release.
—
Reply to this email directly, view it on GitHubhttps://github.com/Leonezz/obsidian-tasks-calendar-wrapper/issues/22#issuecomment-1556074100, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMUPL7VZRGMXG6NTIWJLPS3XHGEXFANCNFSM6AAAAAAYJCGHZU.
You are receiving this because you were mentioned.Message ID: @.***>

Hi @toasterknight , I have made a few changes int the latest release, could you please confirm if this bug still exists?

Just installed and everything is looking good. Only possible improvement I could suggest is a separate option for forwarding tasks and hiding forwarded tasks. When I enable forward tasks, it is exactly how I was hoping for. When I disable the overdue tasks are shown on their original day and today. I could foresee this being a bug report generator. Doesn't have an impact on my workflow however.

From: zhuwenq @.>
Sent: Monday, May 22, 2023 3:03 AM
To: Leonezz/obsidian-tasks-calendar-wrapper @.>
Cc: Tyler Greene @.>; Mention @.>
Subject: Re: [Leonezz/obsidian-tasks-calendar-wrapper] Forward Tasks From Past (Issue #22)
Hi @toasterknighthttps://github.com/toasterknight , I have made a few changes int the latest release, could you please confirm if this bug still exists?
—
Reply to this email directly, view it on GitHubhttps://github.com/Leonezz/obsidian-tasks-calendar-wrapper/issues/22#issuecomment-1556927479, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMUPL7QQVF2TWH4I2A54Y2LXHM2W5ANCNFSM6AAAAAAYJCGHZU.
You are receiving this because you were mentioned.Message ID: @.***>

Thanks for the report, that is clearly a bug.

Hi @toasterknight , I think the latest release should have fixed this, could you please confirm?

Closing this, please reopen if issue still exists.


MASTER_HOST=FQDN to IP

How to change MASTER_HOST=FQDN to MASTER_HOST=IP when Failover?

You should not resolve as fqdn in the first place. Use
 "HostnameResolveMethod": "none",
 "MySQLHostnameResolveMethod": "",

alternatively, use
 "HostnameResolveMethod": "default",
 "MySQLHostnameResolveMethod": "@@report_host",

and make sure that report_host variable contains IP address.
In the future, I might add  "HostnameResolveMethod": "ip".

I am using the first of these two proposed configs, and the hostname alias is always what is used when establishing replication.  Am I missing something?

I am using the first of these two proposed configs, and the hostname alias is always what is used when establishing replication.

What do you have for DiscoverByShowSlaveHosts configruation?
If the existing replicas already identify master by hostname, or if show slave hosts identifies replicas by hostname, then that's what orchestrator will use.
The real solution will be to support "HostnameResolveMethod": "ip". This has come up in the past; I should do it.

Ah, this is what I suspected.  This would absolutely be a great feature to have.  I guess we're stuck with DNS until then.

Looks like "HostnameResolveMethod": "ip" was added as a valid option in this PR  #926


fixed typo

Description

Fixed typo in README.md
Type of Change

[ ] 📚 Examples / docs / tutorials / dependencies update
[x] 🔧 Bug fix (non-breaking change which fixes an issue)

Checklist

[x] I've read the CODE_OF_CONDUCT.md document.
[x] I've read the CONTRIBUTING.md guide.
[x] I've updated the code style using make codestyle.
[x] I've written tests for all new methods and classes that I created.
[x] I've written the docstring in Sphinx format for all the methods and classes that I used.

Codecov Report

Merging #144 (3a05102) into main (5c9d51d) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #144   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           46        46
  Branches        15        15
=========================================
  Hits            46        46

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


fix(django): support streaminghttpresponse

:tada: This PR is included in version 1.73.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


componentDidMount fires twice on app load (dev, prod)

Is this a bug report?
Yes

Did you try recovering your dependencies?

Yes
Environment

Environment Info:

  System:
    OS: macOS 10.14.1
    CPU: x64 Intel(R) Core(TM) i7-6920HQ CPU @ 2.90GHz
  Binaries:
    Node: 10.10.0 - ~/.nvm/versions/node/v10.10.0/bin/node
    Yarn: 1.9.4 - /usr/local/bin/yarn
    npm: 6.4.1 - ~/.nvm/versions/node/v10.10.0/bin/npm
  Browsers:
    Chrome: 70.0.3538.110
    Safari: 12.0.1
  npmPackages:
    @types/react:  16.7.6
    react: ^16.4.2 => 16.6.3
    react-dom: ^16.4.2 => 16.6.3
    react-scripts: Not Found
  npmGlobalPackages:
    create-react-app: Not Found

Steps to Reproduce

Place code snippet in componentDidMount() of any component, and refresh the page.
Look at console.

Expected Behavior

componentDidMount should only fire once.
Actual Behavior

Doing anything within componentDidMount() consistently fires twice on page load in both development and production builds. I am using create-react-app and have disabled service workers.
MyComponent extends Component {
  componentDidMount() {
    console.log('component did mount')
  }
}

The following results are logged on the console:
component did mount             VM408 bundle.js:119905
component did mount                        index.js:51

When I hover my cursor over the file path, I see:
debugger:///VM408 bundle.js:119905
Refreshing the page produces another bundle, and I see something like this:
component did mount             VM552 bundle.js:119905
component did mount                        index.js:51

I would like to disable the instance of VMxxx bundles. I cannot rely on react/redux state to ensure that something doesn't fire twice, as these are separate apps entirely.
Note that transitioning to the component only fires cDM once; it is on page load where I'm having trouble.
The webpack config that comes out of the box with react is available here: https://github.com/Robinnnnn/create-react-app-webpack-config
Example screenshot from dev:

Example screenshot from prod:

Could you please setup a codesandbox demo?

This issue was caused by using a root .ejs template rather than .html. Apologies!


There is a vulnerability in Netty Project 4.1.53.Final,upgrade recommended

https://github.com/apache/iotdb/blob/4d6bc04a6afdb5308f776e62e673f0e61a7baf4f/pom.xml#L160
CVE-2021-37136
CVE-2021-37137
CVE-2021-21290
CVE-2021-21295
CVE-2021-21409
Recommended upgrade version：4.1.77.Final

but the version is already 4.1.82.Final.


Added Korean translation - Jun 23 (#1)

Based on B18.

Thanks! Currently away from my desktop but I'll accept your pull request asap (next Wednesday).

Op 22 jun. 2018 om 18:41 heeft Orange_mushroom<EMAIL_ADDRESS>het volgende geschreven:
Based on B18.
You can view, comment on, or merge this pull request online at:
https://github.com/Mehni/kNumbers/pull/1
Commit Summary
Added Korean translation - Jun 23 (#1)
File Changes
A Languages/Korean/DefInjected/MainButtonDef/kNumbers.xml     (8)
A Languages/Korean/Keyed/Keys.xml (34)
Patch Links:
https://github.com/Mehni/kNumbers/pull/1.patch
https://github.com/Mehni/kNumbers/pull/1.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks again =)


Support custom mime types

Right now, we don't use the consumes and produces fields at all - we just assume that we're using JSON. We can support application/json and application/yaml out of the box since those serde libs are stable, but we can't deal with other things like application/xml, which means we should let the user pick their encoder/decoder through an OpenAPI extension field (globally), say x-content-encoder and x-content-decoder, which could then be used by the emitter.

For custom en/decoders, we now support x-coders field in the root, which is a map of media ranges and the corresponding (serde) encoder/decoder information. By default, we support JSON and YAML. If we were to include XML, for example, then our spec would look something like this:
{
  "swagger": "2.0",
  // ...
  // Spec stuff
  // ...
  "x-rust-coders": {
    "application/xml": {
      "encoder_path": "serde_xml_rs::to_writer",
      "decoder_path": "serde_xml_rs::from_reader",
      "error_path": "serde_xml_rs::Error"
    }
  },
  // Specify dependency crate
  "x-rust-dependencies": {
    "serde_xml_rs": "{ git = \"https://github.com/RReverser/serde-xml-rs\" }"
  }
}

And XML en/decoder will be added to the generated code. At this point, there's no validation for the existence of the functions or error type. If they're non-existent, then the generated code will fail to compile.


Updated plot_singlediode.py

Changed the unit from C to degree C (°C)

[ ] Closes #xxxx
[ ] I am familiar with the contributing guidelines
[ ] Tests added
[ ] Updates entries in docs/sphinx/source/reference for API changes.
[ ] Adds description and name entries in the appropriate "what's new" file in docs/sphinx/source/whatsnew for all changes. Includes link to the GitHub Issue with :issue:`num` or this Pull Request with :pull:`num`. Includes contributor name and/or GitHub username (link with :ghuser:`user`).
[ ] New code is fully documented. Includes numpydoc compliant docstrings, examples, and comments where necessary.
[ ] Pull request is nearly complete and ready for detailed review.
[ ] Maintainer: Appropriate GitHub Labels and Milestone are assigned to the Pull Request and linked Issue.

Hi, thanks for the contribution. I have a concern and a preference if you’ll indulge me.
I’m concerned about using non-ascii Unicode characters. My preference is for the LaTeX \degree symbol in matplotlib which avoids any encoding issues with using Unicode characters.
This:
plt.plot([1, 2, 3], [4, 9, 16])
plt.title(r'temp = $10 \degree C$')

works for me:

Yeah, I think that'll be great :)

@mikofski Why does it show 8 failed checks? Do I have to make some more changes?

@kanderso-nrel  I can't see the rendered docs - they are failing. Any ideas why? @RoyCoding8  can you render the docs locally and copy/paste an image of the gallery example showing that the degree symbol is present? thanks!

@mikofski

In my case it shows the presence of the degree symbol.


CE-868 - Update Map Popup Layout

Description
Please provide a summary of the change and the issue fixed. Please include relevant context. List dependency changes.
Fixes # (issue)
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist

[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Further comments

Thanks for the PR!
Any successful deployments (not always required) will be available below.
Backend available
Frontend available
Once merged, code will be promoted and handed off to following workflow run.
Main Merge Workflow

@jeznorth I view this in Google using Mac, and it has this weird icon "?".
Also this line has black colour, which is different from the greyish in the design 🤔

Out of scope question: sometimes the "...complaints could not be mapped" is covering the tooltip's header, so the complaint number, status and sometimes the line below it cannot be seen, and users have to move the map around to find perfect spot to view the tooltip. Do we want to address this UIUX issue? 🤔

Out of scope question: sometimes the "...complaints could not be mapped" is covering the tooltip's header, so the complaint number, status and sometimes the line below it cannot be seen, and users have to move the map around to find perfect spot to view the tooltip. Do we want to address this UIUX issue? 🤔

I talked about this with the design team and we have a solution in place - however it is won't be part of this ticket.

@jeznorth I view this in Google using Mac, and it has this weird icon "?". Also this line has black colour, which is different from the greyish in the design 🤔

I'll address the missing character, however the horizontal rule uses the 'gray' variables from the pattern library, and it's verified with the design team.


[Bug] pulsar-admin 2.x links don't properly link to 3.2

Search before asking

[X] I searched in the issues and found nothing similar.

Read release policy

[X] I understand that unsupported versions don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker.

Version
Chrome
Minimal reproduce step
Visit https://pulsar.apache.org/docs/2.10.x/pulsar-admin/ and click the We recommend you use the 3.2.x. link
What did you expect to see?
The 3.2 docs
What did you see instead?

Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

@visortelle do you have a chance to check this one? thanks!

@illegalnumbers this doc page was removed for newer versions.
You can find the pulsar-admin CLI reference here ➡
https://pulsar.apache.org/reference/#/next/pulsar-admin/

2.10.x support period ended a year ago therefore I think we shouldn't handle it.
If it makes sense, we could make a HEAD request to the suggested URL to check if it is broken. And if the page doesn't exist, don't show the latest version suggestion link.

@visortelle I disagree with  your assessment of the issue. This page is still up and publicly available. Most search links to anything pulsar related links to 2.x versions or to older 3.x versions rather than next. In fact, the reason I used that in the first place is because it was the first link returned from Google.
It is myopic to consider that just because the support period has ended that the pages are removed and no one will find them. Additionally, this redirect should just work. Old versions of docs should link to new versions.

Most search links to anything pulsar related links to 2.x versions or to older 3.x versions rather than next.

There were attempts to fix it in the past. It improved the situation a bit, but not completely. We probably should make one more attempt to exclude old version pages from the Google index.
https://github.com/apache/pulsar-site/pull/506
https://github.com/apache/pulsar/issues/17898

Additionally, this redirect should just work.

This page doesn't exist anymore.
Do you suggest handling each such case individually? I mean instead of simply removing pulsar-admin.md file, leave it and add a message that the page has been moved, or this page isn't relevant for newer Pulsar versions (Say Hi! to Pulsar SQL)
We can introduce a way to override the version suggestion message and link on a per-page basis.
It could work together with this:

If it makes sense, we could make a HEAD request to the suggested URL to check if it is broken. And if the page doesn't exist, don't show the latest version suggestion link.

Handling it properly looks like a task for one or two full days. @illegalnumbers your GitHub profile says that you work in SN. Maybe you're ready to review all the docs pages across all the versions? Unfortunately, I don't have time to do it for free.

A quick hack could be to add some reasonable page as the redirect target.
Redirects could be made with Apache httpd syntax in https://github.com/apache/pulsar-site/blob/main/static/.htaccess

Reopening since the "not found" page isn't nice. We can keep this open for contributions.


thunderbird-bin: 52.2.0 -> 52.2.1

References #26816.
Motivation for this change
Things done

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Thank you. I merged https://github.com/NixOS/nixpkgs/pull/26887 instead as it also contained a bump for the from-source version.