view CONTRIBUTING @ 40131:535fc8a22365 stable

lfs: avoid a potential variable reference before assignment error in cmdserver

A coworker hit this once yesterday when pulling in thg (a retry worked), and
then I hit it with strip after a pull.  I had a difficult time recreating a test
for this (at least one of the tricks was to not use '-R', which seems to cause
reposetup() to be called for each command), so I'm not sure how large of a
window there actually is for this.  Calling reposetup() *after* the requirement
is added will skip the hook entirely.

The other issue I had was adding a couple `ui.status()` lines around the check
that installs the hook.  On Windows, the cmdserver process ballooned to 1.6GB
and hung.  Changing that to `ui.warn()` avoided the hang.  It also hung on
macOS, but without the large memory usage.

Our full contribution guidelines are in our wiki, please see:

https://www.mercurial-scm.org/wiki/ContributingChanges

If you just want a checklist to follow, you can go straight to

https://www.mercurial-scm.org/wiki/ContributingChanges#Submission_checklist

If you can't run the entire testsuite for some reason (it can be
difficult on Windows), please at least run `contrib/check-code.py` on
any files you've modified and run `python contrib/check-commit` on any
commits you've made (for example, `python contrib/check-commit
273ce12ad8f1` will report some style violations on a very old commit).