oyd
/
minio
6
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
3790 Commits
1 Branch
0 Tags
89 MiB
Tag: Branch: Tree: dd68cdd802
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'dd68cdd802'
${ noResults }
minio/vendor/vendor.json

312 lines
9.9 KiB
Raw Normal View History Unescape

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.
9 years ago
{
"comment": "",
vendorize deps for snappy, blake2b and sha256 (#3476) Bring in new optimization and portability changes. Fixes https://github.com/minio/minio-go/issues/578
8 years ago
"ignore": "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.
9 years ago
"package": [
logrus logger
9 years ago
{
Migrate to new govendor
9 years ago
"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
9 years ago
"revision": "32055c351ea8b00b96d70f28db48d9840feaf0ec",
"revisionTime": "2016-07-12T20:17:32-04:00"
logrus logger
9 years ago
},
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
9 years ago
{
"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
9 years ago
"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
9 years ago
},
Add support for Kafka as a notifications target (#2869) (#3439)
8 years ago
{
"checksumSHA1": "/5cvgU+J4l7EhMXTK76KaCAfOuU=",
"path": "github.com/davecgh/go-spew/spew",
"revision": "346938d642f2ec3594ed81d874461961cd0faa76",
"revisionTime": "2016-10-29T20:57:26Z"
},
jwt: Add JWT support for minio server. Please read JWT.md before using this feature.
9 years ago
{
"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
9 years ago
"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.
9 years ago
},
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.
9 years ago
{
Migrate to new govendor
9 years ago
"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
9 years ago
"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.
9 years ago
},
Add support for Kafka as a notifications target (#2869) (#3439)
8 years ago
{
"checksumSHA1": "y2Kh4iPlgCPXSGTCcFpzePYdzzg=",
"path": "github.com/eapache/go-resiliency/breaker",
"revision": "b86b1ec0dd4209a588dc1285cdd471e73525c0b3",
"revisionTime": "2016-01-04T19:15:39Z"
},
{
"checksumSHA1": "WHl96RVZlOOdF4Lb1OOadMpw8ls=",
"path": "github.com/eapache/go-xerial-snappy",
"revision": "bb955e01b9346ac19dc29eb16586c90ded99a98c",
"revisionTime": "2016-06-09T14:24:08Z"
},
{
"checksumSHA1": "oCCs6kDanizatplM5e/hX76busE=",
"path": "github.com/eapache/queue",
"revision": "44cc805cf13205b55f69e14bcb69867d1ae92f98",
"revisionTime": "2016-08-05T00:47:13Z"
},
UI: vendorize github.com/elazarl/go-bindata-assetfs which is needed by ui-assets.go
9 years ago
{
"path": "github.com/elazarl/go-bindata-assetfs",
ui-assets: Integrate UI assets.
9 years ago
"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
9 years ago
},
Add WebUI assetfs initial version
9 years ago
{
Migrate this project to minio micro services code
9 years ago
"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
9 years ago
"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.
9 years ago
},
Add support for Kafka as a notifications target (#2869) (#3439)
8 years ago
{
vendorize deps for snappy, blake2b and sha256 (#3476) Bring in new optimization and portability changes. Fixes https://github.com/minio/minio-go/issues/578
8 years ago
"checksumSHA1": "W+E/2xXcE1GmJ0Qb784ald0Fn6I=",
Add support for Kafka as a notifications target (#2869) (#3439)
8 years ago
"path": "github.com/golang/snappy",
"revision": "d9eb7a3d35ec988b8585d4a0068e462c27d28380",
"revisionTime": "2016-05-29T05:00:41Z"
},
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.
9 years ago
{
Migrate this project to minio micro services code
9 years ago
"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
9 years ago
"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.
9 years ago
},
browser-assets: serve asset files with compression.
9 years ago
{
"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
9 years ago
"revision": "66e6c6f01d8da976ee113437745ca029c2b585a6",
"revisionTime": "2016-04-10T11:53:17-07:00"
browser-assets: serve asset files with compression.
9 years ago
},
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.
9 years ago
{
Migrate this project to minio micro services code
9 years ago
"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
9 years ago
"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.
9 years ago
},
Bring in the list APIs implemented by Bala <bala@minio.io>
9 years ago
{
"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
9 years ago
"revision": "bd3317b8f6704b1b40e4e705ec9e987a535cd5d3",
"revisionTime": "2016-05-16T23:23:31-07:00"
Bring in the list APIs implemented by Bala <bala@minio.io>
9 years ago
},
{
WebUI: move from rpc/v2/json to rpc/v2/json2 which has better error response structure.
9 years ago
"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
9 years ago
"revision": "bd3317b8f6704b1b40e4e705ec9e987a535cd5d3",
"revisionTime": "2016-05-16T23:23:31-07:00"
Bring in the list APIs implemented by Bala <bala@minio.io>
9 years ago
},
rewrite minio runtime checks
9 years ago
{
"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
9 years ago
{
"path": "github.com/klauspost/cpuid",
"revision": "349c675778172472f5e8f3a3e0fe187e302e5a10",
"revisionTime": "2016-01-06T11:44:51+01:00"
},
Add support for Kafka as a notifications target (#2869) (#3439)
8 years ago
{
"checksumSHA1": "BM6ZlNJmtKy3GBoWwg2X55gnZ4A=",
"path": "github.com/klauspost/crc32",
"revision": "cb6bfca970f6908083f26f39a79009d608efd5cd",
"revisionTime": "2016-10-16T15:41:25Z"
},
Implement XL layer - preliminary work.
9 years ago
{
vendorize deps for snappy, blake2b and sha256 (#3476) Bring in new optimization and portability changes. Fixes https://github.com/minio/minio-go/issues/578
8 years ago
"checksumSHA1": "Pzd1bfm8Yj1radncaohNZu+UT1I=",
Implement XL layer - preliminary work.
9 years ago
"path": "github.com/klauspost/reedsolomon",
vendorize deps for snappy, blake2b and sha256 (#3476) Bring in new optimization and portability changes. Fixes https://github.com/minio/minio-go/issues/578
8 years ago
"revision": "d0a56f72c0d40a6cdde43a1575ad9686a0098b70",
"revisionTime": "2016-10-28T07:13:20Z"
Implement XL layer - preliminary work.
9 years ago
},
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.
8 years ago
{
"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.
9 years ago
{
"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
9 years ago
"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.
9 years ago
},
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
9 years ago
{
Migrate this project to minio micro services code
9 years ago
"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
9 years ago
"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
9 years ago
},
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
9 years ago
{
vendorize deps for snappy, blake2b and sha256 (#3476) Bring in new optimization and portability changes. Fixes https://github.com/minio/minio-go/issues/578
8 years ago
"checksumSHA1": "IgPoMBktWdCLuyzDBfzi34sT+jg=",
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
9 years ago
"path": "github.com/minio/blake2b-simd",
vendorize deps for snappy, blake2b and sha256 (#3476) Bring in new optimization and portability changes. Fixes https://github.com/minio/minio-go/issues/578
8 years ago
"revision": "c50cace0dc7d72a80244a5f88ddd3e08a73db8de",
"revisionTime": "2016-07-22T09:38:12Z"
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
9 years ago
},
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.
9 years ago
{
Migrate this project to minio micro services code
9 years ago
"path": "github.com/minio/cli",
cli: vendorize to new CLI package updates. - Fix a new line issue for minioHelpTemplate. - Fixes #974
9 years ago
"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.
9 years ago
},
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
8 years ago
{
Vendorize recent fixes in dsync (#3365) * Update 'i' only if lock grant read from buffered channel
8 years ago
"checksumSHA1": "ddMyebkzU3xB7K8dAhM1S+Mflmo=",
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
8 years ago
"path": "github.com/minio/dsync",
Vendorize recent fixes in dsync (#3365) * Update 'i' only if lock grant read from buffered channel
8 years ago
"revision": "dd0da3743e6668b03559c2905cc661bc0fceeae3",
"revisionTime": "2016-11-28T22:07:34Z"
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
8 years ago
},
rewrite minio runtime checks
9 years ago
{
"path": "github.com/minio/go-homedir",
vendor update for go-homedir
9 years ago
"revision": "0b1069c753c94b3633cc06a1995252dbcc27c7a6",
"revisionTime": "2016-02-15T17:25:11+05:30"
rewrite minio runtime checks
9 years ago
},
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.
9 years ago
{
"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
8 years ago
{
web: add method to get all policies for given bucket name. (#2756) Refer #1858
8 years ago
"checksumSHA1": "qTxOBp3GVxCC70ykb7Hxg6UgWwA=",
web: add handlers for set/get bucket policy. (#2486) Refer #1858
8 years ago
"path": "github.com/minio/minio-go/pkg/policy",
web: add method to get all policies for given bucket name. (#2756) Refer #1858
8 years ago
"revision": "40505f5d08c721dfe5a6450fbdef3bcd6567aa97",
"revisionTime": "2016-09-04T08:12:15Z"
web: add handlers for set/get bucket policy. (#2486) Refer #1858
8 years ago
},
admin: Fix wrong vendorized location for s3signer and s3utils.
8 years ago
{
"checksumSHA1": "l95EyvF0yFAItXsXYqsZ6g7yGy4=",
"path": "github.com/minio/minio-go/pkg/s3signer",
"revision": "d02caa62b9e1034f93a82d41da806651a666c5a3",
"revisionTime": "2016-12-14T00:10:05Z"
},
{
"checksumSHA1": "bPvxFS1qu6W9lOqdt8aEfS5Sids=",
"path": "github.com/minio/minio-go/pkg/s3utils",
"revision": "532b920ff28900244a2ef7d07468003df36fe7c5",
"revisionTime": "2016-12-20T20:43:13Z"
},
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
8 years ago
{
"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.
9 years ago
{
Vendorize with bug fixes from minio browser. (#3341) This patch brings in changes from miniobrowser repo. - Bucket policy UI and functionality fixes by @krishnasrinivas - Bucket policy implementation by @balamurugana - UI changes and new functionality changing password etc. @rushenn - UI and new functionality for sharing URLs, deleting files @rushenn and @krishnasrinivas. - Other misc fixes by @vadmeste @brendanashworth
8 years ago
"checksumSHA1": "Npl9R1pdTKB5LDiGh/hls8nMNQc=",
web: Removing dependency for gpg and downloading assets. Assets are vendorized from now on and updated for each release.
9 years ago
"path": "github.com/minio/miniobrowser",
Vendorize with bug fixes from minio browser. (#3341) This patch brings in changes from miniobrowser repo. - Bucket policy UI and functionality fixes by @krishnasrinivas - Bucket policy implementation by @balamurugana - UI changes and new functionality changing password etc. @rushenn - UI and new functionality for sharing URLs, deleting files @rushenn and @krishnasrinivas. - Other misc fixes by @vadmeste @brendanashworth
8 years ago
"revision": "d9214007ee7c5404358031c3e5af7df69300f874",
"revisionTime": "2016-11-24T00:39:49Z"
web: Removing dependency for gpg and downloading assets. Assets are vendorized from now on and updated for each release.
9 years ago
},
rewrite minio runtime checks
9 years ago
{
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
9 years ago
"checksumSHA1": "GOSe2XEQI4AYwrMoLZu8vtmzkJM=",
"path": "github.com/minio/redigo/redis",
"revision": "5e2117cd32d677a36dcd8c9c83776a065555653b",
"revisionTime": "2016-07-24T00:05:56Z"
rewrite minio runtime checks
9 years ago
},
Switched to faster minio/sha256-simd implementation (#2320)
8 years ago
{
vendorize deps for snappy, blake2b and sha256 (#3476) Bring in new optimization and portability changes. Fixes https://github.com/minio/minio-go/issues/578
8 years ago
"checksumSHA1": "URVle4qtadmW9w9BulDRHY3kxnA=",
Switched to faster minio/sha256-simd implementation (#2320)
8 years ago
"path": "github.com/minio/sha256-simd",
vendorize deps for snappy, blake2b and sha256 (#3476) Bring in new optimization and portability changes. Fixes https://github.com/minio/minio-go/issues/578
8 years ago
"revision": "e82e73b775766b9011503e80e6772fc32b9afc5b",
"revisionTime": "2016-12-19T23:17:30Z"
Switched to faster minio/sha256-simd implementation (#2320)
8 years ago
},
Add NATS notifier (#2795)
8 years ago
{
"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)
9 years ago
{
"path": "github.com/pkg/profile",
vendor changes to pkg/profile (#1671)
9 years ago
"revision": "c78aac22bd43883fd2817833b982153dcac17b3b",
"revisionTime": "2016-05-18T16:56:57+10:00"
server: Enable server profiling as needed. (#1565)
9 years ago
},
Enable controller to have CORS
9 years ago
{
Migrate to new govendor
9 years ago
"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
9 years ago
"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
9 years ago
},
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
9 years ago
{
"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
9 years ago
{
"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.
8 years ago
{
"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.
9 years ago
{
"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
9 years ago
{
"path": "golang.org/x/net/context",
"revision": "a728288923b47049b2ce791836767ffbe964a5bd",
"revisionTime": "2016-07-07T15:24:52-07:00"
},
Add support for Kafka as a notifications target (#2869) (#3439)
8 years ago
{
"checksumSHA1": "p36nkSZUaOs/7Wtcy/FduBLgm8g=",
"path": "gopkg.in/Shopify/sarama.v1",
"revision": "bd61cae2be85fa6ff40eb23dcdd24567967ac2ae",
"revisionTime": "2016-08-30T13:25:53Z"
},
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.
9 years ago
{
Migrate to new govendor
9 years ago
"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.
9 years ago
"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
9 years ago
},
{
"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.
9 years ago
}
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
9 years ago
],
"rootPath": "github.com/minio/minio"
Migrate to new govendor
9 years ago
}