Binary artifacts must be rebuilt prior to download with up to date changes made by the conversational interface.

Add content moderator and also look for an ARM for https://portal.azure.com/#create/Microsoft.CognitiveServicesContentModerator and put into deploy process.

https://docs.microsoft.com/en-us/previous-versions/azure/reference/dn725458(v=azure.100)

Generalize the use of https://stackoverflow.com/questions/61221414/how-to-suppress-and-or-increase-the-15-seconds-timeout-message-while-posting-to.

As default when accuracy of intent is low, a subject catcher should run trying to find an appropriated subject from the Subject Tree and offer this an alternative.

Ref: microsoft/BotFramework-WebChat#1146

Store.js:692 Uncaught TypeError: e.ofType(...).map(...).filter(...).throttleTime is not a function
at O (Store.js:692)
at combineEpics.js:37
at Array.map ()
at combineEpics.js:36
at t.project (createEpicMiddleware.js:50)
at t._next (map.js:100)
at t.next (Subscriber.js:120)
at t.next (Subject.js:82)
at createEpicMiddleware.js:61
at applyMiddleware.js:52

sequelize deprecated Instance.updateAttributes has been deprecated, please use Instance.update instead node_modules\sequelize\lib\model.js:4232:9

nlpKey is specified more than once on endPoint address. See records of Instance table.

Today there is no useful log whenever an exception occurs while loading the web.

pluginName: '@semantic-release/git' } { Error: Command failed: git commit

It is not possible to specify additional Directory in function IsDirectory();

Sample code.

  public static getDialogSetup(min: GBMinInstance) {

    return {
      id: '/setup', waterfall: [
        async step => {

          const phone = step.context.activity.from.id;
          const service = new OpptService();
          const ref = await TurnContext.getConversationReference(step.context.activity);
          await service.updateConversationReference(phone, JSON.stringify(ref));

          await step.context.sendActivity('Telefone irá receber notificações.');

          return await step.next();
        }
      ]
    };
  }

  public static getDialogMessageBack(min: GBMinInstance) {

    return {
      id: '/back', waterfall: [
        async step => {

          const phone = step.context.activity.from.id;
          const service = new OpptService();
          const conversationReference = await service.getConversationReference(phone);

          await min.bot.continueConversation(conversationReference, async turnContext => {
            // TODO: MicrosoftAppCredentials.trustServiceUrl('https://directline.botframework.com',
            new Date(new Date().setFullYear(new Date().getFullYear() + 10)));

          await turnContext.sendActivity('proactive hello');

          return await step.next();
        });

        }
      ]
  }
};

Alerta da noite de 03/04
Parece se tratar de algum movimento externo a Pragmatismo.
A vulnerabilidade alertada afetaria o OppBot?

“
permite que a entrada do usuário externo substitua certos atributos internos por um nome conflitante, conforme demonstrado por 'constructor': {'name': 'Symbol'}. Portanto, uma carga útil criada pode substituir esse atributo interno para manipular o resultado da detecção de tipo.

GHSA-6c8f-qphg-qjgp

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

The bot theme will change when the subject is selected/detected.

Ref: microsoft/BotFramework-WebChat#1146

Store.js:692 Uncaught TypeError: e.ofType(...).map(...).filter(...).throttleTime is not a function
at O (Store.js:692)
at combineEpics.js:37
at Array.map ()
at combineEpics.js:36
at t.project (createEpicMiddleware.js:50)
at t._next (map.js:100)
at t.next (Subscriber.js:120)
at t.next (Subject.js:82)
at createEpicMiddleware.js:61
at applyMiddleware.js:52

Today, automation is just partial, requiring Data Source and Index to have manual procedures.

A customer wants a new answer type: Navigate to URL.
Proposed syntax on Answer column, just like dialog:vba-name:

url:http://www.domain.com

On web channel, this is shown and the browser navigates to this link on a new window/tab.
On other channels, the link is shown allowing the address to be reached by tap/click.

While accessing the web version a 404 is thrown.

To Reproduce
Steps to reproduce the behavior:

1. Go to bot homepage
2. Go to console (F12)
3. See error

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

Describe the bug
When run build task in VSCode occurs the folowing error, despite the build run succesfuly:
Error: The typescript task detection didn't contribute a task for the following configuration:
{
"type": "typescript",
"tsconfig": "tsconfig.json",
"option": "watch",
"problemMatcher": [
"$tsc-watch"
],
"group": {
"kind": "build",
"isDefault": true
}
}
The task will be ignored.

To Reproduce
Steps to reproduce the behavior:

1. Ctrl + B
2. Run tscwatch [BotServer path]

Expected behavior
Build without errors

2020-02-28T12:22:28.857Z [GeneralBots] �[31merror�[39m: ERROR: Error finding dialog associated to NLP event: showReviews: connect ETIMEDOUT [IP REMOVED]: Error: Error finding dialog associated to NLP event: showReviews: connect ETIMEDOUT [IP REMOVED]:
at GBConversationalService.routeNLP (D:\home\site\wwwroot\dist\packages\core.gbapp\services\GBConversationalService.js:128:39)
at process._tickCallback (internal/process/next_tick.js:68:7)

See this code

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

ZIP https://camo.githubusercontent.com/0150c0f148d50fe9750ebc5d313581da699a8c50/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f7a69702d646f776e6c6f61642d626c75652e737667
Chocolatey https://camo.githubusercontent.com/7ebb46b310e025a9b721bbcb8434208e1f4abb50/68747470733a2f2f696d672e736869656c64732e696f2f63686f636f6c617465792f762f736368656d61637261776c65722e737667

O Bot deve apresentar a situação do NGROK