On locust stop data available before stopping keeps on getting scrape with same last available data

# HELP locust_up The current health status of the server (1 = UP, 0 = DOWN).
# TYPE locust_up gauge
locust_up 0

level=error msg="Can't scrape Pack: Get \"http://localhost:8089/stats/requests\": dial tcp localhost:8089: connect: connection refused" source="main.go:333"

Eg : locust_requests_min_response_time{method="GET",name="SomeRequestName"} 2

This should not be coming in /metrics response.

Start at main.go:333, where the failed scrape is logged, and trace how the /metrics response handles the last successful Pack data after Locust stops. Verify that old locust_requests metrics are no longer exposed after the connection is refused while locust_up remains 0.

Written by the indexing model from the issue text.