Hey all, I’m trying to do a timestamp matcher, and my timestamp looks like

2023-01-05T10:38:01.611240928Z

, and the pact-js docs require a format string to match against in java simple date format. I’m currently using the format string

yyyy-MM-dd'T'HH:mm:ss.SSS'Z'

Where I believe SSS is just meant to represent milliseconds in general. However this returns an error from the verifier that reads

Error(Nom("171690Z", Tag))

. If I update the format string to include 9 S’s, to represent the amount of milliseconds we return in the response, I then get the error

Error(InvalidMillisecond("294910091"))

. Does anyone have any idea how I could alter my format string to get it working? To add, it seems like java SimpleDateTime doesn’t handle nanoseconds, so I’m wondering if my next best solution is to just write a regex for it instead.

I don’t think your timestamp matches that format string.

Where I believe SSS is just meant to represent milliseconds in general.

That’s my understanding too. However, your string seems to say 611240928 milliseconds, I think? That doesn’t match

SSS

, as it’s not in the range 0-999.

Hey Timothy, apologies for the delayed response, but thanks a lot for your response! It turns out your suggestion for using nanoseconds as

nnnnnnnnn

was exactly what was needed! Slightly frustrating that that Java documentation didn’t mention this, and that all the stackoverflow questions I saw said it wasn’t supported or something. I guess in retrospect the error does sort of make sense. I’m not exactly sure what else I’d expect Pact to respond with tbf, it’s expecting milliseconds based on the format string I gave it, and the bit at the end certainly wasn’t in milliseconds 🤔

Awesome! Glad you got it sorted