Cannot create venv after installing virtualenv package

Process completed with exit code 1.

Process completed with exit code 127.

Process completed with exit code 1.

Running this action via 'uses: EnricoMi/publish-unit-test-result-action/composite@v2 is deprecated! For details, see: https://github.com/EnricoMi/publish-unit-test-result-action/tree/v2#running-as-a-composite-action

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-dotnet@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

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

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

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

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

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

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

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

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

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

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

The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.

Nullability of reference types in type of parameter 'value' of 'void LexboxAuthAttribute.Policy.set' doesn't match implicitly implemented member 'void IAuthorizeData.Policy.set' (possibly because of nullability attributes).

Cannot convert null literal to non-nullable reference type.

Parameter 'lexAuthService' is unread.

Possible null reference argument for parameter 'activity' in 'void ActivityExtensions.RecordException(Activity activity, Exception? ex)'.

Dereference of a possibly null reference.

Possible null reference argument for parameter 'Email' in 'TestingControllerProjectUser.TestingControllerProjectUser(string? Username, string Role, string Email, Guid Id)'.

'JwtBearerOptions.SecurityTokenValidators' is obsolete: 'SecurityTokenValidators is no longer used by default. Use TokenHandlers instead. To continue using SecurityTokenValidators, set UseSecurityTokenValidators to true. See https://aka.ms/aspnetcore8/security-token-changes'

Dereference of a possibly null reference.

Possible null reference argument for parameter 'newAdminEmail' in 'Task EmailService.SendNewAdminEmail(IAsyncEnumerable<User> admins, string newAdminName, string newAdminEmail)'.

Dereference of a possibly null reference.

Dereference of a possibly null reference.

Dereference of a possibly null reference.

Dereference of a possibly null reference.

Dereference of a possibly null reference.

Dereference of a possibly null reference.

Possible null reference argument for parameter 'value' in 'Claim.Claim(string type, string value)'.

Dereference of a possibly null reference.

Avoid "async void" methods, because any exceptions not handled by the method will crash the process (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD100.md)