lunny/git-lfs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
63d04e26c7
git-lfs/go.mod

48 lines
2.0 KiB
Modula-2
Raw Normal View History

go.mod,README.md: add caution about unstable API Since Git LFS is only intended to be utilized as a compiled binary and as we do not provide any guarantee of a stable API or ABI, add notes this effect in go.mod and our main README.
2021-08-16 03:54:07 +00:00
// The Git LFS project does not maintain a stable API or ABI for this module.
// Please do not import this module outside of the Git LFS project.
Set package version to v3 Since we're about to do a v3.0.0 release, let's bump the version to v3. Make this change automatically with the following command to avoid any missed items: git grep -l github.com/git-lfs/git-lfs/v2 | \ xargs sed -i -e 's!github.com/git-lfs/git-lfs/v2!github.com/git-lfs/git-lfs/v3!g'
2021-09-01 19:41:10 +00:00
module github.com/git-lfs/git-lfs/v3
all: use Go Modules instead of Glide Since we are now building on Go 1.11 (as of 074a2d4f (all: use Go 1.11 in CI, 2018-08-28)) and Go 1.11 supports Go Modules [1], let's stop using Glide, and begin using Go Modules. This involves a few things: * Teach the Makefile how to build go.sum files instead of glide.lock files. * Teach continuous integration services to build Git LFS in a non-$GOPATH environment, since (without setting GO111MODULE=on explicitly, which we choose not to do), this will break compiling Git LFS, because Go 1.11 will ignore modules present in a Go checkout beneath $GOPATH. * In order to do the above, let's also make sure that we are un-setting $GOCACHE in the environment, as this causes Go to work without modules support [2]. * Because we're no longer building in a `$GOPATH`-based location, let's instruct the CircleCI base image to archive the new location, too. * Similarly, teach the RPM spec to build in a non-$GOPATH location. * By contrast, since we use dh_golang to build git-lfs binaries on Debian, let's wait until the upstream dh_golang package is released with support for Go 1.11 module support explicitly. Therefore, force GO111MODULE to be on so that we can build a copy of Git LFS whose checkout is within a $GOPATH. Although the go.mod versions match the glide.yaml ones, the diff attached is large because Go Modules do not vendor `_test.go` files, whereas Glide does. [1]: https://golang.org/doc/go1.11#modules [2]: `GOCACHE=on` will be deprecated in Go 1.12, so this change makes sense for that reason, too. Co-authored-by: brian m. carlson <bk2204@github.com>
2018-08-28 20:53:57 +00:00
require (
Implement retry logic to fix LFS storage race conditions on Windows Testing showed that while race condition analysis in #3880 was correct, the way it tries to fix that does not work for the *first* git-lfs process that will actually perform file move. Instead, this commit performs multiple attempts when working with files in LFS storage. Similar logic is already implemented in "cmd/go/internal/robustio" and "cmd/go/internal/renameio" packages. However, they are not public, so we cannot use them.
2019-10-29 11:26:39 +00:00
github.com/avast/retry-go v2.4.2+incompatible
Bump go-spnego to the latest version This version uses a newer version of the Kerberos library, which should work better in some environments. Tidy the go.mod and go.sum files and vendor the dependencies.
2021-04-14 14:45:24 +00:00
github.com/dpotapov/go-spnego v0.0.0-20210315154721-298b63a54430
go.mod: bump gitobj to v2.1.1 Bump gitobj to a version which addresses a misparsing in commit headers.
2022-09-29 17:57:43 +00:00
github.com/git-lfs/gitobj/v2 v2.1.1
netrc: consider same machine may have different login names
2021-11-04 09:31:37 +00:00
github.com/git-lfs/go-netrc v0.0.0-20210914205454-f0c862dd687a
git: use pktline repository We have a pktline repository that provides our pkt-line code from Git LFS, but separated out into a separate, reusable repository. The current code is private to the git package, and since we'll want to use it in the future from multiple packages, it makes sense to just use the separate repository, which we want to do anyway. Let's include the repository in our go.mod and vendor the modules. Remove the old code and replace its use with the new code.
2021-02-08 21:25:03 +00:00
github.com/git-lfs/pktline v0.0.0-20210330133718-06e9096e2825
Bump wildmatch to v2.0.1 Now that we have a fully Git-compatible wildmatch, let's use it in Git LFS. Vendor the module appropriately.
2021-08-23 15:52:52 +00:00
github.com/git-lfs/wildmatch/v2 v2.0.1
go.mod: add module for gotext We'd like to support localization in Git LFS. To do so, add the gotext package, which implement gettext-compatible localization.
2021-11-09 20:56:58 +00:00
github.com/leonelquinteros/gotext v1.5.0
tasklog: don't log progress status when stdout is not a tty But make it overridable by either - setting lfs.forceprogress 1 - setting GIT_LFS_FORCE_PROGRESS=1
2018-10-30 08:06:55 +00:00
github.com/mattn/go-isatty v0.0.4
go.mod: use latest github.com/olekukonko/ts We use package github.com/olekukonko/ts to issue IOCTL's to gather the terminal size of the calling terminal in order to determine the length of lines we attempt to print. Until now, we have used revision ecf753e7c962, which is over 4 years old. Since then, github.com/olekukonko/ts has introduced support for Solaris, which we previously could not build or run on because package syscall on Solaris does not export an IOCTL constant. Let's upgrade to the latest version, and bring in support for Solaris.
2018-09-03 13:27:17 +00:00
github.com/olekukonko/ts v0.0.0-20171002115256-78ecb04241c0
all: use Go Modules instead of Glide Since we are now building on Go 1.11 (as of 074a2d4f (all: use Go 1.11 in CI, 2018-08-28)) and Go 1.11 supports Go Modules [1], let's stop using Glide, and begin using Go Modules. This involves a few things: * Teach the Makefile how to build go.sum files instead of glide.lock files. * Teach continuous integration services to build Git LFS in a non-$GOPATH environment, since (without setting GO111MODULE=on explicitly, which we choose not to do), this will break compiling Git LFS, because Go 1.11 will ignore modules present in a Go checkout beneath $GOPATH. * In order to do the above, let's also make sure that we are un-setting $GOCACHE in the environment, as this causes Go to work without modules support [2]. * Because we're no longer building in a `$GOPATH`-based location, let's instruct the CircleCI base image to archive the new location, too. * Similarly, teach the RPM spec to build in a non-$GOPATH location. * By contrast, since we use dh_golang to build git-lfs binaries on Debian, let's wait until the upstream dh_golang package is released with support for Go 1.11 module support explicitly. Therefore, force GO111MODULE to be on so that we can build a copy of Git LFS whose checkout is within a $GOPATH. Although the go.mod versions match the glide.yaml ones, the diff attached is large because Go Modules do not vendor `_test.go` files, whereas Glide does. [1]: https://golang.org/doc/go1.11#modules [2]: `GOCACHE=on` will be deprecated in Go 1.12, so this change makes sense for that reason, too. Co-authored-by: brian m. carlson <bk2204@github.com>
2018-08-28 20:53:57 +00:00
github.com/pkg/errors v0.0.0-20170505043639-c605e284fe17
github.com/rubyist/tracerx v0.0.0-20170927163412-787959303086
Update cobra to 1.7.0
2023-07-31 03:58:16 +00:00
github.com/spf13/cobra v1.7.0
Use different parser for cookiejar files The original parser that was used in #3825 brings in a lot of dependencies that complicate packaging git-lfs. This replaces it with a small parser I wrote with almost no dependencies. I've tested this as extensively as i can and it seems to work correctly.
2019-10-27 21:48:15 +00:00
github.com/ssgelm/cookiejarparser v1.0.1
Bump go-spnego to the latest version This version uses a newer version of the Kerberos library, which should work better in some environments. Tidy the go.mod and go.sum files and vendor the dependencies.
2021-04-14 14:45:24 +00:00
github.com/stretchr/testify v1.6.1
all: use Go Modules instead of Glide Since we are now building on Go 1.11 (as of 074a2d4f (all: use Go 1.11 in CI, 2018-08-28)) and Go 1.11 supports Go Modules [1], let's stop using Glide, and begin using Go Modules. This involves a few things: * Teach the Makefile how to build go.sum files instead of glide.lock files. * Teach continuous integration services to build Git LFS in a non-$GOPATH environment, since (without setting GO111MODULE=on explicitly, which we choose not to do), this will break compiling Git LFS, because Go 1.11 will ignore modules present in a Go checkout beneath $GOPATH. * In order to do the above, let's also make sure that we are un-setting $GOCACHE in the environment, as this causes Go to work without modules support [2]. * Because we're no longer building in a `$GOPATH`-based location, let's instruct the CircleCI base image to archive the new location, too. * Similarly, teach the RPM spec to build in a non-$GOPATH location. * By contrast, since we use dh_golang to build git-lfs binaries on Debian, let's wait until the upstream dh_golang package is released with support for Go 1.11 module support explicitly. Therefore, force GO111MODULE to be on so that we can build a copy of Git LFS whose checkout is within a $GOPATH. Although the go.mod versions match the glide.yaml ones, the diff attached is large because Go Modules do not vendor `_test.go` files, whereas Glide does. [1]: https://golang.org/doc/go1.11#modules [2]: `GOCACHE=on` will be deprecated in Go 1.12, so this change makes sense for that reason, too. Co-authored-by: brian m. carlson <bk2204@github.com>
2018-08-28 20:53:57 +00:00
github.com/xeipuuv/gojsonschema v0.0.0-20170210233622-6b67b3fab74d
Update golang.org/x/text The version we're using is vulnerable to CVE-2022-32149. We don't use the vulnerable code, but upgrade the remaining golang.org/x packages we depend on, since the text package is merely a dependency of them. In doing so, we'll update the text package, and avoid triggering any warning from vulnerability scanners. In addition, now that we're using released versions, it will be easier to keep things up to date.
2023-02-21 20:22:49 +00:00
golang.org/x/net v0.7.0
golang.org/x/sync v0.1.0
golang.org/x/sys v0.5.0
go.mod: bump version to 1.17 One of our dependencies now requires Go 1.17. Bump the version in go.mod accordingly. To please Go, now also run `go mod tidy`, which separates the indirect dependencies into separate stanzas.
2023-02-21 21:53:32 +00:00
)
require (
github.com/alexbrainman/sspi v0.0.0-20210105120005-909beea2cc74 // indirect
github.com/davecgh/go-spew v1.1.1 // indirect
github.com/hashicorp/go-uuid v1.0.2 // indirect
Update cobra to 1.7.0
2023-07-31 03:58:16 +00:00
github.com/inconshreveable/mousetrap v1.1.0 // indirect
go.mod: bump version to 1.17 One of our dependencies now requires Go 1.17. Bump the version in go.mod accordingly. To please Go, now also run `go mod tidy`, which separates the indirect dependencies into separate stanzas.
2023-02-21 21:53:32 +00:00
github.com/jcmturner/aescts/v2 v2.0.0 // indirect
github.com/jcmturner/dnsutils/v2 v2.0.0 // indirect
github.com/jcmturner/gofork v1.0.0 // indirect
github.com/jcmturner/goidentity/v6 v6.0.1 // indirect
github.com/jcmturner/gokrb5/v8 v8.4.2 // indirect
github.com/jcmturner/rpc/v2 v2.0.3 // indirect
go.*,lfs: mock time in copy callback log file test In commit 00f1e9521ab5d39aab393796745189d39c27b9a0 of PR #5504 we added the TestCopyCallbackFileThrottle() test function to confirm that the CopyCallbackFile() method of GitFilter structure in the "lfs" package now throttled its output of progress messages into a log file so that, in general, no more than one message was written during the interval defined by the tasklog.DefaultLoggingThrottle value. This new throttling behaviour was added in commit 5bfa9009dafce59789b88b1a0854691b596f6e76 in the same PR. The TestCopyCallbackFileThrottle() function attempts to validate the throttling action by reading a test buffer in segments and waiting or not waiting between each read, expecting the log messages to be written or not written, as appropriate. However, because our CI test suite may experience slow execution times as a result of running in virtualized environments, reads may occur at times more than the tasklog.DefaultLoggingThrottle interval apart even without the artifical waits injected by the test function, causing the test to fail when it sees more log messages than it expects. We can avoid this problem by making the wait intervals in the test deterministic using a mocked value for the current time. We use the github.com/jmhodges/clock package for this purpose, adding an object of its Clock interface type to the GitFilter structure. In all non-test code this object is simply a wrapper for the "time" package's functions, but in our test we can use a variant which allows us to control the time values returned to the CopyCallbackFile() method, either stepping forward or not, as we desire.
2023-09-28 06:13:30 +00:00
github.com/jmhodges/clock v1.2.0 // indirect
go.mod: bump version to 1.17 One of our dependencies now requires Go 1.17. Bump the version in go.mod accordingly. To please Go, now also run `go mod tidy`, which separates the indirect dependencies into separate stanzas.
2023-02-21 21:53:32 +00:00
github.com/pmezard/go-difflib v1.0.0 // indirect
Initial addition of shell completion script generator
2023-03-14 16:45:03 +00:00
github.com/spf13/pflag v1.0.5 // indirect
go.mod: bump version to 1.17 One of our dependencies now requires Go 1.17. Bump the version in go.mod accordingly. To please Go, now also run `go mod tidy`, which separates the indirect dependencies into separate stanzas.
2023-02-21 21:53:32 +00:00
github.com/xeipuuv/gojsonpointer v0.0.0-20180127040702-4e3ac2762d5f // indirect
github.com/xeipuuv/gojsonreference v0.0.0-20180127040603-bd5ef7bd5415 // indirect
golang.org/x/crypto v0.0.0-20220411220226-7b82a4e95df4 // indirect
golang.org/x/text v0.7.0 // indirect
go.mod: require gopkg.in/yaml.v3 v3.0.1 Versions before v3.0.0, including the version from 2020 we're using, lack the patches in v3.0.1 that fix a security issue. Update to v3.0.1 to improve the security situation here.
2022-06-01 16:06:37 +00:00
gopkg.in/yaml.v3 v3.0.1 // indirect
all: use Go Modules instead of Glide Since we are now building on Go 1.11 (as of 074a2d4f (all: use Go 1.11 in CI, 2018-08-28)) and Go 1.11 supports Go Modules [1], let's stop using Glide, and begin using Go Modules. This involves a few things: * Teach the Makefile how to build go.sum files instead of glide.lock files. * Teach continuous integration services to build Git LFS in a non-$GOPATH environment, since (without setting GO111MODULE=on explicitly, which we choose not to do), this will break compiling Git LFS, because Go 1.11 will ignore modules present in a Go checkout beneath $GOPATH. * In order to do the above, let's also make sure that we are un-setting $GOCACHE in the environment, as this causes Go to work without modules support [2]. * Because we're no longer building in a `$GOPATH`-based location, let's instruct the CircleCI base image to archive the new location, too. * Similarly, teach the RPM spec to build in a non-$GOPATH location. * By contrast, since we use dh_golang to build git-lfs binaries on Debian, let's wait until the upstream dh_golang package is released with support for Go 1.11 module support explicitly. Therefore, force GO111MODULE to be on so that we can build a copy of Git LFS whose checkout is within a $GOPATH. Although the go.mod versions match the glide.yaml ones, the diff attached is large because Go Modules do not vendor `_test.go` files, whereas Glide does. [1]: https://golang.org/doc/go1.11#modules [2]: `GOCACHE=on` will be deprecated in Go 1.12, so this change makes sense for that reason, too. Co-authored-by: brian m. carlson <bk2204@github.com>
2018-08-28 20:53:57 +00:00
)
go.mod: add go version declaration This declaration is automatically added by Go 1.13 if it doesn't exist during any build step. Since we don't want the file to be modified during normal use, explicitly declare it as 1.11, since that's the oldest version we currently support.
2019-09-04 19:59:01 +00:00
go.mod: bump version to 1.17 One of our dependencies now requires Go 1.17. Bump the version in go.mod accordingly. To please Go, now also run `go mod tidy`, which separates the indirect dependencies into separate stanzas.
2023-02-21 21:53:32 +00:00
go 1.17
Reference in New Issue Copy Permalink