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: Mage Install runs into "no such file or directory" #2989

Closed
schristoff opened this issue Feb 8, 2024 · 4 comments · Fixed by #2996
Closed

bug: Mage Install runs into "no such file or directory" #2989

schristoff opened this issue Feb 8, 2024 · 4 comments · Fixed by #2996
Assignees
Labels
bug Oops, sorry!

Comments

@schristoff
Copy link
Member

It's somewhere around here

mage Install
installing Porter from bin to /Users/schristoff/.porter
Error: remove /Users/schristoff/.porter/mixins/arm/arm: no such file or directory
@schristoff schristoff added the bug Oops, sorry! label Feb 8, 2024
@Bharadwajshivam28
Copy link
Contributor

@schristoff can you please assign me this ?

@schristoff
Copy link
Member Author

Here's some light debug steps I would use to start figuring out what is happening:

Goal: Figure out exactly where the error is occurring.
Assumption: Since the error is about removal of a mixins directory, I can safely assume it is in here - if we comment out these lines (682-683), what happens?

Goal: Figure out how to stop the error
Assumption: We have this for loop iterating over all directories it finds on L657 - what directories is it finding?

End Goal: We still want to copy any existing /bin/mixins over, because if I have an arm or terraform mixin installed, I want to use it with my newly locally built Porter bundle. The goal is to copy over all existing and relevant porter bin * directories, while leveraging the newly built executable.

@sgettys is welcome to share his debugs steps he'd go through as well.

@Bharadwajshivam28
Copy link
Contributor

Here's some light debug steps I would use to start figuring out what is happening:

Goal: Figure out exactly where the error is occurring. Assumption: Since the error is about removal of a mixins directory, I can safely assume it is in here - if we comment out these lines (682-683), what happens?

Goal: Figure out how to stop the error Assumption: We have this for loop iterating over all directories it finds on L657 - what directories is it finding?

End Goal: We still want to copy any existing /bin/mixins over, because if I have an arm or terraform mixin installed, I want to use it with my newly locally built Porter bundle. The goal is to copy over all existing and relevant porter bin * directories, while leveraging the newly built executable.

@sgettys is welcome to share his debugs steps he'd go through as well.

Thanks looking in it

@Bharadwajshivam28
Copy link
Contributor

Bharadwajshivam28 commented Feb 8, 2024

@schristoff

Here are few things to discuss and i noticed-

  1. Commenting out line no 682 and 683 fixes the issue

Screenshot from 2024-02-08 23-30-42

  1. But i added some line to Print loop info. Inside the loop then i got some lines with the output-

Screenshot from 2024-02-08 23-34-53

  1. Printed contents of the destination directory
    Screenshot from 2024-02-08 23-38-03

The issue is fixed from the point 1 but we can add these debug info if we need more clarity...

or directly i can create the PR by commenting out those lines

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Oops, sorry!
Projects
None yet
2 participants