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

fix bug where no returned reading would cause failure #178

Merged
merged 1 commit into from
Jun 22, 2018

Conversation

edaniszewski
Copy link
Contributor

This PR fixes #176

This fixes the immediate issue, but the behavior of returning None when the SDK indicates that there is no reading available is in question. See the semi-related:

@edaniszewski edaniszewski merged commit 77d32b7 into sdk1.0 Jun 22, 2018
@codecov
Copy link

codecov bot commented Jun 22, 2018

Codecov Report

Merging #178 into sdk1.0 will increase coverage by 0.31%.
The diff coverage is 0%.

Impacted file tree graph

@@            Coverage Diff             @@
##           sdk1.0     #178      +/-   ##
==========================================
+ Coverage   81.11%   81.42%   +0.31%     
==========================================
  Files          44       44              
  Lines        1276     1276              
==========================================
+ Hits         1035     1039       +4     
+ Misses        241      237       -4
Impacted Files Coverage Δ
synse/commands/read.py 96.15% <0%> (+15.38%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 94e77ff...ecace29. Read the comment docs.

@edaniszewski edaniszewski deleted the no-read-err branch June 22, 2018 14:23
edaniszewski added a commit that referenced this pull request Jul 2, 2018
* start to update internal grpc client for sdk1.0 changes

* update internal grpc client handling

* add capabilities route

* update models, update tests

* update plugins route to include metadata and health info

* update plugin registration flow. still needs to be cleaned up, tests need to be updated/added

* add support for service discovery via kubernetes service endpointswith labels

* update deployment configurations, fix bug in unix registration

* update tests for plugin flow changes

* update api docs

* use new synse_grpc package

* more doc updates, fix serialization bug

* user guide docs update

* update user guide docs

* fix bug where no returned reading would cause failure (#178)

* Change read scheme to allow multiple readings of the same type (#181)

* update read scheme to allow multiple readings of the same type from the same device (e.g. a single device might provide multiple voltage readings)

* update api docs

* Fix build args for old docker versions (#183)

* fix build args for old docker version

* update comment

* scan output should have type, not kind (#186)

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

Successfully merging this pull request may close these issues.

None yet

1 participant