View Issue Details

IDProjectCategoryView StatusLast Update
0007895Talerexchangepublic2023-08-02 23:23
Reportersebasjm Assigned ToChristian Grothoff  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionwon't fix 
Product Versiongit (master) 
Target Version0.9.3Fixed in Version0.9.3 
Summary0007895: wirewatch request inconming transaction endpoint without waiting
DescriptionExample, this request

$ curl "http://exchange:qwe@bank.localhost:3000/taler-wire-gateway/exchange/history/incoming?delta=1022&start=713660416&long_poll_ms=60000"

have this response

{"incoming_transactions":[{"reserve_pub":"N19234F1B942Z7HD7XEKNZCA9MG291CTEJTPN6BXRT3MN5VESM7G","subject":"N19234F1B942Z7HD7XEKNZCA9MG291CTEJTPN6BXRT3MN5VESM7G","credit_account":"payto://x-taler-bank/bank.localhost:3000/exchange","debit_account":"payto://x-taler-bank/bank.localhost:3000/sebasjm","date":{"t_s":1690906096},"amount":"KUDOS:100","amountValue":100,"row_id":1690906096,"id":1690906096}]}


the next immediate request will be the current $start + $delta and it should be the row_id of the last response, otherwise (for this case) it will request a lot until it reach the current row_id
TagsNo tags attached.

Activities

Christian Grothoff

2023-08-02 23:23

manager   ~0020397

row IDs should be small and somewhat contiguous. I don't think we should at this point worry about being efficient if there are huge gaps.

Issue History

Date Modified Username Field Change
2023-08-01 20:43 sebasjm New Issue
2023-08-01 20:43 sebasjm Status new => assigned
2023-08-01 20:43 sebasjm Assigned To => Christian Grothoff
2023-08-02 23:23 Christian Grothoff Status assigned => resolved
2023-08-02 23:23 Christian Grothoff Resolution open => won't fix
2023-08-02 23:23 Christian Grothoff Fixed in Version => 0.9.3
2023-08-02 23:23 Christian Grothoff Note Added: 0020397
2023-08-02 23:23 Christian Grothoff Status resolved => closed
2023-08-02 23:23 Christian Grothoff Target Version 1.0 => 0.9.3