[roll] Roll fuchsia [netstack3] Don't bleed IP state to TCP layer When we added upper layer confirmations we ended up binding the TCP SyncContext to the IpStateContext which ends up inheriting too many responsibilities in the TCP SyncContext trait. The proper separation of concerns here is to put the lookup and resolution to next hop behind the trait that TCP already uses to abstract the IP Layer. This greatly reduces the mocking necessary in TCP without any loss of functionality. Add debug log line when we can't resolve the destination route to confirm reachable while I'm here. Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/927916 Original-Revision: caacbec5f890d62dd3bd22f9cc1b9bbffd899058 GitOrigin-RevId: 7594ec50e8636682a3deda0a7f5f7fa026856fa7 Change-Id: I4d504faafdd6b00e4c2192eb9f099c0e515f6d6f
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.