Skip to content

CLI $GOPATH not resolved properly #107

Open
@dcsouthwick

Description

@dcsouthwick

Current behavior (how does the issue manifest):
Flogo fails to create any and all projects with Centos8 (other OS not yet checked)

Expected behavior:
Not that. Anything but that.

Minimal steps to reproduce the problem (not required if feature enhancement):
(taken from my initial gitter report)

docker run -it centos:centos8 bash
dnf install golang git
go get -u github.com/project-flogo/cli/...
flogo create new --verbose
Setting up app directory: /root/go/src/new
go: creating new go.mod: module main
Installing: github.com/project-flogo/core@latest
go: finding github.com/project-flogo/core v0.10.1
...
all modules verified
Adding sample flogo.json
Error creating project: open pkg/mod/github.com/project-flogo/core@v0.10.1/examples/engine/main.go: no such file or directory

...profit?

What is the motivation / use case for changing the behavior?
To make the core product function.

Please tell us about your environment (Operating system, docker version, browser & verison if webui, etc):
As described in the centos8 default docker image.

Flogo version (CLI & contrib/lib. If unknown, leave empty or state unknown): 0.X.X
All?
Additional information you deem important (e.g. issue happens only occasionally):
This issue is a path resolving problem. Flogo clearly has no problem pulling the modules and installing them in $GOPATH/pkg, but when it tries to load them, it appears to load from $GOPATHpkg without a '/'. Flogo should not make whatever assumption it seems to be making at this step.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions