-
Notifications
You must be signed in to change notification settings - Fork 49
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
generateEndpointConfigBase64Payload needs to use generateEndpointConfigClientId #532
Conversation
This is still draft... is it ready for review? |
validator/src/main/java/com/google/daq/mqtt/sequencer/sequences/BlobsetSequences.java
Show resolved
Hide resolved
@@ -99,7 +99,8 @@ public void endpoint_config_connection_success_reconnect() { | |||
return phase != null | |||
&& phase.equals(BlobPhase.FINAL) | |||
&& stateStatus.category.equals(SYSTEM_CONFIG_APPLY) | |||
&& stateStatus.level == Level.NOTICE.value(); | |||
&& stateStatus.level == Level.NOTICE.value() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I meant that the status in the blob block was as intended. The system status is not always indicative of what the blob is doing... the specific problem here was that the blob was reporting an error that was not checked by this condition -- this change doesn't fix that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed this to check blob state message for success.
Note this means that pubber was potentially a false positive on restart?