Page MenuHomePhabricator

ptarjan (Paul Tarjan)
User

Projects

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Friday

  • Clear sailing ahead.

User Details

User Since
Feb 17 2011, 11:09 AM (476 w, 5 d)
Availability
Available

Recent Activity

Wed, Mar 25

ptarjan committed rARC33b9728b5f65: Run ls-files from the root of the directory (authored by ptarjan).
Run ls-files from the root of the directory
Wed, Mar 25, 9:24 PM
ptarjan closed D21045: Run ls-files from the root of the directory.
Wed, Mar 25, 9:24 PM
ptarjan updated the summary of D21045: Run ls-files from the root of the directory.
Wed, Mar 25, 9:13 PM
ptarjan updated the summary of D21045: Run ls-files from the root of the directory.
Wed, Mar 25, 9:13 PM
ptarjan updated the summary of D21045: Run ls-files from the root of the directory.
Wed, Mar 25, 9:12 PM
ptarjan updated the diff for D21045: Run ls-files from the root of the directory.

use repository api

Wed, Mar 25, 9:06 PM
ptarjan requested review of D21045: Run ls-files from the root of the directory.
Wed, Mar 25, 8:45 PM

Fri, Mar 20

ptarjan committed rARC97e050fce7a5: Use a named remote and branches for staging to help git-lfs (authored by ptarjan).
Use a named remote and branches for staging to help git-lfs
Fri, Mar 20, 6:57 PM
ptarjan closed D21041: Use a named remote and branches for staging to help git-lfs.
Fri, Mar 20, 6:57 PM
ptarjan updated the diff for D21041: Use a named remote and branches for staging to help git-lfs.
  • code rewview
Fri, Mar 20, 6:44 PM
ptarjan added a comment to D21041: Use a named remote and branches for staging to help git-lfs.

Thanks for the code review and archeology! I did some archeology on our end and indeed, it was removed on Sep 26, 2018 when we forked this diff workflow for exactly the reason in this diff. With the --no-verify the LFS objects were not being pushes to our staging repo, so our Jenkins jobs wouldn't have them and would fail. So I do think this the right fix :)

Fri, Mar 20, 3:56 PM
ptarjan updated the diff for D21041: Use a named remote and branches for staging to help git-lfs.
  • oops wrong way
Fri, Mar 20, 1:01 AM
ptarjan added a comment to D21041: Use a named remote and branches for staging to help git-lfs.

Nice find! I see there is already a --no-verify in this upstream version but we didn't have it in ours... maybe because of the lfs version? So maybe this diff is actually improving the life of lfs folks?

Fri, Mar 20, 1:00 AM
ptarjan updated the diff for D21041: Use a named remote and branches for staging to help git-lfs.
  • go with --no-verify
Fri, Mar 20, 12:59 AM
ptarjan updated the diff for D21041: Use a named remote and branches for staging to help git-lfs.
  • Revert "only run fetch if git for-each-ref is empty"
  • Revert "fix spelling"
  • Revert "handle the case where you need to remove it before adding it"
  • Revert "Use a named remote and branches for staging to help git-lfs"
  • try the double push thing for lfs repos
Fri, Mar 20, 12:42 AM
ptarjan added a comment to D21041: Use a named remote and branches for staging to help git-lfs.

Thanks Evan! I tried what you suggested but I think GIT_LFS_SKIP_SMUDGE=1 is only for pulling not pushing, since the first push in your suggestion is still uploading to LFS and their code doesn't seem to refer to that env var https://github.com/git-lfs/git-lfs/blob/5f969e6a3e48ecee48b6235adccc42a644e82101/commands/command_push.go, I can't really see any way to disable lfs other than git lfs uninstall; git push; git lfs install. Is that nuts?

Fri, Mar 20, 12:28 AM

Thu, Mar 19

ptarjan updated the diff for D21041: Use a named remote and branches for staging to help git-lfs.
  • only run fetch if git for-each-ref is empty
Thu, Mar 19, 9:59 PM
ptarjan updated the diff for D21041: Use a named remote and branches for staging to help git-lfs.
  • fix spelling
Thu, Mar 19, 6:41 PM
ptarjan updated the diff for D21041: Use a named remote and branches for staging to help git-lfs.
  • handle the case where you need to remove it before adding it
Thu, Mar 19, 6:38 PM
ptarjan updated the diff for D21041: Use a named remote and branches for staging to help git-lfs.

try again now that I put in my ssh key

Thu, Mar 19, 6:33 PM
ptarjan updated the diff for D21041: Use a named remote and branches for staging to help git-lfs.

try again now that I put in my ssh key

Thu, Mar 19, 6:33 PM
ptarjan requested review of D21041: Use a named remote and branches for staging to help git-lfs.
Thu, Mar 19, 6:29 PM

Jun 9 2015

ptarjan added a comment to D11384: Add a recommendation for the amount of RAM required to run Phabricator.

@epriestley is a t2.micro enough to handle phabricator for say 10 users (small startup)? What's the tipping point (concurrent requests I'm assuming not DB size for extra users)?

Jun 9 2015, 7:05 PM

Sep 30 2014

ptarjan added a comment to P1098 (An Untitled Masterwork).

How did you fix this problem?

Sep 30 2014, 9:54 PM

Sep 22 2014

ptarjan created T6157: Failing to parse patch with binary delta.
Sep 22 2014, 9:52 AM · Arcanist

Mar 22 2014

ptarjan added a comment to T4662: Make arc look for .arcconfig in non-root directories.

@epriestley I'm totally with you, we don't want any special casing for Facebook. I was just hoping others could benefit from this as well.

Mar 22 2014, 5:39 AM · Arcanist
ptarjan updated subscribers of T4662: Make arc look for .arcconfig in non-root directories.
Mar 22 2014, 4:03 AM · Arcanist