Skip to content

Integrate Ruleset usage into screener server #2394

Integrate Ruleset usage into screener server

Integrate Ruleset usage into screener server #2394

Triggered via pull request September 12, 2023 16:04
Status Failure
Total duration 4m 50s
Artifacts

build-and-test-e2e.yml

on: pull_request
build-and-test-e2e
4m 41s
build-and-test-e2e
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
build-and-test-e2e
Module '"../apiCalls"' declares 'MisttrackData' locally, but it is not exported.
build-and-test-e2e
Argument of type '{ call: "TRM_SCREENING_ADDRESSES"; threshold: (data: TrmData) => boolean; action: { type: "Rejection"; reason: string; }; }' is not assignable to parameter of type 'RuleParams<"TRM_SCREENING_ADDRESSES">'.
build-and-test-e2e
Property 'risk' does not exist on type 'TrmData'.
build-and-test-e2e
Property 'risk' does not exist on type 'TrmData'.
build-and-test-e2e
Type '{ type: "Delay"; timeSeconds: number; }' is not assignable to type 'Rejection | DelayAction'.
build-and-test-e2e
Argument of type '{ call: "MISTTRACK_ADDRESS_RISK_SCORE"; threshold: (data: MisttrackData) => boolean; action: { type: "Rejection"; reason: string; }; }' is not assignable to parameter of type 'RuleParams<"MISTTRACK_ADDRESS_RISK_SCORE">'.
build-and-test-e2e
Argument of type 'Rule<"TRM_SCREENING_ADDRESSES">' is not assignable to parameter of type 'RuleParams<"TRM_SCREENING_ADDRESSES">'.
build-and-test-e2e
Argument of type 'Rule<"TRM_SCREENING_ADDRESSES">' is not assignable to parameter of type 'RuleParams<"TRM_SCREENING_ADDRESSES">'.
build-and-test-e2e
Argument of type 'Rule<"MISTTRACK_ADDRESS_RISK_SCORE">' is not assignable to parameter of type 'RuleParams<"MISTTRACK_ADDRESS_RISK_SCORE">'.
build-and-test-e2e
Argument of type 'DepositRequest' is not assignable to parameter of type 'ScreeningDepositRequest'.
build-and-test-e2e
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/