-
Notifications
You must be signed in to change notification settings - Fork 22
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
Various maintenance updates #136
Merged
Merged
Commits on Nov 1, 2024
-
- Fix a G115 linter warning - Add documentation/comments to all usecase NewABC implementations
Configuration menu - View commit details
-
Copy full SHA for e2f7609 - Browse repository at this point
Copy the full SHA e2f7609View commit details -
Configuration menu - View commit details
-
Copy full SHA for 708761d - Browse repository at this point
Copy the full SHA 708761dView commit details
Commits on Nov 4, 2024
-
Configuration menu - View commit details
-
Copy full SHA for f14275a - Browse repository at this point
Copy the full SHA f14275aView commit details
Commits on Nov 11, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 36f8cc2 - Browse repository at this point
Copy the full SHA 36f8cc2View commit details -
Make DataUpdateHeartbeat event names more consistent
This also allows differentiating between eglpc.DataUpdateHeartbeat and cslpc.DataUpdateHeartbeat events.
Configuration menu - View commit details
-
Copy full SHA for 6f64d63 - Browse repository at this point
Copy the full SHA 6f64d63View commit details -
Make DataUpdateHeartbeat event names more consistent (#141)
This also allows differentiating between eglpc.DataUpdateHeartbeat and cslpc.DataUpdateHeartbeat events. While syncing my branch on dev, I saw #137 and noticed that the DataUpdateHeartbeat events for eg/lpc and cs/lpc used the same identifier which means they can't be differentiated from another over e.g. json-rpc. I also took the liberty of changing the "uclppserver-" identifier to "cs-lpp-" to make it consistent with the other event names.
Configuration menu - View commit details
-
Copy full SHA for bb09c16 - Browse repository at this point
Copy the full SHA bb09c16View commit details
Commits on Nov 18, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 4095577 - Browse repository at this point
Copy the full SHA 4095577View commit details -
Configuration menu - View commit details
-
Copy full SHA for 2ceb1ba - Browse repository at this point
Copy the full SHA 2ceb1baView commit details -
Configuration menu - View commit details
-
Copy full SHA for 99b6519 - Browse repository at this point
Copy the full SHA 99b6519View commit details -
Configuration menu - View commit details
-
Copy full SHA for 76c28c1 - Browse repository at this point
Copy the full SHA 76c28c1View commit details -
Configuration menu - View commit details
-
Copy full SHA for c33ba90 - Browse repository at this point
Copy the full SHA c33ba90View commit details -
Configuration menu - View commit details
-
Copy full SHA for 90a5c1f - Browse repository at this point
Copy the full SHA 90a5c1fView commit details
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.