- User Since
- Oct 9 2013, 12:25 AM (228 w, 5 d)
Tue, Feb 20
Jan 6 2018
Jan 4 2018
Dec 28 2017
FWIW, I am using a custom file and mail engine that utilises the AWS SDK and supports instance profile credentials. See P2082 and P2083. You need to install and require the AWS SDK before using these extensions.
Nov 26 2017
Nov 24 2017
I will land it shortly.
Nov 16 2017
Nov 13 2017
Oct 10 2017
Oct 9 2017
Sep 27 2017
Sep 25 2017
Sep 18 2017
Oh cool. I'm somewhat surprised this is being accepted as I expected it to be blocked on T4334#222499.
Aug 10 2017
Thanks for the detailed response, I certainly didn't expect it.
Aug 9 2017
(interestingly, I didn't receive an email about this diff being accepted)
Aug 6 2017
I wonder if this OOM error can also be hit in other workflow though, given that it seems to occur in PhabricatorFileStorageEngine::getRawFileDataIterator.
Yep, agreed that the re-targeted proposal is a better solution... I had just assumed that this was a documentation oversight.
Aug 2 2017
Jul 31 2017
I'm seeing these errors failing regularly:
I've got a reproduction case for this now: https://secure.phabricator.com/differential/diff/44008/
Jul 30 2017
Jul 27 2017
See PHI18 for discussion
Jul 25 2017
@hach-que, did you end up implementing a solution for this?
Jul 24 2017
I am also seeing this error and am trying to work on a fix.
Jul 19 2017
Jul 12 2017
Another correction, Puppet doesn't //need/ a dedicated server. You can run Puppet in a standalone (agent) mode, if you are willing to somehow get your Puppet manifests onto each host that you wish to provision.
FWIW, I am actively working on a Puppet module for Phabricator, see https://forge.puppet.com/joshuaspence/phabricator.
AWS doesn't have a single device which can both listen for TCP on 22 (only ELB) and terminate SSL for websockets (only ALB).
Jul 11 2017
Jul 10 2017
Ah sorry, I should've made that clear. Yes, I am able to reproduce the issue on our installation.