I am sorry this happened. Buildbot's format for timestamps is double. It was an inconsistency on our side that that particular field was a long. This was a part of admittedly dangerous refactoring. The protocol change was not intended, but was discovered after the deployment.

We don't plan to do more refactorings to this API the foreseeable future (we would rather turn this API). What is the action you expect from this bug?

re BuildInfo: please refrain from migrating to that. We plan to include whatever data you need to the Buildbucket API v2 responses, so there will be only one API to call.

We do need to migrate to BuildInfo temporarily, as we are moving away from Buildbot. 

As for the action item, is there a repo that we can subscribe to its changes. Or automatically got added as one of the reviewer? 

the Buildbot API protocols are defined in https://chromium.googlesource.com/infra/luci/luci-go/+/master/milo/api/buildbot/

you can probably subscribe to changes in that dir by adding WATCHLIST file there. I am not sure how such files work though, here is an example https://cs.chromium.org/chromium/src/WATCHLISTS?dr&q=file:WATCH&sq=package:chromium

did WATCHLIST work for you?

Sorry I haven't tried it yet, but I will soon :-) 

Thank you for cc-ing me in the CLs recently. 

I also added a "Legoland" tag for you to easily identify future issues from us. 

I'd like to close this bug because it is assigned to me, but I don't see how can I do it. Assigning to you to try out the WATCHLIST file.