Error occurs when publish luis
See original GitHub issueVersion
source code 7 Oct
Describe the bug
publish luis errors
To Reproduce
I create a lu file and click the ‘startbot’ button in the upper right corner, and asked to fill in the ‘athuoring key’.
Firstly, from the reference here, authoring key, goto luis setting page, I found this:
The only key in this page is the Primary Key of Starter_key. Then I fill in this one. But error appears, Composer shows this message: 'Error publishing to LUIS.'
, then I goto the debug console line and get the message code:
"code":"401","message": "The apps - Get applications list Operation under LUIS Programmatic APIs v2.0 API is not supported with the current subscription key and pricing tier LUIS.F0."
,
So I do not know If I should update my luis pricing tier to get the access permission.
After, I get into Azure portal to create a luis cognitive service (S0), and find that there are two resources have been created, one is the name of my luis, the other one is ‘luisname-Authoring’.
Firstly, I use the luis resource key, same as before, ‘401’ is the result.
Then I try the second one, errors as before:
code: 'BadArgument', message: 'Import operation has failed.'
,
and the request body is
'{"name":"empty(composer)-Main.en-us.lu","versionId":"0000000001","desc":"Model for empty app, targetting composer for Main.lu file","culture":"en-us","intents":[{"name":"greeting"}],"entities":[],"closedLists":[],"composites":[],"patternAnyEntities":[],"regex_entities":[],"prebuiltEntities":[],"regex_features":[],"model_features":[],"patterns":[],"utterances":[{"text":"hi","intent":"greeting","entities":[]},{"text":"hello","intent":"greeting","entities":[]}]}'
So, what is the right step to solve this issue. Thanks.
Expected behavior
Publish luis successfully
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (6 by maintainers)
Top GitHub Comments
This is a luis service issue. No known changes needed on our end.
Hi @lei9444 , I remember you’re the author of this package, can you help to check this issue?