-
Notifications
You must be signed in to change notification settings - Fork 60
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
moq-pub #54
moq-pub #54
Conversation
For http::uri::Uri
Crib a bunch of code from the old moq-warp File source so we can work out which track(s) moofs and mdats belong to
ANNOUNCE a new track namespace, 'foo' and simply wait for everything to time out because we haven't wired up a way to send objects for it yet.
We don't need to clone clients, so no need to wrap everything up like this anymore
Added while debugging async issues, accidentally committed earlier
and everything it contains. Stop short of printing all of the bytes in a State's VecDeque, but expose most everything else for easier troubleshooting.
Rebasing this and working through the updates it'll need to get back in sync with the latest from |
For quinn, higher values take precedence over lower values, the inverse of how we had been treating "send order" so far.
Work around relay / quinn bug with send_order / stream priority by only sending streams with the same priority.
There are maybe a few things that could still be cleaned up here, but I'm inclined to try to get this merged sooner rather than later to avoid further integration issues. With the latest changes (basically not using prioritization for now), it works again against the latest relay. |
Oof, forgot that I do still need to switch over the the JSON catalog. Spent so long poking around in quinn today trying to chase down those panics around prioritization and mutex poisoning I almost forgot about that. |
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.
rough around the edges but yolo
This avoids breaking workflows now that we have another binary in the workspace (`moq-pub`).
This is still a little rough around the edges, but I think it's better to get it merged and avoid further drift and integration issues.