##// END OF EJS Templates
contrib: add a set of scripts to run pytype in Docker...
contrib: add a set of scripts to run pytype in Docker Having a simple way to run pytype for developers can massively shorten development cycle. Using the same Docker image and scripts that we use on our CI guarantees that the result achieved locally will be very similar to (if not the same as) the output of our CI runners. Things to note: the Dockerfile needs to do a little dance around user permissions inside /home/ci-runner/ because: - on one hand, creating new files on the host (e.g. .pyi files inside .pytype/) should use host user's uid and gid - on the other hand, when we run the image as uid:gid of host user, it needs to be able to read/execute files inside the image that are owned by ci-runner Since local user's uid might be different from ci-runner's uid, we execute this very broad chmod command inside /home/ci-runner/, but then run the image as the host user's uid:gid. There might be a better way to do this.

File last commit:

r41072:ce0bc295 default
r52200:87bfd170 default
Show More
TODO.rst
21 lines | 782 B | text/x-rst | RstLexer
Gregory Szorc
narrow: remove narrowrevlog...
r39807 Address commentary in manifest.excludedmanifestrevlog.add -
Augie Fackler
narrow: add a TODO document...
r36121 specifically we should improve the collaboration with core so that
add() never gets called on an excluded directory and we can improve
the stand-in to raise a ProgrammingError.
Reason more completely about rename-filtering logic in
narrowfilelog. There could be some surprises lurking there.
Martin von Zweigbergk
narrow: update TODO.rst now that we share format with sparse...
r40116 Formally document the narrowspec format. For bonus points, unify with the
server-specified narrowspec format.
Augie Fackler
narrow: add a TODO document...
r36121
narrowrepo.setnarrowpats() or narrowspec.save() need to make sure
they're holding the wlock.
Martin von Zweigbergk
narrow: move remaining narrow-limited dirstate walks to core...
r40123
The follinwg places do an unrestricted dirstate walk (including files outside the
narrowspec). Some of them should perhaps not do that.
* debugfileset
* perfwalk
* sparse (but restricted to sparse config)
* largefiles