RBTools Ticket #4968: How to find 'movedFile' for Perforce shelved changes

2022-04-21 Thread Kevin Masssey
--
To reply, visit https://hellosplat.com/s/beanbag/tickets/4968/
--

New ticket #4968 by masseyk
For Beanbag, Inc. > RBTools

Status: New
Tags: Priority:Medium, Type:Enhancement


--
How to find 'movedFile' for Perforce shelved changes
==

This is just an FYI communication to share knowledge. I noticed in RBTools 
source the following comment:
 
# XXX: fstat *ought* to work, but Perforce doesn't supply the movedFile
# field in fstat (or apparently anywhere else) when a change is
# shelved. For now, _diff_pending will avoid calling this method at all
# for shelved changes, and instead treat them as deletes and adds.
 
This is possible, though, if you use the Perforce client name associated with 
the shelved change. For example, here's a shelved change that contains a moved 
file and is associated with client "masseyk_priv":

$ p4 changes -umasseyk -sshelved -m1
Change 2464690 on 2022/04/19 by masseyk@masseyk_priv *pending* 'Test Testing 
Done:  Bug Number:'

If I run fstat within another client, I don't get movedFile:

$ p4 client -o | grep '^Client:'
Client: masseyk_build-vmshared
$ p4 fstat -T depotFile,movedFile 
//depot/Priv/masseyk/manifest-test4/text-2-move@=2464690
... depotFile //depot/Priv/masseyk/manifest-test4/text-2-move

But if I specify client "massey_priv" in this command, I do:

$ p4 -c masseyk_priv fstat -T depotFile,movedFile 
//depot/Priv/masseyk/manifest-test4/text-2-move@=2464690
... depotFile //depot/Priv/masseyk/manifest-test4/text-2-move
... movedFile //depot/Priv/masseyk/manifest-test4/text-2

(I don't know why Perforce works this way.)

For the record, here's my Perforce info:

$ p4 info
User name: masseyk
Client name: masseyk_build-vmshared
Client host: ubuntu
Client root: /s/vmshared/clients/build
Current directory: /s/vmshared/clients/build/apps/lib/build/rbutils
Peer address: 10.118.252.166:33142
Client address: 10.21.243.247
Server address: perforce-releng.eng.vmware.com:1850
Server root: /p4d/perforce-releng_1850
Server date: 2022/04/21 06:28:15 -0700 PDT
Server uptime: 4323:04:10
Server version: P4D/LINUX26X86_64/2020.2/2179691 (2021/09/02)
ServerID: perforce-releng_1850
Server services: standard
Proxy address: bos2-prd-rdev-p4p001a.eng.vmware.com:1850
Proxy version: P4P/LINUX26X86_64/2020.2/2112800 (2021/04/08)
Server license: Vmware, Inc. 4823 users (support ends 2022/05/19) (expires 
2022/05/19) 
Server license-ip: 127.0.0.1
Case Handling: sensitive


--

-- 
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/reviewboard-issues/20220421133049.30829.25162%40ip-10-1-54-209.ec2.internal.


Reviewboard Git binary support

2020-04-20 Thread kevin fortinet
Hi,

I'm using Reviewboard 2.5.18 and rbtools 1.0.3. I've noticed rbt patch/land 
would always fail if there's a binary in the diff.

Steps:

   1. Create a commit with binary and text change. then post it to 
   reviewboard
   2. On a clean clone, rbt patch .

I am wondering whether reviewboard supports git binary, and if it doesn't, 
is there a way to avoid skip patching the binaries but to finish with the 
text changes?

kevin@kevin-OptiPlex-7020:~/repo/fac$ rbt patch --debug 60122 
>>> RBTools 1.0.3
>>> Python 2.7.12 (default, Oct  8 2019, 14:14:10) 
[GCC 5.4.0 20160609]
>>> Running on Linux-4.15.0-91-generic-x86_64-with-Ubuntu-16.04-xenial
>>> Home = /home/kevin
>>> Current directory = /home/kevin/repo/fac
>>> Command line: rbt patch --debug 60122
>>> Running: tf vc help
>>> Checking for a Subversion repository...
>>> Running: svn --non-interactive info
>>> Command exited with rc 1: [u'svn', u'--non-interactive', u'info']
>>> Checking for a Git repository...
>>> Running: git rev-parse --git-dir
>>> Running: git config core.bare
>>> Running: git rev-parse --show-toplevel
>>> Running: git symbolic-ref -q HEAD
>>> Running: git config --get branch.master.merge
>>> Running: git config --get branch.master.remote
>>> Running: git config --get remote.origin.url
>>> Repository info: Path: g...@git.corp.abc.com:fac/fortiauthenticator.git, 
Base path: , Supports changesets: False
>>> Checking for a Mercurial repository...
>>> Unable to execute "hg --help": skipping Mercurial
>>> Checking for a CVS repository...
>>> Unable to execute "cvs": skipping CVS
>>> Checking for a Perforce repository...
>>> Unable to execute "p4 help": skipping Perforce
>>> Checking for a Plastic repository...
>>> Unable to execute "cm version": skipping Plastic
>>> Checking for a ClearCase repository...
>>> Unable to execute "cleartool help": skipping ClearCase
>>> Checking for a Bazaar repository...
>>> Unable to execute "bzr help": skipping Bazaar
>>> Checking for a Team Foundation Server repository...
>>> Unable to execute "tf help": skipping TFS
>>> Making HTTP GET request to http://reviewboard-test.corp.abc.com/api/
>>> Making HTTP GET request to https://reviewboard-test.corp.abc
.com/api/review-requests/60122/diffs/
>>> Cached response for HTTP GET 
>>> https://reviewboard-test.corp.abc.com/api/review-requests/60122/diffs/ 
expired and was modified
>>> Making HTTP GET request to https://reviewboard-test.corp.abc
.com/api/review-requests/60122/diffs/2/
>>> Cached response for HTTP GET 
>>> https://reviewboard-test.corp.abc.com/api/review-requests/60122/diffs/2/ 
expired and was not modified
>>> Making HTTP GET request to https://reviewboard-test.corp.abc
.com/api/review-requests/60122/diffs/2/
>>> Cached response for HTTP GET 
>>> https://reviewboard-test.corp.abc.com/api/review-requests/60122/diffs/2/ 
expired and was not modified
>>> Running: git status --porcelain --untracked-files=no 
--ignore-submodules=dirty
Patch is being applied from request 60122 with diff revision 2.
>>> Running: git apply -3 /tmp/rbtools.qYiOC7
>>> Command exited with rc 1: [u'git', u'apply', u'-3', 
u'/tmp/rbtools.qYiOC7']
error: missing binary patch data for 'cp'
error: binary patch does not apply to 'cp'
Falling back to three-way merge...
error: missing binary patch data for 'cp'
error: binary patch does not apply to 'cp'
error: cp: patch does not apply
---

error: missing binary patch data for 'cp'
error: binary patch does not apply to 'cp'
Falling back to three-way merge...
error: missing binary patch data for 'cp'
error: binary patch does not apply to 'cp'
error: cp: patch does not apply

Traceback (most recent call last):
  File "/usr/local/bin/rbt", line 10, in 
sys.exit(main())
  File "/usr/local/lib/python2.7/dist-packages/rbtools/commands/main.py", 
line 120, in main
command.run_from_argv([RB_MAIN, command_name] + args)
  File 
"/usr/local/lib/python2.7/dist-packages/rbtools/commands/__init__.py", line 
725, in run_from_argv
exit_code = self.main(*args) or 0
  File "/usr/local/lib/python2.7/dist-packages/rbtools/commands/patch.py", 
line 203, in main
revert=self.options.revert_patch)
  File "/usr/local/lib/python2.7/dist-packages/rbtools/commands/patch.py", 
line 119, in apply_patch
'Unable to apply the patch. The patch may be invalid, or '
rbtools.commands.CommandError: Unable to apply the patch. The patch may be 
invalid, or there may be conflicts that could not be resolved.



-- 
Superchar

Review Board Ticket #4842: post a review request by RBTool client and then I can't review any data details on reviewboard server

2019-08-28 Thread Kevin Jiang
--
To reply, visit https://hellosplat.com/s/beanbag/tickets/4842/
--

New ticket #4842 by kevin.jiang
For Beanbag, Inc. > Review Board

Status: New
Tags: Priority:Medium, Type:Defect

File attachments:

 * reviewboard error.png
   

 * reviewboard error2.png
   



--
 post a review request by RBTool client and then I can't review any data 
details on reviewboard server
==

# What version are you running?
3.0.14 (reviewboard)

1.0.2 (RBTool client)

# What's the URL of the page containing the problem?
http://reviewboard..com:8000/r/1/diff/1/

the page show error:
patching file SettingServerControllerTest.java-new (read from 
SettingServerControllerTest.java)
Hunk #1 FAILED at 68.
1 out of 1 hunk FAILED -- saving rejects to file 
SettingServerControllerTest.java.rej


# What steps will reproduce the problem?
1. client : rbt post
2. server :open url http://reviewboard..com:8000/r/1/diff/
2. then youcan see it
3. 


# What is the expected output? What do you see instead?


# What operating system are you using? What browser?
chrome

# Please provide any additional information below.
i just set repo info by reviewboard;

Repository type: git
Path: http://gitlab.xxx.com/xxx/xx/xx.git
Mirror: http://gitlab.xxx.com/xxx/xx/xx.git
Raw file URL mask: 
http://gitlab.xxx.com/xxx/xx/xx.git;a=blob_plain;f=;h=



--

-- 
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/reviewboard-issues/20190829051254.20548.66931%40ip-10-1-54-209.ec2.internal.


Re: Review Board Ticket #4699: Wrong filtering of opcodes for an interdiff

2019-04-29 Thread Kevin Yu
--
To reply, visit https://hellosplat.com/s/beanbag/tickets/4699/
--

New update by alexG
For Beanbag, Inc. > Review Board > Ticket #4699


Reply:

Was this back ported to 2.5 by any chance?

-- 
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at https://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.


RBTools Ticket #4804: rbt patch doesn't work with svn 1.10 and above

2019-03-15 Thread Kevin Yu
--
To reply, visit https://hellosplat.com/s/beanbag/tickets/4804/
--

New ticket #4804 by samsun387
For Beanbag, Inc. > RBTools

Status: New
Tags: Priority:Medium, Type:Defect


--
rbt patch doesn't work with svn 1.10 and above
==

# What version are you running?


# What steps will reproduce the problem?
1. Install rbtools
2. Install subversion 1.10.3 or 1.11
3. rbt patch 


# What is the expected output? What do you see instead?
rbt should patch the diff

# What operating system are you using?
Ubuntu 16.04


# Attach the debug out from the command.

```
root@c082ae5714ae:/src_code/test_2/trunk# rbt patch 41661
WARNING: Unable to parse SVN client version triple from "svn: warning: cannot 
set LC_CTYPE locale
svn: warning: environment variable LC_ALL is en_US.UTF-8
svn: warning: please check that your locale name is correct
1.10.3". Assuming version 0.0.0.
Patch is being applied from request 41661 with diff revision 1.
CRITICAL: Using "rbt patch" with the SVN backend requires at least svn 1.7.0
```


# Please provide any additional information below.


--

-- 
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at https://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.


Re: Review Board Ticket #4750: SVN 1.10 binary file not showing up DIFF file list

2019-03-11 Thread Kevin Yu
--
To reply, visit https://hellosplat.com/s/beanbag/tickets/4750/
--

New update by totoroliu
For Beanbag, Inc. > Review Board > Ticket #4750


Reply:

We are encountering this issue as well. Basically any user with SVN 1.10 
would be affected by this.

-- 
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at https://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.


Reviewboard SVN 1.10 binary file detection not working

2018-09-27 Thread Kevin Yu
Hi,

I noticed when I upgraded Subversion to 1.10, Reviewboard stopped 
displaying binary files on Diff GUI.

   Index: /abc/branches/3.x/3.0/trunk/cooked/basepkgs/abc.pkg


  ===

  Cannot display: file marked as a binary type.

  svn:mime-type = application/octet-stream

  

  Property changes on:
cooked/basepkgs/abc.pkg

  ___

  Added: svn:mime-type

  ## -0,0 +1 ##

  +application/octet-stream

  \ No newline at end of property



>From SVN 1.9 "rbt diff" output, I have:



Index: /abc/branches/3.x/3.0/trunk/cooked/basepkgs/abc.pkg

  ===

  Cannot display: file marked as a binary type.

  svn:mime-type = application/octet-stream

  Index:
/abc/branches/3.x/3.0/trunk/cooked/basepkgs/abc.pkg

  ===

  ---
/abc/branches/3.x/3.0/trunk/cooked/basepkgs/abc.pkg (nonexistent)+++
/abc/branches/3.x/3.0/trunk/cooked/basepkgs/abc.pkg (working copy)

  

  Property changes on:
cooked/basepkgs/abc.pkg

  ___

  Added: svn:mime-type

  ## -0,0 +1 ##

  +application/octet-stream

  \ No newline at end of property

In this case, abc.pkg would not show up on the Diff GUI. I suspect it has 
to do with the binary format change in diff in SVN 1.10.2.

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: HTTP 403 when using api review_group_users (using admin user)

2018-07-04 Thread Kevin Yu
Hi Christian,

After more debugging, turns out own in house extension created this 
problem. We added some security check to restrict only the api that we use.

Thanks,
Kevin
On Wednesday, July 4, 2018 at 12:24:00 PM UTC-7, Christian Hammond wrote:
>
> Hi Kevin,
>
> What are the settings on the group? Is it an invite-only group?
>
> Can you re-run the query and then check reviewboard.log on the server for 
> access warnings?
>
> Christian
>
>
> On Wed, Jul 4, 2018 at 10:47 AM Kevin Yu > 
> wrote:
>
>> Hi,
>>
>> I'm having issues using the review_group_users api. When I called the 
>> api as admin users, I'm getting http 403 (permission denied) back. 
>>
>> This is the api I'm referring to 
>> https://www.reviewboard.org/docs/manual/2.5/webapi/2.0/resources/review-group-user-list/#example_application/vnd.reviewboard.org.review-group-users+json
>>
>> The way i call it is
>> self.client = RBClient(url, username=username, password=password)
>> self.client.get_root().get_review_group_users(group_name=group_name)
>>
>> I also tried hitting the url 
>> ${reviewboard_url}//api/groups/{group_name}/users/ 
>> and same result.
>>
>> My reviewboard version is 2.5.17
>>
>> -- 
>> Supercharge your Review Board with Power Pack: 
>> https://www.reviewboard.org/powerpack/
>> Want us to host Review Board for you? Check out RBCommons: 
>> https://rbcommons.com/
>> Happy user? Let us know! https://www.reviewboard.org/users/
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "Review Board Community" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to reviewboard...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> Christian Hammond
> President/CEO of Beanbag <https://www.beanbaginc.com/>
> Makers of Review Board <https://www.reviewboard.org/>
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


HTTP 403 when using api review_group_users (using admin user)

2018-07-04 Thread Kevin Yu
Hi,

I'm having issues using the review_group_users api. When I called the api 
as admin users, I'm getting http 403 (permission denied) back. 

This is the api I'm referring 
to 
https://www.reviewboard.org/docs/manual/2.5/webapi/2.0/resources/review-group-user-list/#example_application/vnd.reviewboard.org.review-group-users+json

The way i call it is
self.client = RBClient(url, username=username, password=password)
self.client.get_root().get_review_group_users(group_name=group_name)

I also tried hitting the url ${reviewboard_url}//api/groups/{group_name}/users/ 
and same result.

My reviewboard version is 2.5.17

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Error after High Sierra upgrade

2017-10-06 Thread Kevin Brock
After upgrading my macOS system to 10.13, and upgrading RBTools to 0.7.10, 
 I started seeing a certificate error when I run rbt post.

ERROR: Could not reach the Review Board server at 
https://reviewboard.yourcompany.com: [SSL: CERTIFICATE_VERIFY_FAILED] 
certificate verify failed (_ssl.c:590)

I saw in various discussion groups that there were similar errors a while 
back related to the upgrade from Python 2.6 to Python 2.7, and Apple 
upgraded to 2.7 on High Sierra, but those problems were supposed to be 
fixed several versions of RBTools ago, weren't they?  I saw one message 
saying that the fix would be in 0.7.3...

The relevant certificate *is* self-signed, but is marked as trusted for all 
uses in Keychain Access.  Everything was working fine before the upgrade.

Is there a fix known for this problem?

Kev





-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: How long does Reviewboard session alive

2017-09-18 Thread Kevin Yu
Hi Christian,

I tried to delete my post before you see it but i guess it was too late :) 
Sorry about that.

I noticed it's my extension that caused the issue. I tried disable 
extension and it works flawlessly. 

In Django, there's another setting called SESSION_SAVE_EVERY_REQUEST, which 
extends the session based on last activity. Do you know if Reviewboard 
supports that?

Thanks,
Kevin
On Monday, September 18, 2017 at 5:30:43 PM UTC-7, Christian Hammond wrote:
>
> Hi Kevin,
>
> I'm not able to reproduce this. Can you send more of the stack trace? I 
> don't need to see any of the expanded "Local vars" (at least not yet), but 
> need to see every line of code being shown in the trace.
>
> Thanks,
>
> Christian
>
> On Mon, Sep 18, 2017 at 5:24 PM, Kevin Yu <sams...@gmail.com 
> > wrote:
>
>>
>> <https://lh3.googleusercontent.com/-Dh7WFQhHhyw/WcBh0i_j5SI/Dw0/WYNTQGOxjXEx5ERFt_fgmGHXZcViKkqzQCLcBGAs/s1600/exception.bmp>
>>
>>  Christian,
>>
>> Thanks for sharing. Looks like that's the Django native setting. I've 
>> tried it and it does expires the session after specified time. However, 
>> once the session expires, instead of showing the login page, it throws an 
>> exception:
>>
>>
>> <https://lh3.googleusercontent.com/-Dh7WFQhHhyw/WcBh0i_j5SI/Dw0/WYNTQGOxjXEx5ERFt_fgmGHXZcViKkqzQCLcBGAs/s1600/exception.bmp>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On Wednesday, September 13, 2017 at 2:32:13 PM UTC-7, Christian Hammond 
>> wrote:
>>>
>>> Hi Kevin,
>>>
>>> Sessions default to lasting 1 year. You can customize this by adding the 
>>> SESSION_COOKIE_AGE setting to your $sitedir/conf/settings_local.py file, 
>>> like:
>>>
>>>
>>> SESSION_COOKIE_AGE = 365 * 24 * 60 * 60  # 1 year
>>>
>>>
>>> Christian
>>>
>>> On Wed, Sep 13, 2017 at 1:37 PM, Kevin Yu <sams...@gmail.com> wrote:
>>>
>>>> I have a question about Reviewboard login session. I've noticed i never 
>>>> have to login again after inactive for a long period of time. Just 
>>>> wondering how long would the session expire, if at all?
>>>>
>>>> Is there a setting to set this?
>>>>
>>>> -- 
>>>> Supercharge your Review Board with Power Pack: 
>>>> https://www.reviewboard.org/powerpack/
>>>> Want us to host Review Board for you? Check out RBCommons: 
>>>> https://rbcommons.com/
>>>> Happy user? Let us know! https://www.reviewboard.org/users/
>>>> --- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "reviewboard" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to reviewboard...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>>>
>>> -- 
>>> Christian Hammond
>>> President/CEO of Beanbag <https://www.beanbaginc.com/>
>>> Makers of Review Board <https://www.reviewboard.org/>
>>>
>> -- 
>> Supercharge your Review Board with Power Pack: 
>> https://www.reviewboard.org/powerpack/
>> Want us to host Review Board for you? Check out RBCommons: 
>> https://rbcommons.com/
>> Happy user? Let us know! https://www.reviewboard.org/users/
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "reviewboard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to reviewboard...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Christian Hammond
> President/CEO of Beanbag <https://www.beanbaginc.com/>
> Makers of Review Board <https://www.reviewboard.org/>
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: How long does Reviewboard session alive

2017-09-18 Thread Kevin Yu


<https://lh3.googleusercontent.com/-Dh7WFQhHhyw/WcBh0i_j5SI/Dw0/WYNTQGOxjXEx5ERFt_fgmGHXZcViKkqzQCLcBGAs/s1600/exception.bmp>

 Christian,

Thanks for sharing. Looks like that's the Django native setting. I've tried 
it and it does expires the session after specified time. However, once the 
session expires, instead of showing the login page, it throws an exception:

<https://lh3.googleusercontent.com/-Dh7WFQhHhyw/WcBh0i_j5SI/Dw0/WYNTQGOxjXEx5ERFt_fgmGHXZcViKkqzQCLcBGAs/s1600/exception.bmp>














On Wednesday, September 13, 2017 at 2:32:13 PM UTC-7, Christian Hammond 
wrote:
>
> Hi Kevin,
>
> Sessions default to lasting 1 year. You can customize this by adding the 
> SESSION_COOKIE_AGE setting to your $sitedir/conf/settings_local.py file, 
> like:
>
>
> SESSION_COOKIE_AGE = 365 * 24 * 60 * 60  # 1 year
>
>
> Christian
>
> On Wed, Sep 13, 2017 at 1:37 PM, Kevin Yu <sams...@gmail.com 
> > wrote:
>
>> I have a question about Reviewboard login session. I've noticed i never 
>> have to login again after inactive for a long period of time. Just 
>> wondering how long would the session expire, if at all?
>>
>> Is there a setting to set this?
>>
>> -- 
>> Supercharge your Review Board with Power Pack: 
>> https://www.reviewboard.org/powerpack/
>> Want us to host Review Board for you? Check out RBCommons: 
>> https://rbcommons.com/
>> Happy user? Let us know! https://www.reviewboard.org/users/
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "reviewboard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to reviewboard...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Christian Hammond
> President/CEO of Beanbag <https://www.beanbaginc.com/>
> Makers of Review Board <https://www.reviewboard.org/>
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


How long does Reviewboard session alive

2017-09-13 Thread Kevin Yu
I have a question about Reviewboard login session. I've noticed i never 
have to login again after inactive for a long period of time. Just 
wondering how long would the session expire, if at all?

Is there a setting to set this?

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Review Board Ticket #4577: IE exception happens on screen resolution 1366* 768

2017-08-18 Thread Kevin Yu
--
To reply, visit https://hellosplat.com/s/beanbag/tickets/4577/
--

New update by samsun387
For Beanbag, Inc. > Review Board > Ticket #4577


Reply:

I want to update the description but somehow there's no way to do it. 

Anyway, forget about scrollbar. Basically if you open the 
/dashboard/?view=outgoing under IE 11 with the specified resolution, there will 
be exception thrown.

-- 
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at https://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.


Re: Review Board Ticket #4577: IE exception happens on screen resolution 1366* 768

2017-08-18 Thread Kevin Yu
--
To reply, visit https://hellosplat.com/s/beanbag/tickets/4577/
--

New update by samsun387
For Beanbag, Inc. > Review Board > Ticket #4577


Summary:
- Scrollbar does not work on 
+ IE exception happens on screen resolution 1366* 768

-- 
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at https://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.


Review Board Ticket #4577: Scrollbar does not work on

2017-08-18 Thread Kevin Yu
--
To reply, visit https://hellosplat.com/s/beanbag/tickets/4577/
--

New ticket #4577 by samsun387
For Beanbag, Inc. > Review Board

Status: New
Tags: Priority:Medium, Type:Defect

File attachments:

 * IE Browser Issue.png
   



--
Scrollbar does not work on 
==

# What version are you running?
2.5.12. This issue happens on IE11

# What's the URL of the page containing the problem?
/r/

# What steps will reproduce the problem?
1. Open reviewboard with screen resolution 1366* 768 (Pretty common for 15 
inches laptop). browser zoom percentage is 100%
2. try to press up/down key to scroll up and down


# What is the expected output? What do you see instead?
Scrollbar should move. Instead it freeze and there's a exception on IE.

# What operating system are you using? What browser?
Windows 10 and IE 11.

# Please provide any additional information below.


--

-- 
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at https://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.


Re: Upgrade to ReviewBoard 2.5.13.1

2017-07-07 Thread Kevin Yu
We recently performed the same operation. We also backup the site folder 
under /var/www and /usr/local/lib/python2.7/dist-packages

On Thursday, July 6, 2017 at 8:34:20 PM UTC-7, harish varadarajan wrote:
>
> Hi,
>
> We intend to upgrade to RB 2.5.13.1 (from 2.5.6.1) and below is the list 
> of steps that is intended to be followed on the day of migration.
> Please help review and let know if there is anything specific that needs 
> to be accounted for the upgrade.
>
> (1) Create sql backup, using mysqldump.
> (2) Create backup of site directory.
> (3) easy_install -U ReviewBoard==2.5.13.1
> (4) rb-site upgrade $site_dir
> (5) Validation of the server and checks for extensions.
>
> Thanks.
>
> --
> Harish
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Review Board Ticket #4450: ReviewRequest.last_review_activity_timestamp should be exposed in the API

2017-06-23 Thread Kevin Yu
--
To reply, visit https://hellosplat.com/s/beanbag/tickets/4450/
--

New update by samsun387
For Beanbag, Inc. > Review Board > Ticket #4450


Reply:

Hi,

Just following up on this. Since it's marked as an easy fix, is there a 
targetted release for it at the moment?

-- 
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at https://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.


Re: Cannot install extension after upgrading from 2.5.6.1 to 2.5.12 - lessc not found!

2017-06-14 Thread Kevin Yu
;>>> PIPELINE_LESS_BINARY1 = 
>>>>>> /src2/rb-extension-pack/fortinet/build/node_modules/less/bin/lessc
>>>>>> PIPELINE_UGLIFYJS_BINARY1 = 
>>>>>> /src2/rb-extension-pack/fortinet/build/node_modules/uglifyjs/bin/uglifyjs
>>>>>>
>>>>>>
>>>>>> On Monday, June 12, 2017 at 5:51:13 PM UTC-7, Alexander Galperin 
>>>>>> wrote:
>>>>>>>
>>>>>>> Set print 
>>>>>>> in 
>>>>>>> /usr/local/lib/python2.7/dist-packages/pipeline/compressors/uglifyjs.py:
>>>>>>> class UglifyJSCompressor(SubProcessCompressor):
>>>>>>> def compress_js(self, js):
>>>>>>> *print 'PIPELINE_SETTING_UGLIFYJS_BINARY = 
>>>>>>> {}'.format(settings.PIPELINE_UGLIFYJS_BINARY)*
>>>>>>> command = '%s %s' % (settings.PIPELINE_UGLIFYJS_BINARY, 
>>>>>>> settings.PIPELINE_UGLIFYJS_ARGUMENTS)
>>>>>>> if self.verbose:
>>>>>>> command += ' --verbose'
>>>>>>> return self.execute_command(command, js)
>>>>>>> output:
>>>>>>> PIPELINE_SETTING_UGLIFYJS_BINARY = /usr/local/lib/python2.7/dist-
>>>>>>> packages/ReviewBoard-2.5.12.dev0-py2.7.egg/reviewboard/../
>>>>>>> node_modules/uglifyjs/bin/uglifyjs
>>>>>>>  And it takes from 'settings', which probably is wrong
>>>>>>>
>>>>>>> I will try to stop in call_command
>>>>>>>
>>>>>>>
>>>>>>> On Monday, June 12, 2017 at 5:37:29 PM UTC-7, Christian Hammond 
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Can you also try placing debugging output right before the 
>>>>>>>> "call_command('collectstatic', ...)" command in _build_static_media?
>>>>>>>>
>>>>>>>> Along with this, try printing `command` in 
>>>>>>>> pipeline/compilers/less.py (pipeline will be another module in 
>>>>>>>> site-packages somewhere, perhaps under a django-pipeline-* directory).
>>>>>>>>
>>>>>>>> Christian
>>>>>>>>
>>>>>>>> On Mon, Jun 12, 2017 at 5:22 PM, Alexander Galperin <
>>>>>>>> galperin@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> I've put some print in packaging.py to help debugging. Here's what 
>>>>>>>>> I have changed:
>>>>>>>>>  def install_pipeline_deps(self, extension, css_bundles, 
>>>>>>>>> js_bundles):
>>>>>>>>> ...
>>>>>>>>> ...
>>>>>>>>> with open(package_file, 'w') as fp:
>>>>>>>>> fp.write(json.dumps(
>>>>>>>>> {
>>>>>>>>> 'name': '%s-extension' % 
>>>>>>>>> os.path.basename(os.getcwd()),
>>>>>>>>> 'private': 'true',
>>>>>>>>> 'devDependencies': {},
>>>>>>>>> 'dependencies': dependencies,
>>>>>>>>> },
>>>>>>>>> indent=2))
>>>>>>>>>
>>>>>>>>> old_cwd = os.getcwd()
>>>>>>>>> os.chdir(build_dir)
>>>>>>>>> *print 'PIPELINE_LESS_BINARY = 
>>>>>>>>> {}'.format(pipeline_settings.LESS_BINARY)*
>>>>>>>>> *print 'PIPELINE_UGLIFYJS_BINARY = 
>>>>>>>>> {}'.format(pipeline_settings.UGLIFYJS_BINARY)*
>>>>>>>>> self.npm_install()
>>>>>>>>>
>>>>>>>>> And the output is:
>>>>>>>>> PIPELINE_LESS_BINARY = /src2/rb-extension-pack/fortinet/build/
>>>>>>>>> node_modules/less/bin/lessc
>>>>>>>>> PIPELINE_UGLIFYJS_BINARY = /src2/rb-extension-pack/fortinet/build/
>>>>>>>>> node_modules/uglifyjs/bin/uglifyjs
>>>>>>>>>
>>>>>>>>> Also build/node_modules.. c

Re: Cannot install extension after upgrading from 2.5.6.1 to 2.5.12 - lessc not found!

2017-06-12 Thread Kevin Yu
Hi Christian,

Thanks for trying out. I also did some debugging to see if I can find any 
information. I added some print in the settings.py  

PIPELINE_LESS_BINARY = os.path.join(NODE_PATH, 'less', 'bin', 'lessc')
PIPELINE_UGLIFYJS_BINARY = os.path.join(NODE_PATH, 'uglifyjs', 'bin',
'uglifyjs')
print 'PIPELINE_UGLIFYJS_BINARY = {}'.format(PIPELINE_UGLIFYJS_BINARY)
print 'PIPELINE_LESS_BINARY = {}'.format(PIPELINE_LESS_BINARY)



And this is what I see in the log:

[Mon Jun 12 14:47:50.821618 2017] [:error] [pid 12918:tid 140227234481920] 
PIPELINE_UGLIFYJS_BINARY = 
/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.5.12-py2.7.egg/reviewboard/../node_modules/uglifyjs/bin/uglifyjs
[Mon Jun 12 14:47:50.821692 2017] [:error] [pid 12918:tid 140227234481920] 
PIPELINE_LESS_BINARY = 
/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.5.12-py2.7.egg/reviewboard/../node_modules/less/bin/lessc



On Saturday, June 10, 2017 at 1:43:26 AM UTC-7, Christian Hammond wrote:
>
> Right. We override this though in djblets/extensions/packaging.py in 
> install_pipeline_deps(). We compute the path to the extension's 
> node_modules and its lessc, and we set that in settings.
>
> I tested locally and it's performing as expected for me. Review Board's 
> lessc isn't being used, but the extension's is. So something's going wrong 
> here with the paths.
>
> How comfortable are you debugging Python? I'm curious as to whether 
> pipeline_settings.LESS_BINARY in install_pipeline_deps() is being correctly 
> set.
>
> Christian
>
> On Fri, Jun 9, 2017 at 5:51 PM, Kevin Yu <sams...@gmail.com > 
> wrote:
>
>> Looks like the path to the npm_modules are prepopulated based on the 
>> following code in settings.py:
>> # Static media setup
>> if RUNNING_TEST:
>>PIPELINE_COMPILERS = []
>> else:
>>PIPELINE_COMPILERS = [
>>'djblets.pipeline.compilers.es6.ES6Compiler',
>>'djblets.pipeline.compilers.less.LessCompiler',
>>]
>>
>> NODE_PATH = os.path.join(REVIEWBOARD_ROOT, '..', 'node_modules')
>>
>>
>>
>> On Friday, June 9, 2017 at 5:44:51 PM UTC-7, Kevin Yu wrote:
>>>
>>> Thanks Christian for the quick reply! much appreciated.
>>>
>>> It was installed using easy_install under Ubuntu.
>>>
>>> On Friday, June 9, 2017 at 5:38:11 PM UTC-7, Christian Hammond wrote:
>>>>
>>>> Hi Kevin,
>>>>
>>>> I actually don't believe this is related in this case. It looks like 
>>>> the extension packaging stage is trying to locate the lessc path relative 
>>>> to Review Board, which is not correct. It should be locating it from the 
>>>> extension package. It sets the path prior to building the extension to the 
>>>> place in your tree, which, based on that output, should be populated...
>>>>
>>>> I have to run right now, but let me play around with this when I get 
>>>> back and see if I can reproduce this.
>>>>
>>>> In the meantime, how do you install Review Board? Are you using 
>>>> easy_install or yum?
>>>>
>>>> Christian
>>>>
>>>> On Fri, Jun 9, 2017 at 5:34 PM, Kevin Yu <sams...@gmail.com> wrote:
>>>>
>>>>> I just saw on 
>>>>> https://www.reviewboard.org/docs/manual/dev/extending/extensions/static-files/,
>>>>>  
>>>>> it says
>>>>>
>>>>> Static bundles are packaged along with your extension automatically. 
>>>>> You don’t have to do anything special. You will, however, need some 
>>>>> node.js <https://nodejs.org/> dependencies in order to package static 
>>>>> media bundles.
>>>>>
>>>>> *If you’re running Review Board 2.5.7+, these dependencies will be 
>>>>> installed for you when you begin to build the package.*
>>>>>
>>>>> *If you’re running an older version, you will need to manually install 
>>>>> them yourself. First, make sure you have a modern version of node.js 
>>>>> installed and then run:*
>>>>>
>>>>> $ sudo npm install -g less uglifyjs
>>>>>
>>>>> I am wondering if this is related...
>>>>>
>>>>> On Friday, June 9, 2017 at 4:41:10 PM UTC-7, Kevin Yu wrote:
>>>>>>
>>>>>> On our server, we had reviewboard core 2.5.6.1 running with our own 
>>>>>> extension. it was all fine until we recently upgraded reviewboard core 
>>>>>> to 
>>&

Re: Cannot install extension after upgrading from 2.5.6.1 to 2.5.12 - lessc not found!

2017-06-09 Thread Kevin Yu
Looks like the path to the npm_modules are prepopulated based on the 
following code in settings.py:
# Static media setup
if RUNNING_TEST:
   PIPELINE_COMPILERS = []
else:
   PIPELINE_COMPILERS = [
   'djblets.pipeline.compilers.es6.ES6Compiler',
   'djblets.pipeline.compilers.less.LessCompiler',
   ]

NODE_PATH = os.path.join(REVIEWBOARD_ROOT, '..', 'node_modules')



On Friday, June 9, 2017 at 5:44:51 PM UTC-7, Kevin Yu wrote:
>
> Thanks Christian for the quick reply! much appreciated.
>
> It was installed using easy_install under Ubuntu.
>
> On Friday, June 9, 2017 at 5:38:11 PM UTC-7, Christian Hammond wrote:
>>
>> Hi Kevin,
>>
>> I actually don't believe this is related in this case. It looks like the 
>> extension packaging stage is trying to locate the lessc path relative to 
>> Review Board, which is not correct. It should be locating it from the 
>> extension package. It sets the path prior to building the extension to the 
>> place in your tree, which, based on that output, should be populated...
>>
>> I have to run right now, but let me play around with this when I get back 
>> and see if I can reproduce this.
>>
>> In the meantime, how do you install Review Board? Are you using 
>> easy_install or yum?
>>
>> Christian
>>
>> On Fri, Jun 9, 2017 at 5:34 PM, Kevin Yu <sams...@gmail.com> wrote:
>>
>>> I just saw on 
>>> https://www.reviewboard.org/docs/manual/dev/extending/extensions/static-files/,
>>>  
>>> it says
>>>
>>> Static bundles are packaged along with your extension automatically. You 
>>> don’t have to do anything special. You will, however, need some node.js 
>>> <https://nodejs.org/> dependencies in order to package static media 
>>> bundles.
>>>
>>> *If you’re running Review Board 2.5.7+, these dependencies will be 
>>> installed for you when you begin to build the package.*
>>>
>>> *If you’re running an older version, you will need to manually install 
>>> them yourself. First, make sure you have a modern version of node.js 
>>> installed and then run:*
>>>
>>> $ sudo npm install -g less uglifyjs
>>>
>>> I am wondering if this is related...
>>>
>>> On Friday, June 9, 2017 at 4:41:10 PM UTC-7, Kevin Yu wrote:
>>>>
>>>> On our server, we had reviewboard core 2.5.6.1 running with our own 
>>>> extension. it was all fine until we recently upgraded reviewboard core to 
>>>> 2.5.12. After the upgrade, we can't run python setup.py -v build 
>>>> anymore... 
>>>> The error is as follows:
>>>> devops@Reviewboard-Test-trunk:/tmp/ReviewBoardExt$ python setup.py -v 
>>>> build
>>>> running build
>>>> running build_py
>>>> running build_static_files
>>>> Installing node packages...
>>>> npm http GET https://registry.npmjs.org/uglifyjs/2.4.10
>>>> npm http GET https://registry.npmjs.org/less/2.7.1
>>>> npm http 304 https://registry.npmjs.org/less/2.7.1
>>>> npm http 304 https://registry.npmjs.org/uglifyjs/2.4.10
>>>> npm WARN deprecated uglifyjs@2.4.10: uglifyjs is deprecated - use 
>>>> uglify-js instead.
>>>> npm WARN engine less@2.7.1: wanted: {"node":">=0.12"} (current: 
>>>> {"node":"v0.10.25","npm":"1.3.10"})
>>>> npm http GET https://registry.npmjs.org/source-map/0.1.34
>>>> npm http GET https://registry.npmjs.org/yargs
>>>> npm http GET https://registry.npmjs.org/async
>>>> npm http GET https://registry.npmjs.org/uglify-to-browserify
>>>> npm http 304 https://registry.npmjs.org/source-map/0.1.34
>>>> npm http 304 https://registry.npmjs.org/yargs
>>>> npm http 304 https://registry.npmjs.org/async
>>>> npm http 304 https://registry.npmjs.org/uglify-to-browserify
>>>> npm http GET https://registry.npmjs.org/amdefine
>>>> npm http 304 https://registry.npmjs.org/amdefine
>>>> npm http GET https://registry.npmjs.org/errno
>>>> npm http GET https://registry.npmjs.org/graceful-fs
>>>> npm http GET https://registry.npmjs.org/image-size
>>>> npm http GET https://registry.npmjs.org/mime
>>>> npm http GET https://registry.npmjs.org/mkdirp
>>>> npm http GET https://registry.npmjs.org/promise
>>>> npm http GET https://registry.npmjs.org/source-map
>>>> npm http 304 https://registry.npmjs.org/errno
>>>> npm http 304 https://registry.n

Re: Cannot install extension after upgrading from 2.5.6.1 to 2.5.12 - lessc not found!

2017-06-09 Thread Kevin Yu
I just saw 
on 
https://www.reviewboard.org/docs/manual/dev/extending/extensions/static-files/, 
it says

Static bundles are packaged along with your extension automatically. You 
don’t have to do anything special. You will, however, need some node.js 
<https://nodejs.org/> dependencies in order to package static media bundles.

*If you’re running Review Board 2.5.7+, these dependencies will be 
installed for you when you begin to build the package.*

*If you’re running an older version, you will need to manually install them 
yourself. First, make sure you have a modern version of node.js installed 
and then run:*

$ sudo npm install -g less uglifyjs

I am wondering if this is related...
On Friday, June 9, 2017 at 4:41:10 PM UTC-7, Kevin Yu wrote:
>
> On our server, we had reviewboard core 2.5.6.1 running with our own 
> extension. it was all fine until we recently upgraded reviewboard core to 
> 2.5.12. After the upgrade, we can't run python setup.py -v build anymore... 
> The error is as follows:
> devops@Reviewboard-Test-trunk:/tmp/ReviewBoardExt$ python setup.py -v build
> running build
> running build_py
> running build_static_files
> Installing node packages...
> npm http GET https://registry.npmjs.org/uglifyjs/2.4.10
> npm http GET https://registry.npmjs.org/less/2.7.1
> npm http 304 https://registry.npmjs.org/less/2.7.1
> npm http 304 https://registry.npmjs.org/uglifyjs/2.4.10
> npm WARN deprecated uglifyjs@2.4.10: uglifyjs is deprecated - use 
> uglify-js instead.
> npm WARN engine less@2.7.1: wanted: {"node":">=0.12"} (current: 
> {"node":"v0.10.25","npm":"1.3.10"})
> npm http GET https://registry.npmjs.org/source-map/0.1.34
> npm http GET https://registry.npmjs.org/yargs
> npm http GET https://registry.npmjs.org/async
> npm http GET https://registry.npmjs.org/uglify-to-browserify
> npm http 304 https://registry.npmjs.org/source-map/0.1.34
> npm http 304 https://registry.npmjs.org/yargs
> npm http 304 https://registry.npmjs.org/async
> npm http 304 https://registry.npmjs.org/uglify-to-browserify
> npm http GET https://registry.npmjs.org/amdefine
> npm http 304 https://registry.npmjs.org/amdefine
> npm http GET https://registry.npmjs.org/errno
> npm http GET https://registry.npmjs.org/graceful-fs
> npm http GET https://registry.npmjs.org/image-size
> npm http GET https://registry.npmjs.org/mime
> npm http GET https://registry.npmjs.org/mkdirp
> npm http GET https://registry.npmjs.org/promise
> npm http GET https://registry.npmjs.org/source-map
> npm http 304 https://registry.npmjs.org/errno
> npm http 304 https://registry.npmjs.org/graceful-fs
> npm http 304 https://registry.npmjs.org/image-size
> npm http 304 https://registry.npmjs.org/mime
> npm http 304 https://registry.npmjs.org/promise
> npm http 304 https://registry.npmjs.org/source-map
> npm http 304 https://registry.npmjs.org/mkdirp
> npm http GET https://registry.npmjs.org/prr
> npm http 304 https://registry.npmjs.org/prr
> npm http GET https://registry.npmjs.org/minimist/0.0.8
> npm http 304 https://registry.npmjs.org/minimist/0.0.8
> npm http GET https://registry.npmjs.org/asap
> npm http 304 https://registry.npmjs.org/asap
> uglifyjs@2.4.10 node_modules/uglifyjs
> ├── uglify-to-browserify@1.0.2
> ├── async@0.2.10
> ├── yargs@1.3.3
> └── source-map@0.1.34 (amdefine@1.0.1)
>
> less@2.7.1 node_modules/less
> ├── graceful-fs@4.1.11
> ├── mime@1.3.6
> ├── image-size@0.5.4
> ├── errno@0.1.4 (prr@0.0.0)
> ├── mkdirp@0.5.1 (minimist@0.0.8)
> ├── promise@7.1.1 (asap@2.0.5)
> └── source-map@0.5.6
> Copying '/tmp/ReviewBoardExt/fortinet/static/css/rev_req_det.less'
> Copying '/tmp/ReviewBoardExt/fortinet/static/js/views/account_handler.js'
> Copying '/tmp/ReviewBoardExt/fortinet/static/js/views/branch_builds.js'
> Copying '/tmp/ReviewBoardExt/fortinet/static/js/views/bootstrap.js'
> Copying '/tmp/ReviewBoardExt/fortinet/static/js/views/apprreqView.js'
> Copying '/tmp/ReviewBoardExt/fortinet/static/js/views/test_cvrg_rprt.js'
> Copying '/tmp/ReviewBoardExt/fortinet/static/js/views/ftnchkHoldItView.js'
> Copying 
> '/tmp/ReviewBoardExt/fortinet/static/js/views/sel_rqst_4_det_copy.js'
> Copying 
> '/tmp/ReviewBoardExt/fortinet/static/js/views/approval_status_View.js'
> Copying '/tmp/ReviewBoardExt/fortinet/static/js/views/dashboard.js'
> Copying '/tmp/ReviewBoardExt/fortinet/static/js/views/rqst_descr.js'
> Copying '/tmp/ReviewBoardExt/fortinet/static/js/views/cm_portalView.js'
> Copying '/tmp/ReviewBoardExt/fortinet/static/images/Remove.png'
> Copying '/tmp/ReviewBoardExt/fortinet/static/images/fortinet.png'
> Copying '/tmp/ReviewBoardExt/fortinet/static/images/forti...@2x.png'
> Copying '/tmp/ReviewBoardExt/fortinet/static/images/d...@2

Cannot install extension after upgrading from 2.5.6.1 to 2.5.12 - lessc not found!

2017-06-09 Thread Kevin Yu
On our server, we had reviewboard core 2.5.6.1 running with our own 
extension. it was all fine until we recently upgraded reviewboard core to 
2.5.12. After the upgrade, we can't run python setup.py -v build anymore... 
The error is as follows:
devops@Reviewboard-Test-trunk:/tmp/ReviewBoardExt$ python setup.py -v build
running build
running build_py
running build_static_files
Installing node packages...
npm http GET https://registry.npmjs.org/uglifyjs/2.4.10
npm http GET https://registry.npmjs.org/less/2.7.1
npm http 304 https://registry.npmjs.org/less/2.7.1
npm http 304 https://registry.npmjs.org/uglifyjs/2.4.10
npm WARN deprecated uglifyjs@2.4.10: uglifyjs is deprecated - use uglify-js 
instead.
npm WARN engine less@2.7.1: wanted: {"node":">=0.12"} (current: 
{"node":"v0.10.25","npm":"1.3.10"})
npm http GET https://registry.npmjs.org/source-map/0.1.34
npm http GET https://registry.npmjs.org/yargs
npm http GET https://registry.npmjs.org/async
npm http GET https://registry.npmjs.org/uglify-to-browserify
npm http 304 https://registry.npmjs.org/source-map/0.1.34
npm http 304 https://registry.npmjs.org/yargs
npm http 304 https://registry.npmjs.org/async
npm http 304 https://registry.npmjs.org/uglify-to-browserify
npm http GET https://registry.npmjs.org/amdefine
npm http 304 https://registry.npmjs.org/amdefine
npm http GET https://registry.npmjs.org/errno
npm http GET https://registry.npmjs.org/graceful-fs
npm http GET https://registry.npmjs.org/image-size
npm http GET https://registry.npmjs.org/mime
npm http GET https://registry.npmjs.org/mkdirp
npm http GET https://registry.npmjs.org/promise
npm http GET https://registry.npmjs.org/source-map
npm http 304 https://registry.npmjs.org/errno
npm http 304 https://registry.npmjs.org/graceful-fs
npm http 304 https://registry.npmjs.org/image-size
npm http 304 https://registry.npmjs.org/mime
npm http 304 https://registry.npmjs.org/promise
npm http 304 https://registry.npmjs.org/source-map
npm http 304 https://registry.npmjs.org/mkdirp
npm http GET https://registry.npmjs.org/prr
npm http 304 https://registry.npmjs.org/prr
npm http GET https://registry.npmjs.org/minimist/0.0.8
npm http 304 https://registry.npmjs.org/minimist/0.0.8
npm http GET https://registry.npmjs.org/asap
npm http 304 https://registry.npmjs.org/asap
uglifyjs@2.4.10 node_modules/uglifyjs
├── uglify-to-browserify@1.0.2
├── async@0.2.10
├── yargs@1.3.3
└── source-map@0.1.34 (amdefine@1.0.1)

less@2.7.1 node_modules/less
├── graceful-fs@4.1.11
├── mime@1.3.6
├── image-size@0.5.4
├── errno@0.1.4 (prr@0.0.0)
├── mkdirp@0.5.1 (minimist@0.0.8)
├── promise@7.1.1 (asap@2.0.5)
└── source-map@0.5.6
Copying '/tmp/ReviewBoardExt/fortinet/static/css/rev_req_det.less'
Copying '/tmp/ReviewBoardExt/fortinet/static/js/views/account_handler.js'
Copying '/tmp/ReviewBoardExt/fortinet/static/js/views/branch_builds.js'
Copying '/tmp/ReviewBoardExt/fortinet/static/js/views/bootstrap.js'
Copying '/tmp/ReviewBoardExt/fortinet/static/js/views/apprreqView.js'
Copying '/tmp/ReviewBoardExt/fortinet/static/js/views/test_cvrg_rprt.js'
Copying '/tmp/ReviewBoardExt/fortinet/static/js/views/ftnchkHoldItView.js'
Copying 
'/tmp/ReviewBoardExt/fortinet/static/js/views/sel_rqst_4_det_copy.js'
Copying 
'/tmp/ReviewBoardExt/fortinet/static/js/views/approval_status_View.js'
Copying '/tmp/ReviewBoardExt/fortinet/static/js/views/dashboard.js'
Copying '/tmp/ReviewBoardExt/fortinet/static/js/views/rqst_descr.js'
Copying '/tmp/ReviewBoardExt/fortinet/static/js/views/cm_portalView.js'
Copying '/tmp/ReviewBoardExt/fortinet/static/images/Remove.png'
Copying '/tmp/ReviewBoardExt/fortinet/static/images/fortinet.png'
Copying '/tmp/ReviewBoardExt/fortinet/static/images/forti...@2x.png'
Copying '/tmp/ReviewBoardExt/fortinet/static/images/d...@2x.png'
Copying '/tmp/ReviewBoardExt/fortinet/static/images/teamlead.png'
Copying '/tmp/ReviewBoardExt/fortinet/static/images/favicon_notify.png'
Copying '/tmp/ReviewBoardExt/fortinet/static/images/Create.png'
Copying '/tmp/ReviewBoardExt/fortinet/static/images/ftnt.ico'
Copying '/tmp/ReviewBoardExt/fortinet/static/images/u...@2x.png'
Copying '/tmp/ReviewBoardExt/fortinet/static/images/shipit-grey.png'
Copying '/tmp/ReviewBoardExt/fortinet/static/images/teaml...@2x.png'
Copying '/tmp/ReviewBoardExt/fortinet/static/images/Up.png'
Copying '/tmp/ReviewBoardExt/fortinet/static/images/Bottom.png'
Copying '/tmp/ReviewBoardExt/fortinet/static/images/bot...@2x.png'
Copying '/tmp/ReviewBoardExt/fortinet/static/images/stop16.png'
Copying '/tmp/ReviewBoardExt/fortinet/static/images/cre...@2x.png'
Copying '/tmp/ReviewBoardExt/fortinet/static/images/rem...@2x.png'
Copying '/tmp/ReviewBoardExt/fortinet/static/images/shipit.png'
Copying '/tmp/ReviewBoardExt/fortinet/static/images/shi...@2x.png'
Copying '/tmp/ReviewBoardExt/fortinet/static/images/sto...@2x.png'
Copying '/tmp/ReviewBoardExt/fortinet/static/images/Down.png'
Copying '/tmp/ReviewBoardExt/fortinet/static/images/shipit-g...@2x.png'
Traceback (most recent call last):
  

Python api - how to create a review as a different user

2017-05-08 Thread Kevin Yu
Hi All,

I'm using an admin user to create the RBClient and I'm trying to post a 
review with ship_it=True as user 'team_waive'. However, it's still posting 
as the admin user.

Here's my code:
def create_review(self, request, comment='', ship_it=False, \
public=True, hold_it=False, tl=None):
review = request.get_reviews().create()
review.update(body_top=comment, ship_it=ship_it, user='team_waive')
review.update(public=public)

Is there anyway to do this?

Thanks!

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Reviewboard Extension - Database schema update issues

2017-05-08 Thread Kevin Yu
Just to provide an update, it works! Thanks a lot

On Wednesday, May 3, 2017 at 5:50:54 PM UTC-7, Kevin Yu wrote:
>
> Thanks David! I will give it a try!
>
> On Wednesday, May 3, 2017 at 4:25:03 PM UTC-7, David Trowbridge wrote:
>>
>> Kevin,
>>
>> The correct solution is to write your own evolution. See 
>> https://www.reviewboard.org/docs/manual/2.5/extending/extensions/models/#making-changes-to-custom-models
>>  for 
>> instructions on how to do this and where to put the file.
>>
>> -David
>>
>> On Wed, May 3, 2017 at 4:08 PM Kevin Yu <sams...@gmail.com> wrote:
>>
>>> Hi All, 
>>>
>>> Recently we updated our database schema to add another field to a table 
>>> that's used by our own reviewboard extension. When we run python setup.py 
>>> install to install the extension, we run into the following error:
>>>
>>> stdout: Project signature has changed - an evolution is required
>>>
>>>
>>> stderr: WARNING:py.warnings:/usr/local/lib/python2.7/dist-packages/
>>> Django-1.6.11-py2.7.egg/django/db/backends/mysql/base.py:124: Warning: 
>>> Specified key was too long; max key length is 767 bytes
>>>   return self.cursor.execute(query, args)
>>>
>>>
>>> ERROR:root:Error evolving extension models: Your models contain changes 
>>> that Django Evolution cannot resolve automatically.: The stored 
>>> evolutions do not completely resolve all model changes.
>>> Run `./manage.py evolve --hint` to see a suggestion for the changes 
>>> required.
>>>
>>>
>>> The following are the changes that could not be resolved:
>>> In model fortinet.required_by_branch:
>>> Field 'CLI_review_group' has been added
>>> Traceback (most recent call last):
>>>   File 
>>> "/usr/local/lib/python2.7/dist-packages/Djblets-0.9.3-py2.7.egg/djblets/extensions/manager.py"
>>> , line 1068, in _migrate_extension_models
>>> stdout=stream, stderr=stream)
>>>   File 
>>> "/usr/local/lib/python2.7/dist-packages/Django-1.6.11-py2.7.egg/django/core/management/base.py"
>>> , line 285, in execute
>>> output = self.handle(*args, **options)
>>>   File 
>>> "/usr/local/lib/python2.7/dist-packages/django_evolution-0.7.6-py2.7.egg/django_evolution/management/commands/evolve.py"
>>> , line 65, in handle
>>> self.evolve(*app_labels, **options)
>>>   File 
>>> "/usr/local/lib/python2.7/dist-packages/django_evolution-0.7.6-py2.7.egg/django_evolution/management/commands/evolve.py"
>>> , line 133, in evolve
>>> self.check_simulation()
>>>   File 
>>> "/usr/local/lib/python2.7/dist-packages/django_evolution-0.7.6-py2.7.egg/django_evolution/management/commands/evolve.py"
>>> , line 262, in check_simulation
>>> raise CommandError('Your models contain changes that Django '
>>> CommandError: Your models contain changes that Django Evolution cannot 
>>> resolve automatically.
>>>
>>>
>>>
>>> Eventually, what we had to do is manually add the field to mysql, then 
>>> run the following commands and restart apache2.
>>> rb-site manage /var/www/reviews.example.com shell 
>>> from django_evolution.models import Version
>>> Version.objects.exclude(evolutions__pk__gt=0).delete()
>>>
>>>
>>> I know this is probably a hack at the moment, but what would be the 
>>> proper time to handle database schema update for reviewboard extension? The 
>>> Reviewboard version i'm using is 2.5.6.1.
>>>
>>> -- 
>>> Supercharge your Review Board with Power Pack: 
>>> https://www.reviewboard.org/powerpack/
>>> Want us to host Review Board for you? Check out RBCommons: 
>>> https://rbcommons.com/
>>> Happy user? Let us know! https://www.reviewboard.org/users/
>>> --- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "reviewboard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to reviewboard...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Reviewboard Extension - Database schema update issues

2017-05-03 Thread Kevin Yu
Thanks David! I will give it a try!

On Wednesday, May 3, 2017 at 4:25:03 PM UTC-7, David Trowbridge wrote:
>
> Kevin,
>
> The correct solution is to write your own evolution. See 
> https://www.reviewboard.org/docs/manual/2.5/extending/extensions/models/#making-changes-to-custom-models
>  for 
> instructions on how to do this and where to put the file.
>
> -David
>
> On Wed, May 3, 2017 at 4:08 PM Kevin Yu <sams...@gmail.com > 
> wrote:
>
>> Hi All, 
>>
>> Recently we updated our database schema to add another field to a table 
>> that's used by our own reviewboard extension. When we run python setup.py 
>> install to install the extension, we run into the following error:
>>
>> stdout: Project signature has changed - an evolution is required
>>
>>
>> stderr: WARNING:py.warnings:/usr/local/lib/python2.7/dist-packages/Django
>> -1.6.11-py2.7.egg/django/db/backends/mysql/base.py:124: Warning: 
>> Specified key was too long; max key length is 767 bytes
>>   return self.cursor.execute(query, args)
>>
>>
>> ERROR:root:Error evolving extension models: Your models contain changes 
>> that Django Evolution cannot resolve automatically.: The stored 
>> evolutions do not completely resolve all model changes.
>> Run `./manage.py evolve --hint` to see a suggestion for the changes 
>> required.
>>
>>
>> The following are the changes that could not be resolved:
>> In model fortinet.required_by_branch:
>> Field 'CLI_review_group' has been added
>> Traceback (most recent call last):
>>   File 
>> "/usr/local/lib/python2.7/dist-packages/Djblets-0.9.3-py2.7.egg/djblets/extensions/manager.py"
>> , line 1068, in _migrate_extension_models
>> stdout=stream, stderr=stream)
>>   File 
>> "/usr/local/lib/python2.7/dist-packages/Django-1.6.11-py2.7.egg/django/core/management/base.py"
>> , line 285, in execute
>> output = self.handle(*args, **options)
>>   File 
>> "/usr/local/lib/python2.7/dist-packages/django_evolution-0.7.6-py2.7.egg/django_evolution/management/commands/evolve.py"
>> , line 65, in handle
>> self.evolve(*app_labels, **options)
>>   File 
>> "/usr/local/lib/python2.7/dist-packages/django_evolution-0.7.6-py2.7.egg/django_evolution/management/commands/evolve.py"
>> , line 133, in evolve
>> self.check_simulation()
>>   File 
>> "/usr/local/lib/python2.7/dist-packages/django_evolution-0.7.6-py2.7.egg/django_evolution/management/commands/evolve.py"
>> , line 262, in check_simulation
>> raise CommandError('Your models contain changes that Django '
>> CommandError: Your models contain changes that Django Evolution cannot 
>> resolve automatically.
>>
>>
>>
>> Eventually, what we had to do is manually add the field to mysql, then 
>> run the following commands and restart apache2.
>> rb-site manage /var/www/reviews.example.com shell 
>> from django_evolution.models import Version
>> Version.objects.exclude(evolutions__pk__gt=0).delete()
>>
>>
>> I know this is probably a hack at the moment, but what would be the 
>> proper time to handle database schema update for reviewboard extension? The 
>> Reviewboard version i'm using is 2.5.6.1.
>>
>> -- 
>> Supercharge your Review Board with Power Pack: 
>> https://www.reviewboard.org/powerpack/
>> Want us to host Review Board for you? Check out RBCommons: 
>> https://rbcommons.com/
>> Happy user? Let us know! https://www.reviewboard.org/users/
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "reviewboard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to reviewboard...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Reviewboard Extension - Database schema update issues

2017-05-03 Thread Kevin Yu
Hi All, 

Recently we updated our database schema to add another field to a table 
that's used by our own reviewboard extension. When we run python setup.py 
install to install the extension, we run into the following error:

stdout: Project signature has changed - an evolution is required


stderr: WARNING:py.warnings:/usr/local/lib/python2.7/dist-packages/Django-
1.6.11-py2.7.egg/django/db/backends/mysql/base.py:124: Warning: Specified 
key was too long; max key length is 767 bytes
  return self.cursor.execute(query, args)


ERROR:root:Error evolving extension models: Your models contain changes 
that Django Evolution cannot resolve automatically.: The stored evolutions 
do not completely resolve all model changes.
Run `./manage.py evolve --hint` to see a suggestion for the changes required
.


The following are the changes that could not be resolved:
In model fortinet.required_by_branch:
Field 'CLI_review_group' has been added
Traceback (most recent call last):
  File 
"/usr/local/lib/python2.7/dist-packages/Djblets-0.9.3-py2.7.egg/djblets/extensions/manager.py"
, line 1068, in _migrate_extension_models
stdout=stream, stderr=stream)
  File 
"/usr/local/lib/python2.7/dist-packages/Django-1.6.11-py2.7.egg/django/core/management/base.py"
, line 285, in execute
output = self.handle(*args, **options)
  File 
"/usr/local/lib/python2.7/dist-packages/django_evolution-0.7.6-py2.7.egg/django_evolution/management/commands/evolve.py"
, line 65, in handle
self.evolve(*app_labels, **options)
  File 
"/usr/local/lib/python2.7/dist-packages/django_evolution-0.7.6-py2.7.egg/django_evolution/management/commands/evolve.py"
, line 133, in evolve
self.check_simulation()
  File 
"/usr/local/lib/python2.7/dist-packages/django_evolution-0.7.6-py2.7.egg/django_evolution/management/commands/evolve.py"
, line 262, in check_simulation
raise CommandError('Your models contain changes that Django '
CommandError: Your models contain changes that Django Evolution cannot 
resolve automatically.



Eventually, what we had to do is manually add the field to mysql, then run 
the following commands and restart apache2.
rb-site manage /var/www/reviews.example.com shell 
from django_evolution.models import Version
Version.objects.exclude(evolutions__pk__gt=0).delete()


I know this is probably a hack at the moment, but what would be the proper 
time to handle database schema update for reviewboard extension? The 
Reviewboard version i'm using is 2.5.6.1.

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Review Board Ticket #4545: User name is not shown with certain actions (update and publish diff, closing review request as submitted)

2017-04-24 Thread Kevin Yu
--
To reply, visit https://hellosplat.com/s/beanbag/tickets/4545/
--

New ticket #4545 by samsun387
For Beanbag, Inc. > Review Board

Status: New
Tags: Priority:Medium, Type:Defect

File attachments:

 * Selection_004.bmp
   



--
User name is not shown with certain actions (update and publish diff, closing 
review request as submitted)
==

# What version are you running?
2.5.6.1

# What's the URL of the page containing the problem?
/r/

# What steps will reproduce the problem?
1. Create review request
2. Close review request as submitted or discarded
3. Check the review events at the bottom of the page


# What is the expected output? What do you see instead?
The name of the user who performed these action should be shown. It should be 
the same as any other events. Please refer to the events that were not 
highlighted in the screenshot

--

-- 
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at https://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.


Is there a way to update the notification subject before sending out email?

2017-04-24 Thread Kevin Yu
Hi,

I'm wondering there is any way to update the notification subject before 
sending out email. We would like add some information to the notification 
email subject, which is currently using the review request's summary.

I've created https://hellosplat.com/s/beanbag/tickets/4544/ as feature 
request but so far no news.


-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: reviewboard - review is being posted with a different user!

2017-04-24 Thread Kevin Yu
Just looked at your question again. If you are posting review request 
through GUI, I assume our issue is different.


On Monday, April 24, 2017 at 4:30:12 PM UTC-7, Kevin Yu wrote:
>
> We had run into the same issue a few times. What happened is that I use 
> user A for Reviewboard Server A and B user for reviewboard Server B. Even 
> after rbt logout, when i run rbt post to reviewboard B, it's posted as User 
> A.
>
> rm -Rf ~/.rbtools-cookies fixed the issue for me.
>
> On Monday, March 27, 2017 at 4:51:53 AM UTC-7, Narayanarao Yenduri wrote:
>>
>> thanks Christian for quick reply.
>> unfortunately re-login did not help.
>>
>> i also suspect some cookie might causing this., any other options to 
>> narrow it down?
>>
>> On Monday, 27 March 2017 14:44:55 UTC+5:30, Christian Hammond wrote:
>>>
>>> Sounds like the local user account on Windows is being reused by user2, 
>>> which would mean there's a stale session cookie file for the user.
>>>
>>> Try forcing a re-login using `rbt login`, and provide the 
>>> username/password of the user you want to use.
>>>
>>> Christian
>>>
>>> -- 
>>> Christian Hammond
>>> President/CEO of Beanbag <https://www.beanbaginc.com/>
>>> Makers of Review Board <https://www.reviewboard.org/>
>>>
>>> On Mon, Mar 27, 2017 at 1:54 AM, Narayanarao Yenduri <
>>> ynaray...@gmail.com> wrote:
>>>
>>>> hi 
>>>>
>>>> we have an windows machine with perforce as version control being used 
>>>> by user1.
>>>> uesr1 able to raise reviews properly (rbt post  )
>>>> now user1 left, so allotted the same machine to user2.
>>>> when user2 tries to post review, it seems taking id of user1.
>>>> so user2 not able to submit the diff for reviews.
>>>>
>>>> did any one face similar issue.
>>>>
>>>> appreciate any quick response.
>>>>
>>>> thanks.
>>>>
>>>> -- 
>>>> Supercharge your Review Board with Power Pack: 
>>>> https://www.reviewboard.org/powerpack/
>>>> Want us to host Review Board for you? Check out RBCommons: 
>>>> https://rbcommons.com/
>>>> Happy user? Let us know! https://www.reviewboard.org/users/
>>>> --- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "reviewboard" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to reviewboard...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: reviewboard - review is being posted with a different user!

2017-04-24 Thread Kevin Yu
We had run into the same issue a few times. What happened is that I use 
user A for Reviewboard Server A and B user for reviewboard Server B. Even 
after rbt logout, when i run rbt post to reviewboard B, it's posted as User 
A.

rm -Rf ~/.rbtools-cookies fixed the issue for me.

On Monday, March 27, 2017 at 4:51:53 AM UTC-7, Narayanarao Yenduri wrote:
>
> thanks Christian for quick reply.
> unfortunately re-login did not help.
>
> i also suspect some cookie might causing this., any other options to 
> narrow it down?
>
> On Monday, 27 March 2017 14:44:55 UTC+5:30, Christian Hammond wrote:
>>
>> Sounds like the local user account on Windows is being reused by user2, 
>> which would mean there's a stale session cookie file for the user.
>>
>> Try forcing a re-login using `rbt login`, and provide the 
>> username/password of the user you want to use.
>>
>> Christian
>>
>> -- 
>> Christian Hammond
>> President/CEO of Beanbag 
>> Makers of Review Board 
>>
>> On Mon, Mar 27, 2017 at 1:54 AM, Narayanarao Yenduri > > wrote:
>>
>>> hi 
>>>
>>> we have an windows machine with perforce as version control being used 
>>> by user1.
>>> uesr1 able to raise reviews properly (rbt post  )
>>> now user1 left, so allotted the same machine to user2.
>>> when user2 tries to post review, it seems taking id of user1.
>>> so user2 not able to submit the diff for reviews.
>>>
>>> did any one face similar issue.
>>>
>>> appreciate any quick response.
>>>
>>> thanks.
>>>
>>> -- 
>>> Supercharge your Review Board with Power Pack: 
>>> https://www.reviewboard.org/powerpack/
>>> Want us to host Review Board for you? Check out RBCommons: 
>>> https://rbcommons.com/
>>> Happy user? Let us know! https://www.reviewboard.org/users/
>>> --- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "reviewboard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to reviewboard...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Review Board Ticket #4544: TemplateHook: Support hook for notification email subject

2017-04-17 Thread Kevin Yu
--
To reply, visit https://hellosplat.com/s/beanbag/tickets/4544/
--

New ticket #4544 by samsun387
For Beanbag, Inc. > Review Board

Status: New
Tags: Priority:Medium, Type:Enhancement


--
TemplateHook: Support hook for notification email subject
==

# What version are you running?
2.5.8

# What's the URL of the page this enhancement relates to, if any?
NA

# Describe the enhancement and the motivation for it.
To allow modifying notification email subject

# What operating system are you using? What browser?
Ubuntu 14.04

# Please provide any additional information below.
In release 2.5.8, it has this feature:
TemplateHook now supports the review-email-html-summary and 
review-email-text-summary hook points for adding custom content to HTML and 
plain text e-mails (respectively).

It would be great if it supports updating the review email subject as well. 

--

-- 
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at https://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.


Re: Python API : How to get the file id of add/removed file

2017-03-20 Thread Kevin Yu
Hi Christian,
I just tried dest_file. It doesn't contain the file I am looking for either.

Basically what i am seeing is that neither dest_file and src_file contain 
the file. In my screenshot, I have new add file A (was B). However, neither 
A or B exist in the response from dest_file and src_file. Seems like the 
dest_file and src_file just ignore this kind of diff. Perhaps the 
reviewboard is treating this kind of diff differently ?

Many thanks,
Kevin

On Monday, March 20, 2017 at 3:07:08 PM UTC-7, Christian Hammond wrote:
>
> Hey Kevin,
>
> Your script is going through and checking the source_file attribute of the 
> files, but the source file will be the "Was ..." filename, rather than the 
> new name. Can you try checking dest_file? Maybe that's what you're hitting.
>
> Christian
>
> -- 
> Christian Hammond
> President/CEO of Beanbag <https://www.beanbaginc.com/>
> Makers of Review Board <https://www.reviewboard.org/>
>
> On Mon, Mar 20, 2017 at 3:02 PM, Kevin Yu <sams...@gmail.com 
> > wrote:
>
>> I just did a quick simple test, I svn rm and svn add some files and then 
>> i run my script again. this time, i am able to get the file id..
>>
>> I did a compare with the review request i had issue with. The only 
>> difference is that the files in the original review request involve svn 
>> merge. In this case, the api doesn't return the file id.
>> Please see the screenshot below.
>>
>>
>> <https://lh3.googleusercontent.com/-Fk8E5uZFIKE/WNBRPscrr6I/ClQ/RhXQJbrtj34HVQvICDAE1Ki3MAnL7g39QCLcB/s1600/Selection_001.bmp>
>>
>>
>> On Monday, March 13, 2017 at 2:33:02 PM UTC-7, Kevin Yu wrote:
>>
>>> My Workflow when rbt patch fail because of file conflicts:
>>> Get Review Request by ID -> review_request.get_diffs() and from the 
>>> return, i get the file id by matching the filename. With the file id, my 
>>> script will create an issue against this file to indicate there's merge 
>>> conflicts.
>>>
>>> It works for all the modified files. However, I noticed the get_diffs() 
>>> *doesn't* contain the files that are added or removed from this review 
>>> request. Is there any other way to get the file id for the added or removed 
>>> files from the diff?
>>>
>> -- 
>> Supercharge your Review Board with Power Pack: 
>> https://www.reviewboard.org/powerpack/
>> Want us to host Review Board for you? Check out RBCommons: 
>> https://rbcommons.com/
>> Happy user? Let us know! https://www.reviewboard.org/users/
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "reviewboard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to reviewboard...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Python API : How to get the file id of add/removed file

2017-03-20 Thread Kevin Yu


I just did a quick simple test, I svn rm and svn add some files and then i 
run my script again. this time, i am able to get the file id..

I did a compare with the review request i had issue with. The only 
difference is that the files in the original review request involve svn 
merge. In this case, the api doesn't return the file id.
Please see the screenshot below.

<https://lh3.googleusercontent.com/-Fk8E5uZFIKE/WNBRPscrr6I/ClQ/RhXQJbrtj34HVQvICDAE1Ki3MAnL7g39QCLcB/s1600/Selection_001.bmp>


On Monday, March 13, 2017 at 2:33:02 PM UTC-7, Kevin Yu wrote:
>
> My Workflow when rbt patch fail because of file conflicts:
> Get Review Request by ID -> review_request.get_diffs() and from the 
> return, i get the file id by matching the filename. With the file id, my 
> script will create an issue against this file to indicate there's merge 
> conflicts.
>
> It works for all the modified files. However, I noticed the get_diffs() 
> *doesn't* contain the files that are added or removed from this review 
> request. Is there any other way to get the file id for the added or removed 
> files from the diff?
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Python API : How to get the file id of add/removed file

2017-03-20 Thread Kevin Yu
Hi Christian,

Reviewboard version we are using is 2.5.6.1 and the rbtools is 0.7.9

On Saturday, March 18, 2017 at 3:24:56 PM UTC-7, Christian Hammond wrote:
>
> There's no difference internally between modified files or added/removed 
> files. It's just a field indicating the type. The API is also not doing any 
> filtering that I can see.
>
> What version of Review Board and RBTools are you using?
>
> Christian
>
>
> On Fri, Mar 17, 2017 at 15:54 Kevin Yu <sams...@gmail.com > 
> wrote:
>
>> Hi Christian,
>>
>> Thanks for your reply. What i'm referring to is this. request is the 
>> review request object i get from from reviewboard python api.
>>
>> for conflict_file in conflict_file_list:
>> filediff_id = None
>> for file in request.get_diffs()[-1].get_files():
>> logging.debug(file)
>> if file.source_file == conflict_file:
>> filediff_id = file.id
>> filediff_id_list.append(filediff_id)
>> if not filediff_id:
>> logging.error('ERROR: Failed to find file id for file %s', 
>> conflict_file)
>> sys.exit(1)
>>
>> The return from request.get_diffs()[-1].get_files() doesn't contain the 
>> files that are added or deleted. The added and deleted files are showing on 
>> the web gui diff viewer though. 
>>
>>
>> On Monday, March 13, 2017 at 3:24:42 PM UTC-7, Christian Hammond wrote:
>>
>>> Hi Kevin,
>>>
>>> I assume you're referring to the files provided in diff.get_files(), for 
>>> the appropriate diff in get_diffs(). These will contain all files shown in 
>>> the diff viewer, including added/removed files. They only wouldn't appear 
>>> if they weren't uploaded in the first place. Are you seeing these files in 
>>> the diff viewer itself?
>>>
>>> Christian
>>>
>>
>>> -- 
>>> Christian Hammond
>>> President/CEO of Beanbag <https://www.beanbaginc.com/>
>>> Makers of Review Board <https://www.reviewboard.org/>
>>>
>>> On Mon, Mar 13, 2017 at 2:37 PM, Kevin Yu <sams...@gmail.com> wrote:
>>>
>> I'm using SVN btw.
>>>>
>>>>
>>>> On Monday, March 13, 2017 at 2:33:02 PM UTC-7, Kevin Yu wrote:
>>>>>
>>>>> My Workflow when rbt patch fail because of file conflicts:
>>>>> Get Review Request by ID -> review_request.get_diffs() and from the 
>>>>> return, i get the file id by matching the filename. With the file id, my 
>>>>> script will create an issue against this file to indicate there's merge 
>>>>> conflicts.
>>>>>
>>>>> It works for all the modified files. However, I noticed the 
>>>>> get_diffs() *doesn't* contain the files that are added or removed 
>>>>> from this review request. Is there any other way to get the file id for 
>>>>> the 
>>>>> added or removed files from the diff?
>>>>>
>>>> -- 
>>>> Supercharge your Review Board with Power Pack: 
>>>> https://www.reviewboard.org/powerpack/
>>>> Want us to host Review Board for you? Check out RBCommons: 
>>>> https://rbcommons.com/
>>>> Happy user? Let us know! https://www.reviewboard.org/users/
>>>> --- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "reviewboard" group.
>>>>
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to reviewboard...@googlegroups.com.
>>>>
>>>
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>> -- 
> -- 
> Christian Hammond
> President/CEO of Beanbag <https://www.beanbaginc.com/>
> Makers of Review Board <https://www.reviewboard.org/>
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: rbt diff very slow when svn rm a huge folder (750MB)

2017-03-20 Thread Kevin Yu
Hi Christian,

Thanks for taking the time to look at this issue. 

>From what I have seen so far, after rbt diff, when i run rbt post to post 
this diff to reviewboard, I am guessing reviewboard has checking as well? 
When I run rbt post, it took very long( I cancelled after 10 hours) to 
post. During that time, I did a tcpdump to verify whether the process died 
in the middle or it really takes this long. From what i can see in the 
tcpdump, there's still packet transfer between my local and reviewboard 
server.


On Friday, March 17, 2017 at 11:37:59 PM UTC-7, Christian Hammond wrote:
>
> Hi Kevin,
>
> 5 hours, wow. Well, the reason this is happening is that `svn diff` itself 
> isn't very reliable for some cases, and we have to fix up some metadata in 
> the diff. This means going through each file and doing a lookup and 
> rebuilding some diff data. That's a lot of work. It doesn't add too much to 
> the time for standard changes, but a whole source tree, definitely. 
>
> Nobody can realistically review a change of that size, and the best thing 
> to do is leave that directory out of the diff being posted (using the -X 
> argument, for exclude). People can be told through the review request 
> description that it's been deleted instead.
>
> Ideally, though, we wouldn't be this slow. Ideally we could just trust the 
> diff we're given. There might be things we could do to simplify the work 
> needed for changes of this size, and maybe there's some good optimizations 
> we can do that would help everyone. 750MB is definitely a corner case, 
> though. Still, I want to track this, see if it leads to possible 
> shortcuts/improvements in our algorithm.
>
> Christian 
>
>
> On Fri, Mar 17, 2017 at 16:15 Kevin Yu <sams...@gmail.com > 
> wrote:
>
>> I recently run in this issue. Basically I had to svn rm an older kernel 
>> folder which is about 750MB. I did a rbt diff but it's not return after 5 
>> hours and counting.
>>
>> I understand it's not normal practice to delete a huge folder and post to 
>> reviewboard. However, is this performance expected?
>>
>> -- 
>> Supercharge your Review Board with Power Pack: 
>> https://www.reviewboard.org/powerpack/
>> Want us to host Review Board for you? Check out RBCommons: 
>> https://rbcommons.com/
>> Happy user? Let us know! https://www.reviewboard.org/users/
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "reviewboard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to reviewboard...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> -- 
> Christian Hammond
> President/CEO of Beanbag <https://www.beanbaginc.com/>
> Makers of Review Board <https://www.reviewboard.org/>
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


rbt diff very slow when svn rm a huge folder (750MB)

2017-03-17 Thread Kevin Yu
I recently run in this issue. Basically I had to svn rm an older kernel 
folder which is about 750MB. I did a rbt diff but it's not return after 5 
hours and counting.

I understand it's not normal practice to delete a huge folder and post to 
reviewboard. However, is this performance expected?

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Python API : How to get the file id of add/removed file

2017-03-17 Thread Kevin Yu
Hi Christian,

Thanks for your reply. What i'm referring to is this. request is the review 
request object i get from from reviewboard python api.

for conflict_file in conflict_file_list:
filediff_id = None
for file in request.get_diffs()[-1].get_files():
logging.debug(file)
if file.source_file == conflict_file:
filediff_id = file.id
filediff_id_list.append(filediff_id)
if not filediff_id:
logging.error('ERROR: Failed to find file id for file %s', 
conflict_file)
sys.exit(1)

The return from request.get_diffs()[-1].get_files() doesn't contain the 
files that are added or deleted. The added and deleted files are showing on 
the web gui diff viewer though. 


On Monday, March 13, 2017 at 3:24:42 PM UTC-7, Christian Hammond wrote:
>
> Hi Kevin,
>
> I assume you're referring to the files provided in diff.get_files(), for 
> the appropriate diff in get_diffs(). These will contain all files shown in 
> the diff viewer, including added/removed files. They only wouldn't appear 
> if they weren't uploaded in the first place. Are you seeing these files in 
> the diff viewer itself?
>
> Christian
>
> -- 
> Christian Hammond
> President/CEO of Beanbag <https://www.beanbaginc.com/>
> Makers of Review Board <https://www.reviewboard.org/>
>
> On Mon, Mar 13, 2017 at 2:37 PM, Kevin Yu <sams...@gmail.com 
> > wrote:
>
>> I'm using SVN btw.
>>
>>
>> On Monday, March 13, 2017 at 2:33:02 PM UTC-7, Kevin Yu wrote:
>>>
>>> My Workflow when rbt patch fail because of file conflicts:
>>> Get Review Request by ID -> review_request.get_diffs() and from the 
>>> return, i get the file id by matching the filename. With the file id, my 
>>> script will create an issue against this file to indicate there's merge 
>>> conflicts.
>>>
>>> It works for all the modified files. However, I noticed the get_diffs() 
>>> *doesn't* contain the files that are added or removed from this review 
>>> request. Is there any other way to get the file id for the added or removed 
>>> files from the diff?
>>>
>> -- 
>> Supercharge your Review Board with Power Pack: 
>> https://www.reviewboard.org/powerpack/
>> Want us to host Review Board for you? Check out RBCommons: 
>> https://rbcommons.com/
>> Happy user? Let us know! https://www.reviewboard.org/users/
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "reviewboard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to reviewboard...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Python API : How to get the file id of add/removed file

2017-03-13 Thread Kevin Yu
I'm using SVN btw.

On Monday, March 13, 2017 at 2:33:02 PM UTC-7, Kevin Yu wrote:
>
> My Workflow when rbt patch fail because of file conflicts:
> Get Review Request by ID -> review_request.get_diffs() and from the 
> return, i get the file id by matching the filename. With the file id, my 
> script will create an issue against this file to indicate there's merge 
> conflicts.
>
> It works for all the modified files. However, I noticed the get_diffs() 
> *doesn't* contain the files that are added or removed from this review 
> request. Is there any other way to get the file id for the added or removed 
> files from the diff?
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


RBTools Ticket #4527: rbt patch fail when user do svn merge cherry-pick

2017-03-02 Thread Kevin Yu
--
To reply, visit https://hellosplat.com/s/beanbag/tickets/4527/
--

New ticket #4527 by samsun387
For Beanbag, Inc. > RBTools

Status: New
Tags: Priority:Medium, Type:Defect

File attachments:

 * rbt_patch_debug.log
   



--
rbt patch fail when user do svn merge cherry-pick
==

# What version are you running?
0.7.9

# What steps will reproduce the problem?
1. In a feature branch, do svn merge -c 
2. rbt post --svn-show-copies-as-adds=y
3. In a clean checkout of feature branch, do rbt patch 


# What is the expected output? What do you see instead?
Expected Result: Should be able to patch the diff.
Actual Result: rbt patch failed. 
Error is:
svn: E21: Can't move 
'/home/devops/jenkins_slave/workspace/ReviewBoard/ReviewBoard_Commit/FortiSwitchOS
 v3.00/svn-qdo28p' to 
'/home/devops/jenkins_slave/workspace/ReviewBoard/ReviewBoard_Commit/FortiSwitchOS
 v3.00/3.5': Is a directory

# What operating system are you using?
Ubuntu 14.04

# Attach the debug out from the command.

```
$ rbt patch --debug 
Debug log attached


# Please provide any additional information below.
When svn merge -c is used, when rbt post, it somehow knows it's a merge so rbt 
modifies the file path. For example, the diff from rbt post would look 
something like this:

Index: /ABC/branches/3.x/3.5/trunk/cooked/cert/802.1x.crt
===
--- /ABC/trunk/cooked/cert/802.1x.crt   (nonexistent)
+++ /ABC/branches/3.x/3.5/trunk/cooked/cert/802.1x.crt  (working copy)

Somehow rbt knows it's merge from trunk to 3.5 branch, so it modified the path 
in the diff. When I run rbt patch, then it will fail. 

Eventually I had to manually modify the diff file to the following for it to 
work:
Index: /ABC/branches/3.x/3.5/trunk/cooked/cert/802.1x.crt
===
--- /ABC/branches/3.x/3.5/trunk/cooked/cert/802.1x.crt  (nonexistent)
+++ /ABC/branches/3.x/3.5/trunk/cooked/cert/802.1x.crt  (working copy)

--

-- 
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at https://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.


Re: RBTools Ticket #4409: rbt patch deletes folder even though the folder deletion is not in the diff!

2017-03-02 Thread Kevin Yu
--
To reply, visit https://hellosplat.com/s/beanbag/tickets/4409/
--

New update by samsun387
For Beanbag, Inc. > RBTools > Ticket #4409


Reply:

This ticket should not be NeedInfo anymore but i couldn't update that...

-- 
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at https://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.


Review Board Ticket #4488: Discarding a draft will lose the diff

2016-11-22 Thread Kevin Yu
--
To reply, visit https://hellosplat.com/s/beanbag/tickets/4488/
--

New ticket #4488 by samsun387
For Beanbag, Inc. > Review Board

Status: New
Tags: Priority:Medium, Type:Defect


--
Discarding a draft will lose the diff
==

# What version are you running?
2.5.6.1

# What's the URL of the page containing the problem?
draft

# What steps will reproduce the problem?
1. Use rbt post to create a draft
2. Don't publish it. Discard it 
3. Reopen the draft


# What is the expected output? What do you see instead?
Expected: Diff should still be there. 
Actual: Diff is gone. the tab for showing diff is gone too.

# What operating system are you using? What browser?
Ubuntu 14.04 Chrome Version 54.0.2840.100 (64-bit)

# Please provide any additional information below.

--

-- 
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at https://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.


Re: RBTools Ticket #4409: rbt patch deletes folder even though the folder deletion is not in the diff!

2016-11-22 Thread Kevin Yu
--
To reply, visit https://hellosplat.com/s/beanbag/tickets/4409/
--

New update by samsun387
For Beanbag, Inc. > RBTools > Ticket #4409


Summary:
- rbt patch deletes folder even though the folder deletion is not in the 
diff
+ rbt patch deletes folder even though the folder deletion is not in the 
diff!

-- 
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at https://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.


Re: RBTools Ticket #4409: rbt patch deletes folder even though the folder deletion is not in the diff

2016-11-07 Thread Kevin Yu
--
To reply, visit https://hellosplat.com/s/beanbag/tickets/4409/
--

New update by samsun387
For Beanbag, Inc. > RBTools > Ticket #4409


Reply:

Any update on this ? thanks

-- 
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at https://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.


Re: Review Board Ticket #4450: ReviewRequest.last_review_activity_timestamp should be exposed in the API

2016-08-16 Thread Kevin Yu
--
To reply, visit https://hellosplat.com/s/beanbag/tickets/4450/
--

New update by samsun387
For Beanbag, Inc. > Review Board > Ticket #4450


Reply:

Thanks for the quick response. Yes I also tried to use the 
last_review_timestamp(the column name in db in reviewrequest table) but found 
out it's not available through API. It would be great if you can expose that.

With last_review_timestamp being exposed through API, is there a way to 
call the API so that it returns the review requests with either 
last_updated_from or last_review_timestamp within 24 hours, whichever is later? 
Otherwise I will make two api calls to get two lists of review request and 
combine them.

-- 
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at https://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.


Review Board Ticket #4450: Fixed issue / Drop issue doesn't update the last_updated_from in Review Request

2016-08-15 Thread Kevin Yu
--
To reply, visit https://hellosplat.com/s/beanbag/tickets/4450/
--

New ticket #4450 by samsun387
For Beanbag, Inc. > Review Board

Status: New
Tags: Priority:Medium, Type:Defect


--
Fixed issue / Drop issue doesn't update the last_updated_from in Review Request
==

# What version are you running?
2.5.6.1

# What steps will reproduce the problem?
1. Create a review request
2. Create an issue in the review request
3. Check the last_updated_from field. Note that it's updated
4. Wait for at least one minute or longer, then fix the issue or drop the issue.
5. Note that the last_updated_from is not updated

# What is the expected output? What do you see instead
In Step 5, last_updated_from should be updated when an issue is closed or 
dropped. Otherwise it seems contradicting as the last_updated_from is updated 
when the issue is created

# What operating system are you using? What browser?
Linux, Chrome

# Please provide any additional information below.
I'm doing some integration with Reviewboard. Basically I have a script which 
uses python API to fetch any review request with last-updated-from within 24 
hours. If the review is approved, then trigger something.

With this ticket i'm reporting, It's causing some review requests slipping 
through the cracks. Let's say everyone approves the review request 5 days ago, 
with an open issue. In this case, the last-updated-from would be 5 days ago, 
but it's not approved due to the open issue. Then someone drops the issue 
today. Now the request.approved becomes True, but last-updated-from is still 5 
days ago.

--

-- 
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at https://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.


Reviewboard Extension Upgrade

2015-12-22 Thread Kevin Yin
I recently upgraded Reviewboard from 1.7.x to 2.0.x. I had a Reviewbot 
extension which also require upgrade from 0.1 to 0.2. Everything seemed 
working  fine until I wanted to try other extensions.

On enabling other extensions, it gives me:

The stored evolutions do not completely resolve all model changes.
Run `./manage.py evolve --hint` to see a suggestion for the changes required.

The following are the changes that could not be resolved:
The model reviewbotext.Tool has been deleted
The model reviewbotext.Profile has been deleted
The model reviewbotext.ToolExecution has been deleted
The model reviewbotext.AutomaticRunGroup has been deleted
The model reviewbotext.ManualPermission has been deleted
In model reviewbotext.ReviewBotTool:
Meta property 'unique_together' has changed


Traceback (most recent call last):
  File 
"/usr/local/python2.7/lib/python2.7/site-packages/Djblets-0.8.23-py2.7.egg/djblets/extensions/manager.py",
 line 818, in _install_extension_media_internal
stdout=stream, stderr=stream)
  File 
"/usr/local/python2.7/lib/python2.7/site-packages/Django-1.6.11-py2.7.egg/django/core/management/base.py",
 line 285, in execute
output = self.handle(*args, **options)
  File 
"/usr/local/python2.7/lib/python2.7/site-packages/django_evolution-0.7.6-py2.7.egg/django_evolution/management/commands/evolve.py",
 line 65, in handle
self.evolve(*app_labels, **options)
  File 
"/usr/local/python2.7/lib/python2.7/site-packages/django_evolution-0.7.6-py2.7.egg/django_evolution/management/commands/evolve.py",
 line 133, in evolve
self.check_simulation()
  File 
"/usr/local/python2.7/lib/python2.7/site-packages/django_evolution-0.7.6-py2.7.egg/django_evolution/management/commands/evolve.py",
 line 262, in check_simulation
raise CommandError('Your models contain changes that Django '
CommandError: Your models contain changes that Django Evolution cannot resolve 
automatically.



When I run rb-site mange /path evolve, it says nothing to evolve.


How can I get around it?

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Failed to upgrade from 1.7.12 to 1.7.28 and 2.x

2015-12-11 Thread Kevin Yin
Turned out I have django_evolution version updated somehow. Rolling back to 
the previous version worked.

On Tuesday, December 8, 2015 at 4:42:50 PM UTC-8, Kevin Yin wrote:
>
> So I got this reviewboard 1.7.12 server assigned to me. We have the need 
> for some new features from newer versions of reviewboard. So I simply did 
> easy_install -U ReviewBoard and rb-site upgrade. It failed. I did not have 
> a recent backup, but luckily rolling back the ReviewBoard python package 
> version worked. So I read a bunch of discussions here. I decided to upgrade 
> to 1.7.28 first. But it fails too, with following error same as 
> https://groups.google.com/forum/#!searchin/reviewboard/Downgrading$20Reviewboard$202.0RC2%7Csort:relevance/reviewboard/pxQ3eyYPhzE/PxEj_0_Oi9YJ
> :
>
> --  --
> Creating tables ...
>
> [!] Unable to execute the manager command syncdb: No module named
> db.fields
>
> [!] Unable to execute the manager command evolve: No module named
> db.fields
> ---  ---
>
> So I compared some schema and content, figured out it is from 
> reviewboard.django_project_version. Then I took dumpdb this time, and 
> deleted the last record of reviewboard.django_project_version, retried 
> upgrading, it now fails with
>
>
> -  --
> Creating tables ...
> Upgrading Review Board from 1.7.12 to 1.7.28
> There are unapplied evolutions for accounts.
> There are unapplied evolutions for attachments.
> There are unapplied evolutions for diffviewer.
> There are unapplied evolutions for site.
> Project signature has changed - an evolution is required
> Installing custom SQL ...
> Installing indexes ...
> Installed 0 object(s) from 0 fixture(s)
> The stored evolutions do not completely resolve all model changes.
> Run `./manage.py evolve --hint` to see a suggestion for the changes 
> required.
>
> The following are the changes that could not be resolved:
> In model attachments.FileAttachment:
> Field 'orig_filename' has been added
> In model hostingsvcs.HostingServiceAccount:
> Field 'hosting_url' has been added
> The model auth.Message has been deleted
> In model reviews.FileAttachmentComment:
> Field 'extra_data' has been added
> In model reviews.ReviewRequest:
> Field 'last_review_activity_timestamp' has been added
> Field 'depends_on' has been added
> Field 'last_review_timestamp' has been deleted
> In model reviews.ReviewRequestDraft:
> Field 'depends_on' has been added
> In model accounts.Profile:
> Field 'timezone' has been added
> Field 'open_an_issue' has been added
> Field 'extra_data' has been added
> In model diffviewer.DiffSetHistory:
> Field 'last_diff_updated' has been added
> In model diffviewer.FileDiff:
> Field 'diff_hash' has been added
> Field 'parent_diff_hash' has been added
> Field 'diff64' has been added
> Field 'parent_diff64' has been added
> Field 'parent_diff' has been deleted
> Field 'diff' has been deleted
> Error: Your models contain changes that Django Evolution cannot resolve 
> automatically.
>
> How can I proceed? I have a backup before this happens (quite old so not 
> possible to load back).
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Downgrading Reviewboard 2.0RC2 -> 1.7.25

2015-12-10 Thread Kevin Yin
Thank you for your reply. I create a thread 
at https://groups.google.com/forum/#!topic/reviewboard/EVEDKKQ2b78

On Sunday, December 6, 2015 at 12:27:20 PM UTC-8, Christian Hammond wrote:
>
> Hi Kevin,
>
> Given how long ago that was, and how many releases ago, can you start a 
> new thread with the issue you're hitting, including versions and all error 
> output? That'll help keep discussion focused on your problem, and help us 
> offer recommendations.
>
> Thanks,
>
> Christian
>
> -- 
> Christian Hammond - chri...@beanbaginc.com 
> Review Board - https://www.reviewboard.org
> Beanbag, Inc. - https://www.beanbaginc.com
>
> On Sun, Dec 6, 2015 at 3:22 AM, Kevin Yin <keviny...@gmail.com 
> > wrote:
>
>> Hi Daniel,
>>
>> I ran into the same problem here. Did you ever figure out? Thanks!
>>
>> Kevin
>>
>>
>> On Saturday, May 10, 2014 at 5:14:27 AM UTC-7, Daniel Laird wrote:
>>>
>>> My original email was not very clear.
>>> On my backup server I want to remove the 2.0RC2 installation and get a 
>>> 1.7.x installation running.
>>> However I removed all the RB2.0RC2 files and then dropped the 
>>> reviewboard table from mysql database.
>>> I then did a clean installation of 1.7.25.
>>> I then imported the data from my old server (which was running 1.7.18) - 
>>> at this point I would have thought I would have a 'clean' installation.
>>> However the rb-site upgrade fails and when I visit the homepage I get 
>>> the errors below.
>>>
>>> It is almost as if there are some settings files that are stored someone 
>>> not in my installation directory and not in the mysql database.
>>> Might there be some files related to django evolutions that I have to 
>>> delete?
>>>
>>> Dan
>>>
>>>
>>>
>>> On Friday, 9 May 2014 20:27:23 UTC+1, Christian Hammond wrote:
>>>>
>>>> Hi Dan,
>>>>
>>>> There are many reasons why a 2.0 database will not cleanly turn into a 
>>>> 1.7.x database. We stick certain data in new tables/columns that don't 
>>>> exist in 1.7. We've migrated data from those older columns. 
>>>> Django-Evolution has no concept of a downgrade and will likely just break 
>>>> every future attempt to ever upgrade your database again.
>>>>
>>>> You're looking to keep the 2.0 data in 1.7.x? Any chance you can just 
>>>> upgrade to 2.0 RC 3 and stick with that until 2.0 is out (very very soon)?
>>>>
>>>> Christian
>>>>
>>>> -- 
>>>> Christian Hammond - chi...@chipx86.com
>>>> Review Board - http://www.reviewboard.org
>>>> Beanbag, Inc. - http://www.beanbaginc.com
>>>>
>>>>
>>>> On Fri, May 9, 2014 at 8:04 AM, Daniel Laird <daniel@googlemail.com
>>>> > wrote:
>>>>
>>>>> All,
>>>>>
>>>>> Due to various issue my development server has to be re-purposed as 
>>>>> the main server.
>>>>> This has meant I have to revert from 2.0RC2 -> 1.7.25 (the latest 
>>>>> stable version).
>>>>>
>>>>> At this point I usually import the database and media files and all 
>>>>> works ok.
>>>>> However I get the following:
>>>>> Traceback (most recent call last):
>>>>>
>>>>>   File 
>>>>> "/usr/local/lib/python2.6/dist-packages/Django-1.4.12-py2.6.egg/django/core/handlers/base.py",
>>>>>  
>>>>> line 89, in get_response
>>>>> response = middleware_method(request)
>>>>>
>>>>>   File 
>>>>> "/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.25-py2.6.egg/reviewboard/accounts/middleware.py",
>>>>>  
>>>>> line 12, in process_request
>>>>> user = Profile.objects.get(user=request.user)
>>>>>
>>>>>   File 
>>>>> "/usr/local/lib/python2.6/dist-packages/Django-1.4.12-py2.6.egg/django/db/models/manager.py",
>>>>>  
>>>>> line 131, in get
>>>>> return self.get_query_set().get(*args, **kwargs)
>>>>>
>>>>>   File 
>>>>> "/usr/local/lib/python2.6/dist-packages/Django-1.4.12-py2.6.egg/django/db/models/query.py",
>>>>>  
>>>>> line 361, in get
>>>>> num = len(clone)
>>>>&g

Failed to upgrade from 1.7.12 to 1.7.28 and 2.x

2015-12-08 Thread Kevin Yin
So I got this reviewboard 1.7.12 server assigned to me. We have the need 
for some new features from newer versions of reviewboard. So I simply did 
easy_install -U ReviewBoard and rb-site upgrade. It failed. I did not have 
a recent backup, but luckily rolling back the ReviewBoard python package 
version worked. So I read a bunch of discussions here. I decided to upgrade 
to 1.7.28 first. But it fails too, with following error same as 
https://groups.google.com/forum/#!searchin/reviewboard/Downgrading$20Reviewboard$202.0RC2%7Csort:relevance/reviewboard/pxQ3eyYPhzE/PxEj_0_Oi9YJ:

--  --
Creating tables ...

[!] Unable to execute the manager command syncdb: No module named
db.fields

[!] Unable to execute the manager command evolve: No module named
db.fields
---  ---

So I compared some schema and content, figured out it is from 
reviewboard.django_project_version. Then I took dumpdb this time, and 
deleted the last record of reviewboard.django_project_version, retried 
upgrading, it now fails with


-  --
Creating tables ...
Upgrading Review Board from 1.7.12 to 1.7.28
There are unapplied evolutions for accounts.
There are unapplied evolutions for attachments.
There are unapplied evolutions for diffviewer.
There are unapplied evolutions for site.
Project signature has changed - an evolution is required
Installing custom SQL ...
Installing indexes ...
Installed 0 object(s) from 0 fixture(s)
The stored evolutions do not completely resolve all model changes.
Run `./manage.py evolve --hint` to see a suggestion for the changes 
required.

The following are the changes that could not be resolved:
In model attachments.FileAttachment:
Field 'orig_filename' has been added
In model hostingsvcs.HostingServiceAccount:
Field 'hosting_url' has been added
The model auth.Message has been deleted
In model reviews.FileAttachmentComment:
Field 'extra_data' has been added
In model reviews.ReviewRequest:
Field 'last_review_activity_timestamp' has been added
Field 'depends_on' has been added
Field 'last_review_timestamp' has been deleted
In model reviews.ReviewRequestDraft:
Field 'depends_on' has been added
In model accounts.Profile:
Field 'timezone' has been added
Field 'open_an_issue' has been added
Field 'extra_data' has been added
In model diffviewer.DiffSetHistory:
Field 'last_diff_updated' has been added
In model diffviewer.FileDiff:
Field 'diff_hash' has been added
Field 'parent_diff_hash' has been added
Field 'diff64' has been added
Field 'parent_diff64' has been added
Field 'parent_diff' has been deleted
Field 'diff' has been deleted
Error: Your models contain changes that Django Evolution cannot resolve 
automatically.

How can I proceed? I have a backup before this happens (quite old so not 
possible to load back).

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Downgrading Reviewboard 2.0RC2 -> 1.7.25

2015-12-06 Thread Kevin Yin
Hi Daniel,

I ran into the same problem here. Did you ever figure out? Thanks!

Kevin

On Saturday, May 10, 2014 at 5:14:27 AM UTC-7, Daniel Laird wrote:
>
> My original email was not very clear.
> On my backup server I want to remove the 2.0RC2 installation and get a 
> 1.7.x installation running.
> However I removed all the RB2.0RC2 files and then dropped the reviewboard 
> table from mysql database.
> I then did a clean installation of 1.7.25.
> I then imported the data from my old server (which was running 1.7.18) - 
> at this point I would have thought I would have a 'clean' installation.
> However the rb-site upgrade fails and when I visit the homepage I get the 
> errors below.
>
> It is almost as if there are some settings files that are stored someone 
> not in my installation directory and not in the mysql database.
> Might there be some files related to django evolutions that I have to 
> delete?
>
> Dan
>
>
>
> On Friday, 9 May 2014 20:27:23 UTC+1, Christian Hammond wrote:
>>
>> Hi Dan,
>>
>> There are many reasons why a 2.0 database will not cleanly turn into a 
>> 1.7.x database. We stick certain data in new tables/columns that don't 
>> exist in 1.7. We've migrated data from those older columns. 
>> Django-Evolution has no concept of a downgrade and will likely just break 
>> every future attempt to ever upgrade your database again.
>>
>> You're looking to keep the 2.0 data in 1.7.x? Any chance you can just 
>> upgrade to 2.0 RC 3 and stick with that until 2.0 is out (very very soon)?
>>
>> Christian
>>
>> -- 
>> Christian Hammond - chi...@chipx86.com
>> Review Board - http://www.reviewboard.org
>> Beanbag, Inc. - http://www.beanbaginc.com
>>
>>
>> On Fri, May 9, 2014 at 8:04 AM, Daniel Laird <daniel@googlemail.com> 
>> wrote:
>>
>>> All,
>>>
>>> Due to various issue my development server has to be re-purposed as the 
>>> main server.
>>> This has meant I have to revert from 2.0RC2 -> 1.7.25 (the latest stable 
>>> version).
>>>
>>> At this point I usually import the database and media files and all 
>>> works ok.
>>> However I get the following:
>>> Traceback (most recent call last):
>>>
>>>   File 
>>> "/usr/local/lib/python2.6/dist-packages/Django-1.4.12-py2.6.egg/django/core/handlers/base.py",
>>>  
>>> line 89, in get_response
>>> response = middleware_method(request)
>>>
>>>   File 
>>> "/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.25-py2.6.egg/reviewboard/accounts/middleware.py",
>>>  
>>> line 12, in process_request
>>> user = Profile.objects.get(user=request.user)
>>>
>>>   File 
>>> "/usr/local/lib/python2.6/dist-packages/Django-1.4.12-py2.6.egg/django/db/models/manager.py",
>>>  
>>> line 131, in get
>>> return self.get_query_set().get(*args, **kwargs)
>>>
>>>   File 
>>> "/usr/local/lib/python2.6/dist-packages/Django-1.4.12-py2.6.egg/django/db/models/query.py",
>>>  
>>> line 361, in get
>>> num = len(clone)
>>>
>>>   File 
>>> "/usr/local/lib/python2.6/dist-packages/Django-1.4.12-py2.6.egg/django/db/models/query.py",
>>>  
>>> line 85, in __len__
>>> self._result_cache = list(self.iterator())
>>>
>>>   File 
>>> "/usr/local/lib/python2.6/dist-packages/Django-1.4.12-py2.6.egg/django/db/models/query.py",
>>>  
>>> line 291, in iterator
>>> for row in compiler.results_iter():
>>>
>>>   File 
>>> "/usr/local/lib/python2.6/dist-packages/Django-1.4.12-py2.6.egg/django/db/models/sql/compiler.py",
>>>  
>>> line 763, in results_iter
>>> for rows in self.execute_sql(MULTI):
>>>
>>>   File 
>>> "/usr/local/lib/python2.6/dist-packages/Django-1.4.12-py2.6.egg/django/db/models/sql/compiler.py",
>>>  
>>> line 818, in execute_sql
>>> cursor.execute(sql, params)
>>>
>>>   File 
>>> "/usr/local/lib/python2.6/dist-packages/Django-1.4.12-py2.6.egg/django/db/backends/mysql/base.py",
>>>  
>>> line 114, in execute
>>> return self.cursor.execute(query, args)
>>>
>>>   File 
>>> "/usr/local/lib/python2.6/dist-packages/MySQL_python-1.2.3-py2.6-linux-x86_64.egg/MySQLdb/cursors.py",
>>>  
>>> line 174, in execute
>>>  

RB 2.5.1.1 Email not getting sent

2015-12-04 Thread Kevin Jones
Hi there.

Setup:

Server has reviewboard running with a localhost (port 25) email server. 
We're not using TLS.

My users are complaining about not receiving email notifications, and I'm 
stuck as to the next steps to debug the issue.

What I've done:

Turned on Reviewboard logging.
Attempted to send test emails from the Admin interface. No joy.
Telnet to the email server port and send a message from there. That works.

Look at apache logs, reviewboard logs, nothing is popping out. The one 
thing I'm seeing is an SSL protocol issue, but that would be between the 
server and the repository (I think). 

Look at other RB setups and compare. Nothing appears to be out of the 
ordinary. 

Any advice on what to look at next would be appreciated.

-Kevin

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: RB 2.5.1.1 Email not getting sent

2015-12-04 Thread Kevin Jones
This was, but we had to do a wipeout and start with the most recent 
version. I essentially nuked the server to get that to happen.
We're using Postfix, and there doesn't seem to be any sort of error in the 
logs. A stop and start of postfix doesn't change anything.

-Kevin

On Friday, December 4, 2015 at 1:19:34 PM UTC-6, Christian Hammond wrote:
>
> Hi Kevin,
>
> Was this working in a prior version?
>
> I'm not aware of any e-mail-breaking bugs right now. We had some in some 
> previous releases, but it appears things have stabilized.
>
> What are you using for the e-mail server? Is there anything at all in the 
> e-mail server's logs?
>
> Christian
>
> -- 
> Christian Hammond - chri...@beanbaginc.com 
> Review Board - https://www.reviewboard.org
> Beanbag, Inc. - https://www.beanbaginc.com
>
> On Fri, Dec 4, 2015 at 8:03 AM, Kevin Jones <kjl...@gmail.com 
> > wrote:
>
>> Hi there.
>>
>> Setup:
>>
>> Server has reviewboard running with a localhost (port 25) email server. 
>> We're not using TLS.
>>
>> My users are complaining about not receiving email notifications, and I'm 
>> stuck as to the next steps to debug the issue.
>>
>> What I've done:
>>
>> Turned on Reviewboard logging.
>> Attempted to send test emails from the Admin interface. No joy.
>> Telnet to the email server port and send a message from there. That works.
>>
>> Look at apache logs, reviewboard logs, nothing is popping out. The one 
>> thing I'm seeing is an SSL protocol issue, but that would be between the 
>> server and the repository (I think). 
>>
>> Look at other RB setups and compare. Nothing appears to be out of the 
>> ordinary. 
>>
>> Any advice on what to look at next would be appreciated.
>>
>> -Kevin
>>
>> -- 
>> Supercharge your Review Board with Power Pack: 
>> https://www.reviewboard.org/powerpack/
>> Want us to host Review Board for you? Check out RBCommons: 
>> https://rbcommons.com/
>> Happy user? Let us know! https://www.reviewboard.org/users/
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "reviewboard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to reviewboard...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: How to display local picture for user?

2015-01-28 Thread Kevin Brotcke
Did this enhancement ever get added or someone start working on it?

On Wednesday, February 1, 2012 at 4:44:56 AM UTC-5, Christian Hammond wrote:

 Depending on how you do it, yeah, we'll accept it. Seems like a good 
 addition.

 What I'd request is that you add new optional functions to the AuthBackend 
 classes (reviewboard/accounts/backends.py). There should be some function 
 for requesting an avatar image for a user. Should return a URL and 
 width/height if available. The default implementation would return the 
 gravatar.

 The Profile class (accounts/models.py) should have a function for 
 returning the avatar as HTML. It would talk to the auth backend to get it.

 The HTML would then use this function in the Profile class, instead of 
 calling into gravatars.

 Then, if the LDAP field for the pictures is in any way standard (not just 
 specific to your install), the LDAPBackend (and ActiveDirectoryBackend if 
 relevant?) should return the profile from the server if available, and fall 
 back to the default implementation otherwise.

 Christian

 -- 
 Christian Hammond - chi...@chipx86.com javascript:
 Review Board - http://www.reviewboard.org
 VMware, Inc. - http://www.vmware.com


 2012/2/1 Michael Zhilin miz...@gmail.com javascript:

 Hi,

 As I understand it's question of avatar caching. But in our company we 
 have another issue in our company. Pictures are stored in LDAP and we have 
 plan to develop patch to support it. Could you please check if it's 
 acceptable for you?

 Thank you,
 Michael Zhilin | Research  Development | www.NetCracker.com  
 Accelerating Business Transformation

 On Feb 1, 2012, at 10:17 AM, Christian Hammond chi...@chipx86.com 
 javascript: wrote:

 Hi,

 Review Board's only avatar method today is gravatars. There are no 
 current plans to implement a secondary system. What I'd be willing to 
 accept is a setting for turning on/off gravatars, but we'd probably need a 
 patch for it.

 Christian

 -- 
 Christian Hammond - chi...@chipx86.com javascript:
 Review Board - http://www.reviewboard.org
 VMware, Inc. - http://www.vmware.com


 2012/1/30 深圳手机(王) 8257...@qq.com javascript:

 It seems the user's picture are download from : *www.gravate.com* 
 http://www.google.com.hk/search?hl=zh-CNgbv=2gs_sm=sgs_upl=470532l470532l0l471313l1l1l0l0l0l0l0l0ll0l0q=www.gravate.comspell=1sa=X,
  
 but I  don't want to downlad the picture  from this website because our 
 network is not so good. I want to down load all the pictures from local 
 server, such as http://RBserver.
 How can I do?

 -- 
 Want to help the Review Board project? Donate today at 
 http://www.reviewboard.org/donate/
 Happy user? Let us know at http://www.reviewboard.org/users/
 -~--~~~~--~~--~--~---
 To unsubscribe from this group, send email to 
 reviewboard...@googlegroups.com javascript:
 For more options, visit this group at 
 http://groups.google.com/group/reviewboard?hl=en


  -- 
 Want to help the Review Board project? Donate today at 
 http://www.reviewboard.org/donate/
 Happy user? Let us know at http://www.reviewboard.org/users/
 -~--~~~~--~~--~--~---
 To unsubscribe from this group, send email to 
 reviewboard...@googlegroups.com javascript:
 For more options, visit this group at 
 http://groups.google.com/group/reviewboard?hl=en

  -- 
 Want to help the Review Board project? Donate today at 
 http://www.reviewboard.org/donate/
 Happy user? Let us know at http://www.reviewboard.org/users/
 -~--~~~~--~~--~--~---
 To unsubscribe from this group, send email to 
 reviewboard...@googlegroups.com javascript:
 For more options, visit this group at 
 http://groups.google.com/group/reviewboard?hl=en




-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
reviewboard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Another The file was not found in the repository Error 207 issue

2014-12-11 Thread Kevin Jones
I tried rbt post HEAD~1 to get a diff from the last commit to the master,
but it only caused the error.

-Kevin

On Wed, Dec 10, 2014 at 6:46 PM, David Trowbridge trowb...@gmail.com
wrote:

 What commands are you using for your post-commit review?

 -David


 On Tue, Dec 9, 2014 at 6:57 PM, Kevin Jones kjlo...@gmail.com wrote:

 Yes. Same hash.

 More digging showed that creating a review from a new branch via rbt post
 works. Attempting to do a post-commit review is where the error occurs.

 -Kevin

 On Tue, Dec 9, 2014 at 4:46 PM, David Trowbridge trowb...@gmail.com
 wrote:

 Do master and origin/master point to the same thing?

 -David

 On Tue, Dec 9, 2014 at 10:16 AM, Kevin Jones kjlo...@gmail.com wrote:

 Greetings,

 I'm trying to figure out why a diff, regardless of whether it was
 created with local diff tools or rbt, keeps reporting that it can't find a
 particular revision of a file in the repository.

 Using: Git and reviewboard 2.0.5
 What I've tried:
 rbt diff
 rbt post master changed_branch
 other permutations of the above to load the diff into reviewboard.

 Right now, I'm grasping at straws, and I'm not even sure how to begin
 debugging the issue. The reviewboard user has access to the repository.
 Gitweb access is configured properly... all of the usual suspects aren't
 that suspicious.

 I know I've done something wrong. I just don't know what.

 Any tips on where to start debugging would be greatly appreciated.
 -Kevin

 --
 Get the Review Board Power Pack at
 http://www.reviewboard.org/powerpack/
 ---
 Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
 ---
 Happy user? Let us know at http://www.reviewboard.org/users/
 ---
 You received this message because you are subscribed to the Google
 Groups reviewboard group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to reviewboard+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


  --
 Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
 ---
 Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
 ---
 Happy user? Let us know at http://www.reviewboard.org/users/
 ---
 You received this message because you are subscribed to a topic in the
 Google Groups reviewboard group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/reviewboard/Pewp-yIO9Kc/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 reviewboard+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


  --
 Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
 ---
 Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
 ---
 Happy user? Let us know at http://www.reviewboard.org/users/
 ---
 You received this message because you are subscribed to the Google Groups
 reviewboard group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to reviewboard+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


  --
 Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
 ---
 Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
 ---
 Happy user? Let us know at http://www.reviewboard.org/users/
 ---
 You received this message because you are subscribed to a topic in the
 Google Groups reviewboard group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/reviewboard/Pewp-yIO9Kc/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 reviewboard+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
reviewboard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Another The file was not found in the repository Error 207 issue

2014-12-09 Thread Kevin Jones
Greetings,

I'm trying to figure out why a diff, regardless of whether it was created 
with local diff tools or rbt, keeps reporting that it can't find a 
particular revision of a file in the repository. 

Using: Git and reviewboard 2.0.5
What I've tried:
rbt diff 
rbt post master changed_branch
other permutations of the above to load the diff into reviewboard.

Right now, I'm grasping at straws, and I'm not even sure how to begin 
debugging the issue. The reviewboard user has access to the repository. 
Gitweb access is configured properly... all of the usual suspects aren't 
that suspicious.

I know I've done something wrong. I just don't know what.

Any tips on where to start debugging would be greatly appreciated.
-Kevin

-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
reviewboard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Another The file was not found in the repository Error 207 issue

2014-12-09 Thread Kevin Jones
Yes. Same hash.

More digging showed that creating a review from a new branch via rbt post
works. Attempting to do a post-commit review is where the error occurs.

-Kevin

On Tue, Dec 9, 2014 at 4:46 PM, David Trowbridge trowb...@gmail.com wrote:

 Do master and origin/master point to the same thing?

 -David

 On Tue, Dec 9, 2014 at 10:16 AM, Kevin Jones kjlo...@gmail.com wrote:

 Greetings,

 I'm trying to figure out why a diff, regardless of whether it was created
 with local diff tools or rbt, keeps reporting that it can't find a
 particular revision of a file in the repository.

 Using: Git and reviewboard 2.0.5
 What I've tried:
 rbt diff
 rbt post master changed_branch
 other permutations of the above to load the diff into reviewboard.

 Right now, I'm grasping at straws, and I'm not even sure how to begin
 debugging the issue. The reviewboard user has access to the repository.
 Gitweb access is configured properly... all of the usual suspects aren't
 that suspicious.

 I know I've done something wrong. I just don't know what.

 Any tips on where to start debugging would be greatly appreciated.
 -Kevin

 --
 Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
 ---
 Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
 ---
 Happy user? Let us know at http://www.reviewboard.org/users/
 ---
 You received this message because you are subscribed to the Google Groups
 reviewboard group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to reviewboard+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


  --
 Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
 ---
 Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
 ---
 Happy user? Let us know at http://www.reviewboard.org/users/
 ---
 You received this message because you are subscribed to a topic in the
 Google Groups reviewboard group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/reviewboard/Pewp-yIO9Kc/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 reviewboard+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
reviewboard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: The file something/orother/withsomeextens.ion (revision hexadecimal joy) was not found in the repository

2014-09-24 Thread Kevin Jones
In my attempts to get the command used, the developer informed me that they 
can see the diffs now.

I'm going to assume I fat-fingered the password to the repo in the setup 
and fixed it by reentering it yesterday.

Christian, your help is amazing, and I feel somewhat silly for having 
wasted your time on this. Mea culpa and thank you.

-Kevin

On Tuesday, September 23, 2014 1:14:12 PM UTC-5, Christian Hammond wrote:

 Hi Kevin, 

 A few more questions: 

 1) Can you show me an exact revision string from the error? I'm mostly 
 interested in whether it's a 7-character string (short SHA1) or a full 
 SHA1. 

 2) Is the developer using RBTools (rbt post) to upload the diff? 

 3) If RBTools, can you have the developer `rbt post` with --debug, and 
 provide the information? 

 Christian 

 -- 
 Christian Hammond - chri...@beanbaginc.com javascript: 
 Review Board - https://www.reviewboard.org 
 Beanbag, Inc. - https://www.beanbaginc.com 


 On September 23, 2014 at 8:49:54 AM, Kevin Jones (kjl...@gmail.com 
 javascript:) wrote: 
  Sent via email. Semi-sensitive information. 
  
  -Kevin 
  
  On Monday, September 22, 2014 1:05:32 PM UTC-5, Kevin Jones wrote: 
   
   Greetings, 
   
   I'd like to thank the community for their continued help in attempting 
 to 
   figure out solutions to issues I'm having. I've searched the web for 
   possible solutions to this and haven't found any that have worked. 
   
   We have our repositories on one machine while reviewboard sits on 
 another. 
   The links to the repositories are (I believe) configured correctly, as 
 is 
   user access. However, the error listed in the subject appears when one 
 of 
   my users attempts to post a review. 
   
   I've examined access issues for the reviewboard user, whether or not 
 the 
   repo is set up properly, and about a million other things. Yet still 
 the 
   error persists. 
   
   Attempts to turn on logging are met with read-only access errors. I 
   realize that's probably the most critical piece of data, but what user 
   needs access to write log files? The reviewboard user? 
   
   -Kevin 
   
  
  -- 
  Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ 
  --- 
  Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ 
  --- 
  Happy user? Let us know at http://www.reviewboard.org/users/ 
  --- 
  You received this message because you are subscribed to the Google 
 Groups reviewboard 
  group. 
  To unsubscribe from this group and stop receiving emails from it, send 
 an email to reviewboard...@googlegroups.com javascript:. 
  For more options, visit https://groups.google.com/d/optout. 
  



-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
reviewboard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: The file something/orother/withsomeextens.ion (revision hexadecimal joy) was not found in the repository

2014-09-23 Thread Kevin Jones
Sent via email. Semi-sensitive information.

-Kevin

On Monday, September 22, 2014 1:05:32 PM UTC-5, Kevin Jones wrote:

 Greetings,

 I'd like to thank the community for their continued help in attempting to 
 figure out solutions to issues I'm having. I've searched the web for 
 possible solutions to this and haven't found any that have worked.

 We have our repositories on one machine while reviewboard sits on another. 
 The links to the repositories are (I believe) configured correctly, as is 
 user access. However, the error listed in the subject appears when one of 
 my users attempts to post a review.

 I've examined access issues for the reviewboard user, whether or not the 
 repo is set up properly, and about a million other things. Yet still the 
 error persists. 

 Attempts to turn on logging are met with read-only access errors. I 
 realize that's probably the most critical piece of data, but what user 
 needs access to write log files? The reviewboard user?

 -Kevin


-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
reviewboard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


The file something/orother/withsomeextens.ion (revision hexadecimal joy) was not found in the repository

2014-09-22 Thread Kevin Jones
Greetings,

I'd like to thank the community for their continued help in attempting to 
figure out solutions to issues I'm having. I've searched the web for 
possible solutions to this and haven't found any that have worked.

We have our repositories on one machine while reviewboard sits on another. 
The links to the repositories are (I believe) configured correctly, as is 
user access. However, the error listed in the subject appears when one of 
my users attempts to post a review.

I've examined access issues for the reviewboard user, whether or not the 
repo is set up properly, and about a million other things. Yet still the 
error persists. 

Attempts to turn on logging are met with read-only access errors. I realize 
that's probably the most critical piece of data, but what user needs access 
to write log files? The reviewboard user?

-Kevin

-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
reviewboard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: The file something/orother/withsomeextens.ion (revision hexadecimal joy) was not found in the repository

2014-09-22 Thread Kevin Jones
It's a git repository. I'll get logs set up to see what might be happening.

-Kevin

On Monday, September 22, 2014 1:39:56 PM UTC-5, Christian Hammond wrote:

 Hi Kevin, 

 The log directory must be writable by whatever user your web server runs 
 at (usually www-data or apache, if you're using Apache). 

 What kind of repository is this? 

 Christian 

 -- 
 Christian Hammond - chri...@beanbaginc.com javascript: 
 Review Board - https://www.reviewboard.org 
 Beanbag, Inc. - https://www.beanbaginc.com 


 On September 22, 2014 at 11:05:35 AM, Kevin Jones (kjl...@gmail.com 
 javascript:) wrote: 
  Greetings, 
  
  I'd like to thank the community for their continued help in attempting 
 to 
  figure out solutions to issues I'm having. I've searched the web for 
  possible solutions to this and haven't found any that have worked. 
  
  We have our repositories on one machine while reviewboard sits on 
 another. 
  The links to the repositories are (I believe) configured correctly, as 
 is 
  user access. However, the error listed in the subject appears when one 
 of 
  my users attempts to post a review. 
  
  I've examined access issues for the reviewboard user, whether or not the 
  repo is set up properly, and about a million other things. Yet still the 
  error persists. 
  
  Attempts to turn on logging are met with read-only access errors. I 
 realize 
  that's probably the most critical piece of data, but what user needs 
 access 
  to write log files? The reviewboard user? 
  
  -Kevin 
  
  -- 
  Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ 
  --- 
  Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ 
  --- 
  Happy user? Let us know at http://www.reviewboard.org/users/ 
  --- 
  You received this message because you are subscribed to the Google 
 Groups reviewboard 
  group. 
  To unsubscribe from this group and stop receiving emails from it, send 
 an email to reviewboard...@googlegroups.com javascript:. 
  For more options, visit https://groups.google.com/d/optout. 
  



-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
reviewboard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Illegal mix of collations error being emailed from reviewboard

2014-07-31 Thread Kevin Jones
/python2.6/dist-packages/Django-1.6.5-py2.6.egg/django/db/models/sql/query.py,
 
line 390, in get_count

number = obj.get_aggregation(using=using)[None]

 

  File 
/usr/local/lib/python2.6/dist-packages/Django-1.6.5-py2.6.egg/django/db/models/sql/query.py,
 
line 356, in get_aggregation

result = query.get_compiler(using).execute_sql(SINGLE)

 

  File 
/usr/local/lib/python2.6/dist-packages/Django-1.6.5-py2.6.egg/django/db/models/sql/compiler.py,
 
line 786, in execute_sql

cursor.execute(sql, params)

 

  File 
/usr/local/lib/python2.6/dist-packages/Django-1.6.5-py2.6.egg/django/db/backends/util.py,
 
line 53, in execute

return self.cursor.execute(sql, params)

 

  File 
/usr/local/lib/python2.6/dist-packages/Django-1.6.5-py2.6.egg/django/db/utils.py,
 
line 99, in __exit__

six.reraise(dj_exc_type, dj_exc_value, traceback)

 

  File 
/usr/local/lib/python2.6/dist-packages/Django-1.6.5-py2.6.egg/django/db/backends/util.py,
 
line 53, in execute

return self.cursor.execute(sql, params)

 

  File 
/usr/local/lib/python2.6/dist-packages/Django-1.6.5-py2.6.egg/django/db/backends/mysql/base.py,
 
line 124, in execute

return self.cursor.execute(query, args)

 

  File /usr/lib/pymodules/python2.6/MySQLdb/cursors.py, line 166, in 
execute

self.errorhandler(self, exc, value)

 

  File /usr/lib/pymodules/python2.6/MySQLdb/connections.py, line 35, in 
defaulterrorhandler

raise errorclass, errorvalue

 

OperationalError: (1267, Illegal mix of collations 
(latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation 
'like')

 

 

WSGIRequest

path:/reviewboard/api/users/,

GET:QueryDict: {u'q': [u'\u310d\u311f'], u'timestamp': [u'1406790482470'], 
u'fullname': [u'1'], u'limit': [u'150']},

POST:QueryDict: {},

COOKIES:{'collapsediffs': 'True',

 'csrftoken': 'h52J5ERI1Wli9hYLKNVdRFMKBVqjPybS',

 'rbsessionid': 'nb1owxohc5ocrjvucaq82rthkwrkn4rj'},

META:{'DOCUMENT_ROOT': '/var/www/reviewboard.x.com/htdocs',

 'GATEWAY_INTERFACE': 'CGI/1.1',

 'HTTP_ACCEPT': '*/*',

 'HTTP_ACCEPT_ENCODING': 'gzip,deflate,sdch',

 'HTTP_ACCEPT_LANGUAGE': 'zh-TW,zh;q=0.8,en-US;q=0.6,en;q=0.4,zh-CN;q=0.2',

 'HTTP_CONNECTION': 'keep-alive',

 'HTTP_COOKIE': 'rbsessionid=nb1owxohc5ocrjvucaq82rthkwrkn4rj; 
csrftoken=h52J5ERI1Wli9hYLKNVdRFMKBVqjPybS; collapsediffs=True',

 'HTTP_HOST': 'bedlam',

 'HTTP_REFERER': 'http:///reviewboard/r/31/',

 'HTTP_USER_AGENT': 'Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 
(KHTML, like Gecko) Chrome/36.0.1985.125 Safari/537.36',

 'HTTP_X_REQUESTED_WITH': 'XMLHttpRequest',

 'PATH': '/usr/local/bin:/usr/bin:/bin',

 'PATH_INFO': u'/reviewboard/api/users/',

 'PATH_TRANSLATED': 
'/var/www/reviewboard.xxx.com/htdocs/reviewboard.wsgi/reviewboard/api/users/',

 'QUERY_STRING': 
'q=%E3%84%8D%E3%84%9Flimit=150timestamp=1406790482470fullname=1',

 'REMOTE_ADDR': '10.11.0.65',

 'REMOTE_PORT': '57736',

 'REQUEST_METHOD': 'GET',

 'REQUEST_URI': 
'/reviewboard/api/users/?q=%E3%84%8D%E3%84%9Flimit=150timestamp=1406790482470fullname=1',

 'SCRIPT_FILENAME': 
'/var/www/reviewboard.xx.com/htdocs/reviewboard.wsgi',

 'SCRIPT_NAME': u'',

 'SERVER_ADDR': '10.0.50.11',

 'SERVER_ADMIN': '[no address given]',

 'SERVER_NAME': 'x',

 'SERVER_PORT': '80',

 'SERVER_PROTOCOL': 'HTTP/1.1',

 'SERVER_SIGNATURE': 'addressApache/2.2.14 (Ubuntu) Server at 
xxPort 80/address\n',

 'SERVER_SOFTWARE': 'Apache/2.2.14 (Ubuntu)',

 'mod_wsgi.application_group': '|',

 'mod_wsgi.callable_object': 'application',

 'mod_wsgi.listener_host': '',

 'mod_wsgi.listener_port': '80',

 'mod_wsgi.process_group': '',

 'mod_wsgi.reload_mechanism': '0',

 'mod_wsgi.script_reloading': '1',

 'mod_wsgi.version': (2, 8),

 'wsgi.errors': mod_wsgi.Log object at 0x2391ebe0,

 'wsgi.file_wrapper': built-in method file_wrapper of mod_wsgi.Adapter 
object at 0x23a4e698,

 'wsgi.input': mod_wsgi.Input object at 0x23733980,

 'wsgi.multiprocess': True,

 'wsgi.multithread': True,

 'wsgi.run_once': False,

 'wsgi.url_scheme': 'http',

 'wsgi.version': (1, 0)}
I've obfuscated the company-specific bits of the above. I'm using Mysql, 
and apparently there's conflict between Latin1 and utf8 somewhere in the 
query. If anyone has suggestions on how to resolve this such that I don't 
get strange errors, I'd appreciate it. 

-Kevin

-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
reviewboard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Can't log in after new site install

2014-07-27 Thread Kevin Jones
Greetings,

After an unexpected crash of a disk destroyed our old reviewboard site, I 
decided to move to a new 2.0.5 instance. After some unsuccessful first 
attempts, I finally got the site visible. However, attempts to log in with 
admin to attempt to manage the site don't produce an expected Manage link 
in the upper right corner. I know the username/password combo is working 
because an altered password fails to validate.

To try and fix this, I created a superuser with the manage command and 
tried to log in as that. Same issue with that user. Attempt to log in, get 
taken to the default site with the Log In link in the upper right. 

Of course, since I can't get into admin functions to turn on logging, I 
can't tell what exactly is going on. The apache log isn't giving any hints, 
so I'm asking for any sort of oh, yeah, I've seen this before help I can 
get.

Thanks in advance,
Kevin

-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
reviewboard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Authentication - Subversion

2014-07-14 Thread Kevin Norton
It might be because of certificate. Have you tried saving sssl cert for 
your repo. You can force this I believe by executing and SVN command via 
command line.



On Monday, July 7, 2014 11:45:52 PM UTC-7, shravanthi s wrote:

 I am facing a similar issue. But my login credentials are correct and am 
 able to access the svn repo link directly. However its not letting me add a 
 repository and gives an authentication failed error. Any idea what is going 
 wrong here? My review board log is as follows

  'ERROR -  - SVN: Failed to get repository information for 
 https://test.com/svn/adis: callback_get_login required'

 On Wednesday, 14 September 2011 21:20:36 UTC+5:30, hs_etd wrote:

 I am trying to add a repository in Subversion. After entering in the 
 path to the repository which looks like svn://xxx.yyy.net/zzz, I click 
 Save but I always get the error Authentication failed. 

 I look at the /etc/httpd/logs/error_log file and it says Failed to 
 get repository information for svn://xxx.yyy.net/zzz: 
 callback_get_login required 

 Thanks for any pointers on what I need to do.



-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
reviewboard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Error: Error applying evolution: (1051, Unknown table 'auth_message')

2014-03-24 Thread Kevin Phillips
Post the failed upgrade dump. How is the migration not working? You are 
going to have to do some leg work on your end to get this working.

On Monday, March 24, 2014 9:38:09 AM UTC-7, Bhaskar Roy wrote:

 It is not working.
 I am stuck with migration from old server to new server.

 /Bhaskar 

 On Sunday, 23 March 2014 02:19:22 UTC+5:30, Kevin Phillips wrote:


 The devs changed the format to:
 DATABASES = {
  'default' : {
   'ENGINE': 'django.db.backends,mysql',
   'NAME': '',
   'USER': '',
   'PASSWORD': '',
   'HOST': '',
  },
 }

 The caches format has changed similarly. Note that the caches location 
 has dropped the URI.
 # Cache backend settings.
 CACHES = {
 'default': {
 'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache',
 'LOCATION': 'localhost:11211',
 },
 }

 On Wednesday, March 19, 2014 8:48:23 PM UTC-7, Bhaskar Roy wrote:

 Hi Kevin,

 What changes I need to make for the points mentioned below line?

 admin@remotehost2:~$ sudo cp 
 /var/www/reviewboard-1.7.14/conf/settings_local.py /home/admin
 admin@remotehost2:~$ vim /home/admin/settings_local.py (make the 
 mentioned changes from my thread


 My current settings file looks like this.

 # Site-specific configuration settings for Review Board
 # Definitions of these settings can be found at
 # http://docs.djangoproject.com/en/dev/ref/settings/

 # Database configuration
 DATABASES = {
 'default': {
 'ENGINE': 'django.db.backends.mysql',
 'NAME': 'reviewboard',
 'USER': 'root',
 'PASSWORD': 'password',
 'HOST': 'localhost',
 },
 }

 # Unique secret key. Don't share this with anybody.
 SECRET_KEY = 'ic%zzz9a#p_m#1=lip_5_1mkidljkgh89090t@s93fku#kdh@c'

 # Cache backend settings.
 CACHE_BACKEND = 'memcached://localhost:11211/'

 # Extra site information.
 SITE_ID = 1
 SITE_ROOT = '/'
 FORCE_SCRIPT_NAME = ''
 DEBUG = True



 On Thu, Mar 20, 2014 at 3:48 AM, Kevin Phillips 
 kevin.grenvi...@gmail.com wrote:

 admin@remotehost1:~$ export REVIEWBOARD_DB_NAME=review
 admin@remotehost1:~$ mysqldump  -u backup -p  --max_allowed_packet=512M 
 $REVIEWBOARD_DB_NAME  /tmp/reviewboard-`date`.sql
 admin@remotehost1:~$ scp /tmp/reviewboard-`date`.sql 
 admin@remotehost2:/tmp/
 admin@remotehost1:~$ scp -r /var/www/reviewboard-1.5.2 
 admin@remotehost2:/var/www/reviewboard-1.7.14

 admin@remotehost2:~$ sudo apt-get install mysql-server 
 libmysqlclient-dev memcached ntpd apache2 libapach2-mod-wsgi 
 libapache2-mod-python
 admin@remotehost2:~$ sudo easy_install Reviewboard==1.7.14 
 Django==1.4.10 python-memcached MySQL-Python
 admin@remotehost2:~$ sudo easy_install -m Reviewboard==1.7.14
 admin@remotehost2:~$ sudo cp 
 /var/www/reviewboard-1.7.14/conf/settings_local.py /home/admin
 admin@remotehost2:~$ vim /home/admin/settings_local.py (make the 
 mentioned changes from my thread)
 admin@remotehost2:~$ sudo cp /home/admin/settings_local.py 
 /usr/local/lib/python2.7/dist-packages/Reviewboard-1.7.14-py2.7.egg/reviewboard/
 admin@remotehost2:~$ mysql -u root -p
 mysql create database review;
 mysql create user 'review'@'localhost' identified by 'password';
 mysql grant all on review.* to 'review'@'localhost';
 admin@remotehost2:~$ mysql --max_allowed_packet=128M -u review -p 
 review  /tmp/reviewboard-`date`.sql
 admin@remotehost2:~$ mysql -u root -p review
 mysql show table status
 mysql alter table `table_name` engine='InnoDB'; (there are definitely 
 faster ways, but I can't spoon feed you everything...)
 admin@remotehost2:~$ sudo rb-site --version (confirm you are at 1.7.14) 
 admin@remotehost2:~$ sudo rb-site upgrade /var/www/reviewboard-1.7.14
 For Apache, you will need to add:

 Location /review/static
 SetHandler None
 /Location

 Alias /review/static 
 /var/www/reviewboard-1.7.14/htdocs/statichttp://review.company.com/htdocs/static
 

 For lighttpd:

 alias.url = (
 ...
 /review/static = /var/www/review.company.com/htdocs/static
 ,
 ...
 )

 url.rewrite-once = (
 ...
 ^(/review/static/.*)$ = $1,
 ...
 )

 Once you have made these changes, type the following
 to resolve this:

 $ rb-site manage /var/www/r 
 http://review.company.com/eviewboard-1.7.14 resolve-check 
 static-media

 Make the changes...
 admin@remotehost2:~$ ln -s /var/www/reviewboard-1.7.14 /var/www/review
 admin@remotehost2:~$ rb-site manage /var/www/reviewboard-1.7.14 
 resolve-check static-media
 And for good measure...
 admin@remotehost2:~$ rb-site manage /var/www/reviewboard-1.7.14 syncdb

 Hope that helps,

 KP


 On Wednesday, March 19, 2014 3:11:13 AM UTC-7, Bhaskar Roy wrote:

 Hi Kevin,

 I did what you said but I am on same page.

 Can you please provide the procedure to do migration.


 regards
 bahskar 


 On Wed, Mar 19, 2014 at 12:38 AM, Kevin Phillips kevin.grenvi...@
 gmail.com wrote:

 Your database dump appears incomplete. Try dumping with 
 --max_allowed_packet=512M (large packet to avoid

Re: Error: Error applying evolution: (1051, Unknown table 'auth_message')

2014-03-22 Thread Kevin Phillips

The devs changed the format to:
DATABASES = {
 'default' : {
  'ENGINE': 'django.db.backends,mysql',
  'NAME': '',
  'USER': '',
  'PASSWORD': '',
  'HOST': '',
 },
}

The caches format has changed similarly. Note that the caches location has 
dropped the URI.
# Cache backend settings.
CACHES = {
'default': {
'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache',
'LOCATION': 'localhost:11211',
},
}

On Wednesday, March 19, 2014 8:48:23 PM UTC-7, Bhaskar Roy wrote:

 Hi Kevin,

 What changes I need to make for the points mentioned below line?

 admin@remotehost2:~$ sudo cp 
 /var/www/reviewboard-1.7.14/conf/settings_local.py /home/admin
 admin@remotehost2:~$ vim /home/admin/settings_local.py (make the mentioned 
 changes from my thread


 My current settings file looks like this.

 # Site-specific configuration settings for Review Board
 # Definitions of these settings can be found at
 # http://docs.djangoproject.com/en/dev/ref/settings/

 # Database configuration
 DATABASES = {
 'default': {
 'ENGINE': 'django.db.backends.mysql',
 'NAME': 'reviewboard',
 'USER': 'root',
 'PASSWORD': 'password',
 'HOST': 'localhost',
 },
 }

 # Unique secret key. Don't share this with anybody.
 SECRET_KEY = 'ic%zzz9a#p_m#1=lip_5_1mkidljkgh89090t@s93fku#kdh@c'

 # Cache backend settings.
 CACHE_BACKEND = 'memcached://localhost:11211/'

 # Extra site information.
 SITE_ID = 1
 SITE_ROOT = '/'
 FORCE_SCRIPT_NAME = ''
 DEBUG = True



 On Thu, Mar 20, 2014 at 3:48 AM, Kevin Phillips 
 kevin.grenvi...@gmail.comjavascript:
  wrote:

 admin@remotehost1:~$ export REVIEWBOARD_DB_NAME=review
 admin@remotehost1:~$ mysqldump  -u backup -p  --max_allowed_packet=512M 
 $REVIEWBOARD_DB_NAME  /tmp/reviewboard-`date`.sql
 admin@remotehost1:~$ scp /tmp/reviewboard-`date`.sql 
 admin@remotehost2:/tmp/
 admin@remotehost1:~$ scp -r /var/www/reviewboard-1.5.2 
 admin@remotehost2:/var/www/reviewboard-1.7.14

 admin@remotehost2:~$ sudo apt-get install mysql-server libmysqlclient-dev 
 memcached ntpd apache2 libapach2-mod-wsgi libapache2-mod-python
 admin@remotehost2:~$ sudo easy_install Reviewboard==1.7.14 Django==1.4.10 
 python-memcached MySQL-Python
 admin@remotehost2:~$ sudo easy_install -m Reviewboard==1.7.14
 admin@remotehost2:~$ sudo cp 
 /var/www/reviewboard-1.7.14/conf/settings_local.py /home/admin
 admin@remotehost2:~$ vim /home/admin/settings_local.py (make the 
 mentioned changes from my thread)
 admin@remotehost2:~$ sudo cp /home/admin/settings_local.py 
 /usr/local/lib/python2.7/dist-packages/Reviewboard-1.7.14-py2.7.egg/reviewboard/
 admin@remotehost2:~$ mysql -u root -p
 mysql create database review;
 mysql create user 'review'@'localhost' identified by 'password';
 mysql grant all on review.* to 'review'@'localhost';
 admin@remotehost2:~$ mysql --max_allowed_packet=128M -u review -p review 
  /tmp/reviewboard-`date`.sql
 admin@remotehost2:~$ mysql -u root -p review
 mysql show table status
 mysql alter table `table_name` engine='InnoDB'; (there are definitely 
 faster ways, but I can't spoon feed you everything...)
 admin@remotehost2:~$ sudo rb-site --version (confirm you are at 1.7.14) 
 admin@remotehost2:~$ sudo rb-site upgrade /var/www/reviewboard-1.7.14
 For Apache, you will need to add:

 Location /review/static
 SetHandler None
 /Location

 Alias /review/static 
 /var/www/reviewboard-1.7.14/htdocs/statichttp://review.company.com/htdocs/static
 

 For lighttpd:

 alias.url = (
 ...
 /review/static = /var/www/review.company.com/htdocs/static,
 ...
 )

 url.rewrite-once = (
 ...
 ^(/review/static/.*)$ = $1,
 ...
 )

 Once you have made these changes, type the following
 to resolve this:

 $ rb-site manage /var/www/r 
 http://review.company.com/eviewboard-1.7.14 resolve-check 
 static-media

 Make the changes...
 admin@remotehost2:~$ ln -s /var/www/reviewboard-1.7.14 /var/www/review
 admin@remotehost2:~$ rb-site manage /var/www/reviewboard-1.7.14 
 resolve-check static-media
 And for good measure...
 admin@remotehost2:~$ rb-site manage /var/www/reviewboard-1.7.14 syncdb

 Hope that helps,

 KP


 On Wednesday, March 19, 2014 3:11:13 AM UTC-7, Bhaskar Roy wrote:

 Hi Kevin,

 I did what you said but I am on same page.

 Can you please provide the procedure to do migration.


 regards
 bahskar 


 On Wed, Mar 19, 2014 at 12:38 AM, Kevin Phillips kevin.grenvi...@
 gmail.com wrote:

 Your database dump appears incomplete. Try dumping with 
 --max_allowed_packet=512M (large packet to avoid truncation). Check your 
 1.5.X db and verify the table exists in production and in the backup. Also 
 verify all your tables are InnoDB instead of MYISAM, you can make manual 
 modification to the table engine without much recourse. 

 Take a look at my thread, I just migrated 1.5.2 to 1.7.14 on the same 
 platform as you.

 KP


 On Tuesday, March 18, 2014 2:31:44 AM UTC-7

Re: Site Migration Issues from 1.5.2 to 1.7.14

2014-03-19 Thread Kevin Phillips
The 1050 error from django was due to changes in to configuration file 
format. Instead of using the format:
DATABASE_ENGINE = '',
DATABASE_NAME='',
.
.
.

The devs changed the format to:
DATABASES = {
 'default' : {
  'ENGINE': 'django.db.backends,mysql',
  'NAME': '',
  'USER': '',
  'PASSWORD': '',
  'HOST': '',
 },
}

The caches format has changed similarly. 
# Cache backend settings.
CACHES = {
'default': {
'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache',
'LOCATION': 'localhost:11211',
},
}

Have you verified the integrity of your dump? If so, you should not have to 
drop your tables just convert them all to InnoDB. If you don't convert your 
tables you will see sql errors when the upgrade script attempts to create 
primary keys in the database.

KP

On Wednesday, March 19, 2014 3:09:29 AM UTC-7, Bhaskar Roy wrote:

 Hi Kevin,

 Can I know how you performed these steps.

 5. Upgrade failed with a 1050 (or similar) error because it couldn't 
 access some table. So I temporarily overrode django's default database 
 handler to use mysql + client configs in my.cnf (only a single site will 
 reside on this VM) via django's conf/global_settings.py, I then ran 
 './reviewboard/manage.py syncdb'.
 6. syncdb also failed, so I dropped all my tables and re-ran the syncdb.

 regards
 Bhaskar 

 On Friday, 14 March 2014 23:20:27 UTC+5:30, Kevin Phillips wrote:

 All;

 I'm having some issues performing a site migration of RB 1.5.2 to 1.7.14 
 from an EOL server to a VM. Here are the steps I preformed:

 1. Took SQL dump of reviewboard database and restored on new system
 2. Took copy of application web root and copied to new system
 3. Configured memcached on new system.
 3. Installed Reviewboard==1.7.14 Django==1.4.10 python-memcached 
 MySQL-python + deps via easy_install (Python 2.7.3)
 4. Preformed a rb-site upgrade of application web root.
 5. Upgrade failed with a 1050 (or similar) error because it couldn't 
 access some table. So I temporarily overrode django's default database 
 handler to use mysql + client configs in my.cnf (only a single site will 
 reside on this VM) via django's conf/global_settings.py, I then ran 
 './reviewboard/manage.py syncdb'.
 6. syncdb also failed, so I dropped all my tables and re-ran the syncdb.
 7. The second syncdb after dropping my tables worked, then I re-ran the 
 rb-site upgrade
 8. The second rb-site upgrade was successful but prompted me to modify my 
 apache vhost config and validate the site settings.
 9. I actioned the changes and restarted the web server.

 After this I get the error 500 page but I get a mod_python stack trace 
 (yes I know mod_python is simply in there for legacy purposes, but the old 
 site ran it and I cannot figure out how to cut-over to mod_wsgi).

 STACKTRACE:
 [Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] mod_python 
 (pid=2342, interpreter='reviewboard_review_vmem_com', 
 phase='PythonHandler', handler='django.core.handlers.modpython'): 
 Application error, referer: http://reviewboard.sub.domain/review/
 [Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] ServerName: 
 'reviewboard.sub.domain', referer: http://reviewboard.sub.domain/review/
 [Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] DocumentRoot: 
 '/var/www/review.vmem.com/htdocs', referer: 
 http://reviewboard.sub.domain/review/
 [Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] URI: '/review/', 
 referer: http://reviewboard.sub.domain/review/
 [Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] Location: 
 '/review/', referer: http://reviewboard.sub.domain/review/
 [Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] Directory: None, 
 referer: http://reviewboard.sub.domain/review/
 [Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] Filename: 
 '/var/www/review.vmem.com/htdocs/review', referer: 
 http://reviewboard.sub.domain/review/
 [Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] PathInfo: '/', 
 referer: http://reviewboard.sub.domain/review/
 [Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] Traceback (most 
 recent call last):, referer: http://reviewboard.sub.domain/review/
 [Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48]   File 
 /usr/lib/python2.7/dist-packages/mod_python/importer.py, line 1537, in 
 HandlerDispatch\ndefault=default_handler, arg=req, 
 silent=hlist.silent), referer: http://reviewboard.sub.domain/review/
 [Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48]   File 
 /usr/lib/python2.7/dist-packages/mod_python/importer.py, line 1202, in 
 _process_target\nmodule = import_module(module_name, path=path), 
 referer: http://reviewboard.sub.domain/review/
 [Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48]   File 
 /usr/lib/python2.7/dist-packages/mod_python/importer.py, line 304, in 
 import_module\nreturn __import__(module_name, {}, {}, ['*']), referer: 
 http://reviewboard.sub.domain/review/
 [Fri Mar 14 09:48:18 2014] [error] [client

Re: Error: Error applying evolution: (1051, Unknown table 'auth_message')

2014-03-19 Thread Kevin Phillips
admin@remotehost1:~$ export REVIEWBOARD_DB_NAME=review
admin@remotehost1:~$ mysqldump  -u backup -p  --max_allowed_packet=512M 
$REVIEWBOARD_DB_NAME  /tmp/reviewboard-`date`.sql
admin@remotehost1:~$ scp /tmp/reviewboard-`date`.sql admin@remotehost2:/tmp/
admin@remotehost1:~$ scp -r /var/www/reviewboard-1.5.2 
admin@remotehost2:/var/www/reviewboard-1.7.14

admin@remotehost2:~$ sudo apt-get install mysql-server libmysqlclient-dev 
memcached ntpd apache2 libapach2-mod-wsgi libapache2-mod-python
admin@remotehost2:~$ sudo easy_install Reviewboard==1.7.14 Django==1.4.10 
python-memcached MySQL-Python
admin@remotehost2:~$ sudo easy_install -m Reviewboard==1.7.14
admin@remotehost2:~$ sudo cp 
/var/www/reviewboard-1.7.14/conf/settings_local.py /home/admin
admin@remotehost2:~$ vim /home/admin/settings_local.py (make the mentioned 
changes from my thread)
admin@remotehost2:~$ sudo cp /home/admin/settings_local.py 
/usr/local/lib/python2.7/dist-packages/Reviewboard-1.7.14-py2.7.egg/reviewboard/
admin@remotehost2:~$ mysql -u root -p
mysql create database review;
mysql create user 'review'@'localhost' identified by 'password';
mysql grant all on review.* to 'review'@'localhost';
admin@remotehost2:~$ mysql --max_allowed_packet=128M -u review -p review  
/tmp/reviewboard-`date`.sql
admin@remotehost2:~$ mysql -u root -p review
mysql show table status
mysql alter table `table_name` engine='InnoDB'; (there are definitely 
faster ways, but I can't spoon feed you everything...)
admin@remotehost2:~$ sudo rb-site --version (confirm you are at 1.7.14) 
admin@remotehost2:~$ sudo rb-site upgrade /var/www/reviewboard-1.7.14
For Apache, you will need to add:

Location /review/static
SetHandler None
/Location

Alias /review/static 
/var/www/reviewboard-1.7.14/htdocs/statichttp://review.company.com/htdocs/static


For lighttpd:

alias.url = (
...
/review/static = /var/www/review.company.com/htdocs/static,
...
)

url.rewrite-once = (
...
^(/review/static/.*)$ = $1,
...
)

Once you have made these changes, type the following
to resolve this:

$ rb-site manage /var/www/r http://review.company.com/eviewboard-1.7.14 
resolve-check 
static-media

Make the changes...
admin@remotehost2:~$ ln -s /var/www/reviewboard-1.7.14 /var/www/review
admin@remotehost2:~$ rb-site manage /var/www/reviewboard-1.7.14 
resolve-check static-media
And for good measure...
admin@remotehost2:~$ rb-site manage /var/www/reviewboard-1.7.14 syncdb

Hope that helps,

KP


On Wednesday, March 19, 2014 3:11:13 AM UTC-7, Bhaskar Roy wrote:

 Hi Kevin,

 I did what you said but I am on same page.

 Can you please provide the procedure to do migration.


 regards
 bahskar 


 On Wed, Mar 19, 2014 at 12:38 AM, Kevin Phillips 
 kevin.grenvi...@gmail.com javascript: wrote:

 Your database dump appears incomplete. Try dumping with 
 --max_allowed_packet=512M (large packet to avoid truncation). Check your 
 1.5.X db and verify the table exists in production and in the backup. Also 
 verify all your tables are InnoDB instead of MYISAM, you can make manual 
 modification to the table engine without much recourse. 

 Take a look at my thread, I just migrated 1.5.2 to 1.7.14 on the same 
 platform as you.

 KP


 On Tuesday, March 18, 2014 2:31:44 AM UTC-7, Bhaskar Roy wrote:

 Hi Christian,

 I am trying migration on new server and not in current production box. 

 1. On new server I installed ubuntu 12.04/mysql 5.5/RB 1.7.14
 1. I took backup of SQL and copied to new server and done rb-site 
 upgrade.

 Copied the databse to new server and tired . I get error messages as 
 listed above.

 regards
 Bhaskar 


 On Thu, Mar 13, 2014 at 12:53 AM, Christian Hammond 
 chi...@chipx86.comwrote:

  Hi,

 First, did you back up your database?

 Second, can you verify the version of Review Board you've upgraded to, 
 and also verify the version of django-evolution installed? (These should 
 be 
 in your Python's site-packages directory).

 You shouldn't do *any* hand-modifying of the database of any sort, or 
 you'll cause further issues in the upgrade process. Our stuff expects to 
 own the full schema of the database.

 Christian

 -- 
 Christian Hammond - chi...@chipx86.com

 Review Board - http://www.reviewboard.org
 Beanbag, Inc. - http://www.beanbaginc.com


 On Wed, Mar 12, 2014 at 3:23 AM, Bhaskar Roy bhaska...@gmail.comwrote:

  Hi Christian,

 I am getting following error while doing site upgrade from 1.5 to 
 Latest 1.7.
 Even created auth_message tablein MySqL DB.


 /usr/bin/python /usr/local/bin/rb-site upgrade /var/www/reviewboard
 Rebuilding directory structure
 Updating database. This may take a while.

 The log output below, including warnings and errors,
 can be ignored unless upgrade fails.

 -- begin log output --
 Creating tables ...
 There are unapplied evolutions for auth.
 There are unapplied evolutions for sessions.
 There are unapplied evolutions

Re: Site Installation Failing with database error.

2014-03-19 Thread Kevin Phillips
Christian;

Could he not just modify his settings_local.py to reflect to updates to the 
file format. The specific errors are for CACHES and DATABASES which are 
defined in that file. I understand Django-1.4 is not supposed to be 
supported.

KP

On Thursday, August 30, 2012 4:25:36 PM UTC-7, Christian Hammond wrote:

 Hi,

 You'll need to remove Django 1.4 and downgrade to 1.3.3. Only the upcoming 
 Review Board 1.7 betas support Django 1.4.

 I assume you're upgrading to the latest 1.6, and not 1.7 beta?

 Christian

 -- 
 Christian Hammond - chi...@chipx86.com javascript:
 Review Board - http://www.reviewboard.org
 VMware, Inc. - http://www.vmware.com


 On Thu, Aug 30, 2012 at 2:53 PM, CudaPrime cuda...@gmail.comjavascript:
  wrote:

 Hi all, any help would be appreciated here. I'm a complete noob to Review 
 Board and it's installation. That said I've been tasked with upgrading our 
 current 1.5.5 installation to the most current.
 I've created a test machine and loaded CentOS 6.3, installed the 
 dependencies I know about from the installation documentation, and finally 
 succeeded in getting ReviewBoard installed, at least I'm pretty sure it's 
 installed.

 When I attempt to run rb-site install /var/www/reviewboard

 I get this;
 * Installing the site...
 Building site directories ... OK
 Building site configuration files ... OK
 /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.egg/django/conf/__init__.py:75:
  
 DeprecationWarning: The ADMIN_MEDIA_PREFIX setting has been removed; use 
 STATIC_URL instead.
   use STATIC_URL instead., DeprecationWarning)
 /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.egg/django/core/cache/__init__.py:82:
  
 DeprecationWarning: settings.CACHE_* is deprecated; use settings.CACHES 
 instead.
   DeprecationWarning
 Creating database ... Traceback (most recent call last):
   File /usr/bin/rb-site, line 8, in module
 load_entry_point('ReviewBoard==1.5.5', 'console_scripts', 'rb-site')()
   File 
 /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-py2.6.egg/reviewboard/cmdline/rbsite.py,
  
 line 1611, in main
 command.run()
   File 
 /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-py2.6.egg/reviewboard/cmdline/rbsite.py,
  
 line 1177, in run
 self.show_install_status()
   File 
 /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-py2.6.egg/reviewboard/cmdline/rbsite.py,
  
 line 1436, in show_install_status
 site.sync_database)
   File 
 /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-py2.6.egg/reviewboard/cmdline/rbsite.py,
  
 line 703, in step
 func()
   File 
 /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-py2.6.egg/reviewboard/cmdline/rbsite.py,
  
 line 339, in sync_database
 self.run_manage_command(syncdb, params)
   File 
 /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-py2.6.egg/reviewboard/cmdline/rbsite.py,
  
 line 397, in run_manage_command
 execute_manager(reviewboard.settings, [__file__, cmd] + params)
   File 
 /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.egg/django/core/management/__init__.py,
  
 line 459, in execute_manager
 utility.execute()
   File 
 /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.egg/django/core/management/__init__.py,
  
 line 382, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File 
 /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.egg/django/core/management/base.py,
  
 line 196, in run_from_argv
 self.execute(*args, **options.__dict__)
   File 
 /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.egg/django/core/management/base.py,
  
 line 232, in execute
 output = self.handle(*args, **options)
   File 
 /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.egg/django/core/management/base.py,
  
 line 371, in handle
 return self.handle_noargs(**options)
   File 
 /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.egg/django/core/management/commands/syncdb.py,
  
 line 57, in handle_noargs
 cursor = connection.cursor()
   File 
 /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.egg/django/db/backends/dummy/base.py,
  
 line 15, in complain
 raise ImproperlyConfigured(settings.DATABASES is improperly 
 configured. 
 django.core.exceptions.ImproperlyConfigured: settings.DATABASES is 
 improperly configured. Please supply the ENGINE value. Check settings 
 documentation for more details.

 It appears that django can't properly access mySQL to create it's 
 database, I've checked and rechecked and I can access the database via 
 command line, so I'm not sure why the site installion would be having a 
 problem.

 Thanks in advance for any help!

 -- 
 Want to help the Review Board project? Donate today at 
 http://www.reviewboard.org/donate/
 Happy user? Let us know at http://www.reviewboard.org/users/
 -~--~~~~--~~--~--~---
 To unsubscribe from this group, send email to 
 reviewboard...@googlegroups.com javascript:
 For more options, visit this group at 
 

Re: Site Installation Failing with database error.

2014-03-19 Thread Kevin Phillips
Doh, I should have realized. Thanks for filling me in.

KP

On Wednesday, March 19, 2014 4:30:01 PM UTC-7, Christian Hammond wrote:

 Review Board 1.5 will flat-out fail with Django 1.4. Django goes through 
 deprecation processes in their releases, and we're using a number of things 
 in RB 1.5 that are gone in Django 1.4, and other things that have changed. 
 Updating settings_local.py wouldn't be sufficient.

 This is also true with our versions of Djblets, and some other 
 dependencies we use.

 Christian

 -- 
 Christian Hammond - chi...@chipx86.com javascript:
 Review Board - http://www.reviewboard.org
 Beanbag, Inc. - http://www.beanbaginc.com
  

 On Wed, Mar 19, 2014 at 3:20 PM, Kevin Phillips 
 kevin.grenvi...@gmail.comjavascript:
  wrote:

 Christian;

 Could he not just modify his settings_local.py to reflect to updates to 
 the file format. The specific errors are for CACHES and DATABASES which are 
 defined in that file. I understand Django-1.4 is not supposed to be 
 supported.

 KP


 On Thursday, August 30, 2012 4:25:36 PM UTC-7, Christian Hammond wrote:

 Hi,

 You'll need to remove Django 1.4 and downgrade to 1.3.3. Only the 
 upcoming Review Board 1.7 betas support Django 1.4.

 I assume you're upgrading to the latest 1.6, and not 1.7 beta?

 Christian

 -- 
 Christian Hammond - chi...@chipx86.com

 Review Board - http://www.reviewboard.org
 VMware, Inc. - http://www.vmware.com


 On Thu, Aug 30, 2012 at 2:53 PM, CudaPrime cuda...@gmail.com wrote:

  Hi all, any help would be appreciated here. I'm a complete noob to 
 Review Board and it's installation. That said I've been tasked with 
 upgrading our current 1.5.5 installation to the most current.
 I've created a test machine and loaded CentOS 6.3, installed the 
 dependencies I know about from the installation documentation, and finally 
 succeeded in getting ReviewBoard installed, at least I'm pretty sure it's 
 installed.

 When I attempt to run rb-site install /var/www/reviewboard

 I get this;
 * Installing the site...
 Building site directories ... OK
 Building site configuration files ... OK
 /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
 egg/django/conf/__init__.py:75: DeprecationWarning: The 
 ADMIN_MEDIA_PREFIX setting has been removed; use STATIC_URL instead.
   use STATIC_URL instead., DeprecationWarning)
 /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
 egg/django/core/cache/__init__.py:82: DeprecationWarning: 
 settings.CACHE_* is deprecated; use settings.CACHES instead.
   DeprecationWarning
 Creating database ... Traceback (most recent call last):
   File /usr/bin/rb-site, line 8, in module
 load_entry_point('ReviewBoard==1.5.5', 'console_scripts', 
 'rb-site')()
   File /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-
 py2.6.egg/reviewboard/cmdline/rbsite.py, line 1611, in main
 command.run()
   File /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-
 py2.6.egg/reviewboard/cmdline/rbsite.py, line 1177, in run
 self.show_install_status()
   File /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-
 py2.6.egg/reviewboard/cmdline/rbsite.py, line 1436, in 
 show_install_status
 site.sync_database)
   File /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-
 py2.6.egg/reviewboard/cmdline/rbsite.py, line 703, in step
 func()
   File /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-
 py2.6.egg/reviewboard/cmdline/rbsite.py, line 339, in sync_database
 self.run_manage_command(syncdb, params)
   File /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-
 py2.6.egg/reviewboard/cmdline/rbsite.py, line 397, in 
 run_manage_command
 execute_manager(reviewboard.settings, [__file__, cmd] + params)
   File /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
 egg/django/core/management/__init__.py, line 459, in execute_manager
 utility.execute()
   File /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
 egg/django/core/management/__init__.py, line 382, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
 egg/django/core/management/base.py, line 196, in run_from_argv
 self.execute(*args, **options.__dict__)
   File /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
 egg/django/core/management/base.py, line 232, in execute
 output = self.handle(*args, **options)
   File /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
 egg/django/core/management/base.py, line 371, in handle
 return self.handle_noargs(**options)
   File /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
 egg/django/core/management/commands/syncdb.py, line 57, in 
 handle_noargs
 cursor = connection.cursor()
   File /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
 egg/django/db/backends/dummy/base.py, line 15, in complain
 raise ImproperlyConfigured(settings.DATABASES is improperly 
 configured. 
 django.core.exceptions.ImproperlyConfigured: settings.DATABASES is 
 improperly configured. Please supply

Re: Error: Error applying evolution: (1051, Unknown table 'auth_message')

2014-03-18 Thread Kevin Phillips
Your database dump appears incomplete. Try dumping with 
--max_allowed_packet=512M (large packet to avoid truncation). Check your 
1.5.X db and verify the table exists in production and in the backup. Also 
verify all your tables are InnoDB instead of MYISAM, you can make manual 
modification to the table engine without much recourse. 

Take a look at my thread, I just migrated 1.5.2 to 1.7.14 on the same 
platform as you.

KP

On Tuesday, March 18, 2014 2:31:44 AM UTC-7, Bhaskar Roy wrote:

 Hi Christian,

 I am trying migration on new server and not in current production box. 

 1. On new server I installed ubuntu 12.04/mysql 5.5/RB 1.7.14
 1. I took backup of SQL and copied to new server and done rb-site upgrade.

 Copied the databse to new server and tired . I get error messages as 
 listed above.

 regards
 Bhaskar 


 On Thu, Mar 13, 2014 at 12:53 AM, Christian Hammond 
 chi...@chipx86.comjavascript:
  wrote:

 Hi,

 First, did you back up your database?

 Second, can you verify the version of Review Board you've upgraded to, 
 and also verify the version of django-evolution installed? (These should be 
 in your Python's site-packages directory).

 You shouldn't do *any* hand-modifying of the database of any sort, or 
 you'll cause further issues in the upgrade process. Our stuff expects to 
 own the full schema of the database.

 Christian

 -- 
 Christian Hammond - chi...@chipx86.com javascript:
 Review Board - http://www.reviewboard.org
 Beanbag, Inc. - http://www.beanbaginc.com


 On Wed, Mar 12, 2014 at 3:23 AM, Bhaskar Roy 
 bhaska...@gmail.comjavascript:
  wrote:

 Hi Christian,

 I am getting following error while doing site upgrade from 1.5 to Latest 
 1.7.
 Even created auth_message tablein MySqL DB.


 /usr/bin/python /usr/local/bin/rb-site upgrade /var/www/reviewboard
 Rebuilding directory structure
 Updating database. This may take a while.

 The log output below, including warnings and errors,
 can be ignored unless upgrade fails.

 -- begin log output --
 Creating tables ...
 There are unapplied evolutions for auth.
 There are unapplied evolutions for sessions.
 There are unapplied evolutions for accounts.
 There are unapplied evolutions for changedescs.
 There are unapplied evolutions for diffviewer.
 There are unapplied evolutions for reviews.
 There are unapplied evolutions for scmtools.
 Project signature has changed - an evolution is required
 Installing custom SQL ...
 Installing indexes ...
 Installed 0 object(s) from 0 fixture(s)
 Evolution could not be simulated, possibly due to raw SQL mutations
 Error: Error applying evolution: (1051, Unknown table 'auth_message')
  
 Regards
 bhaskar 

 -- 
 Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
 ---
 Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
 ---
 Happy user? Let us know at http://www.reviewboard.org/users/
 --- 
 You received this message because you are subscribed to the Google 
 Groups reviewboard group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to reviewboard...@googlegroups.com javascript:.
 For more options, visit https://groups.google.com/d/optout.


  -- 
 Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
 ---
 Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
 ---
 Happy user? Let us know at http://www.reviewboard.org/users/
 --- 
 You received this message because you are subscribed to the Google Groups 
 reviewboard group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to reviewboard...@googlegroups.com javascript:.
 For more options, visit https://groups.google.com/d/optout.




-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
reviewboard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: css not coming up

2014-03-18 Thread Kevin Phillips
Verify your static and media settings in your web server configuration.

You will probably have to post your apache vhost or lighthttp confg for 
better help.

On Tuesday, March 18, 2014 6:07:16 AM UTC-7, shravanthi s wrote:

 Hi,

 We installed review board succesfully and created a site as well. Its 
 coming up but there is no style or css present so its only plain text and 
 hyperlinks in the webpage. Please let us know how we can fix this issue (RB 
 installed is 1.7.21)

 Thanks,
 Shravanthi


-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
reviewboard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Site Migration Issues from 1.5.2 to 1.7.14

2014-03-15 Thread Kevin Phillips


 Christian;


Good news! Turns out the dump has been truncated by the allowed_packet_size 
for mysqldump (problem with the interface between the seat and keyboard). 
The upgrade succeeded, however I had to alter the engine type of all the 
tables from myisam to innodb.

Can you advise on updating to mod_wsgi? Is there a way to get reviewboard 
to update it for me, just kidding, here is what I have:
reviewboard.wsgi

import os
import sys

os.environ['DJANGO_SETTINGS_MODULE'] = reviewboard.settings
os.environ['PYTHON_EGG_CACHE'] = /var/www/review.company.com/tmp/egg_cache
os.environ['HOME'] = /var/www/review.company.com/data
os.environ['PYTHONPATH'] = '/var/www/review.company.com/conf:' + 
os.environ.get('PYTHONPATH', '')

sys.path = ['/var/www/review.company.com/conf'] + sys.path

import django.core.handlers.wsgi
application = django.core.handlers.wsgi.WSGIHandler()

apache vhost config:
VirtualHost *:80
ServerName review.some.internal.dns.subdomain
DocumentRoot /var/www/review.company.com/htdocs

# Error handlers
ErrorDocument 500 /errordocs/500.html

WSGIPassAuthorization On
WSGIScriptAlias / 
/var/www/review.company.com/htdocs/reviewboard.wsgi/

Directory /var/www/review.company.com/htdocs
AllowOverride All
Options -Indexes +FollowSymLinks
Allow from all
/Directory

# Prevent the server from processing or allowing the rendering of
# certain file types.
Location /media/uploaded
SetHandler None
Options None

AddType text/plain .html .htm .shtml .php .php3 .php4 .php5 
.phps .asp
AddType text/plain .pl .py .fcgi .cgi .phtml .phtm .pht 
.jsp .sh .rb

IfModule mod_php5.c
php_flag engine off
/IfModule
/Location

# Alias static media requests to filesystem
Alias /media /var/www/review.vmem.com/htdocs/media
Alias /static /var/www/review.vmem.com/htdocs/static
Alias /errordocs /var/www/review.vmem.com/htdocs/errordocs
Alias /favicon.ico 
/var/www/review.vmem.com/htdocs/static/rb/images/favicon.png
/VirtualHost


For posterity's sake, here is my upgrade log,
Rebuilding directory structure
Updating database. This may take a while.

The log output below, including warnings and errors,
can be ignored unless upgrade fails.

-- begin log output --
Creating tables ...
Creating table extensions_registeredextension
Creating table accounts_localsiteprofile
Creating table attachments_fileattachment
Creating table diffviewer_filediffdata
Creating table hostingsvcs_hostingserviceaccount
Creating table reviews_fileattachmentcomment
Creating table site_localsite_users
Creating table site_localsite_admins
Creating table site_localsite
Upgrading Review Board from 1.5.2 to 1.7.14
There are unapplied evolutions for auth.
There are unapplied evolutions for sessions.
There are unapplied evolutions for accounts.
There are unapplied evolutions for attachments.
There are unapplied evolutions for changedescs.
There are unapplied evolutions for diffviewer.
There are unapplied evolutions for hostingsvcs.
There are unapplied evolutions for reviews.
There are unapplied evolutions for scmtools.
Adding baseline version for new models
Evolutions in attachments baseline: file_attachment_orig_filename, 
file_attachment_file_max_length_512
Evolutions in hostingsvcs baseline: account_hosting_url, 
account_hosting_url_max_length_255
Project signature has changed - an evolution is required
Installing custom SQL ...
Installing indexes ...
Installed 0 object(s) from 0 fixture(s)
Registering new SCM Tool Plastic SCM 
(reviewboard.scmtools.plastic.PlasticTool) in database
Evolution could not be simulated, possibly due to raw SQL mutations
Evolution successful.
--- end log output ---

Resetting in-database caches.

Upgrade complete!

The location of static media files (CSS, JavaScript, images)
has changed. You will need to make manual changes to
your web server configuration.

For Apache, you will need to add:

Location /review/static
SetHandler None
/Location

Alias /review/static /var/www/review.company.com/htdocs/static

For lighttpd:

alias.url = (
...
/review/static = /var/www/review.company.com/htdocs/static,
...
)

url.rewrite-once = (
...
^(/review/static/.*)$ = $1,
...
)

Once you have made these changes, type the following
to resolve this:

$ rb-site manage /var/www/review.company.com resolve-check static-media
 

-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the 

Site Migration Issues from 1.5.2 to 1.7.14

2014-03-14 Thread Kevin Phillips
All;

I'm having some issues performing a site migration of RB 1.5.2 to 1.7.14 
from an EOL server to a VM. Here are the steps I preformed:

1. Took SQL dump of reviewboard database and restored on new system
2. Took copy of application web root and copied to new system
3. Configured memcached on new system.
3. Installed Reviewboard==1.7.14 Django==1.4.10 python-memcached 
MySQL-python + deps via easy_install (Python 2.7.3)
4. Preformed a rb-site upgrade of application web root.
5. Upgrade failed with a 1050 (or similar) error because it couldn't access 
some table. So I temporarily overrode django's default database handler to 
use mysql + client configs in my.cnf (only a single site will reside on 
this VM) via django's conf/global_settings.py, I then ran 
'./reviewboard/manage.py syncdb'.
6. syncdb also failed, so I dropped all my tables and re-ran the syncdb.
7. The second syncdb after dropping my tables worked, then I re-ran the 
rb-site upgrade
8. The second rb-site upgrade was successful but prompted me to modify my 
apache vhost config and validate the site settings.
9. I actioned the changes and restarted the web server.

After this I get the error 500 page but I get a mod_python stack trace (yes 
I know mod_python is simply in there for legacy purposes, but the old site 
ran it and I cannot figure out how to cut-over to mod_wsgi).

STACKTRACE:
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] mod_python 
(pid=2342, interpreter='reviewboard_review_vmem_com', 
phase='PythonHandler', handler='django.core.handlers.modpython'): 
Application error, referer: http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] ServerName: 
'reviewboard.sub.domain', referer: http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] DocumentRoot: 
'/var/www/review.vmem.com/htdocs', referer: 
http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] URI: '/review/', 
referer: http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] Location: 
'/review/', referer: http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] Directory: None, 
referer: http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] Filename: 
'/var/www/review.vmem.com/htdocs/review', referer: 
http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] PathInfo: '/', 
referer: http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] Traceback (most 
recent call last):, referer: http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48]   File 
/usr/lib/python2.7/dist-packages/mod_python/importer.py, line 1537, in 
HandlerDispatch\ndefault=default_handler, arg=req, 
silent=hlist.silent), referer: http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48]   File 
/usr/lib/python2.7/dist-packages/mod_python/importer.py, line 1202, in 
_process_target\nmodule = import_module(module_name, path=path), 
referer: http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48]   File 
/usr/lib/python2.7/dist-packages/mod_python/importer.py, line 304, in 
import_module\nreturn __import__(module_name, {}, {}, ['*']), referer: 
http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] ImportError: No 
module named django.core.handlers.modpython, referer: 
http://reviewboard.sub.domain/review/

VHOST CONFIG
VirtualHost *:80
ServerName reviewboard.sub.domain
DocumentRoot /var/www/reviewboard/htdocs

# Error handlers
ErrorDocument 500 /errordocs/500.html

# Serve django pages
Location /review/
PythonPath ['/var/www/reviewboard/conf'] + sys.path
SetEnv DJANGO_SETTINGS_MODULE reviewboard.settings
SetEnv PYTHON_EGG_CACHE /var/www/reviewboard/tmp/egg_cache
SetHandler mod_python
PythonHandler django.core.handlers.modpython
PythonAutoReload Off
PythonDebug Off
# Used to run multiple mod_python sites in the same apache
PythonInterpreter reviewboard_reviewboard
/Location

# Serve static without running it through mod_python
# Required for upgrade from Reviewboard 1.5.2 to 1.7.14
Location /review/static
SetHandler None
/Location

Alias /review/static /var/www/reviewboard/htdocs/static

# Serve static media without running it through mod_python
# (overrides the above)
Location /review/media
SetHandler None
/Location
Location /review/errordocs
SetHandler None
/Location

Directory /var/www/reviewboard/htdocs
AllowOverride All
/Directory

# Alias static media requests to filesystem
Alias /review/media /var/www/reviewboard/htdocs/media
Alias /review/errordocs /var/www/reviewboard/htdocs/errordocs
/VirtualHost

Any suggestions would be much appreciated. If you live in the bay area, 
I'll buy you a six pack.

Thanks,

Kevin

-- 
Get

Re: Site Migration Issues from 1.5.2 to 1.7.14

2014-03-14 Thread Kevin Phillips
 root?

Settings_local.py
# Site-specific configuration settings for Review Board
# Definitions of these settings can be found at
# http://docs.djangoproject.com/en/dev/ref/settings/

# Database configuration
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.mysql',
'NAME': 'review',
'USER': 'review',
'PASSWORD': 'OMITTED',
'HOST': 'localhost',
'PORT': '',
},
}

# Unique secret key. Don't share this with anybody.
SECRET_KEY = 'OMITTED

# Cache backend settings.
CACHES = {
'default': {
'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache',
'LOCATION': 'localhost:11211',
},
}

# Extra site information.
SITE_ID = 1
SITE_ROOT = '/review/'
FORCE_SCRIPT_NAME = ''
DEBUG = True

On Friday, March 14, 2014 1:13:10 PM UTC-7, Christian Hammond wrote:

 Hi Kevin,

 The first red flag is that you had to do anything special with the 
 database. Working around those issues is going to likely just result in new 
 issues down the line, so for the moment, let's consider the workarounds as 
 not a real solution, and dig into what went wrong there.

 Can you reproduce the original steps and show me exactly what errors you 
 hit?

 Something important to watch out for is that your database dump is 
 consistent with regards to the table type (MyISAM vs. InnoDB). If they're 
 not, you will have problems importing the dump. This is the usual cause of 
 the problems.

 You also need to be sure your database is completely wiped before 
 importing, so that there aren't any conflicts there.

 I don't remember which version of django-evolution we depended on back in 
 1.7.14, but make sure you have django-evolution 0.6.9 installed before 
 upgrading the database. (Also, why not run a more modern 1.7.x? Lots of bug 
 fixes since 1.7.14.)

 As far as the last error goes, mod_python is completely unsupported now, 
 by both us and Django (and, really, the project itself, last I heard). You 
 should be using mod_wsgi for any installations now.

 Christian


 -- 
 Christian Hammond - chi...@chipx86.com javascript:
 Review Board - http://www.reviewboard.org
 Beanbag, Inc. - http://www.beanbaginc.com


 On Fri, Mar 14, 2014 at 10:50 AM, Kevin Phillips 
 kevin.grenvi...@gmail.com javascript: wrote:

 All;

 I'm having some issues performing a site migration of RB 1.5.2 to 1.7.14 
 from an EOL server to a VM. Here are the steps I preformed:

 1. Took SQL dump of reviewboard database and restored on new system
 2. Took copy of application web root and copied to new system
 3. Configured memcached on new system.
 3. Installed Reviewboard==1.7.14 Django==1.4.10 python-memcached 
 MySQL-python + deps via easy_install (Python 2.7.3)
 4. Preformed a rb-site upgrade of application web root.
 5. Upgrade failed with a 1050 (or similar) error because it couldn't 
 access some table. So I temporarily overrode django's default database 
 handler to use mysql + client configs in my.cnf (only a single site will 
 reside on this VM) via django's conf/global_settings.py, I then ran 
 './reviewboard/manage.py syncdb'.
 6. syncdb also failed, so I dropped all my tables and re-ran the syncdb.
 7. The second syncdb after dropping my tables worked, then I re-ran the 
 rb-site upgrade
 8. The second rb-site upgrade was successful but prompted me to modify my 
 apache vhost config and validate the site settings.
 9. I actioned the changes and restarted the web server.

 After this I get the error 500 page but I get a mod_python stack trace 
 (yes I know mod_python is simply in there for legacy purposes, but the old 
 site ran it and I cannot figure out how to cut-over to mod_wsgi).

 STACKTRACE:
 [Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] mod_python 
 (pid=2342, interpreter='reviewboard_review_vmem_com', 
 phase='PythonHandler', handler='django.core.handlers.modpython'): 
 Application error, referer: http://reviewboard.sub.domain/review/
 [Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] ServerName: 
 'reviewboard.sub.domain', referer: http://reviewboard.sub.domain/review/
 [Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] DocumentRoot: 
 '/var/www/review.vmem.com/htdocs', referer: 
 http://reviewboard.sub.domain/review/
 [Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] URI: '/review/', 
 referer: http://reviewboard.sub.domain/review/
 [Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] Location: 
 '/review/', referer: http://reviewboard.sub.domain/review/
 [Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] Directory: None, 
 referer: http://reviewboard.sub.domain/review/
 [Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] Filename: 
 '/var/www/review.vmem.com/htdocs/review', referer: 
 http://reviewboard.sub.domain/review/
 [Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] PathInfo: '/', 
 referer: http://reviewboard.sub.domain/review/
 [Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] Traceback (most 
 recent call last):, referer: http://reviewboard.sub.domain/review/
 [Fri Mar 14 09:48:18 2014

Re: post-review: entering username and password everytime

2011-10-20 Thread Kevin Tran
I think adding a note about ~/.post-review-cookies.txt to the post-review 
manual page would be helpful.

I created a 
ticket: http://code.google.com/p/reviewboard/issues/detail?id=2342

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en

How does ReviewBoard know who I am?

2011-10-06 Thread Kevin Tran
When I post a review using post-review, I am not prompted for a 
username/password and I omit it from the command, yet the review request 
created is created with my username. How does ReviewBoard know which user I 
am without me telling it or it prompting me? I think it prompted me the 
first time, but after that it didn't anymore. Did it save my credentials 
somewhere?

The command I use is:
$ post-review --revision-range=xxx --server=https://reviewboard.foo.com/

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en

Review entire repository

2011-08-14 Thread kevin gill
Hi,

I am using git, and starting with reviewboard on a new project.

Is there a command to create a review/diff for the entire repository.
I can use post-review to create a diff between  the first commit and
the current version (using a --revision-range). However, the git
repository initial revision contains some code that should be
reviewed.

This is just for my convenience. If there is no way to do this easily,
that is fine.

Thanks

Kevin

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en


Re: post-reivew WEB API?

2011-03-08 Thread Kevin
I'm also seeing a similar problem and might have a few more details to
add. Please let me know if there is anything else I can try to help
debug this issue. I'm not a web guru, have no experience with Django,
and am running short on things to try.

Originally I had the problem with RB 1.5.3.1 and RBTools 0.3.2. Since
then I've upgraded to RB 1.5.4 and still see a similar problem.

A few more details:
*I'm running Apache/2.2.16, Django-1.2.5, Djblets-0.6.7,
django_evolution-0.6.2, python 2.6, PostgreSQL 9.0.3, mod_fastcgi
2.4.7
*I modified the following in my apache config (as per
http://www.mail-archive.com/reviewboard@googlegroups.com/msg03636.html):
Directory /
Options FollowSymLinks
AllowOverride None
Order deny,allow
/Directory
*Set 'DEBUG = True' and don't see anything interesting in the server
logs
*Web access to the server works fine
*Checking Allow anonymous read-only access gets post-review to
progress further
*Looking at the wire traffic I see 3 tcp connections:
  1) GET /api/ - 200 OK
  2) GET /api/info/ - 401 UNAUTHORIZED
  3) GET /api/info/ (with Authorization: Basic [credentials]) - 401
UNAUTHORIZED
*The RB unit tests fail to run
  1) Initially I got (Required Python Imaging Library). Strace
showed a search for PIL.py, but PIL-1.1.7-py2.6 doesn't have such a
file. I edited manage.py to remove the import check.
  2) Then the database setup in the tests fails at:
File /usr/lib64/python2.6/site-packages/Django-1.2.5-
py2.6.egg/django/db/backends/postgresql_psycopg2/base.py, line 44, in
execute
  return self.cursor.execute(query, args)
django.db.utils.DatabaseError: no such savepoint

~Kevin


On Mar 8, 3:33 am, Christian Hammond chip...@chipx86.com wrote:
 Hi Chris,

 Assuming your install is from before RB 1.5.2, you need to make a small
 change to your Apache configuration.

 Try:

 http://www.reviewboard.org/docs/manual/dev/faq/#i-m-using-post-review...

 Christian

 --
 Christian Hammond - chip...@chipx86.com
 Review Board -http://www.reviewboard.org
 VMware, Inc. -http://www.vmware.com

 On Mon, Mar 7, 2011 at 10:48 AM, Chris Tandiono 
 chris.tandi...@gmail.comwrote:







  Sorry to interject: I'm having the same problem, and I am indeed using
  mod_wsgi. Specifically, if I go tohttps://wherever/rb/api/info/I'm
  given the standard Basic Auth box by my browser, and nothing I type in
  there works...

  Thanks,
  Chris

  On Mar 5, 12:55 am, Christian Hammond chip...@chipx86.com wrote:
   Hi Kevin,

   Are you using mod_wsgi on the server?

   Christian

   --
   Christian Hammond - chip...@chipx86.com
   Review Board -http://www.reviewboard.org
   VMware, Inc. -http://www.vmware.com

   On Fri, Mar 4, 2011 at 11:28 PM, Kevin kevin.quennes...@gmail.com
  wrote:
Thanks for reviewboard!

I am actually having the same issue it seems, did we find a
resolution? Thanks a lot!

I am using RB 1.5.4 and RBTools 0.3.2, and mercurial 1.8.

# post-review --debug
 RBTools 0.3.2
 Home = /Volumes/Home
 svn info
 git rev-parse --git-dir
 hg showconfig
 hg root
 hg svn info
 Using candidate path 'default': 'THE_HG_REP'
 repository info: Path: THE_HG_REP, Base path: , Supports
  changesets:
False
 HTTP GETting api/
 HTTP GETting THE_RB_SERVER.CORP.COM/api/info/
 Using the new web API
 hg branch
 hg -q outgoing --template b:{branches}
r:{rev}

 default
 Found outgoing changeset 53 for branch 'default'
 Found outgoing changeset 54 for branch 'default'
 hg diff -r 52 -r 54
 Attempting to create review request on THE_HG_REP for None
 HTTP POSTing to THE_RB_SERVER.CORP.COM/api/review-requests/:
{'repository': 'THE_HG_REP'}
== HTTP Authentication Required
Enter authorization information for Web API at
THE_RB_SERVER.CORP.COM
Username: THE_USERNAME
Password: THE_PASSWORD
 Got API Error 103 (HTTP code 401): You are not logged in
 Error data: {u'stat': u'fail', u'err': {u'msg': u'You are not
  logged
in', u'code': 103}}
 Attempting to create review request on THE_HG_REP for None
 HTTP POSTing to THE_RB_SERVER.CORP.COM/api/review-requests/:
{'repository': 'THE_HG_REP'}
 Got API Error 103 (HTTP code 401): You are not logged in
 Error data: {u'stat': u'fail', u'err': {u'msg': u'You are not
  logged
in', u'code': 103}}
 Attempting to create review request on THE_HG_REP for None
 HTTP POSTing to THE_RB_SERVER.CORP.COM/api/review-requests/:
{'repository': 'THE_HG_REP'}
 Got API Error 103 (HTTP code 401): You are not logged in
 Error data: {u'stat': u'fail', u'err': {u'msg': u'You are not
  logged
in', u'code': 103}}
 Attempting to create review request on THE_HG_REP for None
 HTTP POSTing to THE_RB_SERVER.CORP.COM/api/review-requests/:
{'repository': 'THE_HG_REP'}
 Got API Error 103 (HTTP code 401): You are not logged in
 Error

Re: post-reivew WEB API?

2011-03-05 Thread Kevin
Thanks for reviewboard!

I am actually having the same issue it seems, did we find a
resolution? Thanks a lot!

I am using RB 1.5.4 and RBTools 0.3.2, and mercurial 1.8.

# post-review --debug
 RBTools 0.3.2
 Home = /Volumes/Home
 svn info
 git rev-parse --git-dir
 hg showconfig
 hg root
 hg svn info
 Using candidate path 'default': 'THE_HG_REP'
 repository info: Path: THE_HG_REP, Base path: , Supports changesets: False
 HTTP GETting api/
 HTTP GETting THE_RB_SERVER.CORP.COM/api/info/
 Using the new web API
 hg branch
 hg -q outgoing --template b:{branches}
r:{rev}

 default
 Found outgoing changeset 53 for branch 'default'
 Found outgoing changeset 54 for branch 'default'
 hg diff -r 52 -r 54
 Attempting to create review request on THE_HG_REP for None
 HTTP POSTing to THE_RB_SERVER.CORP.COM/api/review-requests/: {'repository': 
 'THE_HG_REP'}
== HTTP Authentication Required
Enter authorization information for Web API at
THE_RB_SERVER.CORP.COM
Username: THE_USERNAME
Password: THE_PASSWORD
 Got API Error 103 (HTTP code 401): You are not logged in
 Error data: {u'stat': u'fail', u'err': {u'msg': u'You are not logged in', 
 u'code': 103}}
 Attempting to create review request on THE_HG_REP for None
 HTTP POSTing to THE_RB_SERVER.CORP.COM/api/review-requests/: {'repository': 
 'THE_HG_REP'}
 Got API Error 103 (HTTP code 401): You are not logged in
 Error data: {u'stat': u'fail', u'err': {u'msg': u'You are not logged in', 
 u'code': 103}}
 Attempting to create review request on THE_HG_REP for None
 HTTP POSTing to THE_RB_SERVER.CORP.COM/api/review-requests/: {'repository': 
 'THE_HG_REP'}
 Got API Error 103 (HTTP code 401): You are not logged in
 Error data: {u'stat': u'fail', u'err': {u'msg': u'You are not logged in', 
 u'code': 103}}
 Attempting to create review request on THE_HG_REP for None
 HTTP POSTing to THE_RB_SERVER.CORP.COM/api/review-requests/: {'repository': 
 'THE_HG_REP'}
 Got API Error 103 (HTTP code 401): You are not logged in
 Error data: {u'stat': u'fail', u'err': {u'msg': u'You are not logged in', 
 u'code': 103}}
Error creating review request: You are not logged in


Also it seems the .post-review-cookies.txt doesn't get set:
# cat ~/.post-review-cookies.txt
# Netscape HTTP Cookie File
# http://www.netscape.com/newsref/std/cookie_spec.html
# This is a generated file!  Do not edit.

All works fine from the web ui.

Thanks a lot for the help.

Kevin

On Jan 28, 3:02 pm, Christian Hammond chip...@chipx86.com wrote:
 Is this exactly 1.5.0? And is it the RBTools 0.2 release, or a nightly?

 Can you try with --debug and e-mail me the output?

 Christian

 --
 Christian Hammond - chip...@chipx86.com
 Review Board -http://www.reviewboard.org
 VMware, Inc. -http://www.vmware.com

 On Fri, Jan 28, 2011 at 2:34 PM, Rohan Dhaimade halo.zer...@gmail.comwrote:



  Well.

  I first logged in with my current information.

  But then it asked for this immediately.

  The full flow is this
  I run post-review

  == Review Board Login Required
  Enter username and password for Review Board at
 http://reviewboard.indinerocorp.com/
  Username: rohan
  password:

  Then it asks
  == HTTP Authentication Required
  Enter username and password for Web API at
  reviewboard.indinerocorp.com
  Username:

  The weird thing is here is that even if I type in my username wrong, I
  still get the second prompt.

  I am running ReviewBoard 1.5
  RGB Tools 0.2

  On Jan 28, 3:26 am, Christian Hammond chip...@chipx86.com wrote:
   The message needs to be more clear, but it's like this for legacy
   reasons... Anyhow, you should be using your standard username and
   password for Review Board. If it's not working with your standard
   account, can you tell me what version of Review Board and RBTools
   you're using (including whether it's Git/nightly build)?

   Christian

   On Thursday, January 27, 2011, Rohan Dhaimade halo.zer...@gmail.com
  wrote:
I'm a little confused on what this message means.

Whenever I try to do post-review. I get this message

Enter username and password for Web API at
reviewboard.companyname.com

But it doesn't seem to be any user that I know of What is WEB API? I
couldn't find anything in the docs. Did I install post-review wrong?

Any help would be appreciated,

Thanks,

Rohan

--
Want to help the Review Board project? Donate today athttp://
 www.reviewboard.org/donate/
Happy user? Let us know athttp://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to
  reviewboard+unsubscr...@googlegroups.comreviewboard%2Bunsubscribe@googlegr 
  oups.com
For more options, visit this group athttp://
  groups.google.com/group/reviewboard?hl=en

   --
   --
   Christian Hammond - chip...@chipx86.com
   Review Board -http://www.reviewboard.org
   VMware, Inc. -http://www.vmware.com

  --
  Want to help the Review Board project? Donate today at
 http

Re: post-review degrades into O(n)

2009-02-17 Thread Kevin Kubasik

Even for a large reviewboard install (several dozen repos) I don't see
this being a major performance benefit/detriment. Can you provide some
numbers showing this as a problem? It seems like a largely theoretical
slowdown.

-Kevin

On Tue, Feb 17, 2009 at 2:59 PM, Gary M. Josack g...@byoteki.com wrote:

 Disclaimer: This post is specific to SVN. I admittedly don't know much
 about the other RCS's that reviewboard supports.

 Would anyone be against the addition of UUID as a configurable parameter
 when adding a repository to reviewboard or having it grab the UUID
 automatically when you first configure it and store it? I ask because
 currently post-review will get a list of the repositories then iterate
 over each one until it finds a match. This seems wasteful and can take a
 while when you have a large number of repositories to work through. The
 UUID should not change in a repository and querying possibly every repo
 in your list for this data to find a match seems wasteful when the list
 of the repos can provide this data making post-review perform O(1) for
 number of repos.

 Any comments/questions?

 Thanks,
 Gary M. Josack

 




-- 
Kevin Kubasik
http://kubasik.net/blog

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
reviewboard group.
To post to this group, send email to reviewboard@googlegroups.com
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en
-~--~~~~--~~--~--~---



Bzr as RCS Tool

2008-12-15 Thread Kevin Kubasik

So I am having some problems with the Bzr tool. Namely, if I have
added a new file in a diff, I cannot submit it for review. Are there
any known bugs with the bzr tool?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
reviewboard group.
To post to this group, send email to reviewboard@googlegroups.com
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en
-~--~~~~--~~--~--~---



Re: Bzr as RCS Tool

2008-12-15 Thread Kevin Kubasik

Thanks!

On Mon, Dec 15, 2008 at 10:12 PM, Christian Hammond chip...@chipx86.com wrote:
 There's a review request that was just put up today that addresses this.
 I'll be looking into it tonight or tomorrow.

 Christian

 --
 Christian Hammond - chip...@chipx86.com
 VMware, Inc.


 On Mon, Dec 15, 2008 at 8:27 PM, Kevin Kubasik ke...@kubasik.net wrote:

 So I am having some problems with the Bzr tool. Namely, if I have
 added a new file in a diff, I cannot submit it for review. Are there
 any known bugs with the bzr tool?



 




-- 
Kevin Kubasik
http://kubasik.net/blog

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
reviewboard group.
To post to this group, send email to reviewboard@googlegroups.com
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en
-~--~~~~--~~--~--~---