Open phoogers opened 1 year ago
Hi Peter,
I think it was due to a transient issue with the online database containing the templates.
Can you tell me when you did this operation => So I can check the logs.
Gilles
From: phoogers @.> Sent: Friday, April 28, 2023 13:23 To: GFlisch/Arc4u.Guidance.Doc @.> Cc: Subscribed @.***> Subject: [GFlisch/Arc4u.Guidance.Doc] When creating a new microservice, there are error logs in the Guidance output logs (Issue #171)
Describe the bug Some errors in the output of the Guidance when adding a microservice - in this case called "Core"
To Reproduce Steps to reproduce the behavior:
Expected behavior Guidance creates a Core microservice without errors
Full output of the action:
Low: Adding Micro-service. Low: Create service Core. Med: Folder Core is created to BE. Med: Adding project: Infraref.Core.Host. Med: Added Program.cs file to project Infraref.Core.Host. Med: Adding Properties folder. Med: Added Properties folder. Med: Adding Configs folder. Med: Added Configs folder. Med: Added Properties\launchSettings.json file to project Infraref.Core.Host. Med: Added HealthChecks\LogHealthCheck.cs file to project Infraref.Core.Host. Med: Added Properties\AssemblyInfo.cs file to project Infraref.Core.Host. Med: Adding an AzureDevOps BuildAndPublish.yml file. Med: Added BuildAndPublish.yml file to folder Core. Med: Adding Infrastructure folder. Med: Added Infrastructure folder. Med: Added OAuth2HttpHandler.cs file to folder Infrastructure. Med: Added OAuth2GrpcInterceptor.cs file to folder Infrastructure. Med: Added OAuth2TokenSettingsReader.cs file to folder Infrastructure. Med: Added VolatileMemorySettingsReader.cs file to folder Infrastructure. Med: Add Kestrel configuration. Med: Adding Components folder. Med: Added Components folder. Med: Adding Dev folder to Components. Med: Added Dev folder to Components. Med: Adding Test folder to Components. Med: Added Test folder to Components. Med: Adding Acc folder to Components. Med: Added Acc folder to Components. Med: Adding Prod folder to Components. Med: Added Prod folder to Components. Med: Add SwaggerUi3Route("Core" to Yarp startup file. Med: Added appsettings.json file to folder Configs. Med: Adding section Memory.Settings to the appSettings file. Med: Added appsettings.Development.json file to folder Configs. Med: Adding section AppSettings to the appSettings file. Error: Error when calling content service, wait 200 ms. Error: Error when calling content service, wait 500 ms. Error: Error when calling content service, wait 1000 ms. Error: HTTP Response:
Arc4u.LicManager.Core.Interface.Sdk.RestException: The HTTP status code of the response was not expected (500).
Status: 500 Response:
at Arc4u.LicManager.Core.Interface.Sdk.AssetV1Client.
Arc4u.LicManager.Core.Interface.Sdk.RestException: The HTTP status code of the response was not expected (500).
Status: 500 Response:
at Arc4u.LicManager.Core.Interface.Sdk.AssetV1Client.
Arc4u.LicManager.Core.Interface.Sdk.RestException: The HTTP status code of the response was not expected (500).
Status: 500 Response:
at Arc4u.LicManager.Core.Interface.Sdk.AssetV1Client.
Arc4u.LicManager.Core.Interface.Sdk.RestException: The HTTP status code of the response was not expected (500).
Status: 500 Response:
at Arc4u.LicManager.Core.Interface.Sdk.AssetV1Client.
Arc4u.LicManager.Core.Interface.Sdk.RestException: The HTTP status code of the response was not expected (500).
Status: 500 Response:
at Arc4u.LicManager.Core.Interface.Sdk.AssetV1Client.
— Reply to this email directly, view it on GitHubhttps://github.com/GFlisch/Arc4u.Guidance.Doc/issues/171, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABNE2KOM2UWQKZ53Q7MBWGTXDOSE5ANCNFSM6AAAAAAXPDJSME. You are receiving this because you are subscribed to this thread.Message ID: @.***>
Hi Gilles,
It must have been between these 2 commits, so Fri 28/4 between 13:20 and 13:24
Describe the bug Some errors in the output of the Guidance when adding a microservice - in this case called "Core"
To Reproduce Steps to reproduce the behavior:
Expected behavior Guidance creates a Core microservice without errors
Full output of the action: