Debug
A conversational debugger and drop-in replacement for pdb. Python's default interactive debugging session is already a crude conversation with your program or interpreter, in a sense - this just lets your program communicate to you more effectively.
Quickstart
Here's a broken version of bubble sort that places a duck()
call on the
second to last line where you might normally call breakpoint()
.
from roboduck import duck
def bubble_sort(nums):
for i in range(len(nums)):
for j in range(len(nums) - 1):
if nums[j] > nums[j + 1]:
nums[j + 1] = nums[j]
nums[j] = nums[j + 1]
duck() # <--------------------------- instead of breakpoint()
return nums
nums = [3, 1, 9, 2, 1]
bubble_sort(nums)
Classes
CodeCompletionCache
Stores values related to the last completion from DuckDB in a way that
a. our duck
jupyter magic can access, and
b. allows us to easily reset all defaults
The magic only needs to access it in Paste mode (-p flag) to insert the fixed code snippet into a new code cell.
Source code in lib/roboduck/debug.py
48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 |
|
Attributes
last_completion = []
class-attribute
instance-attribute
last_explanation = []
class-attribute
instance-attribute
last_code = []
class-attribute
instance-attribute
last_new_code = []
class-attribute
instance-attribute
last_code_diff = []
class-attribute
instance-attribute
last_session_id = ''
class-attribute
instance-attribute
last_extra = []
class-attribute
instance-attribute
Functions
update_cache(**kwargs)
classmethod
Source code in lib/roboduck/debug.py
76 77 78 79 80 81 82 83 84 85 86 87 88 89 |
|
get(name, newest=True)
classmethod
Get the first/last truthy value of a given attribute if one exists, e.g. the most recent code completion.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
name |
str
|
Attribute name. Should be a class attribute like 'last_code'. |
required |
newest |
bool
|
Determines whether to get the first (newest=False) or last (newest=True) truthy value. |
True
|
Returns:
Type | Description |
---|---|
any
|
The first/last truthy value of the requested class attribute. If no truthy values are found, we return None. |
Examples:
# Get the most recent LLM response.
CodeCompletionCache.get('last_completion')
Source code in lib/roboduck/debug.py
91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 |
|
DuckDB
Bases: Pdb
Conversational debugger powered by LLM (e.g. gpt-4o-mini or gpt-4). Once you're in a debugging session, regular pdb commands will work as usual but any user command containing a question mark will be interpreted as a question for the lLM. Prefixing your question with "[dev]" will print out the full prompt before making the query (mostly useful when working on the library).
Source code in lib/roboduck/debug.py
130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 |
|
Attributes
prompt = '>>> '
instance-attribute
duck_prompt = '[Duck] '
instance-attribute
comment_prefix = '>'
instance-attribute
query_kwargs = {}
instance-attribute
color = color
instance-attribute
dev_color = 'blue' if self.color == 'red' else 'red'
instance-attribute
chat = Chat.from_template(**chat_kwargs)
instance-attribute
full_context = 'full_code' in self.field_names()
instance-attribute
prompt_name = prompt_name
instance-attribute
repr_func = partial(truncated_repr, max_len=max_len_per_var)
instance-attribute
silent = silent
instance-attribute
parse_func = parse_func
instance-attribute
prev_kwargs_hash = None
instance-attribute
uuid = str(uuid.uuid1())
instance-attribute
Functions
error(line)
Add a hint when displaying errors that roboduck only responds to questions in natural language.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
line |
str
|
|
required |
Source code in lib/roboduck/debug.py
251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 |
|
field_names(key='')
Get names of variables that are expected to be passed into default user prompt template.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
key |
str
|
Determines which user prompt type to use. By default, roboduck
provides "contextful" (which will include the source code, variable
values, and the stack trace when appropriate) and "contextless"
(which includes only the user question). Falls back to a
default defined in the prompt template, in this case
"contextful". Keeping the actual default as an empty string here
means that if we defined a new prompt with different keys, we
don't need to define a new subclass with a custom field_names
method, we just need to pass in the desired |
''
|
Returns:
Type | Description |
---|---|
set[str]
|
|
Source code in lib/roboduck/debug.py
270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 |
|
onecmd(line)
Base class describes this as follows:
Interpret the argument as though it had been typed in response to the prompt. Checks whether this line is typed at the normal prompt or in a breakpoint command list definition.
We add an extra check in the if block to check if the user asked a question (or made a statement that they want to send to the LLM rather than being treated as pdb command, as indicated by a self.comment_prefix prefix). If so, we ask gpt. If not, we treat it as a regular pdb command.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
line |
str or tuple
|
If str, this is a regular line like in the standard debugger. If tuple, this contains (line str, stack trace str - see roboduck.errors.post_mortem for the actual insertion into the cmdqueue). This is for use with the debug_stack_trace mode. |
required |
Source code in lib/roboduck/debug.py
425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 |
|
ask_language_model(question, stack_trace='', verbose=False)
When the user asks a question during a debugging session, query gpt for the answer and type it back to them live.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
question |
str
|
User question, e.g. "Why are the first three values in nums equal to 5 when the input list only had a single 5?". (Example is from a faulty bubble sort implementation.) Could also be a comment/statement if the user prefixes their reply with self.comment_prefix. |
required |
stack_trace |
str
|
When using the "debug_stack_trace" prompt, we need to pass a stack trace string into the prompt. |
''
|
verbose |
bool
|
If True, print the full gpt prompt in red before making the api call. User activates this mode by prefixing their question with '[dev]'. This overrides self.silent. |
False
|
Source code in lib/roboduck/debug.py
461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 |
|
precmd(line)
We need to define this to make our errors module work. Our post_mortem function sometimes places a tuple in our debugger's cmdqueue and precmd is called as part of the default cmdloop method. Technically it calls postcmd too but we don't need to override that because it does nothing with its line argument.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
line |
str or tuple
|
If a tuple, it means roboduck.errors.excepthook is being called and an error has occurred. The stack trace is passed in as the second of two items, where the first item is the same object that is normally passed in. |
required |
Source code in lib/roboduck/debug.py
561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 |
|
print_stack_entry(frame_lineno, prompt_prefix='\n-> ')
This is called automatically when entering a debugger session and it prints a message to stdout like
> <ipython-input-20-9c67d40d0f93>(2)<module>()
-> print + 6
In silent mode (like when using the roboduck logger with stdout=False), we want to disable that message. When silent=False, this behaves identically to the standard pdb equivalent.
Source code in lib/roboduck/debug.py
581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 |
|
Functions
duck(**kwargs)
Roboduck equivalent of native python breakpoint(). The DuckDB docstring is below. Any kwargs passed in to this function will be passed to its constructor.
Source code in lib/roboduck/debug.py
605 606 607 608 609 610 611 |
|