Went back to Araps for Easter!
Trad lead on six routes (up to grade 13, most two pitches), trad second on four routes (up to grade 19) including the epic Watchtower Crack multi.
I don't think I posted on here about it, but I was at Araps last weekend too. Leading on Panzer (gr12 multi) and some fun single pitch routes.
OK i can't focus on work and keep looking at this repo.
So after every "subagent" runs, claude code creates another "agent" to check on whether the first "agent" did the thing it was supposed to. I don't know about you but i smell a bit of a problem, if you can't trust whether one "agent" with a very big fancy model did something, how in the fuck are you supposed to trust another "agent" running on the smallest crappiest model?
That's not the funny part, that's obvious and fundamental to the entire show here. HOWEVER RECALL the above JSON Schema Verification thing that is unconditionally added onto the end of every round of LLM calls. the mechanism for adding that hook is... JUST FUCKING ASKING THE MODEL TO CALL THAT TOOL. second pic is registering a hook s.t. "after some stop state happens, if there isn't a message indicating that we have successfully called the JSON validation thing, prompt the model saying "you must call the json validation thing"
this shit sucks so bad they can't even CALL THEIR OWN CODE FROM INSIDE THEIR OWN CODE.
Look at the comment on pic 3 - "e.g. agent finished without calling structured output tool" - that's common enough that they have a whole goddamn error category for it, and the way it's handled is by just pretending the job was cancelled and nothing happened.
@zl2tod Motorcycle UX designers are awful, so these two switches do many things, depending on whether you press one, or hold one, or press one while holding the other, or hold both at once.
Because of how the unit behaves, I'm pretty sure the error is on the input side of the controller, not the output.
I'm struggling to fix an electronic circuitboard -- can anyone offer suggestions?
It's a circuitboard from a motorcycle instrument panel, manufactured in 2019. It has a layer on each side. I don't know if it has any internal layers.
There are two push switches, and the controller seems to think one of the switches is continually pressed.
Testing the switch with a multimeter, it looks fine. It's normally open, and when pressed, closes the circuit with very low resistance. This is identical to the other, working, button.
The circuitboard has some test points, including for GND and the switches.
When my multimeter is connected to GND and the test point for the bad switch, the results appear good.
ie. No connection normally, and then a very low resistance connection when pressed.
I'm trying to work out what else could be the problem. Maybe the connection to the microcontroller has shorted out against a neighbouring connection?
I can't visually see anything like that, but I don't have a circuit diagram and the circuitboard has a layer on top of it obscuring the tracks.
Maybe a track has somehow broken inside the circuitboard and shorted to ground? I can't see any visual damage, and I guess I wouldn't know how to fix this even if there was.
Are there other possibilities I'm missing?
PSA: The Amazon wishlist doxing threat is much greater and more immediate than folks might realize. Attack works like this:
Stalker who wants your address opens an Amazon seller account and lists themselves as a third party seller for any item on your public wishlist. Then, they order the item from themselves as a gift for you. Bam, they have your address.
In particular, attack does not depend on an existing third party seller having poor PII handling hygiene, like the articles have implied.
jonny (good kind)
Cassandrich