David Vo

Well, luckily all the base classes are listed in the docs anyway, so it's not a major problem if we bikeshed this.

Probably best to save the old `sys.excepthook` in case something else wants an excepthook as well.

Anything interesting in `dmesg`?

I think this is expected behaviour when you SSH in as lvuser. From what I've heard, the process that runs automatically as frcUserProgram has more privileges than a regular lvuser...

I'm quite confused as to what exactly pybind11 is doing here, given that `Sendable::InitSendable` takes a reference…

I managed to get a native code backtrace: ``` #1 0x00007ffff34266db in pybind11::detail::type_caster_generic::cast (_src=_src@entry=0xf73fa8, policy=policy@entry=pybind11::return_value_policy::copy, parent=..., parent@entry=..., tinfo=tinfo@entry=0xdc1380, copy_constructor=0x0, move_constructor=move_constructor@entry=0x0, existing_holder=0x0) at /home/ubuntu/frc/robotpy/venv/lib/python3.8/site-packages/robotpy_build/pybind11/include/pybind11/cast.h:548 #2 0x00007ffff343fced in pybind11::detail::type_caster_base::cast (parent=..., policy=pybind11::return_value_policy::copy, src=0xf73fa8)...

It is rather odd that pybind11 wants to take a copy of SendableBuilder...

> Doesn't find it, so it looks at the holder and sees it's a shared_ptr. Since it can't just reference it, it has to copy the instance? Note that it...

This upstream issue seems related: - https://github.com/pybind/pybind11/issues/1241

Duplicate of #1257?