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
Many of our examples use the WithBlock option to wait for client connections to be established. According to gRPC documentation, this is apparently an anit-pattern that may not be appropriate.
We need to understand how avoiding the WithBlock dial option will impact our use in combination with Gorums.
The text was updated successfully, but these errors were encountered:
I think this might be part of a bigger problem: A config cannot be created if some of the nodes are not up and running.
I have linked a pull request that will create a config regardless of the status of the node (it will, however, try to connect to the node initially). Instead, it will try to connect to nodes (that are offline) for each message that is supposed to be sent to the nodes.
The solution passes all tests and have been tested "live" (i.e. in an actual implementation). It also removes the need for using WithBlock().
Many of our examples use the
WithBlock
option to wait for client connections to be established. According to gRPC documentation, this is apparently an anit-pattern that may not be appropriate.We need to understand how avoiding the
WithBlock
dial option will impact our use in combination with Gorums.The text was updated successfully, but these errors were encountered: