fix: Ignore ipynb files during apply#6151
Conversation
ffe3242 to
fa8ba56
Compare
|
@saipuneet357 if you see discussion on #5177 (comment) The problem is actually with ipynb_checkpoints created in nestead directories as well. When we work inside a JupyterLab workbench and edit .py files (like your Feast feature definitions) in any subdirectory, Jupyter creates .ipynb_checkpoints/ in that subdirectory with checkpoint copies of your .py files. Those checkpoint .py files contain the same Feast object definitions, so feast apply finds and that cause issues. Fix also needs: |
fa8ba56 to
5e20ccb
Compare
|
@ntkathole Thanks for the clarification, it really helped me out! I added to the ignore paths, and tested it out after editing a feast definition on jupyterlab in a subdirectory, and it no longer fails. I guess we can also remove |
f7db7e7 to
ebf7ef8
Compare
Signed-off-by: Saipuneet Munikuntla <[email protected]>
… subdirectories during feast apply Signed-off-by: Saipuneet Munikuntla <[email protected]>
Signed-off-by: Saipuneet Munikuntla <[email protected]>
… name inside subdirectories Signed-off-by: Saipuneet Munikuntla <[email protected]>
…rectories Signed-off-by: Saipuneet Munikuntla <[email protected]>
ebf7ef8 to
7064d1e
Compare
|
@saipuneet357 please fix the tests |
Signed-off-by: Saipuneet Munikuntla <[email protected]>
What this PR does / why we need it:
Ignore Jupyter Notebook Files when we run feast apply
Which issue(s) this PR fixes:
Fixes #5145
Checks
git commit -s)Testing Strategy
Misc
5 of the integration tests are failing due to creating a new spark environment for testing in the functions:
Now these tests are failing even without the change though. I'll take a look if something is wrong with the test or my environment.