User Details
- User Since
- Jun 3 2015, 9:55 AM (463 w, 2 d)
- Availability
- Available
Jun 1 2021
Sep 15 2019
Aug 13 2019
Apr 19 2019
Feb 28 2019
and now when I re-run the command again, it gets another 7 commits and fails again. So, perhaps by me viewing the commit, I kick off a job that rebuilds something on the backend?
It's now failing on this one (consistently if I keep running it):
mysql> SELECT * FROM phabricator_repository.repository_commit WHERE id = 71471; +-------+--------------+--------------------------------+------------------------------------------+------------+------------+-------------+---------+--------------+--------------------+-----------------------+ | id | repositoryID | phid | commitIdentifier | epoch | authorPHID | auditStatus | summary | importStatus | authorIdentityPHID | committerIdentityPHID | +-------+--------------+--------------------------------+------------------------------------------+------------+------------+-------------+---------+--------------+--------------------+-----------------------+ | 71471 | 41 | PHID-CMIT-ohupojjoniypwpghvlr2 | 43034ccb9eac4ca8a655f655b726f73c5e551413 | 1438182566 | NULL | none | | 1024 | NULL | NULL | +-------+--------------+--------------------------------+------------------------------------------+------------+------------+-------------+---------+--------------+--------------------+-----------------------+ 1 row in set (0.01 sec)
I thought rPHU4d21f105b17f250aaaeb8937142ae4cbc978389f was meant to fix this, but apparently not.
Feb 6 2018
As per https://github.com/PHPOffice/PHPExcel/commit/c269793ee715fb5a15f0b2ad25c064d9ee6e8e53, PHPExcel has been deprecated and replaced with PHPSpreadsheet. So, instead of recommending PHPExcel, shouldn't PHPSpreadsheet be supported?
May 27 2017
Thanks, everybody! Appreciate it, especially on a Friday night. :-)
That does indeed work! Thank you so much!
Not easily. :/
Aug 27 2016
See https://github.com/tinfoil/devise-two-factor/issues/30 and https://github.com/mdp/rotp/issues/44 for some discussion about this issue (also discussed a bit on oss-security mailing list as http://www.openwall.com/lists/oss-security/2015/06/20/4).
Nov 27 2015
Note that this diff implements all three forms of AWS-supported SSE (Server-Side Encryption), including SSE-C, which allows for customer-specified encryption keys. See https://docs.aws.amazon.com/AmazonS3/latest/dev/ServerSideEncryptionCustomerKeys.html for more information. You are still trusting Amazon to do the right thing here. https://d0.awsstatic.com/whitepapers/AWS_Securing_Data_at_Rest_with_Encryption.pdf and https://d0.awsstatic.com/whitepapers/KMS-Cryptographic-Details.pdf go into detail on how they do that.
Jul 23 2015
- Add support for two more of S3's server-side encryption types.