Commit Graph

16 Commits

Author SHA1 Message Date
Corey ae08f6bc13
setup v4
Signed-off-by: Jakub Sokołowski <jakub@status.im>
2023-08-22 11:07:40 +02:00
Jakub Sokołowski c18940ff99 add Jenkinsfile for CI builds, extend Makefile
Signed-off-by: Jakub Sokołowski <jakub@status.im>
2023-08-21 15:36:10 -04:00
Corey 16f315e8ee Initial commit 2023-08-21 15:36:10 -04:00
Jacky Zhao cea6834fef profiling, better concurrency heuristics 2023-08-09 00:26:33 -07:00
Jacky Zhao 49bd6bc3ff better concurrency debugging, --concurrency flag for npx quartz build 2023-08-08 22:52:49 -07:00
Jacky Zhao 3ac6b42e16 finish path refactoring, add sourcemap + better trace support 2023-07-15 23:02:12 -07:00
Jacky Zhao 465804a389 basic docs, remove publish, add quartz create 2023-07-05 00:16:06 -07:00
Jacky Zhao 92ca787092 fix default callout state 2023-07-04 18:26:11 -07:00
Jacky Zhao 9ad89997a5 multi-core builds 2023-06-04 12:35:45 -04:00
Jacky Zhao a757521313 base setup 2023-05-28 17:44:08 -07:00
Jacky Zhao 5ef9aad501 feat: add support for semantic search using operand 2022-07-31 12:16:36 -07:00
Claudio Yanes 7e0f2e4449 Fix fetchData
The fetchData function suffer from a race condition. If the function is
called before the promise finishes, it will result in another pair of
HTTP request. This does not only make the function useless but
Actually, it makes it harmful as the data might be redownloaded twice.

Now fetchData is not a function but rather the promise by itself.
Previous callers are expected to await the variable instead, this
should be not concern as awaiting a promise multiple time in
JavaScript is completely safe.
2022-03-04 02:25:30 +00:00
Jacky Zhao fcd5d2807d feat: dynamically fetch indices 2022-02-15 19:39:14 -05:00
jackyzha0 1c851271ea add search support 2021-08-27 14:08:11 -04:00
jackyzha0 ea69050587 add base pages 2021-07-18 11:54:00 -04:00
jackyzha0 c01138a81c add base structure 2021-07-18 09:35:42 -04:00