Skip to content

Latest commit

 

History

History
405 lines (245 loc) · 18.4 KB

CONTRIBUTING.md

File metadata and controls

405 lines (245 loc) · 18.4 KB
Raw

Contributing to Nokogiri

This doc is intended to be a short introduction on how to modify and maintain Nokogiri.

If you're looking for guidance on filing a bug report or getting support, please visit the "Getting Help" tutorial at the nokogiri.org site.

Contents

Introduction

Hello there! I'm super excited that you're interested in contributing to Nokogiri. Welcome!

This document is intended only to provide a brief introduction on how to contribute to Nokogiri. It's not a complete specification of everything you need to know, so if you want to know more, I encourage you to reach out to the maintainers via email, twitter, or a new Github issue. We'd love to get to know you a bit better!

Code of Conduct

Our full Code of Conduct is in CODE_OF_CONDUCT.md.

For best results, be kind. Remember that Nokogiri maintainers are volunteers, and treat them with respect. Do not act entitled to service. Do not be rude. Do not use judgmental or foul language.

Some guiding principles of the project

The top guiding principles, as noted in the README are:

  • be secure-by-default by treating all documents as untrusted by default
  • be a thin-as-reasonable layer on top of the underlying parsers, and don't attempt to fix behavioral differences between the parsers

Nokogiri supports both CRuby and JRuby, and has native code specific to each (though much Ruby code is shared between them). Some related secondary principles are:

  • Whenever possible, implement the same functionality for both CRuby and JRuby.
  • Whenever possible, implement shared behavior as shared Ruby code (i.e., write as little native code as reasonable).
  • Whenever possible, avoid writing tests that are platform-specific (but if you do, use skip to provide an explanation).

Notably, despite all parsers being standards-compliant, there are behavioral inconsistencies between the parsers used in the CRuby and JRuby implementations, and Nokogiri does not and should not attempt to remove these inconsistencies. Instead, we surface these differences in the test suite when they are important/semantic; or we intentionally write tests to depend only on the important/semantic bits (omitting whitespace from regex matchers on results, for example).

Nokogiri is widely used in the Ruby ecosystem, and so extra care should be taken to avoid introducing breaking changes. Please read our Semantic Versioning Policy to understand what we consider to be a breaking change.

Where to start getting involved

Please take a look at our Issues marked "Help Wanted".

Also, pull requests for documentation improvements are always welcome!

Submitting Pull Requests

Pull requests should be made with main as the merge base. See the next section for details.

Pull requests that introduce behavior change must always contain a test demonstrating the behavior being introduced, fixed, or changed. These tests should ideally communicate to the maintainers the problem being solved. We will ask you for clarification if we don't understand the problem you're trying to solve.

If the pull request contains a feature or a bugfix, please make sure to create a CHANGELOG entry in the "unreleased" section.

Please do not submit pull requests that make purely cosmetic changes to the code (style, naming, etc.). While we recognize that the code can always be improved, we prefer that you focus on more impactful contributions.

Feel free to push a "work in progress" to take advantage of the feedback loops from CI. But then please indicate that it's still in progress by marking it as a Draft Pull Request.

Branch Management and Release Management

Nokogiri follows SemVer, and some nuances of that policy are spelled out in Semantic Versioning Policy.

Development should be happening on main, which sets Nokogiri::VERSION to a development version of the next minor release (e.g., "1.14.0.dev"). All pull requests should have main as the merge base.

Patch releases should be made by cherry-picking commits from main onto the release branch (e.g., v1.13.x) in a pull request labeled backport.

How to set up your local development environment

Basic

git clone --recurse-submodules https://github.com/sparklemotion/nokogiri
cd nokogiri
bundle install

Advanced

Please install the latest or previous version of CRuby (e.g., 3.2 or 3.1 as of 2023-01), and a recent version of JRuby. We recommend using rbenv, which is used in test scripts when necessary to test gems against multiple rubies.

Please install a system version of libxml2/libxslt (see Installing Nokogiri for details) so that you can test against both the packaged libraries and your system libraries.

We recommend that you install valgrind if you can, but it's only necessary for debugging problems so feel free to wait until you need it. (I'm not sure valgrind is easily available on MacOS.)

If you plan to package precompiled native gems, make sure docker is installed and is working properly.

How to run the tests

Note that rake test does not compile the native extension, and this is intentional (so we can run the test suite against an installed gem). If you're modifying the extension code, please make sure you re-compile each time you run the tests to ensure you're testing your changes.

The short version

bundle exec rake compile test

To run a focused test, use MiniTest's TESTOPTS:

bundle exec rake compile test TESTOPTS="-n/test_last_element_child/"

CRuby advanced usage

Test using your system's libraries:

bundle exec rake clean  #  blow away pre-existing libraries using packaged libs
bundle exec rake compile test -- --enable-system-libraries

Run performance tests:

bundle exec rake compile test:bench

Run tests using valgrind:

bundle exec rake compile test:valgrind

Run tests in the debugger:

bundle exec rake compile test:gdb
# or
bundle exec rake compile test:lldb

Run tests and look for new memory leaks:

bundle exec rake compile test:memcheck

Note that by you can run the test suite with a variety of GC behaviors. For example, running a major after each test completes has, on occasion, been useful for localizing some classes of memory bugs, but does slow the suite down. Some variations of the test suite behavior are available (see test/helper.rb for more info):

# see failure messages immediately
NOKOGIRI_TEST_FAIL_FAST=t bundle exec rake compile test

# ordinary GC behavior
NOKOGIRI_TEST_GC_LEVEL=normal bundle exec rake compile test

# minor GC after each test
NOKOGIRI_TEST_GC_LEVEL=minor bundle exec rake compile test

# major GC after each test
NOKOGIRI_TEST_GC_LEVEL=major bundle exec rake compile test

# major GC after each test and GC compaction after every 20 tests
NOKOGIRI_TEST_GC_LEVEL=compact bundle exec rake compile test

# verify references after compaction after every 20 tests
# (see https://alanwu.space/post/check-compaction/)
NOKOGIRI_TEST_GC_LEVEL=verify bundle exec rake compile test

# run with GC "stress mode" on
NOKOGIRI_TEST_GC_LEVEL=stress bundle exec rake compile test

libxml2 advanced usage

If you want to build Nokogiri against a modified version of libxml2 or libxslt, clone them both into sibling directories (../libxml2 and ../libxslt) then run scripts/compile-against-libxml2-source.

That script also takes an optional command to run with the proper environment variables set to use the local libxml2 library, which can be useful when trying to git bisect against libxml2 or libxslt. So, for example:

scripts/compile-against-libxml2-source bundle exec rake test

An alternative, if you're not bisecting or hacking on libxml2 or libxslt, is:

bundle exec rake compile -- \
  --with-xslt-source-dir=$(pwd)/../libxslt \
  --with-xml2-source-dir=$(pwd)/../libxml2

gumbo HTML5 parser

To run the test suite for the gumbo parser:

bundle exec rake gumbo

Please note that additional html5lib tests for Nokogiri's HTML5 parser exist in a submodule. If you haven't checked that submodule out, here's how to do so:

git submodule update --init  #  test/html5lib-tests
bundle exec rake compile test

Style Guide

Documentation

We use rdoc to build Nokogiri's documentation. Run rake rdoc to build into the ./html directory, and see the rdoc tasks in rakelib/rdoc.rake.

Previously we made some effort to move towards yard but that work was stopped (and the decision record can be found at RFC: convert to use yard for documentation).

Docstrings should be in RDoc::Markup format, though simple docstrings may be in Markdown (using :markup: markdown).

If you submit pull requests that improve documentation, I will happily merge them and credit you in the CHANGELOG.

Some guidelines (see lib/nokogiri/xml/node.rb and ext/nokogiri/xml/node.c for examples):

  • Use :call-seq: to ...
    • note the return type of the method whenever possible, e.g. :call-seq: upcase(name) → String
    • name all the aliases of a method
    • indicate block/yield usage of a method
  • Briefly explain the purpose of the method, what it returns, and what side effects it has
  • Use a [Parameters] definition to note the expected types of all the parameters as a bulleted list
  • Use a [Returns] definition to note the return type
  • Use a [Yields] definition to note the block parameters
  • Use a ⚠ character to warn the user about tricky usage
  • Use a 💡 character to call attention to important notes
  • See also: should be used to call out related methods
  • Since should be used to indicate the version in which the code was introduced
  • Prefer to show nuanced behavior in code examples, rather than try to explain it in prose.

Code

I don't feel very strongly about code style, but this project follows Shopify's Ruby Style Guide, and for C and Java code the project uses the astyle configuration laid out in ./rakelib/format.rake.

You can auto-format the C, Java, and Ruby code with rake format.

There are some pending Rubocop rules in .rubocop_todo.yml. If you'd like to fix them up, I will happily merge your pull request.

No, I don't want to debate any of the style choices.

How Continuous Integration ("CI") is configured

The bulk of CI is running in Github Actions since May 2021: https://github.com/sparklemotion/nokogiri/actions

However, we also run tests against 32-bit windows (which aren't supported by GA as of this writing) in Appveyor: https://ci.appveyor.com/project/flavorjones/nokogiri

A known hole in CI coverage is the lack native gem tests for arm64-darwin.

Coverage

The ci.yml pipeline includes jobs to:

  • basic security sanity check and formatting check, using Rubocop
  • fast feedback for obvious failures: run against system libraries on vanilla ubuntu
  • run the Gumbo parser tests on ubuntu, macos, and windows
  • run on all supported versions of CRuby:
    • once with packaged libraries
    • once with system libraries
    • once on valgrind (to look for memory bugs)
  • run the test suite looking for new memory leaks (using ruby_memcheck)
  • run on JRuby
  • run on TruffleRuby
  • run on a Musl (Alpine) system:
    • against system libraries
    • with valgrind using packaged libraries
  • run with libxml-ruby loaded (because this can interact with libxml2 in conflicting ways)
    • against system libraries
    • with valgrind using packaged libraries
  • build a "ruby" platform gem
    • install and test on linux, macos, and windows
  • build native gems
    • install and test against all supported versions of CRuby
    • install and test on a variety of linux, macos, and windows systems
  • build a jruby gem, install and test it

The upstream.yml pipeline includes jobs to:

  • run against libxml2 and libxslt head (linux), including a valgrind check
  • run against CRuby head (linux, windows, macos) including a valgrind check
  • run against JRuby head
  • run html5lib-tests from that project's origin/master

The downstream.yml pipeline includes jobs to run notable downstream dependents against Nokogiri main.

The generate-ci-images.yml pipeline builds some containers used by the other pipelines once a week. This is primarily an optimization to make sure system packages (like libxml2-dev and valgrind) are already installed. See oci-images/nokogiri-test/ for details on what's in these containers.

Valgrind and ruby_memcheck

We rely heavily on Valgrind and ruby_memcheck to catch memory bugs by running in combination with every version of CRuby.

We use suppressions primarily to quiet known small memory leaks or quirks of certain Ruby versions. See the files in the /suppressions directory and /rakelib/test.rake for more information.

Benchmark / Performance tests

A separate suite, test:bench, can be run to ensure a few performance expectations. As of 2022-02 this suite is small, but we can grow it over time. These tests are run in CI on CRuby and JRuby.

These tests should use Nokogiri::TestBenchmark as the base class, and be in a file matching the glob test/**/bench_*.rb.

Helpful hints when writing new CI jobs

  • Always checkout the source code including submodules (for the html5lib tests)
  • When testing packaged libraries (not system libraries), cache either ports/ (for compiled libraries) or ports/archives/ (for just tarballs)
    • note that libgumbo is built outside of ports/ to allow us to do this caching safely

Packaging releases

As a prerequisite please make sure you have docker correctly installed, to build native (precompiled) gems.

Run scripts/build-gems which will package gems for all supported platforms, and run some basic sanity tests on those packages using scripts/test-gem-set, scripts/test-gem-file-contents, and scripts/test-gem-installation.

See Making a release below for the checklist.

Other utilities

scripts/test-exported-symbols checks the compiled nokogiri.so library for surprising exported symbols. This script likely only works on Linux, sorry.

scripts/test-nokogumbo-compatibility is used by CI to ensure that Nokogumbo installs correctly against the currently-installed version of Nokogiri. Nokogumbo receives this extra care because it compiles against Nokogiri's and libxml2's header files, and makes assumptions about what symbols are exported by Nokogiri's extension library.

scripts/files-modified-by-open-prs is a hack to see what files are being proposed to change in the set of open pull requests. This might be useful if you're thinking about radically changing a file, to be aware of what merge conflicts might result. This could probably be a rake task.

There's a Vagrantfile in the project root which I've used once or twice to try to reproduce problems non-Linux systems (like OpenBSD). It's not well-maintained so YMMV.

Bumping Java dependencies

Java dependencies, in the form of .jar files, are all vendored as part of the java platform gem.

We use jar-dependencies as a development dependency to manage the project's Java dependencies. Note, however, that we use our own fork of NekoDTD that lives at https://github.com/sparklemotion/nekodtd

To modify or add a dependency, a few things needs to be in sync:

  • nokogiri.gemspec: spec.requirements need to specify the maven group Id, artifact ID, and version
  • nokogiri.gemspec: spec.files need to include the jar files
  • git: the jar files under lib/nokogiri/jruby/ need to be committed to git
  • lib/nokogiri/jruby/nokogiri_jars.rb: needs to include all the jars

A quick summary of what this looks like for you, the developer:

  1. edit the requirements in the gemspec
  2. run bundle exec rake vendor_jars which updates everything under lib/nokogiri/jruby
  3. run bundle exec rake check_manifest and if necessary update the gemspec files
  4. make sure to check everything under lib/nokogiri/jruby into git, including the jar files

Rake tasks

The Rakefile used to be a big fat mess. It's now decomposed into a small set of files in /rakelib. If you've got a new rake task you'd like to introduce, please consider whether it belongs in one of the existing concerns, or needs a new file. Please don't add it to Rakefile without compelling reasons.

Making a release

A quick checklist: