Christian,
Thank you for your answer! I'll try to fix it. I think fix is easy,
Michael.
On 13 авг, 00:34, Christian Hammond wrote:
> I think the person who contributed ClearCase support on the server expected
> that the repository would be locally checked out with the path given. We'll
> certa
Hi Kate,
How did you configure the repository path as "test-bazel?" The repository
path for Git is generated by running "git remote show origin" in the tree.
Now, our Git support in 1.0.x is limited in that it requires a local clone
on the server that is updated regularly. You would specify the P
Hi,
It's possible that when you use the cache function, it's returning
cached data from some older, broken attempt. If you reenable the
caching and then fully clear the cache and try again, does it work?
Christian
On Wednesday, August 12, 2009, schuijo wrote:
>
> More:
>
> I traced the source
On Wed, Aug 12, 2009 at 6:51 PM, Christian Hammond wrote:
> Hi Eduardo,
>
> My biggest concern at this point is adding another dependency, especially
> one that isn't pure-Python and easy_install'able. We have a lot of
> dependencies today, some optional, some required. Those that are required
> a
More:
I traced the source of that parameter to get_original_file() in
diffutils.py. When I bypass the cache lookup and just return the
result of the fetch_file() sub-function I can display diffs properly,
although response is very slow as expected. Any ideas where I should
look to determine why
I think I am very close now, but I have a problem in diffutils.py.
The second parameter in the parse() function (file I believe) contains
some invalid data, where does this get populated?
Thanks!
On Aug 11, 2:29 pm, Christian Hammond wrote:
> Hi,
>
> Path is the path to the file in the reposit
Hi,
We're evaluating Review Board and we're having trouble using post-review
with git repositories. Basically, we keep getting an error that looks like
this:
>>> HTTP POSTing to http://reviews.ninginc.com/api/json/reviewrequests/new/:
{'repository_path': 'test-bazel', 'submit_as': 'davidf'}
Error
Hi Eduardo,
My biggest concern at this point is adding another dependency, especially
one that isn't pure-Python and easy_install'able. We have a lot of
dependencies today, some optional, some required. Those that are required
and pure Python are easy. We can just add them to Review Board's depend
It sounds like it's actually using the ClearCase SCM instead of your own.
Are you sure your repository entry is still mapping to your custom SCM?
In 1.0, we accidentally left out the database entry for the ClearCase SCM,
and added it back. When you did the rb-site upgrade, it probably replaced
you
On Wednesday 12 August 2009 22:55:44 Christian Hammond wrote:
> Given that this error has been seen on both yours and ClearCase, it's
> possible it's somewhere internal to Review Board.
>
> Try this... Edit reviewboard/webapi/json.py, scroll down to the new_diff
> function, and locate the "except
Given that this error has been seen on both yours and ClearCase, it's
possible it's somewhere internal to Review Board.
Try this... Edit reviewboard/webapi/json.py, scroll down to the new_diff
function, and locate the "except Exception, e:" line.
Remove that whole block for that exception (includ
Hello Christian,
On Wednesday 12 August 2009 22:25:03 Christian Hammond wrote:
> There's another thread on this problem as well. Are you using ClearCase?
no, this happens with a proprietary SCM, for which I added support to RB and
post-review. So, I cannot rule out that my scm implementation is
I think the person who contributed ClearCase support on the server expected
that the repository would be locally checked out with the path given. We'll
certainly take a patch to use cleartool to fix this.
We don't have access to ClearCase, so we can't do a lot of testing
ourselves.
Christian
--
On Wed, Aug 12, 2009 at 7:25 AM, gbjbaanb wrote:
> 4. LDAP... I don't know python, so I can't help much. The idea behind
> the proxy user is that you log on as that user and perform a search
> for the user you want to log on as. If that succeeds, you use the same
> connection to bind as the user
Hi Philipp,
We certainly should document this better. I'd also like to expand the UI so
that it will you show when you're making a comment what lines were selected,
and allow you to change this while the dialog is up in such a way where it's
obvious that you can do this.
I'll definitely take a do
There's another thread on this problem as well. Are you using ClearCase?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.review-board.org
VMware, Inc. - http://www.vmware.com
On Wed, Aug 12, 2009 at 11:22 AM, Thilo-Alexander Ginkel
wrote:
>
> Hello everybody,
>
Glad you got it working!
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.review-board.org
VMware, Inc. - http://www.vmware.com
On Wed, Aug 12, 2009 at 5:23 AM, Geetanjali wrote:
>
> I could finally resolve the issue and get RB running :)
> pysvn was crashing as
Hi Isaac,
There's on up-to-date schedules available. We don't have a timeline for 2.0
yet, and are still not 100% sure whta's going to make it into 2.0 and what's
going to go into a future release.
A rough timeline is as follows:
* Review Board 1.1 will enter beta cycle probably in about 2 month
Hi,
I wonder how reviewboard fetches file versions from ClearCase. Now I
have strange error from /api/json/reviewrequests/74/diff/new/:
{"fields": {"path": ["cat: cat: /usr/cc_storage/unix_STREAM/.../
myjava.sql@@/main/STREAM/2: No such file or directory\n"]}, "stat":
"fail", "err": {"msg": "One
Hello everybody,
since upgrading from 1.0rc2 to 1.0.1 I have trouble posting reviews to
RB using a custom post-review implementation. The problem is that the
JSON response does not contain too many error details, just:
{"fields": {"path": ["substring not found"]}, "stat": "fail", "err":
{"msg":
Hi Nathan,
On Tue, Aug 11, 2009 at 19:24, Thilo-Alexander Ginkel wrote:
>> I just uploaded my patch to http://reviews.review-board.org/r/938/.
>
> Thanks! I will try your changes once I have updated my RB installation
> to a current version.
just a brief update: I tried your patch and it works l
thanks.
1. vhost: I'll have a play and see if I can fix it, if so I'll send
you a patch.
2. Lucene: I thought it had python bindings already, but I can't find
much info on the web. I may have a look at converting the perl or php
bindings to python when I have some time.
3.egg cache, I used the
On Aug 4, 9:27 pm, Christian Hammond wrote:
> Hi,
>
> On Wed, Jul 29, 2009 at 3:58 AM, gbjbaanb wrote:
>
> > Hi everyone.
>
> > I'm a very new user of ReviewBoard, I've just set it up, and as you
> > asked for information on how I intend to use it, and suggestion for
> > improvement... I'd tho
I might have missed it, but I can't seem to find a roadmap on your web
site. Is there a planned timeline for the various releases? I am anxiously
waiting for some of the features coming in 2.0. Specifically, issue 421 on
the bug tracking list. My users never close their review requests without
Hi Scott,
That's exactly the functionality I was looking for. Great! Now even my
review request pages provide a good overview. :-)
It would be helpful to underline this feature in the documentation /
user guide / Commenting on Lines:
Commenting on Lines
To co
I could finally resolve the issue and get RB running :)
pysvn was crashing as I was using an older version of subversion
client. After upgrading it to 1.4.6 and rebuilding pysvn, I am able to
work with reviewboard.
Thanks for the quick responses.
Regards,
Geetanjali
On Aug 11, 12:26 pm, Chris
26 matches
Mail list logo
