fix(http): respond with 503 when inverter unavailable at startup#11
Merged
brandon1024 merged 1 commit intomainfrom Apr 5, 2026
Merged
fix(http): respond with 503 when inverter unavailable at startup#11brandon1024 merged 1 commit intomainfrom
brandon1024 merged 1 commit intomainfrom
Conversation
OpenEVT does not have any persistance of any kind. In some situations, whenever the application is restarted for any reason (e.g. upgrades), services that scrape the inverter status can get zero values briefly until OpenEVT has time to talk to the inverter. This can lead to some pretty nasty visualization behaviour (big spikes followed by big corrections). This revision adjusts the web server to respond with a 503 when the status is not yet available, as opposed to returning zeroes. Services that scrape the endpoint should be able to use this to handle the error accordingly, skipping the datapoints rather than plotting zeroes. Improve flag usage strings. Additionally, bump Go to latest release and upgrade dependencies.
07e8074 to
d3da284
Compare
Owner
Author
|
Here's a quick demonstration of the problem. When we restart the container, we briefly get a zero struct: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
OpenEVT does not have any persistance of any kind. In some situations, whenever the application is restarted for any reason (e.g. upgrades), services that scrape the inverter status can get zero values briefly until OpenEVT has time to talk to the inverter. This can lead to some pretty nasty visualization behaviour (big spikes followed by big corrections).
This revision adjusts the web server to respond with a 503 when the status is not yet available, as opposed to returning zeroes. Services that scrape the endpoint should be able to use this to handle the error accordingly, skipping the datapoints rather than plotting zeroes.
Additionally, bump Go to latest release and upgrade dependencies.