Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add resume option to sdk #6083

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from
Open

add resume option to sdk #6083

wants to merge 1 commit into from

Conversation

dogancanbakir
Copy link
Member

@dogancanbakir dogancanbakir commented Mar 3, 2025

Proposed changes

Closes #6078

Checklist

  • Pull request is created against the dev branch
  • All checks passed (lint, unit/integration/regression tests etc.) with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

Summary by CodeRabbit

  • New Features
    • Introduced a configuration option that allows users to specify a resume file, expanding the engine's flexibility for managing process continuity.

@dogancanbakir dogancanbakir requested a review from ehsandeep March 3, 2025 19:57
@dogancanbakir dogancanbakir self-assigned this Mar 3, 2025
@auto-assign auto-assign bot requested a review from dwisiswant0 March 3, 2025 19:57
Copy link
Contributor

coderabbitai bot commented Mar 3, 2025

Walkthrough

This change introduces a new function, WithResumeFile, in the configuration module. The function takes a file path as a string and sets the Resume field of the NucleiEngine’s options. It returns nil upon successful assignment, providing an additional configuration option to manage resume files in the engine.

Changes

File Summary
lib/config.go Added WithResumeFile(file string) NucleiSDKOptions to update the NucleiEngine's resume file.

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant F as WithResumeFile
    participant E as NucleiEngine

    U->>F: Invoke WithResumeFile("resume.txt")
    F->>E: Set Resume field to "resume.txt"
    E-->>F: Return nil (successful execution)
Loading

Poem

I'm a rabbit, full of cheer,
Hopping in code without any fear.
A resume file now lights the track,
Helping the engine get back on track.
With a hop and a skip, hooray! 🐇✨

✨ 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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 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
Contributor

@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

🧹 Nitpick comments (2)
lib/config.go (2)

514-521: The implementation looks good but documentation could be improved.

The function follows the pattern of other option-setting functions in the codebase. However, the documentation could be enhanced to provide more context about what a resume file is used for, what format it expects, and any limitations or requirements.

Consider expanding the comment to be more descriptive, similar to other option-setting functions:

-// WithResumeFile allows setting a resume file
+// WithResumeFile allows setting a resume file path to resume scanning from a previous scan.
+// The resume file contains the progress state of a previous scan which enables
+// continuing from where the scan was stopped.

516-520: Consider adding validation for the file parameter.

Many other option-setting functions in the file include validation logic, but this function accepts any string without validation.

Add basic validation to ensure the file parameter is not empty:

func WithResumeFile(file string) NucleiSDKOptions {
	return func(e *NucleiEngine) error {
+		if file == "" {
+			return errors.New("resume file path cannot be empty")
+		}
		e.opts.Resume = file
		return nil
	}
}
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 3a3f5e2 and 485ae48.

📒 Files selected for processing (1)
  • lib/config.go (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Tests (macOS-latest)
  • GitHub Check: Tests (windows-latest)
  • GitHub Check: Tests (ubuntu-latest)

Comment on lines +516 to +520
func WithResumeFile(file string) NucleiSDKOptions {
return func(e *NucleiEngine) error {
e.opts.Resume = file
return nil
}
Copy link
Contributor

Choose a reason for hiding this comment

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

💡 Verification agent

🧩 Analysis chain

Verify if thread-safety check is needed.

Some configuration functions in this file check if the engine is running in thread-safe mode (if e.mode == threadSafe) and return an error if the option is not supported in that mode. Consider whether this option should have a similar check.


🏁 Script executed:

#!/bin/bash
# Check if other similar file-setting functions check for thread-safe mode

echo "Checking if other file-setting functions check for thread-safe mode..."
rg "e.mode == threadSafe" --context 10 lib/config.go | grep -A 10 -B 10 "func With.*File"

Length of output: 897


Action Required: Add Thread-Safety Check to WithResumeFile

Based on the output from similar functions (e.g., WithSandboxOptions and WithTemplateUpdateCallback), it’s evident that a thread-safety check is applied before setting file-related options. To maintain consistency and avoid unsupported behavior when the engine runs in thread-safe mode, consider adding a check for thread-safe mode in WithResumeFile. For example:

func WithResumeFile(file string) NucleiSDKOptions {
	return func(e *NucleiEngine) error {
		if e.mode == threadSafe {
			return ErrOptionsNotSupported.Msgf("WithResumeFile")
		}
		e.opts.Resume = file
		return nil
	}
}

Please evaluate if the resume file functionality should be restricted in thread-safe mode and update accordingly.

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.

Using resume with Nuclei SDK
2 participants