RhodeCode 1.3.2 Released

27 views
Skip to first unread message

Marcin Kuzminski

unread,
Feb 28, 2012, 1:59:38 PM2/28/12
to rhod...@googlegroups.com
I'm happy to announce the release of RhodeCode 1.3.2!

Downloads at: http://pypi.python.org/pypi#downloads
Demo at:      http://demo.rhodecode.org

Just another bugfix release. Thanks to all who posted issues !


Here is the full changelog for this release
===========================================

1.3.2 (**2012-02-28**)
----------------------

news
++++


fixes
+++++

- fixed git protocol issues with repos-groups
- fixed git remote repos validator that prevented from cloning remote git repos
- fixes #370 ending slashes fixes for repo and groups
- fixes #368 improved git-protocol detection to handle other clients
- fixes #366 When Setting Repository Group To Blank Repo Group Wont Be
  Moved To Root
- fixes #371 fixed issues with beaker/sqlalchemy and non-ascii cache keys
- fixed #373 missing cascade drop on user_group_to_perm table

Vandenbroucke Luc

unread,
Feb 28, 2012, 2:32:43 PM2/28/12
to rhod...@googlegroups.com

Still problems with the admin menu dropdown.

This script is not compatible with IE9.

On the server side I can use whatever I want. Appache, Python, .. Ruby ..

For the client I really  need to support more than  Mozilla…

 

And even with Mozilla, using anonymous logon, clicking on the avatar gives a transparent menu ..

 

1.3.0 was better for the basic user interface. ( first page)

1.3.1+ is better for functionality ..

DwightH

unread,
Feb 28, 2012, 3:24:56 PM2/28/12
to rhodecode
Have 1.3.1 and found the new notifications database table does not
create successfully - I am using MySQL. "paster setup-app
production.ini", gives the following error:

sqlalchemy.exc.OperationalError: (OperationalError) (1074, "Column
length too big for column 'body' (max = 21845); use BLOB or TEXT
instead") '\nCREATE TABLE notifications (\n\tnotification_id INTEGER
NOT NULL AUTO_INCREMENT, \n\tsubject VARCHAR(512), \n\tbody
VARCHAR(50000), \n\tcreated_by INTEGER, \n\tcreated_on DATETIME NOT
NULL, \n\ttype VARCHAR(256), \n\tPRIMARY KEY (notification_id), \n
\tFOREIGN KEY(created_by) REFERENCES users (user_id)\n)\n\n' ()

I searched for the schema definition to see if I could patch it (to
get past this hurdle) but couldn't figure out the database creation
process.

Just repeated the process with 1.3.2 and the same issue remains - I'd
welcome advice on how to tweak the database creation, or perhaps just
a fix in the next release :-)

Thanks,
Dwight

Marcin Kuzminski

unread,
Feb 28, 2012, 3:51:12 PM2/28/12
to rhod...@googlegroups.com
So odd, it works in mysql instance correctly, sqlalchemy automatically changes that from varchat to text

2012-02-28 22:48:26,452 INFO sqlalchemy.engine.base.Engine
CREATE TABLE notifications (
    notification_id INTEGER NOT NULL AUTO_INCREMENT,
    subject VARCHAR(512),
    body VARCHAR(50000),
    created_by INTEGER,
    created_on DATETIME NOT NULL,
    type VARCHAR(256),
    PRIMARY KEY (notification_id),
    FOREIGN KEY(created_by) REFERENCES users (user_id)
)


2012-02-28 22:48:26,452 INFO sqlalchemy.engine.base.Engine ()
/home/marcink/.virtualenvs/rhodecode/lib/python2.6/site-packages/SQLAlchemy-0.7.4-py2.6-linux-x86_64.egg/sqlalchemy/engine/default.py:330: Warning: Converting column 'body' from VARCHAR to TEXT
  cursor.execute(statement, parameters)


What mysql version are you using ?

Anyway to fix it just edit the https://secure.rhodecode.org/rhodecode/files/de372c3a329e0b353bdb093dd50d3cf6ecf7c8e4/rhodecode/model/db.py#L1141-1155 to make it work.

DwightH

unread,
Feb 28, 2012, 4:28:35 PM2/28/12
to rhodecode
Am using
MySQL 5.0.8 - ok that might be an issue; I'm just upgrading to a more
recent release...
SQLAlchemy 0.7.4.
Python 2.7.

DwightH

unread,
Feb 28, 2012, 7:05:41 PM2/28/12
to rhodecode
ok - after upgrading to a newer version of MySQL the RhodeCode
database setup works!
Reply all
Reply to author
Forward
0 new messages