Repository navigation
Avoid blocking on active Upwork pages - #14
Merged
Merged
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
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.
Summary
Follow-up to #12 and closes #13.
The previous authentication fix still reloaded Best Matches even when it was already active, which could leave Selenium waiting on Upwork’s dynamic page load. This change avoids unnecessary target-page reloads and uses eager browser navigation so authentication state can be evaluated without waiting for every page resource.
It also adds an explicit
Upwork authentication readylog entry and regression coverage for active-page reuse and authenticated redirects.Validation
make checkpasseduv run upwork-scraper --validate-loginpassed in approximately 24 secondsNo credentials, cookies, browser profiles, databases, or runtime logs are included.