You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See #3600 for more details. This spike should give us a path forward to getting the run_result data if threads are killed due to --fail-fast or keyboard interrupts.
Describe alternatives you've considered
No response
Who will this benefit?
No response
Are you interested in contributing this feature?
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
Spike: Better handling run_results in threading
[CT-591] Spike: Better handling run_results in threading
May 2, 2022
This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please remove the stale label or comment on the issue, or it will be closed in 7 days.
Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest; add a comment to notify the maintainers.
This would be very useful especially in case when database close connection for loading data but you have a large number of models running by dbt that doesn't fully finished and takes a lot of time.
Is this your first time opening an issue?
Describe the Feature
See #3600 for more details. This spike should give us a path forward to getting the run_result data if threads are killed due to --fail-fast or keyboard interrupts.
Describe alternatives you've considered
No response
Who will this benefit?
No response
Are you interested in contributing this feature?
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: