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

Error when downloading java wildfly starter projects #867

Closed
michael-valdron opened this issue Jun 9, 2022 · 0 comments · Fixed by devfile/registry-support#124 or devfile/registry-support#125
Assignees
Labels
area/registry Devfile registry for stacks and infrastructure kind/bug Something isn't working

Comments

@michael-valdron
Copy link
Member

michael-valdron commented Jun 9, 2022

/kind bug

Which area this bug is related to?

/area registry

What versions of software are you using?

Operating System: N/A

Go Pkg Version: 1.17

Bug Summary

Describe the bug:

The download-starter-project endpoint is producing a file not found error when any of the java-wildfly stack starter projects are requested.

To Reproduce:

Currently:

curl -L https://registry.devfile.io/devfiles/java-wildfly/starterProjects/microprofile-config

After issue #865:

curl -L https://registry.devfile.io/devfiles/java-wildfly/starter-projects/microprofile-config

Expected behavior

A zip archive of the starter project files should be downloaded.

Any logs, error output, screenshots etc? Provide the devfile that sees this bug, if applicable.

Using Registry Viewer after issue #781:

wildfly-error.mp4

Using curl:

{"error":"open /tmp/microprofile-config/README.adoc: no such file or directory","status":"Problem with downloading starter project microprofile-config from location: https://github.com/wildfly/quickstart.git"}%

Additional context

Any workaround?

Removing remote or changing the value of revision to main may work as a workaround until a fix is completed.

UPDATE:

Removing subDir and manually extracting it will work for now.

Suggestion on how to fix the bug

Possible issue within the registry server endpoint or used library functions which does not handle the form of revision or remote properly. A source fix will be required to correct this.

UPDATE:

Bug has been isolated to the subDir extraction feature when using git repos as the remote, a fix to this will need to be discovered and applied to resolve this issue.

Target Date: 06-28-2022

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/registry Devfile registry for stacks and infrastructure kind/bug Something isn't working
Projects
None yet
1 participant