Add breakpoint in get_number method

[parth-deepsource]

No description provided.

[deepsource-development]

Here's the code health analysis summary for commits afe95c8..9a5b0da. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Python	❌ Failure	❗ 8 occurences introduced 🎯 10 occurences resolved	View Check ↗

DeepSource Report Card: D

Dimension	Grade	Issues
Security	A	0
Reliability	D	2 ⚠️
Complexity	C	2
Hygiene	D	3

Focus area: Reliability — Fix the undefined `o` variable causing a runtime error in demo_code.py.

Grade capped at D due to multiple critical issues

View full report →

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[deepsource-development]

DeepSource detected 1 newly introduced issue(s) in this pull request.

[deepsource-development]

breakpoint() call enables debugging in production

The breakpoint() function intentionally pauses execution and enters a debugger. If this code is deployed to a production environment, it will halt the application, causing a denial of service. An attacker with access to the debugger could inspect application state or execute arbitrary code.

Remove the breakpoint() call before committing or deploying the code.

[deepsource-development]

DeepSource detected 1 newly introduced issue(s) in this pull request.

[deepsource-development]

breakpoint() call exposes a debugger

The breakpoint() call will halt execution and drop into a pdb debugger session. In a production environment, this can lead to a denial of service and may expose sensitive information or an interactive shell to an attacker.

Remove the breakpoint() call before committing or deploying code. It should only be used for local debugging.

[deepsource-development]

Here's the code health analysis summary for commits afe95c8..9a5b0da. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Python	❌ Failure	❗ 9 occurences introduced 🎯 10 occurences resolved	View Check ↗

DeepSource Report Card: D

Dimension	Grade	Issues
Security	A	0
Reliability	D	3 ⚠️
Complexity	C	2
Hygiene	D	3

Focus area: Reliability — Fix the critical mutable default list in `moons` causing shared state bugs in demo_code.py.

Grade capped at D due to multiple critical issues

View full report →

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[deepsource-development]

DeepSource detected 1 newly introduced issue(s) in this pull request.

[deepsource-development]

breakpoint() call can halt execution, causing denial of service

The breakpoint() function was added, which will pause code execution at this line. If this code is deployed to a production environment, it will cause the service to hang indefinitely, leading to a denial of service.

Remove the breakpoint() call before committing code. Debugging statements should not be present in shared branches or production releases.

[deepsource-io]

DeepSource Code Review

DeepSource reviewed changes in the commit range afe95c8..9a5b0da on this pull request. Below is the summary for the review, and you can see the individual issues we found as review comments.

For detailed review results, please see the PR on DeepSource ↗

PR Report Card

Security	× 1 issue		Overall PR Quality    Focus Area: Security Guidance Remove the `breakpoint()` call to prevent exposing a debug shell in demo_code.py. Grade capped at C due to critical security issue
Reliability	× 1 issue
Complexity	× 0 issues
Hygiene	× 0 issues

Code Review Summary

Analyzer	Status	Summary	Details
Python		2 new issues detected.	Review ↗
Secrets		1 existing issue fixed.	Review ↗

How are these analyzer statuses calculated?

Administrators can configure which issue categories are reported and cause analysis to be marked as failed when detected. This helps prevent bad and insecure code from being introduced in the codebase. If you're an administrator, you can modify this in the repository's settings.

[deepsource-io]

breakpoint() call halts execution, causing a potential denial of service

The breakpoint() function is intended for interactive debugging and should not be present in committed code. Its presence can lead to a denial of service by halting the execution of the application, making it unresponsive if triggered in a production environment.

Remove the breakpoint() call before merging this change.

[deepsource-development]

DeepSource Code Review

DeepSource reviewed changes in the commit range afe95c8..9a5b0da on this pull request. Below is the summary for the review, and you can see the individual issues we found as review comments.

For detailed review results, please see the PR on DeepSource ↗

PR Report Card

Security	× 1 issue		Overall PR Quality    Focus Area: Security Guidance One critical security issue should be fixed immediately: a `breakpoint()` call in `demo_code.py` (1 occurrence) will halt execution and should be removed or protected behind a debug-only guard before deploying to production. Grade capped at C due to critical security issue
Reliability	× 1 issue
Complexity	× 0 issues
Hygiene	× 0 issues

Code Review Summary

Analyzer	Status	Summary	Details
Python		2 new issues detected.	Review ↗
Secrets		1 existing issue fixed.	Review ↗

How are these analyzer statuses calculated?

Administrators can configure which issue categories are reported and cause analysis to be marked as failed when detected. This helps prevent bad and insecure code from being introduced in the codebase. If you're an administrator, you can modify this in the repository's settings.

[deepsource-development]

breakpoint() call can halt execution and cause Denial of Service

The breakpoint() call will pause program execution and enter the Python debugger. If this code is deployed to a non-interactive environment, such as a production server, the application will hang indefinitely when get_number() is called, leading to a denial-of-service.

Remove the breakpoint() call before committing code to be used in production environments.