-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make request IDs unique across clients #4524
Conversation
@nwatson22, can you post the logs for an example multi-threaded run of |
Co-authored-by: Tamás Tóth <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
@geo2a, please check if this change is breaking for the Haskell backend testing automation.
@tothtamas28 @geo2a Here is a snippet of a run of a kontrol proof. Could you check that this will not break the bug report automation and @PetarMax that the requests are differentiated enough for debugging?
|
Thanks @nwatson22 and @tothtamas28! Look good to me. @jberthold could you also have a look at the output above to make sure it's compatible? |
Yes, this will disambiguate sufficiently in debugging, I think. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @nwatson22 and @tothtamas28! Look good to me. @jberthold could you also have a look at the output above to make sure it's compatible?
LGTM, too, I checked that we only use fromId
and not assume the request ID is an Int
in our code.
Blocked on: * ~#4524~ Since transport-specific files are no longer added to the bug report (e.g. commands for sending a request), bug report handling can be performed in the client.
Changes the ID fields of the requests being sent to the kore RPC server. Before they were just integers counting up the requests of each client, but it is useful to be able to see in the logs which requests are coming from which client, so this changes the IDs to be this same counter, but prepended with
id()
of the client that is making the request.