Skip to content

Add breakpoint in get_number method #7

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.

Sign up for GitHub

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

Open
parth-deepsource wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add breakpoint in get_number method #7

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions demo_code.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,7 @@ def __init__(self):
self.limits = (1, 10)

def get_number(self, min_max):
breakpoint()
Copy link

@deepsource-development deepsource-development bot Feb 6, 2026

Choose a reason for hiding this comment

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

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.

Copy link

@deepsource-development deepsource-development bot Feb 6, 2026

Choose a reason for hiding this comment

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

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.

Copy link

@deepsource-development deepsource-development bot Feb 6, 2026

Choose a reason for hiding this comment

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

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.

Copy link

@deepsource-io deepsource-io bot Feb 18, 2026

Choose a reason for hiding this comment

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

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.

Copy link

@deepsource-development deepsource-development bot Feb 18, 2026

Choose a reason for hiding this comment

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

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.

raise NotImplemented

def smethod():
Expand Down