-
Notifications
You must be signed in to change notification settings - Fork 48
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] Wingbits: Warning message in the logs #105
Comments
@shawaj Would you be able to take a look at this? Also, it would be great if you could confirm that the recent updates to Wingbits have been correctly reflected in recent changes to the balena edition. |
@ketilmo sure I'll take a look. When you say the vector service, you mean it's been updated to a new version in later images? |
Thanks @shawaj! And correct. When I rolled back to an earlier deployment, the warning message disappeared. So it's likely been introduced by a recent Vector service update (via apt). |
Same issue as mentioned here https://gitlab.com/wingbits/config/-/merge_requests/22 |
Pulling in latest update (i.e. clicking on deploy with balena) should fix this now. https://gitlab.com/wingbits/config/-/blob/master/vector.yaml?ref_type=heads |
Actually probably need to bump version. I will sort a PR shortly |
Thanks @shawaj, much apprecaited! |
Looks like they are no longer tagging the release upstream, so latest config update is 0.0.5 but there is no tag. @ketilmo are you happy if I just remove the tag based build and use a commit hash instead? For example https://gitlab.com/wingbits/config/-/blob/96cb3ffb4628fbb8a128a02d691ee16bdff7f917/vector.yaml |
That sounds like a good approach, @shawaj! Please go ahead. |
Bump to latest config version Closes: ketilmo#105
Over the last few weeks, a warning message has appeared in the Wingbits service logs. This is likely due to changes in the Vector service, as it appears on both new and old versions of the Wingbits feeder configuration.
This is the warning message:
The feeding seems to work correctly.
The text was updated successfully, but these errors were encountered: