View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0037387 | mantisbt | bugtracker | public | 2026-09-13 15:11 | 2026-09-13 16:54 |
| Reporter | vboctor | Assigned To | vboctor | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | assigned | Resolution | open | ||
| Product Version | 2.28.0 | ||||
| Summary | 0037387: Caching doesn't get properly invalidated after write operations | ||||
| Description | Often a write operation involves a read and then write. If a read happens after the write, it often reads from stale cache. The write operations need to always flush the cache to avoid such stale reads. This often affects APIs more than web UI. | ||||
| Tags | No tags attached. | ||||