Good day!
While Im doing sudo arc diff origin/develop and my git repositories are also updated (both local and on the github), it always have this error and still not reflected on our Phabricator account.
Totally noob in using arc and phabricator. I pasted here the error message since I also did --trace.
Thank you. And anyone can suggest a good blog/tutorial about arcanist and phabricator for beginners?
It's trying to update an existing diff that has already been marked as closed. if you want to update that old diff, you will need to re-open it or use arc diff origin/develop --create
Related
I am new to using git and currently employ the following combination:
Git-Gui v.0.20
R-studio 0.99.489
R 3.22
Bitbucket code repository
Windows 7
Until recently this combination worked fine for pulling and pushing code to the repository. But now I cannot push modified code anymore nor commit it in R-studio.
In R-studio, modified code is marked by a blue M with a checkbox next to it. I cannot check this box for staging, committing and pushing anymore. It literally does not check and react when I click on it.
When I create a new code sniplet which shows as yellow question mark ? I can check and push it, but modified versions cannot be checked anymore.
I have already deinstalled git and R-studio and re-installed but the problem persists. I also created a new repository but the problem occured in the new repository as well. I am a bit clueless where to start looking for a soluation and a web search did not yield many results except this discussion here, which I cannot fully follow because it perhaps does not apply fully to my problem. In any case when I give
> Sys.which('git')
R returns:
git
""
I would appreciate advice where to go from here.
I found an answer to my question. It is a bug in RStudio, albeit not a very well documented one.
When there is a space in the .R file name, it is not possible to push the file through git. Removing the space solves the problem.
See here for an official comment on the Rstudio board dating February 2015. I am using the most recent version of Rstudio and it is not yet fixed there.
Try if the issue persists with:
the latest git for Windows unzipped anywhere you want: PortableGit-2.6.3-64-bit.7z.exe
its path added to %PATH%:
set PATH=%PATH%;C:\path\to\PortableGit-2.6.3-64-bit\bin
its path declare in R-Studio C:\path\to\PortableGit-2.6.3-64-bit\bin\git.exe
R-Studio itself launched from a CMD session where %PATH% already references git.
You just installed a meteor package, and for some reason it isn't working. You suspect that it's the package itself that has a bug. You want to investigate that. How do you do that?
Optimally, you'd be able to run a command that forks the original package repository with the right version and replaces the original in your meteor application, ready for you to debug it and, once fixed, possibly generate a pull request.
I don't expect something like this to exist as a single command, but is there a workflow that you follow to do exactly that? Or do you approach the problem in a different way?
Do a git clone of the package into your local packages folder. Fix any bugs you need to. Commit them. And make a pull request. Once the pull request is accepted, you can remove the local package and use the regular package.
From when I've asked in the past, there isn't really an easier way to do this it seems. But to be honest, this approach isn't too much work.
Also, if you just want to debug, you can step through the package code while it's running without cloning the repo locally. (Assuming it's running in development mode and hasn't been minified by Meteor).
Please check if you can install this.
https://github.com/AjayMT/online-todos
I have an error with relase file meteor.
Please give me some step to install this app.
The last commit on that repo was 2 years ago, which is a lifetime in Meteor terms, so this is going to use a version of meteor which is way, way out of date. It would probably take a lot of work to get it to function with a supported version.
Whether you're looking for this as a way to learn Meteor or for something to actually use, you should be using the official todos app. The (correct) instructions for Meteor installation are here.
I cannot get phabricator to display the changes in using the file context. I got the "Context not available" on every file.
Does anyone know why is this not work? What should i do to debug this problem?
This seems a problem related with SVN only because its working with GIT.
Thanks.
I bumped in the same problem recently and googled this question. I found out that the context is available only when diff is created via arcanist command line tool (arc diff) in Linux or Mac OS.
It won't work if you create a diff directly by pasting it in Phabricator/Differential or by using arcanist tool in Windows.
I tested this with arcanist on Ubuntu 14.04, Mac OS 10.10 (those two worked) and in Windows 7 (didn't work).
You didn't specify whether you're using the arc diff command line tool, or manually uploading a diff via the Phab. web interface.
If you're not using arc diff, I have an answer for you: It's up to you to include the context yourself. Phab. only knows what's in the diff/patch that you give it. If you can't get the full context, that's a fault with your diff/patch, not with Phab.
If you're using a standard diff utility, like GNU diff, you can use the command-line arguments to dictate how much context to include in the output. I usually use some obscenely large number, like 500 or 1000, to ensure that the entire file ends up in the output.
I just took a quick look at the svn command-line documentation, and it seems that there's no way to control how much context goes into the output. ...but maybe I'm wrong...
In any case, shortboy is correct that the easiest way to get the full file context is to use arc diff.
I would like to know the currently practiced procedure in patching httpunit.
I saw in this thread
Is HttpUnit deprecated / inactive / not supported?
that Russell has put the httpunit source to his github repo.
The FAQ note for httpunit still talks about the svn repo at sourceforge for patching.
If I have a patch, should I use the svn repo and attach the patch to the ticket to source forge's issue tracking or use the repo at github and send a pull request there?
Thanks.
Regards, aki
My name is Wolfgang Fahl and I am one of the committers of httpunit. Thank you for pointing out that the FAQ is outdated regarding the usage of subversion - I am going to fix the FAQ.
The pull request approach seems like a reasonable way to proceed. You might want to make sure that you add
a Junit Test - that shows your change is necessary
-- the test should fail before the change and all other tests should succeed
-- the test should succeed after the change and all other tests should succeed
and the change in the source code
To get the current source code of httpunit you may clone it via:
git clone https://github.com/russgold/httpunit
if you do a
mvn test
the result should like
Results :
Tests run: 822, Failures: 0, Errors: 0, Skipped: 8
With 822/8 being the number of tests as of 2014-02-11 that are executed/skipped.
The Failures should be 0.
Please feel free to add a link to your patch / your pull request here. I appreciate that you are using stackoverflow as a platform for this communication and I hope more of the httpunit users and developers will do so in the future.
This looks like a very good approach; I have to do some work to update the website to reflect it.