Jake Herrmann

I'm having the same problem with Python 3.8.2 on Pop!_OS 20.04 LTS. I'll try to debug the problem further and see if I can learn anything useful.

It looks like `fdct2.fwd` (defined in `fdct2.py`) calls `fdct2_wrapper` (defined in `fdct2_wrapper.py`) which calls `_fdct2_wrapper.fdct2_wrapper`, at which point the memory leak occurs. It looks like `_fdct2_wrapper` is a module imported...

Nevermind. It turns out my input array was just too large. My computer ran out of memory when I called `fdct2.fwd` on a 16384x16384 array but it worked fine when...

Also seeing this bug on Pop!_OS 22.04 LTS. Is there any other information we can provide that would help find a solution?

Also seeing this on Debian 12 with GNOME 43.9 on Wayland, with the dock in the vertical-left position, set to always be visible. I have tried locking/unlocking the screen and...

I enabled auto-hide in dash-to-dock since I realized I don't need the dock always visible anyway, but I also happened to stumble across this setting in dconf Editor and I'm...

I think your interpretation is correct as long as the player who issued the challenge is not the player being assassinated. For example, if player 1 has the assassin and...

@JackieNiebling Interesting. I interpreted the line "Challenges are resolved first before any action or counteraction is resolved" to mean that you may challenge an action or you may challenge a...

I also think that the line, "For example, if you challenge an assassin used against you and lose the challenge, you will lose 1 influence for the lost challenge and...

No problem. I would offer to implement it, but I'm also quite busy right now and have no experience with Node.js.