Cortana bots try to use suggested actions

Version
4.1.5
Describe the bug
It is known that Cortana does not support suggested actions, but there is logic in ChoiceFactory.ForChannel that directs a Cortana bot to use suggested actions when a ChoicePrompt is set to the default list style of ListStyle.Auto. I do not know the reasoning behind this. In the line if (!longTitles && (supportsSuggestedActions || (!hasMessageFeed && supportsCardActions))), Cortana satisfies that condition because even though it doesn't support suggested actions it does support card actions and also doesn't have a message feed. At least one customer has run into issues because of this.
To Reproduce
Steps to reproduce the behavior:

Create a bot with a ChoicePrompt without specifying a list style so that it defaults to "auto"
Connect the bot to Cortana
Run the bot and send messages to it
Observe that the choices are not displayed in any form (text, buttons, or suggested actions)

Expected behavior
The desired behavior would be for the choices to be displayed as buttons, but failing that they should at least be displayed as text.
Screenshots
A screenshot of the behavior can be found here.
Additional context
I am happy to fix this myself if that's acceptable.
[bug]

@v-kydela can we add one more bit, or could you try to direct me to the right team:
The suggested workaround only works on the Windows 10 Cortana app. I have just recently updated Cortana for android v3.0, and it shows 2 buttons, once I select one, it returns an error message, but my bot code does not seem to be hit anymore.
I think it used work with previous version of Cortana for Android.

@ladeak - It's hard to say if that's a problem with Cortana or a problem with the bot. Try to gather as much information you can about the behavior so that you can post an issue with adequate steps for how to reproduce it. If you're building the bot with the .NET V4 SDK, this repo would be a fine place to post the issue

@ladeak - I'm sorry if I was unclear, but I meant that this repo would be a fine place to post your issue as its own issue. I didn't mean that this thread would be a fine place to post your issue. Please post an issue if you'd like your problem to be looked into.


Will there be support for other platforms (mainly Mac / Linux)?

Is planned and the backend already works with mac/linux. I'll just have to get a mac/linux system to fix some window-specific stuff.


oso-ops-base: Support RHEL7 only

Discontinue generating unused CentOS7 images.
Make the generated RHEL7 code canonical and drop the templates.
This allows the oso-rhel7-ops-base BuildConfig to point to a repo directory without keeping generated code under source control.

:+1: @blrm #4118


Indexing with sycl::id

I found this example in an Intel tutorial:
#include <CL/sycl.hpp>

constexpr int N=16;

using namespace cl;

int main() {
  sycl::queue q;
  int *data = sycl::malloc_shared<int>(N, q);
  q.parallel_for(sycl::range<1>(N), [=](sycl::id<1> i) {
      // data[i] = i;  // ?? Intel extension ??
      data[i[0]] = i[0];
    }).wait();
  for (int i=0; i<N; i++)
    std::cout << data[i] << "\n";
  free(data, q);
  return 0;
}

Note the commented-out line. The data[i]=i form works on Intel's devcloud. Is this an intel extension?

Yes, they have added in implicit conversion operator for sycl::id<1> to size_t so that indexing raw pointers with sycl::id<1> works. It's not yet in any released SYCL specification, but might still find its way into other implementations as it makes a lot of sense in the context of USM.


[Feature Enhancement] Webpage Thumbnail

Hello..
Firstly, THANK YOU for an awesome extension.  This has been one of the main issues I haven't given up Opera; the Opera Speed Dial is built-in and is great.  Yours handles this functionality greatly!
My feature request would be a thumbnail creation of the website instead of the title.  Prior versions of Opera had this functionality and it was removed in the around the v5x update chain.  This allows you to "see" the web page without having to visit the page.  Great for when you're searching for a certain website within a folder of multiple pages, and know what the page looks like better than its name.
Thank you again.

Thank you for the note! I'm glad you're enjoying using Toolbar Dial. It was because of my interest in changing from Opera to Firefox that I created it!
For the thumbnail request, I know that Vivaldi still uses thumbnails, and I have been considering  adding this feature. I'll put it on my list to implement in a future update!

I spent some time looking into this, and there doesn't seem to be a user-friendly and privacy-friendly way to do it.
Firefox and Chrome do offer a way to capture a thumbnail of a webpage, but it actually requires opening a tab to create a thumbnail. So for every bookmark a tab would have to be opened to capture a URL.
Also, that would require use of the "<all_urls>" permission by Toolbar Dial, and that is the most powerful permission an extension can request. It gives an extension the ability to execute a script within any tab -- even one in the background. I don't want to require any permissions other than bookmarks and storage. When I created Toolbar Dial, my mantra from the beginning was to be privacy conscious and never ask for more permissions than necessary to load bookmarks and store settings.
There is another way it could be done, using a third-party API to generate the thumbnail and send it back to the browser, but that would require sharing the URL with the third-party API, and I don't feel comfortable doing that. That would then expose every bookmark you have to a third party service, and that doesn't seem like a very friendly thing for an extension to do.
Considering that, I'm going to close this request. I'll revisit in the future if I come across any technique that would allow this to be done in a privacy-friendly manner.


Binding API

I have played around with the current binding API, and it has a few pros and cons. There's a couple of possible directions, that I'd like to outline.
GraphQL server 'as a database'
The Graphcool GraphQL server closely mimics a database. This might validate an API that's closer to traditional ORMbinding libraries. These libraries are more centered around a Type, instead of a query/mutation, and would look something like this (inspired by libraries like Mongoose, Linq, etc.):
schema.Post.find({ name: 'abc' }) //or: schema.Post.findOne(...) and schema.Post.findMany(...)
new schema.Post({ name: 'abc' })

This type of API can only be achieved when the mapping between types and their corresponding query and mutation root fields is known. For Graphcool, they are, for generic GraphQL servers, they are not. This could be implemented using directives in the schema, for example:
type Query {
   myPosts: [Post] @findMany
}

Generic GraphQL server
As seen above, the 'database like approach' required either convention or configuration to work, and would only work well for GraphQL schemas that actually mimic a traditional database design. The alternative is to stick to the root query and mutation fields, like the current implementation:
schema.allPosts(...) // or: schema.topPosts(...) or schema.posts(...)

This stays closest to the original schema you are binding to. I think this is a better fit for GraphQL binding.
Filtering and other parameters
Queries can have parameters. Most commonly used for filtering, ordering, aggregating etc. Currently, they are passed as arguments to the binding method. It might be worth investigating if field parameters can also become part of the API itself. So:
schema.posts({filter: { name: { starts_with: 'Hello' } } })

Could also be written as:
schema.posts.filter({ name: { starts_with: 'Hello' } })

Or even (when also generating types for GraphQL types):
schema.posts.filter(Post.name.startsWith('Hello'))

These calls could be chained too:
schema.posts.filter(...).orderBy(...)

This needs a lot more investigating to see if it can easily be determined which functions to generate. Maybe based on a check for scalar fields, to prevent generating fields for something like:
schema.post({ id: '123'})
schema.post.id('123')

Chaining
There was already an example of chaining in the previous chapter, where filter() and orderBy() were combined. But chaining also offers a possibility to implement functionality that is not offered by the server. For example, if the server doesn't offer aggregation options, this might be implemented as a function in the binding library:
schema.posts().aggregate('{ age }').avg('{ weight }').groupBy('{ age }')

This would be equivalent to SELECT age, avg(weight) FROM posts GROUP BY age.
I believe the possibility to create your own binding, and add functionality like this in an easy way at the binding level, instead of the consuming resolver, would make it a lot easier to implement certain features.

Thanks a lot for your great ideas @kbrandwijk! I think this is definitely something we should explore going forward in order to improve the binding API.
Please also note the recent API changes introduced with Graphcool 1.0 (see https://github.com/graphcool/framework/issues/1340).

I'd be interested to know if orderBy and skip are on the roadmap for prisma-binding.
Any thoughts @schickling ?

Hey 👋, I believe this issue is no longer in sync with the current prisma-binding.
Feel free to reopen the issue if you believe we should further discuss it. 🙂


Automated cherry pick of #4609: fix: 避免仅删除value时,行为演变为删除标签

Cherry pick of #4609 on release/2.11.
#4609: fix: 避免仅删除value时,行为演变为删除标签

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.11@34ca16d). Click here to learn what that means.
The diff coverage is n/a.

@@              Coverage Diff               @@
##             release/2.11   #4614   +/-   ##
==============================================
  Coverage                ?    7.1%
==============================================
  Files                   ?     480
  Lines                   ?   78151
  Branches                ?       0
==============================================
  Hits                    ?    5552
  Misses                  ?   72132
  Partials                ?     467

Flag
Coverage Δ

#aFlag
7.1% <ø> (?)

Impacted Files
Coverage Δ

pkg/cloudcommon/db/metadata.go
11.71% <ø> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 34ca16d...0eea746. Read the comment docs.


use dict instead of if/else logic

Haven't looked at it in a while, but make sure this is in line with #1452.

This does appear to be made obsolete by https://github.com/pallets/flask/pull/1452, thanks @davidism. However that PR has been open for a year and a half, so this simple change might make sense while we're waiting for that to be approved. I'll leave that decision to the discretion of those with merge rights though.

@davidism at first glance #1452 looks like a over-generalization with quite a performance penalty :/


Move the queue component to the left and implement a proper file browser on the left

How would the file browser work - when you open a folder, would it make all of the files in the explorer relative to that folder? If so, when you add a standalone track, possibly from another folder, what would happen?

How would the file browser work - when you open a folder, would it make all of the files in the explorer relative to that folder? If so, when you add a standalone track, possibly from another folder, what would happen?

Instead of loading all the files from inside the subfolders directly, opening a folder with multiple folders inside it should list the actual tree instead of just the audio files.

yes like vscode's explorer but it would use the pixel art text and folder icons (unicode characters) from the Cozette Font we are using


Base challenge migration to wagmi V1, Viem and daisyUI v3

Description :
Tried bringing base-challenge-template up with SE-2 latest changes, mainly wanted to bring wagmi v1, viem and DaisyUI3 as mentioned in #72.
It was mostly mindfully copy-pasting things from SE-2 main repo and fixing some bugs which arise during it 🙌.
Would love it if everyone could test it nicely and report bugs if found 🙌
Once we merge this, we could do eg : git merge --squash base-challenge-template to merge it into other branches slowly

works great!

Been playing with it and it's working great! 🙌
Only thing I found it's when using useScaffoldEventHistory, fromBlock changed from number to bigint, so we have to remember to change Challenge README when migrating, in the Challenges showing event history we give hints in Readme about fromBlock.

fromBlock changed from number to bigint, so we have to remember to change Challenge README when migrating, in the Challenges showing event history we give hints in Readme about fromBlock.

Yup🙌, we can also add a small comment about fromBlock when using useScaffoldEventHistory in code like how we have in docs https://docs.scaffoldeth.io/hooks/useScaffoldEventHistory
Merging this 🙌


ExNihilio Compatibility

Add a way to define Sieve interactions.
Fields needed:

sourceBlock - Block to run through sieve. Will take a BlockStack. Defaults to Blocks.dirt
sieveChance - Chance of the Seed dropping. Defaults to 0.

JSON would look similar to:
{
    "seeds": [
        {
            "name": "Iron",
            "tier": 2,
            "amount": 4,
            "input": "ingotIron",
            "output": "ingotIron#8",
            "color": "#D0CBC7",
            "compat": {
                "exnihilio": {
                    "sourceBlock": {
                        "name": "minecraft:sand",
                        "meta": 0
                    },
                    "sieveChance": 8
                }
            }
        }
    ]
}

le progress has been le made

\o/
Thank you good sir.

As of build 11


[Doc Improvement][Revamp Teams ToolKit]

Docs Build status updates of commit 461b245:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/toolkit/deploy.md
:warning:Warning
View
Details

msteams-platform/toolkit/add-capability.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/provision.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/publish.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/deploy.md

Line 11, Column 1: [Warning: merge-conflict] File contains merge conflict markers.
Line 12, Column 1: [Warning: h1-not-first - See documentation] Markdown content is not allowed before H1 'Deploy to the cloud'.
Line 14, Column 1: [Warning: multiple-h1s - See documentation] Multiple H1s(H1 'Deploy Teams app to the cloud') are not allowed. You can only have one top-level heading.

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/toolkit/add-capability.md
95
4
link
:white_check_mark:

msteams-platform/toolkit/deploy.md
96
1
link
:white_check_mark:

msteams-platform/toolkit/provision.md
93
55
link
:white_check_mark:

msteams-platform/toolkit/publish.md
90
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 b0e538b:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/toolkit/deploy.md
:warning:Warning
View
Details

msteams-platform/toolkit/provision.md
:warning:Warning
View
Details

msteams-platform/toolkit/add-capability.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/publish.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/deploy.md

Line 11, Column 1: [Warning: merge-conflict] File contains merge conflict markers.
Line 12, Column 1: [Warning: h1-not-first - See documentation] Markdown content is not allowed before H1 'Deploy to the cloud'.
Line 14, Column 1: [Warning: multiple-h1s - See documentation] Multiple H1s(H1 'Deploy Teams app to the cloud') are not allowed. You can only have one top-level heading.

msteams-platform/toolkit/provision.md

Line 99, Column 408: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/azure-resource-manager/bicep.md' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 99, Column 408: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/azure/azure-resource-manager/bicep.md' will be broken in isolated environments. Replace with a relative link.

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

Docs Build status updates of commit 9cc9025:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/toolkit/deploy.md
:warning:Warning
View
Details

msteams-platform/toolkit/provision.md
:warning:Warning
View
Details

msteams-platform/toolkit/add-capability.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/publish.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/deploy.md

Line 11, Column 1: [Warning: merge-conflict] File contains merge conflict markers.
Line 12, Column 1: [Warning: h1-not-first - See documentation] Markdown content is not allowed before H1 'Deploy to the cloud'.
Line 14, Column 1: [Warning: multiple-h1s - See documentation] Multiple H1s(H1 'Deploy Teams app to the cloud') are not allowed. You can only have one top-level heading.

msteams-platform/toolkit/provision.md

Line 99, Column 408: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/azure-resource-manager/bicep.md' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 99, Column 408: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/azure/azure-resource-manager/bicep.md' will be broken in isolated environments. Replace with a relative link.

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

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/toolkit/add-capability.md
95
4
link
:white_check_mark:

msteams-platform/toolkit/deploy.md
96
1
link
:white_check_mark:

msteams-platform/toolkit/provision.md
93
55
link
:white_check_mark:

msteams-platform/toolkit/publish.md
90
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 f2915f4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/toolkit/add-capability.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/deploy.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/provision.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/publish.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/toolkit/add-capability.md
95
4
link
:white_check_mark:

msteams-platform/toolkit/deploy.md
96
1
link
:white_check_mark:

msteams-platform/toolkit/provision.md
93
55
link
:white_check_mark:

msteams-platform/toolkit/publish.md
90
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/toolkit/add-capability.md
95
4
link
:white_check_mark:

msteams-platform/toolkit/deploy.md
96
1
link
:white_check_mark:

msteams-platform/toolkit/provision.md
93
55
link
:white_check_mark:

msteams-platform/toolkit/publish.md
90
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 ce5ca84:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/toolkit/add-capability.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/deploy.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/provision.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/publish.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/toolkit/add-capability.md
95
4
link
:white_check_mark:

msteams-platform/toolkit/create-new-project.md
96
2
link
:white_check_mark:

msteams-platform/toolkit/debug-background-process.md
82
24
link
:white_check_mark:

msteams-platform/toolkit/debug-local.md
93
12
link
:white_check_mark:

msteams-platform/toolkit/deploy.md
96
1
link
:white_check_mark:

msteams-platform/toolkit/provision.md
93
55
link
:white_check_mark:

msteams-platform/toolkit/publish.md
90
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 84ddbda:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/toolkit/TeamsFx-multi-env.md
:warning:Warning
View
Details

msteams-platform/toolkit/add-capability.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/create-new-project.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-background-process.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-local.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/deploy.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/provision.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/publish.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-multi-env.md

Line 111, Column 159: [Warning: bookmark-not-found] Cannot find bookmark '#provision-using-teams-toolkit' in 'toolkit/provision.md'.
Line 164, Column 164: [Warning: bookmark-not-found] Cannot find bookmark '#provision-using-teams-toolkit' in 'toolkit/provision.md'.
Line 190, Column 152: [Warning: bookmark-not-found] Cannot find bookmark '#provision-using-teams-toolkit' in 'toolkit/provision.md'.

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

Docs Build status updates of commit 13b13f7:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/toolkit/TeamsFx-multi-env.md
:warning:Warning
View
Details

msteams-platform/toolkit/add-capability.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/create-new-project.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-background-process.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-local.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/deploy.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/provision.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/publish.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-multi-env.md

Line 111, Column 159: [Warning: bookmark-not-found] Cannot find bookmark '#provision-using-teams-toolkit' in 'toolkit/provision.md'.
Line 164, Column 164: [Warning: bookmark-not-found] Cannot find bookmark '#provision-using-teams-toolkit' in 'toolkit/provision.md'.
Line 190, Column 152: [Warning: bookmark-not-found] Cannot find bookmark '#provision-using-teams-toolkit' in 'toolkit/provision.md'.

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/toolkit/add-capability.md
95
4
link
:white_check_mark:

msteams-platform/toolkit/create-new-project.md
96
2
link
:white_check_mark:

msteams-platform/toolkit/debug-background-process.md
82
24
link
:white_check_mark:

msteams-platform/toolkit/debug-local.md
93
12
link
:white_check_mark:

msteams-platform/toolkit/deploy.md
96
1
link
:white_check_mark:

msteams-platform/toolkit/provision.md
93
55
link
:white_check_mark:

msteams-platform/toolkit/publish.md
90
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 0071672:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/toolkit/TeamsFx-multi-env.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/add-capability.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/create-new-project.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-background-process.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-local.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/deploy.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/provision.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/publish.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 8e2fd05:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/toolkit/TeamsFx-multi-env.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/add-capability.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/create-new-project.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-background-process.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-local.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/deploy.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/provision.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/publish.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/toolkit/TeamsFx-multi-env.md
91
29
link
:white_check_mark:

msteams-platform/toolkit/add-capability.md
95
4
link
:white_check_mark:

msteams-platform/toolkit/create-new-project.md
96
2
link
:white_check_mark:

msteams-platform/toolkit/debug-background-process.md
82
24
link
:white_check_mark:

msteams-platform/toolkit/debug-local.md
93
12
link
:white_check_mark:

msteams-platform/toolkit/deploy.md
96
1
link
:white_check_mark:

msteams-platform/toolkit/provision.md
93
55
link
:white_check_mark:

msteams-platform/toolkit/publish.md
90
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 788e71e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/toolkit/TeamsFx-multi-env.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/add-capability.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/create-new-project.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-background-process.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-local.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/deploy.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/provision.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/publish.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


STORM-1850: State Checkpointing Documentation update

update the documentation following this discussion
https://mail-archives.apache.org/mod_mbox/storm-user/201605.mbox/<F9D9F747-8431-4A26-9028-BD74C09BCA84%40hortonworks.com>

+1

+1 once some minor grammar suggestions have been addressed.

Thanks @omallassi this is merged to master and 1.x-branch.

@arunmahadevan Seems like it would be better to apply this to 1.0.x as well. What do you think?

@HeartSaVioR thanks for noticing. The changes are now merged to master, 1.x-branch and 1.0.x-branch.
@omallassi thanks for the patch. You may close this PR.


Need Cloud groups for DevOps and CELR Developer team members

We need following Cloud groups for DevOps and CELR Developer team members has to be created for the DEX Project.

DevOps Groups: We need the following below Four groups for the DevOps team and please add the below users as an owner:
Owner's list:
1. Mitchell, Ken
2. Ning, Yu (Boris)
3. McNabb, Leslyn
4. Pacha, Mounika
Groups list:
1. gp-u-coe-devops-dev
2. gp-u-coe-devops-tst
3. gp-u-coe-devops-stg
4. gp-u-coe-devops-prd

Developer's groups:  We need the following below Four groups for the Developers team and please add the below users as an owner:
   Owner's list:
           1. Ning, Yu (Boris)
           2. McNabb, Leslyn
          3. Pacha, Mounika
  Groups list:
       1. gp-u-dex-celr-developer-dev
       2. gp-u-dex-celr-developer-tst
       3. gp-u-dex-celr-developer-stg
       4. gp-u-dex-celr-developer-prd

Raised the cloud service request for the AD team in order to take care. Please find the request number " RITM0108729"

created the groups and added members to the groups.


Allow ping to to run as non root user & process contrib dir.

Fixes:

I noticed that on occasion the underlying docker environment will not allow ping to work properly for a non-root user. This is an attempt to fix that.
Fix bash syntax error when processing /etc/systemd/system/*.wants files.
Build and install the contents of the contrib directory to add install additional extensions.

Great! Thanks @edespino ! I tested and the changes work well.
But I got one warning as the following:
1 warning found (use --debug to expand):
 - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 5)

Seems that we need to update the line 5 from ENV container docker to ENV container=docker?  https://github.com/cloudberrydb/bootcamp/blob/eb3abc4ffda4aebd642fca0419b6777d56fe4030/000-cbdb-sandbox/Dockerfile.main.rockylinux9#L5
I'm not sure about this, just FYI.

I fixed the ENV warning. Thank you for pointing it out.


Feature: use gon object to show spantree

Although there is no gon object on the obtained window object
but the gon content text information can be obtained through document.innerHTML
so that it can be judged whether it is a gitlab page.

By the way, some of the methods for obtaining gon object judgment mentioned in issues can also be obtained using the document.innerHTML +  regular expression method.

@tavyandy97 This does not modify the previous judgment, it just adds a judgment method, which can work normally in my GitLab Community Edition 14.2.6


Propose license

I propose to use the BSD license, which is not strict at all. I can understand if you'd rather use a different one, feel free to do so.
Anybody know why the package upload gives a warning about the license being empty? Shouldn't the proposed csproj change work?

@frenkel I believe you need to add an additional property group to the .csproj file:
https://stackoverflow.com/questions/57682160/upload-nuget-package-how-to-set-the-license

That's it I think! I've updated the PR.