Skip to content
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

Client chosen ICID is not a unique Identifier of server-side logs #998

Closed
huitema opened this issue Jul 27, 2020 · 3 comments
Closed

Client chosen ICID is not a unique Identifier of server-side logs #998

huitema opened this issue Jul 27, 2020 · 3 comments

Comments

@huitema
Copy link
Collaborator

huitema commented Jul 27, 2020

Debugging an issue with the interop runner was harder than necessary because a single client connection generated two back to back server connections. Since the qlogs are identified by the ICID, the log of the first connection was overwritten by the log of the second one.

@huitema
Copy link
Collaborator Author

huitema commented Jul 27, 2020

On the other hand, a number of test tools set the ICID to a specific value that identifies the test context. There should be an option to keep using the ICID, even if we switch to using the ICID. There should also be an easy way to retrieve the server initial SCID, maybe from the client's standard output.

@huitema
Copy link
Collaborator Author

huitema commented Nov 15, 2021

Plausible choice is to insert a random number in the file name, or maybe a rendering of the date.

@huitema
Copy link
Collaborator Author

huitema commented May 1, 2022

Addressed in PR 1349 -- option to add 16 random bits to the name.

@huitema huitema closed this as completed May 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant