admin-valentin/agent-ecosystem
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix: use full intervals content in worker cache key, not just length

Browse source 
Two different interval sets with the same length would produce
the same cache key, returning stale results. Serialize each
interval's startedAt~completedAt into the key.
This commit is contained in:
Artem Rootman 2026-04-05 18:09:59 +00:00
parent 270eb547cb
commit bc7981f6b9
No known key found for this signature in database
GPG key ID: B7C30676209A822C
1 changed files with 4 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
src/main/workers/team-data-worker.ts
View file

@ -44,7 +44,10 @@ parentPort?.on('message', async (msg: TeamDataWorkerRequest) => {
}
case 'findLogsForTask': {
const { teamName, taskId, options } = msg.payload;
const cacheKey = `${teamName}:${taskId}:${options?.owner ?? ''}:${options?.status ?? ''}:${options?.since ?? ''}:${options?.intervals?.length ?? 0}`;
const intervalsKey = options?.intervals
? options.intervals.map((i) => `${i.startedAt}~${i.completedAt ?? ''}`).join(',')
: '';
const cacheKey = `${teamName}:${taskId}:${options?.owner ?? ''}:${options?.status ?? ''}:${options?.since ?? ''}:${intervalsKey}`;
// Check result cache
const cached = logsResultCache.get(cacheKey);