You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 7, 2019. It is now read-only.
Hi guys. I think I found bug but please validate my findings described below: SourceFileReader uses private method pathForBarcode in order to get path for BarCode. However, SourceFileWriter delegates it to pathResolver.
The bug which above causes is: FileSystemImpl:getRecordState returns RecordState.MISSING all the time as path which was saved by SourceFileWriter is different than path used by SourceFileReader. We talk about the case when BarCode is a key.
Does above make sense?
The text was updated successfully, but these errors were encountered:
If I understood Store lib properly following statements are true:
treat cached data in memory data as up-to-date for 5s
treat cached data in File System as up-to-date for 10s
So after 10 secs data is treat as STALE and fetch call should be performed.
As an addition to bug description I can see that StoreUtil.persisterIsStale always returns true because RecordState recordState = provider.getRecordState(key); is always RecordState.MISSING.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi guys. I think I found bug but please validate my findings described below:
SourceFileReader uses private method
pathForBarcode
in order to get path forBarCode
. However,SourceFileWriter delegates it to
pathResolver
.The bug which above causes is: FileSystemImpl:getRecordState returns
RecordState.MISSING
all the time as path which was saved bySourceFileWriter
is different than path used bySourceFileReader
. We talk about the case whenBarCode
is a key.Does above make sense?
The text was updated successfully, but these errors were encountered: