So i’ve made a few updates to the code and when ru...
# troubleshoot
q
So i’ve made a few updates to the code and when running ./gradlew build I run into a failed test case for spark lineage in the metadata-io test cases. I never touched that code, is it possible that slipped through a recent PR?
m
The Spark lineage test is flaky unfortunately. Not your fault. We plan to fix it soon.
q
Oh good so it’s not something I did
Admittedly dumb question because I haven’t used grade before. Failing that test won’t prevent a usable build will it? I haven’t managed to catch any output that indicated a compiled file anywhere that would be suitable to mount to docker compose
m
This might be a useful resource for you: https://datahubproject.io/docs/docker/development/
q
So if I understand the docker compose files correctly I just need to build the specific binary I’m interested in, (play front end in this case) and then run the dev.sh script. Yes?
At least for testing purposes
Obviously for deployment I’ll have to actually build the docker image to deploy
m
Right. You can skip the tests during the build with
../gradlew :module_name:build -x test
q
Something else i’m running in to. The web react project is failing on eslint. datahub-web-react/src/app/entity/glossaryTerm/profile/AddRelatedTermsModal.tsx 166:29 error JSX props should not use functions react/jsx-no-bind
I didn’t modify any of the typescript that I know of \
Seems like ./gradlew datahub frontendbuild -x yarnTest -x yarnLint did the trick. Oddly replacing build with dist seems to completely ignore the yarnTest and lint directives