User Details
- User Since
- Sep 29 2014, 10:11 PM (529 w, 2 d)
- Availability
- Available
Jul 3 2017
That's what I suspected (I did find the rsrc link, but it seemed a bit suspect, and my default setup doesn't serve it anyway). Thanks!
Jun 27 2017
Nov 19 2016
Great thanks!
Fixed and I'm back up and running, thanks!
I can confirm that SHOW TABLES IN phabricator_xhpast works just fine as root mysql user, and dropping the credentials from the upgrade command yields exactly the same results as running under root. So that seems like it all ties up. I can work around this any number of ways and I will do just that.
Sep 1 2016
params="
{
\"buildTargetPHID\": \"$PHID\",
\"artifactKey\": \"jenkins.uri.$PHID\",
\"artifactType\": \"uri\",
\"artifactData\": {
\"uri\": \"http://build:8080/job/$JOB_NAME/$BUILD_NUMBER\",
\"name\": \"Jenkins Build\",
\"ui.external\": true
},
\"__conduit__\": { \"token\": \"$CONDUIT_API_TOKEN\" }
}"Aug 31 2016
Jul 20 2016
I won't comment on the specifics, but have you looked at the herald transcript? I normally find the answer hiding in there.
Jul 13 2016
Jul 5 2016
That did the trick, thanks!
Jul 4 2016
May 20 2016
If this is the outcome of you using arc land then you are doing it wrong. Just flick the history to immutable if you don't want it squashed.
Would definitely like the ability to swap out the eye via config à la wikimedia install.
May 6 2016
Ahh! It's right there on the bloody page. Sorry.
May 4 2016
May 3 2016
Yeah, I'd like to encourage people to work like that (review each change to the shared branch and then land it to the shared branch) but just getting people to use arc "normally" is proving more than some people can bear (I recently pushed a us onto git from svn, the transition has not been without pain for some). I hadn't considering commiting then reverting the change to .arcconfig.
That would work for us, yes.
Apr 29 2016
Right at the top of the home page...
Apr 28 2016
Can confirm that on latest stable my lfs-test repository now succeeds with both jars and jpegs. Huzzah!
Apr 26 2016
- make a private project
- add tasks you like to it
- ???
- profit
Apr 19 2016
@anthony-verge just edit the repo, scroll down, branch stuff is somewhere around there.
I'm not sure if this solves your problem, but just switch off autoclose for some prefix? We just have autoclose on master, as we don't consider anything on any branch that isn't master as done.
Apr 14 2016
You don't need any plugins with staging. Just set up a parameterised build, use a parameter for the commit and call directly from harbormaster. That's reason for staging repos, regular git tooling can work with them.
I am not sure exactly what you are trying to achieve, but if you want to do CI with differentials, just set up a herald rule to trigger a build plan when a diff is created / updated. This will trigger whether the staging commits are imported by phabricator or not.
Apr 13 2016
I'm not worried about immediate logout. I agree that the effort / reward tradeoff is all wrong there. I was more thinking about the case where you are setup for anonymous search. Every X a check is performed to see if users still exist.
Apr 8 2016
Interesting. Time to update my bot. Thanks!
I have build kind of thing out myself, using polling to check what revisions are open, then diff my list of "envs / build jobs" that I have running and then make the two line up. It would nice if it could be event based and triggered by herald.
Apr 7 2016
I've triggered similar problems running reparse on a repository where branches had been deleted that were tracked.
Unfortunately, no dice. I removed the jar file, and added a jpeg. I have attached a trace of running GIT_TRACE=1 git lfs fetch origin.
Can confirm that navigating to the file in diffusion will let me download it, and it really does give me back the right file.
As an addendum, I can definitely find the zip file on the box...
I'm on latest stable (fea2389), and I just tried the following
$ git clone ssh://git@phabricator.example.com:222/diffusion/18/lfs-test.git [10:54:36] Cloning into 'lfs-test'... warning: You appear to have cloned an empty repository. Checking connectivity... done. $ cd lfs-test/ [10:56:39] $ git lfs install [10:56:42] Updated pre-push hook. Git LFS initialized. $ git lfs track "*.jar" [10:57:05] Tracking *.jar $ cp ../some/path/antlr-3.2.jar . [10:57:19] $ ls [10:57:52] antlr-3.2.jar $ git add antlr-3.2.jar [10:57:54] $ git commit -m "testing" [10:57:57] [master (root-commit) 2690d02] testing 1 file changed, 3 insertions(+) create mode 100644 antlr-3.2.jar $ git push -u origin master [10:58:04] Git LFS: (1 of 1 files) 1.84 MB / 1.84 MB Counting objects: 3, done. Delta compression using up to 6 threads. Compressing objects: 100% (2/2), done. Writing objects: 100% (3/3), 329 bytes | 0 bytes/s, done. Total 3 (delta 0), reused 0 (delta 0) To ssh://git@phabricator.example.com:222/diffusion/18/lfs-test.git * [new branch] master -> master Branch master set up to track remote branch master from origin.
so far so good. however...
$ cd .. [10:58:18] $ rm -rf lfs-test/ [10:59:45] $ git clone ssh://git@phabricator.example.com:222/diffusion/18/lfs-test.git [10:59:50] Cloning into 'lfs-test'... remote: Counting objects: 3, done. remote: Compressing objects: 100% (2/2), done. remote: Total 3 (delta 0), reused 0 (delta 0) Receiving objects: 100% (3/3), done. Checking connectivity... done. $ cd lfs-test/ [11:00:15] $ ls [11:00:19] antlr-3.2.jar $ cat antlr-3.2.jar [11:00:45] version https://git-lfs.github.com/spec/v1 oid sha256:4c8737014e7ca0d2c85171edf37f5a26b2d8d8237c283357b81a3269b6848d38 size 1928009 $ git lfs fetch origin [11:05:19] Fetching master Git LFS: (2 of 1 files) 0 B / 1.84 MB Repository or object not found: http://phabricator.example.com/file/data/w5mihitt7ijile3b7n44/PHID-FILE-kbhl75cnfm6nwks7ojmf/dosd5iqevvn3rune/lfs-4c8737014e7ca0d2c85171edf37f5a26b2d8d8237c283357b81a3269b6848d38 Check that it exists and that you have proper access to it Warning: errors occurred
Mar 7 2016
Mar 4 2016
Perfect!
Feb 29 2016
Feb 27 2016
Feb 26 2016
Thanks!
I tried that and it gives the same complaint.
Feb 17 2016
Feb 16 2016
The other thing that's probably worth mentioning is that when I tried to create a new repo on the updated install, it has the same problems. Running the failing command in the repository root also succeeds, so it seems to be a paths thing... although the '.git' at the end of the command freaks me out, because the repos are bare, so there is no .git folder.
With the results being the same either way. The previous install was @ 6a035d977f22aaf1 (I will admit this was a bit lazy.. that's from November of last year).
Jul 1 2015
Apr 2 2015
Thanks, I'll get on it.
Very interested in this. Willing to contribute code if someone will have time to look at the patch (it doesn't have to be accepted, I just want to know that I am not stepping into something that is unlikely to get merged any time soon).
Mar 29 2015
Thanks for the insight. I guess my interest is registered, and I'll probably try to keep a patch like this maintained locally, and keep watching to see if azure does anything to lower the testing barrier.
What assistance could be offered to help this along? Setting up a test azure as app with access for the phabricator team?