You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds/pull/1138
-- Commit Summary --
* Alphabetize modules
-- File Changes --
M apis/pom.xml (28)
M drivers/pom.xml (12)
M providers/pom.xml (60)
-- Patch Links --
https://github.com
GSoC has ended.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/405#issuecomment-327330685
Closed #405.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/405#event-1235868524
@neykov Do we have a path forward on this pull request?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-cli/pull/38#issuecomment-327331129
Closed #64.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/64#event-1235872581
Closed #1104.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1104#event-1237885337
@archupsg03 Do you plan to continue work on this pull request or should I close
it?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1105#issuecomment-327648825
Release notes:
https://github.com/google/auto/releases/tag/auto-value-1.5
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds/pull/1139
-- Commit Summary --
* Upgrade to AutoValue 1.5
-- File Changes --
M project/pom.xml (2)
-- Patch Lin
@nacx Please review.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1140#issuecomment-327718497
Found via error-prone.
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds/pull/1140
-- Commit Summary --
* Address BindingToUnqualifiedCommonType warnings
-- File Changes --
M apis/chef/src/main/java/org/jclouds/ohai/config/OhaiModule.jav
Closed #1139.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1139#event-1238290032
AutoValue 1.5 requires Java 8.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1139#issuecomment-327723140
This eliminates warnings of the form:
```
/home/gaul/.m2/repository/com/google/guava/guava/18.0/guava-18.0.jar(com/google/common/util/concurrent/Monitor.class):
warning: Cannot find annotation method 'value()' in type 'GuardedBy'
```
You can view, comment on, or merge this pull request online at:
rebuild please
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1140#issuecomment-327734271
CloudBees seems sick; these changes passed local tests.
--
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1137#issuecomment-327735425
andrewgaul approved this pull request.
Agree that we should remove the check -- eventually we will support V4 signer
for non-Amazon providers.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jcl
This is not meaningful since these classes cannot be instantiated.
Found via error-prone.
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds/pull/1143
-- Commit Summary --
* Remove Inject on constructors for abstract classes
-- File Changes --
Successfully tested against rackspace-cloudfiles-us and verified that this
commit reduces openstack-swift failures from:
```
Failed tests:
TemporaryUrlSignerLiveTest.signForPublicAccess:55 » IO Server returned HTTP
re...
ContainerApiLiveTest.testDeleteMetadata:178 » ContainerNotFound
Contai
These often fail in our continuous integration tests.
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds/pull/1145
-- Commit Summary --
* JCLOUDS-1340: Disable BackoffLimitedRetryHandlerTest
-- File Changes --
M
core/src/test/java/org/jc
I successfully ran `mvn test -pl core` 300 times with this commit. Previously
it would fail every 10-20 times.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1145#issuecomment-328709
@VRanga000 Do we have a path forward on this?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/740#issuecomment-328725174
Also switch from unmaintained easymockclassextension to easymock.
Release notes:
https://github.com/easymock/easymock/releases
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds/pull/1146
-- Commit Summary --
* Upgrade to EasyMock 3.5
-- File
I have started to implement the other providers; if you have feedback on the
approach I would appreciate it sooner rather than later.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/11
EasyMock 3.5 conflicts with testng subdependencies in a way that
duplicate-finder-maven-plugin detects. Upgrading to EasyMock 3.4 instead.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/p
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds/pull/1147
-- Commit Summary --
* JCLOUDS-1335: Upgrade to Azure Blob API 2017-04-17
* JCLOUDS-1335: Azure Blob object access tiers
-- File Changes --
M
providers/azureblob/src/main/ja
The new tests will fail until the tiering goes GA or if you opt into the
preview:
https://azure.microsoft.com/en-us/blog/announcing-the-public-preview-of-azure-archive-blob-storage-and-blob-level-tiering/
--
You are receiving this because you are subscribed to this thread.
Reply to this email d
I decline to share my Rackspace credentials which are linked to my credit card
with some random Internet person.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1105#issuecomment-33125
Sorry how do these issues relate to your problem?
Please do not make substantial edits to comments which are better addressed as
new comments. GitHub does not generate mails for these and it ruins the flow
of the discussion.
--
You are receiving this because you are subscribed to this thread.
Please just sign up for a Rackspace account which takes a few minutes. I have
spent hours reviewing code with you.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1105#issuecomment-33
@pimenas do we have a path forward on this pull request?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/433#issuecomment-331354779
@limorbortman do we have a path forward on this pull request?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/697#issuecomment-331354917
@vapgar200 do we have a path forward on this pull request?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/748#issuecomment-331354957
@yaronr do we have a path forward on this pull request?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/790#issuecomment-331354974
@olivergondza do we have a path forward on this pull request?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/863#issuecomment-331355000
@Xianguang-Zhou do we have a path forward on this pull request?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/886#issuecomment-331355022
@bostko do we have a path forward on this pull request?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/964#issuecomment-331355075
@olivierlemasle do we have a path forward on this pull request?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1009#issuecomment-331355104
Closed #130.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/130#event-1260632255
Closed due to inactivity.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/130#issuecomment-331355317
@marcuswanner do we have a path forward on this pull request?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/198#issuecomment-331355396
Closed due to inactivity.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/863#issuecomment-331355485
Closed #863.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/863#event-1260633235
Closed #198.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/198#event-1262100447
Closed due to inactivity.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/198#issuecomment-331580937
Closed #790.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/790#event-1262728330
Sorry code is incomplete without tests. Please reopen if you want to complete
this.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/790#issuecomment-331724074
@timuralp Do you have any insight into this issue? Otherwise we can close this
pull request.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1084#issuecomment-331726071
@stevegomez17 Please stop adding irrelevant comments to jclouds pull requests.
I have been deleting these.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1084#issuecomment-332682134
Closed #697.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/697#event-1270278027
Closed #1009.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1009#event-1270278806
Closed due to inactivity.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/697#issuecomment-332911390
Closed due to inactivity.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1009#issuecomment-332911517
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds/pull/1148
-- Commit Summary --
* JCLOUDS-1337: Portable storage tiers
* JCLOUDS-1337: Azure putBlob portable storage tiers
* JCLOUDS-1337: S3 putBlob portable storage tiers
* JCLOUDS-133
rebuild please
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1148#issuecomment-335918428
CloudBees seems to be consuming some kind of Java 8 artifact with a JVM prior
to 8:
```
Exception in thread "main" java.lang.UnsupportedClassVersionError:
hudson/remoting/Launcher : Unsupported major.minor version 52.0
```
--
You are receiving this because you are subscribed to this thread.
Re
I will add storage tier support for copyBlob in a separate pull request.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1148#issuecomment-335980294
@nacx I encountered similar CloudBees weirdness in jclouds/jclouds#1148 but
could not find a solution.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/414#issuecomment-336373671
Still need to make a decision on how providers without tiering support handle
calls with tiers. See jclouds-dev thread.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1148#issuecomme
@nacx Sorry I missed this earlier. I fixed the tiering regression in
5448b92ee8c9ba230df9ad8e0d89b070f5b869ae.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1149#issuecomment-338271
Closed #748.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/748#event-1303436258
Closed due to inactivity.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/748#issuecomment-338272496
> I'm merging this now to make the builds happy again, although a local build,
> with the blobstore changes in this PR reverted and rebased to the latest
> master version still presented some test failures. @gaul would you mind
> having a look at those?
Can you be more specific about these fail
I see the error on Jenkins -- I was not running the labs integration tests.
Fixed in jclouds/jclouds-labs@adb4087ab1c37bf8435b293778767e312d89e18b.
--
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/
@nacx You have described the problem exactly -- Java on Mac OS does not support
extended attributes. Could you add some test exclusions for tiers similar to
the ones we already have for other attributes?
--
You are receiving this because you modified the open/close state.
Reply to this email d
gaul requested changes on this pull request.
> @@ -89,6 +91,15 @@ protected void checkUserMetadata(Map
> userMetadata1, Maphttps://github.com/jclouds/jclouds/pull/1150#pullrequestreview-71327087
@nacx Agreed that this is inconsistent. I think it is better to throw
`SkipException` since this flags tests in an obvious way, although several
tests use `dataProvider` or conditional logic to avoid running some tests. If
you do change this, note that methods like `validateMetadata` are not t
These providers map all storage tiers to `STANDARD`.
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds/pull/1151
-- Commit Summary --
* JCLOUDS-1337: Atmos putBlob portable storage tiers
* JCLOUDS-1337: B2 putBlob portable storage tiers
*
gaul requested changes on this pull request.
> }
// Mac OS X HFS+ does not support UserDefinedFileAttributeView:
// https://bugs.openjdk.java.net/browse/JDK-8030048
@Override
protected void validateMetadata(BlobMetadata metadata) throws IOException {
- if (!isMacOSX())
gaul approved this pull request.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1150#pullrequestreview-71571973
gaul approved this pull request.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1152#pullrequestreview-71885965
> +1. [Known Issues](#issues)
> +1. [Reminder](#reminder)
> +1. [Credits](#credits)
> +1. [Test Results](#test)
> +
> +## Introduction
> +
> +You can read the official announcement at [Apache jclouds 1.7.3
> released](http://jclouds.markmail.org/message/6ormro7calbt5tjn). You can read
> the detai
> @@ -57,6 +57,7 @@
> data-toggle="dropdown">Release Notes
>
>
> +1.7.3
Broken link:
http://d044609f24846c5cc196-e981417fa0775ee8db370444a872f96e.r86.cf1.rackcdn.com/releasenotes/1.7.3/
---
Reply to thi
> @@ -138,20 +138,35 @@ public UriBuilder host(String host) {
>}
>
>public UriBuilder path(@Nullable String path) {
> + return path(path, true);
> + }
> +
> + public UriBuilder path(@Nullable String path, boolean urlDecode) {
Can we change `UriBuilder` to not en
This pull requests addresses several suggestions from @demobox in #4. Tested
locally and pushed to master.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-aws/pull/5#issuecomment-44710815
Closed #5.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-aws/pull/5#event-126645368
Clock skew refers to the perceived time difference between jclouds and the
blobstore. In most cases this arises due to NTP misconfiguration although the
needlessly tight timeouts can show spurious failures due to slow or lossy
network links, such as my home wireless connection.
---
Reply to th
@imesh jclouds master branch uses Guava 17.0 which makes ```Stopwatch```
constructors private access. The jclouds dependency supersedes your
application dependency on an older version of Guava. You should update your
application dependency to 17.0 and address the Guava API changes and
depreca
> Is there anything else that needs to be done here?
>
> There is one feature that I am developing in jclouds that is made easier
> because of this change. Let me know if there's anything I can do to help make
> progress on this.
I do not think `LocalAsyncBlobStore` is the appropriate place to
> @@ -128,10 +128,14 @@ private void generateGetTempURL() throws IOException {
>
>// GET the file using jclouds
>File file = File.createTempFile(FILENAME, ".tmp");
> - String content =
> Strings2.toString(blobStoreContext.utils().http().invoke(request).getPayload());
>
> + private final CloudFilesApi cloudFiles;
> +
> + /**
> +* To get a username and API key see
> http://jclouds.apache.org/guides/rackspace/
> +*
> +* The first argument (args[0]) must be your username
> +* The second argument (args[1]) must be your API key
> +*/
> + pub
I prefer allowing the server to validate inputs. While the client can give
more helpful error messages, having a single source of truth improves
maintainability.
Tested locally and pushed to master.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-
Closed #6.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-aws/pull/6#event-130009077
> @Inject(optional = true)
> @Named(Constants.PROPERTY_MAX_RETRIES)
> - private int retryCountLimit = 5;
> + static final int NUM_RETRIES = 5;
Should this be non-final since it is injectable?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pul
> @@ -60,6 +67,16 @@ protected RetryOnRenew(LoadingCache
> authenticationResponseCac
>this.backoffHandler = backoffHandler;
> }
>
> + /*
> +* The reason retries need to be tracked is that it is possible that a
> token
> +* * can be expired at any time. The reason we track
@zack-shoylev could you also look at this pull request?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/399#issuecomment-45683808
>@Override
>public PayloadBlobBuilder contentMD5(byte[] md5) {
> + return contentMD5(md5 == null ? null : HashCode.fromBytes(md5));
> + }
> +
> + @Override
> + public PayloadBlobBuilder contentMD5(HashCode md5) {
Added Nullable and allowing null for consisten
>
> + public ContentMetadataBuilder contentMD5(HashCode contentMD5) {
> + this.contentMD5 = contentMD5;
Added a conditional for null. I do believe we want to allow setting to null
although this is beyond the scope of this commit.
---
Reply to this email directly or view it on GitHub:
h
> @@ -83,7 +84,8 @@ public ContentMetadataBuilder expires(@Nullable Date
> expires) {
> }
>
> public ContentMetadata build() {
> - return new BaseImmutableContentMetadata(contentType, contentLength,
> contentMD5, contentDisposition,
> + return new BaseImmutableContentMetadata(
> @@ -41,7 +41,7 @@ public BaseImmutableContentMetadata(String contentType,
> Long contentLength, byte
> String contentDisposition, String contentLanguage, String
> contentEncoding, Date expires) {
>this.contentType = contentType;
>this.contentLength = contentLength;
Addressed Checkstyle violations.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/384#issuecomment-45697797
@rcoedo Sorry to reverse my opinion on this, but I created equivalent live
tests and do not believe the Glacier error messages are useful enough to remove
this functionality. The too long vault name delivers something readable but
the empty and invalid characters do not as shown by this gist:
Closed #384.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/384#event-130960566
Closed #8.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-aws/pull/8#event-131311274
Reworded commit message so that the summary is at most 50 characters as per
best practices:
https://wiki.openstack.org/wiki/GitCommitMessages#Summary_of_GIT_commit_message_structure
Ran integration tests locally and pushed to master.
---
Reply to this email directly or view it on GitHub:
https:
I prefer that all committers to use their apache.org email addresses since they
represent the project first and their employers second when working on jclouds.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/397#issuecomment-46055497
> + }
> +
> + //If there is one hash left, add it too.
> + if (q.size() == 1)
> + result.offer(q.poll());
> + return result;
> + }
> +
> + /**
> +* Build a TreeHash based on a map of hashed chunks.
> +*
> +* @return A String containing the calculated Tree
> + return q.poll().toString();
> + }
> +
> + /**
> +* Build the Hash and the TreeHash values of the payload.
> +*/
> + public void buildHashes() throws IOException {
> + InputStream is = payload.openStream();
> + Hasher hasher = Hashing.sha256().newHasher();
> + Q
> + Queue q = Lists.newLinkedList();
> +
> + //Divide the payload in chunks and queue them.
> + byte[] buffer = new byte[CHUNK_SIZE];
> + int bytesRead;
> + while ((bytesRead = is.read(buffer)) >= 0) {
> + q.offer(Hashing.sha256().hashBytes(buffer, 0, bytesRead));
>
> +
> + //Divide the payload in chunks and queue them.
> + byte[] buffer = new byte[CHUNK_SIZE];
> + int bytesRead;
> + while ((bytesRead = is.read(buffer)) >= 0) {
> + q.offer(Hashing.sha256().hashBytes(buffer, 0, bytesRead));
> + hasher.putBytes(buffer, 0, byte
> + }
> +
> + /**
> +* Build the Hash and the TreeHash values of the payload.
> +*/
> + public void buildHashes() throws IOException {
> + InputStream is = payload.openStream();
> + Hasher hasher = Hashing.sha256().newHasher();
> + Queue q = Lists.newLinkedList();
> +
>
801 - 900 of 4089 matches
Mail list logo
