Wrong link to test results
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
Research direction
The bad link is printed in the test report that microcks-cli test writes, so start by finding where the CLI builds the /tests/ result URL and the base URL it appends to, since the output contains /api//#/tests/. Check how the trailing slash of microcksURL and the #/ fragment are joined. Done when the generated link matches https://…/api/tests/<id> for a URL given with or without a trailing slash, verified by re-running the test command from the report.
Written by the indexing model from the issue text.
Description
Describe the bug
I'm using microcks as binary and run testing stage in gitlab CI as follows:
"$CI_PROJECT_DIR/utils/microcks-cli" test
"$api_version"
"$API_ENDPOINT"
OPEN_API_SCHEMA
--microcksURL="$MICROCKS_URL"
--keycloakClientId="$KEYCLOAK_CLIENT_ID"
--keycloakClientSecret="$KEYCLOAK_CLIENT_SECRET"
--insecure-tls
--filteredOperations='["GET /api/v1/version", "GET /api/v1/services"]'
--waitFor=10sec 2>&1 | tee -a microcks-results/test-report.txt
Report file contains link to results in JSON, but link is corrupted: https://microcks.devops.t-argos.ru/api//#/tests/6ad0b96d3739ce4b92d69ea8
Expected behavior
Correct link is https://microcks.devops.t-argos.ru/api/tests/6ad0b96d3739ce4b92d69ea8 , without //# in the middle.
Actual behavior
No response
How to Reproduce?
No response
Microcks version or git rev
Microcks-CLI 1.0.3
Install method (docker-compose, helm chart, operator, docker-desktop extension,...)
binary
Additional information
No response
- Dominant language
- Java
- Stars
- 2.1k
- Forks
- 371
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 26
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microcks/microcks
-
REST mock returns 500 when an operation name contains a {{variable}} segmentPossibly taken @SebastienDegodez claimed this today. Openkind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 2 days
-
GET /api/jobs ignores page and size parameters when name filter is usedMay be free again @Amaantheprogrammer claimed this 7 days ago, and no pull request is open. Openkind/question
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
microcks/microcks#2357 · 2 comments ·
Maintainers usually reply within 2 days
-
ExpressionParser: hasArgs compares argsStart with 1 instead of -1May be free again @VelpulaGangavardhan claimed this 14 days ago, and no pull request is open. Opencomponent/mocks kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
microcks/microcks#2350 · 2 comments · 2 reactions ·
Maintainers usually reply within 2 days
-
component/importer kind/enhancement kind/question stale
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microcks/microcks#2272 · 11 comments ·
Maintainers usually reply within 2 days
-
Make SSE emitter timeout in McpController configurableMay be free again A pull request for this issue was closed without being merged. Opencomponent/install component/kubernetes component/mocks keep-open kind/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microcks/microcks#2033 · 2 comments · 1 reaction ·
Maintainers usually reply within 2 days
All issues in microcks/microcks
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
PhasetransCrystal/FPSMatch#47 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 76/100
apache/maven-toolchains-plugin#205 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day