Documentation for workaround for caching in TrackStateProvider

Adds an entry in the documentation about the temporary workaround needed to use the TrackStateProvider in Moore. See Rec!1584 (merged) and LHCBPS-1835 for more details.

@sstahl @graven @wouter @apearce @chasse

Not sure what is expected of me here, but I was wondering: I understand from the description in Rec!1584 (merged) that the main problem is that the cleaning of the cache relies on an incident. If that is the case, then would it be an option to put the cache in the event-store and (temporarily) allow this tool to change what is in the event store?

added 1 commit

• 368882cc - add documentation for workaround for caching in TrackStateProvider

Compare with previous version

added 2 commits

• 553b6721 - add documentation for workaround for caching in TrackStateProvider
• 3dd3a7c7 - Add workaround for TrackStateProvider in the example script

Compare with previous version

added 1 commit

• 20da89b3 - Add workaround for TrackStateProvider in the example script

Compare with previous version

changed the description

added 2 commits

• 1383280a - add documentation for workaround for caching in TrackStateProvider
• 942dfe1f - Add workaround for TrackStateProvider in the example script

Compare with previous version

resolved all threads

approved this merge request

assigned to @jonrob

merged

mentioned in commit 4cf38b2d

unassigned @jonrob

added Documentation label