You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The mv command does not have a '/' after bin. As a result of this if there is no folder bin in GOPATH, then flyte binary will be moved in GOPATH and renamed to bin, which is incorrect.
Expected behavior
The flyte binary should move inside ${GOPATH}/bin/ without getting renamed to bin
Additional context to reproduce
Run make compile in flyte folder.
Screenshots
No response
Are you sure this issue hasn't been raised already?
Yes
Have you read the Code of Conduct?
Yes
The text was updated successfully, but these errors were encountered:
Thank you for bringing this to our attention! It's great to see users like you taking an interest in improving the Flyte platform. Your proposed fix makes sense, and we encourage you to go ahead and create a pull request with the necessary changes. Your contribution will be much appreciated by the Flyte community. Keep up the good work!
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.
Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.
If you want to continue the conversation, start your reply with @dosu-bot.
Describe the bug
In flyte/Makefile
The mv command does not have a '/' after bin. As a result of this if there is no folder bin in GOPATH, then flyte binary will be moved in GOPATH and renamed to bin, which is incorrect.
Expected behavior
The flyte binary should move inside ${GOPATH}/bin/ without getting renamed to bin
Additional context to reproduce
Run make compile in flyte folder.
Screenshots
No response
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: