| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007394 | Taler | wallet (WebExtension) | public | 2022-10-17 20:00 | 2023-01-26 22:53 |
| Reporter | sebasjm | Assigned To | sebasjm | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | git (master) | ||||
| Target Version | 0.9.1 | Fixed in Version | 0.9.1 | ||
| Summary | 0007394: weird behavior when service worker send a response to webex | ||||
| Description | to reproduce: add 2 exchanges for the same currency https://exchange.taler.ar/ https://exchange-age.taler.ar/ start a withdrawal click edit exchange switch exchange and expect the comparison table wallet-core response with the the fee details { ..., denomFees: {deposit, refresh, refund, withdraw} } which is ok let obj be the response of the operation from wallet-core: 1./* when the service worker receive the response from the wallet obj.result.denomFees.deposit has length 8 2./* service worker prints the content of obj (https://git.taler.net/wallet-core.git/tree/packages/taler-wallet-webextension/src/platform/chrome.ts#n377) 3./* then is sent to webex 4./* webex receives it and print it out (https://git.taler.net/wallet-core.git/tree/packages/taler-wallet-webextension/src/platform/chrome.ts#n314) 5./* obj.result.denomFees.deposit has length 23 it is the same operation since it have the same id. The problem seems to be between 3 and 4 implying that the object get modified after is sent and before is received. But how is modified is consistent with what you would expect from "createTimeline" funciton in wallet-core so maybe the bug is in denomFees is constructed in function "getExchangeDetailedInfo" Maybe shared object somewhere? | ||||
| Tags | No tags attached. | ||||
- Anonymous
