New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR 2003 , a OffsetError occurred (error 2003), reason:objErrBadOffsetIncomplete, max:0 actual:1 (OffsetError)during upgradeGLASS1 #6
Comments
I'm getting this issue as well when I hit a load conflict on Grease, remove the Grease project registration and then relaunch the upgrade procedure. Here is the transcript: (Smalltalk at: #GsUpgrader) upgradeGLASS1. Metacello-Base' Metacello-Core' Squeak' Grease-Core' |
@jbrichau this is the problem that I've been killing myself trying to reproduce ... I can't force a conflict to save my life... Would you please run a metacelloReport before doing the upgradeGLASS1 ... I assume that the error has something to do with the starting conditions, but I have so far been unable to figure out what the starting condition needs to be ... I suspect that the root cause is a Metacello bug, so I need to have a reproducable test case in my hands ... thanks |
I'm home in an hour and was planning to get you this. Coming up! Johan (sent from my mobile)
|
I'm waiting with bated breath:) On Wed, Sep 24, 2014 at 10:13 AM, Johan Brichau notifications@github.com
|
Before launching the upgrade:Metacello Version REPORT
19. ConfigurationOfXMLWriter 2.3.7 #'release'PACKAGE REPORTAnnouncements.v3-dkh.18 |
Hi guys, I am having a similar issue. I am having the offset error, but I think the cause is different. I am updating a extent that already had seaside 3.0.9 and some old grease version. I am SURE Grease is indeed loaded. #greaseBaselineLoaded does answer true, however, when executing:
That gives an empty list. So... the project is found in Metacello registration because BaselineOfGrease exists, but In the meanwhile...do you know a workaround so that I can load Seaside 3.1? My transcript output is:
And the metacello report is:
|
Of course....all the instructions in the web refer to ss3 repo. But it seems the commit provided by Dale was here in git... but not in ss3. So I am loading an older version. |
OK, using latest version from git worked. Dale, do you want to put last version in ss3 repo as well? thanks! |
Mariano, When you say latest, I assume that you are referring to the github version I'm glad that it worked for you and I suppose that I should close Issue I guess I got sidetracked by the Metacello issue that was raised by that Dale [1] #3 On Sun, Oct 12, 2014 at 8:18 AM, marianopeck notifications@github.com
|
Hi Dale, When I said latest I mean, I saw this commit from you: 6348f88 |
Great! ...Haha, that means the bugfix works:) On Sun, Oct 12, 2014 at 12:10 PM, marianopeck notifications@github.com
|
Here's a stack from Jon:
Have not been able to reproduce this in the lab, but I can certainly handle the case when the registration is empty ... need to be suspicious of empty registrations in all cases...
The text was updated successfully, but these errors were encountered: