-
Notifications
You must be signed in to change notification settings - Fork 9
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.
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
Non-fatal error "bad datetime conversion" messages #71
Comments
Some dates are not converting. Could make the error more detailed error message, and not fatal. If there is no conversion, it defaults to to NOW: try:
beginDateTime = dateutil.parser.parse(beginDateTime)
endDateTime = dateutil.parser.parse(endDateTime)
except Exception as inst:
logging.error('bad datetime conversion')
#TimeInterval
if beginDateTime is None:
beginDateTime = datetime.datetime.now().strftime("%Y-%m-%dT%H:%M:%S")
if endDateTime is None:
endDateTime = datetime.datetime.now().strftime("%Y-%m-%dT%H:%M:%S") |
Thanks, @valentinedwv. We haven't looked into this; at this point we just wanted to capture the issue before we forget. Thanks for digging into it! Like @lsetiawan said, the error is not fatal. |
@lsetiawan, I'm not sure why you added the section "Links to relevant WOFpy resources and documentation" on this issue. I don't think those links discuss anything specific to this issue. We may move that section out of WOFpyODM2LBRtest_installation_notes.md later on, but for now they're still there for reference. Unless I've missed something, please go ahead and delete that section from your original issue text. Thanks. FYI, I'm going to rename the issue to make it more specific. |
As of the latest WOFpy (cf12e13) This is error is not there anymore. I'm closing unless it reappears. |
The text was updated successfully, but these errors were encountered: