ilyazub
ilyazub
Related to the endless scrolling pagination (https://github.com/serpapi/public-roadmap/issues/537).
The `num` parameter is ignored when Google decides to respond with the continuous scroll instead of the regular pagination. It's possible to disable continuous scroll by using an outdated user-agent....
> @ilyazub could using an outdated user agent have other possibly undesired effects, such as omitting certain new elements from searches? Unfortunately, yes — lots of new SERP features would...
> Perhaps we could apply `start =1` if `num!=10` and just make it explicit in our documentation that using `num` will not return the `knowledge_graph`? This workaround is best done...
SVG is huge * lines are not straight. Gaps between edges is a reason of the "aliasing issue".  * There are five elephant images on this SVG :elephant: ...
Probably related: Google Trends Embed data also differs from the Google Trends UI. | Google Trends UI | Google Trends Embed | |--------|--------| |  |  | At the...
There's an unexpected CSS string in the `apply_link.title` in the JSON.  (ref: https://serpapi.com/searches/657b1b1958762b9ea220c263/inspect)
> Would this also resolve something like passing `--require spec_helper` to rspec? Currently having difficulty loading `require 'webmock/rspec'` when running turbo_tests. @OneNeptune Can you please provide a repository with reproduction?...
`turbo_tests` work on Ruby 2.7, 3.0, 3.1, 3.2. Here are GitHub Actions runs: https://github.com/serpapi/turbo_tests/actions/runs/5252614857/job/14212914295 @lubosch Feel free to share a repository with reproducible example if this issue still actual.
We didn't reproduce it. `turbo_tests` and `rspec` executed the same number of examples. ``` bundle exec turbo_tests ./spec/search/yahoo/ 3163 examples, 0 failures bundle exec rspec ./spec/search/yahoo/ 3163 examples, 0 failures...