Azure Bot框架-无法访问的QnA Maker服务

时间:2020-10-09 19:18:11

标签: c# botframework

我们无法从Bot Framework调用QnA Maker知识库。该代码可以正常编译。机器人模拟器也会打开并运行。该代码基于以下GitHub存储库:

https://github.com/Microsoft/BotBuilder-Samples/tree/main/samples/csharp_dotnetcore/14.nlp-with-dispatch

在仓库的代码中,有一个带有两个LUIS实例和一个QnA Maker实例的调度模型。我们能够成功地更改调度代码,从而指向我们的三个QnA Maker实例。这在漫游器模拟器中有效,并且我们能够进行通信,而没有发生错误或异常。

但是-我们正在使用QnA Maker KB和后续提示。尽管代码正在运行,但是没有生成任何后续提示。只有答案被返回。我找到了以下博客文章,并尝试修改我们的一项功能,以便能够从QnA Maker KB中获取后续提示:

https://joji.me/en-us/blog/implement-follow-up-prompt-for-qna-bot/

这并没有完全破坏我们的代码。该代码仍然可以编译并运行。我们可以成功地提出直接指向其他QnA Maker KB的问题(返回答案,但没有后续提示),但是当我们提供将调度工具定向到修改后的代码(尝试返回的代码)的输入时,我们返回以下错误后续提示):

控制台错误消息:(注意:此错误仅在我们在Bot仿真器中测试bot并提供将Dispatch定向到此KB的输入时发生)

fail: Microsoft.Bot.Builder.Integration.AspNet.Core.BotFrameworkHttpAdapter[0]
      [OnTurnError] unhandled error : Object reference not set to an instance of an object.
System.NullReferenceException: Object reference not set to an instance of an object.
   at Microsoft.BotBuilderSamples.DispatchBot.ProcessfindPartQnAAsync(ITurnContext`1 turnContext, CancellationToken cancellationToken) in C:\Users\c50941\source\repos\AIM bot\BotBuilder-Samples\samples\csharp_dotnetcore\14.nlp-with-dispatch\Bots\DispatchBot.cs:line 155
   at Microsoft.BotBuilderSamples.DispatchBot.DispatchToTopIntentAsync(ITurnContext`1 turnContext, String intent, RecognizerResult recognizerResult, CancellationToken cancellationToken) in C:\Users\c50941\source\repos\AIM bot\BotBuilder-Samples\samples\csharp_dotnetcore\14.nlp-with-dispatch\Bots\DispatchBot.cs:line 109
   at Microsoft.BotBuilderSamples.DispatchBot.OnMessageActivityAsync(ITurnContext`1 turnContext, CancellationToken cancellationToken) in C:\Users\c50941\source\repos\AIM bot\BotBuilder-Samples\samples\csharp_dotnetcore\14.nlp-with-dispatch\Bots\DispatchBot.cs:line 88
   at Microsoft.Bot.Builder.ActivityHandler.OnTurnAsync(ITurnContext turnContext, CancellationToken cancellationToken)
   at Microsoft.Bot.Builder.BotFrameworkAdapter.TenantIdWorkaroundForTeamsMiddleware.OnTurnAsync(ITurnContext turnContext, NextDelegate next, CancellationToken cancellationToken)
   at Microsoft.Bot.Builder.MiddlewareSet.ReceiveActivityWithStatusAsync(ITurnContext turnContext, BotCallbackHandler callback, CancellationToken cancellationToken)
   at Microsoft.Bot.Builder.BotAdapter.RunPipelineAsync(ITurnContext turnContext, BotCallbackHandler callback, CancellationToken cancellationToken) 

QnAMaker跟踪:(来自Bot仿真器)

Unable to find a QnA Maker service with Knowledge Base ID d1f*****-****-****-****-************. Please add a QnA Maker service to your bot.

基于对其他问题的研究,我们知道在appsettings.json中没有正确的信息是很常见的。我们已经三重检查了这是否正确。这也证明我们可以成功调用其他两个Qna Maker KB,因为它们的凭据通过相同的方法存储在相同的文件中。这是我们经过修改的函数,用于调用特定的KB,以获取后续提示。根据控制台错误,这似乎是我们的错误所在。另外,这是自整个程序正常工作以来我们唯一修改的功能:(我们在输出日志告诉我们存在问题的行处注释了ERROR)

private async Task ProcessfindPartQnAAsync(ITurnContext<IMessageActivity> turnContext, CancellationToken cancellationToken)
{
    _logger.LogInformation("ProcessfindPartQnAAsync");

    var results = await _botServices.findPartQnA.GetAnswersAsync(turnContext);

    // The actual call to the QnA Maker service.
    var response = await _botServices.findPartQnA.GetAnswersAsync(turnContext);
    if (response != null && response.Length > 0)
    {
        // create http client to perform qna query
        var followUpCheckHttpClient = _httpClientFactory.CreateClient();

        // add QnAAuthKey to Authorization header
        followUpCheckHttpClient.DefaultRequestHeaders.Add("Authorization", _configuration["findPartQnAEndpointKey"]);



        // construct the qna query url
        var url = $"{_configuration["findPartQnAEndpointHostName"]}/knowledgebases/{_configuration["findPartQnAKnowledgebaseId"]}/generateAnswer";
                
        // post query
        // ***** ERROR *****
        var checkFollowUpJsonResponse = await followUpCheckHttpClient.PostAsync(url, new StringContent("{​​​​\"question\":\"" + turnContext.Activity.Text + "\"}​​​​", Encoding.UTF8, "application/json")).Result.Content.ReadAsStringAsync();

        // parse result
        var followUpCheckResult = JsonConvert.DeserializeObject<FollowUpCheckResult>(checkFollowUpJsonResponse);

        // initialize reply message containing the default answer
        var reply = MessageFactory.Text(response[0].Answer);

        // ***** ERROR *****
        if (followUpCheckResult.Answers.Length > 0 && followUpCheckResult.Answers[0].Context.Prompts.Length > 0)
        {
            // if follow-up check contains valid answer and at least one prompt, add prompt text to SuggestedActions using CardAction one by one
            reply.SuggestedActions = new SuggestedActions();
            reply.SuggestedActions.Actions = new List<CardAction>();
            for (int i = 0; i < followUpCheckResult.Answers[0].Context.Prompts.Length; i++)
            {
                var promptText = followUpCheckResult.Answers[0].Context.Prompts[i].DisplayText;
                reply.SuggestedActions.Actions.Add(new CardAction() { Title = promptText, Type = ActionTypes.ImBack, Value = promptText });
            }
        }
        await turnContext.SendActivityAsync(reply, cancellationToken);
    }
    else
    {
        await turnContext.SendActivityAsync(MessageFactory.Text("No QnA Maker answers were found."), cancellationToken);
    }
}

我们认为,构造URL的方式一定有问题...尽管我们已经三遍检查了所有信息都是正确的,因为它们在我们的appsettings.json中被命名,并且我们拥有来自存储在此处的Azure服务的正确凭据。感谢您提供的任何帮助。

1 个答案:

答案 0 :(得分:2)

  1. 通过创建新的QnA Maker服务确保您的QnA Maker实例未损坏
  2. 确保您不会在同一回合中多次以相同的发音呼叫相同的QnA Maker服务
相关问题