View Issue Details

IDProjectCategoryView StatusLast Update
0009184Talermerchant backendpublic2024-09-17 14:29
ReporterFlorian Dold Assigned ToChristian Grothoff Resolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Target Version0.14Fixed in Version0.14 
Summary0009184: merchant's /private/kyc returns status 204 despite zero deposit limit at exchange
Description$ taler-harness run-integrationtests kyc-merchant-deposit

There is clearly a deposit limit configured.

Note that a KYC auth key has *not* been set up in the test yet.

I'm not sure if this is an issue with the exchange (see 0009174) or the merchant.
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

Christian Grothoff

2024-09-12 15:08

manager   ~0023271

Try sleep + loop, seems the KYC data is inserted milliseconds later...

Florian Dold

2024-09-12 17:38

manager   ~0023272

Unfortunately that doesn't seem to help. I've added the loop, but it still only returns 204:

2024-09-12T17:37:42.503Z test-kyc-merchant-deposit.ts INFO requesting GET http://localhost:8083/private/kyc
2024-09-12T17:37:42.504Z test-kyc-merchant-deposit.ts INFO mechant kyc status: 204
2024-09-12T17:37:43.005Z test-kyc-merchant-deposit.ts INFO requesting GET http://localhost:8083/private/kyc
2024-09-12T17:37:43.006Z test-kyc-merchant-deposit.ts INFO mechant kyc status: 204
[...]
2024-09-12T17:38:03.078Z test-kyc-merchant-deposit.ts INFO requesting GET http://localhost:8083/private/kyc
2024-09-12T17:38:03.079Z test-kyc-merchant-deposit.ts INFO mechant kyc status: 204
2024-09-12T17:38:03.580Z test-kyc-merchant-deposit.ts INFO requesting GET http://localhost:8083/private/kyc
2024-09-12T17:38:03.581Z test-kyc-merchant-deposit.ts INFO mechant kyc status: 204

Florian Dold

2024-09-12 17:38

manager   ~0023273

The taler-merchant-kyccheck is running in the background, do I need to explicitly kick it somehow?

Christian Grothoff

2024-09-12 21:29

manager   ~0023278

Nah, that can't be it. I'll check again.

Christian Grothoff

2024-09-13 09:12

manager   ~0023280

Ok , I think the answer is this: the taler-merchant-kyccheck helper hangs *immediately* in the long-polling for /kyc-check, thus NEVER even creates any entry in merchant_kyc table, thus our SQL iterates over zero accounts x exchanges, thus returns 204. This is bad because then the default limits that do apply are also not returned (even though the logic to get them is present).

Solution: have the kyccheck helper do a first pass with a long-poll timeout of zero to ensure we do have a non-empty table in the database. Then we should get a non-204 response.

Christian Grothoff

2024-09-13 18:35

manager   ~0023286

Fixed in 373c5628..6191cf20

Issue History

Date ModifiedUsernameFieldChange
2024-09-11 17:02Florian DoldNew Issue
2024-09-11 17:02Florian DoldStatusnew => assigned
2024-09-11 17:02Florian DoldAssigned To => Christian Grothoff
2024-09-12 15:08Christian GrothoffAssigned ToChristian Grothoff => Florian Dold
2024-09-12 15:08Christian GrothoffNote Added: 0023271
2024-09-12 17:37Florian DoldAssigned ToFlorian Dold => Christian Grothoff
2024-09-12 17:38Florian DoldNote Added: 0023272
2024-09-12 17:38Florian DoldNote Added: 0023273
2024-09-12 21:29Christian GrothoffNote Added: 0023278
2024-09-13 09:12Christian GrothoffNote Added: 0023280
2024-09-13 18:35Christian GrothoffStatusassigned => informing
2024-09-13 18:35Christian GrothoffResolutionopen => fixed
2024-09-13 18:35Christian GrothoffFixed in Version => 0.14
2024-09-13 18:35Christian GrothoffNote Added: 0023286
2024-09-17 14:29Christian GrothoffStatusinforming => closed
2025-03-22 13:09Christian GrothoffCategorymechant backend => merchant backend