Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] AASX File Server does not return a profile for /description #542

Closed
aaronzi opened this issue Nov 25, 2024 · 0 comments · Fixed by #543
Closed

[BUG] AASX File Server does not return a profile for /description #542

aaronzi opened this issue Nov 25, 2024 · 0 comments · Fixed by #543
Assignees
Labels
bug Something isn't working good first issue Good for newcomers

Comments

@aaronzi
Copy link
Member

aaronzi commented Nov 25, 2024

Describe the bug

The endpoint /description for the AASX File Server returns an empty profiles array: {"profiles" : []}

To Reproduce

Start the service and do a GET-Request on /description

Expected behavior

I would expect to get the following result:

{
  "profiles" : { "https://admin-shell.io/aas/API/3/0/AasxFileServerServiceSpecification/SSP-001"}
}

See this PR for reference.

BaSyx (please complete the following information):

  • BaSyx Version [v2.0]
  • BaSyx SDK [Java]
  • AAS Version [DotAAS V3]

System (please complete the following information):

  • OS: [Windows Docker]
  • CPU architecture: [x86]
@aaronzi aaronzi added the bug Something isn't working label Nov 25, 2024
@aaronzi aaronzi moved this from To triage to Ready in Support Requests Nov 25, 2024
@aaronzi aaronzi added the good first issue Good for newcomers label Nov 25, 2024
@seicke seicke self-assigned this Nov 25, 2024
@github-project-automation github-project-automation bot moved this from Ready to Done in Support Requests Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants