You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current BasicTestbed has some odd holes in its functionality. At present, it will never populate specs or nodes, rendering the attempts to read from those member variables before hitting the disk useless. Peering through the commands sources, it's really used as an elaborate container for the directory path. It would be quite useful (and simplify things across the board) if you could mutate the BasicTestbed via some member methods for doing things such as adding new nodes based on specs. If there's any interest in this, I'll do it this week, as it's quite relevant to my current work.
The text was updated successfully, but these errors were encountered:
The current
BasicTestbed
has some odd holes in its functionality. At present, it will never populatespecs
ornodes
, rendering the attempts to read from those member variables before hitting the disk useless. Peering through the commands sources, it's really used as an elaborate container for the directory path. It would be quite useful (and simplify things across the board) if you could mutate theBasicTestbed
via some member methods for doing things such as adding new nodes based on specs. If there's any interest in this, I'll do it this week, as it's quite relevant to my current work.The text was updated successfully, but these errors were encountered: