You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* aws-creds: default to a 30-second request timeout
No (infinite) timeout is a bad default.
* aws-creds: return the previous timeout when overriding
The value is global, so it's not always possible to restore a previous
setting value, but it's better than nothing.
* Simplify instance detection
* Add ap-east-1 region (#235)
Co-authored-by: Juraj Sadel <juraj.sadel@espressif.com>
* Fix crates.io badge, update links and various formatting (#219)
* Make all fail-on-err variations run the same check (#233)
* Make attohttpc optional for credentials (#231)
* Make attohttpc optional for credentials
* Enabling tls implies enabling http
* Use async write for tokio,async-std (#230)
* Fix tokio async doctest
* Add support for the older ListObjects API (#229)
Google Cloud Storage doesn't support the newer ListObjectsV2 call.
* If file is smaller than one chunk, don't initiate multi-part upload (#228)
There already was a special case in put_object_stream() for a small files,
where the multi-part upload was aborted if the input turned out to be
small enough to fit in one chunk. But we can do better than that, and not
initiate the multi-part upload in the first place, avoiding two round
trips to S3 (one to initiate, and another to abort the multi-part upload).
While we're at it, refactor the loop slightly.
* Fix blocking tests
* Make minidom dependency optional (#226)
* Fix a typo
* Make minidom dependency optional
* Import futures-io crate directly instead of through futures (#227)
* Revert "Import futures-io crate directly instead of through futures (#227)"
This reverts commit 7b2e3a0.
* Stream is flaky with rustls-tls
* Implements #223
* s3/bucket: default to 30-second request timeout (#221)
No (infinite) timeout is a bad default.
* aws-creds 0.27.0
* aws-region 0.23.3
* Import futures-* crates directly instead of through futures (#237)
* 0.28.0
* No *s
Co-authored-by: Paul Khuong <pkhuong@backtrace.io>
Co-authored-by: Drazen Urch <durch@users.noreply.guthub.com>
Co-authored-by: JurajSadel <43887390+JurajSadel@users.noreply.github.com>
Co-authored-by: Juraj Sadel <juraj.sadel@espressif.com>
Co-authored-by: Alex Touchet <alextouchet@outlook.com>
Co-authored-by: Riley <asonix@asonix.dog>
Co-authored-by: Heikki Linnakangas <heikki.linnakangas@iki.fi>
Co-authored-by: Jonas Platte <jplatte@users.noreply.github.com>
Copy file name to clipboardexpand all lines: CONTRIBUTING.md
+12-12
Original file line number
Diff line number
Diff line change
@@ -6,11 +6,11 @@ We love your input! We want to make contributing to this project as easy and tra
6
6
- Submitting a fix
7
7
- Proposing new features
8
8
9
-
## We Develop with Github
10
-
We use github to host code, to track issues and feature requests, as well as accept pull requests.
9
+
## We Develop With GitHub
10
+
We use GitHub to host code, to track issues and feature requests, as well as accept pull requests.
11
11
12
-
## We Use [Github Flow](https://guides.github.com/introduction/flow/index.html), So All Code Changes Happen Through Pull Requests
13
-
Pull requests are the best way to propose changes to the codebase (we use [Github Flow](https://guides.github.com/introduction/flow/index.html)). We actively welcome your pull requests:
12
+
## We Use [GitHub Flow](https://guides.github.com/introduction/flow/index.html), So All Code Changes Happen Through Pull Requests
13
+
Pull requests are the best way to propose changes to the codebase (we use [GitHub flow](https://guides.github.com/introduction/flow/index.html)). We actively welcome your pull requests:
14
14
15
15
1. Fork the repo and create your branch from `master`.
16
16
2. If you've added code that should be tested, add tests.
@@ -19,20 +19,20 @@ Pull requests are the best way to propose changes to the codebase (we use [Githu
19
19
5. Make sure your code lints.
20
20
6. Issue that pull request!
21
21
22
-
## Any contributions you make will be under the MIT Software License
23
-
In short, when you submit code changes, your submissions are understood to be under the same [MIT License](http://choosealicense.com/licenses/mit/) that covers the project. Feel free to contact the maintainers if that's a concern.
22
+
## Any Contributions You Make Will Be Under the MIT Software License
23
+
In short, when you submit code changes, your submissions are understood to be under the same [MIT License](https://choosealicense.com/licenses/mit/) that covers the project. Feel free to contact the maintainers if that's a concern.
24
24
25
-
## Report bugs using Github's [issues](https://github.com/briandk/transcriptase-atom/issues)
26
-
We use GitHub issues to track public bugs. Report a bug by [opening a new issue](); it's that easy!
25
+
## Report Bugs Using GitHub's [Issues](https://github.com/durch/rust-s3/issues)
26
+
We use GitHub issues to track public bugs. Report a bug by [opening a new issue](https://github.com/durch/rust-s3/issues/new); it's that easy!
27
27
28
-
## Write bug reports with detail, background, and sample code
28
+
## Write Bug Reports With Detail, Background, and Sample Code
29
29
30
-
**Great Bug Reports** tend to have:
30
+
**Great bug reports** tend to have:
31
31
32
32
- A quick summary and/or background
33
33
- Steps to reproduce
34
34
- Be specific!
35
-
- Give sample code if you can.
35
+
- Give sample code if you can
36
36
- What you expected would happen
37
37
- What actually happens
38
38
- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
@@ -47,4 +47,4 @@ People *love* thorough bug reports. I'm not even kidding.
47
47
By contributing, you agree that your contributions will be licensed under its MIT License.
48
48
49
49
## References
50
-
This document was adapted from the open-source contribution guidelines for [Facebook's Draft](https://github.com/facebook/draft-js/blob/a9316a723f9e918afde44dea68b5f9f39b7d9b00/CONTRIBUTING.md)
50
+
This document was adapted from the open-source contribution guidelines for [Facebook's Draft](https://github.com/facebook/draft-js/blob/master/CONTRIBUTING.md)
<!-- [](https://gitter.im/durch/rust-s3?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge) -->
@@ -10,15 +10,15 @@ Rust library for working with Amazon S3 or arbitrary S3 compatible APIs, fully c
10
10
11
11
### Support further development
12
12
13
-
+ BTC - `3QQdtQGSMStTWEBhe65hPiAWJekXH8n26o`
14
-
+ ETH - `0x369Fd06ACc25CCfE0A28BE40018cF3aC38AcdcB6`
13
+
+ BTC - `3NtVvyhMQepmcaVmCJURUB54wLBaZzfjci`
14
+
+ ETH - `0xfd2643D1A15787D41e61de2620D351Fd232936Af`
15
15
16
16
### Intro
17
17
18
18
Modest interface towards Amazon S3, as well as S3 compatible object storage APIs such as Wasabi, Yandex, Minio or Google Cloud Storage.
19
19
Supports: `put`, `get`, `list`, `delete`, operations on `tags` and `location`, well as `head`.
20
20
21
-
Additionally a dedicated `presign_get``Bucket` method is available. This means you can upload to s3, and give the link to select people without having to worry about publicly accessible files on S3. This also means that you can give people
21
+
Additionally a dedicated `presign_get``Bucket` method is available. This means you can upload to S3, and give the link to select people without having to worry about publicly accessible files on S3. This also means that you can give people
22
22
a `PUT` presigned URL, meaning they can upload to a specific key in S3 for the duration of the presigned URL.
23
23
24
24
**[AWS, Yandex and Custom (Minio) Example](https://github.com/durch/rust-s3/blob/master/s3/bin/simple_crud.rs)**
@@ -33,28 +33,29 @@ There are a lot of various featuers that enable a wide variaty of use cases, ref
33
33
+`no-verify-ssl` - disable SSL verification for endpoints, useful for custom regions
34
34
+`never-encode-slash` - never encode slashes in paths
35
35
36
-
##### with`default-features = false`
36
+
##### With`default-features = false`
37
37
38
38
+`with-async-std` - `async-std` runtime
39
-
+`sync` - no async rutime, `attohttpc` is used for HTTP requests
39
+
+`sync` - no async runtime, `attohttpc` is used for HTTP requests
40
+
+`tags` - required for `Bucket::get_object_tagging`
40
41
41
-
All runtimes support either `native-tls` or `rustls-tls`, there are features for all combinations, refer to `s3/Cargo.toml` for a complete list
42
+
All runtimes support either `native-tls` or `rustls-tls`, there are features for all combinations, refer to `s3/Cargo.toml` for a complete list.
42
43
43
44
#### Path or subdomain style URLs and headers
44
45
45
46
`Bucket` struct provides constructors for `path-style` paths, `subdomain` style is the default. `Bucket` exposes methods for configuring and accessing `path-style` configuration. `blocking` feature will generate a `*_blocking` variant of all of the methods listed below.
Each `GET` method has a `PUT` companion `sync` and `async` methods are generic over `std::io::Read`. `async``stream` methods are generic over `futures::io::AsyncReadExt`, while `tokio` methods are generic over `tokio::io::AsyncReadExt`.
74
+
Each `GET` method has a `PUT` companion `sync` and `async` methods are generic over `std::io::Read`. `async``stream` methods are generic over `futures_io::AsyncReadExt`, while `tokio` methods are generic over `tokio::io::AsyncReadExt`.
0 commit comments