Andrea Mennillo
Andrea Mennillo
# Bug Description If I sumbit an FQDN with a fourth-level domain, hyperglass responds with this error: 'XXX is not a valid Traceroute target'. An example of valid domains that...
## Bug Report **Current Behavior** Google's crawler indexes page X of a discussion (discussion/?page=X) using also the text/images from other pages. This means that what Google's crawler sees doesn't always...
I've added some tests here: https://github.com/HandyMenny/pythonping/commit/a2ecdf2fbef8ffe684871d387c0c987ed9c93010 Besides the fact that they're too messy, without #66 they will fail If you don't completely agree with these changes you might as well...
The output of it/countrywide has wrong encoding. To fix the problem I've to convert from utf8 to latin1, as if there was an unnecessary latin1 to utf8 conversion. I tried...
I don't know how it was before, but the source "Turin" no longer contains streets, but only house numbers with tag "Text". But there's a more [updated source](http://geoportale.comune.torino.it/geonetworkcoto/srv/ita/csw?request=GetRecordById&service=CSW&version=2.0.2&id=c_l219:8987bd22-fea8-44e0-a900-7a6400032b30&elementSetName=full&outputSchema=http://www.isotc211.org/2005/gmd): [Shapefile](http://geoportale.comune.torino.it/secure/zip/numeri_civici.zip) (the...
When network operator isn't "synchronized" with cellinfo, MOCN post processor may replace the correct PLMN with the wrong one. Example: ``` pre : CellLte(network=Network(mcc=222, mnc=10, iso=IT), eci=2***5, tac=4***, pci=0, band=BandLte(downlinkEarfcn=3025,...
This pull request contains some changes to qualcomm LTE parser, I put them in one pull request to avoid creating many, but if you like separate pull requests let me...
I was trying to figure out why scat couldn't parse the UE Capability Information from a samsung s10 5G (SM-G977B). So I added a [raw writer](https://github.com/HandyMenny/scat/commit/6a472e26b50ac8bee9f96b13f2979831bb658364). I found out that...
At least one device, Sony 5 III XQ-BQ52, reports registrationinfo.cellidentity with the same (incorrect) PLMN as ALL_CELL_INFO. I think it's the same for other devices as well, but unfortunately getting...
The correct way to separate tuples in the _coordinates_ field is to separate them with a space, but I saw some kml documents that used a comma instead: ``` 13.08925,37.517,0,13.0859,37.517,0...