SQL table to track which tasks got used #85
Labels
client
related to the Carp client
enhancement
New feature or request
help wanted
Extra attention is needed
indexer
related to the Carp indexer
task
related to Carp tasks
webserver
related to the Carp webserver
One problem with the Carp webserver is that it has no way to know if the user really ran the task required to index the data needed for a specific endpoint. This means the webserver shows endpoints that may be entirely broken or subtly wrong.
One wat we could fix this is make that every time Carp is launched, it saves which tasks were used in the EP to the database. The webserver would then be able to look at this table to know whether or not to disable or fast-fail endpoints
The text was updated successfully, but these errors were encountered: