View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010682 | Taler | merchant backend | public | 2025-11-28 15:23 | 2025-11-28 20:34 |
| Reporter | Bohdan | Assigned To | Bohdan | ||
| Priority | immediate | Severity | block | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 1.2 | ||||
| Target Version | 1.3 | Fixed in Version | 1.3 | ||
| Summary | 0010682: Within specific versions, merchant can be not upgraded automatically (from v1.1.0 or earlier to 1.2.0+) | ||||
| Description | 2025-11-28 14:14:36.320 UTC [73909] taler-merchant-httpd@taler-merchant ERROR: function encode(jsonb, unknown) does not exist at character 167 2025-11-28 14:14:36.320 UTC [73909] taler-merchant-httpd@taler-merchant HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2025-11-28 14:14:36.320 UTC [73909] taler-merchant-httpd@taler-merchant QUERY: resolved_body := replace_placeholder(resolved_body, 'old_description_i18n', encode(OLD.description_i18n, 'escape')) 2025-11-28 14:14:36.320 UTC [73909] taler-merchant-httpd@taler-merchant CONTEXT: PL/pgSQL function handle_inventory_changes() line 117 at assignment 2025-11-28 14:14:36.320 UTC [73909] taler-merchant-httpd@taler-merchant STATEMENT: UPDATE merchant_inventory SET image_hash = CASE WHEN (image IS NULL) OR (image = '') THEN NULL ELSE encode( digest( convert_to(image, 'UTF8'), 'sha256' ), 'hex' ) END; root@debian-instalation-tutorial:~# taler-merchant-httpd --version taler-merchant-httpd v1.2.2-git-ad2aa9a The good thing is that I figured out that migration from the old to the new version really works, that bug can be closed, but some fallback to the old version if the migration fails might be a good thing to have | ||||
| Steps To Reproduce | IDK, have my database, and run taler-merchant-dbconfig and it fails... | ||||
| Tags | No tags attached. | ||||
|
|
Uh, ty for takinkg care! Question, before I break my installation: This would affect migration only from v1.2.1 to v1.2.2, both from trixie-testing, or (likely, I guess) also from older versions (like 1.2.0 and before) to v1.2.2? |
|
|
This affects only the merchants that are upgrading from less or 1.1.0 to 1.2.0 |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-11-28 15:23 | Bohdan | New Issue | |
| 2025-11-28 15:23 | Bohdan | Status | new => assigned |
| 2025-11-28 15:23 | Bohdan | Assigned To | => Bohdan |
| 2025-11-28 16:03 | vecirex | Note Added: 0026659 | |
| 2025-11-28 16:41 | vecirex | Relationship added | child of 0010630 |
| 2025-11-28 18:38 | Christian Grothoff | Target Version | git (master) => 1.3 |
| 2025-11-28 19:04 | Bohdan | Note Added: 0026671 | |
| 2025-11-28 19:06 | Bohdan | Summary | Well I did a shitty job, and migration from previous to new version doesn't work :) => Within specific versions, merchant can be not upgraded automatically |
| 2025-11-28 19:07 | Bohdan | Summary | Within specific versions, merchant can be not upgraded automatically => Within specific versions, merchant can be not upgraded automatically (>=v1.1.0 to 1.2.0+) |
| 2025-11-28 19:08 | Bohdan | Summary | Within specific versions, merchant can be not upgraded automatically (>=v1.1.0 to 1.2.0+) => Within specific versions, merchant can be not upgraded automatically (from v1.1.0 or earlier to 1.2.0+) |
| 2025-11-28 20:20 | Bohdan | Status | assigned => resolved |
| 2025-11-28 20:20 | Bohdan | Resolution | open => fixed |
| 2025-11-28 20:20 | Bohdan | Fixed in Version | => 1.2 |
| 2025-11-28 20:34 | Christian Grothoff | Fixed in Version | 1.2 => 1.3 |
