For your info, my Etoys trunk image offered me an emergency evaluator a few seconds after merging the GetText-Richo.3 snapshot with the updater.
In more detail: 1. Monticello raised a PreDebug Window with a "warning" exception while doing a three way merge of GetText-Richo.3 2. I elected to 'Proceed' 3. The image froze for 20 or 30 seconds (I tried to bring up a world menu but no response. No response to command-period.) 4. Stack dump appeared offering an emergency evaluator (but I could not read it as morphs redrew on top of it.) The top of the stack was: ***System error handling failed*** Original error: MessageNotUnderstood: AnObsoleteTextDomainManager class>>domainOfMethod:
I attach a debug log from the original exception (1 above), but I don't know how to dump the stack from the final image (4).
Hope that helps, David
A few seconds ago, I wrote:
- Monticello raised a PreDebug Window with a "warning" exception
while doing a three way merge of GetText-Richo.3
...
I attach a debug log from the original exception (1 above),
Here is the log file I omitted from the earlier mail.
Sorry, David
Uhhh, that's really bad... I got the same problem when I update today another package but it seemed to be a problem with my image only. I even tested this commit and I thought it was clean. Anyway, I'll try to reproduce the error and see if I can fix it. Thanks for the report.
Richo
On Tue, May 25, 2010 at 2:04 AM, David Corking lists@dcorking.com wrote:
For your info, my Etoys trunk image offered me an emergency evaluator a few seconds after merging the GetText-Richo.3 snapshot with the updater.
In more detail:
- Monticello raised a PreDebug Window with a "warning" exception
while doing a three way merge of GetText-Richo.3 2. I elected to 'Proceed' 3. The image froze for 20 or 30 seconds (I tried to bring up a world menu but no response. No response to command-period.) 4. Stack dump appeared offering an emergency evaluator (but I could not read it as morphs redrew on top of it.) The top of the stack was: ***System error handling failed*** Original error: MessageNotUnderstood: AnObsoleteTextDomainManager class>>domainOfMethod:
I attach a debug log from the original exception (1 above), but I don't know how to dump the stack from the final image (4).
Hope that helps, David _______________________________________________ etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
On Tue, May 25, 2010 at 2:15 PM, Ricardo Moran richi.moran@gmail.com wrote:
Uhhh, that's really bad... I got the same problem when I update today another package but it seemed to be a problem with my image only. I even tested this commit and I thought it was clean. Anyway, I'll try to reproduce the error and see if I can fix it. Thanks for the report.
Hi, Richo, I hit same problem too.
And it seems your changes to GetTextExporter2 in GetText-Richo.3 is wrong; By browsing the version, content of GetTextExporter shown in MC is old GetTextExporter, not GetTextExporter2. Entire exporter stuff would be lost with the change :-<
BTW I believe that this time the version should be committed to etoysinbox, not etoys.
/Korakurider
Richo
On Tue, May 25, 2010 at 2:04 AM, David Corking lists@dcorking.com wrote:
For your info, my Etoys trunk image offered me an emergency evaluator a few seconds after merging the GetText-Richo.3 snapshot with the updater.
In more detail:
- Monticello raised a PreDebug Window with a "warning" exception
while doing a three way merge of GetText-Richo.3 2. I elected to 'Proceed' 3. The image froze for 20 or 30 seconds (I tried to bring up a world menu but no response. No response to command-period.) 4. Stack dump appeared offering an emergency evaluator (but I could not read it as morphs redrew on top of it.) The top of the stack was: ***System error handling failed*** Original error: MessageNotUnderstood: AnObsoleteTextDomainManager class>>domainOfMethod:
I attach a debug log from the original exception (1 above), but I don't know how to dump the stack from the final image (4).
Hope that helps, David _______________________________________________ etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
Yes, I tried updating a clean image and I got the same error. We should remove this version from the repository ASAP. I screwed up badly, but I don't understand why. My image is still working. And I see from the commit message that this commit removed TextDomainManager but I have no idea why. I never meant to remove it: I know the image will crash without it. Also, I always click "changes" before uploading something and I don't remember seeing these weird changes, otherwise I would commited to the inbox. Anyway, I'm sorry...
How can you tell Monticello which order you want the code to be loaded? Because I removed GetTextExporter, renamed GetTextExporter2 to GetTextExporter and then I made changes to GetTextExporter. I thought Monticello would know the order of these operations is important.
Richo
P.S.: My first day as member of etoys-dev and I already screwed up the image... Way to go, Richo!
On Tue, May 25, 2010 at 2:35 AM, Korakurider korakurider@gmail.com wrote:
On Tue, May 25, 2010 at 2:15 PM, Ricardo Moran richi.moran@gmail.com wrote:
Uhhh, that's really bad... I got the same problem when I update today another package but it seemed to be a problem with my image only. I even tested this commit and I thought it was clean. Anyway, I'll try to
reproduce
the error and see if I can fix it. Thanks for the report.
Hi, Richo, I hit same problem too.
And it seems your changes to GetTextExporter2 in GetText-Richo.3 is wrong; By browsing the version, content of GetTextExporter shown in MC is old GetTextExporter, not GetTextExporter2. Entire exporter stuff would be lost with the change :-<
BTW I believe that this time the version should be committed to etoysinbox, not etoys.
/Korakurider
Richo
On Tue, May 25, 2010 at 2:04 AM, David Corking lists@dcorking.com
wrote:
For your info, my Etoys trunk image offered me an emergency evaluator a few seconds after merging the GetText-Richo.3 snapshot with the updater.
In more detail:
- Monticello raised a PreDebug Window with a "warning" exception
while doing a three way merge of GetText-Richo.3 2. I elected to 'Proceed' 3. The image froze for 20 or 30 seconds (I tried to bring up a world menu but no response. No response to command-period.) 4. Stack dump appeared offering an emergency evaluator (but I could not read it as morphs redrew on top of it.) The top of the stack was: ***System error handling failed*** Original error: MessageNotUnderstood: AnObsoleteTextDomainManager class>>domainOfMethod:
I attach a debug log from the original exception (1 above), but I don't know how to dump the stack from the final image (4).
Hope that helps, David _______________________________________________ etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
On Tue, May 25, 2010 at 2:49 PM, Ricardo Moran richi.moran@gmail.com wrote:
Yes, I tried updating a clean image and I got the same error. We should remove this version from the repository ASAP. I screwed up badly, but I don't understand why. My image is still working. And I see from the commit message that this commit removed TextDomainManager but I have no idea why. I never meant to remove it: I know the image will crash without it. Also, I always click "changes" before uploading something and I don't remember seeing these weird changes, otherwise I would commited to the inbox. Anyway, I'm sorry... How can you tell Monticello which order you want the code to be loaded? Because I removed GetTextExporter, renamed GetTextExporter2 to GetTextExporter and then I made changes to GetTextExporter. I thought Monticello would know the order of these operations is important.
My bad, please forget my false report. I am sorry.
/Korakurider
p.s having alpha release image would make sense if updating is such troublesome !
Richo P.S.: My first day as member of etoys-dev and I already screwed up the image... Way to go, Richo! On Tue, May 25, 2010 at 2:35 AM, Korakurider korakurider@gmail.com wrote:
On Tue, May 25, 2010 at 2:15 PM, Ricardo Moran richi.moran@gmail.com wrote:
Uhhh, that's really bad... I got the same problem when I update today another package but it seemed to be a problem with my image only. I even tested this commit and I thought it was clean. Anyway, I'll try to reproduce the error and see if I can fix it. Thanks for the report.
Hi, Richo, I hit same problem too.
And it seems your changes to GetTextExporter2 in GetText-Richo.3 is wrong; By browsing the version, content of GetTextExporter shown in MC is old GetTextExporter, not GetTextExporter2. Entire exporter stuff would be lost with the change :-<
BTW I believe that this time the version should be committed to etoysinbox, not etoys.
/Korakurider
Richo
On Tue, May 25, 2010 at 2:04 AM, David Corking lists@dcorking.com wrote:
For your info, my Etoys trunk image offered me an emergency evaluator a few seconds after merging the GetText-Richo.3 snapshot with the updater.
In more detail:
- Monticello raised a PreDebug Window with a "warning" exception
while doing a three way merge of GetText-Richo.3 2. I elected to 'Proceed' 3. The image froze for 20 or 30 seconds (I tried to bring up a world menu but no response. No response to command-period.) 4. Stack dump appeared offering an emergency evaluator (but I could not read it as morphs redrew on top of it.) The top of the stack was: ***System error handling failed*** Original error: MessageNotUnderstood: AnObsoleteTextDomainManager class>>domainOfMethod:
I attach a debug log from the original exception (1 above), but I don't know how to dump the stack from the final image (4).
Hope that helps, David _______________________________________________ etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
On Tue, May 25, 2010 at 2:35 PM, Korakurider korakurider@gmail.com wrote:
On Tue, May 25, 2010 at 2:15 PM, Ricardo Moran richi.moran@gmail.com wrote:
Uhhh, that's really bad... I got the same problem when I update today another package but it seemed to be a problem with my image only. I even tested this commit and I thought it was clean. Anyway, I'll try to reproduce the error and see if I can fix it. Thanks for the report.
MC Browser shows that GetText-Richo.3 will remove TextDomainManager and MOFIle. That should be the problem, as I saw DNU of #domainOfMethod in emergency evaluator. hope this helps.
/Korakurider
On 25.05.2010, at 08:18, Korakurider wrote:
On Tue, May 25, 2010 at 2:35 PM, Korakurider korakurider@gmail.com wrote:
On Tue, May 25, 2010 at 2:15 PM, Ricardo Moran richi.moran@gmail.com wrote:
Uhhh, that's really bad... I got the same problem when I update today another package but it seemed to be a problem with my image only. I even tested this commit and I thought it was clean. Anyway, I'll try to reproduce the error and see if I can fix it. Thanks for the report.
MC Browser shows that GetText-Richo.3 will remove TextDomainManager and MOFIle. That should be the problem, as I saw DNU of #domainOfMethod in emergency evaluator. hope this helps.
Amazing what can happen while one is asleep ;)
I moved the offending version to the "Etoys Treated" repository. So it should be safe to update again.
Lesson: do not publish stuff from an unclean image. Always verify what you submit is what you intend to using the "Changes" button.
Actually, it's good you are making these mistakes in public. Don't let that discourage you. We're here to learn, after all :)
- Bert -
Mistakes don't discourage me... but I'll be much more careful from now on :) Sorry for all the trouble.
Cheers Richo
On Tue, May 25, 2010 at 7:51 AM, Bert Freudenberg bert@freudenbergs.dewrote:
On 25.05.2010, at 08:18, Korakurider wrote:
On Tue, May 25, 2010 at 2:35 PM, Korakurider korakurider@gmail.com
wrote:
On Tue, May 25, 2010 at 2:15 PM, Ricardo Moran richi.moran@gmail.com
wrote:
Uhhh, that's really bad... I got the same problem when I update today another package but it seemed to be a problem with my image only. I
even
tested this commit and I thought it was clean. Anyway, I'll try to
reproduce
the error and see if I can fix it. Thanks for the report.
MC Browser shows that GetText-Richo.3 will remove TextDomainManager and
MOFIle.
That should be the problem, as I saw DNU of #domainOfMethod in emergency evaluator. hope this helps.
Amazing what can happen while one is asleep ;)
I moved the offending version to the "Etoys Treated" repository. So it should be safe to update again.
Lesson: do not publish stuff from an unclean image. Always verify what you submit is what you intend to using the "Changes" button.
Actually, it's good you are making these mistakes in public. Don't let that discourage you. We're here to learn, after all :)
- Bert -
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
etoys-dev@lists.squeakfoundation.org
-
Bert Freudenberg -
David Corking -
Korakurider -
Ricardo Moran