Status: provide details on the last fetched date #256
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
avdempsey
approved these changes
Jan 9, 2026
mistydemeo
force-pushed
the
misty/last_fetched_details
branch
3 times, most recently
from
ee37852 to
890f891
Compare
mistydemeo
force-pushed
the
misty/last_fetched_details
branch
from
890f891 to
06967c5
Compare
mistydemeo
force-pushed
the
misty/last_fetched_details
branch
from
06967c5 to
803ef7d
Compare
Contributor
Author
|
I reworked this to return the status as a dictionary instead of an ever-growing tuple. Makes it easier to iterate on. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As part of debugging our long-running "oldest last fetched URL" issue I wanted to provide more detail about what we're fetching. The method that calculates it now also fetches the socket or recorded URL, as appropriate, and fills in whatever data it can provide.
This is split out of #254, but with only the logging and with the
RecordedUrlhandling added.