nulltoken

:+1: Although returning `202` for a `GET` reads a bit weird, the "come back later" approach makes a lot a sense. One thing that may also be added on top...

Please, dear bot, don't mark it as stale

@hectorhdzg Thanks for the feedback. However, I'm not sure to understand why a call to time() generates a trace entry. The spec (https://console.spec.whatwg.org/#timing) only defines calls to `Printer` for `timeLog`...

@hectorhdzg I know there's not a lot of meat in this issue. However, it keeps on happening. How could we try and tackle this?

@hectorhdzg Thanks for the response. > are you manually or automatically tracking the dependencies? Automatically >if automatically from where the telemetry is coming from? HTTPs library? Azure SDK? Mostly [Got](https://www.npmjs.com/package/got/v/11.8.2)...

@hectorhdzg What would be the next steps according to you?

@hectorhdzg Sorry for the delay. I've completely missed your message from March, 15th. I'll come back to you in the following days with some answers.

@hectorhdzg Below the requested information > also which version of node.js runtime are you using? Node v16.17.0 >in failed dependencies log you shared, both events are the same except the...

In a different schema validation library (ajv), a similar issue (timeoffset not being considered as mandatory by the validation engine) was eventually considered as too permissive => https://github.com/ajv-validator/ajv-formats/pull/33#issuecomment-881636023

:wave: @eric-personal Hey! Sorry for the delay. It seems I missed the notification on this issue. I'm a little lost here. Could you explain what you're trying to achieve? What's...