search

oxequa / realize

Realize is the #1 Golang Task Runner which enhance your workflow by automating the most common tasks and using the best performing Golang live reloading.
GNU General Public License v3.0
4.46k stars 229 forks source link

install exec: not started #229

Open u007 opened 5 years ago

u007 commented 5 years ago

ive a project based on go module, and on a new machine with latest realize, it somehow returns:

Watching 154 file/s 36 folder/s [11:55:29][....] : Install started [11:55:29][....] : Install exec: not started

settings:
  files:
    outputs:
      status: false
      path: ""
      name: .r.outputs.log
    logs:
      status: false
      path: ""
      name: .r.logs.log
    errors:
      status: false
      path: ""
      name: .r.errors.log
  legacy:
    force: false
    interval: 0s
schema:
- name: mypro
  path: .
  commands:
    run:
      status: true
  args:
    - serve
  watcher:
    extensions:
    - go
    - graphql
    paths:
    - /
    ignore:
      paths:
      - .git
      - .realize
      - vendor
      - .idea
frederikhors commented 5 years ago

Same here. News?

jhartman86 commented 5 years ago

Same thing as well. Downgrading to 2.0.1 works, but if you're using the latest release (eg. just doing go get ...), this error occurs.

Edit these other issues seem to be related as well:

frederikhors commented 5 years ago

@jhartman86 how to downgrade?

jhartman86 commented 5 years ago

@frederikhors this is what worked for me (note, this is within Docker, using the golang:1.11.3-alpine3.8 image):

#!/usr/bin/env bash

export GO111MODULE=off

cd ~/
go get github.com/oxequa/realize
cd /go/src/github.com/oxequa/realize && \
  git fetch && \
  git checkout v2.0.2 && \
  go get github.com/oxequa/realize

RV=$(realize --version)
echo "Realize installed @: $RV"

export GO111MODULE=on

Frankly, I've got no idea why checking out the tag and then running go get ... again works, but it does. YMMV

yu19991013 commented 5 years ago

@frederikhors I've just solved this problem. In your .realize.yaml, path is "." As I wrote same setting, I got below error

exec: not started

So I changed path setting to below.

- name: mypro
  path: ./cmd/api/

Finally, realize could work without error. I hope this comment helps your issue.

chjiyun commented 5 years ago

didn't work for me , tired...

[13:26:05][GIN_APP] : Watching 5 file/s 1 folder/s
[13:26:05][GIN_APP] : Install started
[13:26:05][GIN_APP] : Install 
 exec: not started
chjiyun commented 5 years ago

@jhartman86 it works successfull, 666~

fordguo commented 4 years ago

the lasted version 2.0.3,have the same error.

danielo515 commented 4 years ago

I am also having the same problem. I'm subscribing for a fix 😄

benc-uk commented 4 years ago

Same problem Using it inside a container, get "exec: not started"

patrickhener commented 4 years ago

Same here, also subscribing for solution

smithyj commented 4 years ago

metoo

settings:
  legacy:
    force: false
    interval: 0s
schema:
- name: apiserver
  path: .
  commands:
    fmt:
      status: true
    run:
      status: true
      method: echo 1111
  watcher:
    extensions:
    - go
    paths:
    - /
    ignored_paths:
    - .git
    - .realize
    - vendor
myhendry commented 3 years ago

same issue for me. my .realize.yaml

settings:
  legacy:
    force: false
    interval: 0s
schema:
  - name: go-server
    path: .
    commands:
      run:
        status: true
    watcher:
      extensions:
        - go
      paths:
        - /
      ignored_paths:
        - .git
        - .realize
        - vendor
jeffreylean commented 2 years ago

Adding install under commands, works for me.

    commands:
      install:
        status: true
        method: go install
      run:
        status: true