-
Notifications
You must be signed in to change notification settings - Fork 79
Comparing changes
Open a pull request
base repository: thibaultcha/lua-resty-mlcache
base: 2.4.1
head repository: thibaultcha/lua-resty-mlcache
compare: 2.5.0
- 15 commits
- 13 files changed
- 2 contributors
Commits on Mar 25, 2020
-
Configuration menu - View commit details
-
Copy full SHA for 013f94f - Browse repository at this point
Copy the full SHA 013f94fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 5c17028 - Browse repository at this point
Copy the full SHA 5c17028View commit details
Commits on Jul 28, 2020
-
chore(t) use 'strict' in Util.md
Also ensure github-linguist does not parse this file as Raku.
Configuration menu - View commit details
-
Copy full SHA for 4451e32 - Browse repository at this point
Copy the full SHA 4451e32View commit details
Commits on Sep 25, 2020
-
feat(get) callback can now be 'nil' to probe L1/L2 caches
Signed-off-by: Thibault Charbonnier <thibaultcha@me.com> Specifying a `nil` callback to `:get()` is now possible. Doing so will return any item from L1/L2 (and do the L2 -> L1 promotion as usual). If a requested key is not in the cache, the return values will be `nil, nil, -1`, where -1 is a new meaning for the `hit_lvl` return value indicating a cache miss. This is helpful when trying to distinguish a *negative hit* (cached `nil`) from a regular *miss* (no value). The former will have a positive `hit_lvl` indicating the negative hit was cached in L1/L2). Example: local val, err, hit_lvl = cache:get("key") if val == nil then if hit_lvl == -1 then -- miss (no value) end -- negative hit (cached `nil`) end Thanks Hamish Forbes and Corina Purcarea for the feature proposal and patch. From #96
Configuration menu - View commit details
-
Copy full SHA for 5ad5126 - Browse repository at this point
Copy the full SHA 5ad5126View commit details -
Configuration menu - View commit details
-
Copy full SHA for cdb0489 - Browse repository at this point
Copy the full SHA cdb0489View commit details -
chore(ci) add OpenResty 1.17.8.x to the tests matrix
lua-resty-lru's `get()` now returns a third value `flags` in 1.17.8.x.
Configuration menu - View commit details
-
Copy full SHA for d0e1c02 - Browse repository at this point
Copy the full SHA d0e1c02View commit details -
Configuration menu - View commit details
-
Copy full SHA for 07d20ec - Browse repository at this point
Copy the full SHA 07d20ecView commit details -
Configuration menu - View commit details
-
Copy full SHA for 75bc831 - Browse repository at this point
Copy the full SHA 75bc831View commit details -
tests(get) enable the 'opts' validation test
This test should have been enabled a long time ago already.
Configuration menu - View commit details
-
Copy full SHA for 0a690a6 - Browse repository at this point
Copy the full SHA 0a690a6View commit details -
Configuration menu - View commit details
-
Copy full SHA for 4e8f5b9 - Browse repository at this point
Copy the full SHA 4e8f5b9View commit details
Commits on Nov 18, 2020
-
feat(ipc) avoid new workers attempting to replay evicted events
A follow-up to #88. Described in #93 and reported a few months ago is the likely possibility that mlcache and ipc instances are created in the `init` phase. If a worker is to be started much later in the master process' lifetime, the newly forked ipc instance will have an `idx` attribute set to the shm_idx value at the time of `init` (likely 0). These workers will resume polling evicted events, and `poll()` will likely timeout indefinitely from there. For the fix in #88 to work, the mlcache instance has to be instantiated during `init_worker` or later. This patch proposes an approach which works for instances created in both `init` and `init_worker`: as soon as the ipc shm has started evicting items, we guarantee that future workers will resume polling at the current index, without having to call any method but `poll()`. Fix #93
Configuration menu - View commit details
-
Copy full SHA for 1a5bd4a - Browse repository at this point
Copy the full SHA 1a5bd4aView commit details
Commits on Nov 19, 2020
-
Configuration menu - View commit details
-
Copy full SHA for 3a6b051 - Browse repository at this point
Copy the full SHA 3a6b051View commit details -
Configuration menu - View commit details
-
Copy full SHA for 8096940 - Browse repository at this point
Copy the full SHA 8096940View commit details -
Configuration menu - View commit details
-
Copy full SHA for 23662c9 - Browse repository at this point
Copy the full SHA 23662c9View commit details -
Configuration menu - View commit details
-
Copy full SHA for acf6d6e - Browse repository at this point
Copy the full SHA acf6d6eView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 2.4.1...2.5.0