Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a test that validates the default configuration #97

Closed
subnetmarco opened this issue Mar 25, 2015 · 0 comments
Closed

Create a test that validates the default configuration #97

subnetmarco opened this issue Mar 25, 2015 · 0 comments
Assignees
Milestone

Comments

@subnetmarco
Copy link
Member

So that if something changes in the default configuration, it needs to be explicitly fixed in the test too.

@subnetmarco subnetmarco added this to the 0.2.0-beta milestone Mar 25, 2015
@subnetmarco subnetmarco self-assigned this Apr 3, 2015
ctranxuan pushed a commit to streamdataio/kong that referenced this issue Aug 25, 2015
bungle added a commit that referenced this issue Dec 7, 2020
### Summary

#### [2.5.0]

> Released on: 2020/11/18

##### Added

- `get()` callback functions are now optional. Without a callback, `get()` now
  still performs on-cpu L1/L2 lookups (no yielding). This allows implementing
  new cache lookup patterns guaranteed to be on-cpu for a more constant,
  smoother latency tail end (e.g. values are refreshed in background timers with
  `set()`).
  Thanks Hamish Forbes and Corina Purcarea for proposing this feature and
  participating in its development!
  [#96](thibaultcha/lua-resty-mlcache#96)

##### Fixed

- Improve `update()` robustness to worker crashes. Now, the library behind
  `cache:update()` is much more robust to re-spawned workers when initialized in
  the `init_by_lua` phase.
  [#97](thibaultcha/lua-resty-mlcache#97)
- Document the `peek()` method `stale` argument which was not mentioned, as well
  as the possibility of negative TTL return values for expired items.
bungle added a commit that referenced this issue Dec 8, 2020
### Summary

#### [2.5.0]

> Released on: 2020/11/18

##### Added

- `get()` callback functions are now optional. Without a callback, `get()` now
  still performs on-cpu L1/L2 lookups (no yielding). This allows implementing
  new cache lookup patterns guaranteed to be on-cpu for a more constant,
  smoother latency tail end (e.g. values are refreshed in background timers with
  `set()`).
  Thanks Hamish Forbes and Corina Purcarea for proposing this feature and
  participating in its development!
  [#96](thibaultcha/lua-resty-mlcache#96)

##### Fixed

- Improve `update()` robustness to worker crashes. Now, the library behind
  `cache:update()` is much more robust to re-spawned workers when initialized in
  the `init_by_lua` phase.
  [#97](thibaultcha/lua-resty-mlcache#97)
- Document the `peek()` method `stale` argument which was not mentioned, as well
  as the possibility of negative TTL return values for expired items.
gszr pushed a commit that referenced this issue Dec 8, 2020
### Summary

#### [2.5.0]

> Released on: 2020/11/18

##### Added

- `get()` callback functions are now optional. Without a callback, `get()` now
  still performs on-cpu L1/L2 lookups (no yielding). This allows implementing
  new cache lookup patterns guaranteed to be on-cpu for a more constant,
  smoother latency tail end (e.g. values are refreshed in background timers with
  `set()`).
  Thanks Hamish Forbes and Corina Purcarea for proposing this feature and
  participating in its development!
  [#96](thibaultcha/lua-resty-mlcache#96)

##### Fixed

- Improve `update()` robustness to worker crashes. Now, the library behind
  `cache:update()` is much more robust to re-spawned workers when initialized in
  the `init_by_lua` phase.
  [#97](thibaultcha/lua-resty-mlcache#97)
- Document the `peek()` method `stale` argument which was not mentioned, as well
  as the possibility of negative TTL return values for expired items.
gszr pushed a commit that referenced this issue Jun 10, 2021
gszr pushed a commit that referenced this issue Aug 6, 2021
javierguerragiraldez pushed a commit that referenced this issue Sep 3, 2021
A new consistent hashing algorithm was added. It should not rely on
the order of adding and removing addresses to always build the same
balancing strategy.
hutchic pushed a commit that referenced this issue Jun 10, 2022
### Summary

#### libyaml 0.2.2 release

- #95 -- build: do not install config.h
- #97 -- appveyor.yml: fix Release build
- #103 -- Remove unused code in yaml_document_delete
- #104 -- Allow colons in plain scalars inside flow collections
- #109 -- Fix comparison in tests/run-emitter.c
- #117 -- Fix typo error
- #119 -- The closing single quote needs to be indented...
- #121 -- fix token name typos in comments
- #122 -- Revert removing of open_ended after top level plain scalar
- #125 -- Cherry-picks from PR 27
- #135 -- Windows/C89 compatibility
- #136 -- allow override of Windows static lib name

#### libyaml 0.2.3 release

- #130 Fixed typo.
- #144 Fix typo in comment
- #140 Use pointer to const for strings that aren't/shouldn't be modified
- #128 Squash a couple of warnings in example-deconstructor-alt
- #151 Fix spelling for error message
- #161 Make appveyor config be a hidden file
- #159 Add CHANGES file
- #160 Always output document end before directive (YAML 1.2 compatibility)
- #162 Output document end marker after open ended scalars
- #157 change cmake target name from libOFF.a to libyaml.a
- #155 include/yaml.h: fix comments
- #169 Fixed missing token in example
- #127 Avoid recursion in the document loader.
- #172 Support %YAML 1.2 directives
- #66 Change dllexport controlling macro to use _WIN32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant