Re: [twdev] Re: First call for planned release of v5.1.20

2019-06-18 Thread bimlas
I'm very sorry, but it was a false alarm, see https://github.com/Jermolene/TiddlyWiki5/issues/3998#issuecomment-503312664 -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send

Re: [twdev] Re: First call for planned release of v5.1.20

2019-06-18 Thread Jeremy Ruston
Hi Bimlas Thanks, that’s very helpful. This may get quite involved so I’ve created a GitHub ticket for further discussion: https://github.com/Jermolene/TiddlyWiki5/issues/3998 Best wishes Jeremy > On 18 Jun 2019, at 11:29, bimlas

Re: [twdev] Warning: Potential Security Risk Ahead - accessing upgrade page

2019-06-18 Thread Jeremy Ruston
Just adding that this turns out to be a common problem when hosting HTTPS sites on GitHub Pages: https://github.community/t5/GitHub-Pages/Does-GitHub-Pages-Support-HTTPS-for-www-and-subdomains/td-p/7116

Re: [twdev] Re: First call for planned release of v5.1.20

2019-06-18 Thread bimlas
The results of the first two case are above, so I just doing the test again on prerelease with disabled indexing: - Chrome: - Prerelease - mainRefresh: 1206.61ms - (from $tw.perf.log()) filter "[kin::to[TableOfContents]]"; invocations 3; avgTime

Re: [twdev] Re: First call for planned release of v5.1.20

2019-06-18 Thread Jeremy Ruston
Hi Bimlas Thanks for the report, that’s very helpful. There’s quite a lot that’s changed between v5.1.19 and the current prerelease, not just the indexing. One quick thing to try might be to make some more timings while manually enabling and disabling the indexing mechanism in the prerelease.

[twdev] Re: First call for planned release of v5.1.20

2019-06-18 Thread bimlas
Maybe it's just the plugin's fault, but it seems that for some reason the Kin filter is slower on prerelease (heavily using cache mechanism). I don't know if it's a new indexing system or a performance log issue. The code of the filter: