Skip to content

fix: fixed bug with rollout when starting with 100 instead of 0 #3754

fix: fixed bug with rollout when starting with 100 instead of 0

fix: fixed bug with rollout when starting with 100 instead of 0 #3754

Triggered via pull request December 2, 2024 20:18
Status Failure
Total duration 1m 38s
Artifacts

nx-affected-test.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

1 error and 11 warnings
build (20.x)
Process completed with exit code 1.
build (20.x)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build (20.x): lib/shared/bucketing/__tests__/bucketing.test.ts#L1221
Forbidden non-null assertion
build (20.x): lib/shared/bucketing/src/segmentation.ts#L31
Unexpected any. Specify a different type
build (20.x): lib/shared/bucketing/src/segmentation.ts#L87
Unexpected any. Specify a different type
build (20.x): lib/shared/bucketing/src/segmentation.ts#L100
Unexpected any. Specify a different type
build (20.x): sdk/nextjs/src/client/internal/useRerenderOnVariableChange.ts#L5
'_' is assigned a value but never used
build (20.x): sdk/nextjs/src/client/renderIfEnabled.tsx#L6
Unexpected any. Specify a different type
build (20.x): sdk/nextjs/src/common/serializeUser.ts#L3
Unexpected any. Specify a different type
build (20.x): sdk/nextjs/src/common/serializeUser.ts#L3
Unexpected any. Specify a different type
build (20.x): sdk/nextjs/src/pages/bucketing.ts#L47
Forbidden non-null assertion