From cc7369d9d71b72b97929a2f1387c4f006bab5832 Mon Sep 17 00:00:00 2001
From: KernelDeimos <7225168+KernelDeimos@users.noreply.github.com>
Date: Tue, 4 Nov 2025 21:01:50 -0500
Subject: [PATCH] fix: also check this.entry.id when checking mysql_id

There is a case where this.entry.id has a value in FSNodeContext while
this.mysql_id does not. I was under the impression that this state was
not possibole. The cause of this eludes me. This commit does not correct
the root cause - it only adds a workaround to this issue by falling back
to this.entry.id if this.mysql_id is `undefined`.
---
 src/backend/src/filesystem/FSNodeContext.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/backend/src/filesystem/FSNodeContext.js b/src/backend/src/filesystem/FSNodeContext.js
index 709714fe2..c8436e065 100644
--- a/src/backend/src/filesystem/FSNodeContext.js
+++ b/src/backend/src/filesystem/FSNodeContext.js
@@ -627,7 +627,7 @@ module.exports = class FSNodeContext {
 
         if ( key === 'mysql-id' ) {
             await this.fetchEntry();
-            return this.mysql_id;
+            return this.mysql_id ?? this.entry.id;
         }
 
         if ( key === 'owner' ) {