Publish main to live 2021-10-20

Docs Build status updates of commit d698923:
:warning: Validation status: warnings

File
Status
Preview URL
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

docs-ref-autogen/toc.yml
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/communication-chat-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/preview/arm-postgresql-readme.md
:warning:Warning
View (azure-node-preview)
Details

docs-ref-services/preview/arm-resources-subscriptions-readme.md
:warning:Warning
View (azure-node-preview)
Details

ci-configs/packages-latest.json
:white_check_mark:Succeeded

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (azure-node-latest)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (azure-node-latest)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (azure-node-latest)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (azure-node-latest)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (azure-node-latest)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (azure-node-latest)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (azure-node-latest)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (azure-node-latest)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (azure-node-latest)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (azure-node-latest)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (azure-node-latest)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (azure-node-latest)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (azure-node-latest)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (azure-node-latest)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (azure-node-latest)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (azure-node-latest)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (azure-node-latest)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (azure-node-latest)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (azure-node-latest)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (azure-node-latest)

metadata/latest/azure-communication-chat.json
:white_check_mark:Succeeded

metadata/preview/azure-arm-postgresql.json
:white_check_mark:Succeeded

metadata/preview/azure-arm-resources-subscriptions.json
:white_check_mark:Succeeded

<EMAIL_ADDRESS>
Line 46, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 49, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.CommunityGalleriesGetResponse'.

<EMAIL_ADDRESS>
Line 62, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 65, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.CommunityGalleryImageVersionsGetResponse'.
Line 55, Column 48: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'MajorVersion' isn't allowed. Disallowed HTML poses a security risk and must be replaced with approved Docs Markdown syntax.
Line 55, Column 63: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'MinorVersion' isn't allowed. Disallowed HTML poses a security risk and must be replaced with approved Docs Markdown syntax.
Line 55, Column 78: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'Patch' isn't allowed. Disallowed HTML poses a security risk and must be replaced with approved Docs Markdown syntax.
Line 98, Column 48: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'MajorVersion' isn't allowed. Disallowed HTML poses a security risk and must be replaced with approved Docs Markdown syntax.
Line 98, Column 63: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'MinorVersion' isn't allowed. Disallowed HTML poses a security risk and must be replaced with approved Docs Markdown syntax.
Line 98, Column 78: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'Patch' isn't allowed. Disallowed HTML poses a security risk and must be replaced with approved Docs Markdown syntax.
Line 141, Column 48: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'MajorVersion' isn't allowed. Disallowed HTML poses a security risk and must be replaced with approved Docs Markdown syntax.
Line 141, Column 63: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'MinorVersion' isn't allowed. Disallowed HTML poses a security risk and must be replaced with approved Docs Markdown syntax.
Line 141, Column 78: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'Patch' isn't allowed. Disallowed HTML poses a security risk and must be replaced with approved Docs Markdown syntax.

<EMAIL_ADDRESS>
Line 49, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 52, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.CommunityGalleryImagesGetResponse'.

<EMAIL_ADDRESS>
Line 32, Column 1: [Warning: xref-not-found] Cross reference not found: 'https://www.npmjs.com/package/@azure/identity'.
Line 50, Column 17: [Warning: xref-not-found] Cross reference not found: 'Models.ComputeManagementClientOptions'.

<EMAIL_ADDRESS>
Line 58, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 95, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 126, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 162, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 209, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 245, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 248, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DiskAccessesCreateOrUpdateResponse'.
Line 284, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 315, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 346, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 349, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DiskAccessesGetResponse'.
Line 446, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 449, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DiskAccessesGetAPrivateEndpointConnectionResponse'.
Line 557, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 560, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DiskAccessesGetPrivateLinkResourcesResponse'.
Line 646, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 649, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DiskAccessesListResponse'.
Line 704, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 707, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DiskAccessesListByResourceGroupResponse'.
Line 774, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 777, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DiskAccessesListByResourceGroupNextResponse'.
Line 844, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 847, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DiskAccessesListNextResponse'.
Line 922, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 925, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DiskAccessesListPrivateEndpointConnectionsResponse'.
Line 1018, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 1021, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DiskAccessesListPrivateEndpointConnectionsNextResponse'.
Line 1107, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 1110, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DiskAccessesUpdateResponse'.
Line 1154, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 1157, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DiskAccessesUpdateAPrivateEndpointConnectionResponse'.

<EMAIL_ADDRESS>
Line 60, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 90, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 128, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 166, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 169, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DiskEncryptionSetsCreateOrUpdateResponse'.
Line 198, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 228, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 231, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DiskEncryptionSetsGetResponse'.
Line 310, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 313, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DiskEncryptionSetsListResponse'.
Line 377, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 380, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DiskEncryptionSetsListAssociatedResourcesResponse'.
Line 467, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 470, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DiskEncryptionSetsListAssociatedResourcesNextResponse'.
Line 538, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 541, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DiskEncryptionSetsListByResourceGroupResponse'.
Line 608, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 611, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DiskEncryptionSetsListByResourceGroupNextResponse'.
Line 678, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 681, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DiskEncryptionSetsListNextResponse'.
Line 763, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 766, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DiskEncryptionSetsUpdateResponse'.

<EMAIL_ADDRESS>
Line 65, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 102, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 137, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 140, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DiskRestorePointGetResponse'.
Line 256, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 259, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DiskRestorePointGrantAccessResponse'.
Line 290, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 293, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DiskRestorePointListByRestorePointResponse'.
Line 384, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 387, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DiskRestorePointListByRestorePointNextResponse'.
Line 468, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.

<EMAIL_ADDRESS>
Line 56, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 87, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 125, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 156, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 190, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 224, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 227, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DisksCreateOrUpdateResponse'.
Line 255, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 286, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 289, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DisksGetResponse'.
Line 383, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 386, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DisksGrantAccessResponse'.
Line 399, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 402, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DisksListResponse'.
Line 453, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 456, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DisksListByResourceGroupResponse'.
Line 515, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 518, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DisksListByResourceGroupNextResponse'.
Line 581, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 584, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DisksListNextResponse'.
Line 653, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 687, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 690, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.DisksUpdateResponse'.

<EMAIL_ADDRESS>
Line 56, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 87, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 126, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 157, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 193, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 227, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 230, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.SnapshotsCreateOrUpdateResponse'.
Line 258, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 289, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 292, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.SnapshotsGetResponse'.
Line 386, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 389, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.SnapshotsGrantAccessResponse'.
Line 402, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 405, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.SnapshotsListResponse'.
Line 460, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 463, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.SnapshotsListByResourceGroupResponse'.
Line 530, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 533, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.SnapshotsListByResourceGroupNextResponse'.
Line 600, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 603, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.SnapshotsListNextResponse'.
Line 676, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 712, Column 17: [Warning: xref-not-found] Cross reference not found: 'msRest.RequestOptionsBase'.
Line 715, Column 26: [Warning: xref-not-found] Cross reference not found: 'Models.SnapshotsUpdateResponse'.

docs-ref-autogen/toc.yml

Line 50200, Column 12: [Warning: xref-not-found] Cross reference not found<EMAIL_ADDRESS>Line 81873, Column 12: [Warning: xref-not-found] Cross reference not found<EMAIL_ADDRESS>Line 94563, Column 12: [Warning: xref-not-found] Cross reference not found: 'microsoft-cognitiveservices-speech-sdk.request'.

docs-ref-services/latest/communication-chat-readme.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning: ms-prod-technology-invalid - See documentation] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'communication'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 5, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'magpint' is not a valid Microsoft alias.
Line 19, Column 46: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/communication-services/overview' will be broken in isolated environments. Replace with a relative link.
Line 26, Column 134: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/powershell/module/az.communication/new-azcommunicationservice' will be broken in isolated environments. Replace with a relative link.
Line 26, Column 179: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 185, Column 34: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/communication-services/concepts/authentication?tabs=javascript' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/preview/arm-postgresql-readme.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning: ms-prod-technology-invalid - See documentation] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 5, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'magpint' is not a valid Microsoft alias.
Line 23, Column 1: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/arm-postgresql' will be broken in isolated environments. Replace with a relative link.
Line 61, Column 76: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/preview/arm-resources-subscriptions-readme.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning: ms-prod-technology-invalid - See documentation] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'resourcessubscriptions'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 5, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'magpint' is not a valid Microsoft alias.
Line 23, Column 1: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/arm-resources-subscriptions' will be broken in isolated environments. Replace with a relative link.
Line 61, Column 76: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Error compiling firmware: include file "uECC.h" missing

Hi,
I'm following instructions on https://github.com/espressif/esp32-at
I'm on windows and installed toolchain using this guide: https://docs.espressif.com/projects/esp-idf/en/latest/get-started/windows-setup.html#introduction

'make defconfig' worked, with a wvroom32 library not found warning.
'make menuconfig' worked
But 'make flash' failed. I attached a screenshot.

Is there something I can do ?

in ubuntu, the same

Hi, i test a method, it is OK.

git clone -b release/v<IP_ADDRESS> https://github.com/espressif/esp32-at.git
cd esp32-at
change the .gitmodules, add one line:
branch = release/v3.3
then, run command:
git submodule update --init --recursive
make menuconfig
make flash -j12

It seem to have compiled without error. Thanks, that's awesome !
But now... Does the firmware is uploaded to the mcu ? There was no progress bar of erasing memory and flashing... Is it normal ?

It work well. After "make flash -j12", You can find the wifi by your phone.
"make flash -j12", the command can build the esp-idf and esp-at, flash program to your esp32 device.

Classic bluetooth commands doesn't seem to be available in the "make menuconfig" in this version.. I need these commands.

Classic bluetooth command configuration  has added in make menuconfig

The lastest ESP32-WROVER AT Bin V2.0 firmware has been released, which enables classic bluetooth command by default, you can find it at https://www.espressif.com/zh-hans/support/download/at


Incorrect namespace for JSON Schema

It's in the standard library so should be TypeSpec.JsonSchema, but is JsonSchema. Very sad this was missed, and it will be a breaking change to fix.

est: 1

fixed in https://github.com/microsoft/typespec/pull/2119


docs: fix anchor scroll position

Description
Add an offset when the window scrolls to an anchor position to compensate for sticky header size.
Pull Request Checklist

[x] Ask the contributors if a similar effort is already in process or has been solved.
[x] Review the contribution guidelines.
[x] Use staging as your pull request's base branch. (All PRs using production as its base branch will be declined).
[x] Ensure all gulp scripts successfully compile.
[x] Update, remove, or extend all affected documentation.
[x] Ensure no private Dialpad links or info are in the code or pull request description (Dialtone is a public repo!).

Obligatory GIF (super important!)

Is it possible to apply this fix to the header anchor? Seems that's the same issue with the TOC links

Is it possible to apply this fix to the header anchor? Seems that's the same issue with the TOC links

Hmm I didn't notice that, I'll look into it.


docs: Best practices guides

A current gap in our docs is a set of "best practices" guides, case studies, or example repos. We want to cater to the user who comes to the docs saying "given this set of objectives, what is the best way to get this done with weave gitops".
In the docs we have various recommended or not recommended highlights in docs around how to use specific features, but no definitive guide on how to create a gold-star setup for hypothetical use-cases. Examples include:

https://github.com/fluxcd/flux2-kustomize-helm-example
https://github.com/fluxcd/flux2-multi-tenancy
https://github.com/microsoft/multicluster-gitops
https://fluxcd.io/flux/guides/repository-structure/
https://codefresh.io/blog/scaling-argo-cd-securely-in-2022/

To begin with we should get a list of our users' top hypothetical use cases (along with any constraints, structures or requirements) and pick the top two.

cc @mestadler @joe-terrible

closing to reframe


DELETE /observations/{id} responds with incorrect status code

DELETE /observations/{id}.json without proper credentials (e.g. don't own observation) responds with Status 200 OK. This should respond with Status 401 Unauthorized (like other endpoints).

Hi, @kgarsuta @kueda
Looks like the status code , status: :unauthorized is missing in the render method on this line : https://github.com/inaturalist/inaturalist/blob/183cadef95c3fb4ac841a51d637d818bc24ab348/app/controllers/observations_controller.rb#L2505
Would be agree be agree with me on that ? I'm a newcomer, still new to ruby, rails and oss in general.
Thanks.

When I do curl -XDELETE -v https://www.inaturalist.org/observations/12919932.json I get a 401 Unauthorized response, so I think this got fixed somewhere along the way. Regarding the body of the response, the responses from our Rails API are pretty inconsistent and I don't think we include a status attribute that much. I recommend using our Node API which is a lot more consistent: curl -XDELETE -v https://api.inaturalist.org/v1/observations/12919932. Docs at http://api.inaturalist.org/v1/docs/#!/Observations/delete_observations_id

ok. thank you @kueda. Anything you could suggest a beginner to work on (preferably ruby on rails) ?

First step is to actually get a local version of iNat running, which is no small feat. We have a few other issues labeled easy that might be good to try from there: https://github.com/inaturalist/inaturalist/labels/easy

yeah you were right : bundler is giving me a hard time with puma. Thank you.


Maintain context across calls

Figured I'd drop a note here to ask your opinion before I go implement anything; for context:
My goal is to rig up some fzf vim commands to very quickly search docs without leaving the editor.
I'm imagining running something like this:
hdc $currentWord | rg '^\d+' | fzf --tac | rg '^(\d+)' -or '$1' | hdc

Breaking it down:

hdc $currentWord: Search hoogle for the word under the cursor (or type one myself)
rg '^\d+' use ripgrep to find the list of possible results (all result rows start with a number)
fzf --tac use the fzf fuzzyfinder to interactively select which result I want docs for
rg '^(\d+)' -or '$1' | hdc pull out only the number from the selected line and pass it to hdc to give me the docs.

Currently this doesn't work because hdc loses all of its context in between invocations.
I'm wondering, do you have ideas on how best to solve this? Ideally hdc would have fuzzy-find built-in, but that might be a bit too much to ask, and would only help support this very specific workflow.
Although it's a bit of a hack since it might cause confusion if multiple scripts are running at once, I'm wondering if stashing the context on exit and re-loading it on startup would be a reasonable solution here?
Perhaps a more reasonable solution would be to simply rely on the search being cached and provide a full query as the second search?
Let me know your thoughts, thanks!

Looking into this further, I think it would work well to allow a query like:
> async 2

Which would search for "async" then immediately select result 2.
This way I could write my command like this:
hdc $search | rg '^\d+' | fzf --tac | rg '^(\d+)' -or "$search \$1" | hdc

And we avoid any conflict between multiple scripts, the cache makes this plenty fast :)

I see what you mean.
You may it difficult to do it using rg to select the lines. Lines are cropped at 80 characters, so if a type signature is too long your script wouldn't show all of it.
It might be more worth it to have an editor command that would drop you into an interactive session in hdc with the results for the word you are interested in. There wouldn't be fuzzy-finding but you would be able to select an option by number or by infix using the / notation.
Currently this is not possible as the only two modes are interactive, which has no starting search, or non-interactive, which accepts a term to search but exits immediately.
A new flag could be added, --interactive, which forces the execution to be interactive even if an initial search term is provided.

A new flag could be added, --interactive, which forces the execution to be interactive even if an initial search term is provided. Do you think that would work with your setup?

@lazamar, it would've been great if you could implement it.
I'm planning to use the same workflow as @ChrisPenner described.

@andreystepanov I'm away from my computer now, but does it work if you pass the input through stdin instead of as an argument?

@lazamar Thanks for quick reply.
It seems i can pass selection number using this command:
echo -e "map\n2" | hdc

And the output would be:
...
3  map :: (Word8 -> Word8) -> ByteString -> ByteString
   bytestring Data.ByteString, bytestring Data.ByteString.Lazy,
   rio RIO.ByteString, rio RIO.ByteString.Lazy
2  map :: (a -> b) -> NonEmpty a -> NonEmpty b
   base Data.List.NonEmpty, base-compat Data.List.NonEmpty.Compat,
   rio RIO.NonEmpty
1  map :: (a -> b) -> [a] -> [b]
   base Prelude, base Data.List, base GHC.Base, base GHC.List, base GHC.OldList,
   ghc GHC.Prelude.Basic, base-compat Prelude.Compat,
   haskell-gi-base Data.GI.Base.ShortPrelude, relude Relude.List.Reexport
search: map
==================================================
map :: (a -> b) -> NonEmpty a -> NonEmpty b
base Data.List.NonEmpty, base-compat Data.List.NonEmpty.Compat, rio RIO.NonEmpty
Map a function over a NonEmpty stream.
https://hackage.haskell.org/package/rio/docs/RIO-NonEmpty.html#v:map
https://hackage.haskell.org/package/base-compat/docs/Data-List-NonEmpty-Compat.html#v:map
https://hackage.haskell.org/package/base/docs/Data-List-NonEmpty.html#v:map
==================================================
search: map
> ⏎

So it first sends function  name to search for, and then selection number.
But i still exits immediately, and the plan was to stay in interactive mode and play around with different searched (in case i selected a wrong option).


I have created two users and kept them in same group. Each user has created his own folder at home .Will they be able to view each others folder?

no, currently folder sharing is not supported. Each user can see only his/her folders.

cannot we enable that?


Contribution to "Deeply nested json in jackson-databind"

Updates

Affected products

As per https://github.com/FasterXML/jackson-databind/compare/jackson-databind-2.13.2...jackson-databind-<IP_ADDRESS>


fix(Confluence) -  prevent type issue on pageId

Description

The confluence CLI command confluence upsert-page is current unusable because of a type issue: Error: Invalid command: Expecting string at 2.args.pageId.0 but instead got: 9....,Expecting undefined at 2.args.pageId.1 but instead got: 9.....
This issue comes from the validation we enforce between our types ConfluenceCommandType and the values coming from minimist; since the pageId looks like a number it will be parsed as a number by minimist, which then fails the validation.
This PR fixes this issue by vaildating the value as a number and then parsing it as a string: it is a correct validation because the pageIds should look like numbers (we can't pass custom arguments to parseArgs just for Confluence).

Risk

Very low, at worst the commands do not run.

Deploy Plan

Deploy connectors.

👍 This is annoying and not the first time we have that issue.


Push to Docker Hub

Create Docker images for Aurora scheduler, executor (+ Mesos slave) and CLI and push them to Hub.

Done, see https://hub.docker.com/u/pkleindienst/.


Edited SVG image via Adobe Illustrator

Edited SVG cloudbridge image using Adobe Illustrator and updated the associated raw text file here. Added a box around Network and changed the colors of some boxes.

Thanks!


Fix/registration pages

Closes #64

I could resolve some of the comments, but some of them can't be fixed at the moment since we use the default Django views for this functionality.


[Feature Request] vue-i18n-loader for extracting all components' $t() key to JSON file

What is Expected?
@kazupon There are many case that we need an i18n json manifest file which contains this project's i18n, and give it to our Project Manger for professional translation in a big project development process.
If we write the i18n in the component, we need to change all component i18n code for translation(maybe the PM will set down beside you and search which translation is not good or not done each time), I think it is not a good idea for development process.
So we should have this feature for better our life, it is the i18n extract.
// for webpack config file
module.exports = {
  module: {
    rules: [{
      test: /\.vue$/,
      loader: 'vue',
      options: {
        loaders: {
          i18n: '@kazupon/vue-i18n-loader'
        },
        extract: true // new option to tell loader if we extract all components' i18n
        extractPath: './dist/i18n/[name].json' // i18n output location
      }
    }]
  }
}

Just like the webpack configuration above, it will be done.
For static translation:
We should not write <i18n> or locales in *.vue files. Just write your $t('userName') in the code, and the loader will output the file automatically.
{
  "en": {
    "userName": "userName" // maybe just output original string or on placeholder?
  },
  "jp": {
    "userName": "userName"
  }
}

If the translate has already changed, the output will not overwrite the value, just keep it.
For dynamic translation (UPDATED):
Write your $t(yourVariable, yourI18nList), and give the possible i18n key list, just likevar yourI18nList = ['your possible i18n key1', 'your possible i18n key2', 'and so on']. And then, let it go!

release out! vue-i18n-locale-message!
https://github.com/kazupon/vue-i18n-locale-message/releases/tag/v0.1.0


Extend tests for VM floating-point arithmetic ops

We'll likely want to avoid such bitwise equality tests on floats but if this passes it's fine for now. As part of removing the check module I've been meaning to add a vm.check.near_eq that uses ULP-based comparisons and we could fix this as part of that work. Filed https://github.com/google/iree/issues/5854.


Pass NetworkOperation error if present when operation finishes

Hi again! I noticed that when wrapping a NetworkOperation in a RetryOperation, it would never retry because the error is not passed. Passing the task error in finished() seems most straightforward to me (it is nil for successful operations) but I'm happy to consider other approaches.

Hi @estromlund - yeah, seems to be a bit of an obvious one! 👍
Is there any chance you could send this PR to swift/2.1 though? The development branch has moved on to Swift 2.2. Alternatively can you pull development into your fork and update your branch?

No problem, just created #260 on swift/2.1


USB-to-Ethernet Hub cannot be detected when I upgrade EFI to v3.1.0

USB-to-Ethernet Hub cannot be detected when I upgrade EFI to v3.1.0
I have a USB-to-Ethernet hub connected to the right port (type-c) (not Power Source port) by matedock-2. The LAN (labeled as "USB 10/100/1000 LAN" in normal) cannot be detected when I upgrade EFI to v3.1.0. However, the USB ports on the HUB can be recognized, but only usb2.0.
Previous EFI Version: I do not remember which version is used now ...
HUB model: Lenovo USB-C to RJ45 Adapter C506.
The "USB 10/100/1000 LAN" is recognized as different USB versions.
It is noted that this difference does not affect my daily use, but it does exist.
When the USB-to-Ethernet Hub is connected to the left type-c port (close to the 3.5mm earphone jack), "USB 10/100/1000 LAN" works as usb3.0.

When the USB-to-Ethernet Hub is connected to the right type-c port, "USB 10/100/1000 LAN" works as usb2.0.

@wswn Could you provide your previous working EFI, please?

@profzei Sure. The original EFI folder has been compressed and uploaded as the attached file "EFI-Origin". Please check it
EFI-Origin.zip
.

Did you also update to Monterey recently? Monterey has introduced USB problems that sound quite the symptoms you're seeing: https://screenrant.com/macos-monterey-breaking-usb-hubs-user-reports/

@wswn
From a technical point of view there is no difference in USB stuff and support between actual EFI and what you reported: all is unchanged from almost one year!
@unverbraucht Thank you for your report!
Today OpenCore v. 0.7.5 has been released: I'll make very soon a new release for supporting some Bluetooth fixes, but atm nothing else since I'm very busy in real life...

@unverbraucht
Thanks for your advice. It doesn't seem like a problem introduced by the macOS version changing because I keep using Big Sur 11.5.
@profzei
Thank you, profzei! I re-upgrade EFI to v3.1.0 now and find the hub mentioned above works fine when connected to the left type-c port. But it's still weird that the hub can no longer work as usual (a usb2.0 device as before) when connected to the right port.
I noticed that the USB 3.1 bus disappeared in v3.1.0. Is that related to this problem?
Here are some screenshots:
When the hub is plugged into the left port.
![3451635852649_ pic_hd](https://user-images.githubusercontent.com/9503473/139845025-4d7e33df-aacf-4a73-8f87-5315004d4410.jpg

When the hub is plugged into the right port.

@profzei Very thanks for your reply and clarification! I think I get the idea...
The right type-c port (actually type-A port) supports usb3.0 only if Thunderbolt is enabled.
I naively think both type-c ports can provide USB3.0 even if Thunderbolt is disabled... But, I'm still confused: Why the USB-Ethernet Hub can no longer work as a USB 2.0 device when plugged into the type-A port? it works fine though it works on USB2.0 protocol in previous EFI.


Better way to manage telescope extensions

Currently, telescope extensions are all inside of the telescope.nix file. That means this file will get bigger and bigger the more extensions we add to it.
I would suggest we use separate files for the extensions just like with the lsp plugins. Would that be a good idea?

Oh good idea, yes. Kind of like it's being done for LSP. Should probably do
it for treesitter, too. I'm kinda busy right now but I should be more free
to work on this after Christmas!
A quarta, 22/12/2021, 19:41, Builditluc @.***> escreveu:

Currently, telescope extensions are all inside of the telescope.nix file.
That means this file will get bigger and bigger the more extensions we add
to it.
I would suggest we use separate files for the extensions just like with
the lsp plugins. Would that be a good idea?
—
Reply to this email directly, view it on GitHub
https://github.com/pta2002/nixvim/issues/10, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABYZLTESDP2WMVLTZCFLSITUSISWVANCNFSM5KTIFO7A
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I'm kinda busy right now
No problem, I can work on it.

Thanks for the PR :) Fixed by #11


Since 0.1.3, InputDataError: Constructor is not found in ABI

Since v0.1.3, with #39 merged, it is harder to decode simple functions when the provided ABI does not include contructor metadata.
In fact, before 0.1.3, decode_function() and decode_contructor() where specifialized functions.
With the new class, both are mixed, and one needs to provide too much information IMO: the class requires stuff for the constructor, and stuff for functions.
As a potential solution, we could split the InputDecoder class like:
class InputDecoderContructor:
    def __init__(self, abi):
        self._constructor_type_def = get_constructor_type(abi)

    def decode_constructor(...): ...

class InputDecoderFunction:
    def __init__(self, abi):
        self._selector_to_type_def = {}
        for type_def in abi:
            if type_def["type"] == "function":
                selector = function_abi_to_4byte_selector(type_def)
                self._selector_to_type_def[selector] = type_def

    def decode_function(...): ...

class InputDecoder(InputDecoderContructor, InputDecoderFunction):
    def __init__(self, abi):
        InputDecoderContructor.__init__(self, abi)
        InputDecoderFunction.__init__(self, abi)

Maybe not the best approach though. WDYT about preserving the pre-0.1.3 behaviour?
I can provide a PR if you would like to :)

Thanks for pointing out this. It's okay to postpone the error when decode_constructor is called.
By the way, can you provide some test data on this?

Indeed. I am decoding swap inputs.
I am using such simplified ABI:
[
    {
        "name": "swapExactAVAXForTokens",
        "type": "function",
        "inputs": [
            {"name": "amountOutMin", "type": "uint256"},
            {"name": "path", "type": "address[]"},
            {"name": "to", "type": "address"},
            {"name": "deadline", "type": "uint256"}
        ],
        "outputs": [
            {"name": "amounts", "type": "uint256[]"}
        ]
    }
]

And then decode TX data as usual.

Thanks for the quick response 👍

0.1.4 has been released 😄


EntityArchetypes not accepting Data Keys properly

This issue was originally submitted by @Xenmai in SpongePowered/SpongeAPI#1838.

Hi there.
I'm having an issue when giving keys to entity archetypes. I've tried both inside the builder using EntityArchetype.Builder#set(Key, Value) and with an already built EntityArchetype using DataHolder#offer(Key, Value). The latter returns an unsuccessful DataTransaction, even though I'm checking if the DataHolder supports the key first (and it does).
So it seems EntityArchetypes are not accepting Data Keys at all.
Also on a side note, when creating an entity with EntityArchetype#apply(Location<World>) and then spawning it, I get an error about Minecraft not being able to track the entity properly. The full error can be found here: https://pastebin.com/0Y0Tnwhz
Thanks a lot for your help and have a nice day!
Note: I'm using spongevanilla-1.12.2-7.1.0-BETA-48.jar.
Note 2: I've checked some SpongeCommon code (this issue should probably be moved there, sorry), and inside SpongeEntityArchetypeBuilder the #set(Key, Value) and #set(Value) methods seem to use a NBT processor of type "Tile Entity", not an "Entity" one. Could this be causing the issue? I'm confused as to why that method seems to be coded to work just for Tile Entities, can't I give keys to an Archetype of type Entity? Thanks again for your time!

I think I found the real issue. When entity archetypes were implemented, supports() returned true for any unknown data because of the possibility of custom data. In reality, however, neither custom data nor vanilla data (https://github.com/SpongePowered/SpongeCommon/issues/950) appears to be implemented for archetypes at the moment... not sure what happened to that. All I see implemented is FlyingData, and just the manipulator for that.

Part of the issue is that we haven't written the data implementation to read data manipulators from raw nbt.

@gabizou are they ready to just smash out in bulk? or is there supporting code missing?

A little of both. I haven't written it to work yet, but the processor for retrieving the not Is there.

https://github.com/SpongePowered/SpongeCommon/issues/950


rename package lib-caffe-bvlc-opencl-cpu-universal2 #61

Installation for Ubuntu works fine after rename:
Installation time:<PHONE_NUMBER>12 sec.


Provide API to retrieve access_token for calling backend services

According to the docs there seems to be no way to get a hand at the access_token of the current user.
It would be very helpful if flask-oidc would provide a easy way to retrieve an access_token for the current user to make requests to other services.

Just saw that this is a duplicate of #29


Setting the Flow Control MaxOutstandingElementCount cause stuck messages

The behaviour was observed in the 0.21.1-beta version of the Java client library
It seems resolved in the 0.23.1-beta version, however this newer version implements the bi-directional streaming pull and the previous doesn't.
Test Setup:

100k messages published to a Topic
Single Subscription
n Subscribers (k8s running on GKE, each pod running in separate node) {n ∈ Z |  1 ≤ n ≤ 4}
Each node had 2 vCPU and each Subscriber provided 10 user threads to the client library
All Subscribers running the same code (Parse message, build various classes, callback processing takes ~20ms)
Flow control settings: MaxOutstandingElementCount: 1000
Results:
n Messages remain stuck on Topic n  ∈ [223, 6652]
Observations:
When messages are stuck: mod_ack_deadline_request_count  > 0, Pull request count > 0
When messages are stuck Subscriber callback threads are Waiting
No stuck messages when retesting with default Flow Control Settings (i.e. MaxOutstandingElementCount = null)
Experiments with MaxOutstandingElementCount ∈ [1000, 500, 250, 125] resulted in stuck message count ∈ [~6K, ~3K, ~1.7K, ~6K]

Interpretation:
Message ACK deadlines are being continuously extended and the callback threads are not being invoked

@robertsaxby It sounds like the subscriber application code executes the listener MessageReceiver (parsing the message, etc), but never calls AckReplyConsumer.ack for some messages.  Can you confirm that:

The MessageReceiver implementation actually calls AckReplyConsumer.ack explicitly in the user code.
That for stuck messages the listener code executes successfully, including a call to .ack?

Got answers offline: The call to .ack happens successfully in the application code, but the acks are never actually sent.

I'll look into this, but @robertsaxby is there any reason you cannot move to streaming pull?

Good news is I can reproduce this. I'm working to determine the root cause.

I found the problem. @davidtorres @mdietz94
The bug is actually in MessageDispatcher::processOutstandingBatches. The method works roughly like this:

We keep a queue of messages we pulled but haven't processed (outstandingMessageBatches)
We pull one message, and try to reserve a spot for it. If there's no spot left, do nothing, and the message stays in the queue.
If we get a spot, process the message.
After processing, call the method again.
The idea is that if the flow control is full, then there's at least one message executing. When we finish, it will cause us to process more.

The problem is that we have many MessageDispatchers but only one FlowController. Consider a scenario where the flow controller has room for 1 message, but we have dispatchers, A and B.

A and B pulls 1 message each
A gets the spot

This means B stops at step 2 above

A executes its message
When the message finishes, A looks for more work in its own queue and doesn't realize B has a message. B's message will sit in the queue forever. Of course, B dutifully extends the message's deadline.

This explains @robertsaxby 's observations (I split out the points a little differently)

n Messages remain stuck on Topic

those messages are in B's queue

When messages are stuck: mod_ack_deadline_request_count > 0

B is extending the deadlines

When messages are stuck: Pull request count > 0

B is stuck, but A isn't; the pulls are probably coming from A

No stuck messages when retesting with default Flow Control Settings (i.e. MaxOutstandingElementCount = null)

because in step 2 there's always a spot left, so we always reach step 3.

I see two ways out of this:

Make all dispatchers share the same queue.
This will probably increase contention. I have an idea that might reduce it.
Give every dispatcher its own control flow (where each has totalSlots/numDispatchers slots).

David and Max, do you have a preference? I'm leaning towards 1.

@pongad : The reason @robertsaxby went back to the original library was to work around the idle streams issue.

I agree with 1, I think each having its own control flow will lead to poor flow control behavior if the dispatchers do not fill fairly.

Also agree with 1
David Torres | Senior Software Engineer |<EMAIL_ADDRESS>| +1
212-565-9096
On Wed, Sep 20, 2017 at 11:30 AM, Max Dietz<EMAIL_ADDRESS>wrote:

I agree with 1, I think each having its own control flow will lead to poor
flow control behavior if the dispatchers do not fill fairly.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-java/issues/2452#issuecomment-330889182,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEnLq3kjB4biFTinNXZwDzsg9wddP1KGks5skS-VgaJpZM4PcSPW
.


Disable full backfill action

Disabling backfill Job action since it was intended to run only one time.
Later, it will be a cron job (But should backfill only missing cache records in order to avoid appending too many jobs).

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

I'm not sure how the jobs work, but I imagine that we have to wait for the previous upgrade to finish (ie for the post-upgrade job to finish) before deploying again, no?

I'm not sure how the jobs work, but I imagine that we have to wait for the previous upgrade to finish (ie for the post-upgrade job to finish) before deploying again, no?
cc @rtrompier

Yes, I confirm.

Merging because @AndreaFrancis is off


[Transaction] Add transaction integration test

Motivation
Currently, the transaction is a lack of integration test for validation.
Modifications
Add transaction integration test, the test based on the mock transfer business scene.
Verifying this change
This change added tests and can be verified as follows:

org.apache.pulsar.tests.integration.transaction.TransactionTest

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (no)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)

/pulsarbot run-failure-checks


How to sort by down websites first?

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

📝 Describe your problem
Sorry if been asked before, can't find it...
I can't see how to get my down status websites to the top of the list. The status list is no good, as it just shows the status changes in date descending order, not the ones that are down still. Not having down websites at the top means it's harder to review and find them.
Example use case... Let's say one of my servers go down, so I get 100 down alerts. Then it comes back up and I have 99 up alerts. The status list will show 100 down, then 99 up. BUT if one or more of those sites stays down for whatever reason, then it's not easy to find when you have a long list of websites. Its not at the top in the status list nor the website list. I have to scroll down my website list slowly until I find it. Sometimes I like to review uptime monitor to make sure everything is up, and my old system would just list down sites at the top, but this system I have to scroll down my huge list.
So is it possible to sort by down at the top, or do I need to make a feature request?
Thanks
🐻 Uptime-Kuma Version
1.17.1
💻 Operating System and Arch
Ubuntu 20.04
🌐 Browser
Chrome latest
🐋 Docker Version
No response
🟩 NodeJS Version
No response

Realized in #1585

I'd like a reply yes it's very important to have this feature

@amityweb  - it seems like we've got a lot of tickets open referencing the same features, which splits up the responses and keeps this from rising to the top.  Is there anything in this ticket that's not covered in #1585 where there's already a pull request?  If not, can you close this?


FixedDimension has to go

Full discussion on slack
Code-generation API can not create interface object that don't make sense for cleanup purposes.

Ok, first of all, polemic titles like this are not helping anyone. FixedDimension objects will most definitely stay, if (and only if) the concept of fixed dimensions even survives at all.
Now for the technical explanation:
a) The introduction of a specialised FixedDimension type is not merely "for cleanup purposes"! The concept of fixed dimensions is naturally incompatible with certain aspects of more advanced features that we are working on, eg. checkpointing or MPI support. As such, having regular dimensions and fixed ones present as the same object type throughout the code generation engine is making developing these features extremely difficult. Hence separating the types makes a lot of sense, and paves the way for these new features.
b) The real problem with fixed dimensions is that the default dimension used by function symbols are currently managed globally, and thus runtime injection of specialised dimensions is tricky at best. This is the reason that the fixed-dimension test in test_adjointA.py was recently disabled. A more comprehensive solution to this problem is to not use global dimension symbols as defaults, but build them on a per-case basis. This can be done via the newly introduced Grid classes and I'm working on a new API to facilitate just that.
c) Important: The concept of a "fixed dimension", ie. hard-coding loop bounds, is a purely low-level compiler feature and not part of any formal mathematical abstraction Devito provides. It is largely kept around for legacy purposes and was introduced as an implementation shortcut in Devito-2.0 (Propagator). As such, no high-level domain-specific application should depend on this feature! After all, Devito operators are supposed to be black boxes where the engine decides how best to solve the given mathematical definition in the fastest way, leaving low-level implementation details, such as loop bounds, to the compiler engine. This is the essence of software abstraction!

FixedDimension objects will most definitely stay, if (and only if) the concept of fixed dimensions even survives at all.

Since when?

features that we are working on, eg. checkpointing or MPI support. As such, having regular dimensions and fixed ones present as the same object type throughout the code generation engine is making developing these features extremely difficult

After spending three weeks telling me that the features we are working on is not an argument for not having it, the argument is because your features need it?

The concept of a "fixed dimension", ie. hard-coding loop bounds, is a purely low-level compiler feature and not part of any formal mathematical abstraction

I don't agree, wether the loop size is in the signature or the loop itself, the problem solved is exactly the same. FixedDimension decides it's not. The mathematical abstraction/problem does not care where the dimension size is known.

Devito operators are supposed to be black boxes where the engine decides how best to solve the given mathematical definition in the fastest way, leaving low-level implementation details, such as loop bounds, to the compiler engine.

Except now, Devito doesn't decides anything, there is only "all loop size must be inputs" choice because you decided so.

FixedDimension objects will most definitely stay, if (and only if) the concept of fixed dimensions even survives at all.

Since when?

Fixed dimension are an obsolete feature ever since the generalization of loop bounds in Devito-3.0. They have no proven benefit and cause a large amount of unnecessary special-casing in the code generator. The only reason they still exist is because SLIM depends on them, and the API change was needed to amortize the codebase against existing and further special casing, so that we can move forward. Therefore the class FixedDimension needs to stay, while the API to enable their usage is still under development.

After spending three weeks telling me that the features we are working on is not an argument for not having it, the argument is because your features need it?

Both arguments are true, none are relevant to the discussion; the codebase becomes cleaner and it makes further development easier.

I don't agree, wether the loop size is in the signature or the loop itself, the problem solved is exactly the same. FixedDimension decides it's not. The mathematical abstraction/problem does not care where the dimension size is known.

Brilliant, we agree: the mathematical abstraction does not care about a known dimensions size. Hence, any high-level seismic abstractions should not either, as it does not change the behaviour of the operator that Devito generates from the given problem specification.

Devito operators are supposed to be black boxes where the engine decides how best to solve the given mathematical definition in the fastest way, leaving low-level implementation details, such as loop bounds, to the compiler engine.

Except now, Devito doesn't decides anything, there is only "all loop size must be inputs" choice because you decided so.

Devito does make a decision and it is not to use fixed dimensions(!) - again, because they have no proven value except for legacy compatibility. The statement that "all loop size must be inputs" is also simply false(!), since Devito will figure them all out for you during the operator.apply() call.  This interface is the official interface to use for Devito operators! If you choose not to use these public and supported interfaces, and instead bypass the parameter automation step, it will create a massive amount of work on the application side as we develop Devito and implement further features, which ultimately constitutes a non-maintainable model of software development (more in the relevant slack channel).

Agreed on and fixed in #373, closing


Support combined rust and c application

I want to trace a C application running on hermitcore with my tracer written in rust (rftrace). I'd ideally want to:

compile the kernel into a static library libhermit.a
compile the rust library into a static library librftrace_frontend_ffi.a
compile the C application, linking to these two (gcc main.c -lhermit -lrftrace_frontend_ffi -o main)

I got it working, but this currently requires a number of workarounds:

duplicate runtime_entry:

the rust-library needs std. std defines runtime_entry, so does newlib which the c app requires.
workaround: remove runtime_entry symbol from the library. As far as I can see this will only affect environment variables, which I dont need and some destructors, which are not strictly needed since the OS will shut down on exit. (objcopy --strip-symbol runtime_entry librftrace_frontend_ffi.a)

OOM exceptions

currently, only 4MB of heap space is allocated for the "kernel" if we enable the newlib feature. This is not actual kernel heap, but all of rust heap. (sidenote: this might also be an issue even if not linking rust+c together, depending on how the virtio virtqueues are utilized)
workaround: patch kernel to increase the size. (let size = 100 * LargePageSize::SIZE; in /src/mm/mod.rs::init())

errors about non-defined functions like sys_tcp_stream_connect

the rust stdlib includes hermit-abi, which contains all "systemcalls". Since the networking changes, there are now a bunch of functions which are not defined in the kernel, but in hermit-sys.
workaround: define empty stub-functions in the c source.
it might be possible to compile hermit-sys as a static library and link against it instead of libhermit.a? I have not investigated this further

@tlambertz I oversaw this issue. I merged the latest version of libhermit to this project. However, some test cases didn't run. I will solve it.

Now, the latest version of lib hermit-rs is able to run C applications. Now, I will look in your problems.

Do you want to use Rust`s libstd in combination newlib?

Yes, this is essentially what I want. libstd in a library, linked to a newlib C application.

Hm, difficult... Currently, Rust's libstd uses another memory layout in comparison to newlib. That this the reason, why we forward the feature flag newlib during the build process of libhermit, if we use it in combination of newlib.


Add Jekyll favicon

I really like this, Jonathan. Wanna update the PR with storing the icon file locally in the repo and referencing that?
Then I'll merge this in.
That way if the URL ever changes on jekyllrb.com we won't have to worry about everyone's blog icons being broken :)

@barryclark Yes, I agree. It should be a relative reference if you want to store the favicon on the repo.

@dijonkitchen wanna update the PR to add it, and I'll merge?

@dijonkitchen @barryclark What happens with this? Is it gonna be merged?

@dijonkitchen @barryclark What happens with this? Is it gonna be merged?

Sorry, been really busy. Feel free to do this yourself!

Sorry, been really busy. Feel free to do this yourself!

The only one who can merge this is @barryclark I'm afraid ;-)

The only one who can merge this is @barryclark I'm afraid ;-)

I've opened a PR #481 and added a commit after the initial commit by @dijonkitchen.


Versions

Actually, three birds with one pull request...

Testing. I noticed that the tests originally didn't test anything. They just tested that true === true. Now they test things with a database and everything.

Dependency updates. Updated a bucketload of dependencies. Can't promise I did the right thing with all of them, but nothing screams, the tests succeed, and there are no vulnerabilities with npm audit.

Versions. The reason I did this. This is explicit versioning. Whereas paper trails provides fire-and-forget zero-action revision tracking, I've added Model.newVersion(), which will increment a version counter, and reset the revision counter. Handy for when you want to make an explicit break/signpost for a record (getting ready to dig into a project where having explicit versions will be handy, and I figured, why re-invent the wheel?)

PLEASE review my changes (and/or have others review them). There may very well be a nasty hive of bees hiding in there, despite my best efforts and intentions.

I do like everything besides newVersion . Could you do it without that change?

Sure could. Give me a few...


Ordering between flag and flag_if_supported is not maintained

C and C++ compilers consider the ordering of arguments important and semantic. However, if you construct a builder like this:
cc::Build::new().flag_if_supported("-xc").flag("-xc++").flag("-std=c++11")

the constructed command line will look like this:
$CC -xc++ -std=c++11 -xc ...

which will then error (or warn...), even though the otherwise nonsensical, but valid invocation would be
$CC -xc -xc++ -std=c++11

Some valid use-cases of this ordering generally involve overriding previous arguments.

As far as fixing this is concerned, I imagine we would maintain some sort of a per-Builder sequence index that gets associated with each flag pushed to one of the many vectors that are used to maintain these flags.
So instead of flags: Vec<Arc<str>> or flags_supported: Vec<Arc<str>> we'd have flags: Vec<(usize, Arc<str>)>, flags_supported: Vec<(usize, Arc<str>)> and so on for all the flag vectors. Then, in the try_get_compiler function we’d carefully draw from all vectors with flags in the order of usize sequence numbers. This may end up being slower, but with how many flags there are generally, it shouldn’t pose a problem.

You mean it would be breaking to fix the ordering because someone might be relying on us using the current order? I suppose that's true, but I'm not worried about it. We never wrote down that this is the behavior, and this isn't a crate where we'd get anything done if we preserved Hyrum-esque stability promises.
I think I'd take a PR for this if it was reasonably implemented. I don't have a strong opinion between enum vs (usize, Arc<str>), either is fine (the enum approach seems simpler, though). Obviously if the enum approach is used, the type should not be part of the public API.

You mean it would be breaking to fix the ordering because someone might be relying on us using the current order?

That too, but especially that now
Build().flag_if_supported("-foo").flag("-bar").flag("-baz")

will test whether appending -foo is valid for $CC -bar -baz rather than testing $CC without arguments yet and for some arguments I suspect that might make a difference :shrug:


Using slots and props with the component

Hi Vaadin team,
Super work for this router, really easy to use!
I am wondering whether it is possible to specify props and slots for the components defined in the routes. For example, something like:
[
  --- SNIP ---
 {
        children: [
          { component: 'my-service-view', path: '/compliance', props:".data=${compliance}" },
          { component: 'my-service-view', path: '/penetration-testing', props:".data=${penetration-testing}" },
        ],
        path: '/services',
      },
}
 --- SNIP ---
]

With ${compliance} and ${penetration-testing} being JSON objects.
Looking forward to an answer,
Best,
Alex

This is not currently supported.
We recommend using URL parameters (which obviously can't be used for passing JSON data).
Then the view components can fetch the data based on those.

@aress31
Hey, I know it's been a little late but you could use the action property instead of component when describing the child routes.
[
  --- SNIP ---
 {
        children: [
          {
            path: '/compliance',
            action(_context, _command): HTMLElement {
               const myServiceView = document.createElement('my-service-view');
               myServiceView.data = compliance;
               return myServiceView;
             }
           },
                    {
            path: '/penetration-testing',
            action(_context, _command): HTMLElement {
               const myServiceView = document.createElement('my-service-view');
               myServiceView.data = penetrationTesting;
               return myServiceView;
             }
           },
        ],
        path: '/services',
      },
}
 --- SNIP ---
]


ImageWorker: Only one of two simultaneous requests for the same src url resolves

If two requests for the same URL happen at the same time to the ImageWorker only one of them resolves.
This is because the ImageWorker uses the src as the sole key when tracking messages between the main thread and the worker thread.

Blocker for a test I'm writing for #170


Obtain cropped mesh of the scene

Hi,
I am writing to know if there is any easy way to obtain a crop or a segment of the mesh of the scene surrounding the vehicle. I would like to have this because I am testing an algorithm for scene reconstruction from pointcloud using the simulated lidar and I would like to compare my results against the actual real mesh of the scene. Having the possibility of extract the mesh of a portion of the scene, (equivalent to what it has been scanned by the simulated lidar) would be awesome.
Thanks in advance.

Hi @luigui2906, thanks for the interest on Carla.
This is something we want to make in the future but currently, we don't have anything like that.
You can modify the server and create some kind of sensor that does such a thing.

Hi @marcgpuig. Ok. Thanks for the answer.


HTTP Connector - Support for timeout, error handling and retrying

This feature should primarily cover all the error handling requirements, timeout handling, and retrying mechanisms.

Hi Kasun,
We have implemented timeout and retrying.
For error handling, we have created specific tasks,
https://github.com/ballerinalang/ballerina/issues/3951
https://github.com/ballerinalang/ballerina/issues/4025
Hence, closing this issue.


consistency in DOI capitalization (not 'doi') in XML

Closes #445

Coverage increased (+0.003%) to 36.676% when pulling fed8ffac30ca18004d6f467447577d820a843eae on bnewbold:bnewbold-tei-doi-capitalization into 4ef11633cedca0994539e26a00327a5f9cba2900 on kermitt2:master.

Thanks !


Dev server v2 kills arc sandbox ungracefully, not giving sandbox plugins a chance to clean up

What version of Remix are you using?
1.18.1
Are all your remix dependencies & dev-dependencies using the same version?

[X] Yes

Steps to Reproduce
When you are using dev_v2 mode in an Architect app, when you interrupt npm run dev with ^C, it kills all subprocesses with extreme prejudice and does not permit Architect plugins to clean up.
To reproduce:

Start a basic Architect project using create-remix.
Add a toy sandbox plugin that has a start method (which would normally start a sidecar process --- such as an OpenSearch server) and a stop method (which would normally stop the sidecar process and delete any temporary directories). For example:

plugin-sandbox.js
export default {
  sandbox: {
    start() {
      console.log("starting example sandbox plugin");
    },
    end() {
      console.log("stopping example sandbox plugin");
    },
  },
};

Install this plugin in app.arc.

app.arc
...
@plugins
plugin-remix
  src plugin-remix.js
plugin-example
  src plugin-example.js
...

Fire up the dev server using npm run dev. Wait until it's up and running.
Stop the dev server with a keyboard interrupt (^C on Linux and macOS).

Expected Behavior
The dev server should come down cleanly and you should see both of the log messages from the Architect sandbox plugin, both starting example sandbox plugin and stopping example sandbox plugin. Here's the good output with dev_v2: false set. For a reproducer, see https://github.com/lpsinger/remix-bug-report-arc-sandbox-killed-ungracefully/tree/dev_v1.
$ npm run dev

> dev
> npm-run-all build --parallel "dev:*"

> build
> remix build

 info  building... (NODE_ENV=production)
 info  built (315ms)

> dev:remix
> remix watch

> dev:arc
> cross-env NODE_ENV=development arc sandbox

Watching Remix app in development mode...
💿 Building...
         App ⌁ remix-architect-app
      Region ⌁ us-west-2
     Profile ⌁ @aws profile / AWS_PROFILE not configured
     Version ⌁ Architect 10.13.1
         cwd ⌁ /private/tmp/my-remix-app

✓ Sandbox @http (HTTP API mode / Lambda proxy v2.0 format / live reload) routes
    any /* ................................ server

    http://localhost:3333

✓ Sandbox Started in 9ms
❤ Local environment ready!

⚬ Sandbox Running 1 Sandbox startup plugin
starting example sandbox plugin
✓ Sandbox Ran Sandbox startup plugin in 7ms
✓ Sandbox File watcher now looking for project changes
💿 Rebuilt in 441ms
[REMIX DEV] D7AD53A4 ready
^C
⚬ Sandbox Running 1 Sandbox shutdown plugin
stopping example sandbox plugin
✓ Sandbox Ran Sandbox shutdown plugin in 0ms
^C

Actual Behavior
Here's the bad output. You see starting example sandbox plugin, but you never see stopping example sandbox plugin. For a reproducer, see https://github.com/lpsinger/remix-bug-report-arc-sandbox-killed-ungracefully/tree/dev_v2.
$ npm run dev
> dev
> remix dev --no-restart -c "arc sandbox -e testing"

 💿  remix dev

 info  building...
 info  built (536ms)
         App ⌁ remix-architect-app
      Region ⌁ us-west-2
     Profile ⌁ @aws profile / AWS_PROFILE not configured
     Version ⌁ Architect 10.13.1
         cwd ⌁ /private/tmp/my-remix-app

✓ Sandbox @http (HTTP API mode / Lambda proxy v2.0 format / live reload) routes
    any /* ................................ server

    http://localhost:3333

✓ Sandbox Started in 9ms
❤ Local environment ready!

⚬ Sandbox Running 1 Sandbox startup plugin
starting example sandbox plugin
✓ Sandbox Ran Sandbox startup plugin in 4ms
✓ Sandbox File watcher now looking for project changes
^C

I tried to remove all Remix code for killing the app server process, but my system was still killing the app server when remix dev was CTRL-C'd. I tried removing any process.on calls for SIGINT and SIGTERM, clearing out the body of any exitHooks, and setting cleaup: false for execa.
The only way the app server process stayed alive is when I set detached: true for the subprocess, but detached subprocesses are another can of worms and their behavior differs across OSs. Might revisit this later, but if anyone has more insight into what can be done here, would be appreciated.

@pcattori, I think that part of the problem is that arc sandbox itself doesn't handle signals. I opened the PR https://github.com/architect/sandbox/pull/729 to try to address that. Would you please see if your changes on the Remix side work when combined with that PR?

I did some testing on this issue as I could see it as well. I was able to change my docker to use an entrypoint. In my entrypoint I created a signal trap. I was able to trap all signals. This told me that sending signals from outside of docker into docker was working.
I then ensured that I was using exec in the entrypoint so that the second process after docker-init would be npm run dev. At this point it stopped responding to SIGINT and SIGTERM signals. SIGHUP and SIGKILL continued to function. This told me that the issue was possibly with the npm run process itself. I used strace to trace the npm run dev process and I never registered a sigint or sigterm, it was always just instant death.
I went digging and I have found this issue and this PR that I believe may be the cause (or a partial cause) of this issue.
I have updated my npm version to be the most recent version (10.3.0) and I was able to see it close the process in under a second when I use control + c, so I believe this should fix it.

I tried to remove all Remix code for killing the app server process, but my system was still killing the app server when remix dev was CTRL-C'd. I tried removing any process.on calls for SIGINT and SIGTERM, clearing out the body of any exitHooks, and setting cleaup: false for execa.
The only way the app server process stayed alive is when I set detached: true for the subprocess, but detached subprocesses are another can of worms and their behavior differs across OSs. Might revisit this later, but if anyone has more insight into what can be done here, would be appreciated.

@pcattori  could you please ensure your npm version is 10.3.0 and try your experiment again? I am hopeful this is your issue.

I can reliably "gracefully" terminate the child process now, but I have done terrible things to get there. I am hoping though that this at least helps point in the right direction and maybe one of you will advise further.
in in the devServer_unstable/index file, if I replace exitHook__default["default"](cleanup); with:
  state.appServer.on("exit", ()=>{
    process.exit(0)
  })

  process.on("SIGINT", ()=>{
    cleanup()
  })

and then in to the sandbox/src/cli/index file in architect's sandbox I ALSO add this:
    process.on("exit", (signal)=>{
      sandbox.end()
    })

It will work as expected, but not how I would have thought it would. I added an exit event for the child process so that basically when it exits I then can exit the main process. I did this because handling asynchronous shutdown actions was a beast and this way I'm listening on the main process for the child process to reach exit status which then triggers the exit of the main process. Like I said, super duper ugly, but maybe illuminating?
a maybe odd thing:
If I run the process and then I take the PID for the arc process and kill -2 it, everything terminates as expected within arc and the remix process carries on as expected. I put logs in where sdtin/stdout are piped and so I could see what was passed through. When I kill -2 the process, something was passed through STDOUT 3 times and arc received the exit event twice. I would have expected to only get an exit signal once and I would not have expected anything to come through stdout much less 3 times. I'm not sure what it was as it didn't print so I am assuming it's signal. It could be normal but it seemed a bit odd to me. When I control + c it's just the signal and nothing goes through STDOUT (which is expected).

@Courey Thanks for diving deep on this! 🙏
We've been heads down on getting Vite stuff stabilized. We're going to need to clean up some of the CLI code soon anyway, so will try to include some/all of this there. In the meantime, would love any arc experts to help me figure out how best to interop with Vite dev server since that's what we're moving to anyway. I think we can use sandbox to spin up a Vite dev server in middleware mode, and then delegate asset requets and route requests to it within the arc request handler. Conceptually, that all checks out to me, but haven't tried getting it running for real. One piece to figure out is that the Vite middleware is Express-style middleware. So there's a chance we may need to adapt the web fetch standard Request/Response that both arc and Remix prefer to Node-style (i.e. Express-style) IncomingRequest, ServerResponse.

I created this issue with Arc because I was able to isolate the process and send it signals manually and did not get the expected response from arc sandbox, so I thought they might be able to tell me more about that and that might point me in the right direction. That was a red herring. They believe the issue lies with execa and how it handles children of children. They seem extremely helpful and friendly, and I know in your comment you said:

In the meantime, would love any arc experts to help me figure out how best to interop with Vite dev server since that's what we're moving to anyway.
I was hoping to introduce y'all to each other because it sounds like it could be a useful pairing.


cant rotate map without hot reload

hi, how can i rotate the map without hot reload bcz i get angle from compass then i want to rotate the map when angle changes but i couldnt bcz every time i set the rotation i need to do a hot reload to update it.
Thanks in advance.

This should not be necessary. How do you change the rotation?

in the rotation argument u can set that but its not working untill u do some hot restart, i want to rotate the map as compass value get changes.

You have to use the Map Controller for that it has a rotate metheAm 16.09.2019 21:00 schrieb CalmAndCoDe notifications@github.com:in the rotation argument u can set that but its not working untill u do some hot restart, i want to rotate the map as compass value get changes.
—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or mute the thread.

@CalmAndCoDe did that work?

@escamoteur sorry for delay, yeah it solved thanks.


Fix CompactMerkleTree when cloning an empty source tree.

Done reviewing, the change to the code itself looks good, but the test needs a tweak?


Recommend a language expansion pack.

https://github.com/overtrue/laravel-lang

https://github.com/caouecs/Laravel4-lang is the community standard

it's different. you can take a try.

FYI: https://github.com/caouecs/Laravel4-lang/issues/352


koboldcpp: Fix Package Build Failure with CUDA Enabled

Description of changes
When attempting to build the latest koboldcpp with cublasSupport setting to true, I encountered the following error:
koboldcpp> nvcc fatal   : Value 'sm_sm_89' is not defined for option 'gpu-architecture'
koboldcpp> make: *** [Makefile:228: ggml-cuda.o] Error 1
koboldcpp> make: *** Waiting for unfinished jobs....

This PR fixes the following issue by

Fix the value of CUDA_DOCKER_ARCH, and use cudaFlags.realArches instead of cudaFlags.arches.
Correct the usage of makeWrapper.

Issue 1: CUDA_DOCKER_ARCH Contains Duplicated sm_ Prefix
The error appears to stem from the CUDA_DOCKER_ARCH variable being defined with a duplicated sm_ prefix. This occurs in the makeFlags definition:
(lib.optionals cublasSupport "CUDA_DOCKER_ARCH=sm_${builtins.head cudaArches}")

The cudaArches argument, which defaults to cudaPackages.cudaFlags.arches, already includes the sm_ prefix, as seen here:
# realArches :: List String
# The real architectures are physical architectures supported by the CUDA version.
# E.g. [ "sm_75" "sm_86" ]
realArches = archMapper "sm" cudaCapabilities;

# virtualArches :: List String
# The virtual architectures are typically used for forward compatibility, when trying to support
# an architecture newer than the CUDA version allows.
# E.g. [ "compute_75" "compute_86" ]
virtualArches = archMapper "compute" cudaCapabilities;

# arches :: List String
# By default, build for all supported architectures and forward compatibility via a virtual
# architecture for the newest supported architecture.
# E.g. [ "sm_75" "sm_86" "compute_86" ]
arches = realArches ++ lists.optional enableForwardCompat (lists.last virtualArches);

On my machine, cudaFlags.arches evaluates to:
$ nix eval github:NixOS/nixpkgs/master#cudaPackages.cudaFlags.arches
[ "sm_60" "sm_61" "sm_70" "sm_75" "sm_80" "sm_86" "sm_89" "sm_90" "sm_90a" "compute_90a" ]

As a result, koboldcpp.makeFlags[-1] evaluates to CUDA_DOCKER_ARCH=sm_sm_60:
$ nix eval 'github:NixOS/nixpkgs/master#koboldcpp' --apply 'x: (x.override { cublasSupport = true; }).makeFlags'
[ "LLAMA_OPENBLAS=1" "LLAMA_CUBLAS=1" "LLAMA_CLBLAST=1" "LLAMA_VULKAN=1" "" "CUDA_DOCKER_ARCH=sm_sm_60" ]

This causes the build to fail since the Makefile is effectively being passed -arch=sm_sm_XX:
ifdef CUDA_DOCKER_ARCH
    NVCCFLAGS += -Wno-deprecated-gpu-targets -arch=$(CUDA_DOCKER_ARCH)
else

Issue 2: Incorrect Usage of makeWrapper
There is also an issue with the usage of makeWrapper in the postFixup phase:
$ nix eval --raw nixpkgs#koboldcpp.postFixup
wrapPythonProgramsIn "$out/bin" "$pythonPath"
makeWrapper "$out/bin/koboldcpp.unwrapped" "$out/bin/koboldcpp" \
  --prefix PATH /nix/store/a79hjvwbgnn5xrf571hslxgw987ivj4d-tk-8.6.13/bin --prefix LD_LIBRARY_PATH : "/run/opengl-driver/lib"

According to the comments and definition in make-wrapper.sh, the --prefix option requires three arguments:
--prefix ENV SEP VAL   : suffix/prefix ENV with VAL, separated by SEP

Note on Further Improvements
It seems that each -arch option only supports a single value like sm_XX. When using CUDA_DOCKER_ARCH, supporting multiple architectures simultaneously becomes challenging.
I am unsure if it would be better to patch the original Makefile to use cudaPackages.cudaFlags.gencode instead.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Hey @KiruyaMomochi thanks for making this PR! I already made a similar PR https://github.com/NixOS/nixpkgs/pull/329426 but it didn't fix the makeWrapper issues so, I will close it in favor of yours.

Result of nixpkgs-review pr 330038 --extra-nixpkgs-config '{   cudaSupport = true;   cudaCapabilities = [     "7.0"     "8.0"     "8.6"   ];   cudaEnableForwardCompat = false;   allowUnfreePredicate =     p:     builtins.all (       license:       license.free       || builtins.elem license.shortName [         "CUDA EULA"         "cuDNN EULA"         "cuTENSOR EULA"         "NVidia OptiX EULA"       ]     ) (if builtins.isList p.meta.license then p.meta.license else [ p.meta.license ]);   permittedInsecurePackages = [     "electron-24.8.6"     "zotero-6.0.27"   ]; }' run on x86_64-linux 1

1 package built:

koboldcpp

Thank you and sorry for my late response!

Yea I just want a runtime test...

I checked out and built f0ff29350933140f2d69ef044c11414f74e89df2 - my ~/.config/nixpkgs/config.nix was just:
{
  allowUnfree = true;
  cudaSupport = true;
}

I ran it as ./result/bin/koboldcpp <a LLaMa 3 8B GGUF file> --usecublas --contextsize 8192 --gpulayers 33 with a GTX 1080 GPU.
nvidia-smi reported:
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 550.90.07              Driver Version: 550.90.07      CUDA Version: 12.4     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce GTX 1080        Off |   00000000:05:00.0 Off |                  N/A |
|  0%   32C    P8             12W /  180W |    6145MiB /   8192MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+

+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI        PID   Type   Process name                              GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|    0   N/A  N/A     28930      C   ...lgklv72l-python3-3.12.4/bin/python3       6142MiB |
+-----------------------------------------------------------------------------------------+

Generated some stuff, my stats were:
Processing Prompt [BLAS] (7607 / 7607 tokens)
Generating (250 / 250 tokens)
CtxLimit: 7857/8192, Process:25.13s (3.3ms/T = 302.68T/s), Generate:34.71s (138.9ms/T = 7.20T/s), Total:59.85s (4.18T/s)

I'm happy with that!


FINERACT-823 Gradle modernizer plugin

Description
Describe the changes made and why they were made. Ignore if these details are present on the associated Jira ticket https://issues.apache.org/jira/browse/FINERACT-823
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Commit message starts with the issue number from https://issues.apache.org/jira/projects/FINERACT/. Ex: FINERACT-646 Pockets API.

[x] Coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions have been followed.

[ ] API documentation at https://github.com/apache/fineract/blob/develop/api-docs/apiLive.htm has been updated with details of any API changes.

[ ] Integration tests have been created/updated for verifying the changes made.

[ ] All Integrations tests are passing with the new commits.

[ ] Submission is not a "code dump".  (Large changes can be made "in repository" via a branch.  Ask on the list.)

Our guidelines for code reviews is at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide

Thanks for this PR @percyashu ...Next time..before sending a PR, Make sure to run the integration tests locally first using ./gradlew clean integrationTest.. When all passes then can you send a PR... I see this PR has a failure somewhere..Will you like to investigate and find out why? Then update the PR.

@percyashu Please..make sure you complete 1 issue before moving to the next one. THere is no point opening more than 1 PR at a time and try to work on all at same time. In general, thats usually a bad idea especially for new programmers. Finish one, then pick another and you find that you make more progress that way. Leave the other PRs you have opened like that and take one of them to fix before moving to the next.

@awasum I did run ./gradlew clean integrationTest and FixedDepositTest does not fail.

@awasum or @vorburger could you review this.

@percyashu , Please squash these 3 commits into 1.

@awasum OK I will do that

@awasum I have squash them.

@vorburger I resolved all violation except does pertaining to replacing Joda.time with Java.time which will be handle in a PR to issue https://issues.apache.org/jira/projects/FINERACT/issues/FINERACT-826.


Under Ubuntu, if computer sleeps, can no longer launch project

Tested versions
Reproducible on ALL versions of Godot 4.x in Ubuntu.  Haven't noticed this issue on Windows
System information
Godot v4.2.2.stable - Ubuntu 22.04.4 LTS 22.04 - Wayland - Vulkan (Mobile) - integrated Intel(R) Xe Graphics (TGL GT2) () - 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz (8 Threads)
Issue description
Godot will no longer launch (play) a project after the desktop locks from inactivity or if you force the desktop to lock (Windows-L)
Steps to reproduce

load a project
play your project to confirm it runs
lock the desktop (Windows-L)
log back in
You will no longer be able to play your project

Workaround:  Just exit Godot and re-launch
Minimal reproduction project (MRP)
Create a 2D scene, call it main.tscn, add the following script:
extends Node2D

func _ready() -> void:
	print ("Hello, World!")

Sounds related to:

https://github.com/godotengine/godot/issues/87394

Thanks for the report! Consolidating in https://github.com/godotengine/godot/issues/87394.


Github User

The problem
I work with several github accounts and to me it is useful to display my github user in my prompt
Describe the solution you'd like
Show the github user before the current directory like this:

where lobosan is my github username
Describe alternatives you've considered
No response
Documentation and adoption
No response

When using oh-my-zsh I use the avit theme, and display my git name by adding $(git config user.name) to the _user_host function
You can have a look at the whole theme here https://github.com/lobosan/zsh-theme/blob/main/avit.zsh-theme#LL16C1-L27C2
So, it would be great if you could add it to the spaceship configuration. In my case I'm installing it through fig, so it would be nice to see it under the git section

You are confusing git with github. It's not the same. Git is a VCS. GitHub is a hosting (website) for Git repos.
Yes, it's possible to display the result of git config user.name, though it's probably not the info you need to know when typing every other command. You probably need that once in a while, don't you?

you right sorry for the confusion, but is it possible to show my git user when working on a project with git?

Sure, you can do it yourselft. Here's a guide how to create a custom section: https://spaceship-prompt.sh/advanced/creating-section/#Typical-section-breakdown
You can create your custom git_user section. Istead of foobar --version you can run git config user.name.

thanks @denysdovhan


Add ability to specify endpoint url

Adds capability to specify the S3 endpoint url to send requests to if using a non-standard AWS endpoint or an S3 service other than AWS (such as DigitalOcean Spaces or self-hosting an endpoint directly within your private VPC). Only applicable when using the S3 storage backend.
Type: trivial

Fixes #21

The single test that failed during CI is for an error unrelated to the code.
Please let me know if this PR is helpful, or if you would prefer I change something. I'm already using this modified version on my own project, and loving django-pgclone now that I'm able to use it with my DgitalOcean account!

@wesleykendall Just wanted to make sure you'd seen this and ask if you have any questions/concerns/recommendations.
Thanks for this awesome package!

@jacklinke thanks for this wonderful contribution! And for the nice docs/test changes
I was about to deploy a few other non-breaking changes in a separate PR and will plan on getting this change out with it in the next release.
I will handle fixing the failing test on your branch here and then deploy it. I will have to deploy this change tomorrow sometime. Will report back when I do.

Deployed in v2.5.0


vue3 - i18n component injections

Describe the bug
i18n component injections $d() and $n() are not working correctly with vue3.
Console:
[intlify] Not found 'short' key in 'en-US' locale messages.

To Reproduce
Vue3 branch: https://github.com/samuveth/snapshot/tree/samuveth/vue3
Steps to reproduce the behavior:

Go to any proposal
Scroll down to Information
See dates and snapshot missing
See error in console

Fixed:
https://github.com/balancer-labs/snapshot/pull/188/commits/a941339d9ac771c3cc49313d7867e5455a2ee13a

Fixed:
https://github.com/balancer-labs/snapshot/pull/188/commits/a941339d9ac771c3cc49313d7867e5455a2ee13a


override the bind-timeout to match ask timeout value

bindTimeout is used as the receive timeout for the tcp bind. This defaults to 1 sec, which seems to cause occasional test failures. This fix sets the bind timeout value to the ask timeout. Addresses #108

:shipit:


Weather error line 15

This is line 15:
print("%s, %i °%s" % (info, temp, unit_key))
I'm missing something here?
Thanks

Do you get an error from running it? I'm unsure as to what the question is here, sorry.

Yes I do have an error when I run it...
It show the path of the weather script then add the number 15.

Could you give us a little more information. What is the exact error? I'm assuming you are using the user contributed weather module, so can you give us the output of that script if you run it inside a terminal and not polybar.

I think this issue has been fixed on wiki.
I believe what caused the error is that if the returned HTTP request code is not OK,
then something else might be returned along the line.
See also: comparison of b74908 and the previous one.

@natebwangsut The code on the wiki has been changed but didn't yet fix the issue, it just spits out another message now if the HTTP status code is not 200. I have now changed it to output an error message if the request fails.
Closing this.

@patrick96 That just fixes the error if the code is not 200.
I guess it's safe to assume that the data would be in the expected format.
You can also do this
try:
    # HTTP CODE = OK
    if REQ.status_code == 200:
        CURRENT = REQ.json()["weather"][0]["description"].capitalize()
        TEMP = int(float(REQ.json()["main"]["temp"]))
        print("{}, {} °{}".format(CURRENT, TEMP, UNIT_KEY))
    else:
        print("Error: BAD HTTP STATUS CODE " + str(REQ.status_code))
except (ValueError, IOError):
    print("Error: Unable print the data")

Anyways, good job!

Yes we can do that too. Feel free to add this to the wiki page as well. Thanks!


updates to hotel and content apis

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

BingAds/hotel-service/reporting.md
:white_check_mark:Succeeded

BingAds/shopping-content/catalogs-resource.md
:white_check_mark:Succeeded

BingAds/shopping-content/get-started.md
:white_check_mark:Succeeded

BingAds/shopping-content/how-get-status-product-offers.md
:white_check_mark:Succeeded

BingAds/shopping-content/index.md
:white_check_mark:Succeeded

BingAds/shopping-content/manage-catalogs.md
:white_check_mark:Succeeded

BingAds/shopping-content/manage-products.md
:white_check_mark:Succeeded

BingAds/shopping-content/products-resource.md
:white_check_mark:Succeeded

BingAds/shopping-content/release-notes.md
:white_check_mark:Succeeded

BingAds/shopping-content/status-resource.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.