Hi, Thank you for your question, I see what you meen.
If I may, I would suggest that we do not try to store nulls anywhere becuse that will result in more pullrequests, checking for nulls in different places. If you could summerize the problem from the user perspective, that you are trying to solve - that usually helps to get more feedback from both users and developers. I.e right now date in UI beeing off for a running paragraph does not appear to me as a problem require immediate fix, allthough I might be wrong. -- Alex On Wed, Dec 23, 2015, 14:28 Jungtaek Lim <[email protected]> wrote: > Hi devs, > > Paragraph seems to show the latest job run info (date, status), and another > run overrides this information. > Confused thing is that another run doesn't override the finished date until > job finished, so while running start date is greater than finished date > which is not intuitive. > > What do you think? Is it intention, or just a bug? > If we agree that we'd be better to set finished date to initial value > (null) when start of the run I'll address it to new issue / pull request. > > Btw, would it be better to store job run history? > Maybe unit is paragraph, since we can run individual paragraph without > running whole notebook. > It is just a idea and I didn't think a way to realize. > > Please share your opinion. > > Thanks, > Jungtaek Lim (HeartSaVioR) > > -- > Name : Jungtaek Lim > Blog : http://medium.com/@heartsavior > Twitter : http://twitter.com/heartsavior > LinkedIn : http://www.linkedin.com/in/heartsavior >
