Skip to content

feat: add internal BigSegmentStoreWrapper with caching and status polling #2320

feat: add internal BigSegmentStoreWrapper with caching and status polling

feat: add internal BigSegmentStoreWrapper with caching and status polling #2320

Triggered via pull request June 2, 2026 17:38
Status Success
Total duration 2m 52s
Artifacts

cpp-linter.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 13 warnings
/libs/server-sdk-redis-source/src/redis_big_segment_store.cpp:1:10 [clang-diagnostic-error]: /libs/server-sdk-redis-source/src/redis_big_segment_store.cpp#L1
'launchdarkly/server_side/integrations/redis/redis_big_segment_store.hpp' file not found
/libs/server-sdk-dynamodb-source/src/dynamodb_big_segment_store.cpp:1:10 [clang-diagnostic-error]: /libs/server-sdk-dynamodb-source/src/dynamodb_big_segment_store.cpp#L1
'launchdarkly/server_side/integrations/dynamodb/dynamodb_big_segment_store.hpp' file not found
cpp-linter
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, MarkusJx/install-boost@3039450bb3dd2e8630d1cf10ec39cb1da3054bbd. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
/libs/internal/include/launchdarkly/async/promise.hpp:221:40 [bugprone-move-forwarding-reference]: /libs/internal/include/launchdarkly/async/promise.hpp#L221
forwarding reference passed to std::move(), which may unexpectedly cause lvalues to be moved; use std::forward() instead
/libs/internal/include/launchdarkly/async/promise.hpp:197:29 [bugprone-move-forwarding-reference]: /libs/internal/include/launchdarkly/async/promise.hpp#L197
forwarding reference passed to std::move(), which may unexpectedly cause lvalues to be moved; use std::forward() instead
/libs/internal/include/launchdarkly/async/promise.hpp:180:37 [bugprone-move-forwarding-reference]: /libs/internal/include/launchdarkly/async/promise.hpp#L180
forwarding reference passed to std::move(), which may unexpectedly cause lvalues to be moved; use std::forward() instead
/libs/internal/include/launchdarkly/async/promise.hpp:167:62 [performance-unnecessary-value-param]: /libs/internal/include/launchdarkly/async/promise.hpp#L167
the parameter 'executor' is copied for each invocation but only used as a const reference; consider making it a const reference
/libs/internal/include/launchdarkly/async/promise.hpp:39:12 [cppcoreguidelines-special-member-functions]: /libs/internal/include/launchdarkly/async/promise.hpp#L39
class 'Base' defines a default destructor but does not define a copy constructor, a copy assignment operator, a move constructor or a move assignment operator
/libs/internal/include/launchdarkly/async/promise.hpp:35:7 [cppcoreguidelines-special-member-functions]: /libs/internal/include/launchdarkly/async/promise.hpp#L35
class 'Continuation' defines a move constructor and a move assignment operator but does not define a destructor, a copy constructor or a copy assignment operator
cpp-linter
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0FhUfagAAAAD9Jf83lQ83Qb/xMI/qcUA9UEhMMzBFREdFMDQxMwBFZGdl
cpp-linter
Failed to restore: Cache service responded with 400