There should be a tool that analyze a subscription for move resources.

There has to be a tool that analyse the subscription for move operation we cannot go about analyzing 1000+ resources all together.

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

ID: 76c1c185-685f-27e0-e634-844b510b1834
Version Independent ID: 09375778-5354-ab44-c5c6-94c2aebe34bc
Content: Move Azure resources to new subscription or resource group
Content Source: articles/azure-resource-manager/resource-group-move-resources.md
Service: azure-resource-manager
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

@Anmolgan81 Thanks for the feedback! We are currently investigating and will update you shortly.

@Anmolgan81 - you can run the Validate move operation to assess whether the move will succeed. I am adding a section to this article about that operation.

But that will tell if resource will move or not, I need some tool that will analyse the csp subscription and look for dependence and judge the subscription according to those finding s do we have something like that?
Get Outlook for Androidhttps://aka.ms/ghei36

From: Tom FitzMacken<EMAIL_ADDRESS>Sent: Wednesday, September 5, 2018 3:36:17 AM
To: MicrosoftDocs/azure-docs
Cc: Anmol Ganju; Mention
Subject: Re: [MicrosoftDocs/azure-docs] There should be a tool that analyze a subscription for move resources. (#14416)
@Anmolgan81https://github.com/Anmolgan81 - you can run the Validate move operationhttps://docs.microsoft.com/en-us/rest/api/resources/resources/validatemoveresources to assess whether the move will succeed. I am adding a section to this article about that operation.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/14416#issuecomment-418533463, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AhHKpySBjWU1EFSyTeraqmFqrXfUjmBFks5uXvlZgaJpZM4WXXy-.
This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. IFI Techsolutions Pvt. Ltd. : www.ifi.tech

@Anmolgan81 while your comment is valid, I believe it is out of scope for this doc. sounds like you are looking for a tool to validate within the context of the subscription and not the resource itself . this is more of a product feedback and will be great if you can share this feedback directly with the engineering team using this link. thanks.

Sure you can close it, if I have to look for other options rather then so be it. Seems like Microsoft is no help for us in such kind of things. Never mind we will research on this.
Get Outlook for Androidhttps://aka.ms/ghei36

From: femsulu-MSFT<EMAIL_ADDRESS>Sent: Friday, September 7, 2018 12:22:55 AM
To: MicrosoftDocs/azure-docs
Cc: Anmol Ganju; Mention
Subject: Re: [MicrosoftDocs/azure-docs] There should be a tool that analyze a subscription for move resources. (#14416)
Closed #14416https://github.com/MicrosoftDocs/azure-docs/issues/14416.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/14416#event-1831180369, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AhHKp5UXuw6V82pqNxZ8SqoiTrIpA6Kfks5uYW8HgaJpZM4WXXy-.
This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. IFI Techsolutions Pvt. Ltd. : www.ifi.tech

@Anmolgan81 , we strive for positive interaction with your community members. Your comment above seems to suggest there may be an opportunity for us to improve our bi-lateral relationship. Happy to continue the conversation over email or phone. Please send mail to<EMAIL_ADDRESS>with your preferred contact method and we will be happy to continue the conversation. Looking forward to your response.


Resize handle out of reach when window larger than screen

If a window is opened and has a with or height larger than the size of the screen, the resize handle in the lower right cannot be reached so cannot be used to shrink the window. A possible solution may be to add resize handles to all sides of the window.
It can be worked around by maximizing the window and making the handle visible, so not a critical issue.

Ugh I knew you'd ask for this. Curse you and your demands for improvements that I should have added ages ago! I'll look into it. Unfortunately, implementing proper window resizing options will almost certainly be non-trivial, and possibly impossible. Either way this won't be coming anytime soon
Wait you're saying it's possible to create windows larger than the screen? That's the real bug here

Oh this is the devkit repo... Oops

lol


fix(react-query): non continuous suspense with useSuspenseQueries (#6298)

#6298

Nice and simple.
The tests run.

There are some warnings with the way the tests are written:
Warning: The current testing environment is not configured to support act(...)

maybe relates to:

https://github.com/testing-library/react-testing-library/issues/1061

not sure if we'd need to update testing-library or vitest or both?
Maybe you could also change the tests to be written more like the other tests that we have? We basically don't test hooks, but wrap them in components like so:
https://github.com/TanStack/query/blob/c014ea7a29db5bdd0770733e3c531c9050d7e4e9/packages/react-query/src/__tests__/suspense.test.tsx#L123-L148

Happy to comply.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files
Coverage Δ

packages/react-query/src/useQueries.ts
87.50% <100.00%> (ø)

... and 67 files with indirect coverage changes
:loudspeaker: Thoughts on this report? Let us know!.


Quasar v2 / Vue 3

not ready for review yet
To run this branch, delete all node_modules folders before installing with rm -rf node_modules **/node_modules
Known issues:

network selector doesn't prompt you to change networks (it did work the other day though, so seems I broke this recently and the fix should be easy) fixed in af1256f
language selector at the bottom doesn't populate by default fixed in 87c3539
faq page works, but throws errors in the console due to some i18n interpolation changes (we need to update strings to escape certain characters, see here) fixed in 7caac17
sending does not work, details below, which I'm assuming affects all sending of txs fixed in 971aa53
receiving always shows "nothing found" when it's done scanning, which I'm guessing is related to some web worker change we need fixed in 8520d1c (not web worker related)
some form validations are broken due to quasar changes. I think this is the fix but haven't investigated yet fixed in 9a36d86
ENS avatars don't work usually? Lots of requests and they 429 fixed in aef7e00
Warnings such as shared.esm-bundler.js?d074:54 [intlify] Detected HTML in 'Use the Setup page to configure your account' message. Recommend not using HTML messages to avoid XSS. — This is from our use of v-html, which we use for i18n stuff. So these warnings can be safely ignored since it's coming from a local, trusted source and not external input. TBD about turning off this warning or ignoring all/some of them somehow fixed in 2544383
Benchmark scan times with web workers on this branch vs production across networks. If scan times are the same or this branch is faster, we can consider leaving leave the implementation alone for now. Otherwise, we probably have fixes to make. Regardless, look into removing the worker-loader dependency used by worker.ts since it's no longer needed now that we're upgrading from webpack v4 to v5.

Benchmarked using my account on polygon with the live site vs. deploy preview for ba552dc. Live site was 24s to fetch announcements, 69s to scan. Deploy preview was 25s to fetch announcements, 67 to scan. This is close enough to conclude performance is unaffected (though, small sample size). Also updated to remove worker-loader in 93f8acc

When withdrawing you get the following error (with both ENS and regular address): runtime-core.esm-bundler.js?69b0:4178 Uncaught (in promise) TypeError: Cannot convert object to primitive value fixed in c7e9124

TODO before deploy:

[ ] @apbendi to look into doing a phased rollout via Netlify
[ ] @mds1 and @davidlaprade to ensure we're familiar with how to rollback deploys on Netlify

So far just found this page button delay bug
Screencast from 2023-01-16 15-53-22.webm

Just manually tested and found two small issues:

on arbitrum, this payment link didn't populate the amount
on polygon, with advanced mode enabled, on the receive page, I specified a from-block to begin scanning but it still scanned blocks before the specified number

Otherwise things looked great!

Just manually tested and found this issue:

on polygon, with advanced mode enabled, on the receive page, I specified a from-block to begin scanning but it still scanned blocks before the specified number


Added a test that checks that the roster is not changed after queryin…

This test will check that you do not change the roster by adding an empty grade when querying for a grade. I think this test will make the exercise better and that you can learn something from it (const methods).

That seems oddly implementation specific...but it is an edge case I guess. This also doesn't really enforce const methods, the real way would be to have a const grade_school::school object and call grade on that.
I think this would be better if you just added that check to the other test case grade_returns_an_empty_array_if_there_are_no_students_in_that_grade

It is maybe implementation specific, but many submissions change the roster because they implement it as return roster[grade];, which changes the roster map by inserting an empty vector into it.
I still propose to add it as a separate test because it states in its name it is testing this edge case.

Makes sense, I didn't realize how easy that issue would show up.
Thanks.


Fix classification and highlighting of filter lists

This pull-request fixes the syntax highlighting and language classification of this project's filter-list files, which are currently unrecognised by GitHub. It achieves this by using .gitattributes to specify the languages of files whose filenames and/or extensions aren't registered with GitHub Linguist.
Note that due to caching issues, merging this may not update the project's classification immediately; pushing a follow-up change will fix it.

Very interesting, thanks!


wrong download links in master

master branch readme links point to 3.5.b1, while the latest release is 3.5.b2

https://github.com/pybee/Python-Apple-support/pull/20

#20 has been merged. Thanks for the report!


inspecting elements not working properly

Issue Report Checklist

[x] Searched the issues page for similar reports
[x] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[x] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ ] Could not reproduce inside jupyter qtconsole (if console-related)
[x] Tried basic troubleshooting (if a bug/error)

[x] Restarted Spyder
[x] Reset preferences with spyder --reset
[ ] Reinstalled the latest version of Anaconda
[x] Tried the other applicable steps from the Troubleshooting Guide

[x] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
inspect element (e.g. crtl + i) is showing some very strange behaviour...
What steps reproduce the problem?

type something like the following in the editor (do NOT use tab - autocompletion!)

import numpy as np
np.cos

and then hit crtl + i to inspect np.cos from the editor
>>> No documentation available

is shown in the Help panel (and the Object-field on top of the help-panel is empty)
(also if the first line is executed)

do the same in the console
--> still no documentation for np.cos but now the Object-field on top of the help-panel shows cos   --> change cos  to  np.cos  in the Object-field   --> the documentation appears!

now type np.array instead of np.cos in the editor and hit crtl + i   --> the documentation appears!

do the same again in the console
--> now the Object-field on top of the help-panel shows array  and the documentation for the array-module appears...  --> change array  to  np.array  in the Object-field   --> the correct docstring of the numpy-array function appears!

What is the expected output? What do you see instead?
I'd expect to see the docstring of the inspected object :-)
Versions

Spyder version: 4.1.1
Python version: 3.6.7
Qt version: 5.9.6
PyQt version: 5.9.2
Operating System name/version: Windows 10

Dependencies

# Mandatory:
atomicwrites >=1.2.0           :  1.3.0 (OK)
chardet >=2.0.0                :  3.0.4 (OK)
cloudpickle >=0.5.0            :  1.2.2 (OK)
diff_match_patch >=20181111    :  20181111 (OK)
intervaltree                   :  None (OK)
IPython >=4.0                  :  7.13.0 (OK)
jedi =0.15.2                   :  0.15.2 (OK)
nbconvert >=4.0                :  5.6.1 (OK)
numpydoc >=0.6.0               :  0.9.2 (OK)
paramiko >=2.4.0               :  2.7.1 (OK)
parso =0.5.2                   :  0.5.2 (OK)
pexpect >=4.4.0                :  4.8.0 (OK)
pickleshare >=0.4              :  0.7.5 (OK)
psutil >=5.3                   :  5.7.0 (OK)
pygments >=2.0                 :  2.6.1 (OK)
pylint >=0.25                  :  2.4.4 (OK)
pyls >=0.31.9;<0.32.0          :  0.31.9 (OK)
qdarkstyle >=2.8               :  2.8 (OK)
qtawesome >=0.5.7              :  0.7.0 (OK)
qtconsole >=4.6.0              :  4.7.1 (OK)
qtpy >=1.5.0                   :  1.9.0 (OK)
rtree >=0.8.3                  :  0.9.3 (OK)
sphinx >=0.6.6                 :  2.4.0 (OK)
spyder_kernels >=1.9.0;<1.10.0 :  1.9.0 (OK)
watchdog                       :  None (OK)
zmq >=17                       :  18.1.1 (OK)

# Optional:
cython >=0.21                  :  None (OK)
matplotlib >=2.0.0             :  3.1.3 (OK)
numpy >=1.7                    :  1.17.2 (OK)
pandas >=0.13.1                :  0.25.1 (OK)
scipy >=0.17.0                 :  1.3.1 (OK)
sympy >=0.7.3                  :  1.4 (OK)

Duplicate of #11821

Thanks for taking the time to report it in such detail. We'll try to fix this in 4.1.2 or 4.1.3

OK perfect :-) Thanks for the response!


remove extra output from CXSMILES

An unintended consequence of the changes in #5264 was empty atom label sections being output to CXSMILES.
This clears that up.

@ptosco this should address the root cause of #5276


Sideframe hide duration

condition was not accepting falsy value such as 0,
now it does, but we changed the closing duration of the sideframe to be half of the opening duration

LGTM


Is there a version targeting .netframework4.8

Need to use this in a visual studio extension targeting .netframework4.8

is:open is:issue linked:pr updated:<2024-11-20


Strong Customer Authentication / PSD2 (critical if your startup is EU based)

Please fill and explain the choice of your control point
Name (mandatory)
Add Strong Customer Authentication
Chronology (mandatory)
Before development
Level or priority (mandatory)
high
Details (mandatory)
EU Payments Services Directive (PSD2) has been delayed by about 2 years for EU businesses (at least in the UK) but all FE and BE payment flows must be designed with SCA steps in mind, especially if you have complex payments flows and processes, otherwise face disruption to your revenues as soon as PSD2 is official.
Principle (optional)
Single Source Of Truth, Separation Of Concerns...

Hello! Thank you for this point, it is very interesting and deserves to be on the list, I can add it for you or I let you do a PR
Thank you so much for your contribution

Hey Florian, thanks for this project it is quite useful for many people. Feel free to add it yourself 👍

Thank you! I added your contribution


Do docker metadata checks only in docker compatibility mode

We don't want to be checking for existing /var/lib/docker/metadata/ dir
for cases where inputfile and outputfile has been specified.
Signed-off-by: Vivek Goyal<EMAIL_ADDRESS>

@rhatdan PTAL

Should we wait for @shishir-a412ed patch to just check if STORAGE_CONFIG="docker"?
That way user could specify /etc/sysconfig/docker-storage-setup with STORAGE_CONFIG="docker"

Fine LGTM

@rh-atomic-bot r+ 16334a1


ADX queries and ADT on a Visual Studio MSDN subscription with outlook account

Hi,
From my MVP membership I have an Visual Studio MSDN subscription with Azure credits. Now I have followed the manual (and my ADT is already running with other apps, ADT explorer is also working with this account, so security wise everything is ok) but when I try to run on sample ADX database the queries in this example receive the following error:
Request is invalid and cannot be processed: AADSTS50020: User account '{EmailHidden}' from identity provider 'live.com' does not exist in tenant 'Microsoft Services' and cannot access the application 'XXXXXXXXXXXX'(Azure Data Explorer) in that tenant. The account needs to be added as an external user in the tenant first. Sign out and sign in again with a different Azure Active Directory user account.
Trace ID: f9f56b8a-e645-4eed-8c84-e1c2e469ae00
Correlation ID: b1a5f978-d480-40a3-87e6-ad725c4baef6
Timestamp: 2021-06-24 07:40:42Z
I was following this manual: https://github.com/Azure-Samples/azure-digital-twins-getting-started/blob/main/adt-adx-queries/sample-queries.kusto
thanks,
Remco

@baanders do you know who might be able to help @rploeg on this?

@jjadta Hey Taylor, could you help us with this issue on ADX queries across tenants?

Sure thing. Will investigate.
On Wed, Jul 28, 2021 at 1:14 PM Bailey Anderson @.***>
wrote:

@jjadta https://github.com/jjadta Hey Taylor, could you help us with
this issue on ADX queries across tenants?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Azure-Samples/azure-digital-twins-getting-started/issues/10#issuecomment-888479554,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGTTG725J3IWHMEJ4DMTFBTT2A3JBANCNFSM47HKLEQA
.

--
Sent from Gmail Mobile

@rploeg, are you able to connect to the ADX Help cluster:
https://dataexplorer.azure.com/clusters/help/databases/Samples
If not, try logging out and logging back in.

@jjadta sorry for the delay I was on holiday. Yes, I am succesfull connected to the cluster:


Fix getComponent route link

@TomasHubelbauer perfect, thanks for catching. I removed that file without updating the link 😄 .
Thanks for your contribution.


Compatibility with plone.restapi 7.x

There's one incompatibility with plone.restapi 7.x block transformer.
The image transformer yields block URLs as resolveuids . This has to be handled in server.jsx

@tiberiuichim could you provide the steps to reproduce this problem?

@tisto
The obligatory
cd api
bin/develop co plone.restapi
bin/develop activate plone.restapi
bin/instance fg

Then in Volto, create a new page, save it, then edit it and add a new image block. Save the page. On the view page, you'll see that the images are linked as /resolveuid/uid links instead of the usual @@images/image links

Ah, but the code I've linked above is in the deserializer. It's ok if we store the Image link as a resolve uid. We just need to add the coresponding Serializer transformer for the Image block.


Fix memory leaks

there's bunch of leaks (after adding server-mode)

closing now since I can't see any, reopen if needed.


Add automatic chord tag detection

Some songs don't have chord tag annotations, but they might be possible to put in dynamically.
For example:
https://pg.zachmanson.com/tab/seals-crofts/summer-breeze-tabs-1017722

REGEX can do almost all of this
https://stackoverflow.com/questions/11229080/regex-for-matching-a-music-chord


Get all keys

If I want to store some keys and then get all of them how can I do that?

Unfortunately you can't do that now. You should create your own wrapper which handles multiple keys.


microsoft-surface: add surface-control

This adds surface-control, a command line tool to control various aspects of the Microsoft Surface line of devices from the command line.
This PR depends on https://github.com/NixOS/nixpkgs/pull/111690, and is a draft until it is merged.

Hey @Mic92, can we get this merged? Thanks! :)

Looks like we got a merge conflict now. Maybe afterwards?

Should be good now.


[Doc Feature][Update of conversationUpdate and installationUpdate event in bot channel][2333298]

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
88
17
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 730b633:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
85
23
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 9e48056:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
77
40
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 2e990f2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 5fedfd3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
93
9
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
93
9
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 586596f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 5f5fb24:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
93
9
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 033e44a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
93
9
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 7560bd1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 3e1099b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
93
9
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
93
9
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 27fed90:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
93
9
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 9cb2f9b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
95
6
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 3686604:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
95
6
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit d65aaa9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 5426315:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
95
6
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
93
9
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 1ad2566:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/bots/uninstallbot.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
93
9
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 9856c5d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/bots/uninstallbot.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
94
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 17fe121:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/bots/uninstallbot.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
94
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 7198526:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/bots/uninstallbot.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 148b707:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/bots/uninstallbot.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
94
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
94
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 2599cdb:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:warning:Warning
View
Details

msteams-platform/assets/images/bots/uninstallbot.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md

Line 33, Column 1: [Warning: file-not-found - See documentation] Invalid file link: '~/javascript/api/botbuilder-dialogs/componentdialog'.
Line 33, Column 1: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: ~/javascript/api/botbuilder-dialogs/componentdialog?view=botbuilder-ts-latest. Otherwise, remove the view parameter.

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
94
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 5645af3:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:warning:Warning
View
Details

msteams-platform/assets/images/bots/uninstallbot.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md

Line 33, Column 1: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/javascript/api/@microsoft/teamsfx/?view=msteams-client-js-latest' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 33, Column 1: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/javascript/api/@microsoft/teamsfx/?view=msteams-client-js-latest' will be broken in isolated environments. Replace with a relative link.
Line 33, Column 1: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/en-us/javascript/api/@microsoft/teamsfx/?view=msteams-client-js-latest. Otherwise, remove the view parameter.

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
94
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 474b269:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:bulb:Suggestion
View
Details

msteams-platform/assets/images/bots/uninstallbot.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md

Line 33, Column 1: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /javascript/api/@microsoft/teamsfx/?view=msteams-client-js-latest. Otherwise, remove the view parameter.

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 9ecfc89:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/bots/uninstallbot.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
94
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 32a6fba:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/bots/uninstallbot.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
93
9
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 6b077c3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/bots/uninstallbot.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
94
7
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit a69f9cb:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/bots/uninstallbot.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
94
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit e1f2a06:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/bots/uninstallbot.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 8274ce7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/bots/uninstallbot.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
94
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 5db70a5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/bots/uninstallbot.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
91
12
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
91
12
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit bc34297:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/bots/uninstallbot.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
91
12
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit f4f5755:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/bots/uninstallbot.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Hi @vule-msft,
Please note we have incorporated all the comments from this PR to #6026.

Closing this PR as all the comments are being taken care in #6026
We'd revisit the comments again when we pick this article for a revamp.


Remove test that touch network

This test fails on my machine but passes on CI. I don't know why, but tests that touch external network services are not nice.

LGTM

LGTM


Confusing for these codes of interface implementation and calling.Someone please help.

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?

go version go1.11 darwin/amd64

Does this issue reproduce with the latest release?

not testing

What operating system and processor architecture are you using (go env)?

not related

What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
Code 1:
package main

import "fmt"

type myintf interface {
	GotU()
}

type esc struct {
	 i int
}

//func GotU(t esc);
func (e esc)GotU() {
	e.i = 10
}

func TestFunc(it myintf) string {
	it.GotU()
	return  "kk"
}

func main() {

	var test esc
	test.i = 9

	TestFunc(test)

	fmt.Println(test.i)

}

Code 2:
package main

import "fmt"

type myintf interface {
	GotU()
}

type esc struct {
	 i int
}

func (e esc)GotU() {
	e.i = 10
}

func TestFunc(it myintf) string {
	it.GotU()
	return  "kk"
}

func main() {

	var test esc
	test.i = 9

	TestFunc(test)

	fmt.Println(test.i)

}

Code 3:
package main

import "fmt"

type myintf interface {
	GotU()
}

type esc struct {
	 i int
}

func (e *esc)GotU() {
	e.i = 10
}

func TestFunc(it myintf) string {
	it.GotU()
	return  "kk"
}

func main() {

	var test esc
	test.i = 9

	TestFunc(test)

	fmt.Println(test.i)

}

What did you expect to see?

nothing to expect

What did you see instead?
code 1 output: 9
code 2 output: 9
code 3 cannot be compiled due to a type mismatch
Since only func (e esc)GotU() implemented, why should both pieces of code work and deliver the same result?
It's kind of confusing for me to pass a pointer of struct to that function (TestFunc) to get the same answer.

Hi,
the Go project does not use its bug tracker for general discussion or asking questions about the language. The Github bug tracker is only used for tracking bugs and proposals going through the Proposal Process.
Please see the Questions wiki page; it has a list of good places for asking questions about the language. Thanks!
Closing, since this is not a bug.


Readme updates

this text was removed in https://github.com/uc-cdis/gen3-helm/commit/f59210c09a8c7cb0191dafe8c6bb828f379785ec


Trollstore UICache update breaks Jailbroken icons

Exactly as the title says, running uicache in trollstore breaks icons added by Dopamine. I'm not sure if this should be an issue opened here or on the Trollstore repo, so if this is in the wrong please please move the issue, thanks.

Yeah because there is no icon cache hook. I tried doing it and almost bootlooped my main device, so that's postponed indefinitely


Fixed code block fencing on winrm commands

Commands don't work as described in PowerShell (they work fine from a Command Prompt, but there's no code block fence for Command Prompt).

Docs Build status updates of commit 9c38a5d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/exchange-online/connect-to-exchange-online-powershell/mfa-connect-to-exchange-online-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/docs-conceptual/office-365-scc/connect-to-scc-powershell/mfa-connect-to-scc-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

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.

Docs Build status updates of commit a17c6b7:
:clock10: Full build: the average full build time is 11 min(s) 46 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit a17c6b7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/exchange-online/connect-to-exchange-online-powershell/mfa-connect-to-exchange-online-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/docs-conceptual/office-365-scc/connect-to-scc-powershell/mfa-connect-to-scc-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

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.


Mortgage redemption interest rate incorrect

Mortgage redemption should be charged at 10%.  On the manage screen it is charged at 20%

Corrected rate charged but wrong rate still shown on manage screen

Comparison in mortgage button click function still using wrong value


Address some Elixir 1.4 compilation warnings

This also bumps the Travis test target to Elixir 1.4 (from 1.3).

Thanks!


Outline File

Outlining our ideas for this guide.

What is the point of this?

@tiosgz It is meant to create a structure as the guide will probably be more than one page and will have multiple contents on each page and some parts may get reused.

Added some actual content to discuss.

I don’t see any reason to have everything in a single file. It also doesn’t make sense to me to have a ‘plan that must be satisfied’. However, both are my opinions and others may disagree, in which case I will eventually merge it.
Also you completely ingore CONTRIBUTING.md. It states that you shouldn’t contribute any content to this repo yet (although having one PR open probably wouldn’t hurt much if the situation didn’t evolve as it currently does)
https://github.com/tiosgz/modding-vivaldi/blob/878fddce565e9e4ab9c38cc2b35e3dfda5455505/CONTRIBUTING.md#L3-L5
and you break some of the rules even though you didn’t disagree with them in #1.
And something that wasn’t here at the time you opened the PR, but is here now: the purpose of the repository isn’t clear at this time, so the message at the beginning of CONTRIBUTING.md has a lot of importance.

Said all that, the best you can currently do is wait for #1.
I’d recommend you (but if you can manage to work with the resulting situation, I don’t require it from you) closing this PR, moving 79069a9 to a new branch and resetting your master to 878fddc – and (ideally after #1 is solved) creating a new PR from that other branch if it will still make sense.

Ok, I will close for now. What do we need to do to close #1?

What do we need to do to close #1?

Wait for the others to respond, and agree together on what the repo will be used for and on the contributing guidelines. Originally it was only the second purpose, but now it isn’t clear what the repo will become.


fix: bump spectral dependencies

PR summary
This PR bumps our spectral-related dependencies to their current most recent versions in order to pull in the fix for https://github.ibm.com/arf/planning-sdk-squad/issues/3531
PR Checklist
General checklist
Please make sure that your PR fulfills the following requirements:

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

Checklist for adding a new validation rule:

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

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

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

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


*: set health status to unknown when raftstore gets stuck

What is changed and how it works?

Issue Number: Close #12398
What's Changed:

The client uses health service to determine whether it should
still send requests to this TiKV or whether it should refresh
related region cache.

But if the raftstore alone becomes unavailable because of IO hang
or bugs, the health service still returns Serving status. This may
mislead the TiKV client and increase the recover time even if the
leader is already transferred to other TiKV instances.

This commit reuses the mechanism of slow score calculation
to detect whether the raftstore is normally working. So, the client
can refresh its region cache in time.

Check List
Tests

Integration test

Release note
Report bad health status if raftstore stops working.

I'm not sure whether this is a good approach. If there are better ways to do this, I'm happy to change it.

When will the slow score be recalculated? If the store stuck for 5 seconds and then recover, how can client notice the recovery in time?

When will the slow score be recalculated? If the store stuck for 5 seconds and then recover, how can client notice the recovery in time?

The slow score calculation is driven by PD worker. It sends StoreMsg::LatencyInspect at inspect_interval (500ms by default), and the slow score is updated every 30 ticks. So, it means, the health status will recover in 15 seconds.
As regards client-go, if it finds a store is not healthy, it will recheck its status every 1 second.

So in this case, use health status will cause regression, right?

So in this case, use health status will cause regression, right?

Personally, I think it an accetable regression. The update interval is 15 seconds, so the health status does not change until the raftstore keeps stuck for more than 15 seconds. And if there is such an extreme situation where it has been stuck for 15 seconds, it seems not a big problem to wait for another 15 seconds to get recovered.

How about if UNKNOWN is returned, schedule the requests at random fashion?

, if the liveness of a store is not reachable, it will not filter out the store. If request forwarding is enabled, it will try forwarding

This seems wrong to me. The new behavior may cause one slow stores slow down other nodes as forwarding is not cost free.

Now, I change the unknown status to become "strict enter, easy exit".
The status is changed to unknown only if no StoreMsg is not handled within 15 seconds (in this case, the leader should have dropped). And as long as one tick does not timeout, the status will change back to serving.

/merge

/run-cherry-picker


Errors using small TMS tileset

I've got a small TMS tileset that I've created a ol3 map with.  The tilemap resource file uses pixel coordinates,
<?xml version="1.0" encoding="utf-8"?>
<TileMap version="1.0.0" tilemapservice="http://tms.osgeo.org/1.0.0">
  <Title>Small TMS set</Title>
  <Abstract></Abstract>
  <SRS></SRS>
  <BoundingBox minx="-4949.00000000000000" miny="0.00000000000000" maxx="0.00000000000000" maxy="7000.00000000000000"/>
  <Origin x="-4949.00000000000000" y="0.00000000000000"/>
  <TileFormat width="256" height="256" mime-type="image/jpeg" extension="jpg"/>
  <TileSets profile="raster">
    <TileSet href="0" units-per-pixel="32.00000000000000" order="0"/>
    <TileSet href="1" units-per-pixel="16.00000000000000" order="1"/>
    <TileSet href="2" units-per-pixel="8.00000000000000" order="2"/>
    <TileSet href="3" units-per-pixel="4.00000000000000" order="3"/>
    <TileSet href="4" units-per-pixel="2.00000000000000" order="4"/>
    <TileSet href="5" units-per-pixel="1.00000000000000" order="5"/>
  </TileSets>
</TileMap>

The code I've used to create the ol3 map is
var res = 32;
var levels = 6;
var x = 7000;
var y = 4949;
var extent = [0,0,x,y];
var resolutions = [32, 16, 8, 4, 2, 1];

var mapLayer = new ol.layer.Tile({
    preload: Infinity,
    source: new ol.source.TileImage({
        crossOrigin: null,
        extent: extent,
        tileGrid: new ol.tilegrid.TileGrid({
            extent: extent,
            origin: [0,0],
            resolutions: resolutions
        }),
        tileUrlFunction: function(c) {
            if (c === null) return undefined;
            return  host + '/'+ c[0] +'/'+ c[1] +'/'+ c[2] +'.jpg';
        }
    })
});

var map = new ol.Map({
  layers: [
    mapLayer
  ],
  target: 'map2d',
  controls: ol.control.defaults({
    attributionOptions:
      collapsible: false
    })
  }),
    view :  new ol.View ({
        center:	[x/2, y/2],
        resolution: 16,
        resolutions: resolutions,
        extent: extent,
        constrainRotation: true
    })
});

This ol3 map works great.  I'm now trying to view the map using ol3-cesium with a SceneMode of COLUMBUS_VIEW with the following code
var ol3d = new olcs.OLCesium({map: map, target: 'map3d' });
var scene = ol3d.getCesiumScene();
scene.mode = Cesium.SceneMode.COLUMBUS_VIEW;
ol3d.setEnabled(true);

I had to change the scene3DOnly parameter to false in the build when olcs is initialising the scene to get the code to run.
The ol3-cesium view is not rendering correctly - there are loads of missing image tile errors, and the 3d scene is not showing.  What am I missing - is there some conversion that needs to happen, or some bounding rectangle that needs to be configured somewhere?  Is it possible to use small TMS tilesets in ol3-cesium with columbus view?
Any help gratefully appreciated - many thanks in advance

@dilignt, if you remove you columbus changes, does the tileset appears in 3D?

Thanks for your reply @gberaudo
No - I can't get any 3d view with those changes removed, it's just a blue screen.  Looking at the console it seems that none of the images can be found because the path is being formatted Incorrectly. eg
An error occurred in "kh": Failed to obtain image tile X: 1 Y: 0 Level: 1.
An error occurred in "kh": Failed to obtain image tile X: 1 Y: 1 Level: 1

on Line 424 of Cesium.js it is looking for the images in paths  host/1/1/-1.jpg and host/1/1/-2.jpg but the images are actually at host/1/1/0.jpg and host/1/1/1.jpg.  All of the tiles have the same error in Cesium, but they are fine in ol3.  Do you know what needs to change so that the images can be found correctly?

@dilignt, in 2D, OL3 is displaying your map while in 3D it is Cesium.
You are using a custom tilegrid in OL3 but there is no support for this in OL3-Cesium.
In a general case, I think it would require reprojection.
Tiles are requested by Cesium in src/core/olimageryprovider.js requestImage().
You may try to adapt the code there.
Alternatively, you may try using a standard tilegrid, and restrict the layer to your extent:
http://openlayers.org/en/master/apidoc/ol.source.XYZ.html
http://openlayers.org/en/master/apidoc/ol.layer.Layer.html
For this to work, you will need to generate you tileset on a global tilegrid.

Thanks - I tried changing requestImage() and the tiles are now loaded into cesium.  The problem now is that the 3d view is zoomed all the way in so that you can't see the images at all.  If I zoom out I start to see a tile magnified, but then the browser runs out of memory and crashes.  There are also other tile requests from Cesium for tiles that are outwith the bounding box of my tileset.  Is there a way to somehow constrain the zoom levels and extent of the 3d view in Cesium so that these problems don't occur?

There is a rectangle property on the imagery provider.

Yes, I noticed the Rectangle, but I can't see a way to convert my pixel dimensions into radians or degrees when my tileset is flat and not a globe - Cesium.Rectangle is instantiated with NSEW lat/lon points in radians.  Do you know if this is possible?
I have no way of generating a tileset on a global grid - it isn't a map it's a floorplan.


Implement LMNT full-duplex TTS generation

LMNT has an interesting approach to 'full-duplex' TTS:
async def main():
  async with Speech() as speech:
    connection = await speech.synthesize_streaming('lily')
    t1 = asyncio.create_task(reader_task(connection))
    t2 = asyncio.create_task(writer_task(connection))
    asyncio.gather([t1, t2])
    connection.close()

This doesn't really work with our FrameProcessor architecture, but it does actually work pretty well with the idea of a custom pipeline. I've started building that out in examples/foundational/02a-async-llm-say-one-thing.py.
I'm currently stuck because I think there's a bug in their implementation. After I get the first chunk of audio back, the websocket connection to LMNT seems to close. I've tried logging just about everywhere I can think of, and I can't find an explanation. I'm going to try and get in touch with the LMNT team to troubleshoot.
(I found out about LMNT through Andy Korman, who I met at our Voice + AI Summit.)

Hi Chad, this is awesome! I patched this and was able to initially repro the issue you describe, but after the issue manigesting on my first test room and connection, it is now working every time.
Do you have specific repro steps that you find surface the issue each time? This would make debugging easier.
A guess is that somehow the way the pipeline logic is set up for a new room, or an edge case on entering a room, is causing the in/out tasks to immediately conclude. Also open to getting on Slack or a VC to discuss more efficiently whenever works for you, FYI @sayitwithai

Closing in favor of #391


Fix & Update the Getting Started README

Describe the bug
Updating the README.md Getting Started to run the Nest ONDC repo, instead of the ecommerce repo
Expected behavior
I want the Getting Started Section in the main README to:

Indicate proper running specifications for the current repo,
Including all the additional dependencies required for setting up

Screenshots

Additional Context

Contributing as an SSOC participant
I'd like to be assigned on the specified issue.

@ShubhamTiwary914 duplicate issue #6


CLI: make self-encryption optional

plumb options through to engine
tested successfully via the command line
test in engine/
fix C/I tests for new encryption arg format

@akalin-keybase here is the new PR

lgtm after nit!


Remove background-importer when going to the table view after being on the map view

:+1:

https://github.com/CartoDB/cartodb/commit/cb455adb1a3abe6ece79d818abb0dd6525f01d45


Build Complexity, Musl Support? - Use of ort

I'd like to start off with a thank you for developing this library - it's awesome, and so convenient! :)
Cutting to the chase: your implementation of fastembed uses ort to handle the underlying ONNX inference (i.e. the actual "embed" in "fastembed"). While this allows it to be performant on supported platforms, my understanding is that it leads to a more complex build process and makes targeting *-musl (e.g. x86_64-unknown-linux-musl, my go-to for portable Linux programs) platforms a chore: to do so, you must build the onnxruntime library for musl yourself, and then configure the ort build to use your local onnxruntime with ORT_LIB_LOCATION=/path/to/musl/onnxruntime/build during compilation time.
Are there any plans to switch the ONNX inference library to something other than ort, like sonos/tract, or would such a change be better suited to a fork?

Hey @inadahime.
There are no plans as such.

I see.


origination: First get properties from provider before trying to persist

Summary
The incoming origination message might not have all properties set. This
finds the entity from the provider before trying to persist.
Change Type
Mark the type of change your PR introduces:

[ ] Bug fix (resolves an issue without affecting existing features)
[x] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[ ] Refactoring or test improvements (no bug fixes or new functionality)

Testing
Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.
Review Checklist:

[x] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

I think the logic is good. Let me fixup the tests as part of reviewing the PR.

This works. I updated the tests as part of the review.

coverage: 53.252% (-0.001%) from 53.253%
when pulling 30c6a8a785b9ad19e51b6ad709b1e19d9e6f5d2c on origination-get-properties
into ba646eb8df8c7e88c72321b0552d778ad6882cd4 on main.


Updating extension id regex

Updating the extension Id regex. This resource is a proxy resource and it's creation is completely controlled by us, service owners. Fixing this bug, so that only alphabets are allowed in the extensionId prefix and suffix.
Also this service is  yet in private preview with customers onboarded using feature flags.
Requesting reviewer to by accept this PR despite breaking change since this has zero customer impact.
Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[x] Other, please clarify: Fixing bug in extension id pattern

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[x] No, no need to refresh for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[x] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
[ ] Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
Adding a new service

[x] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

@anuchandy looking forward to your review.

@JeffreyRichter - As per my discussion with @priyankajayaswal1, this is is a pattern bug fix in the swagger. The service already validates that the input id is in the format expressed by the regex. Could you take a look and provide the breaking-change approval if there are no concerns


Update readme with details about flags

Specifically character flags (which got updated), plus new structure of effect flags.

completed in v10.


stafox/huawei-iap library can be used for PHP

Hi.
I've developed the small library (stafox/huawei-iap)to add support of huawei iap to php backend applications.
Maybe it will be helpful to somebody.

The official php demo is also available.


LittleDocBug on http://phantomjs.org/page-automation.html

In the doc "Dom Manipulation" of the http://phantomjs.org/page-automation.html, the line
 return document.getElementById('myagent').textContent;

should be, I think,
return document.getElementById('qua').textContent;

because "myagent" return "null is not an object".

Oh yeah, it looks like that web page has changed, it also now redirects from http://www.httpuseragent.org to https://useragent.openadmintools.com.
Same for me, element with ID myagent is no longer there and qua is there instead.


fix reshape size check from symbolic shape to int shape

Added .val for all sint Nodes and use that to get int_size. Also reshape_and_permute shares the same code path, but the Variables are no longer bound so passed the check in that case
fix #4501 too as we now support reshape into MulNode and SumNode provided that the int_size are the same

hmm in jitted function, if the inputs are symbolized before passing into the function, the function output shape can use the old variable value.

Stale, closing


Status of this project

The last commit was pushed in 2018. What is exactly the status of this project? The native Scintilla is not that far off from version 5 while our wrapper release wraps a 3.7.2.
There are plenty of downstream projects that use and rely on the ScintillaNET library, and it would be greatly appreciated to at least communicate and let us know the future of this project. It is completely understandable that life can make one too busy for open source projects like ScintillaNET, but some form of communication is never a bad thing.
Thanks.

The good thing about open source is that you can continue to develop it. Just fork and go. I refactored the source code and published NuGet packages for .NET Framework and .NET Core WinForms applications with an addition to a new event CallTipClick which registers the up / down arrow clicks on call tips. The pull request #486 is still open for merge which also includes the other PRs merged into it. I'll be needing help though - too many projects going on...


[WAYANG-38] Licences validation

Apache Wayang was having some licenses issues, this got deleted following the step below:

Add a License Checker (org.codehaus.mojo:license-maven-plugin:2.0.0)
The tool found the org.json have a not compatible license with Apache License
The org.json was remove after a creation of a wrapper, the wrapper it not fully complete but it covering the requirements of the existing code

Looks good!


testInterface linking error in 2.12 community build

in recent Scala 2.12 community build runs such as this one, scala-js has consistently been failing with:
[scala-js] Running "test" in: testInterface
[scala-js] [info] Fast optimizing /home/jenkins/workspace/scala-2.12.x-integrate-community-build/target-0.9.16/project-builds/scala-js-88da8c6fe8815e1303df7c5b6f01d6cd0572be74/test-interface/target/scala-2.12/scalajs-test-interface-test-fastopt.js
[scala-js] [error] Referring to non-existent class org.scalajs.testing.bridge.Bridge$
[scala-js] [error]   called from core module module initializers
[scala-js] [error] Referring to non-existent class org.scalajs.testing.bridge.Bridge$
[scala-js] [error]   called from core module module initializers
[scala-js] [error] Cannot access module for non-module org.scalajs.testing.bridge.Bridge$
[scala-js] [error]   called from core module module initializers
[scala-js] org.scalajs.linker.LinkingException: There were linking errors

any clue what this is about?

Yes, it's https://github.com/scala/community-builds/issues/465 / #2752 coming back to haunt us, but this time with the testInterface project rather than library.
I'll fix it.
But honestly we're working around the fact that dbuild insists on running x/test for every x that y transitively depends on, when all we're asking is that it run y/test...

It sounds like I could work around it with:
      // Seb says it isn't appropriate to run tests in this subproject;
      // see https://github.com/scala-js/scala-js/issues/3680
      "set executeTests in testInterface in Test := Tests.Output(TestResult.Passed, Map(), Iterable())"

I'll try it

oh no wait duh, it's a problem compiling, not running, that won't help

maybe I can just  "set test in testInterface in Test := {}"

yeah that does it, scala/community-builds@82e1d1232d459a86a25fa224e081360c4d2f849f

maybe I can just set test in testInterface in Test := {}

Yes, that would work, since the fix in Scala.js is basically to do just that. See
https://github.com/scala-js/scala-js/blob/118a97b29f8e81c8fd43e3b98ab1c73f6e29fa0f/project/Build.scala#L1026-L1028

yeah that does it, scala/community-builds@82e1d12

Thanks :)

LOL, https://github.com/scala/community-builds/commit/e071600dca13c1ff6e256e8767ecfb02a8f0c78f https://github.com/scala/community-builds/commit/311fa06252531425d1460a77832f7f87c6c5e28e


HDX balances claims

depends on #16

1 HDX = 10 BSX
batch vested to the HDX wallets (terms TBD)

Do we do this to the same (hydradx) address or new one?
Do we copy the accounts that didn't claim from xHDX yet?

Do we do this to the same (hydradx) address or new one?
same HDX address

Do we copy the accounts that didn't claim from xHDX yet?
no


v3: in select boxes the accent colour is used for the unselected items

Select boxes have their items coloured in the accent colour. The selected item is coloured in a more dimmed, neutral colour:

In the image above, I would expect "OFF" to be the selected item, but it is actually "COOL".
What is the selected item is more obvious when there are more than two items. It remains an unconventional design choice though, especially since for toggle sliders the accent colour indicates "on" and the dimmed colour indicates "off". I would recommend giving "on" / "selected" similar colours, and the same for "off" / "unselected".

hi, I think we updated the climate component. how does it currently look?


Track oci2cw tool ideas on how to build images

Building images requires a separate step that generates the keys in a secure way, and then sends them to the KBS.
The oci2cw tool does this for confidential workloads.
Discussing with @slp earlier, he mentioned that he wanted to do a Rust version. During a later discussion at KVM Forum, he mentioned that there was a possibility this would be integrated into buildah instead.
See also build process overview

(source)

@wainersm This is the issue for future reference.

I think we are on a right way for image encryption now? As showed in https://github.com/confidential-containers/kbs/blob/main/docs/cluster.md


protobuf3_21: 3.21.2 -> 21.5, update versioning scheme

Description of changes
Upstream dropped the previous "3" major version, to better help with handling changes to underlying ecosystems. https://developers.google.com/protocol-buffers/docs/news/2022-05-06
cc @infinisil if this is the correct way to do this version transition
Things done

Built on platform(s)

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

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

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

IMO we should also try to reduce the number of protobuf variants we have.

I think the maintenance is pretty minimal. And protobuf is pretty pedantic about which versions you use, so I think we should keep around the non-EOL versions.

New version, v21.6, is available:
https://github.com/protocolbuffers/protobuf/releases/tag/v21.6

When I try to cross-compile, I get this:
rick@nixos-asus:~/nixpkgs$ nix build .#pkgsCross.aarch64-multiplatform.protobuf_21
error: attribute 'protobuf21_5' missing

       at /nix/store/pycf5k246bmfz21fnl96a2m4yxdl84wy-source/pkgs/development/libraries/protobuf/generic-v3-cmake.nix:65:7:

           64|       # re-use the executable generated as part of the build
           65|       buildPackages."protobuf${protobufVersion}"
             |       ^
           66|     ];
(use '--show-trace' to show detailed location information)

This could fix several errors in https://github.com/NixOS/nixpkgs/pull/191339 because it picks up https://github.com/protocolbuffers/protobuf/pull/10271.
From my reading of the ticket, it seems that protobufc is built in debug mode but protobuf isn't? I don't know enough about building C++ programs to know for sure.

If I add the alias protobuf21_5, it works.

Yea.... cross compilation + overriding :(

FYI, it's these lines that cause this to happen: https://github.com/NixOS/nixpkgs/blob/e2420ef939f2a5b83db62f837ca299ece557f60c/pkgs/development/libraries/protobuf/generic-v3-cmake.nix#L59-L65
Maybe still using the minor version in the name would be good? Otherwise those lines should probably be changed to support both.

Seeing as 3.21/21.x are the only versions of protobuf using the cmake builder, I can just adopt the newer convention.

Note: 3.21 got security update in the meantime.

v21.7 is released.
https://github.com/protocolbuffers/protobuf/releases/tag/v21.7

Can I help with anything to move this forward?
Also, would it make sense to rename/add a new package called protoc? Given that the new versioning scheme is for protoc only and language runtimes will continue using semver.

After 6 months, I stopped caring, let's get this in.

@ofborg eval

much of this was applied