White screen only after upgrade to latest version 2.5.1

General
1

Hi, I find my instance totally white screen after upgrade to the latest. with only following showing in the console of the client.

Does anyone have clue why this fallback is happening? Also cleared the cache multiple times.

logger.ts:43 [Client] Falling back to cache for .config
logger.ts:43 [Client] TypeError: Cannot set properties of undefined (setting 'enableClientEncryption')
    at boot.ts:138:17
(anonymous) @ logger.ts:43
(anonymous) @ async.ts:153
Promise.catch
q2 @ async.ts:152
(anonymous) @ boot.ts:27
(anonymous) @ boot.ts:352
logger.ts:43 [Client] Falling back to cache for .fs/Library/Std/APIs/Schema.md
logger.ts:43 [Client] Falling back to cache for .fs/Library/Std/Config.md
logger.ts:43 [Client] Falling back to cache for .fs/Library/Std/APIs/Tag.md
logger.ts:43 [Client] Falling back to cache for .fs/CONFIG.md
2

I managed to dig deeper. and I find the problem:

SilverBullet client fetch for .config times out at 1.0s (AbortSignal.timeout(1000) in silverbullet/client/boot.ts:304).

My endpoint is healthy, but too slow for that timeout (~1.64s), so browser code falls back to cache. :sweat_smile:

@zef I wonder if this is possible to later configure this timeout via env? otherwise I am stucked here infinitely. Now I will just patch the repo.

3

1s is quite short, so I can prolong it a bit (although I should not this didnā€™t change in 2.5). As to making this configurableā€¦ Iā€™d almost say yes, via the /.config endpoint :laughing:

4

Hi Zef, long time no see. How is it going?

I made a local patch to 5000ms but I didn't solve this issue yet. so I think I still need to dig deeper to understand what is wrong now.

I will make this available later after I find the real culprit.

5

I finished my debugging and made it a blog on my website: Debugging Silverbullet not Loading - How to peel off the onion of cache ā˜ļø Live my life consciously

So it was really incurred by timeout. But I find it interesting that SB update is very dependent on the browser caches/cloudflare caches.

I think I might open a new topic the other day to introduce what I found to other people in the community.