Re: [jclouds-labs] [JCLOUDS-1046] Remove h2-jdbc provider from source tree (#236)
Closed #236. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/236#event-566997012
Re: [jclouds-labs] [JCLOUDS-1046] Remove h2-jdbc provider from source tree (#236)
I made one more fix 2b597284e7ecf035cffa3bc9a59f5fbce0f7fb6b and now all tests pass so I enabled the module in 2f4dc796c325e1362ea27612c94059e4f5fc3770. If we want to continue discussing removal of the JDBC blobstore let's revisit it on the mailing list instead of code review. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/236#issuecomment-189132927
[jira] [Commented] (JCLOUDS-1005) Backblaze B2 Cloud Storage
[ https://issues.apache.org/jira/browse/JCLOUDS-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15168553#comment-15168553 ] Andrew Gaul commented on JCLOUDS-1005: -- [~rishabh7m] Thanks for introducing yourself! Let's scope this issue to only B2 continue other discussions on the jclouds-user mailing list. But in the mean-time, please look at some of the smaller jclouds-blobstore issues or possible the azureblob ones given your previous experience: * https://issues.apache.org/jira/browse/JCLOUDS-193?jql=project%20%3D%20JCLOUDS%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20jclouds-blobstore%20ORDER%20BY%20priority%20DESC * https://issues.apache.org/jira/browse/JCLOUDS-887?jql=labels%20%3D%20azureblob%20AND%20status%20!%3D%20resolved We also have some smaller TODOs in the azureblob provider to address. > Backblaze B2 Cloud Storage > -- > > Key: JCLOUDS-1005 > URL: https://issues.apache.org/jira/browse/JCLOUDS-1005 > Project: jclouds > Issue Type: New Feature > Components: jclouds-blobstore >Affects Versions: 1.9.1 >Reporter: Andrew Gaul > Labels: gsoc2016 > > Backblaze announced B2 which has its own object storage API: > https://www.backblaze.com/b2/docs/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (JCLOUDS-255) atmos, aws-s3, azure blob signers doesn't support query parameter authentication
[ https://issues.apache.org/jira/browse/JCLOUDS-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Gaul updated JCLOUDS-255: Labels: atmos azureblob (was: ) > atmos, aws-s3, azure blob signers doesn't support query parameter > authentication > > > Key: JCLOUDS-255 > URL: https://issues.apache.org/jira/browse/JCLOUDS-255 > Project: jclouds > Issue Type: Improvement > Components: jclouds-blobstore >Affects Versions: 1.6.2 >Reporter: Kevin Krouse >Priority: Minor > Labels: atmos, azureblob > > Some blob store providers allow using signed requests in two forms: either > with an Authorization header or with query parameters. Using the query > parameter form of the signed request is necessary for clients that don't > support adding a header or for returning a redirect where the Authorization > header would be removed. > The jclouds atmos, aws-s3, and azure implementations generate signed requests > only with the Authorization header, while cloudfiles-us, > hpcloud-objectstorage use query parameters. Ideally the BlobRequestSigner > interface would allow the user to decide which form of signed request to > create. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (JCLOUDS-1046) h2-jdbc module is not listed in jclouds-labs/pom.xml
[
https://issues.apache.org/jira/browse/JCLOUDS-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul resolved JCLOUDS-1046.
--
Resolution: Fixed
Assignee: Andrew Gaul (was: Roman Coedo)
Fix Version/s: 2.0.0
> h2-jdbc module is not listed in jclouds-labs/pom.xml
>
>
> Key: JCLOUDS-1046
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1046
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-blobstore, jclouds-labs
>Affects Versions: 2.0.0
>Reporter: Josef Cacek
>Assignee: Andrew Gaul
> Labels: jdbc
> Fix For: 2.0.0
>
>
> The h2-jdbc module is not listed in jclouds-labs/pom.xml. It means the {{mvn
> versions:set}} call doesn't set correctly version of this module for instance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (JCLOUDS-1046) h2-jdbc module is not listed in jclouds-labs/pom.xml
[
https://issues.apache.org/jira/browse/JCLOUDS-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15168539#comment-15168539
]
ASF subversion and git services commented on JCLOUDS-1046:
--
Commit 2f4dc796c325e1362ea27612c94059e4f5fc3770 in jclouds-labs's branch
refs/heads/master from [~gaul]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds-labs.git;h=2f4dc79 ]
JCLOUDS-1046: Enable h2-jdbc module
All tests now pass.
> h2-jdbc module is not listed in jclouds-labs/pom.xml
>
>
> Key: JCLOUDS-1046
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1046
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-blobstore, jclouds-labs
>Affects Versions: 2.0.0
>Reporter: Josef Cacek
>Assignee: Roman Coedo
> Labels: jdbc
> Fix For: 2.0.0
>
>
> The h2-jdbc module is not listed in jclouds-labs/pom.xml. It means the {{mvn
> versions:set}} call doesn't set correctly version of this module for instance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: [jclouds] Swift container JSON requests and null checks (#923)
> @@ -69,7 +69,7 @@ public void testExtractArchive() throws Exception {
>
> .extractArchive(containerName, payload, "tar.gz");
> assertEquals(extractResponse.getCreated(), OBJECT_COUNT);
> assertTrue(extractResponse.getErrors().isEmpty());
> -
> assertEquals(api.getContainerApi(regionId).get(containerName).getObjectCount(),
> OBJECT_COUNT);
> +
> assertEquals(api.getContainerApi(regionId).get(containerName).getObjectCount(),
> Long.valueOf(OBJECT_COUNT));
Is this needed (here and elsewhere)? If you let OBJECT_COUNT be autoboxed, the
test spec will reflect the backwards compatibility of the change, as least in
source, as was mentioned. Thoughts?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/923/files#r54118030
Re: [jclouds] Properly handler ProfitBricks service errors (#928)
+1. Thanks for the fix @nacx ! :) --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/928#issuecomment-188742502
[jclouds] Properly handler ProfitBricks service errors (#928)
The current implementation of the error handler just propagated exceptions for the expected response codes, but ignored all other failed responses. This ended up in failed requests to be treated as successful ones, and errors appeared later and without the proper context. This PR fixes that. Also, ProfitBricks returns a `javax.ejb.EJBException` when calling `getImage` from an account that has permissions on that image but does not own it. it is likely to be a bug on their side, but we can properly handle that, so the compute service adapter has been changed to the this into account. /cc @devcsrj You can view, comment on, or merge this pull request online at: https://github.com/jclouds/jclouds/pull/928 -- Commit Summary -- * Properly handler ProfitBricks service errors -- File Changes -- M providers/profitbricks/src/main/java/org/jclouds/profitbricks/compute/ProfitBricksComputeServiceAdapter.java (13) M providers/profitbricks/src/main/java/org/jclouds/profitbricks/domain/ServiceFault.java (89) M providers/profitbricks/src/main/java/org/jclouds/profitbricks/handlers/ProfitBricksHttpErrorHandler.java (11) M providers/profitbricks/src/main/java/org/jclouds/profitbricks/http/ResponseStatusFromPayloadHttpCommandExecutorService.java (12) M providers/profitbricks/src/main/java/org/jclouds/profitbricks/http/parser/ServiceFaultResponseHandler.java (27) M providers/profitbricks/src/test/java/org/jclouds/profitbricks/http/parser/ServiceFaultResponseHandlerTest.java (32) A providers/profitbricks/src/test/resources/fault-500.xml (9) -- Patch Links -- https://github.com/jclouds/jclouds/pull/928.patch https://github.com/jclouds/jclouds/pull/928.diff --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/928
