ITADN

Kanban board column not deleting.

#11118OpenSuperDarius-git 创建于 8 天前
State: Triageawaiting feedbackUI
S
SuperDarius-gitcommented
### Description Good day I am trying to delete a column from a Kanban board note. It's an empty column, but when I am deleting it, it asks for confirmation, and when I say "Yes" it just doesn't delete it. The column is still there. It does move to the back, though. Please tell me if there are any logs I should post other than the Docker compose logs: ``` `trilium-1 | Slow query took 33ms: INSERT INTO sessions (id, expires, data) VALUES (@id, @expires, @data) ON CONFLICT (id) DO UPDATE SET id = @id, expires = @expires, data = @data trilium-1 | Slow 200 POST /api/login/sync with 56 bytes took 34ms trilium-1 | Sending message to all clients: {"type":"sync-pull-in-progress","lastSyncedPush":89456} trilium-1 | Slow query took 46ms: INSERT OR REPLACE INTO blobs ( blobId, content, dateModified, utcDateModified, textRepresentation ) VALUES (?, ?, ?, ?, ?) trilium-1 | Slow query took 33ms: SELECT 1 FROM entity_changes WHERE changeId = ? trilium-1 | Slow query took 266ms: INSERT OR REPLACE INTO attachments ( attachmentId, ownerId, role, mime, title, isProtected, position, blobId, dateModified, utcDateModified, utcDateScheduledForErasureSince, isDeleted, deleteId ) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) trilium-1 | Slow query took 27ms: SELECT 1 FROM entity_changes WHERE changeId = ? trilium-1 | updated: {blobs: [4BsPdCRSRfBrpnuC2cLX], attachments: [2G3rZ7uSf7o7], attributes: [04572dfc2a6b]}, alreadyUpdated: 0, erased: 0, alreadyErased: 0 trilium-1 | Slow 204 PUT /api/sync/update?logMarkerId=NO8bbFurAA with 0 bytes took 428ms trilium-1 | 200 GET /api/sync/changed?instanceId=lm7LaxrVNVVM&lastEntityChangeId=196054&logMarkerId=SZ0KUnaQs3 with 73 bytes took 1ms trilium-1 | 204 POST /api/sync/finished with 0 bytes took 1ms trilium-1 | Slow query took 227ms: SELECT blobs.blobId FROM blobs LEFT JOIN notes ON notes.blobId = blobs.blobId LEFT JOIN attachments ON attachments.blobId = blobs.blobId LEFT JOIN revisions ON revisions.blobId = blobs.blobId WHERE notes.noteId IS NULL AND attachments.attachmentId IS NULL AND revisions.revisionId IS NULL trilium-1 | Erased unused blobs: ["6dxw7hvPLgTy8bEMS0JY"] trilium-1 | Content hash computation took 225ms trilium-1 | Slow 200 GET /api/sync/check with 14012 bytes took 461ms trilium-1 | 200 GET /api/health-check with 15 bytes took 0ms trilium-1 | 200 GET /api/health-check with 15 bytes took 1ms trilium-1 | 304 GET /api/setup/status with 155 bytes took 0ms trilium-1 | 200 POST /api/login/sync with 56 bytes took 2ms trilium-1 | 200 GET /api/sync/changed?instanceId=lm7LaxrVNVVM&lastEntityChangeId=196057&logMarkerId=fcNAoC94Kz with 73 bytes took 1ms trilium-1 | 204 POST /api/sync/finished with 0 bytes took 0ms trilium-1 | 304 GET /api/sync/check with 14012 bytes took 4ms trilium-1 | 200 GET /api/health-check with 15 bytes took 1ms trilium-1 | 200 GET /api/health-check with 15 bytes took 1ms trilium-1 | 304 GET /api/setup/status with 155 bytes took 0ms trilium-1 | 200 POST /api/login/sync with 56 bytes took 1ms trilium-1 | Sending message to all clients: {"type":"sync-pull-in-progress","lastSyncedPush":89456} trilium-1 | updated: {blobs: [4BsPdCRSRfBrpnuC2cLX], attachments: [2G3rZ7uSf7o7], attributes: [04572dfc2a6b]}, alreadyUpdated: 0, erased: 0, alreadyErased: 0 trilium-1 | 204 PUT /api/sync/update?logMarkerId=WsQsxjt7TI with 0 bytes took 3ms trilium-1 | 200 GET /api/sync/changed?instanceId=lm7LaxrVNVVM&lastEntityChangeId=196057&logMarkerId=InkiQpRbng with 73 bytes took 0ms trilium-1 | 204 POST /api/sync/finished with 0 bytes took 0ms trilium-1 | Content hash computation took 93ms trilium-1 | Slow 200 GET /api/sync/check with 14012 bytes took 114ms` ``` I'm not sure if these logs mean anything. I'm sure it is a bug. ### TriliumNext Version 0.105.0 (database: 240, sync protocol: 39) Build: Aug 19, 2026, 8:04:30 PM, revision: a0908a6 ### What operating system are you using? Windows ### What is your setup? Server access only ### Operating System Version Windows 11 ### Error logs trilium-1 | Slow query took 33ms: INSERT INTO sessions (id, expires, data) VALUES (@id, @expires, @data) ON CONFLICT (id) DO UPDATE SET id = @id, expires = @expires, data = @data trilium-1 | Slow 200 POST /api/login/sync with 56 bytes took 34ms trilium-1 | Sending message to all clients: {"type":"sync-pull-in-progress","lastSyncedPush":89456} trilium-1 | Slow query took 46ms: INSERT OR REPLACE INTO blobs ( blobId, content, dateModified, utcDateModified, textRepresentation ) VALUES (?, ?, ?, ?, ?) trilium-1 | Slow query took 33ms: SELECT 1 FROM entity_changes WHERE changeId = ? trilium-1 | Slow query took 266ms: INSERT OR REPLACE INTO attachments ( attachmentId, ownerId, role, mime, title, isProtected, position, blobId, dateModified, utcDateModified, utcDateScheduledForErasureSince, isDeleted, deleteId ) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) trilium-1 | Slow query took 27ms: SELECT 1 FROM entity_changes WHERE changeId = ? trilium-1 | updated: {blobs: [4BsPdCRSRfBrpnuC2cLX], attachments: [2G3rZ7uSf7o7], attributes: [04572dfc2a6b]}, alreadyUpdated: 0, erased: 0, alreadyErased: 0 trilium-1 | Slow 204 PUT /api/sync/update?logMarkerId=NO8bbFurAA with 0 bytes took 428ms trilium-1 | 200 GET /api/sync/changed?instanceId=lm7LaxrVNVVM&lastEntityChangeId=196054&logMarkerId=SZ0KUnaQs3 with 73 bytes took 1ms trilium-1 | 204 POST /api/sync/finished with 0 bytes took 1ms trilium-1 | Slow query took 227ms: SELECT blobs.blobId FROM blobs LEFT JOIN notes ON notes.blobId = blobs.blobId LEFT JOIN attachments ON attachments.blobId = blobs.blobId LEFT JOIN revisions ON revisions.blobId = blobs.blobId WHERE notes.noteId IS NULL AND attachments.attachmentId IS NULL AND revisions.revisionId IS NULL trilium-1 | Erased unused blobs: ["6dxw7hvPLgTy8bEMS0JY"] trilium-1 | Content hash computation took 225ms trilium-1 | Slow 200 GET /api/sync/check with 14012 bytes took 461ms trilium-1 | 200 GET /api/health-check with 15 bytes took 0ms trilium-1 | 200 GET /api/health-check with 15 bytes took 1ms trilium-1 | 304 GET /api/setup/status with 155 bytes took 0ms trilium-1 | 200 POST /api/login/sync with 56 bytes took 2ms trilium-1 | 200 GET /api/sync/changed?instanceId=lm7LaxrVNVVM&lastEntityChangeId=196057&logMarkerId=fcNAoC94Kz with 73 bytes took 1ms trilium-1 | 204 POST /api/sync/finished with 0 bytes took 0ms trilium-1 | 304 GET /api/sync/check with 14012 bytes took 4ms trilium-1 | 200 GET /api/health-check with 15 bytes took 1ms trilium-1 | 200 GET /api/health-check with 15 bytes took 1ms trilium-1 | 304 GET /api/setup/status with 155 bytes took 0ms trilium-1 | 200 POST /api/login/sync with 56 bytes took 1ms trilium-1 | Sending message to all clients: {"type":"sync-pull-in-progress","lastSyncedPush":89456} trilium-1 | updated: {blobs: [4BsPdCRSRfBrpnuC2cLX], attachments: [2G3rZ7uSf7o7], attributes: [04572dfc2a6b]}, alreadyUpdated: 0, erased: 0, alreadyErased: 0 trilium-1 | 204 PUT /api/sync/update?logMarkerId=WsQsxjt7TI with 0 bytes took 3ms trilium-1 | 200 GET /api/sync/changed?instanceId=lm7LaxrVNVVM&lastEntityChangeId=196057&logMarkerId=InkiQpRbng with 73 bytes took 0ms trilium-1 | 204 POST /api/sync/finished with 0 bytes took 0ms trilium-1 | Content hash computation took 93ms trilium-1 | Slow 200 GET /api/sync/check with 14012 bytes took 114ms
3 条评论