Network devices are identified by means of a slot index to the user level.
Adding and removing devices at runtime means we can no longer be confident that the device x from an hour ago is the same as device x now.
To solve this, we can add a global network devices generation counter that is incremented on each insertion/removal.
Additionally, we might expose the birth generation numbers of each device.
Also, the 'number of active devices' should be replaced with 'number of highest allocated slot', similar to other API functions, to cover the fact that suddenly we can have holes.
Network devices are identified by means of a slot index to the user level.
Adding and removing devices at runtime means we can no longer be confident that the device x from an hour ago is the same as device x now.
To solve this, we can add a global network devices generation counter that is incremented on each insertion/removal.
Additionally, we might expose the birth generation numbers of each device.
Also, the 'number of active devices' should be replaced with 'number of highest allocated slot', similar to other API functions, to cover the fact that suddenly we can have holes.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Network devices are identified by means of a slot index to the user level.
Adding and removing devices at runtime means we can no longer be confident that the device x from an hour ago is the same as device x now.
To solve this, we can add a global network devices generation counter that is incremented on each insertion/removal.
Additionally, we might expose the birth generation numbers of each device.
Also, the 'number of active devices' should be replaced with 'number of highest allocated slot', similar to other API functions, to cover the fact that suddenly we can have holes.