Serializing an error (Fuel)

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

Serializing an error (Fuel)

Bernat Romagosa
Hi list,

Until recently, we've been dealing with all errors in our Iliad application by having the Iliad error handler serialize them and send us an email referring to the file.

This way, debugging was as easy as:

GRPlatform current openDebuggerOn: (FLMaterializer materializeFromFileNamed: 'errorReports/1366980822.obj').

But recently this has stopped working, and I've just found out I can't even serialize simple errors. Something like:

[ 3 / 0 ] on: Error do: [ :error | FLSerializer serialize: error toFileNamed: 'error.obj' ]

brings out a debugger saying I need FuelMetalevel to fully serialize methods (which is installed, by the way). The error reads:

FLNotInstalledMethod: Serialization error. DoIt can not be serialized as global because it is not installed. You need FuelMetalevel to fully serialize methods. See the documentation.

I'm not sure whether one thing is related to the other... any ideas?

--
Bernat Romagosa.
Reply | Threaded
Open this post in threaded view
|

Re: Serializing an error (Fuel)

Bernat Romagosa
Ouch! Disregard that. I've just tried to serialize an error from the Iliad error handler and it worked... not sure what was going on!

Sorry!


2013/4/29 Bernat Romagosa <[hidden email]>
Hi list,

Until recently, we've been dealing with all errors in our Iliad application by having the Iliad error handler serialize them and send us an email referring to the file.

This way, debugging was as easy as:

GRPlatform current openDebuggerOn: (FLMaterializer materializeFromFileNamed: 'errorReports/1366980822.obj').

But recently this has stopped working, and I've just found out I can't even serialize simple errors. Something like:

[ 3 / 0 ] on: Error do: [ :error | FLSerializer serialize: error toFileNamed: 'error.obj' ]

brings out a debugger saying I need FuelMetalevel to fully serialize methods (which is installed, by the way). The error reads:

FLNotInstalledMethod: Serialization error. DoIt can not be serialized as global because it is not installed. You need FuelMetalevel to fully serialize methods. See the documentation.

I'm not sure whether one thing is related to the other... any ideas?

--
Bernat Romagosa.



--
Bernat Romagosa.
Reply | Threaded
Open this post in threaded view
|

Re: Serializing an error (Fuel)

Mariano Martinez Peck
In reply to this post by Bernat Romagosa



On Mon, Apr 29, 2013 at 6:30 AM, Bernat Romagosa <[hidden email]> wrote:
Hi list,

Until recently, we've been dealing with all errors in our Iliad application by having the Iliad error handler serialize them and send us an email referring to the file.

This way, debugging was as easy as:

GRPlatform current openDebuggerOn: (FLMaterializer materializeFromFileNamed: 'errorReports/1366980822.obj').

But recently this has stopped working, and I've just found out I can't even serialize simple errors. Something like:

[ 3 / 0 ] on: Error do: [ :error | FLSerializer serialize: error toFileNamed: 'error.obj' ]

brings out a debugger saying I need FuelMetalevel to fully serialize methods (which is installed, by the way). The error reads:

FLNotInstalledMethod: Serialization error. DoIt can not be serialized as global because it is not installed. You need FuelMetalevel to fully serialize methods. See the documentation.


This is old. Fuel 1.9 (last stable version and the one integrated in Pharo 2.0) should be able to fully serialize methods. Moreover, it automatically serialize uninstalled methods and do-its. 

cheers,    
 

I'm not sure whether one thing is related to the other... any ideas?

--
Bernat Romagosa.



--
Mariano
http://marianopeck.wordpress.com
Reply | Threaded
Open this post in threaded view
|

Re: Serializing an error (Fuel)

Bernat Romagosa
Hi Mariano,

We're stuck on Pharo 1.4 until Iliad and some other packages are available for 2.0... however, I'll try to update it to the latest possible version and see if it still happens.

Thanks!


2013/4/29 Mariano Martinez Peck <[hidden email]>



On Mon, Apr 29, 2013 at 6:30 AM, Bernat Romagosa <[hidden email]> wrote:
Hi list,

Until recently, we've been dealing with all errors in our Iliad application by having the Iliad error handler serialize them and send us an email referring to the file.

This way, debugging was as easy as:

GRPlatform current openDebuggerOn: (FLMaterializer materializeFromFileNamed: 'errorReports/1366980822.obj').

But recently this has stopped working, and I've just found out I can't even serialize simple errors. Something like:

[ 3 / 0 ] on: Error do: [ :error | FLSerializer serialize: error toFileNamed: 'error.obj' ]

brings out a debugger saying I need FuelMetalevel to fully serialize methods (which is installed, by the way). The error reads:

FLNotInstalledMethod: Serialization error. DoIt can not be serialized as global because it is not installed. You need FuelMetalevel to fully serialize methods. See the documentation.


This is old. Fuel 1.9 (last stable version and the one integrated in Pharo 2.0) should be able to fully serialize methods. Moreover, it automatically serialize uninstalled methods and do-its. 

cheers,    
 

I'm not sure whether one thing is related to the other... any ideas?

--
Bernat Romagosa.



--
Mariano
http://marianopeck.wordpress.com



--
Bernat Romagosa.
Reply | Threaded
Open this post in threaded view
|

Re: Serializing an error (Fuel)

Mariano Martinez Peck



On Mon, Apr 29, 2013 at 10:32 AM, Bernat Romagosa <[hidden email]> wrote:
Hi Mariano,

We're stuck on Pharo 1.4 until Iliad and some other packages are available for 2.0... however, I'll try to update it to the latest possible version and see if it still happens.


Fuel 1.9 does work in Pharo 1.4 as well. Anyway, if you are in Fuel 1.8 or before, then yes, you should install FuelMetalevel in order to fully serialized do-it or not installed methods. 

Hope it works!
 
Thanks!


2013/4/29 Mariano Martinez Peck <[hidden email]>



On Mon, Apr 29, 2013 at 6:30 AM, Bernat Romagosa <[hidden email]> wrote:
Hi list,

Until recently, we've been dealing with all errors in our Iliad application by having the Iliad error handler serialize them and send us an email referring to the file.

This way, debugging was as easy as:

GRPlatform current openDebuggerOn: (FLMaterializer materializeFromFileNamed: 'errorReports/1366980822.obj').

But recently this has stopped working, and I've just found out I can't even serialize simple errors. Something like:

[ 3 / 0 ] on: Error do: [ :error | FLSerializer serialize: error toFileNamed: 'error.obj' ]

brings out a debugger saying I need FuelMetalevel to fully serialize methods (which is installed, by the way). The error reads:

FLNotInstalledMethod: Serialization error. DoIt can not be serialized as global because it is not installed. You need FuelMetalevel to fully serialize methods. See the documentation.


This is old. Fuel 1.9 (last stable version and the one integrated in Pharo 2.0) should be able to fully serialize methods. Moreover, it automatically serialize uninstalled methods and do-its. 

cheers,    
 

I'm not sure whether one thing is related to the other... any ideas?

--
Bernat Romagosa.



--
Mariano
http://marianopeck.wordpress.com



--
Bernat Romagosa.



--
Mariano
http://marianopeck.wordpress.com