7 Commits

Author	SHA1	Message	Date
Garfield69	da340ed952	assorted: follow up on #12274 but for C#	2021-09-08 13:02:29 +12:00
Diego Heras	aca4a16bae	ci/cd: fix whitespaces (#11749)	2021-05-16 20:13:54 +02:00
XYZJR	eaf0513605	Core: rewrite of configuration items. Resolves #2114 (#11104)	2021-03-17 12:29:26 +13:00
Diego Heras	69125add3e	core: redo search cache from scratch. resolves #10382 (#10447) ... In simple words, when you make a request in Jackett, the results are saved in memory (cache). The next request will return results form the cache improving response time and making fewer requests to the sites. * We assume all indexers/sites are stateless, the same request return the same response. If you change the search term, categories or something in the query Jackett has to make a live request to the indexer. * There are some situations when we don't want to use the cache: ** When we are testing the indexers => if query.IsTest results are not cached ** When the user updates the configuration of one indexer => We call CleanIndexerCache to remove cached results before testing the configuration ** When there is some error/exception in the indexer => The results are not cached so we can retry in the next request * We want to limit the memory usage, so we try to remove elements from cache ASAP: ** Each indexer can have a maximum number of results in memory. If the limit is exceeded we remove old results ** Cached results expire after some time * Users can configure the cache or even disable it	2020-12-11 23:14:21 +01:00
Diego Heras	f3c8035a04	magnetico: add clarification note. resolves #10174 (#10316)	2020-11-28 18:34:37 +01:00
Diego Heras	2ea22af9ef	core: rename comments field to details #10092 (#10135)	2020-11-08 15:11:27 +13:00
Diego Heras	f0d8c88505	magnetico: add new local dht tracker. #2684 (#10136) ... https://github.com/boramalper/magnetico	2020-11-08 02:45:03 +01:00