Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: microsoft/variable-substitution@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The following actions uses node12 which is deprecated and will be forced to run on node16: microsoft/variable-substitution@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Non-nullable property 'Message' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'Role' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'Content' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Possible null reference argument for parameter 'previous' in 'ChatLinkedListItem.ChatLinkedListItem(ChatMessage message, ChatLinkedListItem previous, AvailableGptModels gptModel)'.

Non-nullable event 'OnAuthenticationStateChangedEvent' must contain a non-null value when exiting constructor. Consider declaring the event as nullable.

This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.

Argument of type 'string?[]' cannot be used for parameter 'authorizedUrls' of type 'IEnumerable<string>' in 'AuthorizationMessageHandler AuthorizationMessageHandler.ConfigureHandler(IEnumerable<string> authorizedUrls, IEnumerable<string>? scopes = null, string? returnUrl = null)' due to differences in the nullability of reference types.

Argument of type 'string?[]' cannot be used for parameter 'authorizedUrls' of type 'IEnumerable<string>' in 'AuthorizationMessageHandler AuthorizationMessageHandler.ConfigureHandler(IEnumerable<string> authorizedUrls, IEnumerable<string>? scopes = null, string? returnUrl = null)' due to differences in the nullability of reference types.

This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.