commonmarker: Problem with CommonMarker on an Azure VM

We are encountering a problem with CommonMarker as part of a build on an Azure VM. It is an indirect reference to CommonMarker; our project uses github-pages, which in turn uses jekyll-commonmarker-ghpages, which references commonmarker. When I run the build locally, it succeeds, but on the Azure VM, it gives the following error:

##[error]Bash exited with code '1'.
##[error]Bash wrote one or more lines to the standard error stream.
##[error]  Dependency Error: Yikes! It looks like you don't have jekyll-commonmark-ghpages or one of its dependencies installed. In order to use Jekyll as currently configured, you'll need to install this gem. The full error message from Ruby is: '126: The specified module could not be found. - C:/hostedtoolcache/windows/Ruby/3.1.3/x64/lib/ruby/gems/3.1.0/gems/commonmarker-0.23.7/lib/commonmarker/commonmarker.so' If you run into trouble, you can find helpful resources at https://jekyllrb.com/help/!

I have investigated and found that the file at the specified path does in fact exist. In addition, I made a test script to explicitly call the Win32 LoadLibrary API function on that path, and it loads successfully. But, a require statement pointed at it fails, not locally but on the Azure VM running the build pipeline. I’ve run out of things to check next at this time. Do you have any idea what might cause these symptoms?

About this issue

Original URL
State: closed
Created a year ago
Comments: 23 (9 by maintainers)

Most upvoted comments

@anticomputer I’ve grabbed the full build log and thrown it up here:

https://distribution.iqmetrix.net/buildlog.txt

It’s a bit big but each build step is clearly delineated between ##[section]Starting: and ##[section]Finishing:.

logiclrd on Jan 26, 2023

I like to keep the issues in my OS projects open to let me know there’s something actionable for me to do. As this hasn’t had an update in two weeks, and it sounds like a specific issue to the server, I’m going to close it out. Feel free to keep discussing; I had thought that the time the issue was opened was related to the recent release but that doesn’t appear to be the case.

gjtorikian on Feb 9, 2023

I made a build step to check ruby --version and the version in the build VM is identical to what I have locally: 3.1.3p185

logiclrd on Jan 26, 2023

I’ll add a build step to output the environment and get back to you.

logiclrd on Jan 26, 2023

@anticomputer Yep, that’s the one, the complete Gemfile looks like:

source 'https://rubygems.org'

gem 'github-pages', group: :jekyll_plugins
gem 'faraday-retry'

logiclrd on Jan 26, 2023

@phillmv @anticomputer Could you please help investigate this? It suggests that something broke in the recent cmark changes y’all made.

@logiclrd Would you be able to upgrade to commonmarker 1.0.0.pre7? The current C-based commonmarker (the 0.23.x series) is not really something I want to keep maintaining. The 1.0.0 series is “the future” and aside from a method signature change, shouldn’t disrupt your workflow and is still considered stable to use in produciton.

gjtorikian on Jan 26, 2023