cml-publish ERR_INVALID_URL

[DavidGOrtega]

Happened here

TypeError [ERR_INVALID_URL]: Invalid URL: 
    at onParseError (internal/url.js:257:9)
    at new URL (internal/url.js:333:5)
    at watermark_uri (/cml/src/utils.js:135:15)
    at CML.publish (/cml/src/cml.js:110:13)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async run (/cml/bin/cml-publish.js:25:18) {
  input: '',
  code: 'ERR_INVALID_URL'

[0x2b3bfa0]

I have been able to reproduce this issue artificially by mocking the asset server and replying with an empty 200 response.

If this is a real issue, it's was probably caused on the backend.

[DavidGOrtega]

If this is a real issue, it's was probably caused on the backend.

Yes. I have been noticing it from and you are right its in the backend

[0x2b3bfa0]

I haven't been able to isolate any deterministic cause for this issue after reading the backend code and performing some tests. I'll set up a similar function on my private account and try to reproduce the issue repeatedly.

[0x2b3bfa0]

Excerpt from the workflow run linked on the original post including log timestamps:

Fri, 12 Mar 2021 12:24:48 GMT TypeError [ERR_INVALID_URL]: Invalid URL: 
Fri, 12 Mar 2021 12:24:48 GMT     at onParseError (internal/url.js:257:9)
Fri, 12 Mar 2021 12:24:48 GMT     at new URL (internal/url.js:333:5)
Fri, 12 Mar 2021 12:24:48 GMT     at watermark_uri (/cml/src/utils.js:135:15)
Fri, 12 Mar 2021 12:24:48 GMT     at CML.publish (/cml/src/cml.js:110:13)
Fri, 12 Mar 2021 12:24:48 GMT     at processTicksAndRejections (internal/process/task_queues.js:97:5)
Fri, 12 Mar 2021 12:24:48 GMT     at async run (/cml/bin/cml-publish.js:25:18) {
Fri, 12 Mar 2021 12:24:48 GMT   input: '',
Fri, 12 Mar 2021 12:24:48 GMT   code: 'ERR_INVALID_URL'
Fri, 12 Mar 2021 12:24:48 GMT }

[0x2b3bfa0]

What puzzles me is that there isn't any CloudWatch log with that timestamp and, after correlating newer runs like 2096426611, I haven't found any noticeable clock skew.

It looks like the request didn't even trigger the lambda function and errored somewhere near API Gateway, so I declare myself incapable of fixing this issue with a single sample, no means to reproduce it and no logs.

@DavidGOrtega, unless you choose otherwise, I'm closing this issue by adding an user-friendly error with debug information just in case somebody is able to reproduce it in the future.