[BUG] [Java Client]Cache will not be expired for getMultiVersionMessage().
Open
@huihuiw01 is already working on this.
Since Sep 25, 2023.
area/java-client
kind/bug
priority/medium
- Dominant language
- Java
- Stars
- 72
- Forks
- 69
- Avg merge
- 23h 32m
- Merged PRs (30d)
- 4
Description
Describe the bug
commit: 577b87bea7eea93fa1e02305ff2049820d65a30d
Cache will not be expired for getMultiVersionMessage().
To Reproduce
Steps to reproduce the behavior:
- Using getMultiVersionMessage() method in sharedLibary feature.
- Set its cache items to expire with below method:
cacheItem_zhcn.setCacheItem(cacheItem_zhcn.getEtag(), cacheItem_zhcn.getTimestamp(), 0l);
cacheItem_source.setCacheItem(cacheItem_source.getEtag(), cacheItem_source.getTimestamp(), 0l);
cacheItem_en.setCacheItem(cacheItem_en.getEtag(), cacheItem_en.getTimestamp(), 0l);
- Check the cache whether is expired:
cache.getExpiredTime() - See error: the cache always not expire
Expected behavior
cache should be expired in certain time, then new request will be sent out to service for updated translation.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.