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
Perhaps this is not likely to happen, or for this to be an issue, but it seems that the rhex() function as defined isn't gauranteed to create a unique name if there are many many nodes (like 1 million).
stopgap solution - create error to catch unique names of nodes - basically tell the user there is something wrong with duplicated node names and that rerunning the model should fix this.
create unit test to test the mechanism that generates node names and that they are unique
test if loading multiple greta objects from past environments results in mixed up / wrongly defined nodes/models
It makes me wonder if perhaps this is related to this issue. We have not been able to reliably develop a small reprex for this issue, so it might not be related to this one.
Perhaps this is not likely to happen, or for this to be an issue, but it seems that the rhex() function as defined isn't gauranteed to create a unique name if there are many many nodes (like 1 million).
This is used in node_class.R.
See example below.
Created on 2021-04-08 by the reprex package (v2.0.0)
Perhaps digest or something like https://github.com/coolbutuseless/xxhashlite could be used to give nodes unique IDs
The text was updated successfully, but these errors were encountered: