Skip to content

fix: client init state should not regress when data source interrupted #1815

fix: client init state should not regress when data source interrupted

fix: client init state should not regress when data source interrupted #1815

Triggered via pull request September 30, 2024 21:42
Status Success
Total duration 2m 27s
Artifacts

cpp-linter.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
/libs/client-sdk/src/client_impl.cpp:238:51 [bugprone-easily-swappable-parameters]: libs/client-sdk/src/client_impl.cpp#L238
2 adjacent parameters of 'VariationInternal' of convertible types are easily swapped by mistake
/libs/client-sdk/src/client_impl.hpp:31:5 [readability-inconsistent-declaration-parameter-name]: libs/client-sdk/src/client_impl.hpp#L31
function 'launchdarkly::client_side::ClientImpl::ClientImpl' has a definition with different parameter names
/libs/client-sdk/src/client_impl.hpp:102:36 [readability-identifier-length]: libs/client-sdk/src/client_impl.hpp#L102
parameter name 'fn' is too short, expected at least 3 characters
cpp-linter
The following actions use a deprecated Node.js version and will be forced to run on node20: MarkusJx/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/