I get a repo is not local error. It looks like the code is trying to get
the file contents as of a specific changeset from a remote server via ssh.
I'm not sure if there is a way to do that without cloning the repo. If
there repo is available via a webbrowser, then the file can be retrieved
via
I'm still getting the file not found error when I do a rbt post -u -d. Here
is the error (I'm trying a different file than before.)
Error data: {u'stat': u'fail', u'file': u'src/SIPSA.cpp', u'err':
{u'msg': u'The file was not found in the repository.', u'code': 207},
u'revision':
What happens if you remove the —cwd line?
We probably want to conditionalize setting that.
Christian
--
Christian Hammond - christ...@beanbaginc.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On June 16, 2014 at 9:39:08 AM, Ali Ghorashi
Are the hg svn errors normal?
I'm also confused about another thing: Why does the reviewboard server
needs to know where the main Mercurial repo is? What if one does not exist?
In a distributed source control system, all the data is available to the
rbt tool. It should be able to post a
The ‘hg svn’ errors are normal in debug output, if the appropriate extension is
not installed or it’s not a hg svn repository.
Review Board fetches the full contents of the files referenced in the diffs in
order to generate a side-by-side diff viewer that can be analyzed and expanded.
Because
Thanks for clearing that up.
Is there any file/function I can put some debug statements in to see what
the problem is? I have't had time to start tracing though the code yet.
On Thursday, June 12, 2014 1:32:36 PM UTC-6, Christian Hammond wrote:
The ‘hg svn’ errors are normal in debug output,
The thing I’d want to check first is that src/Message.h, revision 79c09fdfad23
is actually in the repository that Review Board is pointed to. Can you verify
that? If that’s not the case, then either that repository doesn’t have the
latest-and-greatest (which is important), or there’s some issue
Thanks Christian,
See the attached file for the debug output. There is nothing special about
the repo setup: I don't have any branches. Everything up to changeset
100:79c09fdfad23 is pushed into the main repo. I changed a file with
changeset: 101:1170d2410ead and then did a rbt post. To say it
Ok. I must be missing something. Here is what I'm trying on a fresh
reviewboard install
1) Configure a repo with a full path: ssh://source.xxx.com//path_to_project
2) Enter user name and password
3) Push all changes to the Mercurial Repo
4) Change a file
5) Commit the file (no push)
6) Run rbt
Hi Ali,
Can you run the ‘rbt post’ with —debug and show me the result?
Also, what does your branch structure look like? It’ll be helpful for me to
know what the commit ID is for the change you’re trying to post, as well as the
nearest upstream branch.
Christian
--
Christian Hammond -
Thanks for the reply Christian.
I posted the wrong error message. The error is:
ERROR: Error uploading diff
The file was not found in the repository. (HTTP 400, API Error 207)
Your review request still exists, but the diff is not attached.
Successive attempts with the -u options (i.e. rbt post
Update: The rbt post 101 command does not work either.
I should mention that I'm using mercurial via ssh. In other words, my
server URL is ssh://xxx.xxx.com
On Monday, June 9, 2014 12:45:48 PM UTC-6, Ali Ghorashi wrote:
Thanks for the reply Christian.
I posted the wrong error message. The
Hello All,
I'm evaluating Review Board. I'm running RB version 2.0.1 on Centos 6.5
with Mercurial v 2.8.3.
My question is regarding the rbt post command: After I do a commit and
run rbt post, I get the following error:
ERROR: Error creating review request: Review request with this commit ID
They don’t need to specify a version number. It is using the tip.
What’s happening with that error is that you’ve already posted a review request
representing the commit that you’ve posted for review. Review Board tries to
keep a 1-to-1 mapping of commit ID and review request, and so it’s
14 matches
Mail list logo
