Skip to content

Fix/lazy tensorflow import - #152

Open
hanzalaareeb wants to merge 3 commits into
google:mainfrom
hanzalaareeb:fix/lazy-tensorflow-import
Open

hanzalaareeb wants to merge 3 commits into
google:mainfrom
hanzalaareeb:fix/lazy-tensorflow-import

Conversation

@hanzalaareeb

@hanzalaareeb hanzalaareeb commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

Fixes #151
This PR removes eager TensorFlow initialization from shared pipeline import paths.

@hanzalaareeb
hanzalaareeb force-pushed the fix/lazy-tensorflow-import branch from 7f00c93 to 4c8c632 Compare September 18, 2026 14:00
@hanzalaareeb

Copy link
Copy Markdown
Contributor Author

Hi @ryan112358 — gentle ping on this small fix. I’ve rebased it onto current main and added a regression test confirming that non-TFRecord pipeline imports do not load TensorFlow. Current main still eagerly imports TensorFlow in these paths, and CI is green. Could you confirm whether this direction is still wanted? Happy to adjust anything needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Lazy-load TensorFlow for TFRecord-specific pipeline paths

1 participant