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.

Sign up for GitHub

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

Jump to bottom

tcpinfo tables should be per-experiment #49

Open
pboothe opened this issue Oct 11, 2019 · 2 comments
Open

tcpinfo tables should be per-experiment #49

pboothe opened this issue Oct 11, 2019 · 2 comments
Assignees
@gfr10598
Labels
backlog bug Something isn't working P2

Comments

@pboothe
Copy link
Contributor

pboothe commented Oct 11, 2019 •
edited
Loading

Right now the tcpinfo tables (e.g. measurement-lab.ndt.tcpinfo) are global rather than restricted to the given experiment, which is not the right thing.
@autolabel autolabel bot added the review/triage Team should review and assign priority label Oct 11, 2019
@mehtab11 mehtab11 added the bug Something isn't working label Oct 21, 2019
@pboothe pboothe added P2 and removed review/triage Team should review and assign priority labels Oct 21, 2019
@mehtab11 mehtab11 added review/triage Team should review and assign priority and removed review/triage Team should review and assign priority labels Oct 21, 2019
@pboothe
Copy link
Contributor Author

pboothe commented Oct 21, 2019

The proper fix for this depends on work @gfr is doing. Assigning to the backlog for the next month or so.

@pboothe
Copy link
Contributor Author

pboothe commented Oct 21, 2019

Traceroute has the same issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gfr10598 gfr10598

Labels
backlog bug Something isn't working P2
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@pboothe @gfr10598 @mehtab11