-
Updated
Apr 11, 2020 - C
network-management
Here are 30 public repositories matching this topic...
-
Updated
Jun 14, 2020 - Python
-
Updated
Dec 3, 2019
-
Updated
May 21, 2020 - Python
-
Updated
Oct 22, 2019 - Python
Currently, it appears that the only way one can modify an alias is to remove it and re-add a new entry. It would be nice if while on the Modify screen for the parent hostname, if all aliases were also listed and options to modify / remove those aliases were available.
For normal builds, it is helpful to have more specific versions than simply the upcoming version snapshot. 2019.2.MMDD.HHmmSS.0 seems like a reasonable format. It combines the year major and minor open source versions with a timestamp and ending in .0 which follows an internal convention where these are treated specially as development builds.
It should be possible for the user to not use whitespace around the operators in the expr command. Right now, this is a syntax error:
$ ./netcalc.py expr 192.0.2.0/24 -192.0.2.0/25
usage: netcalc.py [-h] COMMAND ...
netcalc.py: error: unrecognized arguments: -192.0.2.0/25
This relates to the simple way in which we're parsing the command line. We'll need to be smarter than this.
-
Updated
May 26, 2020 - Perl
-
Updated
Jun 4, 2017 - JavaScript
-
Updated
Jun 12, 2020 - PHP
-
Updated
Mar 21, 2019 - Erlang
-
Updated
Sep 3, 2018
-
Updated
Oct 22, 2018 - JavaScript
-
Updated
Aug 30, 2017 - Common Lisp
-
Updated
Oct 11, 2017 - Ruby
-
Updated
Jan 16, 2020
-
Updated
Mar 21, 2019 - C++
-
Updated
Apr 30, 2020 - Dockerfile
-
Updated
Jan 31, 2019 - Python
-
Updated
Mar 17, 2020 - Python
-
Updated
Apr 1, 2020
-
Updated
Dec 4, 2019 - PHP
-
Updated
Apr 28, 2020
Improve this page
Add a description, image, and links to the network-management topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the network-management topic, visit your repo's landing page and select "manage topics."
See https://coveralls.io/builds/17797671/source?filename=ytypes%2Flist.go#L476 -- we have a number of error cases that we're not covering with existing tests. This issue tracks covering them.