Does anyone else have trouble getting the build to reliably create new images on their local machine? My workflow:

* make a change in some core module, e.g. add a print statement in the server
* ./gradlew :composeBuild
* VERSION=dev docker-compose up -V
* expect print statement to fire

I would expect the print statement to run, but this isn't reliably happening in this workflow. It seems like there's some series of steps I need to run to get it to pick up changes. Still trying to figure out what the exact steps are (maybe includes

./gradlew clean

). Anyone else experiencing similar?

this problem is getting expensive for me, because every time i run into it, i auto lose like 30-45 min of dev time.

I tried this and the print statement worked without ./`gradlew clean`.

Where exactly did you add the print statement? I added the statement in

ServerApp.java

by the way.

line 181 of ServerApp.java

first line in the main method.

Adding the line in line 181 also works for me. No idea what is the root cause. Is it possible that you are running another server in the background already?

nah. this has happened a few times now.

my hunch is that something in gradle or docker is getting cached sometimes.

i just gotta figure out what 🙃

Is the workflow you posted complete?

or do you also run

docker-compose down

i generally just run airbyte in non detached mode.

so i just kill the process

and then start again

(unless i need to clear out airbyte docker volumes)

I just ran into this too

how did you fix this charles?

i think it's restarting docker that fix this for me.

i don't think ./gradlew clean did it in this cas.e

I had to restart my computer