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
{{ message }}
This repository has been archived by the owner on Jul 19, 2018. It is now read-only.
We know that some validation can not be done immediately when recording a command (e.g. tracking image layout). So some of them are deferred at submission time. However, if we hit an error (or a warning) there, then we lose the context from where the offending command comes.
So, a nice (and non-intrusive) feature that would be very practical is if, for such deferred validation, information about the call stack could be saved (at record time) and displayed along with messages. This should be possible to implement at least on some platforms.
The text was updated successfully, but these errors were encountered:
We know that some validation can not be done immediately when recording a command (e.g. tracking image layout). So some of them are deferred at submission time. However, if we hit an error (or a warning) there, then we lose the context from where the offending command comes.
So, a nice (and non-intrusive) feature that would be very practical is if, for such deferred validation, information about the call stack could be saved (at record time) and displayed along with messages. This should be possible to implement at least on some platforms.
The text was updated successfully, but these errors were encountered: