Skip to content
Build&Test

fix: FasterKv cache expiration time is not effective #22

Sign in to view logs

fix: FasterKv cache expiration time is not effective

fix: FasterKv cache expiration time is not effective #22

Triggered via push September 26, 2024 07:29
@MemoyuMemoyu
pushed 022f9c8
fix-#550
Status Success
Total duration 1m 45s
Artifacts –

buildandtest.yml

on: push
Matrix: linux
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
build and test on ubuntu-latest
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build and test on ubuntu-latest: src/EasyCaching.FasterKv/Internal/FasterKvCacheValue.cs#L5
Non-nullable property 'Value' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
build and test on ubuntu-latest: src/EasyCaching.FasterKv/Internal/FasterKvCacheValue.cs#L5
Non-nullable property 'Value' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
build and test on ubuntu-latest: src/EasyCaching.FasterKv/Internal/FasterKvCacheValue.cs#L5
Non-nullable property 'Value' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
build and test on ubuntu-latest: src/EasyCaching.FasterKv/Internal/FasterKvCacheValue.cs#L5
Non-nullable property 'Value' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
build and test on ubuntu-latest: src/EasyCaching.FasterKv/Internal/FasterKvCacheValue.cs#L5
Non-nullable property 'Value' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.