Lahiru Sandaruwan created JCLOUDS-509:
-
Summary: Jclouds does not support AssociatePublicIpAddress
attribute of EC2 RunInstances API
Key: JCLOUDS-509
URL: https://issues.apache.org/jira/browse/JCLOUDS-509
[
https://issues.apache.org/jira/browse/JCLOUDS-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lahiru Sandaruwan updated JCLOUDS-509:
--
Description: This is required if the instance needs internet when the EC2
IaaS is not
[
https://issues.apache.org/jira/browse/JCLOUDS-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lahiru Sandaruwan updated JCLOUDS-509:
--
Description: This is required if the instance needs internet when the EC2
IaaS with a
[
https://issues.apache.org/jira/browse/JCLOUDS-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shri Javadekar updated JCLOUDS-510:
---
Description:
The current implementation of DeleteAllKeysInList suffers from the
+ // If a future to delete a blob/directory actually got created
above,
+ // keep a reference of that in the outstandingFutures list. This is
+ // useful in case of a timeout exception. All outstanding futures
can
+ // then be cancelled.
+ if
import com.google.common.util.concurrent.ListenableFuture;
import com.google.common.util.concurrent.ListeningExecutorService;
import com.google.inject.Inject;
/**
* Deletes all keys in the container
- *
+ *
* @author Adrian Cole
Done
---
Reply to this email directly or view
[
https://issues.apache.org/jira/browse/JCLOUDS-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul reassigned JCLOUDS-510:
---
Assignee: Andrew Gaul
Head-of-line blocking problem with DeleteAllKeysInList
[
https://issues.apache.org/jira/browse/JCLOUDS-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul updated JCLOUDS-510:
Affects Version/s: 1.8.0
1.7.1
Head-of-line blocking problem with
+ * a timeout. Also, when the reference is removed from this list and
when
+ * the executorService removes the reference that it has maintained,
the
+ * future will be marked for GC since there should be no other
references
+ * to it. This is important because
+ listing = blobStore.list(containerName, options);
+ } catch (ContainerNotFoundException ce) {
+ return listing;
+ }
+
+ // recurse on subdirectories
+ if (options.isRecursive()) {
+ for (StorageMetadata md : listing) {
+String
+ String marker = listing.getNextMarker();
+ if (marker != null) {
+logger.debug(%s with marker %s, message, marker);
+options = options.afterMarker(marker);
+listing = getListing(containerName, options, semaphore,
+
Looks like a network glitch on cloudbees.
code
ERROR: Error cloning remote repo 'origin'
hudson.plugins.git.GitException: Could not clone
git://github.com/jclouds/jclouds.git
...
stderr: fatal: unable to connect to github.com:
github.com[0: 192.30.252.129]: errno=Connection timed out
/code
Can
12 matches
Mail list logo
