Hi Jasper, Thanks for fixing and giving feedback.
Regards, Dave Op ma 16 dec. 2019 om 12:21 schreef Jasper den Hertog <[email protected]>: > hi Dave, > > We’ve dug into this and it turned out that the metadata for DNS > measurements wasn’t propagating correctly through our infrastructure, but > the measurement data (metadata + results) themselves were not affected. > > We’ve corrected this behaviour and have stored the metadata correctly so > it can be retrieved by users. All the measurement ids you have mentioned in > this thread will now return results and metadata. > > Thanks again for your valuable feedback and happy measuring, > > greetings, > > Jasper > > On 15 Dec 2019, at 20:13, Jasper den Hertog <[email protected]> wrote: > > hi Dave, > > Thanks for the feedback, I will try to reproduce this tomorrow. This is > serious enough to warrant thorough investigation, we should never skip > measurement ids, no matter what the response of a particular resolve is. > > I’ll keep you posted, > > Greetings, > > Jasper > > On 15 Dec 2019, at 18:28, Dave . <[email protected]> wrote: > > Hi Jasper, > > Same result for new tests unfortunately. > > https://atlas.ripe.net/measurements/23650744/#!general > > https://atlas.ripe.net/measurements/23650745/ > > In case you want to try and reproduce it, I am trying to start a one-off > DNS test for spotify.com or grc.com and use 74.82.42.42 (Hurricane > Electric) as a resolver. The resolver in Amsterdam has an issue currently > and I'd like to find out whether other nodes in other locations have the > same issue or not. The issue was reported to HE so I guess they will have > fixed it soon. > > Regards, > Dave > > > Op za 14 dec. 2019 om 14:33 schreef Jasper den Hertog <[email protected] > >: > >> hi Dave, >> >> I can confirm that there’s a problem with the measurements with ids your >> mentioning. >> >> The creation process never finished for these measurements. The >> measurements with the ids 23631303,23631304,23631305 and 23631307 all never >> were created. For what I can see now this seems to be a transient problem. >> >> If you see other measurements with the same problem please report them to >> us. >> >> We will look into the cause of this problem monday, >> >> greetings, >> >> Jasper den Hertog >> RIPE Atlas team >> >> >> On 13 Dec 2019, at 21:55, Dave . <[email protected]> wrote: >> >> Hi, >> >> I just started 2 measurements like 10 minutes ago but it does seem >> something broke. >> >> https://atlas.ripe.net/measurements/23631307/#!probes >> >> Same issue here: >> https://atlas.ripe.net/measurements23631307#!probes >> >> I get to see a spinner instead of the results. >> >> Thanks, >> Dave >> >> >> >> >> > >
