-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Skaffold dev does not rebuild or deploy after file changes (macOS Catalina) #3109
Comments
I discovered that if run I cloned skaffold repository into |
Thanks for opening this @dahovey - can you provide some logs for us with |
@dahovey i'm also curious if running |
Ran below from
If I run Hope the below helps in some way.
|
Also I can consistently reproduce this with all projects I my machine. |
I upgraded to v1.0.0 but issue still persists. Any guidance if issue might be something with my setup? |
Figured out the issue! It has to do with the case of the original folder compared to what was typed in the terminal. Originally I created the folder as I was able to use the below simple code to isolate this as NOT a skaffold specific problem. If using the below code and there are differences in case (created folder case vs. current directory), no file watcher events are triggered. package main
import (
"fmt"
"github.com/rjeczalik/notify"
)
func main() {
c := make(chan notify.EventInfo, 100)
if err := notify.Watch("./...", c, notify.All); err != nil {
fmt.Println("Error watching directory")
return
}
for {
fmt.Println("Wating for changes...")
select {
case e := <-c:
fmt.Println("Change detected", e)
}
}
} Coming from a Windows background, and being that MacOS doesn't complain about the difference in case I didn't even notice the difference. I would consider this a bug with the |
@dahovey glad you were able to dig into this issue, and sorry there's nothing we can really do for you here! going to close this now as it's not a skaffold specific issue. |
Expected behavior
Running
skaffold dev
should rebuild docker images and re-deploy after local file changes.Actual behavior
After first deployment, and after making any local file changes nothing happens.
Information
Steps to reproduce the behavior
examples
folderskaffold dev
.I tried
helm-deployment
andmicroservices
samples. Making change to change to any local file doesn't trigger new build.The text was updated successfully, but these errors were encountered: