dmesg --follow
[ 66338820.000 ] posts.x: Full talk on where vision models substitute pattern matching for actually looking, and what that costs in robotics, construction, and design:  |   [ 66338820.000 ] posts.x: Show a frontier model a chessboard with only part of it visible and ask how many white squares it has. It says 32, because a full chessboard always…  |   [ 66323520.000 ] posts.x: When the speed of models increases to the point where we can stay in flow whilst working in a single session, we'll see another inflection point in…  |   [ 66321000.000 ] posts.x: Full talk on the nine techniques behind Impeccable, from adversarial sub-agents to compiling one skill across Claude Code, Codex, and Cursor:  |   [ 66321000.000 ] posts.x: Banning "Inter" or "Roboto" from an AI design model doesn't make it more creative, it just nudges the model to the next-best font in the same…  |   [ 66317580.000 ] posts.x: @TrelisResearch @dialt_ai Well done, you!  |   [ 66260400.000 ] posts.x: Full talk on two vLLM Mamba bugs, the scheduler ordering issue and the int32 overflow, and how the AI21 team traced both through logprobs.  |   [ 66260400.000 ] posts.x: Two production bugs in vLLM's Mamba support produced zero crashes and zero errors, only confidently wrong output. @aiDotEngineer published "Two Bugs…  |   [ 66257640.000 ] posts.x: @mattpocockuk @davekiss @poteto @dexhorthy @emilkowalski 🤣 brilliant!  |   [ 66255540.000 ] posts.x: @yoheinakajima 👊  |   [ 66254340.000 ] posts.x: @yoheinakajima Shockingly quick response!  |   [ 66251100.000 ] posts.x: Full talk on FriendliAI's four-pillar rebuild for agent inference, from prefix caching to cache-aware routing:  |   [ 66251100.000 ] posts.x: A tower defense game, built by two different models on the same coding-agent task: one run cost $1.50, the other 27 cents. @bgchun, founder and CEO…  |   [ 66243600.000 ] posts.x: Full talk on what's changed in quantization, KV caching, and speculative decoding since Philip's book came out:  |   [ 66243600.000 ] posts.x: A quantization method called TurboQuant promised to shrink the KV cache down to four bits this year, then turned out to cut tokens per second by more…  |  
corey@gallon.me:~/til$
apropos
/writing 7 pieces · long form /til 27 notes · small /conferences 15 write-ups /snips 2 · links, quotes /projects 61 things that run /speaking 3 talks · rooms /courses 1 taught · cohorts about.md who this is
CONTENTS 1 min
Debugging Python Tests in VSCode FIG 1 FIG 2Command Palette Python Configure T FIG 3Command Palette Select Framework.p FIG 4Right Click Debug Test.png
~/til/debugging-python-tests-in-vscode.md
-rw-r--r-- 95 words 1 min4 figures 2024-09-15

Debugging Python Tests in VSCode

FIGURE 1 ⋅ Debugging Python Tests in VSCode

VSCode offers native test capabilities that are quite useful. Testing Python in Visual Studio Code

It doesn’t, however, recognize your Python tests by default. You must configure it to do so for each project.

Command Palette (CTRL+SHIFT+P) → “Python: Configure Tests” →

Command Palette Python Configure Tests.png
FIGURE 2 ⋅ Command Palette Python Configure Tests.png

Select the framework you’re using:

Command Palette Select Framework.png
FIGURE 3 ⋅ Command Palette Select Framework.png

Now, you get all of the testy-goodness that VSCode has to offer for Python.

In this case, I wanted to debug a specific test. Super easy! Just drop breakpoints in the test where you want them, then run “Debug Test”.

Right Click Debug Test.png
FIGURE 4 ⋅ Right Click Debug Test.png

The “Test Explorer” is also quite useful.

corey@gallon.me:~$ tail -f /writing Attach to the stream. An email when I have something worth sending. Replies encouraged!
corey@gallon.me:~$ ls -lt /til ↑2024-10-06 raco: Racket's Package Management System (and More)
▸2024-09-15 Debugging Python Tests in VSCode ⋅ you are here
↓2024-09-15 Debugging Python CLI Arguments in VSCode