Page MenuHomeElementl

include original user code stack trace in scheduler/sensor/partition user code errors
AbandonedPublicDraft

Authored by dgibson on Tue, Apr 13, 3:05 AM.

Details

Reviewers
prha
Summary

This seems better than the generic 'there was an error loading the run_config fn' without any indication of what that error was. (The downside is it doesn't tell you which funtion had the problem, but that is still clear from the stack trace I think?)

Test Plan

BK

Diff Detail

Repository
R1 dagster
Branch
nomoretodayatmidnight (branched from master)
Lint
Lint Passed
Unit
No Test Coverage

Event Timeline

Harbormaster returned this revision to the author for changes because remote builds failed.Tue, Apr 13, 3:26 AM
Harbormaster failed remote builds in B28753: Diff 35293!