split openAPI docs into public vs non public #75
release-pipeline.yaml
on: push
Set Version
0s
Build API
/
publish-api
3m 16s
Build UI
/
publish-ui
2m 12s
Matrix: build-hgweb / deploy-hgweb / verify-published
Waiting for pending jobs
Matrix: Deploy Staging / verify-published
Matrix: Integration tests
Matrix: Deploy Production / verify-published
Generate Release
5s
Deployment protection rules
Reviewers, timers, and other rules protecting deployments in this run
Event | Environments |
---|---|
hahn-kev
approved
|
production |
Annotations
18 errors, 114 warnings, and 1 notice
Integration tests (ubuntu-latest, 6) / Playwright tests on ubuntu-latest for Mercurial 6 on staging
Process completed with exit code 2.
|
[chromium] βΊ emailWorkflow.test.ts:115:1 βΊ register via new-user invitation email:
frontend/tests/emailWorkflow.test.ts#L1
1) [chromium] βΊ emailWorkflow.test.ts:115:1 βΊ register via new-user invitation email βββββββββββββ
Test timeout of 80000ms exceeded.
|
[chromium] βΊ emailWorkflow.test.ts:115:1 βΊ register via new-user invitation email:
frontend/tests/emailWorkflow.test.ts#L130
1) [chromium] βΊ emailWorkflow.test.ts:115:1 βΊ register via new-user invitation email βββββββββββββ
Error: locator.click: Test timeout of 80000ms exceeded.
Call log:
- waiting for locator('dialog.modal').filter({ hasText: 'Add or invite a Member to this project' }).getByRole('button', { name: /Add Member|Add or invite Member/ })
128 | await addMemberModal.selectEditorRole();
129 | await addMemberModal.inviteCheckbox.check();
> 130 | await addMemberModal.submitButton.click();
| ^
131 | await page.locator(':text("has been sent an invitation email")').waitFor();
132 |
133 | // Check invite link returnTo is relative path, not absolute
at /home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/emailWorkflow.test.ts:130:37
|
[chromium] βΊ emailWorkflow.test.ts:115:1 βΊ register via new-user invitation email:
frontend/tests/emailWorkflow.test.ts#L1
1) [chromium] βΊ emailWorkflow.test.ts:115:1 βΊ register via new-user invitation email βββββββββββββ
Retry #1 βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
Test timeout of 80000ms exceeded.
|
[chromium] βΊ emailWorkflow.test.ts:115:1 βΊ register via new-user invitation email:
frontend/tests/emailWorkflow.test.ts#L130
1) [chromium] βΊ emailWorkflow.test.ts:115:1 βΊ register via new-user invitation email βββββββββββββ
Retry #1 βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
Error: locator.click: Test timeout of 80000ms exceeded.
Call log:
- waiting for locator('dialog.modal').filter({ hasText: 'Add or invite a Member to this project' }).getByRole('button', { name: /Add Member|Add or invite Member/ })
128 | await addMemberModal.selectEditorRole();
129 | await addMemberModal.inviteCheckbox.check();
> 130 | await addMemberModal.submitButton.click();
| ^
131 | await page.locator(':text("has been sent an invitation email")').waitFor();
132 |
133 | // Check invite link returnTo is relative path, not absolute
at /home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/emailWorkflow.test.ts:130:37
|
[chromium] βΊ errorHandling.test.ts:61:1 βΊ client-side gql 500 does not break the application:
frontend/tests/fixtures.ts#L40
2) [chromium] βΊ errorHandling.test.ts:61:1 βΊ client-side gql 500 does not break the application ββ
Error: Unexpected response status: 500. (Request URL: https://staging.languagedepot.org/api/graphql. Traceparent: 00-509047366e14c52c0154336ea18e367c-f8948b71679aa33c-01.)
expect(received).toBeLessThan(expected)
Expected: < 500
Received: 500
at fixtures.ts:40
38 | const url = response.request().url();
39 | const unexpectedResponseMessage = `Unexpected response status: ${status}. (Request URL: ${url}. Traceparent: ${traceparent}.)`;
> 40 | expect.soft(response.status(), unexpectedResponseMessage).toBeLessThan(500);
| ^
41 | if (response.request().isNavigationRequest()) {
42 | expect.soft(response.status(), unexpectedResponseMessage).toBeLessThan(400);
43 | }
at BrowserContext.<anonymous> (/home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/fixtures.ts:40:63)
|
[chromium] βΊ errorHandling.test.ts:61:1 βΊ client-side gql 500 does not break the application:
frontend/tests/errorHandling.test.ts#L70
2) [chromium] βΊ errorHandling.test.ts:61:1 βΊ client-side gql 500 does not break the application ββ
Error: locator.click: Error: strict mode violation: getByText('Lexbox') resolved to 2 elements:
1) <a class="link" href="mailto:lexbox_support@groups.β¦>[email protected]</a> aka getByRole('link', { name: '[email protected]' })
2) <a href="/" class="flex flex-col text-lg md:text-3xβ¦>β¦</a> aka getByRole('link', { name: 'Lexbox formerly Language Depot' })
Call log:
- waiting for getByText('Lexbox')
68 | await expect(page.locator(':text-matches("Unexpected response:.*(500)", "g")').first()).toBeVisible();
69 | await page.getByRole('button', { name: 'Dismiss' }).click();
> 70 | await page.getByText('Lexbox').click();
| ^
71 | await new UserDashboardPage(page).waitFor();
72 | test.fail(); // Everything up to here passed, but we expect a soft 500 response assertion to ultimately fail the test
73 | });
at /home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/errorHandling.test.ts:70:34
|
[chromium] βΊ errorHandling.test.ts:61:1 βΊ client-side gql 500 does not break the application:
frontend/tests/fixtures.ts#L40
2) [chromium] βΊ errorHandling.test.ts:61:1 βΊ client-side gql 500 does not break the application ββ
Retry #1 βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
Error: Unexpected response status: 500. (Request URL: https://staging.languagedepot.org/api/graphql. Traceparent: 00-24403a197e52d8b12de6d8a4f98215db-706a15f44f626ca6-01.)
expect(received).toBeLessThan(expected)
Expected: < 500
Received: 500
at fixtures.ts:40
38 | const url = response.request().url();
39 | const unexpectedResponseMessage = `Unexpected response status: ${status}. (Request URL: ${url}. Traceparent: ${traceparent}.)`;
> 40 | expect.soft(response.status(), unexpectedResponseMessage).toBeLessThan(500);
| ^
41 | if (response.request().isNavigationRequest()) {
42 | expect.soft(response.status(), unexpectedResponseMessage).toBeLessThan(400);
43 | }
at BrowserContext.<anonymous> (/home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/fixtures.ts:40:63)
|
[chromium] βΊ errorHandling.test.ts:61:1 βΊ client-side gql 500 does not break the application:
frontend/tests/errorHandling.test.ts#L70
2) [chromium] βΊ errorHandling.test.ts:61:1 βΊ client-side gql 500 does not break the application ββ
Retry #1 βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
Error: locator.click: Error: strict mode violation: getByText('Lexbox') resolved to 2 elements:
1) <a class="link" href="mailto:lexbox_support@groups.β¦>[email protected]</a> aka getByRole('link', { name: '[email protected]' })
2) <a href="/" class="flex flex-col text-lg md:text-3xβ¦>β¦</a> aka getByRole('link', { name: 'Lexbox formerly Language Depot' })
Call log:
- waiting for getByText('Lexbox')
68 | await expect(page.locator(':text-matches("Unexpected response:.*(500)", "g")').first()).toBeVisible();
69 | await page.getByRole('button', { name: 'Dismiss' }).click();
> 70 | await page.getByText('Lexbox').click();
| ^
71 | await new UserDashboardPage(page).waitFor();
72 | test.fail(); // Everything up to here passed, but we expect a soft 500 response assertion to ultimately fail the test
73 | });
at /home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/errorHandling.test.ts:70:34
|
[chromium] βΊ resetProject.test.ts:20:1 βΊ reset project and upload .zip file:
frontend/tests/resetProject.test.ts#L35
3) [chromium] βΊ resetProject.test.ts:20:1 βΊ reset project and upload .zip file βββββββββββββββββββ
Error: Timed out 5000ms waiting for expect(locator).toBeVisible()
Locator: getByText('Project successfully reset')
Expected: visible
Received: <element(s) not found>
Call log:
- expect.toBeVisible with timeout 5000ms
- waiting for getByText('Project successfully reset')
33 | await resetProjectModel.clickNextStepButton('Reset project');
34 | await resetProjectModel.uploadProjectZipFile('tests/data/test-project-one-commit.zip');
> 35 | await expect(page.getByText('Project successfully reset')).toBeVisible();
| ^
36 | await page.getByRole('button', { name: 'Close' }).click();
37 | await resetProjectModel.assertGone();
38 |
at /home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/resetProject.test.ts:35:62
|
[chromium] βΊ resetProject.test.ts:20:1 βΊ reset project and upload .zip file:
frontend/tests/resetProject.test.ts#L75
3) [chromium] βΊ resetProject.test.ts:20:1 βΊ reset project and upload .zip file βββββββββββββββββββ
Retry #1 βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
Error: Timed out 5000ms waiting for expect(locator).toBeVisible()
Locator: getByText('Project successfully reset')
Expected: visible
Received: <element(s) not found>
Call log:
- expect.toBeVisible with timeout 5000ms
- waiting for getByText('Project successfully reset')
73 | await resetProjectModel.clickNextStepButton('Reset project');
74 | await resetProjectModel.uploadProjectZipFile(join(tempDir, 'reset-project-test-step-1.zip'));
> 75 | await expect(page.getByText('Project successfully reset')).toBeVisible();
| ^
76 | await page.getByRole('button', { name: 'Close' }).click();
77 | await resetProjectModel.assertGone();
78 |
at /home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/resetProject.test.ts:75:62
|
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging
Process completed with exit code 1.
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging
Process completed with exit code 1.
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging
Process completed with exit code 2.
|
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging
Process completed with exit code 1.
|
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging
Process completed with exit code 1.
|
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging
Process completed with exit code 1.
|
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging
Process completed with exit code 1.
|
Build API / publish-api:
backend/FixFwData/Program.cs#L1
The variable 'doNothing' is assigned but its value is never used
|
Build API / publish-api:
backend/FwLite/MiniLcm/InMemoryApi.cs#L177
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.
|
Build API / publish-api:
backend/FwLite/MiniLcm/InMemoryApi.cs#L182
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.
|
Build API / publish-api:
backend/FwLite/MiniLcm/InMemoryApi.cs#L214
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.
|
Build API / publish-api:
backend/FwLite/MiniLcm/InMemoryApi.cs#L233
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.
|
Build API / publish-api:
backend/LexData/SeedingData.cs#L18
Parameter 'logger' is unread.
|
Build API / publish-api:
backend/LfClassicData/LfClassicLexboxApi.cs#L62
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.
|
Build API / publish-api:
backend/LfClassicData/LfClassicLexboxApi.cs#L67
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.
|
Build API / publish-api:
backend/LfClassicData/LfClassicLexboxApi.cs#L201
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.
|
Build API / publish-api:
backend/LexBoxApi/Services/UserService.cs#L10
Parameter 'lexAuthService' is unread.
|
Build API / publish-api
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.
|
Build API / publish-api
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.
|
Build API / publish-api
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.
|
Build API / publish-api
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.
|
Build API / publish-api
Parameter 'logger' is unread.
|
Build API / publish-api
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.
|
Build API / publish-api
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.
|
Build API / publish-api
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.
|
Build API / publish-api
Parameter 'lexAuthService' is unread.
|
Build API / publish-api
Parameter 'loggedInContext' is unread.
|
Slow Test:
frontend/[firefox] βΊ userPage.test.ts#L1
frontend/[firefox] βΊ userPage.test.ts took 59.9s
|
Slow Test:
frontend/[firefox] βΊ resetProject.test.ts#L1
frontend/[firefox] βΊ resetProject.test.ts took 26.9s
|
Slow Test:
frontend/[chromium] βΊ userPage.test.ts#L1
frontend/[chromium] βΊ userPage.test.ts took 25.9s
|
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging:
backend/FixFwData/Program.cs#L1
The variable 'doNothing' is assigned but its value is never used
|
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging:
backend/FwLite/MiniLcm/InMemoryApi.cs#L177
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.
|
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging:
backend/FwLite/MiniLcm/InMemoryApi.cs#L182
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.
|
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging:
backend/FwLite/MiniLcm/InMemoryApi.cs#L214
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.
|
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging:
backend/FwLite/MiniLcm/InMemoryApi.cs#L233
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.
|
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging:
backend/LfClassicData/LfClassicLexboxApi.cs#L62
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.
|
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging:
backend/LfClassicData/LfClassicLexboxApi.cs#L67
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.
|
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging:
backend/LfClassicData/LfClassicLexboxApi.cs#L201
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.
|
|
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging:
backend/LexBoxApi/Services/UserService.cs#L10
Parameter 'lexAuthService' is unread.
|
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging
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.
|
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging:
backend/LfClassicData/LfClassicLexboxApi.cs#L62
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.
|
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging:
backend/LfClassicData/LfClassicLexboxApi.cs#L67
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.
|
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging:
backend/LfClassicData/LfClassicLexboxApi.cs#L201
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.
|
|
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging:
backend/LexBoxApi/Services/UserService.cs#L10
Parameter 'lexAuthService' is unread.
|
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging:
backend/LexBoxApi/Auth/JwtTicketDataFormat.cs#L122
'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'
|
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging:
backend/LexBoxApi/Hub/CrdtProjectChangeHub.cs#L8
Parameter 'loggedInContext' is unread.
|
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging:
backend/LexBoxApi/Services/HgService.cs#L374
The switch expression does not handle some values of its input type (it is not exhaustive) involving an unnamed enum value. For example, the pattern '(LexBoxApi.Services.RepoEmptyState)2' is not covered.
|
|
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging
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.
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging
The support for python 2.7 was removed on June 19, 2023. Related issue: https://github.com/actions/setup-python/issues/672
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging:
backend/Testing/Fixtures/Tests/ServicesFixtureTests.cs#L8
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.
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging:
backend/Testing/Fixtures/Tests/ServicesFixtureTests.cs#L8
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.
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging:
backend/FixFwData/Program.cs#L1
The variable 'doNothing' is assigned but its value is never used
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging:
backend/FwLite/MiniLcm/InMemoryApi.cs#L177
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.
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging:
backend/FwLite/MiniLcm/InMemoryApi.cs#L182
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.
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging:
backend/FwLite/MiniLcm/InMemoryApi.cs#L214
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.
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging:
backend/FwLite/MiniLcm/InMemoryApi.cs#L233
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.
|
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging:
backend/LfClassicData/LfClassicLexboxApi.cs#L62
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.
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging:
backend/LfClassicData/LfClassicLexboxApi.cs#L67
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.
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging:
backend/LfClassicData/LfClassicLexboxApi.cs#L201
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.
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging:
backend/LexBoxApi/Services/UserService.cs#L10
Parameter 'lexAuthService' is unread.
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging
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.
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging:
backend/LfClassicData/LfClassicLexboxApi.cs#L62
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.
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging:
backend/LfClassicData/LfClassicLexboxApi.cs#L67
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.
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging:
backend/LfClassicData/LfClassicLexboxApi.cs#L201
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.
|
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging:
backend/LexBoxApi/Services/UserService.cs#L10
Parameter 'lexAuthService' is unread.
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging:
backend/LexBoxApi/Hub/CrdtProjectChangeHub.cs#L8
Parameter 'loggedInContext' is unread.
|
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging:
backend/LexBoxApi/Auth/JwtTicketDataFormat.cs#L122
'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'
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging:
backend/LexBoxApi/Services/HgService.cs#L374
The switch expression does not handle some values of its input type (it is not exhaustive) involving an unnamed enum value. For example, the pattern '(LexBoxApi.Services.RepoEmptyState)2' is not covered.
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging
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.
|
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging:
backend/FixFwData/Program.cs#L1
The variable 'doNothing' is assigned but its value is never used
|
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging:
backend/FwLite/MiniLcm/InMemoryApi.cs#L177
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.
|
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging:
backend/FwLite/MiniLcm/InMemoryApi.cs#L182
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.
|
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging:
backend/FwLite/MiniLcm/InMemoryApi.cs#L214
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.
|
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging:
backend/FwLite/MiniLcm/InMemoryApi.cs#L233
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.
|
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging:
backend/LfClassicData/LfClassicLexboxApi.cs#L62
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.
|
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging:
backend/LfClassicData/LfClassicLexboxApi.cs#L67
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.
|
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging:
backend/LfClassicData/LfClassicLexboxApi.cs#L201
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.
|
|
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging:
backend/LexBoxApi/Services/UserService.cs#L10
Parameter 'lexAuthService' is unread.
|
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging
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.
|
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging:
backend/Testing/Fixtures/Tests/ServicesFixtureTests.cs#L8
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.
|
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging:
backend/Testing/Fixtures/Tests/ServicesFixtureTests.cs#L8
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.
|
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging
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.
|
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging:
backend/LfClassicData/LfClassicLexboxApi.cs#L62
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.
|
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging:
backend/LfClassicData/LfClassicLexboxApi.cs#L67
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.
|
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging:
backend/LfClassicData/LfClassicLexboxApi.cs#L201
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.
|
|
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging:
backend/LexBoxApi/Services/UserService.cs#L10
Parameter 'lexAuthService' is unread.
|
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging:
backend/LexBoxApi/Auth/JwtTicketDataFormat.cs#L122
'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'
|
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging:
backend/LexBoxApi/Hub/CrdtProjectChangeHub.cs#L8
Parameter 'loggedInContext' is unread.
|
|
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging:
backend/LexBoxApi/Services/HgService.cs#L374
The switch expression does not handle some values of its input type (it is not exhaustive) involving an unnamed enum value. For example, the pattern '(LexBoxApi.Services.RepoEmptyState)2' is not covered.
|
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging:
backend/FixFwData/Program.cs#L1
The variable 'doNothing' is assigned but its value is never used
|
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging:
backend/FwLite/MiniLcm/InMemoryApi.cs#L177
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.
|
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging:
backend/FwLite/MiniLcm/InMemoryApi.cs#L182
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.
|
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging:
backend/FwLite/MiniLcm/InMemoryApi.cs#L214
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.
|
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging:
backend/FwLite/MiniLcm/InMemoryApi.cs#L233
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.
|
|
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging:
backend/LfClassicData/LfClassicLexboxApi.cs#L62
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.
|
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging:
backend/LfClassicData/LfClassicLexboxApi.cs#L67
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.
|
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging:
backend/LfClassicData/LfClassicLexboxApi.cs#L201
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.
|
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging:
backend/LexBoxApi/Services/UserService.cs#L10
Parameter 'lexAuthService' is unread.
|
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging:
backend/Testing/Fixtures/Tests/ServicesFixtureTests.cs#L8
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.
|
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging:
backend/Testing/Fixtures/Tests/ServicesFixtureTests.cs#L8
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.
|
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging
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.
|
|
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging:
backend/LfClassicData/LfClassicLexboxApi.cs#L62
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.
|
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging:
backend/LfClassicData/LfClassicLexboxApi.cs#L67
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.
|
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging:
backend/LfClassicData/LfClassicLexboxApi.cs#L201
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.
|
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging:
backend/LexBoxApi/Services/UserService.cs#L10
Parameter 'lexAuthService' is unread.
|
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging:
backend/LexBoxApi/Auth/JwtTicketDataFormat.cs#L122
'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'
|
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging:
backend/LexBoxApi/Services/HgService.cs#L374
The switch expression does not handle some values of its input type (it is not exhaustive) involving an unnamed enum value. For example, the pattern '(LexBoxApi.Services.RepoEmptyState)2' is not covered.
|
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging:
backend/LexBoxApi/Hub/CrdtProjectChangeHub.cs#L8
Parameter 'loggedInContext' is unread.
|
|
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging
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.
|
π Playwright Run Summary
5 failed
[chromium] βΊ emailWorkflow.test.ts:115:1 βΊ register via new-user invitation email ββββββββββββββ
[chromium] βΊ errorHandling.test.ts:61:1 βΊ client-side gql 500 does not break the application βββ
[chromium] βΊ resetProject.test.ts:20:1 βΊ reset project and upload .zip file ββββββββββββββββββββ
[firefox] βΊ emailWorkflow.test.ts:115:1 βΊ register via new-user invitation email βββββββββββββββ
[firefox] βΊ errorHandling.test.ts:61:1 βΊ client-side gql 500 does not break the application ββββ
57 passed (11.3m)
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
dotnet-unit-test-results
Expired
|
2.77 KB |
|
playwright-traces-ubuntu-latest-hg-6
Expired
|
353 MB |
|