Closed obilodeau closed 6 years ago
It looks like a broken include. I'll check it out.
(Interesting to note, Travis builds were failing on New Years Eve, so we were getting some false negatives).
I can confirm that the problem was that the include path was incorrect. But the extension code I wrote was too fragile and was crashing the processor instead of issuing a warning. I've updated the extension code. Now it shows that the include path is incorrect.
Content is now visible but at some point the broken include kicks in. From there content is confused probably mixing example asciidoc markup that should have been in a source listing but that is not anymore.
I'll merge asciidoctor/asciidoctor-reveal.js#173 soon and send a PR to update README to 1.1.1 once released. We'll see how it looks like from there.
It looks like there is another error in my extension code. I'll get it fixed later today. Stay tuned!
On Jan 2, 2018 09:52, "Olivier Bilodeau" notifications@github.com wrote:
Content is now visible but at some point the broken include kicks in. From there content is confused probably mixing example asciidoc markup that should have been in a source listing but that is not anymore.
I'll merge asciidoctor/asciidoctor-reveal.js#173 https://github.com/asciidoctor/asciidoctor-reveal.js/pull/173 soon and send a PR to update README to 1.1.1 once released. We'll see how it looks like from there.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/asciidoctor/asciidoctor.org/issues/759#issuecomment-354813013, or mute the thread https://github.com/notifications/unsubscribe-auth/AAE19_brOhUb1avm19zx4x-jBhiQkm7Xks5tGl6xgaJpZM4RQLL9 .
Now it's fixed for real. I finally figured out how to use my own API ;)
I'm pretty sure if you fixed the includes in the README everything will be working perfectly once we update the reference in asciidoctor.org.
resolved by e261ed677b23416ae4f538e9177eed4c8a1524ec
Btw, the functionality this extension provides will be implemented natively in Asciidoctor 1.5.7.
Right now the page is showing a stack trace, probably since we merged #755 :
Travis-CI's successfull (?) build gives more details: https://travis-ci.org/asciidoctor/asciidoctor.org/builds/321443627#L630
I'm going to do an emergency release in the following hours or days due to asciidoctor/asciidoctor-reveal.js#172 so if I need to change something on my side let me know.
First reported by @Maurice-Mueller here: asciidoctor/asciidoctor-reveal.js#172