^hT SrSrSrSrSrSr\S\S\S\S\S\S3 r\S\S\S\S\S3 r\S\S3rS\ S\ S \ 4S jr g ) zYou are a debugging assistant. You will be given a Python stack trace for an error and answer questions related to the root cause of the error. aCall the `pdb` function to run Pdb debugger commands on the stopped program. You may call the `pdb` function to run the following commands: `bt`, `up`, `down`, `p expression`, `list`. Call `pdb` to print any variable value or expression that you believe may contribute to the error. aCall the `info` function to get the documentation and source code for any variable, function, package, class, method reference, field reference, or dotted reference visible in the current frame. Examples include: n, e.n where e is an expression, and t.n where t is a type. Unless it is from a common, widely-used library, you MUST call `info` exactly once on any symbol that is referenced in code leading up to the error. zCall the `slice` function to get the code used to produce the value currently stored a variable. You MUST call `slice` exactly once on any variable used but not defined in the current frame's code. z=Call the provided functions as many times as you would like. aThe root cause of any error is likely due to a problem in the source code from the user. Explain why each variable contributing to the error has been set to the value that it has. Continue with your explanations until you reach the root cause of the error. Your answer may be as long as necessary. End your answer with a section titled "##### Recommendation\n" that contains one of: * a fix if you have identified the root cause * a numbered list of 1-3 suggestions for how to continue debugging if you have not  supports_flowtake_the_wheelreturncBU(aU(a[$[$[$)N)_wheel_and_slice_wheel_no_slice _no_wheel)rrs T/home/james-whalen/.local/lib/python3.13/site-packages/chatdbg/custom_pdb/prompts.pypdb_instructionsr Js # #" "N) _intro _pdb_function_info_function_slice_function_take_the_wheel_instructions_general_instructionsrrr boolstrr r r rs            D$3r