William Woodruff

Unrelated, but just in case others have the same problem: it looks like the root "problem" here is that MusicBrainz uses the formatting character range for many artists/albums/tracks, which `beet`...

I'm not sure if it's helpful or not, but `@property` does something weird to preserve annotations -- they get added to the underlying `property.fget` callable, like so: ```py >>> A.foo.fget.__annotations__...

Hi @halsalem. A couple of things: * The error message in your screenshot is in Clang, not our build system. In particular, it's (one of) the error messages that commonly...

Hmm. `pov.c` is over 30MB of C, so it's very possible you're running out of memory even with 16GB due to the added coverage instrumentation. This isn't something we've tested;...

> I don't need the "povs" for challenges how can I discard other folders "povs" from compiling or building. There currently isn't an easy way to do that. Your best...

> How can change the CMakeLists.txt to not compile the povs? Take a look at the `buildCB` function. It calls `buildPOV` in a loop for each POV discovered for the...

I don't believe anyone is currently maintaining the poller scripts, sorry. We don't currently use them internally. If you make any progress, please feel free to submit a PR with...

The `ELFCLASS32` error means that you're trying to load a 32-bit library into a 64-bit process. If you built the challenges as 32-bit, you'll probably need to use a 32-bit...

> How can I use 32-bit runtime with these challenges? That depends on what you're doing. Did you intend to build these challenges as 32-bit? If you did, then you'll...

Ah, my bad -- it looks like the build *does* do everything as 32-bit. Hmm. Your best bet is probably to get a 32-bit build of Python. You might have...