Fix module loading bug in instance tracker class #1902
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
TL;DR
This PR fixes an issue reported here where
pyflyte
and other executables were trying to be loaded by thetracker.py
module when finding trackable instances.Type
Are all requirements met?
[ ] Smoke tested[ ] Unit tests added(will be added subsequently)[ ] Code documentation added[ ] Any pending items have an associated IssueComplete description
The eager workflow PR introduced a bug that caused breakages in
@dynamic
workflows and agents. The underlying reason is that eager workflows need to be able to load task/dynamic/workflow functions asInstanceTrackingMeta
instances so that it can execute them viaFlyteRemote
. The issue is that, before1579
,InstanceTrackingMeta
did not support loading entities defined in the__main__
module.This PR handles a module loading error that was being raised because the
tracker
module was trying to load thepyflyte
and otherpyflyte-*
executables.Tracking Issue
flyteorg/flyte#4245
Follow-up issue
#1892