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] Containerless-Kantra : [Windows-Only - Java Project analysis] Fails to create static-report #362

Closed
1 task done
kthatipally opened this issue Oct 29, 2024 · 6 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@kthatipally
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Konveyor version

https://github.com/konveyor/kantra/releases/tag/v0.6.0-alpha.2

Priority

Undefined (Default)

Current Behavior

I have run the analysis using the command:

.\windows-kantra.exe analyze-bin --input C:\testing\spring-petclinic\ --output .\output-spc --target cloud-readiness --overwrite

The files Dependencies.yaml and output.yaml have been successfully created. However, there's a problem with generating the static-report due to an issue with the cp command for the static-report. Let me know if you need any more info.

See the error below:

Image

Expected Behavior

Analysis is run successfully, and the static-report is generated.

How Reproducible

Always (Default)

Steps To Reproduce

  1. OS: Windows
  2. Run Command: .\windows-kantra.exe analyze-bin --input C:\testing\spring-petclinic\ --output .\output-spc --target cloud-readiness --overwrite
  3. Run via windows-powershell

Environment

  • OS: Windows

Anything else?

No response

@kthatipally kthatipally added kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Oct 29, 2024
@konveyor-ci-bot
Copy link

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.

@konveyor-ci-bot konveyor-ci-bot bot added the needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. label Oct 29, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in Planning Oct 29, 2024
@eemcmullan
Copy link
Collaborator

@kthatipally Thank you for finding this issue. This is interesting because the cp command for the static report is only (supposed) to be used by the container analyze command, as we don't use an executable for the containerless version. Do you have the analysis.log and kantra logs?

@kthatipally
Copy link
Contributor Author

kthatipally commented Oct 29, 2024

Hi @eemcmullan ,
Please find the attached analysis.log.
static-report.log is empty. Let me know if you need more logs. analysis.log

This is the line that is causing the error:

cmd := exec.Command("cp", "-r", outputFileDestPath, a.output)

@eemcmullan
Copy link
Collaborator

@kthatipally Sorry, forgot we did that there. Is it fair to say xcopy would be the equivalent command?

@kthatipally
Copy link
Contributor Author

@eemcmullan , Yes, the xcopy command works on Windows. Would it be worth considering a platform-agnostic approach? We might be able to use or adapt a function like (

func copyFileContents(src string, dst string) (err error) {
) to ensure cross-platform compatibility.

@eemcmullan
Copy link
Collaborator

Fixed in #366

@github-project-automation github-project-automation bot moved this from 🆕 New to ✅ Done in Planning Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
Status: ✅ Done
Development

No branches or pull requests

2 participants