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]: keploy test fails when running in user-application #1576

Closed
1 task done
shivamsouravjha opened this issue Feb 16, 2024 · 0 comments · Fixed by #1585
Closed
1 task done

[bug]: keploy test fails when running in user-application #1576

shivamsouravjha opened this issue Feb 16, 2024 · 0 comments · Fixed by #1585
Labels
bug Something isn't working Go Pull requests that update Go code Good First Issue Good for newcomers keploy

Comments

@shivamsouravjha
Copy link
Contributor

shivamsouravjha commented Feb 16, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current behavior

  • While running keploy test in user application it fails to grant permission to and thus fails with error failed to set the permission of keploy directory
  • Granting permission in cmd := exec.Command("sudo", "chmod", "-R", "777", path) causes the error.
  • This happens when keploy test cases aren't created and access is being given to them.

Steps to reproduce

  • Build the binary with keploy repo and try to run keploy test in user application.

Important note

  • Check if keploy folder exists, if it does then only grant the access.

Environment

Production

Version

Cloud

Repository

keploy

@shivamsouravjha shivamsouravjha added the bug Something isn't working label Feb 16, 2024
@shivamsouravjha shivamsouravjha added Good First Issue Good for newcomers Go Pull requests that update Go code labels Feb 16, 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 Go Pull requests that update Go code Good First Issue Good for newcomers keploy
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants