Applies to one job then crashes

[xMacJ]

I seem to be running into a similar issue as before. The script applies to one job and can't locate the next job. I am using Selenium v4.1.0 and Chrome v96.0.

[nopmop]

@xMacJ that's strange. Are you running the page in full resolution? How many jobs are on the page? Can you attach a screenshot and the source of the page (as files) here?

[xMacJ]

@nopmop I took a screenshot of the page where the script breaks. I have also attached the source code of the page below. There are plenty of jobs listed on each page where the script breaks. Let me know if you need any additional information. I also want to note that this issue occurs on two of my windows machines, so it doesn't seem to be a device-related bug.

Source File

Screenshot

[nopmop]

@xMacJ I'm afraid, from the file I can't see the source that's fully rendered on your browser. FYI: because some HTML elements are added dynamically to the page as you browse, saving the page or right-clicking and choosing "View Source" and saving the source is not enough with Linkedin. When you're requested a page source it's always better to open the debugger's pane (F12), go to the Inspector tab (usually the first tab) and then select the HTML tag from the tree, right-click, and select Copy -> InnerHTML. Anyway, I see no reason why you should get that error, so let me try to reproduce it by using your query and I'll get back to you.

[nopmop]

@xMacJ look, I added a possible workaround for your bug which I wasn't able to reproduce in any way. Clone from my fork & test please. Please note: I added 3 new parameters (hourlyRate, dailyRate, desiredSalary) to the config, and you must add them to your existing config too.

[xMacJ]

@nopmop Thank you for that information. I gone ahead and pulled the source again using the mentioned method. The script is still throwing the same error after the most recent changes. Source

[nopmop]

@xMacJ I'm trying to help you but, as I've told you, I haven't managed to reproduce your error so I can't really fix it.
Anyhow, I've looked a bit more carefully at the code and I can tell you: it's messed up 👎 Regardless of the bugs that are due to old age (i.e. Linkedin made updates to to the structure of its pages which weren't reflected in the code) some features of the bot promised by the config aren't even there (e.g. the gender, race, veteran - which is even misspelled in the config - and disability don't actually do anything), while other parts of the code will never work properly because they have logic/flow errors. I fixed most of these bugs but at some point I thought that maybe it's not worth to maintain/expand this, and so didn't even commit to my repo. Maybe actually I'll cancel my PR, because by running this code (even in a Linux VM, which would surely bypass your error) one would hardly get hired - rather one would risk spoiling some good job opportunities.
Maybe I could just use a weekend to write a full-fledged app that runs directly in the browser as an Extension/Add-on. It would be easier to use for ordinary people and I could make it so that it could be updated by the community of users rather than by developers. Bah.

[NathanDuma]

If you read the bottom of the readme it says it is currently unused.

…

On Sat., Oct. 22, 2022, 7:53 a.m. nopmop, ***@***.***> wrote: @xMacJ <https://github.com/xMacJ> I'm trying to help you but, as I've told you, I haven't managed to reproduce your error so I can't really fix it. Anyhow, I've looked a bit more carefully at the code and I can tell you: it's messed up 👎 Regardless of the bugs that are due to old age (i.e. Linkedin made updates to to the structure of its pages which weren't reflected in the code) some features of the bot promised by the config aren't even there (e.g. the *gender*, *race*, *veteran* - which is even misspelled in the config - and *disability* don't actually do anything), while other parts of the code will never work properly because they have logic/flow errors. I fixed most of these bugs but at some point I thought that maybe it's not worth to maintain/expand this, and so didn't even commit to my repo. Maybe actually I'll cancel my PR, because by running this code (even in a Linux VM, which would surely bypass your error) one would hardly get hired - rather one would risk spoiling some good job opportunities. Maybe I could just use a weekend to write a full-fledged app that runs directly in the browser as an Extension/Add-on. It would be easier to use for ordinary people and I could make it so that it could be updated by the community of users rather than by developers. Bah. — Reply to this email directly, view it on GitHub <#53 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACXY2FCYJV4ZKSKOPRK2PB3WEP5X3ANCNFSM6AAAAAARICA4VM> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[xMacJ]

@nopmop Thank you for attempting to reproduce the issue and find solutions. I'll be manually applying for now and look forward to see what is created down the line in terms of automation!