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
After calling CheckOperationsVerbose and getting a result I would love be able to access the "longest linearizable path" found. In the case of an Ok result this would be equivalent to the path shown in the visualization. In the case of an Illegal result the visualization can show a few different paths, in this case either the longest or all the paths would be useful to have access to.
The reason I am hoping to access this information is because we have written a step function that looks like this
Our dst function returns an updated model and an error that contains additional useful information. In the case where the error is non nil, we report false to porcupine and the error information is effectively lost. If I could access the longest path (I'm hoping for a slice of type []porcupine.Operation) I could feed this information back into our dst model and report the error that occurs, this would be super helpful for debugging and developing.
If this is something that is possible and something you are up to add to porcupine I am happy to create a PR :)
The text was updated successfully, but these errors were encountered:
+1 to that from etcd. It would be really useful to get the linearization to be able to validate etcd watch, the eventually consistent stream that of changes to etcd.
After calling
CheckOperationsVerbose
and getting a result I would love be able to access the "longest linearizable path" found. In the case of anOk
result this would be equivalent to the path shown in the visualization. In the case of anIllegal
result the visualization can show a few different paths, in this case either the longest or all the paths would be useful to have access to.The reason I am hoping to access this information is because we have written a step function that looks like this
Our dst function returns an updated model and an error that contains additional useful information. In the case where the error is non nil, we report false to porcupine and the error information is effectively lost. If I could access the longest path (I'm hoping for a slice of type
[]porcupine.Operation
) I could feed this information back into our dst model and report the error that occurs, this would be super helpful for debugging and developing.If this is something that is possible and something you are up to add to porcupine I am happy to create a PR :)
The text was updated successfully, but these errors were encountered: