Skip to content

Cache is not invalidated on changes in tunables #1

@csachs

Description

@csachs

Reported by @ chrisp87

If a user changes tunables without either deactivating caching or deleting the cache files inbetween runs, they might be puzzled by the lack of changes in results.

Possible fix: Store a hash of tunables alongside the caches, automatically invalidate them if tunables are changed.

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions