Closed divagant-martian closed 23 hours ago
make sure to also add this to the two ci files that need a list of crates
looking good, found one last rename
@dignifiedquire fixed. There's a bunch of net_report report
that I don't love but I.. think it will have to do for now? or maybe we can rename Report
to Check
or similar? not looking forwards to more renaming but it's something I noticed. Thoughts? These are all in strings (docs, comments, etc) which make them technically correct: It's a net_report::Report
. Code that would have been a NetReportReport(Report)
looks like NetReport(Report)
at least
There's a bunch of
net_report report
that I don't love but I..
I think we can clean this up in follow ups :) lets get the structure in
Description
Introduces net-report as its own crate. For this, introduces a new feature flag
relay
iniroh-base
for the relay topology types.iroh-base
, theRelayUrl
is moved to its own file. It can still be used as before, this is not a breaking change.RelayMap
,RelayNode
are moved toiroh-base
under therelay
feature flag.RelayMode
is moved toendpoint
. See the NOTES section about this.iroh-net
toiroh-net-report
. This is the only place where it's used so it should have probably been part ofnetcheck
as a module from the beginig.Breaking Changes
iroh-net
'sNetcheckMetrics
are now calledNetReportMetrics
Notes & open questions
RelayMode
remains iniroh-net
instead of moving toiroh-base
with other relay related because this is coupled with the staging and prod configuration of relay urls. Since this is more configuration than concept I think it's best to keep it in iroh-net.iroh-net-report
because -at least currently- it depends on relay concepts. For example, the tests depend heavily on the internal order of theRelayMap
. Can we change this? yes. Should we change this? we can discuss it. Is this PR the place for any of that? No.iroh-net
) It's not terrible but it could be improved.Change checklist