Skip to content

useLocalCrawling & maxDepth parameters are ignored #5957

Closed as not planned
Closed as not planned
useLocalCrawling & maxDepth parameters are ignored#5957
Assignees
sestinj
Labels
area:indexingRelates to embedding and indexingkind:bugIndicates an unexpected problem or unintended behaviorstale

Description

@vincentkelleher
vincentkelleher
opened on Jun 3, 2025

Before submitting your bug report

Relevant environment info

- OS: Ubuntu 24.04.2 LTS
- Continue version: 1.0.11
- IDE version: 1.100.2
- Model: Not relevant
- config:
  
  docs:
  - name: Continue.dev YAML Migration Documentation
    startUrl: https://docs.continue.dev/yaml-migration
    maxDepth: 1
    useLocalCrawling: true

Description

When I define the maxDepth & useLocalCrawling parameters for document indexing, they are ignored and their default values are used.

I've noticed it while using Continue.dev so I also checked within a debugging session and saw those values weren't mapped from the YAML configuration.

To reproduce

Append the configuration snippet above to your config.yaml file and write a prompt that references that document, you will notice that pages deeper than the first level are used.

A debugging session in the DocsService is ideal to notice this.

Activity

  1. sestinj
    self-assigned this
    on Jun 3, 2025
  2. dosubot
    added
    area:indexingRelates to embedding and indexing
    kind:bugIndicates an unexpected problem or unintended behavior
    on Jun 3, 2025

  3. vincentkelleher commented on Jun 3, 2025

    @vincentkelleher
    vincentkelleher
    on Jun 3, 2025
    ContributorAuthor

    I've opened #5958 about this issue 😇

  4. vincentkelleher commented on Jun 12, 2025

    @vincentkelleher
    vincentkelleher
    on Jun 12, 2025
    ContributorAuthor

    Quick bump for this tiny issue/MR 👋

  5. github-actions commented on Sep 11, 2025

    @github-actions
    github-actionsbot
    on Sep 11, 2025 – with GitHub Actions
    Contributor

    This issue hasn't been updated in 90 days and will be closed after an additional 10 days without activity. If it's still important, please leave a comment and share any new information that would help us address the issue.

  6. github-actions
    added
    stale
    on Sep 11, 2025

  7. github-actions commented on Sep 21, 2025

    @github-actions
    github-actionsbot
    on Sep 21, 2025 – with GitHub Actions
    Contributor

    This issue was closed because it wasn't updated for 10 days after being marked stale. If it's still important, please reopen + comment and we'll gladly take another look!

  8. github-actions
    closed this as not plannedon Sep 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area:indexingRelates to embedding and indexingkind:bugIndicates an unexpected problem or unintended behaviorstale

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions