Category archives: Snaking
Discussions of programming, particularly of programming Python
New TwistedSNMP available (Allowing you to pass maxRepetitions into your Get Bulk requests)
Written by
on
in
Snaking.
I haven't had a chance to test this theory yet, but it makes so much sense...
When doing get bulk requests (which are done once for each modem on all non-intensive scans in Cinemon), the default behaviour for an agent is to encode 255 records for each requested field. That is, if you are requesting ...
Ruminations on going back to Windows for a day
Written by
on
in
Snaking.
Been working in Windows all day (good old reliable Windows ;) ). I'd forgotten how much more worn-in my working environment is here, everything set up for two-key access, everything defaulting to opening in the right directory, every tool winnowed from the pack over years of Darwinian selection, every device "just working", without few if ...
A day passes, only one official 'item' crossed out, and it's not a key one (Spent most of the day in auditing and cleanup trying to find memory leak...)
Written by
on
in
Snaking.
Did rather a lot of cleanup of the code today. Finished a number of "polish" elements (e.g. links upward in the hierarchy, retaining hierarchy names and comments through upload/download cycles, that kind of thing). Confirmed that email alerts do work when the email account is set up.
Last task of the day was sitting down ...
Just to torment me, the Windows install goes flawlessly (Clickety-click, installation trick...)
Written by
on
in
Snaking.
Even updated the viewer to allow for picture-in-picture (though I don't have cable-tv-cables or audio-cables to make that work yet). Linux may be stable and fast, but Windows still has it beat on driver support.
Anyway, back to work; going to be a long day I'm guessing. There's no food in the house (didn't get ...
Bleep, that's not what was supposed to happen (What should have been a trivial install of common hardware winds up screwing up core functionality...)
Written by
on
in
Snaking.
Well, I spent about 1.5 hours working on getting the new TV card working (about 1/2 hour longer than I'd intended). Unfortunately, to do that I needed to recompile my kernel (gods what a stupid system that is, honestly), and something wound up upsetting the magic that let the tablet work. Have spent almost 4 ...
Well, that's at least one leak fixed (Now just need to run for 4 or 5 hours to test it)
Written by
on
in
Snaking.
Found a small leak. Basically I keep a table to all streets with (num,apt) indexing lists of modems at that location (normally only a single modem). The code to do that, however, was assuming that it was starting from scratch (i.e. at system load time), whereas these days the locations are re-loaded every 20 minutes ...
Just because it looks so beautiful... (Well, I think so anyway...)
Written by
on
in
Snaking.
You'll need an SVG browser for this one, but I figure it's about time everyone had one anyway :) .
Dratted local minima (Rumours of the leak's demise are unfortunately exaggerated)
Written by
on
in
Snaking.
Bleep. There was a dip at 6 hours, but after 20 minutes or so it started climbing again, so we have an unusable product (demo is still fine, it's been running for 17 hours now).
Worse, though, there was a group that went offline, but I got no email. Of course, I forgot to give ...
Ding dong the leak is dead (The wicked leak, the wicked leak... though it's evil sister the database error is still threatening Dorothy...)
Written by
on
in
Snaking.
Well, it takes approximately 6 hours, but it does eventually reach a steady state for memory consumption. While waiting for it to stabilize I implemented the device-hierarchy. Unfortunately, I'm now seeing hard-hangs every once in a while on my machine (looks like yet another database-driven problem, as it's occurring just after the hierarchy import completes ...
2-hour test-debug cycles are annoying (Not enough time to do anything significant, not enough to work on another project, but way too much to just sit waiting...)
Written by
on
in
Snaking.
Been working on the memory-leak problem. Problem is, the system is supposed to "leak" memory for ~ 2 hours as it scans each modem and records it's values. I think I may have solved it 2 hours ago, but I really won't know for another hour or more (even then, the rate of the leak ...
Mike C. Fletcher, the VRPlumber, is a philosopher of design turned computer programmer based in Toronto, Canada. He works primarily in the Python programming language, and maintains a large number of Open Source software packages. You can reach him at: mcfletch@vrplumber.com.