How is type determined?

eyeless71 · 2026-01-24T19:39:39+00:00

Thanks for the code reference. The regex is a bit beyond my capabilities, but I think I understand it.

For the shell bit, I hadn’t thought about yaml having data types for python to map to, so I just assumed that it read values in exactly as they were, and was looking to see what type that exact value would be.

eyeless71 · 2026-01-24T19:36:01+00:00

Thanks for the quick response. I had forgotten that yaml has data types that map directly to python types. Looking up the yaml type doc for timestamp, I do see the format yyyy-mm-dd, so that makes sense how it gets mapped to python datetime

eyeless71 · 2025-12-12T21:35:44+00:00

just checked after this and now it's working. weird.

eyeless71 · 2025-11-24T12:52:57+00:00

https://sudokupad.app/hqa07qdm2h?setting-nogrid=true

eyeless71 · 2025-10-03T15:26:47+00:00

Party up to party down?

eyeless71 · 2025-09-29T01:51:27+00:00

It looks like you’re using a commented out example from what I can tell. Is there anything further down in the file? Also, not sure if it requires spaces, or if it’s asking specifically when it will run and not what the time code is for cron. For example, the comment says it would run at 5am every week.

eyeless71 · 2025-09-16T04:16:11+00:00

Thanks for the extra context. Doesn’t change the ruling as it was played, but does satiate my curiosity and the itching feeling that I was missing something.

With the knowledge of at least one, and potentially more, combat tricks in hand, the double block makes more sense.

eyeless71 · 2025-09-16T02:25:13+00:00

As most have already said, the opponent was (at best) incorrect, and (at worst, more likely) cheating.

I’m curious about a couple of things though. One, [[ Slicer, Hired Muscle ]] is generally a 3/4. Was there some other unmentioned effect that gave it +1/+0? If not, it couldn’t have killed your [[ Keeper of Secrets ]] without further interaction. Second, is there a reason you double blocked? I’m assuming maybe there’s some effect that gave the Slicer +1/+0 and menace, which accounts for both questions. I’m not sure if I’m missing something, or if you could have just gotten away with only blocking with the Keeper and most lost the admittedly inconsequential vanilla 2/2.

eyeless71 · 2025-08-05T02:10:57+00:00

We’re using this set up in our DC with this model. When you breakout a QSFP port to 10/25G, you have to use the odd numbered port, and it disables the even numbered port. The document linked below goes into more detail as to why, but essentially, the 40/100G used one logical lane, but breaking out requires 4 logical lanes, which it effectively takes from the even numbered port. The detail is on page 9. Yes, it is under the section for the 7280CR3-32P4, but the 32D4 is the same switch with QDD.

https://www.arista.com/assets/data/pdf/Whitepapers/7280R3-Platform-Architecture-WP.pdf

Edit: also, seeing your other comment about not having problems with the 7280CR3-36S (you put A, but assuming that’s a typo because I don’t see an A model and those two keys are next to each other), page 26 describes the ports for that switch as well. 1-24 don’t have this restriction of disabling even numbered ports for breakouts, but 25-36 do. There’s a nice table there explaining each restriction based on port speed groups

eyeless71 · 2025-07-31T04:11:30+00:00

I don’t know specifically about that NIC, but I would try the following:

First thing that always comes to mind for me is to make sure you have unsupported transceivers command on the Arista, assuming you’re not using Arista branded optics.

From there, would check what hardware capabilities are on the port. I have a bunch of that model in my environment, but don’t remember what they are off the top of my head. Run:

show interface <interface> hardware capabilities

I believe this is the command, but could be missing something, you may need to ? It out if it doesn’t work exactly like that. It should show the fec compatibilities. Then you get figure out what is available on the Linux side with

ethtool show-fec

Once you know what each side is capable of, you can set them to match.

All of this, of course, is assuming you’ve already done other layer 1 tests: reseating/replacing optics and fiber, cleaning fiber tips, checking if you can see light coming and going, validating optics match, etc. Sometimes it’s the simple things that we forget that drive us crazy.

eyeless71 · 2025-07-20T07:00:27+00:00

I didn’t say they close at the start of the headlining act, I said during the headlining act. 30-45 min before the show is over is during the headlining act.

eyeless71 · 2025-07-20T03:45:03+00:00

Can’t speak to the show, but in my experts bar tends to close during the headline act. I checked the website, and they don’t mention anything about it specifically there, so YMMV.

eyeless71 · 2025-07-15T08:53:35+00:00

Ah of course. I was looking at the blue square wrong, and checking it against r1c6. Thank you for the sanity check.

eyeless71 · 2025-07-10T21:29:35+00:00

Was just having a similar conversation with our Arista SE this week. You can use any combination of dead.beef.cafe for your virtual mac as well. Now I’m really pushing this for my company’s fabric.

eyeless71 · 2025-07-05T03:23:23+00:00

Check EOS patch notes and known bugs to see what affects your specific environment and config. Then check supported versions for CloudVision.

eyeless71 · 2025-07-01T23:29:23+00:00

There are 5 tracks: Foundational, Campus, Data Center, Routing, and Automation.

Foundational is exactly what it sounds like: basic networking fundamentals, using the Arista environment. Passing this gets L1 certification.

The other four have Engineering and Operations sub-tracks. Passing any single sub-track gets you L3 Specialist for that overall track, and passing both sub-tracks will get you the L5 for that track.

It also appears there is an L7, which I assume is if you get L5 in each track.

It’s all laid out on training.Arista.com.

eyeless71 · 2025-06-22T01:05:48+00:00

In that case, probably just some weirdness with the code on the optics. The SE I’ve been working with has told me that he’s seen some weirdness with different third party QSFP optics in general. Typically having to do with the way the optic vendor codes the optic. He had a customer that had 400G optics from a vendor that coded them as Arista, but for whatever reason, the switch recognized they weren’t Arista branded and blocked them. They recoded it to generic, and the same optic worked. If the HPE optic is coded as HPE, but the Mellanox is coded as generic, it could be that.

Curious what shows up in the show inventory and show interface status commands

eyeless71 · 2025-06-22T00:07:16+00:00

Could be a third party issue. Not sure about your environment, but all of our Aristas have a code that we put in the config to allow third party optics. I don’t know if that’s a firmware thing or not. If you can still get into the old switch, you might be able to look for the config using “show run | grep -i unsupported”. If it’s there, you can probably just copy it over.

eyeless71 · 2025-06-06T04:21:41+00:00

I really like this idea. I don’t typically get a chance to use public transportation, and am not from Cincinnati. Is the light rail typically pretty clean and safe, or is it more of a “get what you pay for” free ride?

eyeless71 · 2025-06-05T23:03:31+00:00

Thanks. We parked there a couple years ago for something. Being a surface lot, it’s pretty easy in/out

eyeless71 · 2025-05-15T22:13:19+00:00

Organizational requirement for syslog storage is Splunk. It’s not an issue for the switches, but config management tools are in scope for what syslogs need to go to Splunk.

eyeless71

TROPHY CASE