codestriker-user Mailing List for Codestriker: collaborative code reviewer (Page 23)
Brought to you by:
sits
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(12) |
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
|
Feb
|
Mar
(1) |
Apr
(6) |
May
(3) |
Jun
(1) |
Jul
|
Aug
(9) |
Sep
(2) |
Oct
(2) |
Nov
(8) |
Dec
(6) |
| 2004 |
Jan
(12) |
Feb
(19) |
Mar
(2) |
Apr
(2) |
May
(4) |
Jun
(11) |
Jul
|
Aug
(14) |
Sep
(4) |
Oct
(27) |
Nov
(4) |
Dec
(22) |
| 2005 |
Jan
(14) |
Feb
(2) |
Mar
(11) |
Apr
(3) |
May
(14) |
Jun
(60) |
Jul
(58) |
Aug
(76) |
Sep
(72) |
Oct
(59) |
Nov
|
Dec
(4) |
| 2006 |
Jan
(1) |
Feb
(5) |
Mar
(13) |
Apr
(11) |
May
(30) |
Jun
(17) |
Jul
(18) |
Aug
(39) |
Sep
|
Oct
|
Nov
|
Dec
(17) |
| 2007 |
Jan
(18) |
Feb
(5) |
Mar
(20) |
Apr
(2) |
May
(3) |
Jun
(13) |
Jul
(11) |
Aug
(4) |
Sep
(6) |
Oct
(9) |
Nov
(3) |
Dec
|
| 2008 |
Jan
(10) |
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
(9) |
Jul
(10) |
Aug
(10) |
Sep
(13) |
Oct
(34) |
Nov
(12) |
Dec
(8) |
| 2009 |
Jan
(4) |
Feb
(11) |
Mar
(12) |
Apr
(3) |
May
(36) |
Jun
(4) |
Jul
(11) |
Aug
(12) |
Sep
(25) |
Oct
(13) |
Nov
(9) |
Dec
|
| 2010 |
Jan
|
Feb
(12) |
Mar
(6) |
Apr
(10) |
May
(12) |
Jun
|
Jul
(4) |
Aug
(9) |
Sep
(12) |
Oct
(3) |
Nov
(6) |
Dec
(3) |
| 2011 |
Jan
(2) |
Feb
(1) |
Mar
(3) |
Apr
(5) |
May
(3) |
Jun
(8) |
Jul
|
Aug
(14) |
Sep
|
Oct
(3) |
Nov
(1) |
Dec
|
| 2012 |
Jan
(2) |
Feb
(10) |
Mar
(4) |
Apr
(3) |
May
(2) |
Jun
(5) |
Jul
|
Aug
(3) |
Sep
|
Oct
(2) |
Nov
(4) |
Dec
(2) |
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(1) |
Nov
|
Dec
(2) |
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Jason R. <jre...@ya...> - 2006-08-02 02:44:02
|
Hi, One more thing. We (myself and David) only test on a limited sets of configurations. It is very possible that other combinations of tools will work just fine. Many configurations that we don't test on work fine. Perhaps somebody else on the list could respond with a working windows 2003 server + apache 2.0 configurations. Thanks Jason. --- DATACOM - Diego <di...@da...> wrote: > Hi all, > > that is my first attempt to install CodeStriker. I have a running > Windows Server 2003 + Apache 2.0.54 + MySQL 4.0.26 and was thinking to > use it to deploy CodeStriker. According to the manual, the preferred > versions are Apache 1.x and MySQL 4.1 or higher. Is it possible to run > CodeStrinker under my current configuration? > > I also read some messages about problems with MySQL 5.0. What would be > the most recommended configuration to run CodeStriker 1.9.2-rc3? Apache > version, MySQL version, Perl version, etc. > > Thanks in advance, > > -- > DIEGO Moreira da Rosa > > DATACOM > Av França, 735 - Porto Alegre, RS - 90230-220 > DDR: 51 3358 0141 > Fax: 51 3358 0101 > site: www.datacom-telematica.com.br > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Codestriker-user mailing list > Cod...@li... > https://lists.sourceforge.net/lists/listinfo/codestriker-user > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: Jason R. <jre...@ya...> - 2006-08-02 02:40:34
|
Hi, --- DATACOM - Diego <di...@da...> wrote: > Hi all, > > that is my first attempt to install CodeStriker. I have a running > Windows Server 2003 + Apache 2.0.54 + MySQL 4.0.26 and was thinking to > use it to deploy CodeStriker. According to the manual, the preferred > versions are Apache 1.x and MySQL 4.1 or higher. Is it possible to run > CodeStrinker under my current configuration? > I am running it under Apache 2.0.54 with mysql 4.0 on debian stable. It should work fine. > I also read some messages about problems with MySQL 5.0. What would be > the most recommended configuration to run CodeStriker 1.9.2-rc3? Apache > version, MySQL version, Perl version, etc. The problem with mysql 5.0 I believe was fixed in the latest rc version. If you plan on using a language other than English you should probably go for the newest stable version of perl. Recent versions of perl have a lot of unicode fixes that codestriker now needs. In general, codestriker works with just about any version of apache. The mysql 4.1 is needed if you want non-english comments. Otherwise 4.0 will work (I am running 4.0 with English only). Same with perl 5.8.anything is fine for English only, otherwise you will want the latest stable 5.8.8. Thanks Jason. > > Thanks in advance, > > -- > DIEGO Moreira da Rosa > > DATACOM > Av França, 735 - Porto Alegre, RS - 90230-220 > DDR: 51 3358 0141 > Fax: 51 3358 0101 > site: www.datacom-telematica.com.br > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Codestriker-user mailing list > Cod...@li... > https://lists.sourceforge.net/lists/listinfo/codestriker-user > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: DATACOM - D. <di...@da...> - 2006-08-01 21:46:34
|
Hi all, that is my first attempt to install CodeStriker. I have a running Windows Server 2003 + Apache 2.0.54 + MySQL 4.0.26 and was thinking to use it to deploy CodeStriker. According to the manual, the preferred versions are Apache 1.x and MySQL 4.1 or higher. Is it possible to run CodeStrinker under my current configuration? I also read some messages about problems with MySQL 5.0. What would be the most recommended configuration to run CodeStriker 1.9.2-rc3? Apache version, MySQL version, Perl version, etc. Thanks in advance, -- DIEGO Moreira da Rosa DATACOM Av França, 735 - Porto Alegre, RS - 90230-220 DDR: 51 3358 0141 Fax: 51 3358 0101 site: www.datacom-telematica.com.br |
|
From: Jason R. <jre...@ya...> - 2006-08-01 12:43:18
|
Hi, PRoblem 1 is caused by problem 2. Your repository need to be working in order for parrell view to work. I am not an perforce person, but your repository looks ok. You need to make the topic via the repository option, then the parrell view will work. Thanks Jason. --- "Wu, Xiaojie" <Xia...@tv...> wrote: > Hi: > > I have got Codestriker 1.9.2-rc1 up running, and I am able to create new projects, new topics, > upload review files, view the diffs, add comments and > so on. The SCM I am using is Perforce. The problem I am experiencing now is that perforce > doesn't seem to be integrated properly. I have two problems > right now: > (1) I can't retrieve the full file content when I click "Parallel" in the "Topic Text" page. > (2) It doesn't show "Repository:(What's this?)" row on the "Create new topic" page when I tried > to create a new topic. > > My settings in codestriker.conf for Perforce are: > > $p4 = 'C:/Program Files/Perforce'; > > @valid_repositories = > ( > 'perforce:MyPerforceUserName:MyPerforcePassword@PerforceServerName:Port' > ); > > Do you have any idea what could I missed? I would appreciate any suggestions! > > Thank you, > xiaojie > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV> _______________________________________________ > Codestriker-user mailing list > Cod...@li... > https://lists.sourceforge.net/lists/listinfo/codestriker-user > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: Jason R. <jre...@ya...> - 2006-08-01 12:39:33
|
Hi,
I think the problem is that codestriker expects the "root" to be .. from where the cgi directory
is. If you really want to fix this, you can change the perl code to emit a different html url.
package Codestriker::Http::UrlBuilder;
<snip...>
# Check if the HTML files are accessible vi another URL (required for
# sourceforge deployment). Check $Codestriker::codestriker_css.
my $htmlurl;
if (defined $Codestriker::codestriker_css &&
$Codestriker::codestriker_css ne "") {
$htmlurl = $Codestriker::codestriker_css;
$htmlurl =~ s/\/codestriker\.css//;
}
else {
# Standard Codestriker deployment.
$htmlurl = $query->url();
$htmlurl =~ s/codestriker\/codestriker\.pl/codestrikerhtml/;
}
$self->{htmldir} = $htmlurl;
return bless $self, $type;
}
change this line.
$htmlurl =~ s/codestriker\/codestriker\.pl/codestrikerhtml/;
To how you want to the URL structure to look. Without changing the perl code, you are stuck with
at least the
codestriker/codestriker.pl
codestrikerhtml
in your URL's. I seem to remember playing with this a long time ago. You may run into some other
minor problems when you remove codestriker.pl from the url. With a little bit of perl changes it
is definitly possible.
Thanks
Jason.
--- Tim Casada <tim...@sh...> wrote:
> I am no apache expert and I am trying to have a "pretty" URL for usage
> with codestriker instead of something like
> "http://XXX.XXX.XXX.XXX/codestriker/codestriker.pl". I am using a
> virtualhost setup and am trying to map the root of the URL to the
> codestiker perl module. Currently I'm using kind of the default config
> like this which does not work how I want it:
>
> Listen 80
> NameVirtualHost XXX.XXX.XXX.XXX:80
>
> <VirtualHost XXX.XXX.XXX.XXX:80>
> ServerName XXX.XXX.XXX.XXX
> BrowserMatch "MSIE" AuthDigestEnableQueryStringHack=On
>
> DocumentRoot /opt/codestriker/codestriker-1.9.2-rc1/cgi-bin/
> DirectoryIndex codestriker.pl
> AddDefaultCharset UTF8
>
> Alias /codestriker/ /opt/codestriker/codestriker-1.9.2-rc1/cgi-bin/
> Alias /codestrikerhtml/ /opt/codestriker/codestriker-1.9.2-rc1/html/
>
> <Location />
> AllowOverride None
> Options ExecCGI
> Order allow,deny
> Allow from all
> SetHandler cgi-script
> </Location>
>
> <Directory "/opt/codestriker/codestriker-1.9.2-rc1/html/">
> AllowOverride None
> Allow from all
> </Directory>
>
> </VirtualHost>
>
> --
> Tim Casada
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Codestriker-user mailing list
> Cod...@li...
> https://lists.sourceforge.net/lists/listinfo/codestriker-user
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
|
|
From: Wu, X. <Xia...@tv...> - 2006-07-31 21:54:17
|
Hi:
=20
I have got Codestriker 1.9.2-rc1 up running, and I am able to create new =
projects, new topics, upload review files, view the diffs, add comments =
and
so on. The SCM I am using is Perforce. The problem I am experiencing now =
is that perforce doesn't seem to be integrated properly. I have two =
problems
right now:
(1) I can't retrieve the full file content when I click "Parallel" in =
the "Topic Text" page.
(2) It doesn't show "Repository:(What's this?)" row on the "Create new =
topic" page when I tried to create a new topic.
=20
My settings in codestriker.conf for Perforce are:
=20
$p4 =3D 'C:/Program Files/Perforce';
=20
@valid_repositories =3D
(
=
'perforce:MyPerforceUserName:MyPerforcePassword@PerforceServerName:Port'
);
=20
Do you have any idea what could I missed? I would appreciate any =
suggestions!
=20
Thank you,
xiaojie
=20
|
|
From: Tim C. <tim...@sh...> - 2006-07-31 19:24:36
|
I am no apache expert and I am trying to have a "pretty" URL for usage with codestriker instead of something like "http://XXX.XXX.XXX.XXX/codestriker/codestriker.pl". I am using a virtualhost setup and am trying to map the root of the URL to the codestiker perl module. Currently I'm using kind of the default config like this which does not work how I want it: Listen 80 NameVirtualHost XXX.XXX.XXX.XXX:80 <VirtualHost XXX.XXX.XXX.XXX:80> ServerName XXX.XXX.XXX.XXX BrowserMatch "MSIE" AuthDigestEnableQueryStringHack=On DocumentRoot /opt/codestriker/codestriker-1.9.2-rc1/cgi-bin/ DirectoryIndex codestriker.pl AddDefaultCharset UTF8 Alias /codestriker/ /opt/codestriker/codestriker-1.9.2-rc1/cgi-bin/ Alias /codestrikerhtml/ /opt/codestriker/codestriker-1.9.2-rc1/html/ <Location /> AllowOverride None Options ExecCGI Order allow,deny Allow from all SetHandler cgi-script </Location> <Directory "/opt/codestriker/codestriker-1.9.2-rc1/html/"> AllowOverride None Allow from all </Directory> </VirtualHost> -- Tim Casada |
|
From: Jason R. <jre...@ya...> - 2006-07-30 13:49:51
|
Hi, I don't have any experience running codestriker under IIS. However, the missing parts of the URL comes from IIS. Codestriker expects the URL to be passed to it via the normal CGI environment. Given that you are getting the host name part of the URL (rather than just being empty), my guess would be that you have a configuration problem in IIS. I only have XP home available to me. Do you know if I can setup IIS to help? Thanks Jason. --- Fabio Hirata <fab...@ho...> wrote: > I installed codestriker-1.9.2-rc3 on Windows XP and I want to use it with > IIS. I ran the install.pl, and I can see the "Topic List" page just fine. > The problem is that all the links from the Topics List page have their paths > incorrect. > > For instance, the path for codestriker in my machine is: > http://localhost/codestriker/cgi-bin/codestriker.pl > > However, the link to Create New Topic is: > http://localhost/?action=create > > If I type the entire path, > (http://localhost/codestriker/cgi-bin/codestriker.pl?action=create), then I > can open the create page just fine. But the links in the create page are > also incorrect. (in Apache, everything works fine) > > Has anyone seem this problem? Any suggestions would be great! > > Thanks! > Fabio > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Codestriker-user mailing list > Cod...@li... > https://lists.sourceforge.net/lists/listinfo/codestriker-user > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: Fabio H. <fab...@ho...> - 2006-07-28 21:38:24
|
I installed codestriker-1.9.2-rc3 on Windows XP and I want to use it with IIS. I ran the install.pl, and I can see the "Topic List" page just fine. The problem is that all the links from the Topics List page have their paths incorrect. For instance, the path for codestriker in my machine is: http://localhost/codestriker/cgi-bin/codestriker.pl However, the link to Create New Topic is: http://localhost/?action=create If I type the entire path, (http://localhost/codestriker/cgi-bin/codestriker.pl?action=create), then I can open the create page just fine. But the links in the create page are also incorrect. (in Apache, everything works fine) Has anyone seem this problem? Any suggestions would be great! Thanks! Fabio |
|
From: Moisei R. <mo...@gm...> - 2006-07-25 10:42:15
|
Hi, just in case it is interesting to somebody. Today I faced following error when launched codestriker topic-list: DBD::ODBC::st fetchrow_array failed: [Microsoft][ODBC SQL Server Driver]String data, right truncation (SQL-01004)(DBD: st_fetch/SQLFetch (long truncated DBI attribute LongTruncOk not set and/or LongReadLen too small) err=-1) at ......../codestriker/bin/../lib/Codestriker/Model/Topic.pm line 260. After some review, I've found that LongReadLen is hardcoded to 1024000 in Database.pm line 64. After I increased this value x10 time (to 10240000) - I did not expire this error anymore. I did not do any more investigations, since this solution works well for me, however I am just wondered whether it is good enough. -- Best Regards, Moisei |
|
From: David S. <si...@us...> - 2006-07-21 06:34:36
|
Ok, I managed to reproduce this under Linux after all. I have modified all the email fields in install.pl to be length 200, and this fixes the issue. I have uploaded 1.9.2rc3 to SF. I have also attached the patch to install.pl to this email if you just want to apply that (after zapping your codestrikerdb database). I'll actually be away from email for the next two weeks on holidays, but Jason will be able to help you out if you still have issues. Thanks for the report. Cheers, David |
|
From: David S. <si...@us...> - 2006-07-21 05:54:13
|
I just tried 4.1.20 under Linux with no problems as well! This is very strange, perhaps under RHEL4, they have configured MySQL in a different way which has this limitation. Cheers, David David Sitsky wrote: > Well, under Windoze, MySQL 4.1.20 and 5.1 work fine without any change > to install.pl. Perhaps this is some specific issue with their Linux > implementation. > > Cheers, > David > > David Sitsky wrote: >> Well, isn't that interesting? Since moving to UTF8, worst case is 4 >> bytes per character, so now for varchar fields of length 255, MySQL >> probably reserves 255 * 4 bytes for it, which is now above this 1000 pk >> byte limit I have never heard of! >> >> I have been using MySQL 5.1, so I haven't seen this issue. This must be >> a limitation of earlier releases. >> >> Anyway - I'll make some changes so we can get this working. Bit of a >> pain alright, but changing the length of the fields to 100 is a >> reasonable workaround. I wouldn't expect any email addresses longer >> than that anyway. >> >> Cheers, >> David >> >> Vladimir Sizikov wrote: >>> Hi Tim, >>> >>> I meant to submit this problem as well. I see it on Fedora Core 5. >>> The workaround for me is rather simple. I replace email field length >>> from 255 to 100 (if I remember it correctly, there are 3 places in >>> install.pl where it should be done). >>> >>> After that, everything works fine. >>> >>> Thanks, >>> --Vladimir >>> >>> On 7/20/06, Tim Casada <tim...@sh...> wrote: >>>> I am having a problem with database creation in 1.9.2 on RHEL4 with >>>> MySQL 4.1.20. When I run install.pl I get the following error message: >>>> >>>> Checking for LWP::UserAgent (any) ok: found v2.031 >>>> Checking for CGI (v2.56) ok: found v3.05 >>>> Checking for Net::SMTP (any) ok: found v2.29 >>>> Checking for MIME::QuotedPrint (any) ok: found v3.07 >>>> Checking for DBI (v1.13) ok: found v1.40 >>>> Checking for Template (v2.07) ok: found v2.15 >>>> Checking for HTML::Entities (any) ok: found v1.27 >>>> Checking for File::Temp (any) ok: found v0.16 >>>> Checking for XML::RSS (v1.05) ok: found v1.10 >>>> Checking for Encode::Byte (any) ok: found v2.00 >>>> Checking for Encode::Unicode (any) ok: found v2.00 >>>> Checking for Authen::SASL (any) ok: found v2.10 >>>> Checking for DBD::mysql (any) ok: found v2.9004 >>>> Creating table topicusermetric... >>>> DBD::mysql::db do failed: Specified key was too long; max key length is >>>> 1000 bytes at ../lib/Codestriker/DB/Database.pm line 137. >>>> Unable to create table/indexes. >>>> >>>> Three tables get created successfully. >>>> >>>> mysql> show tables; >>>> +--------------------------+ >>>> | Tables_in_codestrikerdb2 | >>>> +--------------------------+ >>>> | topic | >>>> | topichistory | >>>> | topicviewhistory | >>>> +--------------------------+ >>>> 3 rows in set (0.00 sec) >>>> >>>> >>>> Any ideas? >>>> >>>> Thanks, >>>> >>>> -- >>>> Tim Casada >> >> ------------------------------------------------------------------------- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to share your >> opinions on IT & business topics through brief surveys -- and earn cash >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> _______________________________________________ >> Codestriker-user mailing list >> Cod...@li... >> https://lists.sourceforge.net/lists/listinfo/codestriker-user >> > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Codestriker-user mailing list > Cod...@li... > https://lists.sourceforge.net/lists/listinfo/codestriker-user > |
|
From: David S. <si...@us...> - 2006-07-21 04:38:54
|
Well, under Windoze, MySQL 4.1.20 and 5.1 work fine without any change to install.pl. Perhaps this is some specific issue with their Linux implementation. Cheers, David David Sitsky wrote: > Well, isn't that interesting? Since moving to UTF8, worst case is 4 > bytes per character, so now for varchar fields of length 255, MySQL > probably reserves 255 * 4 bytes for it, which is now above this 1000 pk > byte limit I have never heard of! > > I have been using MySQL 5.1, so I haven't seen this issue. This must be > a limitation of earlier releases. > > Anyway - I'll make some changes so we can get this working. Bit of a > pain alright, but changing the length of the fields to 100 is a > reasonable workaround. I wouldn't expect any email addresses longer > than that anyway. > > Cheers, > David > > Vladimir Sizikov wrote: >> Hi Tim, >> >> I meant to submit this problem as well. I see it on Fedora Core 5. >> The workaround for me is rather simple. I replace email field length >> from 255 to 100 (if I remember it correctly, there are 3 places in >> install.pl where it should be done). >> >> After that, everything works fine. >> >> Thanks, >> --Vladimir >> >> On 7/20/06, Tim Casada <tim...@sh...> wrote: >>> I am having a problem with database creation in 1.9.2 on RHEL4 with >>> MySQL 4.1.20. When I run install.pl I get the following error message: >>> >>> Checking for LWP::UserAgent (any) ok: found v2.031 >>> Checking for CGI (v2.56) ok: found v3.05 >>> Checking for Net::SMTP (any) ok: found v2.29 >>> Checking for MIME::QuotedPrint (any) ok: found v3.07 >>> Checking for DBI (v1.13) ok: found v1.40 >>> Checking for Template (v2.07) ok: found v2.15 >>> Checking for HTML::Entities (any) ok: found v1.27 >>> Checking for File::Temp (any) ok: found v0.16 >>> Checking for XML::RSS (v1.05) ok: found v1.10 >>> Checking for Encode::Byte (any) ok: found v2.00 >>> Checking for Encode::Unicode (any) ok: found v2.00 >>> Checking for Authen::SASL (any) ok: found v2.10 >>> Checking for DBD::mysql (any) ok: found v2.9004 >>> Creating table topicusermetric... >>> DBD::mysql::db do failed: Specified key was too long; max key length is >>> 1000 bytes at ../lib/Codestriker/DB/Database.pm line 137. >>> Unable to create table/indexes. >>> >>> Three tables get created successfully. >>> >>> mysql> show tables; >>> +--------------------------+ >>> | Tables_in_codestrikerdb2 | >>> +--------------------------+ >>> | topic | >>> | topichistory | >>> | topicviewhistory | >>> +--------------------------+ >>> 3 rows in set (0.00 sec) >>> >>> >>> Any ideas? >>> >>> Thanks, >>> >>> -- >>> Tim Casada > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Codestriker-user mailing list > Cod...@li... > https://lists.sourceforge.net/lists/listinfo/codestriker-user > |
|
From: David S. <si...@us...> - 2006-07-21 02:33:55
|
Well, isn't that interesting? Since moving to UTF8, worst case is 4 bytes per character, so now for varchar fields of length 255, MySQL probably reserves 255 * 4 bytes for it, which is now above this 1000 pk byte limit I have never heard of! I have been using MySQL 5.1, so I haven't seen this issue. This must be a limitation of earlier releases. Anyway - I'll make some changes so we can get this working. Bit of a pain alright, but changing the length of the fields to 100 is a reasonable workaround. I wouldn't expect any email addresses longer than that anyway. Cheers, David Vladimir Sizikov wrote: > Hi Tim, > > I meant to submit this problem as well. I see it on Fedora Core 5. > The workaround for me is rather simple. I replace email field length > from 255 to 100 (if I remember it correctly, there are 3 places in > install.pl where it should be done). > > After that, everything works fine. > > Thanks, > --Vladimir > > On 7/20/06, Tim Casada <tim...@sh...> wrote: >> I am having a problem with database creation in 1.9.2 on RHEL4 with >> MySQL 4.1.20. When I run install.pl I get the following error message: >> >> Checking for LWP::UserAgent (any) ok: found v2.031 >> Checking for CGI (v2.56) ok: found v3.05 >> Checking for Net::SMTP (any) ok: found v2.29 >> Checking for MIME::QuotedPrint (any) ok: found v3.07 >> Checking for DBI (v1.13) ok: found v1.40 >> Checking for Template (v2.07) ok: found v2.15 >> Checking for HTML::Entities (any) ok: found v1.27 >> Checking for File::Temp (any) ok: found v0.16 >> Checking for XML::RSS (v1.05) ok: found v1.10 >> Checking for Encode::Byte (any) ok: found v2.00 >> Checking for Encode::Unicode (any) ok: found v2.00 >> Checking for Authen::SASL (any) ok: found v2.10 >> Checking for DBD::mysql (any) ok: found v2.9004 >> Creating table topicusermetric... >> DBD::mysql::db do failed: Specified key was too long; max key length is >> 1000 bytes at ../lib/Codestriker/DB/Database.pm line 137. >> Unable to create table/indexes. >> >> Three tables get created successfully. >> >> mysql> show tables; >> +--------------------------+ >> | Tables_in_codestrikerdb2 | >> +--------------------------+ >> | topic | >> | topichistory | >> | topicviewhistory | >> +--------------------------+ >> 3 rows in set (0.00 sec) >> >> >> Any ideas? >> >> Thanks, >> >> -- >> Tim Casada |
|
From: Vladimir S. <vsi...@gm...> - 2006-07-20 16:39:50
|
Hi Tim, I meant to submit this problem as well. I see it on Fedora Core 5. The workaround for me is rather simple. I replace email field length from 255 to 100 (if I remember it correctly, there are 3 places in install.pl where it should be done). After that, everything works fine. Thanks, --Vladimir On 7/20/06, Tim Casada <tim...@sh...> wrote: > I am having a problem with database creation in 1.9.2 on RHEL4 with > MySQL 4.1.20. When I run install.pl I get the following error message: > > Checking for LWP::UserAgent (any) ok: found v2.031 > Checking for CGI (v2.56) ok: found v3.05 > Checking for Net::SMTP (any) ok: found v2.29 > Checking for MIME::QuotedPrint (any) ok: found v3.07 > Checking for DBI (v1.13) ok: found v1.40 > Checking for Template (v2.07) ok: found v2.15 > Checking for HTML::Entities (any) ok: found v1.27 > Checking for File::Temp (any) ok: found v0.16 > Checking for XML::RSS (v1.05) ok: found v1.10 > Checking for Encode::Byte (any) ok: found v2.00 > Checking for Encode::Unicode (any) ok: found v2.00 > Checking for Authen::SASL (any) ok: found v2.10 > Checking for DBD::mysql (any) ok: found v2.9004 > Creating table topicusermetric... > DBD::mysql::db do failed: Specified key was too long; max key length is > 1000 bytes at ../lib/Codestriker/DB/Database.pm line 137. > Unable to create table/indexes. > > Three tables get created successfully. > > mysql> show tables; > +--------------------------+ > | Tables_in_codestrikerdb2 | > +--------------------------+ > | topic | > | topichistory | > | topicviewhistory | > +--------------------------+ > 3 rows in set (0.00 sec) > > > Any ideas? > > Thanks, > > -- > Tim Casada > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Codestriker-user mailing list > Cod...@li... > https://lists.sourceforge.net/lists/listinfo/codestriker-user > |
|
From: Tim C. <tim...@sh...> - 2006-07-20 13:51:53
|
I am having a problem with database creation in 1.9.2 on RHEL4 with MySQL 4.1.20. When I run install.pl I get the following error message: Checking for LWP::UserAgent (any) ok: found v2.031 Checking for CGI (v2.56) ok: found v3.05 Checking for Net::SMTP (any) ok: found v2.29 Checking for MIME::QuotedPrint (any) ok: found v3.07 Checking for DBI (v1.13) ok: found v1.40 Checking for Template (v2.07) ok: found v2.15 Checking for HTML::Entities (any) ok: found v1.27 Checking for File::Temp (any) ok: found v0.16 Checking for XML::RSS (v1.05) ok: found v1.10 Checking for Encode::Byte (any) ok: found v2.00 Checking for Encode::Unicode (any) ok: found v2.00 Checking for Authen::SASL (any) ok: found v2.10 Checking for DBD::mysql (any) ok: found v2.9004 Creating table topicusermetric... DBD::mysql::db do failed: Specified key was too long; max key length is 1000 bytes at ../lib/Codestriker/DB/Database.pm line 137. Unable to create table/indexes. Three tables get created successfully. mysql> show tables; +--------------------------+ | Tables_in_codestrikerdb2 | +--------------------------+ | topic | | topichistory | | topicviewhistory | +--------------------------+ 3 rows in set (0.00 sec) Any ideas? Thanks, -- Tim Casada |
|
From: David S. <si...@us...> - 2006-07-12 00:05:01
|
> I can confirm that after I modify the line to be like this:
> if ($line =~ /^svn: (warning:)? URL '.*' refers to a directory/) {
>
> The problem is gone.
I have made this a bit more general for now - but have committed in your
fix.
if ($line =~ /^svn:.*URL '.*' refers to a directory/) {
Perhaps after 1.9.2 is released, we can do this properly using error
return codes instead, but the above fix will be in for 1.9.2.
I'd be keen to see if there is a unique error code for this situation.
Cheers,
David
|
|
From: David S. <si...@us...> - 2006-07-11 23:58:14
|
Hi Vladimir,
Many thanks for your report.
> [...]
> I tracked down the problem to Subversion.pm file, line 146:
> if ($line =~ /^svn: URL '.*' refers to a directory/) {
>
> The problem here is that at least with my Subversion 1.3.2 the output
> from svn cat command is DIFFIRENT:
> svn: warning: URL 'blah-blah-blah' refers to a directory
> [...]
Thanks - I can certaintly change the regexp as you have indicated.
> P.S. I wonder what non-English users of subversion would get from svn
> cat, if their svn is localized.... :) Codestriker uses hardcoded
> English...
Agreed - it would be much better to perhaps use the error code returned
by the svn process, so that this will also work for localised svn
installations.
Does subversion return a unique error code number when this situation
occurs?
I'm not a subversion user yet, so I can't easily check this out..
Cheers,
David
|
|
From: Vladimir S. <vsi...@gm...> - 2006-07-11 18:27:01
|
Hi,
Let's say I have branches/vvs/feature_4 branch that I've finished and
would like to get a review. I submit it for the review via CodeStriker
1.9.2 alpha-9.
Let's say also that I've modified a file Defs.mk in build subdir.
But reviewers will see the following file names:
branches/vvs/build/Defs.mk (please note that feature_4 part is MISSING!)
I tracked down the problem to Subversion.pm file, line 146:
if ($line =~ /^svn: URL '.*' refers to a directory/) {
The problem here is that at least with my Subversion 1.3.2 the output
from svn cat command is DIFFIRENT:
svn: warning: URL 'blah-blah-blah' refers to a directory
Please note an extra token - warning:
It seems that CodeStriker should be more flexible and should handle
both outputs, from older Subversion and from newer Subversions: with
"warning:" and without it.
I can confirm that after I modify the line to be like this:
if ($line =~ /^svn: (warning:)? URL '.*' refers to a directory/) {
The problem is gone.
I'm hoping this would end up in final 1.9.2.
Thank you for the great tool,
--Vladimir
P.S. I wonder what non-English users of subversion would get from svn
cat, if their svn is localized.... :) Codestriker uses hardcoded
English...
|
|
From: David S. <si...@us...> - 2006-07-11 06:55:29
|
Hi Chand, At this stage - its code only. There was some talk a while back about extending Codestriker to handle generic documents, but it is no simple task. Also - Adobe and Microsoft Word have built in reviewing features, which while not perfect, tend to satisfy a lot of people. Having said all that - you can just upload a text file into Codestriker to review it. Cheers, David Chand Warrier Consultant wrote: > Hi, > > I liked the product Codestriker and hence would like to know if codestriker can be used only for reviewing code or it can also be used for reviewing documents also e.g. design document in MS Word format. > > I didn't find the information in "The Codestriker Guide" Version 1.9.0. > > Regards, > Chand Warrier > Infinera India Pvt Ltd > |
|
From: David S. <si...@us...> - 2006-07-06 00:13:23
|
Codestrikers, At long last - version 1.9.2 is coming your way. Please go down to the downloads page from http://codestriker.sourceforge.net and download this release candidate for testing. This release contains a stack of new features since 1.9.1, which I have attached to this email, with contributions from many people. Cheers, David Version 1.9.2 * Codestriker now works with UTF-8 text, to support unicode character input for topic titles, descriptions, comment text, and project names and descriptions. This required making Perl 5.8 as a pre-requisite, as Perl 5.6 doesn't cut the mustard for unicode processing. * Created a new optional configuration parameter $repository_name_map in codestriker.conf. This allows for a user-defined repository name to be displayed in the codestriker UI, rather than the full repository URL. This can be useful for hiding potentially sensitive username/password information that might be a part of the repository URL. See the codestriker.conf file for more information. Submitted by Edwin Fine <edw...@ve...>. * New repository module for linking to ClearCase dynamic views. See the configuration file and/or manual for example configurations. Submitted by Avinandan Sengupta <avi...@gm...>. * Modified the way Perforce retrieves files from the depot, as servers set with a security level of 2 or above were not receiving password information. This has been addressed by modifying the command line to explictly pass in the password rather than the client workspace name, which is ignored for these security levels. The repository configuration for Perforce has also been changed to use the password in place of the client workspace name. Perforce users should update their configuration files appropriately. Submitted by J Dickon Glanville <jdg...@us...>. * Update CVS diff parser to handle rdiffs which have new/removed files in them. * Creating a topic with an invalid bug ID is now shown as an error to the user on the create topic screen. * If there was an error creating a topic, the selected project name was not retained when the create topic screen was redisplayed. This has now been fixed. Submitted by Edwin Fine <edw...@ve...>. * If there is a problem when a comment is created, the error message will correctly display in the AJAX'ed window. An example here is if $mailhost is incorrectly configured. * If there is an email problem while creating a topic, the error message is now correctly displayed to the end-user. * Fixed problem with Subversion repositories on Win32, where Codestriker was unable to launch the svn program. * Comments containing '+' characters were changed into ' ' characters when posted via AJAX. Other potentially damaging characters are now escaped. * Comments with '\' characters are now displayed correctly in all cases within the tooltip window. * Temporary files were not being deleted within the CodestrikerClient.pm module (used for auto-creation of topics on CVS commits). Reported by Martin Apel <Mar...@so...>. * Added support for parsing diffs generated using Subversion's svnlook program. * Matching of CVS repository paths when parsing topic text is now case insensitive to account for the different casing returned by the Window clients: Cygwin and CvsNT. * Defining new entries in $comment_state_metrics in codestriker.conf could not be used for existing topics. This has now been fixed. * Support for sending email via SMTP authentication, via the optional $mailuser and $mailpasswd configuration parameters in codestriker.conf. Contributed by "Hertz Wang" <wa...@ne...>. * The ClearCase Snapshot repository was not using the $tmpdir setting in codestriker.conf if it was set when creating temporary files. This has now been fixed. Contributed by "John Farrelly (AT/LMI)" <joh...@er...>. * Make sure the diffs in the topic are presented in a sorted order by filename. Some SCMs create topic texts in a "semi-sorted" order, such as Subversion. Contributed by "Vladimir Vysotsky" <vvy...@av...>. * Closed topics could still have comments added to them, by hovering over an existing comment in the topic text view, and then clicking the "Add Comment" link in the tooltip window. This link has now been removed if the topic is closed. Contributed by ed....@si.... * Improved memory usage when integrated with very large LXR databases. Contributed by Patrick Diamond <pat...@ma...>. |
|
From: Moisei R. <mo...@gm...> - 2006-07-01 21:35:31
|
> 2. When you clicked on the "issue" topic, it would show all of the commits + comments that include > that comment in its checkin comment. The commits would be shown newest to oldest in the topic. yes! and if there will be another button like "close all the related topics" - it would almost ideal. > It sounds to me like you really want to look at the repository/codestriker from an issue point of > view, rather than a check in point of view. Do you always put the issue numbers into the checkin > comment? Codestriker can't do this, but lets imagine for the sake of the discussion the following. we have our own issue tracker and we use the "stable branches" model. the policy is that commit to the "stable branch" mandatory has an issue reference (it's checked by the svn hook). for the trunk it is not mandatory. but I do not plan (at least now) to have an integration between issue tracker and codestriker. I can put in place another policy to have a topic-id somehow recognizable mentioned in that commits that answer some other code-strike comments (well, as I told, in our case the uniq id is the revision, so I can require to write in the comment something like #r12345 so I can translate it through the svn hook to the real codestriker id) and then the svn hook will update the codestriker accordingly - i.e create new topic that includes comments to the mentioned ones. Thanks! |
|
From: Jason R. <jre...@ya...> - 2006-07-01 13:50:57
|
Hi, It sounds to me like you really want to look at the repository/codestriker from an issue point of view, rather than a check in point of view. Do you always put the issue numbers into the checkin comment? Codestriker can't do this, but lets imagine for the sake of the discussion the following. 1. The top level cs window showed one topic per issue. 2. When you clicked on the "issue" topic, it would show all of the commits + comments that include that comment in its checkin comment. The commits would be shown newest to oldest in the topic. How does this sound? Back to earth, codestriker generates a topicid that is random and unique per topic when it is added in. It is primary key of the topic table. The commentdata_table also has a unique id. Thanks Jason --- Moisei Rabinovich <mo...@gm...> wrote: > Hi, > yes, it's kind of "keep an eye" code review type, just note we are 25 > developers team working on the regular base. > Usually we have about 100 commits a day, so the "eye" must be a strong one. > I can implement an obsolete through the svn hook - it's not a big deal, > simple build the http post carefully. > But what I really missing in codestriker is a kind of relationships between > topics. > It's more complicate than just obsoleteusually topics has few comments not > just one, > from the developer point of view , the commits fix some of them, not all in > one shot and some commits > could fix the the comments from different topics. > On other hand, from the reviewer point of view it would be much easy to > follow the full review history of each issue, > then browse through the different topics as she has to do now. > The ven more complicated case when the fix is not acccepted by the reviewer > or the fix raises new issues. > > As the first step in this direction, I would propose to have the uniq > identifier for each topic (in our case it's a revision) > and uniq identifier for each item inside of the topic (simple numbers > generated automatically ). > > On 6/22/06, David Sitsky < si...@us...> wrote: > > > > Moisei Rabinovich wrote: > > > Hello dear all, > > > I've setup the subversion hook to create a new topic in codestriker on > > > every commit and it works just fine. > > > Now, I am looking for a god way to "link" the commits done based on the > > > review to the original topic. > > > Is there some recommended way? > > > > > > The scenario is like: > > > developer commit some code [new topic created] > > > the reviewer mention the problem in file X1 line Y1 and file X2 line Y2 > > > [mails sent] > > > the developer fixes the X1,Y1 and commits [new topic is created.... not > > > so good... it still relates to the origibal topic... should the original > > > one be obsoleted byt he new one?] > > > > Yes, we need to somehow obsolete the original topic with the new topic. > > This is easy to do if the topics are created "by hand", but via the > > SCM commit hook, we need to handle this in a different way. > > > > I can see a couple of options here, which Jason has already eluded to: > > > > * In the topic description, we could perhaps introduce another magical > > auto-link text, so that if you type in Topic 73514332, this would > > automatically hyperlink to that topic. We actually do this with Bug > > XXXX text if a bug tracker has been enabled. > > > > That way, the developer can add the Topic XXXXXXX text to their commit > > message, as a way of linking topics together. > > > > They can actually do this today, just by adding a full hyperlink to the > > topic they are obsoleting, as Codestriker will render hyperlinks > > automatically. > > > > * Another option would be to have a new field in the topic properties > > tab, something like "Superseeds Topics: XXXXXX", as a way of creating an > > obsolete link directly. The onus would be on somebody to then update > > this field to maintain your links. > > > > Does anyone else have any other ideas? > > > > Cheers, > > David > > > > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > > _______________________________________________ > Codestriker-user mailing list > Cod...@li... > https://lists.sourceforge.net/lists/listinfo/codestriker-user > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: Moisei R. <mo...@gm...> - 2006-06-30 09:02:54
|
Hi, yes, it's kind of "keep an eye" code review type, just note we are 25 developers team working on the regular base. Usually we have about 100 commits a day, so the "eye" must be a strong one. I can implement an obsolete through the svn hook - it's not a big deal, simple build the http post carefully. But what I really missing in codestriker is a kind of relationships between topics. It's more complicate than just obsoleteusually topics has few comments not just one, from the developer point of view , the commits fix some of them, not all in one shot and some commits could fix the the comments from different topics. On other hand, from the reviewer point of view it would be much easy to follow the full review history of each issue, then browse through the different topics as she has to do now. The ven more complicated case when the fix is not acccepted by the reviewer or the fix raises new issues. As the first step in this direction, I would propose to have the uniq identifier for each topic (in our case it's a revision) and uniq identifier for each item inside of the topic (simple numbers generated automatically ). On 6/22/06, David Sitsky < si...@us...> wrote: > > Moisei Rabinovich wrote: > > Hello dear all, > > I've setup the subversion hook to create a new topic in codestriker on > > every commit and it works just fine. > > Now, I am looking for a god way to "link" the commits done based on the > > review to the original topic. > > Is there some recommended way? > > > > The scenario is like: > > developer commit some code [new topic created] > > the reviewer mention the problem in file X1 line Y1 and file X2 line Y2 > > [mails sent] > > the developer fixes the X1,Y1 and commits [new topic is created.... not > > so good... it still relates to the origibal topic... should the original > > one be obsoleted byt he new one?] > > Yes, we need to somehow obsolete the original topic with the new topic. > This is easy to do if the topics are created "by hand", but via the > SCM commit hook, we need to handle this in a different way. > > I can see a couple of options here, which Jason has already eluded to: > > * In the topic description, we could perhaps introduce another magical > auto-link text, so that if you type in Topic 73514332, this would > automatically hyperlink to that topic. We actually do this with Bug > XXXX text if a bug tracker has been enabled. > > That way, the developer can add the Topic XXXXXXX text to their commit > message, as a way of linking topics together. > > They can actually do this today, just by adding a full hyperlink to the > topic they are obsoleting, as Codestriker will render hyperlinks > automatically. > > * Another option would be to have a new field in the topic properties > tab, something like "Superseeds Topics: XXXXXX", as a way of creating an > obsolete link directly. The onus would be on somebody to then update > this field to maintain your links. > > Does anyone else have any other ideas? > > Cheers, > David > |
|
From: David S. <si...@us...> - 2006-06-28 00:04:01
|
Hi Tom, You can't do this directly, but what you can do is simply add the URL of your specification document into the topic's description. That way, a reviewer who reads the description, can follow the hyperlink to read the specification. Cheers, David tom...@pr... wrote: > Hello, > > Please forgive me if I missed this somewhere. > > Is it possible to attach documents MS Word (or any other document type) > to a topic to show the specifications for the functions being reviewed? > > We have specification documents written in MS Word format, I would like > to attach the specification document to the topic so that the reviewer > has the specification and code right there to review. > > Is there another solution? > > Thank you, > > Tom. |