We think we have noticed some issues with the ns_cache emulation in Naviserver 4.99.6 since switching to it a couple of months ago. (Our Xotcl is 1.6.8.)
In one particular case, calls to fs::add_file from the file storage upload page resulted in an “expected boolean but got “”” error. The error was occurring at the reference to content::type::content_type_p. When looking at that proc in the CR, I noticed that content::type::content_type_p_not_cached should never return “”.
We had some other, similar page errors where util_memoize was involved as well. After inserting some log statements in util_memoize, I noticed that “ns_cache get" was returning 1 but the “pair” reference passed in to the proc (ns_cache get util_memoize $script pair) which should contain the data and cache time was not populated.
I haven’t been able to determine if there’s a pattern wrt the cache keys that have been troublesome and, so far at least, this doesn’t seem to be a widespread issue. Nevertheless, we’d like to figure out what’s going on. Anyone else run into this?
