这是indexloc提供的服务,不要输入任何密码
Skip to content

Conversation

@dogancanbakir
Copy link
Member

@dogancanbakir dogancanbakir commented Jun 17, 2025

Closes #1602

Summary by CodeRabbit

  • New Features
    • Improved support for paginated results when retrieving data from Hunter and Quake sources, enabling more comprehensive data collection.
  • Bug Fixes
    • Resolved an issue where only the first page of results was fetched from Hunter and Quake sources, ensuring all available results are now retrieved.
  • Chores
    • Updated recursive support indication for Rsecloud source to reflect accurate capabilities.

@dogancanbakir dogancanbakir requested a review from ehsandeep June 17, 2025 12:56
@dogancanbakir dogancanbakir self-assigned this Jun 17, 2025
@coderabbitai
Copy link

coderabbitai bot commented Jun 17, 2025

"""

Walkthrough

The changes update the pagination logic in the Hunter and Quake source modules. Both modules now correctly iterate through paginated API results by dynamically adjusting the page or start parameters in their respective requests, ensuring all available data is retrieved instead of only the first page.

Changes

File(s) Change Summary
v2/pkg/subscraping/sources/hunter/hunter.go Modified HTTP GET request to use the current page variable for pagination in the Run method.
v2/pkg/subscraping/sources/quake/quake.go Replaced single-request logic with a loop implementing paginated POST requests in the Run method.
v2/pkg/subscraping/sources/rsecloud/rsecloud.go Changed HasRecursiveSupport() method to return false instead of true.

Sequence Diagram(s)

sequenceDiagram
    participant SubscrapingModule
    participant HunterAPI
    participant QuakeAPI

    SubscrapingModule->>HunterAPI: GET /api/search?domain=...&page=currentPage
    loop For each page (Hunter)
        HunterAPI-->>SubscrapingModule: Return paginated results
        SubscrapingModule->>HunterAPI: GET next page
    end

    SubscrapingModule->>QuakeAPI: POST /quake_service with start, size params
    loop For each page (Quake)
        QuakeAPI-->>SubscrapingModule: Return paginated results
        SubscrapingModule->>QuakeAPI: POST next page (increment start)
    end
Loading

Assessment against linked issues

Objective Addressed Explanation
Fix paginations in Quake and Hunter (#1602)

Assessment against linked issues: Out-of-scope changes

Code Change Explanation
Changed HasRecursiveSupport() to return false (v2/pkg/subscraping/sources/rsecloud/rsecloud.go) This change is unrelated to pagination fixes in Hunter and Quake sources as per issue #1602.

Suggested reviewers

  • ehsandeep

Poem

In fields of code where queries hop,
The hunter and quake now never stop.
Through pages they leap, each one in turn,
Gathering data for which we yearn.
With every hop, a subdomain found—
This rabbit’s joy in code abounds! 🐇✨
"""


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1b943c5 and ce6ae5f.

📒 Files selected for processing (1)
  • v2/pkg/subscraping/sources/quake/quake.go (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • v2/pkg/subscraping/sources/quake/quake.go
⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: Test Builds (macOS-13)
  • GitHub Check: Test Builds (windows-latest)
  • GitHub Check: Test Builds (ubuntu-latest)
  • GitHub Check: release-test
✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🔭 Outside diff range comments (1)
v2/pkg/subscraping/sources/hunter/hunter.go (1)

59-61: Wrong divisor ⇒ most pages never queried

page_size is fixed at 100 in the request, but the page‐count is derived with response.Data.Total/1000.
For any data-set larger than 100 records the loop will stop far too early (e.g. 250 items ⇒ 1 page instead of 3).

- var pages = 1
+ const pageSize = 100
+ var pages = 1
...
- pages = int(response.Data.Total/1000) + 1
+ pages = (response.Data.Total + pageSize - 1) / pageSize   // ceil division

Also remember to pass pageSize into the URL:

- &page_size=100&
+ &page_size=%d&

Failing to fix this silently drops large portions of the result-set.

Also applies to: 96-97

🧹 Nitpick comments (1)
v2/pkg/subscraping/sources/hunter/hunter.go (1)

59-64: Minor: avoid redundant base64 encoding inside the loop

qbase64 depends only on the domain and can be pre-computed once before the loop to save a tiny amount of CPU per page.

- for currentPage := 1; currentPage <= pages; currentPage++ {
-     qbase64 := base64.URLEncoding.EncodeToString([]byte(fmt.Sprintf("domain=\"%s\"", domain)))
+ qbase64 := base64.URLEncoding.EncodeToString([]byte(fmt.Sprintf("domain=\"%s\"", domain)))
+ for currentPage := 1; currentPage <= pages; currentPage++ {
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3acf6d5 and d0a7433.

📒 Files selected for processing (2)
  • v2/pkg/subscraping/sources/hunter/hunter.go (1 hunks)
  • v2/pkg/subscraping/sources/quake/quake.go (1 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (1)
v2/pkg/subscraping/sources/quake/quake.go (2)
v2/pkg/subscraping/types.go (3)
  • Result (81-86)
  • Error (94-94)
  • Subdomain (93-93)
v2/pkg/subscraping/sources/anubis/anubis.go (1)
  • Source (16-20)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: release-test
🔇 Additional comments (1)
v2/pkg/subscraping/sources/hunter/hunter.go (1)

63-63: Dynamic page parameter – good catch

Replacing the hard-coded 1 with currentPage finally enables real pagination.

@dogancanbakir
Copy link
Member Author

lint errs fixed in #1601

Copy link
Member

@ehsandeep ehsandeep left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

merge conflict

@dogancanbakir dogancanbakir requested a review from ehsandeep June 20, 2025 17:47
@ehsandeep ehsandeep merged commit a0be3ff into dev Jun 20, 2025
10 checks passed
@ehsandeep ehsandeep deleted the fix_paginations branch June 20, 2025 18:41
x-stp pushed a commit to x-stp/subfinder that referenced this pull request Jun 20, 2025
* fix quake pagination

* update page param

* skip empty

* fix test

* minor
x-stp pushed a commit to x-stp/subfinder that referenced this pull request Jun 20, 2025
* fix quake pagination

* update page param

* skip empty

* fix test

* minor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix paginations in quake and hunter

4 participants