-
Notifications
You must be signed in to change notification settings - Fork 658
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Agent Get Pending Message #4106
Agent Get Pending Message #4106
Conversation
Signed-off-by: Future Outlier <[email protected]>
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4106 +/- ##
==========================================
+ Coverage 59.44% 59.90% +0.46%
==========================================
Files 637 568 -69
Lines 54262 40945 -13317
==========================================
- Hits 32254 24527 -7727
+ Misses 19467 14041 -5426
+ Partials 2541 2377 -164
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
Signed-off-by: Future Outlier <[email protected]>
Signed-off-by: Future Outlier <[email protected]>
Signed-off-by: Future Outlier <[email protected]>
Signed-off-by: Future Outlier <[email protected]>
Signed-off-by: Future Outlier <[email protected]>
Signed-off-by: Future Outlier <[email protected]>
Signed-off-by: Future Outlier <[email protected]>
Description.
Two months ago, I introduced the Databricks agent service.
Currently, job statuses progress from "pending" to "running" to "succeeded".
To enhance user experience, @pingsutw, @kumare3, and I propose enriching the "pending" status with additional information for Databricks API and future implementations.
This update will relay detailed messages to the Flyte console to keep users informed.
Checks
Screenshots
Follow-up issue
#4115
flyteorg/flytekit#1834
#3936