AltME groups: search

hmm, as I can see, RAMBO needs "moste requested fix" voting mechanism, 
or we start missuing blog for that :-)

wow, nice to see the bugfixes for 2.7.6 piling up in RAMBO

please guys keep in mind we can't fix all bugs at once. and we can't 
usually fix two "big" bugs at once (big means it takes a lot of time 
for Carl to figure it out). so we fix one big bug and many small 
ones (bugs that can be fixed in a couple minutes always have precedence 
because there's no point in making them stay for years on rambo).

Then again, it isn't always easy to lift the bug from  [long running 
 / large volumes of data / 1000s of lines of script] applications, 
and set it into a small example.

I once tried to produce a small script that relicated the block-manipulating 
logic of an app I have. I was hoping that running it over night would 
create a "should not happen" bug. It never did.

By way of compensation. I did find this one-liner that will crash 
(without warning) every version of REBOL I've tried it on:

     a: copy [] b: copy [] insert/only a b insert/only b a same? a b
(I think I reported that, but it was before RAMBO)

Sunanda, IIRC that bug was in RAMBO and was fixed some time ago (maybe 
2.6.2 or something like that)

http://www.rebol.net/cgi-bin/rambo.r?id=3259&

i put this on rambo a while ago (same reason, imap servers)

http://www.rebol.net/cgi-bin/rambo.r?id=4302&

Is RAMBO still active? Many bugs probably there. I wonder if over 
the time (depends on how long we want to continue to maintain R2 
family of products) we should port it to CureCode?

2.7.7 release

Call
dockimbel:

About CALL console window issue, the CreateProcess( ) win32 call 
has flags to hide the window. There just need to be set.

In the STARTUPINFO used by CreateProcess( ), just set in dwFlags, 
the STARTF_USESHOWWINDOW flag and set wShowWindow to SW_HIDE.

maybe add a new refinement and let the users decide when they want 
to see the console window ?
or maybe just /show

Paul:
Run is not enabled

Graham

Is anyone concerned that shell windows opened in Encap do not contain 
the correct window title?
Rambo #3660 ( reported march 2005 )

Brian

For me, the big question is what kind of release we will be doing:

- 2.7.7: Patching glaring bugs in a few natives, VID fixes, and continuing 
the backports and mezzanine fixes.

- 2.8.0: Backporting some of the R3 native changes (function, not 
infrastructre), and the above.

I think that the decision a long time ago was to focus on R3 as a 
priority, and just patch up R2 as necessary.

At the very least, I would want a 2.7.7 to have a version that fixes 
post-2.7.6 mezzanine bugs, and 2.7 series regressions vs. 2.6.3.

Henrik
We also need to implement BrianH's new window resize scheme.

Ashley,Anton, Brian, etc ... VID fixes

Graham
Fixes to prot-http to support put etc.

BrianH

SQL_FLOAT and SQL_REAL are converted the same way, just with different 
sizes. And yet SQL_REAL works and SQL_FLOAT doesn't, at least with 
SQL Native Client (an ODBC 3.5 driver). Perhaps that difference can 
point you in the right direction.

Henrik
view/new make face []
a: open/binary/direct/no-wait tcp://:9000
forever [wait reduce [ a 0.001]]


This produces a 16 byte leak when started. And when I move the window 
and click in it, I get a lot of 64 byte leaks.

LAUNCH affects the View desktop too. How is it broken? Is there a 
RAMBO bug report about this?

http://www.rebol.net/cgi-bin/rambo.r?id=4205&

dunno about anton's report http://www.rebol.net/cgi-bin/rambo.r?id=4245&

I posted this report in 2004 http://www.rebol.net/cgi-bin/rambo.r?id=3557&

and Maarten also posted the same bug in 2005 http://www.rebol.net/cgi-bin/rambo.r?id=3593&

2.7.7 release

Call
dockimbel:

About CALL console window issue, the CreateProcess( ) win32 call 
has flags to hide the window. There just need to be set.

In the STARTUPINFO used by CreateProcess( ), just set in dwFlags, 
the STARTF_USESHOWWINDOW flag and set wShowWindow to SW_HIDE.

maybe add a new refinement and let the users decide when they want 
to see the console window ?
or maybe just /show

Paul:
Run is not enabled

Graham

Is anyone concerned that shell windows opened in Encap do not contain 
the correct window title?
Rambo #3660 ( reported march 2005 )

Brian

For me, the big question is what kind of release we will be doing:

- 2.7.7: Patching glaring bugs in a few natives, VID fixes, and continuing 
the backports and mezzanine fixes.

- 2.8.0: Backporting some of the R3 native changes (function, not 
infrastructre), and the above.

I think that the decision a long time ago was to focus on R3 as a 
priority, and just patch up R2 as necessary.

At the very least, I would want a 2.7.7 to have a version that fixes 
post-2.7.6 mezzanine bugs, and 2.7 series regressions vs. 2.6.3.

Henrik
We also need to implement BrianH's new window resize scheme.

Ashley,Anton, Brian, etc ... VID fixes

Graham
Fixes to prot-http to support put etc.

BrianH

SQL_FLOAT and SQL_REAL are converted the same way, just with different 
sizes. And yet SQL_REAL works and SQL_FLOAT doesn't, at least with 
SQL Native Client (an ODBC 3.5 driver). Perhaps that difference can 
point you in the right direction.

Henrik
view/new make face []
a: open/binary/direct/no-wait tcp://:9000
forever [wait reduce [ a 0.001]]


This produces a 16 byte leak when started. And when I move the window 
and click in it, I get a lot of 64 byte leaks.

BrianH, ok, Carl would know about it, so I'll discuss it with him. 
Regarding leak, it's in RAMBO, need to find the ID, hang on.

Next month we'll be migrating RAMBO to CureCode, then retiring it. 
It's best to continue using it for now though.

Ah, there it is. I thought I had put it in RAMBO.

I don't know much about the TLS support in R2, if any. I guess I'll 
find out when we migrate the old RAMBO tickets to CureCode.

OK, now that we have 2.7.7 released (even though there is more work 
to do, i.e. platforms and the SDK), it is time to look ahead to 2.7.8 
- which is scheduled for release in one month on February 1. The 
primary goal of this release is to migrate to REBOL's new development 
infrastructure. This means:

- Migrating the RAMBO database to a new CureCode project and retiring 
RAMBO.

- Using Carl's generation code for the manual to regenerate the R2 
manual, so we can start to get to work updating it.

- Porting the chat client to R2 using the new functions and building 
a CHAT function into R2 similar to the R3 version.


The R2 chat client might be limited to the ASCII character set, though 
support for the Latin-1 character set might be possible. Still text 
mode for now, though if anyone wants to write a GUI client (Henrik?) 
we can put it on the official RT reb site accessible from the View 
desktop. The server is accessed through a simple RPC protocol and 
is designed to be easily scriptable.


It turns out that Carl already rewrote the installer for 2.7.something, 
but it was turned off because of a couple minor bugs that we were 
able to fix in 2.7.7. With any luck, only minor fixes to the registry 
usage will be needed and we'll be good to go.


As for the rest, it's up to you. Graham seems to have a good tweak 
to the http protocol, and others may want to contribute their fixes.

Well, CureCode it when you get the chance, or if you are impatient 
RAMBO it and it will get migrated to CureCode later.

Adding to RAMBO

for 2.7.8, I have submitted this to rambo http://www.rebol.net/cgi-bin/rambo.r?id=-4776&

Before a RAMBO ticket is reviewed and accepted it has a negative 
ID. If it doesn't work now, it must have been reviewed. Don't know 
the current ID.

http://www.rebol.net/cgi-bin/rambo.r?id=4400&

Rambo bug for +13 already exists:
   http://www.rebol.net/cgi-bin/rambo.r?id=4302&
Now all it needs is fixing :)

This is an error I posted back in 2003 to the tracker .. http://www.rebol.net/cgi-bin/rambo.r?id=3174&

Exponent with a negative number gives error on R2, I've submitted 
as a bug report on rambo: -4784
>> -2 ** -4
** Math Error: Positive number required
Fixed in R3.

For R2 bugs we have RAMBO:
http://www.rebol.net/cgi-bin/rambo.r

I think that Carl, Gabriele or BrianH can give you R2-beta access. 
If you need to report R2 bug, you can use any (not R3 related) group 
here and submit it into Rambo.

Yes, Rambo is still the best option for R2 bugs.

Have the registry bugs been reported? If not, do so here or in RAMBO. 
(I am a bit new to the RAMBO admin process.)

Ok, it wasn't rambo

What is the plan for next release ?
Do we need to post bug/request on RAMBO ?

I think so. RAMBO is still the only offical bug report for R2

Btw.. it would be nice to port the bugs from old tired Rambo to the 
CureCode hospital, where it's pretty visible which bug is fixed and 
if the fix is tested as well.

Diffs from the old preliminary changes doc to the actual 2.7.8 release 
(that I know about):

- No installer changes yet (my bad, I didn't have time to do them)
- SINGLE? is LAST? instead
- RESOLVE is a (slow) mezzanine for now, not native

- Don't know about what the Command boot problem was or whether it 
was fixed
- No HTTP fixes yet
- No X fixes yet

- ASSERT and APPLY are still mezzanine, and ASSERT is still rather 
bad
- No FOREACH setword support yet
- SET-ENV native (with limits)
- Delay sound subtask creation (whatever that means)
- RUN function uses 'shell access in SECURE
- FIND and SELECT on objects
- FUNCT /extern option, SPEED? and DT

- Some fixes to bugs in RAMBO that I don't know since RAMBO is down

continued from REBOL3! group.


they where not listed in RAMBO... I was just lucky to be online with 
Carl and it got fixed in a beta version of 2.7.7 in one afternoon 
with cyphre giving a more robust fix the day after.


 He also had the fix to another annoying issue which makes first item 
 to follow a space in a text to affect the transparency.  the more 
 spaces the darker it gets.  his even affects other items in a text 
 ends with spaces ! 

though I wonder if that ended up in the 2.7.8 release ' :-/

Carl said this when I suggested moving the R2 bug tracking from RAMBO 
to a project in CureCode:

In addition, on RAMBO:

1. For presets, I can select the # per page.
2. Preset categories seem more obvious
3. Search is better
4. I like ability to see summary and description in lists

Well, it's all doable, I just need to find some time to add these 
features (not sure how Rambo's search feature is working).

oh it was mostly hack and slash rambo stye fixes... the most important 
is just adding a sub to any style and trying to make it go thru events... 
its easy ... it crashes until all events flow thru gobs which have 
user data set to none.

I looked at Ratio's import-email function on the blog and was wondering 
if R3 is supposed to have an import-email function? He claim's R2's 
import-email function is buggy and there is really an unfixed report 
in RAMBO.

Carl, there is also an issue with waiting more than 597 hours in 
R2. It can be read about in the Core group. Not yet reported to RAMBO. 
I wonder if you could at least comment on it?

.....Sounds like it needs a RAMBO and a CC report :)

If it's not in the RAMBO records when they get migrated to CureCode, 
I'll submit it.

RAMBO shows about ten fixes

RAMBO holds 15 tickets, when searching for "routine!". 9 are Reviewed, 
6 Built.

Perhaps also of importance is that many bugs are already well-documented 
and are actively being discussed in Curecode with R3 rather than 
the simple non-discussed reports for RAMBO with R2.

Oh, I just find it is already in RAMBO.

Just added a ticket in RAMBO, now need to find a workaround.

Can't find any ticket related to this issue in RAMBO.

I've added this to RAMBO.

Do  you know if it is RAMBO as I guess Carl doesn't take much interest 
in %core-tests.r ?

I use CALL without /show in Cheyenne to start worker processes. Anyway, 
CALL is quite unreliable in 2.7.8 on Windows as shown by this RAMBO 
ticket: http://www.rebol.net/cgi-bin/rambo.r?id=4416&

http://www.rebol.net/cgi-bin/rambo.r?id=4332&

Same issue with FIND on native! values: http://www.rebol.net/cgi-bin/rambo.r?id=4126&

Seems it's already been repported:

http://www.rebol.net/cgi-bin/rambo.r?id=4093&