MyFavMirrors/minio
1
0
Fork 0
mirror of https://github.com/minio/minio.git synced 2024-12-26 23:25:54 -05:00
Code Issues Packages Projects Releases Wiki Activity
716316f711
minio/vendor/vendor.json

257 lines
8.0 KiB
JSON
Raw Normal View History

Migrate to govendor to avoid limitations of godep - over the course of a project history every maintainer needs to update its dependency packages, the problem essentially with godep is manipulating GOPATH - this manipulation leads to static objects created at different locations which end up conflicting with the overall functionality of golang. This also leads to broken builds. There is no easier way out of this other than asking developers to do 'godep restore' all the time. Which perhaps as a practice doesn't sound like a clean solution. On the other hand 'godep restore' has its own set of problems. - govendor is a right tool but a stop gap tool until we wait for golangs official 1.5 version which fixes this vendoring issue once and for all. - govendor provides consistency in terms of how import paths should be handled unlike manipulation GOPATH. This has advantages - no more compiled objects being referenced in GOPATH and build time GOPATH manging which leads to conflicts. - proper import paths referencing the exact package a project is dependent on. govendor is simple and provides the minimal necessary tooling to achieve this. For now this is the right solution.
2015-08-12 22:24:31 -04:00
{
"comment": "",
web: Removing dependency for gpg and downloading assets. Assets are vendorized from now on and updated for each release.
2016-02-23 16:05:47 -05:00
"ignore": "appengine test",
Migrate to govendor to avoid limitations of godep - over the course of a project history every maintainer needs to update its dependency packages, the problem essentially with godep is manipulating GOPATH - this manipulation leads to static objects created at different locations which end up conflicting with the overall functionality of golang. This also leads to broken builds. There is no easier way out of this other than asking developers to do 'godep restore' all the time. Which perhaps as a practice doesn't sound like a clean solution. On the other hand 'godep restore' has its own set of problems. - govendor is a right tool but a stop gap tool until we wait for golangs official 1.5 version which fixes this vendoring issue once and for all. - govendor provides consistency in terms of how import paths should be handled unlike manipulation GOPATH. This has advantages - no more compiled objects being referenced in GOPATH and build time GOPATH manging which leads to conflicts. - proper import paths referencing the exact package a project is dependent on. govendor is simple and provides the minimal necessary tooling to achieve this. For now this is the right solution.
2015-08-12 22:24:31 -04:00
"package": [
logrus logger
2015-09-09 23:28:09 -04:00
{
Migrate to new govendor
2015-10-11 01:28:56 -04:00
"path": "github.com/Sirupsen/logrus",
vendorize: update all vendorized packages. (#2206) Bring in new changes from upstream for all the packages. Important ones include - gorilla/mux - logrus - jwt
2016-07-14 17:59:20 -04:00
"revision": "32055c351ea8b00b96d70f28db48d9840feaf0ec",
"revisionTime": "2016-07-12T20:17:32-04:00"
logrus logger
2015-09-09 23:28:09 -04:00
},
server: terminal width should fallback to 80x25. (#1895) Some environments might disable access to `/dev/tty`, fall back to '80' in such scenarios. Move to 'cheggaaa/pb' package for better cross platform support on fetching terminal width. Fixes #1891
2016-06-12 22:35:28 -04:00
{
"path": "github.com/cheggaaa/pb",
vendorize: update all vendorized packages. (#2206) Bring in new changes from upstream for all the packages. Important ones include - gorilla/mux - logrus - jwt
2016-07-14 17:59:20 -04:00
"revision": "73ae1d68fe0bd482ab11913a9828634f795b987f",
"revisionTime": "2016-07-13T13:44:25+03:00"
server: terminal width should fallback to 80x25. (#1895) Some environments might disable access to `/dev/tty`, fall back to '80' in such scenarios. Move to 'cheggaaa/pb' package for better cross platform support on fetching terminal width. Fixes #1891
2016-06-12 22:35:28 -04:00
},
jwt: Add JWT support for minio server. Please read JWT.md before using this feature.
2016-01-21 19:28:15 -05:00
{
"path": "github.com/dgrijalva/jwt-go",
vendorize: update all vendorized packages. (#2206) Bring in new changes from upstream for all the packages. Important ones include - gorilla/mux - logrus - jwt
2016-07-14 17:59:20 -04:00
"revision": "01aeca54ebda6e0fbfafd0a524d234159c05ec20",
"revisionTime": "2016-07-05T13:30:06-07:00"
},
{
"path": "github.com/dgrijalva/jwt-go/request",
"revision": "01aeca54ebda6e0fbfafd0a524d234159c05ec20",
"revisionTime": "2016-07-05T13:30:06-07:00"
jwt: Add JWT support for minio server. Please read JWT.md before using this feature.
2016-01-21 19:28:15 -05:00
},
Migrate to govendor to avoid limitations of godep - over the course of a project history every maintainer needs to update its dependency packages, the problem essentially with godep is manipulating GOPATH - this manipulation leads to static objects created at different locations which end up conflicting with the overall functionality of golang. This also leads to broken builds. There is no easier way out of this other than asking developers to do 'godep restore' all the time. Which perhaps as a practice doesn't sound like a clean solution. On the other hand 'godep restore' has its own set of problems. - govendor is a right tool but a stop gap tool until we wait for golangs official 1.5 version which fixes this vendoring issue once and for all. - govendor provides consistency in terms of how import paths should be handled unlike manipulation GOPATH. This has advantages - no more compiled objects being referenced in GOPATH and build time GOPATH manging which leads to conflicts. - proper import paths referencing the exact package a project is dependent on. govendor is simple and provides the minimal necessary tooling to achieve this. For now this is the right solution.
2015-08-12 22:24:31 -04:00
{
Migrate to new govendor
2015-10-11 01:28:56 -04:00
"path": "github.com/dustin/go-humanize",
vendorize: update all vendorized packages. (#2206) Bring in new changes from upstream for all the packages. Important ones include - gorilla/mux - logrus - jwt
2016-07-14 17:59:20 -04:00
"revision": "fef948f2d241bd1fd0631108ecc2c9553bae60bf",
"revisionTime": "2016-06-23T09:40:21+08:00"
Migrate to govendor to avoid limitations of godep - over the course of a project history every maintainer needs to update its dependency packages, the problem essentially with godep is manipulating GOPATH - this manipulation leads to static objects created at different locations which end up conflicting with the overall functionality of golang. This also leads to broken builds. There is no easier way out of this other than asking developers to do 'godep restore' all the time. Which perhaps as a practice doesn't sound like a clean solution. On the other hand 'godep restore' has its own set of problems. - govendor is a right tool but a stop gap tool until we wait for golangs official 1.5 version which fixes this vendoring issue once and for all. - govendor provides consistency in terms of how import paths should be handled unlike manipulation GOPATH. This has advantages - no more compiled objects being referenced in GOPATH and build time GOPATH manging which leads to conflicts. - proper import paths referencing the exact package a project is dependent on. govendor is simple and provides the minimal necessary tooling to achieve this. For now this is the right solution.
2015-08-12 22:24:31 -04:00
},
UI: vendorize github.com/elazarl/go-bindata-assetfs which is needed by ui-assets.go
2016-02-04 06:20:34 -05:00
{
"path": "github.com/elazarl/go-bindata-assetfs",
ui-assets: Integrate UI assets.
2016-02-04 19:00:52 -05:00
"revision": "57eb5e1fc594ad4b0b1dbea7b286d299e0cb43c2",
"revisionTime": "2015-12-24T06:54:52+02:00"
UI: vendorize github.com/elazarl/go-bindata-assetfs which is needed by ui-assets.go
2016-02-04 06:20:34 -05:00
},
Add WebUI assetfs initial version
2015-09-25 03:37:28 -04:00
{
Migrate this project to minio micro services code
2015-10-16 14:26:01 -04:00
"path": "github.com/fatih/color",
vendorize: update all vendorized packages. (#2206) Bring in new changes from upstream for all the packages. Important ones include - gorilla/mux - logrus - jwt
2016-07-14 17:59:20 -04:00
"revision": "87d4004f2ab62d0d255e0a38f1680aa534549fe3",
"revisionTime": "2016-06-10T14:06:02+03:00"
Migrate to govendor to avoid limitations of godep - over the course of a project history every maintainer needs to update its dependency packages, the problem essentially with godep is manipulating GOPATH - this manipulation leads to static objects created at different locations which end up conflicting with the overall functionality of golang. This also leads to broken builds. There is no easier way out of this other than asking developers to do 'godep restore' all the time. Which perhaps as a practice doesn't sound like a clean solution. On the other hand 'godep restore' has its own set of problems. - govendor is a right tool but a stop gap tool until we wait for golangs official 1.5 version which fixes this vendoring issue once and for all. - govendor provides consistency in terms of how import paths should be handled unlike manipulation GOPATH. This has advantages - no more compiled objects being referenced in GOPATH and build time GOPATH manging which leads to conflicts. - proper import paths referencing the exact package a project is dependent on. govendor is simple and provides the minimal necessary tooling to achieve this. For now this is the right solution.
2015-08-12 22:24:31 -04:00
},
{
Migrate this project to minio micro services code
2015-10-16 14:26:01 -04:00
"path": "github.com/gorilla/context",
vendorize: update all vendorized packages. (#2206) Bring in new changes from upstream for all the packages. Important ones include - gorilla/mux - logrus - jwt
2016-07-14 17:59:20 -04:00
"revision": "aed02d124ae4a0e94fea4541c8effd05bf0c8296",
"revisionTime": "2016-05-25T13:33:19-07:00"
Migrate to govendor to avoid limitations of godep - over the course of a project history every maintainer needs to update its dependency packages, the problem essentially with godep is manipulating GOPATH - this manipulation leads to static objects created at different locations which end up conflicting with the overall functionality of golang. This also leads to broken builds. There is no easier way out of this other than asking developers to do 'godep restore' all the time. Which perhaps as a practice doesn't sound like a clean solution. On the other hand 'godep restore' has its own set of problems. - govendor is a right tool but a stop gap tool until we wait for golangs official 1.5 version which fixes this vendoring issue once and for all. - govendor provides consistency in terms of how import paths should be handled unlike manipulation GOPATH. This has advantages - no more compiled objects being referenced in GOPATH and build time GOPATH manging which leads to conflicts. - proper import paths referencing the exact package a project is dependent on. govendor is simple and provides the minimal necessary tooling to achieve this. For now this is the right solution.
2015-08-12 22:24:31 -04:00
},
browser-assets: serve asset files with compression.
2016-03-03 21:15:56 -05:00
{
"path": "github.com/gorilla/handlers",
vendorize: update all vendorized packages. (#2206) Bring in new changes from upstream for all the packages. Important ones include - gorilla/mux - logrus - jwt
2016-07-14 17:59:20 -04:00
"revision": "66e6c6f01d8da976ee113437745ca029c2b585a6",
"revisionTime": "2016-04-10T11:53:17-07:00"
browser-assets: serve asset files with compression.
2016-03-03 21:15:56 -05:00
},
Migrate to govendor to avoid limitations of godep - over the course of a project history every maintainer needs to update its dependency packages, the problem essentially with godep is manipulating GOPATH - this manipulation leads to static objects created at different locations which end up conflicting with the overall functionality of golang. This also leads to broken builds. There is no easier way out of this other than asking developers to do 'godep restore' all the time. Which perhaps as a practice doesn't sound like a clean solution. On the other hand 'godep restore' has its own set of problems. - govendor is a right tool but a stop gap tool until we wait for golangs official 1.5 version which fixes this vendoring issue once and for all. - govendor provides consistency in terms of how import paths should be handled unlike manipulation GOPATH. This has advantages - no more compiled objects being referenced in GOPATH and build time GOPATH manging which leads to conflicts. - proper import paths referencing the exact package a project is dependent on. govendor is simple and provides the minimal necessary tooling to achieve this. For now this is the right solution.
2015-08-12 22:24:31 -04:00
{
Migrate this project to minio micro services code
2015-10-16 14:26:01 -04:00
"path": "github.com/gorilla/mux",
vendorize: update all vendorized packages. (#2206) Bring in new changes from upstream for all the packages. Important ones include - gorilla/mux - logrus - jwt
2016-07-14 17:59:20 -04:00
"revision": "9fa818a44c2bf1396a17f9d5a3c0f6dd39d2ff8e",
"revisionTime": "2016-06-05T16:35:21-07:00"
Migrate to govendor to avoid limitations of godep - over the course of a project history every maintainer needs to update its dependency packages, the problem essentially with godep is manipulating GOPATH - this manipulation leads to static objects created at different locations which end up conflicting with the overall functionality of golang. This also leads to broken builds. There is no easier way out of this other than asking developers to do 'godep restore' all the time. Which perhaps as a practice doesn't sound like a clean solution. On the other hand 'godep restore' has its own set of problems. - govendor is a right tool but a stop gap tool until we wait for golangs official 1.5 version which fixes this vendoring issue once and for all. - govendor provides consistency in terms of how import paths should be handled unlike manipulation GOPATH. This has advantages - no more compiled objects being referenced in GOPATH and build time GOPATH manging which leads to conflicts. - proper import paths referencing the exact package a project is dependent on. govendor is simple and provides the minimal necessary tooling to achieve this. For now this is the right solution.
2015-08-12 22:24:31 -04:00
},
Bring in the list APIs implemented by Bala <bala@minio.io>
2016-01-23 22:44:32 -05:00
{
"path": "github.com/gorilla/rpc/v2",
vendorize: update all vendorized packages. (#2206) Bring in new changes from upstream for all the packages. Important ones include - gorilla/mux - logrus - jwt
2016-07-14 17:59:20 -04:00
"revision": "bd3317b8f6704b1b40e4e705ec9e987a535cd5d3",
"revisionTime": "2016-05-16T23:23:31-07:00"
Bring in the list APIs implemented by Bala <bala@minio.io>
2016-01-23 22:44:32 -05:00
},
{
WebUI: move from rpc/v2/json to rpc/v2/json2 which has better error response structure.
2016-02-11 13:11:43 -05:00
"path": "github.com/gorilla/rpc/v2/json2",
vendorize: update all vendorized packages. (#2206) Bring in new changes from upstream for all the packages. Important ones include - gorilla/mux - logrus - jwt
2016-07-14 17:59:20 -04:00
"revision": "bd3317b8f6704b1b40e4e705ec9e987a535cd5d3",
"revisionTime": "2016-05-16T23:23:31-07:00"
Bring in the list APIs implemented by Bala <bala@minio.io>
2016-01-23 22:44:32 -05:00
},
rewrite minio runtime checks
2016-02-15 07:26:56 -05:00
{
"path": "github.com/hashicorp/go-version",
"revision": "7e3c02b30806fa5779d3bdfc152ce4c6f40e7b38",
"revisionTime": "2016-01-19T13:13:26-08:00"
},
cpu: Remove pkg/cpu in favor of better klauspost/cpuid. Fixes #1128
2016-02-15 15:45:02 -05:00
{
"path": "github.com/klauspost/cpuid",
"revision": "349c675778172472f5e8f3a3e0fe187e302e5a10",
"revisionTime": "2016-01-06T11:44:51+01:00"
},
Implement XL layer - preliminary work.
2016-03-28 00:52:38 -04:00
{
vendor: update reedsolomon package with new changes. (#2870) - Cached inverse matrices for better reconstruct performance. - New error reconstruction required is returned, helpful in initiating healing.
2016-10-07 00:57:42 -04:00
"checksumSHA1": "XRii0aDqXZvztXflEB2EE9TRoks=",
Implement XL layer - preliminary work.
2016-03-28 00:52:38 -04:00
"path": "github.com/klauspost/reedsolomon",
vendor: update reedsolomon package with new changes. (#2870) - Cached inverse matrices for better reconstruct performance. - New error reconstruction required is returned, helpful in initiating healing.
2016-10-07 00:57:42 -04:00
"revision": "c54154da9e35cab25232314cf69ab9d78447f9a5",
"revisionTime": "2016-09-12T19:31:07Z"
Implement XL layer - preliminary work.
2016-03-28 00:52:38 -04:00
},
Add PostgreSQL notifier (#2739) (#2824) * The user is required to specify a table name and database connection information in the configuration file. * INSERTs and DELETEs are done via prepared statements for speed. * Assumes a table structure, and requires PostgreSQL 9.5 or above due to the use of UPSERT. * Creates the table if it does not exist with the given table name using a query like: CREATE TABLE myminio ( key varchar PRIMARY KEY, value JSONB ); * Vendors some required libraries.
2016-10-03 20:29:55 -04:00
{
"checksumSHA1": "dNYxHiBLalTqluak2/Z8c3RsSEM=",
"path": "github.com/lib/pq",
"revision": "50761b0867bd1d9d069276790bcd4a3bccf2324a",
"revisionTime": "2016-08-31T22:25:20Z"
},
{
"checksumSHA1": "xppHi82MLqVx1eyQmbhTesAEjx8=",
"path": "github.com/lib/pq/oid",
"revision": "50761b0867bd1d9d069276790bcd4a3bccf2324a",
"revisionTime": "2016-08-31T22:25:20Z"
},
vendor: Update to new upstream changes from fatih/color Brings in changes like support for Solaris/FreeBSD.
2016-02-23 17:56:47 -05:00
{
"path": "github.com/mattn/go-colorable",
vendorize: update all vendorized packages. (#2206) Bring in new changes from upstream for all the packages. Important ones include - gorilla/mux - logrus - jwt
2016-07-14 17:59:20 -04:00
"revision": "9056b7a9f2d1f2d96498d6d146acd1f9d5ed3d59",
"revisionTime": "2016-06-03T00:08:27+09:00"
vendor: Update to new upstream changes from fatih/color Brings in changes like support for Solaris/FreeBSD.
2016-02-23 17:56:47 -05:00
},
First time mode for controller - Upon first time invocation ``minio controller`` would create access keys and secret id - Upon request passing 'keys' arg ``minio controller`` would provide the keys - Add colorized notification
2015-10-04 19:31:07 -04:00
{
Migrate this project to minio micro services code
2015-10-16 14:26:01 -04:00
"path": "github.com/mattn/go-isatty",
vendorize: update all vendorized packages. (#2206) Bring in new changes from upstream for all the packages. Important ones include - gorilla/mux - logrus - jwt
2016-07-14 17:59:20 -04:00
"revision": "56b76bdf51f7708750eac80fa38b952bb9f32639",
"revisionTime": "2015-12-11T09:06:21+09:00"
First time mode for controller - Upon first time invocation ``minio controller`` would create access keys and secret id - Upon request passing 'keys' arg ``minio controller`` would provide the keys - Add colorized notification
2015-10-04 19:31:07 -04:00
},
XL/bitrot: Migrate to new blake2b-simd SIMD optimized implementation. (#2031) Thanks for Frank Wessels <fwessels@xs4all.nl> for all the heavy lifting work. Comparative benchmarks are as below. ``` benchmark old ns/op new ns/op delta BenchmarkHash64-4 742 411 -44.61% BenchmarkHash128-4 681 346 -49.19% BenchmarkWrite1K-4 4239 1497 -64.69% BenchmarkWrite8K-4 33633 11514 -65.77% BenchmarkWrite32K-4 134091 45947 -65.73% BenchmarkWrite128K-4 537976 183643 -65.86% benchmark old MB/s new MB/s speedup BenchmarkHash64-4 86.18 155.51 1.80x BenchmarkHash128-4 187.96 369.10 1.96x BenchmarkWrite1K-4 241.55 683.87 2.83x BenchmarkWrite8K-4 3897.06 11383.41 2.92x BenchmarkWrite32K-4 977.48 2852.63 2.92x BenchmarkWrite128K-4 243.64 713.73 2.93x ``` Fixes #2030
2016-06-29 05:06:35 -04:00
{
"path": "github.com/minio/blake2b-simd",
vendor: Bring new updates from blake2b-simd repo. (#2094) This vendorization is needed to bring in new improvements and support for AVX2 and SSE. Fixes #2081
2016-07-06 21:24:31 -04:00
"revision": "25efc542f2c5064cf312cdca043790a7af861c4c",
"revisionTime": "2016-07-06T10:29:24+02:00"
XL/bitrot: Migrate to new blake2b-simd SIMD optimized implementation. (#2031) Thanks for Frank Wessels <fwessels@xs4all.nl> for all the heavy lifting work. Comparative benchmarks are as below. ``` benchmark old ns/op new ns/op delta BenchmarkHash64-4 742 411 -44.61% BenchmarkHash128-4 681 346 -49.19% BenchmarkWrite1K-4 4239 1497 -64.69% BenchmarkWrite8K-4 33633 11514 -65.77% BenchmarkWrite32K-4 134091 45947 -65.73% BenchmarkWrite128K-4 537976 183643 -65.86% benchmark old MB/s new MB/s speedup BenchmarkHash64-4 86.18 155.51 1.80x BenchmarkHash128-4 187.96 369.10 1.96x BenchmarkWrite1K-4 241.55 683.87 2.83x BenchmarkWrite8K-4 3897.06 11383.41 2.92x BenchmarkWrite32K-4 977.48 2852.63 2.92x BenchmarkWrite128K-4 243.64 713.73 2.93x ``` Fixes #2030
2016-06-29 05:06:35 -04:00
},
Migrate to govendor to avoid limitations of godep - over the course of a project history every maintainer needs to update its dependency packages, the problem essentially with godep is manipulating GOPATH - this manipulation leads to static objects created at different locations which end up conflicting with the overall functionality of golang. This also leads to broken builds. There is no easier way out of this other than asking developers to do 'godep restore' all the time. Which perhaps as a practice doesn't sound like a clean solution. On the other hand 'godep restore' has its own set of problems. - govendor is a right tool but a stop gap tool until we wait for golangs official 1.5 version which fixes this vendoring issue once and for all. - govendor provides consistency in terms of how import paths should be handled unlike manipulation GOPATH. This has advantages - no more compiled objects being referenced in GOPATH and build time GOPATH manging which leads to conflicts. - proper import paths referencing the exact package a project is dependent on. govendor is simple and provides the minimal necessary tooling to achieve this. For now this is the right solution.
2015-08-12 22:24:31 -04:00
{
Migrate this project to minio micro services code
2015-10-16 14:26:01 -04:00
"path": "github.com/minio/cli",
cli: vendorize to new CLI package updates. - Fix a new line issue for minioHelpTemplate. - Fixes #974
2015-11-21 11:57:38 -05:00
"revision": "c4a07c7b68db77ccd119183fb1d01dd5972434ab",
"revisionTime": "2015-11-18T20:00:48-08:00"
Migrate to govendor to avoid limitations of godep - over the course of a project history every maintainer needs to update its dependency packages, the problem essentially with godep is manipulating GOPATH - this manipulation leads to static objects created at different locations which end up conflicting with the overall functionality of golang. This also leads to broken builds. There is no easier way out of this other than asking developers to do 'godep restore' all the time. Which perhaps as a practice doesn't sound like a clean solution. On the other hand 'godep restore' has its own set of problems. - govendor is a right tool but a stop gap tool until we wait for golangs official 1.5 version which fixes this vendoring issue once and for all. - govendor provides consistency in terms of how import paths should be handled unlike manipulation GOPATH. This has advantages - no more compiled objects being referenced in GOPATH and build time GOPATH manging which leads to conflicts. - proper import paths referencing the exact package a project is dependent on. govendor is simple and provides the minimal necessary tooling to achieve this. For now this is the right solution.
2015-08-12 22:24:31 -04:00
},
distribute: Make server work with multiple remote disks This change initializes rpc servers associated with disks that are local. It makes object layer initialization on demand, namely on the first request to the object layer. Also adds lock RPC service vendorized minio/dsync
2016-07-31 17:11:14 -04:00
{
New dsync and added ForceUnlock to lock rpc server (#2956) * Update dsync and added ForceUnlock function * Added test cases for ForceUnlock
2016-10-17 04:53:29 -04:00
"checksumSHA1": "UWpLeW+oLfe/MiphMckp1HqKrW0=",
distribute: Make server work with multiple remote disks This change initializes rpc servers associated with disks that are local. It makes object layer initialization on demand, namely on the first request to the object layer. Also adds lock RPC service vendorized minio/dsync
2016-07-31 17:11:14 -04:00
"path": "github.com/minio/dsync",
New dsync and added ForceUnlock to lock rpc server (#2956) * Update dsync and added ForceUnlock function * Added test cases for ForceUnlock
2016-10-17 04:53:29 -04:00
"revision": "fcea3bf5533c1b8a5af3cb377d30363782d2532d",
"revisionTime": "2016-10-15T15:40:54Z"
distribute: Make server work with multiple remote disks This change initializes rpc servers associated with disks that are local. It makes object layer initialization on demand, namely on the first request to the object layer. Also adds lock RPC service vendorized minio/dsync
2016-07-31 17:11:14 -04:00
},
rewrite minio runtime checks
2016-02-15 07:26:56 -05:00
{
"path": "github.com/minio/go-homedir",
vendor update for go-homedir
2016-02-18 02:32:41 -05:00
"revision": "0b1069c753c94b3633cc06a1995252dbcc27c7a6",
"revisionTime": "2016-02-15T17:25:11+05:30"
rewrite minio runtime checks
2016-02-15 07:26:56 -05:00
},
console: Fix console color printing on windows. Print colored accessKeyID and secretAccessKey are unreadable on windows on command prompts and powershell. Use the console package from minio client.
2016-03-04 04:50:59 -05:00
{
"path": "github.com/minio/mc/pkg/console",
"revision": "db6b4f13442b26995f04b3b2b31b006cae7786e6",
"revisionTime": "2016-02-29T08:42:30-08:00"
},
web: add handlers for set/get bucket policy. (#2486) Refer #1858
2016-08-30 13:04:50 -04:00
{
web: add method to get all policies for given bucket name. (#2756) Refer #1858
2016-09-23 02:06:45 -04:00
"checksumSHA1": "qTxOBp3GVxCC70ykb7Hxg6UgWwA=",
web: add handlers for set/get bucket policy. (#2486) Refer #1858
2016-08-30 13:04:50 -04:00
"path": "github.com/minio/minio-go/pkg/policy",
web: add method to get all policies for given bucket name. (#2756) Refer #1858
2016-09-23 02:06:45 -04:00
"revision": "40505f5d08c721dfe5a6450fbdef3bcd6567aa97",
"revisionTime": "2016-09-04T08:12:15Z"
web: add handlers for set/get bucket policy. (#2486) Refer #1858
2016-08-30 13:04:50 -04:00
},
api/bucketPolicy: Use minio-go/pkg/set and fix bucket policy regression. (#2506) Current master has a regression 'mc policy <policy-type> alias/bucket/prefix' does not work anymore, due to the way new minio-go changes do json marshalling. This led to a regression on server side when a ``prefix`` is provided policy is rejected as malformed from th server which is not the case with AWS S3. This patch uses the new ``minio-go/pkg/set`` package to address the unmarshalling problems. Fixes #2503
2016-08-20 06:16:38 -04:00
{
"checksumSHA1": "A8QOw1aWwc+RtjGozY0XeS5varo=",
"path": "github.com/minio/minio-go/pkg/set",
"revision": "9e734013294ab153b0bdbe182738bcddd46f1947",
"revisionTime": "2016-08-18T00:31:20Z"
},
web: Removing dependency for gpg and downloading assets. Assets are vendorized from now on and updated for each release.
2016-02-23 16:05:47 -05:00
{
Update minio browser with new changes. (#2940) - Bucket policy set/unset support. - Shareable URL support. - Delete object support.
2016-10-15 11:51:53 -04:00
"checksumSHA1": "Gok4D2jDvlfXeygOMO+7G9isas0=",
web: Removing dependency for gpg and downloading assets. Assets are vendorized from now on and updated for each release.
2016-02-23 16:05:47 -05:00
"path": "github.com/minio/miniobrowser",
Update minio browser with new changes. (#2940) - Bucket policy set/unset support. - Shareable URL support. - Delete object support.
2016-10-15 11:51:53 -04:00
"revision": "9d4da540a5d8fd8762c53cdc8b11d3f543eac73a",
"revisionTime": "2016-10-15T15:17:03Z"
web: Removing dependency for gpg and downloading assets. Assets are vendorized from now on and updated for each release.
2016-02-23 16:05:47 -05:00
},
rewrite minio runtime checks
2016-02-15 07:26:56 -05:00
{
api: Implement bucket notification. (#2271) * Implement basic S3 notifications through queues Supports multiple queues and three basic queue types: 1. NilQueue -- messages don't get sent anywhere 2. LogQueue -- messages get logged 3. AmqpQueue -- messages are sent to an AMQP queue * api: Implement bucket notification. Supports two different queue types - AMQP - ElasticSearch. * Add support for redis
2016-07-24 01:51:12 -04:00
"checksumSHA1": "GOSe2XEQI4AYwrMoLZu8vtmzkJM=",
"path": "github.com/minio/redigo/redis",
"revision": "5e2117cd32d677a36dcd8c9c83776a065555653b",
"revisionTime": "2016-07-24T00:05:56Z"
rewrite minio runtime checks
2016-02-15 07:26:56 -05:00
},
Switched to faster minio/sha256-simd implementation (#2320)
2016-07-28 17:44:37 -04:00
{
vendor: sha256 32bit updated. (#2459)
2016-08-16 19:19:29 -04:00
"checksumSHA1": "i8Hl0yGP1jqorMgfFMoJCItnI38=",
Switched to faster minio/sha256-simd implementation (#2320)
2016-07-28 17:44:37 -04:00
"path": "github.com/minio/sha256-simd",
vendor: sha256 32bit updated. (#2459)
2016-08-16 19:19:29 -04:00
"revision": "6f50cd1d784b2bea46167b6929f16c0d12eefbfb",
"revisionTime": "2016-08-16T22:25:11Z"
Switched to faster minio/sha256-simd implementation (#2320)
2016-07-28 17:44:37 -04:00
},
Add NATS notifier (#2795)
2016-09-30 02:42:10 -04:00
{
"checksumSHA1": "Nj7vQ2GlvJiPP7sqJX5AurrDSD4=",
"path": "github.com/nats-io/nats",
"revision": "70b70be17b77e8da86b6a3bcfe94fb22718a8dd0",
"revisionTime": "2016-09-16T18:17:35Z"
},
{
"checksumSHA1": "qAIuHdtQrDi2fFmpaP1dZLbgpGc=",
"path": "github.com/nats-io/nats/encoders/builtin",
"revision": "70b70be17b77e8da86b6a3bcfe94fb22718a8dd0",
"revisionTime": "2016-09-16T18:17:35Z"
},
{
"checksumSHA1": "i8Yom1KrpDKwjlGH/gpJGAQmo68=",
"path": "github.com/nats-io/nuid",
"revision": "289cccf02c178dc782430d534e3c1f5b72af807f",
"revisionTime": "2016-09-27T04:49:45Z"
},
server: Enable server profiling as needed. (#1565)
2016-05-09 19:18:56 -04:00
{
"path": "github.com/pkg/profile",
vendor changes to pkg/profile (#1671)
2016-05-18 12:22:06 -04:00
"revision": "c78aac22bd43883fd2817833b982153dcac17b3b",
"revisionTime": "2016-05-18T16:56:57+10:00"
server: Enable server profiling as needed. (#1565)
2016-05-09 19:18:56 -04:00
},
Enable controller to have CORS
2015-08-31 04:47:05 -04:00
{
Migrate to new govendor
2015-10-11 01:28:56 -04:00
"path": "github.com/rs/cors",
vendorize: update all vendorized packages. (#2206) Bring in new changes from upstream for all the packages. Important ones include - gorilla/mux - logrus - jwt
2016-07-14 17:59:20 -04:00
"revision": "a62a804a8a009876ca59105f7899938a1349f4b3",
"revisionTime": "2016-06-18T04:49:35+05:30"
},
{
"path": "github.com/rs/xhandler",
"revision": "ed27b6fd65218132ee50cd95f38474a3d8a2cd12",
"revisionTime": "2016-06-18T12:32:21-07:00"
Enable controller to have CORS
2015-08-31 04:47:05 -04:00
},
backend/fs: Refactor multipart upload This patch modifies multipart upload related functions as below * New multipart upload call creates file EXPORT_DIR/.minio/BUCKET/PATH/TO/OBJECT/UPLOAD_ID.uploadid * Put object part call creates file EXPORT_DIR/.minio/BUCKET/PATH/TO/OBJECT/UPLOAD_ID.PART_NUMBER.MD5SUM_STRING * Abort multipart call removes all files matching EXPORT_DIR/.minio/BUCKET/PATH/TO/OBJECT/UPLOAD_ID.* * Complete multipart call does 1. creates a staging file EXPORT_DIR/.minio/BUCKET/PATH/TO/OBJECT/UPLOAD_ID.complete.TEMP_NAME then renames to EXPORT_DIR/.minio/BUCKET/PATH/TO/OBJECT/UPLOAD_ID.complete 2. rename staging file EXPORT_DIR/.minio/BUCKET/PATH/TO/OBJECT/UPLOAD_ID.complete to EXPORT_DIR/BUCKET/PATH/TO/OBJECT
2016-03-28 12:52:09 -04:00
{
"checksumSHA1": "u0hXGADM3JDza8YjgiyNJpAJk8g=",
"path": "github.com/skyrings/skyring-common/tools/uuid",
"revision": "762fd2bfc12e766d90478d638255981ab1966a3d",
"revisionTime": "2016-03-24T19:44:43+05:30"
},
api: Implement bucket notification. (#2271) * Implement basic S3 notifications through queues Supports multiple queues and three basic queue types: 1. NilQueue -- messages don't get sent anywhere 2. LogQueue -- messages get logged 3. AmqpQueue -- messages are sent to an AMQP queue * api: Implement bucket notification. Supports two different queue types - AMQP - ElasticSearch. * Add support for redis
2016-07-24 01:51:12 -04:00
{
"checksumSHA1": "rKV8YLkXpeNG1Oix8hlYqVsEFb4=",
"path": "github.com/streadway/amqp",
"revision": "2e25825abdbd7752ff08b270d313b93519a0a232",
"revisionTime": "2016-03-11T21:55:03Z"
},
performance: gjson parsing for readXLMeta, listParts, getObjectInfo. (#2631) - Using gjson for constructing xlMetaV1{} in realXLMeta. - Test for parsing constructing xlMetaV1{} using gjson. - Changes made since benchmarks showed 30-40% improvement in speed. - Follow up comments in issue https://github.com/minio/minio/issues/2208 for more details. - gjson parsing of parts from xl.json for listParts. - gjson parsing of statInfo from xl.json for getObjectInfo. - Vendorizing gjson dependency.
2016-09-09 01:38:18 -04:00
{
"checksumSHA1": "+Pcohsuq0Mi/y8bgaDFjb/CGzkk=",
"path": "github.com/tidwall/gjson",
"revision": "7c631e98686a791e5fc60ff099512968122afb52",
"revisionTime": "2016-09-08T16:02:40Z"
},
{
"checksumSHA1": "qmePMXEDYGwkAfT9QvtMC58JN/E=",
"path": "github.com/tidwall/match",
"revision": "173748da739a410c5b0b813b956f89ff94730b4c",
"revisionTime": "2016-08-30T17:39:30Z"
},
jwt: Add JWT support for minio server. Please read JWT.md before using this feature.
2016-01-21 19:28:15 -05:00
{
"path": "golang.org/x/crypto/bcrypt",
"revision": "7b85b097bf7527677d54d3220065e966a0e3b613",
"revisionTime": "2015-11-30T17:07:01-05:00"
},
{
"path": "golang.org/x/crypto/blowfish",
"revision": "7b85b097bf7527677d54d3220065e966a0e3b613",
"revisionTime": "2015-11-30T17:07:01-05:00"
},
vendorize: update all vendorized packages. (#2206) Bring in new changes from upstream for all the packages. Important ones include - gorilla/mux - logrus - jwt
2016-07-14 17:59:20 -04:00
{
"path": "golang.org/x/net/context",
"revision": "a728288923b47049b2ce791836767ffbe964a5bd",
"revisionTime": "2016-07-07T15:24:52-07:00"
},
Migrate to govendor to avoid limitations of godep - over the course of a project history every maintainer needs to update its dependency packages, the problem essentially with godep is manipulating GOPATH - this manipulation leads to static objects created at different locations which end up conflicting with the overall functionality of golang. This also leads to broken builds. There is no easier way out of this other than asking developers to do 'godep restore' all the time. Which perhaps as a practice doesn't sound like a clean solution. On the other hand 'godep restore' has its own set of problems. - govendor is a right tool but a stop gap tool until we wait for golangs official 1.5 version which fixes this vendoring issue once and for all. - govendor provides consistency in terms of how import paths should be handled unlike manipulation GOPATH. This has advantages - no more compiled objects being referenced in GOPATH and build time GOPATH manging which leads to conflicts. - proper import paths referencing the exact package a project is dependent on. govendor is simple and provides the minimal necessary tooling to achieve this. For now this is the right solution.
2015-08-12 22:24:31 -04:00
{
Migrate to new govendor
2015-10-11 01:28:56 -04:00
"path": "gopkg.in/check.v1",
Migrate to govendor to avoid limitations of godep - over the course of a project history every maintainer needs to update its dependency packages, the problem essentially with godep is manipulating GOPATH - this manipulation leads to static objects created at different locations which end up conflicting with the overall functionality of golang. This also leads to broken builds. There is no easier way out of this other than asking developers to do 'godep restore' all the time. Which perhaps as a practice doesn't sound like a clean solution. On the other hand 'godep restore' has its own set of problems. - govendor is a right tool but a stop gap tool until we wait for golangs official 1.5 version which fixes this vendoring issue once and for all. - govendor provides consistency in terms of how import paths should be handled unlike manipulation GOPATH. This has advantages - no more compiled objects being referenced in GOPATH and build time GOPATH manging which leads to conflicts. - proper import paths referencing the exact package a project is dependent on. govendor is simple and provides the minimal necessary tooling to achieve this. For now this is the right solution.
2015-08-12 22:24:31 -04:00
"revision": "11d3bc7aa68e238947792f30573146a3231fc0f1",
"revisionTime": "2015-07-29T10:04:31+02:00"
api: Implement bucket notification. (#2271) * Implement basic S3 notifications through queues Supports multiple queues and three basic queue types: 1. NilQueue -- messages don't get sent anywhere 2. LogQueue -- messages get logged 3. AmqpQueue -- messages are sent to an AMQP queue * api: Implement bucket notification. Supports two different queue types - AMQP - ElasticSearch. * Add support for redis
2016-07-24 01:51:12 -04:00
},
{
"checksumSHA1": "eC4OV7g1tug838fPWrwflstr/TM=",
"path": "gopkg.in/olivere/elastic.v3",
"revision": "f7ae701daf3abe5dfb99f57b3f47738ec93c9c26",
"revisionTime": "2016-07-16T10:42:39Z"
},
{
"checksumSHA1": "lLdKOn9RPtFoTtPUNq5+sIInAiE=",
"path": "gopkg.in/olivere/elastic.v3/backoff",
"revision": "f7ae701daf3abe5dfb99f57b3f47738ec93c9c26",
"revisionTime": "2016-07-16T10:42:39Z"
},
{
"checksumSHA1": "XQg6xG6l15Ke43KolthYYnVDCYo=",
"path": "gopkg.in/olivere/elastic.v3/uritemplates",
"revision": "f7ae701daf3abe5dfb99f57b3f47738ec93c9c26",
"revisionTime": "2016-07-16T10:42:39Z"
Migrate to govendor to avoid limitations of godep - over the course of a project history every maintainer needs to update its dependency packages, the problem essentially with godep is manipulating GOPATH - this manipulation leads to static objects created at different locations which end up conflicting with the overall functionality of golang. This also leads to broken builds. There is no easier way out of this other than asking developers to do 'godep restore' all the time. Which perhaps as a practice doesn't sound like a clean solution. On the other hand 'godep restore' has its own set of problems. - govendor is a right tool but a stop gap tool until we wait for golangs official 1.5 version which fixes this vendoring issue once and for all. - govendor provides consistency in terms of how import paths should be handled unlike manipulation GOPATH. This has advantages - no more compiled objects being referenced in GOPATH and build time GOPATH manging which leads to conflicts. - proper import paths referencing the exact package a project is dependent on. govendor is simple and provides the minimal necessary tooling to achieve this. For now this is the right solution.
2015-08-12 22:24:31 -04:00
}
backend/fs: Refactor multipart upload This patch modifies multipart upload related functions as below * New multipart upload call creates file EXPORT_DIR/.minio/BUCKET/PATH/TO/OBJECT/UPLOAD_ID.uploadid * Put object part call creates file EXPORT_DIR/.minio/BUCKET/PATH/TO/OBJECT/UPLOAD_ID.PART_NUMBER.MD5SUM_STRING * Abort multipart call removes all files matching EXPORT_DIR/.minio/BUCKET/PATH/TO/OBJECT/UPLOAD_ID.* * Complete multipart call does 1. creates a staging file EXPORT_DIR/.minio/BUCKET/PATH/TO/OBJECT/UPLOAD_ID.complete.TEMP_NAME then renames to EXPORT_DIR/.minio/BUCKET/PATH/TO/OBJECT/UPLOAD_ID.complete 2. rename staging file EXPORT_DIR/.minio/BUCKET/PATH/TO/OBJECT/UPLOAD_ID.complete to EXPORT_DIR/BUCKET/PATH/TO/OBJECT
2016-03-28 12:52:09 -04:00
],
"rootPath": "github.com/minio/minio"
Migrate to new govendor
2015-10-11 01:28:56 -04:00
}
Reference in New Issue Copy Permalink