You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 28, 2021. It is now read-only.
I was wondering if there was a reason newReport returned a map[string][]int, which requires sprintf'ing the integer version of the map into the string-based map?
It seems like most of the functions take in sent, received, and paths. If the report struct is changed to integer keyed maps, many functions could take in that struct instead.
I started making these changes here: virtuallynathan@137370e
Stuff still seems to work as intended, but I don't have a large ECMP fabric to test against.
The text was updated successfully, but these errors were encountered:
I was wondering if there was a reason newReport returned a map[string][]int, which requires sprintf'ing the integer version of the map into the string-based map?
It seems like most of the functions take in sent, received, and paths. If the report struct is changed to integer keyed maps, many functions could take in that struct instead.
I started making these changes here: virtuallynathan@137370e
Stuff still seems to work as intended, but I don't have a large ECMP fabric to test against.
The text was updated successfully, but these errors were encountered: