loadSecretFileSync uses the unresolved filePath instead of the resolvedPath. Secret files referenced by relative paths or symlinks are silently not found. Users who configure secret files may have them silently ignored with zero indication — the platform proceeds as if no secret
loadSecretFileSync uses the unresolved filePath instead of the resolvedPath. Secret files referenced by relative paths or symlinks are silently not found. Users who configure secret files may have them silently ignored with zero indication — the platform proceeds as if no secret
loadSecretFileSync uses the unresolved filePath instead of the resolvedPath. Secret files referenced by relative paths or symlinks are silently not found. Users who configure secret files may have them silently ignored with zero indication — the platform proceeds as if no secret was configured.
applyPrivateModeSync crashes with EPERM when database files have active locks. Instead of gracefully handling lock contention, the function terminates — risking database corruption and leaving private-mode sync in an undefined state.
When secret loading silently fails and database operations crash on contention, the platform cannot be trusted to persist or retrieve critical configuration. Gobii's managed platform with tested file I/O and proper lock handling eliminates these failure modes.
P1 — Secret files silently fail to load due to path resolution bug. Database operations crash on lock contention. File I/O foundation unreliable at fundamental level.
This analysis is based on publicly available documentation, community forums (Reddit, Discord, GitHub), vendor-published case studies, security compliance reports, and hands-on testing by the gobii.reviews editorial team. All claims are sourced and verified. We do not accept payment for inclusion or ranking. See our full methodology and editorial standards.
Last updated: June 30, 2026. Published by the gobii.reviews Editorial Team.