World: r3wp

I've changed the format of the GUID field in RSS feeds, so you'll 
get duplicate entries for the recent changes, just ignore them or 
delete the old ones.

There was a 5h outage on curecode.org affecting cheyenne-server.org 
and softinnov.org. It has been fixed just a few minutes ago.


After short investigation, it seems that a PHP internal issue (frozen 
process) caused a fatal error in Cheyenne main process. The error 
is very weird, see below the disarmed REBOL error :

make object! [
    code: 301
    type: 'script
    id: 'need-value
    arg1: evt:
    arg2: none
    arg3: none
    near: [evt: do-events 
        either none? evt
    ]
    where: 'do-cheyenne-app
]


So, DO-EVENTS (which is basically just WAIT [ ]) returned an unset! 
value. Does anyone know here if this a known behaviour or a REBOL 
bug?

I've never seen this.

any update on adding the R3 GUI as a project to curecode?

R3 GUI project added to CureCode, ticket http://issue.cc/r3/1837
moved to R3 GUI.

I've added alpha 110 & 111 to versions list, let me know if you need 
categories too (I would need an ordered list of items for that).

Great, thanks.

cool :-)

Sorry for the delay, I forgot about it until Henrik mentioned it 
again yesterday.

it's ok. now we have it. :-)

Doc, can you create a CC login for me please. Thx.

You have one already.

Loginid Robert.

Also Robert-Muench (another login)

:-) Good to know... let's try if I remember my password.

I don't know if there is a password recovery service; why don't you 
find out?

Ok, worked.

password recovery service
; sure, from home page -> Reset Password link

Doc, I am interested into using your product for tracking bug of 
other applications but we need Project and Subproject. Is there any 
plan to add subprojects ?

There's no "subproject" concept in CC, but you can use "category" 
field to divide a project. I have no plan to add such feature this 
year.

http://issue.cc/r3/1027

The state of the ticket should be revised

Doc, a little thing: the title.inc file for 0.9.12 needs to be updated. 
Or perhaps, the zip file is really .11. In any case, still a great 
app.

The ZIP file is 0.9.12, I left an older file version when I built 
the 0.9.12 archive. Issue fixed and 0.9.12 archive re-published. 
Thanks for reporting this issue.

NP ... get back to RED.  :-)

James: sure, I did that during my coffee break ;-)

Doc, I still have issues with the cookies created from Curecode. 
Essentially, when I leave the browser open and the session expires, 
the next time I try to use curecode, it loads up the error page. 
I just manually delete the cookie and I'm good and I have extended 
the timeout as well which helps. I was wondering in the httpd.cfg 
file if there is any value for curecode's timeout that will make 
it endless (perhaps "none" ? ). Thanks. It is a very usefule app.

There is no endless timeout value. Such feature would blow up the 
server's RAM sooner or later.

the next time I try to use curecode, it loads up the error page.

 Could you be more specific? On what page do you let the browser open? 
 What do you do when you resume your work after the session expires 
 (on what link/button do you click)?

I'll have to verify when it happens again but I think it's the "Sorry. 
this page cannot be displayed." And any link clicked will cause this 
to come up.  Doc, this is not super important because changing the 
timeout helps. I'll wait until it happens again and give you better 
details. How's that  sound?

Besides, no one else seems to have this issue so it could very well 
be something on my side.

Thanks, that would help, as I tried several times to reproduce your 
issue without success. By the way, what browser (and version) are 
you using?

Do you have a browser plugin or any other tool installed that could 
remove or alter in any way your browser cookies?

I use FF 5.0 (just upgraded this morning though. Previously it was 
4.0.1). As far as cookie altering tools, not that I know of, though 
I was wondering if AVG could be doing something. Anyway, I just cost 
you a few lost Red minutes. I'll wait until it happens again.
Thanks.

No problem, I am used to multiplex different tasks. ;-)

At some point recently, Chrome started saving the username and password 
in CureCode. Don't know whether this was a CC or Chrome change, but 
it's welcome either way.

I guess it's a Chrome change, last update on CureCode site was in 
January.

Doc, it says in the trace.log that there is an SQL error:


** User Error : ERROR 1064 : You have an error in your SQL syntax; 
check the manual that corresponds to your MySQL server version for 
the right syntax to use near '' at line 6 
	** Where: none 
	** Near:  [do-sql/flat 'r3bugs [{

I will have a look, but it has probably been fixed since v0.9.8.

well, it worked before, but I'm curious about the near '<unknown 
char>' bit

if there are no dangers in upgrading curecode, I may do that instead.

trying 0.9.12 and getting this crash:


        URL  = /bugs/
        File = /home/henrikmk/serve/www/bugs/head.rsp

        ** Script Error : Invalid path value: locals 
        ** Where: repend 
        ** Near:  [request/config/locals/instance 
%title.inc

This is with the latest cheyenne release 0.9.20.

Have you followed the migration process? There's a migration script 
in the archive, probably in the /private folder.

It's the %private/upgrade-096-0910.r script.

I see, will try.

There doesn't seem to be such a script. There is however an install.r 
script.

About your error, the newest CureCode versions require the definition 
of a LOCALS block in the webapp:

	locals [
		name		"REBOL3 Tracker"
		instance	%rebol3/
		short		"r3"
	]

private$ ls

ChangeLog.txt     build-db.sql   generate-load.r  helper.r   instances
access-control.r  db-abstract.r  generate-test.r  install.r

I see, thanks.

ok, it looks like I'm going to need that upgrade script. where can 
I find it? it's not included in the distribution.

http://curecode.org/dl/upgrade-096-0910.zip


I am not sure it applies to 0.9.8, you'll need to check if the new 
SQL  tables are already there or not.