GitLab

We need https://github.com/timothycrosley/isort/pull/1000 but there's no
release with this fix yet, so we'll install from GitHub.

This is the result of:

    $ isort --recursive examples templates transformers utils hubconf.py setup.py

lines_after_imports = 2 is a matter of taste; I like it.

This is the result of:

    $ black --line-length 119 examples templates transformers utils hubconf.py setup.py

There's a lot of fairly long lines in the project. As a consequence, I'm
picking the longest widely accepted line length, 119 characters.

This is also Thomas' preference, because it allows for explicit variable
names, to make the code easier to understand.

Likely it was added by accident.

adding positional embeds masking to TFRoBERTa

[WIP] Add MMBT Model to Transformers Repo

closes #1960 Add saving and resuming functionality for remaining examples

[BREAKING CHANGE] Setting all ignored index to the PyTorch standard

run_squad with roberta

fix: wrong architecture count in README

:zip: #2106 tokenizer.tokenize speed improvement (3-8x) by caching added_tokens in a Set

[WIP] Sampling sequence generator for transformers

fix run_squad.py during fine-tuning xlnet on squad2.0

Fix TFXLNet

Add special tokens to documentation for bert examples to resolve issue: #1561

Bug-fix: Roberta Embeddings Not Masked

Support running tests in parallel

This looks like debug code accidentally committed in b18509c2.

Refs #2250.

This looks like a copy/paste mistake. Probably this test was never run.

Refs #2250.

This optimizes the total run time of the Circle CI test suite.

We're already using as many processes in parallel as we have CPU cores.
Furthermore, the number of core may be incorrectly calculated as 36
(we've seen this in pytest-xdist) which make compound the problem.

PyTorch performance craters without this.

This should prevent two issues:

- hitting API rate limits for tests that hit the HF API
- multiplying the cost of expensive test setups

Set the number of CPUs manually based on the Circle CI resource class,
or else we're getting 36 CPUs, which is far too much (perhaps that's
the underlying hardware and not what Circle CI allocates to us).

Don't parallelize the custom tokenizers tests because they take less
than one second to run and parallelization actually makes them slower.

Since the file is written to the filesystem, a filesystem lock is the
way to go here. Add a dependency on the third-party filelock library to
get cross-platform functionality.

Caching models across test cases and across runs of the test suite makes
slow tests somewhat more bearable.

Use gettempdir() instead of /tmp in tests. This makes it easier to
change the location of the cache with semi-standard TMPDIR/TEMP/TMP
environment variables.

Fix #2222.