Closed kiyarose closed 2 months ago
That is very odd! Thank you for reporting.
I'm inclined to think this was some kind of temporary networking hiccup. I've verified the restylers manifest that this Job claims was invalid looks correct, and it's not been updated since 7/15, and other jobs have successfully pulled and parsed it since. I've also seen no uptick in our general error rate and, if there were bad data in that file, every single one of our users would be failing in this way.
I also found it very odd because I assumed the only way for this to typically happen, would be if the master restyler file got borked. Which would warrant more than just my report. But it would be interesting to monitor, and if a cause could be determined that might be informative.
Hi there-
I'm having a problem with a Restyled Job
===
What I expected to happen: Restyle job to complete successfully
What happened instead: Restyle job threw YAML error with the default configuration (due to no other configuration specified)
Configuration (if applicable): Default configuration (as no restyled.yaml exists in the repo)
No clue why this happened, if I get more info I will update this