Max Inden

No worries. Rebased on to latest `main` now.

~~Only 10 more tests to go:~~ ``` failures: connection::tests::keys::discarded_initial_keys connection::tests::migration::migrate_same_fail connection::tests::priority::critical connection::tests::priority::high_normal connection::tests::priority::important connection::tests::recovery::pto_handshake_complete connection::tests::resumption::ticket_rtt_larger_than_default connection::tests::resumption::ticket_rtt_less_than_default connection::tests::vn::compatible_upgrade connection::tests::vn::compatible_upgrade_large_initial ```

@grobie As far as I understand, the *receiver* dropdown is not filtering but just sorting. As `backend-engineering-productivity` is closer to `prodeng` then `osc-reporting` it is listed first. Please have a...

Not sure. I would have to redirect this question on to @stuartnelson3.

@mansf-osk I suggest starting with a single module, e.g. `neqo-transport/src/ecn.rs`. Small pull requests reduce the likelihood of merge conflicts and make reviewing easier. > Maybe it makes sense to remove...

It would be defined as: ``` rust // neqo-transport/src/ecn.rs pub struct Info { // ... } ``` and it would be used as: ``` rust // Some other file. use...

> The way we did it in [#2311](https://github.com/mozilla/neqo/pull/2311) (like in Max's example above) we would eventually end up losing lots of explicit imports that we have right now. I'm not...

> If there is consensus for it I'll go ahead and turn `module_name_repetitions` on again. Sounds good to me.

> Regarding `neqo` and `mtu`, we can bump whenever you're ready - just let us know. (CC @mxinden for info). Under the assumption that `windows` `v0.59` does not introduce a...

Failing with: ``` android-actions/setup-android@v2 and reactivecircus/android-emulator-runner@v2 are not allowed to be used in mozilla/neqo. ``` @larseggert where do I find Mozilla's list of allowed GitHub actions?