Skip to content

Fix typo in file.py"#12426

Open
Beandon13 wants to merge 1 commit into
mindsdb:mainfrom
Beandon13:fix/mindsdb-typo-20260505-3-file
Open

Fix typo in file.py"#12426
Beandon13 wants to merge 1 commit into
mindsdb:mainfrom
Beandon13:fix/mindsdb-typo-20260505-3-file

Conversation

@Beandon13
Copy link
Copy Markdown

Minor typo fix for docs/comments.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 5, 2026


Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.


I have read the CLA Document and I hereby sign the CLA


You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.

@entelligence-ai-pr-reviews
Copy link
Copy Markdown
Contributor

EntelligenceAI PR Summary

This PR corrects a spelling error in the error message returned when a file deletion fails in the HTTP API.

  • Fixed misspelling of 'occured' to 'occurred' in the delete method of mindsdb/api/http/namespaces/file.py
  • Change affects the 500 error response message for file deletion failures

Confidence Score: 5/5 - Safe to Merge

Safe to merge — this PR corrects a single-character spelling error in an error message string within the delete method of mindsdb/api/http/namespaces/file.py, changing 'occured' to 'occurred' in the 500 HTTP response body. The change is purely cosmetic to the runtime behavior, carries zero logic or security risk, and improves the professionalism of the API's error messaging. No review comments were raised and the diff scope is minimal and well-contained.

Key Findings:

  • The fix targets only a static string literal in the 500-error response of the delete method — no logic, control flow, or data handling is altered.
  • Correcting 'occured' to 'occurred' is a legitimate documentation/UX improvement that makes error messages more professional without any runtime side effects.
  • No pre-existing unresolved issues exist for this file, and the single changed line has been fully reviewed with zero findings.

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.

1 participant