job-search | small node script for job | Runtime Evironment library

You need page next from the current page. This is quite qasy with following-sibling

There are two elements with same id

I used driver.find_elements_by_id("keywords") method to get all of them as a list

and i accessed the required using index number

You won't be able to use ? for identifiers (the database structures, like table and column names). You will need to use string interpolation to put in the column name.

f"UPDATE users SET {key} = ? WHERE id = ?"

? are basically for values (user-supplied data).

https://docs.python.org/3/library/sqlite3.html

Usually your SQL operations will need to use values from Python variables. You shouldn’t assemble your query using Python’s string operations because doing so is insecure; it makes your program vulnerable to an SQL injection attack (see https://xkcd.com/327/ for humorous example of what can go wrong).

Instead, use the DB-API’s parameter substitution. Put ? as a placeholder wherever you want to use a value, and then provide a tuple of values as the second argument to the cursor’s execute() method. (Other database modules may use a different placeholder, such as %s or :1.)

As you suggest, you'll need an API endpoint to fetch the data from, returning it as a JSON object. You'll need to add a route to your client-side routes that takes the job ID (or slug) as a parameter. In your job component, you can retrieve the route param (e.g. in the created() method) as $route.params.id, for example, and use that to fetch the data from your API.

If your Algolia search is returning all the data that you want to display on your single job listing page, you could just put that in your Vuex store and display it without having to make another HTTP request. The downside of that would be that if a user bookmarked the page to return to later, there'd be no data in the store to display.

You can try the following code:-

As John Hanley commented quota issues are usually handled by the Cloud Support team and should be addressed opening a support ticket. However, this case refers to Cloud Talent Solution Profile Search which as stated in the documentation at this moment is in 'Closed Beta' state, meaning that it doesn't allow new candidates.

In order to use this feature you will have to wait until it's released to the public or the Beta is opened for new candidates.

You need to debug a bit that what is being done while making a pagination request. Site is not storing hrefs for next page because its a dynamic url which is being generated at runtime. I tested it for page 7 and this is the link which was created

1. With v2 the correct endpoint would be https://api.linkedin.com/v2/recommendedJobs https://developer.linkedin.com/docs/guide/v2/jobs/recommended-jobs#retrieve-recommended-job
2. You need r_JYMBII permission but that is not given to any app. You need to manually request that in behalf of your app in linkedin's developer admin panel.
3. First you tried using v2 API without the proper permission than you tried using v1 which is no longer available and than when you tried using v2 you used the old endpoint which doesn't exist under v2.

To be fair the v2 is a LOT more restrictive than v1 and from my experience it will take a lot of time to get permission from linkedin to use any permission apart from r_liteprofile, r_emailaddress and w_member_social that are the ones it gives by default to perform sign in and share.

https://docs.microsoft.com/en-us/linkedin/consumer/integrations/self-serve/sign-in-with-linkedin?context=linkedin/consumer/context

The bottleneck is the server responding slowly to a simple requests.

Try doing request parallel.

You can also use threads instead of asyncio. Here is a previous question explain for to parallerise tasks in Python:

Executing tasks in parallel in python

Please note that a smartly configured server would still slow your requests or ban you if you are scraping without a permission.