Issue 348 in glassdb: SequenceableCollection>>copyFrom:to:into:startingAt: no longer throws errors in 3.1

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue 348 in glassdb: SequenceableCollection>>copyFrom:to:into:startingAt: no longer throws errors in 3.1

glassdb
Status: Accepted
Owner: [hidden email]
Labels: Type-Defect Priority-Medium GLASS-Server Version-3.1.0  
Milestone-1.0-beta.8.7.3

New issue 348 by [hidden email]:  
SequenceableCollection>>copyFrom:to:into:startingAt: no longer throws  
errors in 3.1
http://code.google.com/p/glassdb/issues/detail?id=348

See discussion, analysis and proposed fix in:

   
http://forum.world.st/Gemstone-3-1-0-503-Service-Not-Available-td4641272.html#a4641335

Reply | Threaded
Open this post in threaded view
|

Re: Issue 348 in glassdb: SequenceableCollection>>copyFrom:to:into:startingAt: no longer throws errors in 3.1

glassdb
Updates:
        Labels: bugid-42397

Comment #1 on issue 348 by [hidden email]:  
SequenceableCollection>>copyFrom:to:into:startingAt: no longer throws  
errors in 3.1
http://code.google.com/p/glassdb/issues/detail?id=348

(No comment was entered for this change.)

Reply | Threaded
Open this post in threaded view
|

Re: Issue 348 in glassdb: SequenceableCollection>>copyFrom:to:into:startingAt: no longer throws errors in 3.1

glassdb
Updates:
        Status: Fixed

Comment #2 on issue 348 by [hidden email]:  
SequenceableCollection>>copyFrom:to:into:startingAt: no longer throws  
errors in 3.1
http://code.google.com/p/glassdb/issues/detail?id=348

this bug is fixed in GemStone/S 3.1.0.1.

Added test in GsMisc 0.241.1 (dkh.103)

Reply | Threaded
Open this post in threaded view
|

Re: Issue 348 in glassdb: SequenceableCollection>>copyFrom:to:into:startingAt: no longer throws errors in 3.1

glassdb

Comment #3 on issue 348 by [hidden email]:  
SequenceableCollection>>copyFrom:to:into:startingAt: no longer throws  
errors in 3.1
http://code.google.com/p/glassdb/issues/detail?id=348

woops fixed in GsCore 0.261 (dkh.262)