crewAIInc / crewAIInc/crewAI

Typo: 'occured' in brightdata dataset tool error messages

Open Beginner friendly
#7,598 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
58.8k
Forks
8.5k
Avg merge
1d 15h
Merged PRs (30d)
109

Description

AI-generated contribution: authored with AI assistance (per the Contributing guide). Please apply the llm-generated label — I don't have permission to add labels.

Description

Two error messages in lib/crewai-tools/src/crewai_tools/tools/brightdata_tool/brightdata_dataset.py misspell "occurred" as "occured". These strings are returned to callers as tool output on Bright Data API failures, so the misspelling is user-visible.

Steps to Reproduce

  1. Use BrightDataDatasetTool and trigger a TimeoutError or BrightDataDatasetToolException inside get_dataset_data_async.
  2. Observe the returned tool output: Timeout Exception occured in method : get_dataset_data_async. Details - ...

Expected behavior

The messages should spell "occurred" correctly.

Screenshots/Code snippets

# lib/crewai-tools/src/crewai_tools/tools/brightdata_tool/brightdata_dataset.py, lines 593 and 596
return f"Timeout Exception occured in method : get_dataset_data_async. Details - {e!s}"
f"Exception occured in method : get_dataset_data_async. Details - {e!s}"

Operating System

Windows

Python Version

3.13

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Open lib/crewai-tools/src/crewai_tools/tools/brightdata_tool/brightdata_dataset.py and inspect the two error-message strings around lines 593 and 596 in get_dataset_data_async. Correct the user-visible spelling in both TimeoutError and BrightDataDatasetToolException outputs, then verify both messages use the expected wording.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api
Issue type
Bug
Difficulty
1/5
Estimated time
Under an hour
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
92/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.