Issue 1099 in reviewboard: ProgrammingError exception after beta2 to beta3 update
Updates: Status: Fixed Comment #6 on issue 1099 by chipx86: ProgrammingError exception after beta2 to beta3 update http://code.google.com/p/reviewboard/issues/detail?id=1099 This should be fixed in r1955, and I'm spinning new builds, which will be ready in about 20 minutes from the time of this post. If you could upgrade and try it, I'd very much appreciate it. From my tests, it's fixed now, and working as expected. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en -~--~~~~--~~--~--~---
Issue 1106 in reviewboard: Markup for text fields
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 1106 by nikolai.prokoschenko: Markup for text fields
http://code.google.com/p/reviewboard/issues/detail?id=1106
What version are you running?
1.0rc1
What steps will reproduce the problem?
1. Take a comment field
2. Enter some marked up text ('This is a *strong* _italic_ text')
3. Click OK
What is the expected output? What do you see instead?
The word strong should have been in bold, italic in italics. Instead,
markup is shown as is.
Please provide any additional information below.
Should be easy to implement, for example with the MarkdownTextField from
djangosnippets. But any markup language will do.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
reviewboard-issues group.
To post to this group, send email to reviewboard-issues@googlegroups.com
To unsubscribe from this group, send email to
reviewboard-issues+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/reviewboard-issues?hl=en
-~--~~~~--~~--~--~---
Issue 1108 in reviewboard: RB RC1 uses SQL incompatible with PostgreSQL
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 1108 by ger...@saygo.ca: RB RC1 uses SQL incompatible with PostgreSQL http://code.google.com/p/reviewboard/issues/detail?id=1108 *NOTE: Do not post confidential information in this bug report.* What version are you running? 1.0RC1 What's the URL of the page containing the problem? Internal site What steps will reproduce the problem? 1. Run RB on postgresql_psycopg2 engine. What is the expected output? What do you see instead? HTTP 500 error on all RB pages. Traceback logged (contents below). My guess is that some SQL is incompatible with postgresql. What operating system are you using? What browser? Linux, Ubuntu Hardy All browsers on all platforms. Please provide any additional information below. On a different note, ReviewBoard-1.0beta3.dev_20090402 works perfectly on the same platform/database engine. Here's the traceback generated: Traceback (most recent call last): File /usr/lib/python2.5/site-packages/Django-1.0.2_final-py2.5.egg/ django/core/handlers/base.py, line 86, in get_response response = callback(request, *callback_args, **callback_kwargs) File /usr/lib/python2.5/site-packages/Djblets-0.5rc1-py2.5.egg/djblets/ auth/util.py, line 45, in _checklogin return view_func(request, *args, **kwargs) File /usr/lib/python2.5/site-packages/ReviewBoard-1.0rc1-py2.5.egg/ reviewboard/accounts/decorators.py, line 43, in _check_valid_prefs return view_func(request, *args, **kwargs) File /usr/lib/python2.5/site-packages/ReviewBoard-1.0rc1-py2.5.egg/ reviewboard/reviews/views.py, line 309, in dashboard return grid.render_to_response(template_name) File /usr/lib/python2.5/site-packages/Djblets-0.5rc1-py2.5.egg/djblets/ datagrid/grids.py, line 556, in render_to_response self.load_state() File /usr/lib/python2.5/site-packages/Djblets-0.5rc1-py2.5.egg/djblets/ datagrid/grids.py, line 452, in load_state self.precompute_objects() File /usr/lib/python2.5/site-packages/Djblets-0.5rc1-py2.5.egg/djblets/ datagrid/grids.py, line 509, in precompute_objects for obj in self.page.object_list: File /usr/lib/python2.5/site-packages/Django-1.0.2_final-py2.5.egg/ django/db/models/query.py, line 185, in _result_iter self._fill_cache() File /usr/lib/python2.5/site-packages/Django-1.0.2_final-py2.5.egg/ django/db/models/query.py, line 618, in _fill_cache self._result_cache.append(self._iter.next()) File /usr/lib/python2.5/site-packages/Django-1.0.2_final-py2.5.egg/ django/db/models/query.py, line 275, in iterator for row in self.query.results_iter(): File /usr/lib/python2.5/site-packages/Django-1.0.2_final-py2.5.egg/ django/db/models/sql/query.py, line 206, in results_iter for rows in self.execute_sql(MULTI): File /usr/lib/python2.5/site-packages/Django-1.0.2_final-py2.5.egg/ django/db/models/sql/query.py, line 1734, in execute_sql cursor.execute(sql, params) ProgrammingError: column reviews_review.timestamp must appear in the GROUP BY clause or be used in an aggregate function -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en -~--~~~~--~~--~--~---
Issue 1082 in reviewboard: rb-site not working on Windows
Comment #8 on issue 1082 by javier.ortiz.78: rb-site not working on Windows http://code.google.com/p/reviewboard/issues/detail?id=1082 I tried with the rc1 and still the rb-site file has no extension but this time I was able to rename it as rb-site.exe and ran it. It's taking a while to react. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en -~--~~~~--~~--~--~---
Issue 1032 in reviewboard: Diff currently unavailable when viewing diffs of diffs
Updates: Status: NeedInfo Comment #5 on issue 1032 by chipx86: Diff currently unavailable when viewing diffs of diffs http://code.google.com/p/reviewboard/issues/detail?id=1032 Can you provide a set of diffs that work as a repro case for this? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en -~--~~~~--~~--~--~---
Issue 1099 in reviewboard: ProgrammingError exception after beta2 to beta3 update
Comment #7 on issue 1099 by chipx86: ProgrammingError exception after beta2 to beta3 update http://code.google.com/p/reviewboard/issues/detail?id=1099 Issue 1108 has been merged into this issue. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en -~--~~~~--~~--~--~---
Issue 1108 in reviewboard: RB RC1 uses SQL incompatible with PostgreSQL
Updates: Status: Duplicate Mergedinto: 1099 Comment #1 on issue 1108 by chipx86: RB RC1 uses SQL incompatible with PostgreSQL http://code.google.com/p/reviewboard/issues/detail?id=1108 Dup of bug 1099. Go ahead and five the latest nightly a try and let me know if it works for you in that bug. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en -~--~~~~--~~--~--~---
Issue 1106 in reviewboard: Markup for text fields
Comment #3 on issue 1106 by chipx86: Markup for text fields http://code.google.com/p/reviewboard/issues/detail?id=1106 It definitely could, though we need to be careful not to break out existing text linkification code, and render proposed code incorrectly. Also, this must work in JavaScript, so using MarkdownTextField won't work for us. This is going to be a lot harder than it sounds. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en -~--~~~~--~~--~--~---
Issue 1099 in reviewboard: ProgrammingError exception after beta2 to beta3 update
Comment #8 on issue 1099 by durin42: ProgrammingError exception after beta2 to beta3 update http://code.google.com/p/reviewboard/issues/detail?id=1099 I was seeing this, and it's fixed now. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en -~--~~~~--~~--~--~---
Issue 1082 in reviewboard: rb-site not working on Windows
Comment #9 on issue 1082 by javier.ortiz.78: rb-site not working on Windows http://code.google.com/p/reviewboard/issues/detail?id=1082 Sadly it just hangs there :( -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en -~--~~~~--~~--~--~---
Issue 1106 in reviewboard: Markup for text fields
Comment #4 on issue 1106 by eduardofelipe87: Markup for text fields http://code.google.com/p/reviewboard/issues/detail?id=1106 Why this must work in Javascript? You mean that the conversion should be done client- side? Several webapps use this pretty well. We could at least provide a small subset of Markdown, the same that www.stackoverflow.com provides, for instance. That site is also code oriented, and has a nice set of features. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en -~--~~~~--~~--~--~---
Issue 1106 in reviewboard: Markup for text fields
Updates: Status: Confirmed Labels: Component-Reviews Comment #5 on issue 1106 by chipx86: Markup for text fields http://code.google.com/p/reviewboard/issues/detail?id=1106 When the user modifies a field client-side, we post to the server and then save the field and do any necessary post-processing. Right now that includes linkifying certain text, handling comma-separated fields in some fields, etc. We probably could have the server do this down the road, though we'll need to update the current API to *optionally* take a parameter saying what format we'd like the data returned in (so that we don't force clients to parse HTML if they don't want to, say for console apps). -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en -~--~~~~--~~--~--~---
