Skip to content

Actions: brightdata/linkedin-scraper-python

Actions

Live check

Actions

Loading...
Loading

Show workflow options

Create status badge

Loading
live.yml
18 workflow runs
18 workflow runs

Filter by Event

⌥ + click/return to exclude

Filter by Status

⌥ + click/return to exclude

Filter by Branch

⌥ + click/return to exclude

Filter by Actor

⌥ + click/return to exclude
Daily check: is anything broken? Live check #18: Scheduled
1m 10s main
main
1m 10s
Daily check: is anything broken? Live check #17: Scheduled
1m 30s main
main
1m 30s
Daily check: is anything broken? Live check #16: Scheduled
1m 49s main
main
1m 49s
Push check: Trim the contributing guide Live check #15: Commit 437af5e pushed by anil-bd
1m 22s main
main
1m 22s
Push check: Add a short contributing guide Live check #14: Commit 3146300 pushed by anil-bd
1m 0s main
main
1m 0s
Push check: Drop the note about the repository being private Live check #13: Commit e137035 pushed by anil-bd
57s main
main
57s
Push check: Update the banner to the design team's version Live check #12: Commit 5678f8b pushed by anil-bd
52s main
main
52s
Daily check: is anything broken? Live check #11: Scheduled
2m 0s main
main
2m 0s
Daily check: is anything broken? Live check #10: Scheduled
1m 56s main
main
1m 56s
Weekly check: does every README block still work? Live check #9: Scheduled
2m 15s main
main
2m 15s
Push check: Stagger the scheduled runs so the scraper repos never overlap Every scraper repo ran its daily and Monday checks at 06:00 UTC. On Monday that is the full README matrix in all four at once, up to about sixteen jobs against one account, which is the burst that returned "Your system is sending too many of this type of request" during the LinkedIn Python build. Valid inputs fail with that error, so the runs would go red with nothing wrong in the code. The Monday runs now start at 06:00, 06:20, ... Live check #8: Commit 38a7dc8 pushed by anil-bd
58s main
main
58s
Push check: Add the LinkedIn banner 2400x520, the LinkedIn twin of the Instagram one. The endpoint row and the subtitle are claims, and both hold: /profiles, /companies, /jobs and /posts are all in the endpoint table, collect takes URLs, and discover takes a name or a keyword. The README line was parked in a comment so the repository front page would not show a broken image before the file existed. Restored now. Live check #7: Commit 5bdf05d pushed by anil-bd
48s main
main
48s
Daily check: is anything broken? Live check #6: Scheduled
1m 19s main
main
1m 19s
Daily check: is anything broken? Live check #5: Scheduled
1m 36s main
main
1m 36s
Scrape satyanadella Live check #4: Manually run by anil-bd
1m 11s main
main
1m 11s
Push check: Live check: a failed block shows why, not only its last line The README's CLI block failed with "Saved 1 of 2 profiles", which is the one line that says nothing about the cause. The line naming the profile that failed, and its error, sat just above it and was discarded, so the run could not be diagnosed from its own log. A failing block now shows its failure lines: the CLI's "failed slug: ..." lines, or any line carrying an Error. It falls back to the last six lines. Live check #3: Commit c43bc69 pushed by anil-bd
1m 40s main
main
1m 40s
Scrape satyanadella Live check #2: Manually run by anil-bd
2m 24s main
main
2m 24s
Push check: The Python LinkedIn twin of linkedin-scraper-node LinkedIn profiles, companies, jobs and posts as JSON, on the Bright Data LinkedIn Scraper API, through brightdata-sdk 2.5.2. Every README code block was extracted from the README itself and run against the live API, and shows its real output. The sample file comes from a real run of the CLI. The SDK mislabels list results. With several URLs it pairs rows with inputs by position, and the API returns rows in a different order each run. Measur... Live check #1: Commit 18eab5c pushed by anil-bd
39s main
main
39s