xavierb-amadeus commented on issue #59: Fix BlobMetadata null size when using
ApacheHCHttp module
URL: https://github.com/apache/jclouds/pull/59#issuecomment-575190881
this is a followup of this earlier pull request
https://github.com/apache/jclouds/pull/48, unfortunately it was
xavierb-amadeus commented on issue #58: Fix BlobMetadata null size when using
ApacheHCHttpCommandExecutorServ…
URL: https://github.com/apache/jclouds/pull/58#issuecomment-575187789
replaced by https://github.com/apache/jclouds/pull/59
xavierb-amadeus opened a new pull request #59: Fix BlobMetadata null size when
using ApacheHCHttp module
URL: https://github.com/apache/jclouds/pull/59
JClouds is apparently exclusively using the Payload object from the HTTP
response to fill in the size of the BlobMetadata (when calling
xavierb-amadeus closed pull request #58: Fix BlobMetadata null size when using
ApacheHCHttpCommandExecutorServ…
URL: https://github.com/apache/jclouds/pull/58
This is an automated message from the Apache Git Service.
To
xavierb-amadeus opened a new pull request #58: Fix BlobMetadata null size when
using ApacheHCHttpCommandExecutorServ…
URL: https://github.com/apache/jclouds/pull/58
…iceModule
JClouds is apparently exclusively using the Payload object from the HTTP
response to fill in the size of
roded commented on a change in pull request #64: JCLOUDS-1520 - Reuse
SSLSocketFactory in JavaUrlHttpCommandExecutorSe…
URL: https://github.com/apache/jclouds/pull/64#discussion_r390828189
##
File path:
roded commented on a change in pull request #64: JCLOUDS-1520 - Reuse
SSLSocketFactory in JavaUrlHttpCommandExecutorSe…
URL: https://github.com/apache/jclouds/pull/64#discussion_r390828189
##
File path:
nacx commented on a change in pull request #64: JCLOUDS-1520 - Reuse
SSLSocketFactory in JavaUrlHttpCommandExecutorSe…
URL: https://github.com/apache/jclouds/pull/64#discussion_r390260781
##
File path:
nacx commented on a change in pull request #64: JCLOUDS-1520 - Reuse
SSLSocketFactory in JavaUrlHttpCommandExecutorSe…
URL: https://github.com/apache/jclouds/pull/64#discussion_r390259790
##
File path:
gaul merged pull request #59: Fix BlobMetadata null size when using
ApacheHCHttp module
URL: https://github.com/apache/jclouds/pull/59
This is an automated message from the Apache Git Service.
To respond to the message,
gaul commented on issue #59: Fix BlobMetadata null size when using ApacheHCHttp
module
URL: https://github.com/apache/jclouds/pull/59#issuecomment-596204854
Pushed to 2.2.x as 94f02856b7a9c891e63c2e7296d6ce00c70a43a3. Thank you for
your contribution @xavierb-amadeus!
roded opened a new pull request #64: JCLOUDS-1520 - Reuse SSLSocketFactory in
JavaUrlHttpCommandExecutorSe…
URL: https://github.com/apache/jclouds/pull/64
…rvice
This is an automated message from the Apache Git Service.
To
roded commented on issue #64: JCLOUDS-1520 - Reuse SSLSocketFactory in
JavaUrlHttpCommandExecutorSe…
URL: https://github.com/apache/jclouds/pull/64#issuecomment-596584621
Comments welcome. Thanks.
This is an automated
felfert edited a comment on issue #67: Fix javadoc generation on JDK >= 8
URL: https://github.com/apache/jclouds/pull/67#issuecomment-614765276
Well, on a clean VM with JDK7
(java-1.7.0-openjdk-devel-1.7.0.251-2.6.21.0.el7_7.x86_64)
everything builds fine here. Since I don't have access
felfert commented on issue #67: Fix javadoc generation on JDK >= 8
URL: https://github.com/apache/jclouds/pull/67#issuecomment-614765276
Well, on a clean VM with JDK7
(java-1.7.0-openjdk-devel-1.7.0.251-2.6.21.0.el7_7.x86_64)
everything builds fine here. Since I don't have access to
gaul commented on issue #67: Fix javadoc generation on JDK >= 8
URL: https://github.com/apache/jclouds/pull/67#issuecomment-614639814
Pushed to 2.2.x as 876269427b80d1d4a68403e0e729342d340fbd82.
This is an automated message
felfert commented on issue #67: Fix javadoc generation on JDK >= 8
URL: https://github.com/apache/jclouds/pull/67#issuecomment-614680665
Thats strange. I **did** create a profile "disable-doclint" which should get
activated by jdk8 only.
Even stranger, in travis.yml it says:
```
gaul commented on issue #67: Fix javadoc generation on JDK >= 8
URL: https://github.com/apache/jclouds/pull/67#issuecomment-614641945
@felfert @nacx Oops I missed that this broke master:
https://builds.apache.org/job/jclouds/101/console
It appears that we build with Java 7 and
felfert opened a new pull request #69: Enable docs in travis build
URL: https://github.com/apache/jclouds/pull/69
This PR enables doc and src profiles on travis
This is an automated message from the Apache Git Service.
To
roded opened a new pull request #70:
URL: https://github.com/apache/jclouds/pull/70
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
roded commented on a change in pull request #64:
URL: https://github.com/apache/jclouds/pull/64#discussion_r411465044
##
File path:
core/src/main/java/org/jclouds/http/internal/JavaUrlHttpCommandExecutorService.java
##
@@ -202,19 +206,38 @@ protected HttpURLConnection
roded commented on issue #64:
URL: https://github.com/apache/jclouds/pull/64#issuecomment-616624417
I've pushed an update as per the discussion above. It's still not tested
though - I'll update once it is.
This is an
gaul commented on issue #66: JCLOUDS-1543: change FetchBlobMetadata to retain
original blob order
URL: https://github.com/apache/jclouds/pull/66#issuecomment-615169792
Also pushed to master as 5ac92111c4e9347c492a16ecd402acafdb1f9cd7. Thank
you for your contribution @roded!
nacx merged pull request #69: Enable docs in travis build
URL: https://github.com/apache/jclouds/pull/69
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
gaul merged pull request #66: JCLOUDS-1543: change FetchBlobMetadata to retain
original blob order
URL: https://github.com/apache/jclouds/pull/66
This is an automated message from the Apache Git Service.
To respond to the
felfert opened a new pull request #67: Fix javadoc generation on JDK >= 8
URL: https://github.com/apache/jclouds/pull/67
This fixes javadoc generation with JDK >= 8 so that someone with
write-permission to the jclouds.apache.org site can fix apache/jclouds-site#12
Note: This also
felfert commented on issue #67: Fix javadoc generation on JDK >= 8
URL: https://github.com/apache/jclouds/pull/67#issuecomment-614483466
Another note:
Obviously, this currently does not get validated in travis. I could add a
modification to travis.yml, but I'm not shure if that is
felfert commented on issue #67: Fix javadoc generation on JDK >= 8
URL: https://github.com/apache/jclouds/pull/67#issuecomment-615109912
@nacx , @gaul
See #68
This is an automated message from the Apache Git Service.
To
nacx merged pull request #67: Fix javadoc generation on JDK >= 8
URL: https://github.com/apache/jclouds/pull/67
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
nacx closed issue #12: When is Javadoc 2.2.x coming live?
URL: https://github.com/apache/jclouds-site/issues/12
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub
nacx commented on issue #67: Fix javadoc generation on JDK >= 8
URL: https://github.com/apache/jclouds/pull/67#issuecomment-614592386
>Obviously, this currently does not get validated in travis. I could add a
modification to travis.yml, but I'm not shure if that is desired. IMHO, it is
ikky888 opened a new pull request #65: JCLOUDS-1541: Add Middle East (Bahrain)
region to the AWS EC2 and S3 providers list
URL: https://github.com/apache/jclouds/pull/65
This change request is to add the Middle East (Bahrain) region to the AWS
EC2 and S3 providers list.
I was able
gaul merged pull request #65: JCLOUDS-1541: Add Middle East (Bahrain) region to
the AWS EC2 and S3 providers list
URL: https://github.com/apache/jclouds/pull/65
This is an automated message from the Apache Git Service.
To
gaul commented on issue #65: JCLOUDS-1541: Add Middle East (Bahrain) region to
the AWS EC2 and S3 providers list
URL: https://github.com/apache/jclouds/pull/65#issuecomment-608953218
Also pushed to 2.2.x as f8768003708d78fcb599373523599f2bed63cf27. Thank you
for your contribution
ikky888 opened a new issue #12: When is Javadoc 2.2.x coming live?
URL: https://github.com/apache/jclouds-site/issues/12
Hi,
When is the Javadoc for version 2.2.x coming live?
The latest one published here is 2.1.x:
URL: https://jclouds.apache.org/reference/javadoc/
nacx commented on issue #68:
URL: https://github.com/apache/jclouds/pull/68#issuecomment-617616221
Thanks for the path. And I agree with your opinion. Unfortunately, we have
limited access to what we can configure in Jenkins and those toolchains are one
of those things we don't have
nacx commented on a change in pull request #64:
URL: https://github.com/apache/jclouds/pull/64#discussion_r412727800
##
File path: core/src/main/java/org/jclouds/http/config/SSLModule.java
##
@@ -43,8 +44,8 @@
@Override
protected void configure() {
roded commented on issue #64:
URL: https://github.com/apache/jclouds/pull/64#issuecomment-617347524
Tested to be working on OpenJDK 8 and OpenJ9 8.
Affected modules' test suites pass OK.
This is an automated message from
roded commented on a change in pull request #64:
URL: https://github.com/apache/jclouds/pull/64#discussion_r412901632
##
File path: core/src/main/java/org/jclouds/http/config/SSLModule.java
##
@@ -43,8 +44,8 @@
@Override
protected void configure() {
felfert commented on issue #68:
URL: https://github.com/apache/jclouds/pull/68#issuecomment-618223483
> If you would like to fix our Jenkins configurations, let me know and we'll
happily help you do that. Thanks!
I'd like to help fixing the jenkins setup. I'll contact you via email.
felfert edited a comment on issue #68:
URL: https://github.com/apache/jclouds/pull/68#issuecomment-618223483
> If you would like to fix our Jenkins configurations, let me know and we'll
happily help you do that. Thanks!
I'd like to help fixing the jenkins setup. I'll contact you via
gaul commented on pull request #71:
URL: https://github.com/apache/jclouds/pull/71#issuecomment-621933539
@nacx I tried untangling the 1024-bit SSL certificate error and went down
this OkHttp upgrade rabbit hole. This looks promising but I encountered a
strange error:
```
nacx commented on pull request #71:
URL: https://github.com/apache/jclouds/pull/71#issuecomment-621937550
Hmmm... I've never seen that one, but it looks indeed like a version
incompatibility with BC?
This is an automated
gaul opened a new pull request #71:
URL: https://github.com/apache/jclouds/pull/71
This allows creating an SSL certificate with 2048-bit RSA which
enables newer Java versions to run integration tests. Tweak okhttp
tests which do not allow zero-length requests without bodies.
gaul opened a new pull request #72:
URL: https://github.com/apache/jclouds/pull/72
Also change portable abstraction mapping for `Tier.ARCHIVE`.
This is an automated message from the Apache Git Service.
To respond to the
YYTVicky commented on pull request #63:
URL: https://github.com/apache/jclouds/pull/63#issuecomment-621557305
Hi,
We found the TLS is not secure for building connection
(https://www.packetlabs.net/tls-1-1-no-longer-secure/), would you mind changing
it to TLSv1.3 for security concern?
roded opened a new pull request #66: JCLOUDS-1543: change FetchBlobMetadata to
retain original blob order
URL: https://github.com/apache/jclouds/pull/66
This is an automated message from the Apache Git Service.
To respond
roded commented on pull request #64:
URL: https://github.com/apache/jclouds/pull/64#issuecomment-625057903
I've pushed another attempt at this which handles the issue only for the
untrusted use case.
JavaUrlHttpCommandExecutorService now keeps its existing optional (trusted)
Supplier
roded edited a comment on pull request #64:
URL: https://github.com/apache/jclouds/pull/64#issuecomment-625057903
I've pushed another attempt at this which handles the issue only for the
untrusted use case.
`JavaUrlHttpCommandExecutorService` now keeps its existing optional
(trusted)
gaul commented on pull request #13:
URL: https://github.com/apache/jclouds-site/pull/13#issuecomment-628327090
Thanks for the pointer! Unfortunately it seems that my desktop is too new:
```
OCI runtime create failed: this version of runc doesn't work on cgroups v2:
unknown
nacx commented on pull request #13:
URL: https://github.com/apache/jclouds-site/pull/13#issuecomment-628570723
Published!
We'll have to update it with proper links once the announcement emails are
out.
This is an
nacx edited a comment on pull request #13:
URL: https://github.com/apache/jclouds-site/pull/13#issuecomment-628570723
Published!
~~We'll have to update it with proper links once the announcement emails are
out.~~
This is
demobox opened a new pull request #14:
URL: https://github.com/apache/jclouds-site/pull/14
Using the date of the [ANNOUNCE] email. Follow-up to 713d87d
This is an automated message from the Apache Git Service.
To respond to
demobox merged pull request #14:
URL: https://github.com/apache/jclouds-site/pull/14
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go
demobox commented on pull request #14:
URL: https://github.com/apache/jclouds-site/pull/14#issuecomment-628655299
Thanks for taking a look, @gaul!
This is an automated message from the Apache Git Service.
To respond to the
gaul commented on pull request #13:
URL: https://github.com/apache/jclouds-site/pull/13#issuecomment-628596517
Updated the short links. Thanks @nacx you saved me a reboot. :)
This is an automated message from the Apache
nacx commented on a change in pull request #64: JCLOUDS-1520 - Reuse
SSLSocketFactory in JavaUrlHttpCommandExecutorSe…
URL: https://github.com/apache/jclouds/pull/64#discussion_r393162561
##
File path:
roded commented on a change in pull request #64: JCLOUDS-1520 - Reuse
SSLSocketFactory in JavaUrlHttpCommandExecutorSe…
URL: https://github.com/apache/jclouds/pull/64#discussion_r393551321
##
File path:
roded commented on a change in pull request #64: JCLOUDS-1520 - Reuse
SSLSocketFactory in JavaUrlHttpCommandExecutorSe…
URL: https://github.com/apache/jclouds/pull/64#discussion_r393551321
##
File path:
roded commented on a change in pull request #64: JCLOUDS-1520 - Reuse
SSLSocketFactory in JavaUrlHttpCommandExecutorSe…
URL: https://github.com/apache/jclouds/pull/64#discussion_r393551321
##
File path:
gaul opened a new pull request #13:
URL: https://github.com/apache/jclouds-site/pull/13
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to
gaul opened a new pull request #73:
URL: https://github.com/apache/jclouds/pull/73
Previously this provider worked around a RestAnnotationProcessor quirk
by using multi-part uploads for InputStream payloads. Instead work
around the quirk another way which allows a single-part upload.
gaul commented on a change in pull request #73:
URL: https://github.com/apache/jclouds/pull/73#discussion_r429513609
##
File path:
providers/google-cloud-storage/src/main/java/org/jclouds/googlecloudstorage/binders/MultipartUploadBinder.java
##
@@ -57,6 +57,7 @@
Part
cstamas opened a new pull request #82:
URL: https://github.com/apache/jclouds/pull/82
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go
nacx commented on a change in pull request #82:
URL: https://github.com/apache/jclouds/pull/82#discussion_r487221374
##
File path: apis/sts/src/test/java/org/jclouds/aws/util/AWSUtilsTest.java
##
@@ -88,6 +95,20 @@ public void testNoExceptionParsingTextPlain() {
nacx commented on a change in pull request #82:
URL: https://github.com/apache/jclouds/pull/82#discussion_r487221374
##
File path: apis/sts/src/test/java/org/jclouds/aws/util/AWSUtilsTest.java
##
@@ -88,6 +95,20 @@ public void testNoExceptionParsingTextPlain() {
nacx commented on a change in pull request #82:
URL: https://github.com/apache/jclouds/pull/82#discussion_r487221374
##
File path: apis/sts/src/test/java/org/jclouds/aws/util/AWSUtilsTest.java
##
@@ -88,6 +95,20 @@ public void testNoExceptionParsingTextPlain() {
nacx commented on a change in pull request #82:
URL: https://github.com/apache/jclouds/pull/82#discussion_r487221374
##
File path: apis/sts/src/test/java/org/jclouds/aws/util/AWSUtilsTest.java
##
@@ -88,6 +95,20 @@ public void testNoExceptionParsingTextPlain() {
gaul commented on pull request #71:
URL: https://github.com/apache/jclouds/pull/71#issuecomment-706114180
Superseded by #84.
This is an automated message from the Apache Git Service.
To respond to the message, please log on
gaul closed pull request #71:
URL: https://github.com/apache/jclouds/pull/71
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the
geomacy commented on pull request #78:
URL: https://github.com/apache/jclouds/pull/78#issuecomment-708636833
hi all, just regarding Ignasi's
[comment](https://github.com/apache/jclouds/pull/78#issuecomment-650507931) and
Alex's
korlov42 commented on pull request #84:
URL: https://github.com/apache/jclouds/pull/84#issuecomment-706289116
@nacx, for now, only GET and HEAD requests will be rejected if they have a
body. But there is another validation that forced me to slightly modified the
production code: rejecting
gurkerl83 commented on pull request #78:
URL: https://github.com/apache/jclouds/pull/78#issuecomment-711058485
@geomacy My assessment of whether the change is a critical change is as
follows.
The main area of concern is the way Apache JClouds is used within Apache
Brooklyn?
gurkerl83 commented on pull request #78:
URL: https://github.com/apache/jclouds/pull/78#issuecomment-711096391
The work of this branch is ready for review.
There is an additional feature in the Apache JCloud Lab project waiting
which syncs the OSGi handling due to the shared Maven
gurkerl83 opened a new pull request #5:
URL: https://github.com/apache/jclouds-labs/pull/5
This project, the lab version of Apache JCloud, share the exact build
instructions as the primary Apache JCloud project with all its modules.
Apache JCloud is shifting its strategy in handling
gaul merged pull request #85:
URL: https://github.com/apache/jclouds/pull/85
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the
gurkerl83 commented on pull request #78:
URL: https://github.com/apache/jclouds/pull/78#issuecomment-712657957
Should I do a rebase and squash?
This is an automated message from the Apache Git Service.
To respond to the
gaul commented on pull request #84:
URL: https://github.com/apache/jclouds/pull/84#issuecomment-706448176
This now fails with a compile error:
```
/home/travis/build/apache/jclouds/providers/profitbricks/src/test/java/org/jclouds/profitbricks/features/ImageApiMockTest.java:20:
gaul commented on pull request #84:
URL: https://github.com/apache/jclouds/pull/84#issuecomment-706513786
@korlov42 Thank you for taking on this large task! The change looks good.
How can we best test this so that we have confidence that it works? Have you
tried running against a real
korlov42 commented on pull request #84:
URL: https://github.com/apache/jclouds/pull/84#issuecomment-706498753
The IDEA decided to put changes of one particular file to another change
list, thus locally there is no problem, but these changes have missed in remote
repo.
korlov42 opened a new pull request #84:
URL: https://github.com/apache/jclouds/pull/84
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go
gaul closed pull request #71:
URL: https://github.com/apache/jclouds/pull/71
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the
gaul commented on pull request #71:
URL: https://github.com/apache/jclouds/pull/71#issuecomment-706114180
Superseded by #84.
This is an automated message from the Apache Git Service.
To respond to the message, please log on
nacx commented on pull request #84:
URL: https://github.com/apache/jclouds/pull/84#issuecomment-708374713
>for now, only GET and HEAD requests will be rejected if they have a body.
But there is another validation that forced me to slightly modified the
production code: rejecting requests
korlov42 commented on pull request #84:
URL: https://github.com/apache/jclouds/pull/84#issuecomment-707714150
> Have you tried running against a real provider when overriding the
transport to OkHttp?
Unfortunately, I don't have possibility to test this on real-world
environment, so
nacx commented on pull request #84:
URL: https://github.com/apache/jclouds/pull/84#issuecomment-706210284
I remember quite some time ago I had a look at OkHttp3, but found that some
of the APIs some providers have conflicted with validations in OkHttp3, such as
rejecting DELETE operations
gaul commented on pull request #84:
URL: https://github.com/apache/jclouds/pull/84#issuecomment-706185421
@korlov42 Can you look at the CI failure?
```
Caused by: java.lang.UnsupportedOperationException:
clientBuilder.sslSocketFactory(SSLSocketFactory) not supported on JDK 9+
gaul opened a new pull request #85:
URL: https://github.com/apache/jclouds/pull/85
Fixed via:
```
find -executable -not -type d -name \*.java -exec chmod -x {} \;
```
This is an automated message from the Apache
demobox opened a new pull request #15:
URL: https://github.com/apache/jclouds-site/pull/15
builds.a.o -> ci-builds.a.o
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
demobox commented on pull request #15:
URL: https://github.com/apache/jclouds-site/pull/15#issuecomment-676845501
Thanks for taking a look, @gaul!
This is an automated message from the Apache Git Service.
To respond to the
cdancy commented on pull request #75:
URL: https://github.com/apache/jclouds/pull/75#issuecomment-681975285
@gaul @nacx any chance we can get a new release with this fix?
This is an automated message from the Apache Git
gaul commented on pull request #75:
URL: https://github.com/apache/jclouds/pull/75#issuecomment-682237714
Probably a few months. We are still working on the OkHttp and gson
dependencies.
This is an automated message from
gurkerl83 commented on pull request #78:
URL: https://github.com/apache/jclouds/pull/78#issuecomment-701197844
Thank you for checking the status of the Feature Branch, which has been
pushed into the background a bit because of other things.
The Feature Branch is not complete, the
nacx commented on pull request #82:
URL: https://github.com/apache/jclouds/pull/82#issuecomment-696127269
Cherry-picked to 2.2.x as well.
This is an automated message from the Apache Git Service.
To respond to the message,
nacx merged pull request #82:
URL: https://github.com/apache/jclouds/pull/82
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the
gaul opened a new pull request #83:
URL: https://github.com/apache/jclouds/pull/83
Release notes:
https://github.com/google/guice/wiki/Guice423
This is an automated message from the Apache Git Service.
To respond to
gaul commented on pull request #78:
URL: https://github.com/apache/jclouds/pull/78#issuecomment-699260926
@gurkerl83 @nacx Do we have a path forward on this PR? I would like to
include it in the next release.
This is an
gaul commented on pull request #83:
URL: https://github.com/apache/jclouds/pull/83#issuecomment-699442040
> We may want to update our [jclouds-compat build
matrix](https://ci-builds.apache.org/job/JClouds/job/jclouds-compat/) to better
reflect what we support now.
Done.
gaul merged pull request #83:
URL: https://github.com/apache/jclouds/pull/83
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the
nacx commented on a change in pull request #82:
URL: https://github.com/apache/jclouds/pull/82#discussion_r490171464
##
File path: apis/sts/src/test/java/org/jclouds/aws/util/AWSUtilsTest.java
##
@@ -88,6 +95,20 @@ public void testNoExceptionParsingTextPlain() {
401 - 500 of 1083 matches
Mail list logo
