Kaleb Barrett

If they aren't speedy we *could* update the github action to point to my fork.

Lol the maintainers on that project aren't even watching the repo. We should either switch to my fork or just bring it in as is. [Some more context](https://app.bountysource.com/issues/102774219-call-for-maintainers) on the...

https://github.com/benchmark-action/github-action-benchmark/pull/112 is now merged. We should set up another repo to put the benchmark results.

This seems like a Riviera-PRO issue isn't it? The variable in `sh` is fine, but in Riviera it's screwed up. My guess is Riviera sees it's on Windows running from...

I think it was auto-closed because the `question` label wasn't removed once it was confirmed to be an issue. I can reopen it, but it would be nice to know...

This is probably the problem. https://github.com/cocotb/cocotb/blob/b4a2ce033fb21b10e2a2deb0dbb95d0b9e895e9c/cocotb/share/lib/fli/FliCbHdl.cpp#L43-L49 Other implementations use `m_state` and set the callback in the `GPI_FREE` state in `cleanup_callback`. `handle_fli_callback` checks to see if the callback is in `GPI_PRIMED`...

??? ```python @cocotb.test() async def test_example(_): print(test_example.__name__) ``` Or if you need it to be more abstract. ```python def do_stuff(): cocotb.regression_manager._test.__name__ ``` We really should have a "current test" API...

I don't think that is *wrong* per se, but the basic VPI without the SV extensions has no way to map those regs to specific types. The SV extensions support...

We have `cocotb.types.LogicArray` which was meant to be an incompatible (but for the better) replacement for `BinaryValue`. Fully integrating it like `BinaryValue` would be a breaking change though.

1.7 will be released soon. Then I think we should start breaking things wherever we see fit.