From 2427ecb7125f829bd1df0bbf3e4e7f3b5a786cba Mon Sep 17 00:00:00 2001 From: j Date: Thu, 8 Jun 2023 04:54:23 +0200 Subject: [PATCH] Update page '6-7-2023 Cohort 2 Sync Notes' --- 6-7-2023 Cohort 2 Sync Notes.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/6-7-2023 Cohort 2 Sync Notes.md b/6-7-2023 Cohort 2 Sync Notes.md index c8763e0..efe4d18 100644 --- a/6-7-2023 Cohort 2 Sync Notes.md +++ b/6-7-2023 Cohort 2 Sync Notes.md @@ -1,12 +1,19 @@ 1715h Started late + 1730h Review of VSC git UI, look at the commit graph with `git log --graph --oneline` + 1745h Fixed up wording in homework assignment, looked at Max's submission + 1800h VSC debugger demonstration * Pick the file you want in the Explorer view * Switch to the Run and Debug view * While you have the file you want to debug open, click the run button in the upper left-hand corner. * Set breakpoints by clicking to the left of any source code line that will be executed. The debugger will stop when it hits a breakpoint. * Don't forget to check the types of your arguments and the callers by using the call stack. Even if the debugger says everything is what you expect in the function you're debugging, if the caller is wrong, you will not get the results you expect. + 1815h * Stepping in the debugger is usually either step into (trace into any called functions), or step over (trace to the next line). -* Found a problem with the test suite +* Found a problem with the test suite: https://gogs.gtsplab.com:5432/j/python-test/src/main/test13.py#L57 (11 -> bi11) +* Started getting nonsense behavior, like running the exact same file twice and getting different results +* Root cause was that Scott checked bytecode into the repository +* Added .gitignore file to the repository to stop this from happening again \ No newline at end of file