| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
LGTM, though we might need a fallback in case microseconds appear again.
We should check with the product team to see what they are committing to.
Sorry, something went wrong.
|
Would a try except work better then or should we just wait? try: return ms except ValueError: return ns |
Sorry, something went wrong.
|
I'm emailing the team to check. |
Sorry, something went wrong.
|
I never got a response from the folks I've contacted before on the RuntimeConfig team. @mgannholm Can you comment on this? |
Sorry, something went wrong.
|
Okay, I got confirmation from Victor on the RuntimeConfig team that "it might change from platform to platform". We need to be able to handle both. Yes, try-except would be a good way to do it. Alternatively, I believe we have places (in BigQuery, maybe?) where we try to parse the string a little bit to see how many digits we have before trying to parse. |
Sorry, something went wrong.
Sorry, something went wrong.
|
@tswast PTAL at your convenience. |
Sorry, something went wrong.
| 'name': VARIABLE_PATH, | ||
| 'value': 'bXktdmFyaWFibGUtdmFsdWU=', # base64 my-variable-value | ||
| 'updateTime': '2016-04-14T21:21:54.5000Z', | ||
| 'updateTime': '2016-04-14T21:21:54.123456789Z', |
|
going to merge this and diff from this in the new PR. (I have it written already) |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
@tswast Thanks for the hint.
Closes #4807