running cmd in a subdirectory, issues with go install
llonchj opened this issue · comments
I have a big project with a structure similar to:
.../project /xxxx file.go /yyyy file.go /cmd main.go other.go
I have the following setup:
settings:
legacy:
force: false
interval: 0s
server:
status: false
open: false
port: 5001
host: ""
schema:
- name: server
path: cmd
commands:
install:
status: true
run:
status: true
args:
- server
- --log-level=info
watcher:
paths:
- ../
extensions:
- go
ignored_paths:
- ../.git
- ../.realize
- ../vendor
and when i run realize start
get the following error:
[20:37:18][SERVER] : Watching 472 file/s 167 folder/s
[20:37:18][SERVER] : Install started
[20:37:18][SERVER] : Install
exec: not started
Changing the watcher.paths to /
and running again realize start
returns:
[06:38:02][SERVER] : Watching 6 file/s 1 folder/s
[06:38:02][SERVER] : Install started
[06:38:02][SERVER] : Install
[06:39:05][SERVER] : Running..
[06:39:05][SERVER] : .......
[06:39:05][SERVER] : .......
[06:39:05][SERVER] : .......
[06:39:05][SERVER] : .......
In the first scenario, is watching the files but install fails. In the second scenario it works, but only watches for the 6 files in the cmd folder.
What am I doing wrong?
I ran into something similar and I think the issue has to do with how many files/folders are being watched. In my case I was also getting exec: not started, but when I excluded node_modules and a few other paths to lower the watch count, it started to work again.
Thanks @hemancuso it solved the situation. Had a big tmp folder. Just added the tmp to ignored_paths and it worked.
@OxequaTeam should this case be handled by the software?
I was experiencing the same issue; ignoring node_modules
solved it for me.
Adding error output in the hopes that Google will provide others with the same issue better search results than I had:
$ realize start
[12:47:45][APPLICATION] : Watching 93 file/s 675 folder/s
[12:47:45][APPLICATION] : Install started
[12:47:45][APPLICATION] : Install
exec: not started
@larrybotha under some scenarios, it is related to the amount of watched folders.
I am right now experiencing same error under another case scenario (only 107 file/s 22 folder/s watched) which will investigate at some point
Am encountering the same issue, for me also the amount of files watched didn't affect the issue. Reduced to only watching 2 files, 1 folder and didn't matter.