markbates / markbates/refresh

init not working on macOS

Open
#36 6 comments 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
196
Forks
32
PR merge metrics
No merged PRs in 30d

Description

Unsure on what is happening but `refresh init` is not creating the default yml file.
Note that the `refresh.yml.bak` file is just my backup file to submit this issue.
Also note that the project is outside GOPATH and it seems to make no difference if `GO111MODULE=on` is set.

```
> ls -l
total 24088
-rw-r--r--@ 1 gus staff 130 25 Aug 18:28 Makefile
-rwxr-xr-x 1 gus staff 12272428 25 Aug 18:26 backend*
-rw------- 1 gus staff 2930 25 Aug 18:24 go.mod
-rw------- 1 gus staff 39189 25 Aug 18:24 go.sum
-rw-r--r--@ 1 gus staff 2235 25 Aug 17:38 main.go
drwxr-xr-x 5 gus staff 160 25 Aug 12:52 pkg/
-rw-r--r--@ 1 gus staff 997 25 Aug 18:27 refresh.yml.bak
drwxr-xr-x 4 gus staff 128 25 Aug 14:27 vendor/
> refresh init
Refresh (1.4.0)

> ls -l
total 24088
-rw-r--r--@ 1 gus staff 130 25 Aug 18:28 Makefile
-rwxr-xr-x 1 gus staff 12272428 25 Aug 18:26 backend*
-rw------- 1 gus staff 2930 25 Aug 18:24 go.mod
-rw------- 1 gus staff 39189 25 Aug 18:24 go.sum
-rw-r--r--@ 1 gus staff 2235 25 Aug 17:38 main.go
drwxr-xr-x 5 gus staff 160 25 Aug 12:52 pkg/
-rw-r--r--@ 1 gus staff 997 25 Aug 18:27 refresh.yml.bak
drwxr-xr-x 4 gus staff 128 25 Aug 14:27 vendor/
```

Unable to get any more verbose output from the binary.

`refresh run` runs without the config file but does not work:

```
> refresh run
Refresh (1.4.0)

2019/08/25 18:32:49 No configuration loaded, proceeding with defaults
refresh: 2019/08/25 18:32:49 === Rebuild on: :start: ===
refresh: 2019/08/25 18:32:49 === Running: go build -v -o (PID: 48379) ===
refresh: 2019/08/25 18:32:50 === Building Completed (PID: 48379) (Time: 759.844718ms) ===
refresh: 2019/08/25 18:32:50 === fork/exec : no such file or directory
===
```

However it works fine when I manually create a `refresh.yml` file.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing `refresh init` and `refresh run` on macOS with the command output shown. Inspect the CLI paths responsible for creating the default configuration and launching the rebuilt binary; done means `refresh init` creates `refresh.yml` and `refresh run` executes successfully without a manually created config.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, macos
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.