Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Guard against the absence of the run_start property #7267

Closed
mantid-builder opened this issue Jan 24, 2013 · 1 comment
Closed

Guard against the absence of the run_start property #7267

mantid-builder opened this issue Jan 24, 2013 · 1 comment
Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release.
Milestone
Release 2.4

Comments

@mantid-builder
Copy link
Collaborator

Original Reporter: Russell Taylor

The LogManager::startTime() method throws an (undocumented) exception if the run_start (and the start_time) property is missing. With a 'normally' loaded file it's always (I think) there, but it's conceivable that it isn't with a live data stream.

This mainly shows up as a problem when trying to view the sample logs, if there are any time series property logs there. The relevant method is MantidUI::importNumSeriesLog.
@mantid-builder
Copy link
Collaborator Author

This issue was originally trac ticket 6421

@mantid-builder mantid-builder added High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Mantid labels Jun 3, 2015
@mantid-builder mantid-builder added this to the Release 2.4 milestone Jun 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release.
Projects
None yet
Milestone
Release 2.4
Development

No branches or pull requests
1 participant
@mantid-builder