David Vo

I wonder if this is an ntcore bug as well that we've inherited. Both Shuffleboard and pynetworktables2js proved to be not entirely reliable at competitions for my team this year....

In the meantime, if you would like your update rate to be consistent regardless of what packages are installed, you can use the [`NetworkTablesInstamce.setUpdateRate`](https://robotpy.readthedocs.io/projects/pynetworktables/en/stable/api.html#networktables.NetworkTablesInstance.setUpdateRate) method. Robot code always uses pyntcore,...

Given the performance issues we had last year, I'm not sure I'm comfortable with doubling down on the doubled update rate here.

Well, it's almost 2022. Which way do we want to go? I'm still in favour of matching ntcore here.

Took a look at this. Looks like we need to change line 20 of tests/conftest.py back to import from networktables, otherwise the utils will use a different backend to the...

This might also be an indicator that we should actually pass the NetworkTablesInstance to the util classes in the tests as well.

Fixed by #115 and #118, but perhaps we should also make it possible to run the tests with the ntcore backend here?

> This does run tests with ntcore. I believe early 2021 me was referring to the fact that none of the tests here will actually run against the ntcore backend,...

@brianfcoleman did you enable the GNOME extension?

See also #542