Closed tudopropaganda closed 2 weeks ago
@tudopropaganda please checkout the created PR which by default displays error messages now and am curious if it gives you any different output now.
I removed the .env file to test it and on my machine, it runs.
The main advantage of using Docker: there is no ambiguity about different setups two of us might have... I'll leave it up to you to propose a solution inside the already existing PR, otherwise, I'll close the issue in a week or two.
Thank you for your effort either way 🙏
P.S. the backend / frontend setup is for you to create if you want. Otherwise just ignore it. I have that repository_wrapper for my project that I'm working on.
Hi @GabeGiro ! I have forked the repo and tried a fresh run and it worked. I don't know what was happening.
Thank you for your time and your reply.
Just a suggestion, maybe its something that in the future you can separate, the logic from your other work from the open repo, because linkedin.py relies in this wrapper (although its not doing something...)
I could not run through docker, despite having it installed on my machine.
I've found a bug also after clicking in the Easy apply button regarding the Follow company logic (which i think i've already corrected and will raise a PR).
To be honest, my version is working now, its fetching pages and so on, its clicking in the Easy Apply, but its not moving forward after this, * 🥵 Couldn't apply to this job! Extra info needed... for all the jobs it tries...
Are you using the script and getting fair results from it? Or is it something that needs many corrections yet?
Thank you again!
@tudopropaganda great that it works! I'll close this issue then.
The message "Extra info needed..." could be replaced with "Answers to some questions missing" which is more specific. Currently, answering questions is not done but the tasks that are related to it are under the following milestone https://github.com/GabeGiro/EasyApplyJobsBot/milestone/1 Fair results are there for very easy applications which don't need any additional questions answered. But, I agree that answering should be done as part of this repo. The original repo might have some clues to how to answer to questions but I think the original contributor made it a paid feature if I remember correctly...not sure.
As far as the repository_wrapper goes, I agree that it might be misleading and I will think about a better solution so that it's not part of the public repo.
I'll check your PR asap. Thank you 🙏
In the file repository_wrapper.py I have this missing import statement in line 21.
from frontend.utils import ( api as backend_api, # Change this line with your backend module )
repository_wrapper.py
I see there is no frontend dir in the repo.
The program is exiting prematurely:
I'm trying to run it locally, without Docker.
Please, can you check?