EmbedLiveSample errors should probably be fatal
See original GitHub issueSuppose you have a perfectly working page with {{EmbedLiveSample('honkey_dory', ...)}}
.
It will generate a _samples_/index.html
. And this gets uploaded, by the Deployer, to S3.
But then you “mess” with the page such that at the next render, it can’t generate a new _samples_/index.html
. You won’t notice this and the existing uploaded _samples_/index.html
won’t be replaced.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
stage-integration-tests PDF - Kuma Documentation
msgfmt: found 1 fatal error. These need to be fixed by a Kuma developer. Notify them in the #mdn Matrix room or open...
Read more >Bug List - Bugzilla
If you need to create a new account, then you should use the Github login ... after after FATAL ERROR: Non-local network connections...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@escattone and I chatted about this at length and decided to consider making
MacroEmbedLiveSample
a fatal thing (rather than a flaw). We might need to do some mass editing one-off, if it’s feasible. Or we consider some other way to make it less subtle and confusing.To get out of this funk, I just went ahead with making an exception specifically for
en-US
. Yesterday I fixed the last remainingMacroLiveSampleError
in all of mdn/content.So now, for en-US, it will crash the CI build, for for translated-content it will just be a
console.warn
https://github.com/mdn/yari/pull/3576