| .. |
|
assets
|
bbc5ccb982
Library Upload Doesn't Show New File Until Page Reload ([#704](https://github.com/maziggy/bambuddy/issues/704)) — After uploading a file in the Library file manager, the file list didn't update until the user reloaded the browser. The upload endpoint used `db.flush()` instead of `db.commit()`, so the new row was only written to the database *after* the response was sent to the client. The frontend immediately refetched the file list upon receiving the response, but a new database session couldn't see the uncommitted row — resulting in stale data. Fixed by committing before the response is returned. Also fixed the same race condition in folder create, folder update, and file update endpoints. Reported by @shadowjig.
|
2 months ago |
|
icons
|
7eb82f58fa
Updated CHANGELOG
|
2 months ago |
|
img
|
7eb82f58fa
Updated CHANGELOG
|
2 months ago |
|
index.html
|
bbc5ccb982
Library Upload Doesn't Show New File Until Page Reload ([#704](https://github.com/maziggy/bambuddy/issues/704)) — After uploading a file in the Library file manager, the file list didn't update until the user reloaded the browser. The upload endpoint used `db.flush()` instead of `db.commit()`, so the new row was only written to the database *after* the response was sent to the client. The frontend immediately refetched the file list upon receiving the response, but a new database session couldn't see the uncommitted row — resulting in stale data. Fixed by committing before the response is returned. Also fixed the same race condition in folder create, folder update, and file update endpoints. Reported by @shadowjig.
|
2 months ago |
|
manifest.json
|
7eb82f58fa
Updated CHANGELOG
|
2 months ago |
|
spoolbuddy_logo_dark.png
|
7eb82f58fa
Updated CHANGELOG
|
2 months ago |
|
sw.js
|
7eb82f58fa
Updated CHANGELOG
|
2 months ago |
|
vite.svg
|
7eb82f58fa
Updated CHANGELOG
|
2 months ago |
maziggy
bbc5ccb982
Library Upload Doesn't Show New File Until Page Reload ([#704](https://github.com/maziggy/bambuddy/issues/704)) — After uploading a file in the Library file manager, the file list didn't update until the user reloaded the browser. The upload endpoint used `db.flush()` instead of `db.commit()`, so the new row was only written to the database *after* the response was sent to the client. The frontend immediately refetched the file list upon receiving the response, but a new database session couldn't see the uncommitted row — resulting in stale data. Fixed by committing before the response is returned. Also fixed the same race condition in folder create, folder update, and file update endpoints. Reported by @shadowjig.
