-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Broken pipe error in Mentos #242
Comments
Could you please set |
@slonopotamus , sure!
|
Weird. That What happens if you manually run |
It just says
But if I run it from Python console it seems to work (at least it listens for the input):
|
It looks like someone fully broke I'm getting this:
So, the good thing is that I can reproduce your issue. The bad thing is that it isn't clear where to go from here. |
I'm not sure if it's related to this issue, but my CI has been failing recently with a similar issue: |
Interesting... You're not on Windows. I'm not sure what's going on yet. #242 (comment) indicates that the issue is not related neither to pygments.rb nor to Ruby in general. I'll try to find out what has changed in your CI since last successful build... |
Actually, I only tried to post a new article on my blog, without changing the CI, and it failed. After that, I tried many things to attempt to fix this, but everything failed. Thanks for looking into this. |
I think I've figured out what's going on (at least on Windows). #246 should fix the issue. A new pygments.rb release incoming soon. |
@this-username-has-been-taken @antoyo guys, please give v2.3.1 a try. @this-username-has-been-taken sorry to hear that your username was taken. |
I'm no Ruby expert, but from what I understand from the code, it should not change anything on my CI since it's not on Windows. |
@antoyo I see that your last successful build was on Ubuntu 20.04, while failing ones are now on Ubuntu 22.04. Could you please try changing |
I have the same error with |
Aaargh. I don't understand what's going on yet. |
Wait. You're using some fancy |
See helaili/jekyll-action#135. I'm going to close current issue since the root cause of your issue is not on pygments.rb side. As a quick and dirty hack I might suggest switching from |
Thanks a lot! That was indeed the issue. I made a PR to fix the issue. |
Lol, I somehow confused |
I have tested v.2.3.1 - everything works well! The problem has been fixed. Thank you for help and advice! |
Big, big side track @this-username-has-been-taken, but did you run into something similar to forem/forem#77? Or why did you have to switch the username? 🤔 |
@perlun, I just kinda wanted to stand out a bit from the "47513", "" usernames and choose something more original. |
Pranks are indeed fun sometimes. 😉 Have a great day! |
Hello!
I have faced an error while trying to use pygments.rb with asciidoctor:
Broken pipe - Failed to read response from Python process on a mentos get_all_lexers call: Python (MentosError)
I am using the latest version of Pygments.rb (2.3.0), Asciidoctor (2.0.18), Python (3.11.0) and Ruby (3.1.0).
Steps to reproduce:
asciidoctor --trace <path to the file from paragrapth 1>
Could you please help me identify the cause of the problem and fix it?
The text was updated successfully, but these errors were encountered: