You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What I'd like is to remove "watching the terminal" from the workflow:
fine_ants scrapes and returns a 2FA question to answer
fine_ants_app displays a UI prompting the user for the 2FA answer
fine_ants_app returns the answer to fine_ants, which continues scraping
Challenges to this:
Currently, fine_ants uses stdin for this stuff and just blocks until it gets an answer.
Multiple web requests can't just block the main thread
Capybara/Selenium are really finicky and will lose their connection to a browser at the drop of a hat
Ideas:
Since this is a local/single-tenant app, we can get away with murder and do whatever we want. Like:
Start up a separate long-running process that runs fine_ants and negotiates back and forth using stdout/stdin
Run the fine_ants API in a separate long-lived thread so that we can poke at it over multiple requests
hand-wavey actioncable idea
I think route 2 is actually desirable, because it would allow the app to recover gracefully if the scraper is ever broken in the main thread (which currently requires an app restart).
The text was updated successfully, but these errors were encountered:
What I'd like is to remove "watching the terminal" from the workflow:
Challenges to this:
Ideas:
Since this is a local/single-tenant app, we can get away with murder and do whatever we want. Like:
I think route 2 is actually desirable, because it would allow the app to recover gracefully if the scraper is ever broken in the main thread (which currently requires an app restart).
The text was updated successfully, but these errors were encountered: