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.

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

BUG: consistent return for value of uninitialized data #750

Merged
merged 1 commit into from
Oct 3, 2017

Conversation

pieper
Copy link
Member

@pieper pieper commented Sep 29, 2017

When a dataset cannot be initialized, log an error
and return an empty string for consistency.

Also do not cache value (means that a future call may
succeed with correct value if data file becomes available)

Fixes #749

@jcfr
Copy link
Member

jcfr commented Sep 29, 2017

👍

Before integrating, would it be possible to add a comment explaining what is the value 00ff,eeee ?

When a dataset cannot be initialized, log an error
and return an empty string for consistency.

Also do not cache value (means that a future call may
succeed with correct value if data file becomes available)

Fixes commontk#749
@pieper pieper force-pushed the 749-tag-cache-on-bad-data branch from 58fa2a2 to 295dbfc Compare September 30, 2017 21:04
@pieper
Copy link
Member Author

pieper commented Sep 30, 2017

Thanks for the review 👍

I updated the comment. The exact value 00ff,eeee is arbitrary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants