Hi, I have tested using the latest release and can only get the browser plugin to launch in Google Chrome. The others (IE8, Firefox and Safari) fail with
PluginHTTPDownloadRequest(Object)>>error:
I'm not sure how to debug this. I can connect from the image while in the browser to the showcase but launching always fails.
Karl
At Mon, 26 Oct 2009 18:35:31 +0100, Karl Ramberg wrote:
Hi, I have tested using the latest release and can only get the browser plugin to launch in Google Chrome. The others (IE8, Firefox and Safari) fail with
PluginHTTPDownloadRequest(Object)>>error:
I'm not sure how to debug this. I can connect from the image while in the browser to the showcase but launching always fails.
I saw this for some time and for some examples, but not persistently. I gather that very often the cause is some server issues. When the server is stable, with FireFox and IE, I had no trouble to launch projects (like right now, except that I cannot find TurtleGeometry project).
-- Yoshiki
On Mon, Oct 26, 2009 at 6:52 PM, Yoshiki Ohshima yoshiki@vpri.org wrote:
At Mon, 26 Oct 2009 18:35:31 +0100, Karl Ramberg wrote:
Hi, I have tested using the latest release and can only get the browser plugin to launch in Google Chrome. The others (IE8, Firefox and Safari) fail with
PluginHTTPDownloadRequest(Object)>>error:
I'm not sure how to debug this. I can connect from the image while in the browser to the showcase but launching always fails.
I saw this for some time and for some examples, but not persistently. I gather that very often the cause is some server issues. When the server is stable, with FireFox and IE, I had no trouble to launch projects (like right now, except that I cannot find TurtleGeometry project).
For me this is happens every time I launch the plugin.
I can not find out why though. Do you have a suggestion to track it down ?
The image can connect if I click the showcase folder.
The error must be in StandardFileStream>>requestURLStream: url ifError: errorBlock "Request a FileStream for the given URL. If Squeak is not running in a browser evaluate errorBlock" "FileStream requestURLStream:'http://www.squeak.org'" | sema index request result | self waitBrowserReadyFor: self defaultBrowserReadyWait ifFail: [^errorBlock value]. sema _ Semaphore new. index _ Smalltalk registerExternalObject: sema. request _ self primURLRequest: url semaIndex: index. request == nil ifTrue:[
Smalltalk unregisterExternalObject: sema. ^errorBlock value. ] ifFalse:[ [sema wait. "until something happens" result _ self primURLRequestState: request. result == nil] whileTrue. result ifTrue:[fileID _ self primURLRequestFileHandle: request]. self primURLRequestDestroy: request. ]. Smalltalk unregisterExternalObject: sema. fileID == nil ifTrue:[^nil]. self register. name _ url. rwmode _ false. buffer1 _ String new: 1.
Can you think of a way to test this without the semaphore or with some logging to see what is going on ?
Karl
At Mon, 26 Oct 2009 21:21:37 +0100, karl ramberg wrote:
For me this is happens every time I launch the plugin. I can not find out why though. Do you have a suggestion to track it down ?
Does it happen with all projects?
Can you think of a way to test this without the semaphore or with some logging to see what is going on ?
Hmm. Without sema would not be easily doable, as the primtives expects to have them. Logging to transcript should be possible, I'd imagine. Edit requestURLStream:ifError: and manually invoking the method may give you some info...
-- Yoshiki
On 2009-10-26 22:52, Yoshiki Ohshima wrote:
At Mon, 26 Oct 2009 21:21:37 +0100, karl ramberg wrote:
For me this is happens every time I launch the plugin. I can not find out why though. Do you have a suggestion to track it down ?
Does it happen with all projects?
Can you think of a way to test this without the semaphore or with some logging to see what is going on ?
Hmm. Without sema would not be easily doable, as the primtives expects to have them. Logging to transcript should be possible, I'd imagine. Edit requestURLStream:ifError: and manually invoking the method may give you some info...
-- Yoshiki
This is what I get:
It seems the plugin fails in primURLRequestFileHandle: The thing is that it works reliable on Google Chrome.
I wonder if this is just me seeing this issue ?
Karl
I'm having the same problem. I haven't noticed this before because I use Chrome for almost everything now..
On Tue, Oct 27, 2009 at 8:43 AM, Karl Ramberg karlramberg@gmail.com wrote:
On 2009-10-26 22:52, Yoshiki Ohshima wrote:
At Mon, 26 Oct 2009 21:21:37 +0100, karl ramberg wrote:
For me this is happens every time I launch the plugin. I can not find out why though. Do you have a suggestion to track it down ?
Does it happen with all projects?
Can you think of a way to test this without the semaphore or with some logging to see what is going on ?
Hmm. Without sema would not be easily doable, as the primtives expects to have them. Logging to transcript should be possible, I'd imagine. Edit requestURLStream:ifError: and manually invoking the method may give you some info...
-- Yoshiki
This is what I get:
It seems the plugin fails in primURLRequestFileHandle: The thing is that it works reliable on Google Chrome.
I wonder if this is just me seeing this issue ?
Karl
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
On Tue, Oct 27, 2009 at 1:28 PM, Ricardo Moran richi.moran@gmail.comwrote:
I'm having the same problem. I haven't noticed this before because I use Chrome for almost everything now..
On Tue, Oct 27, 2009 at 8:43 AM, Karl Ramberg karlramberg@gmail.comwrote:
On 2009-10-26 22:52, Yoshiki Ohshima wrote:
At Mon, 26 Oct 2009 21:21:37 +0100, karl ramberg wrote:
For me this is happens every time I launch the plugin. I can not find out why though. Do you have a suggestion to track it down ?
Does it happen with all projects?
Can you think of a way to test this without the semaphore or with some logging to see what is going on ?
Hmm. Without sema would not be easily doable, as the primtives expects to have them. Logging to transcript should be possible, I'd imagine. Edit requestURLStream:ifError: and manually invoking the method may give you some info...
-- Yoshiki
This is what I get:
It seems the plugin fails in primURLRequestFileHandle: The thing is that it works reliable on Google Chrome.
I wonder if this is just me seeing this issue ?
Karl
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
Ok, seems to be a little more serious than I thought...
Andreas, could you look at this issue ?
http://lists.squeakland.org/pipermail/etoys-dev/2009-October/004075.html
Karl
etoys-dev@lists.squeakfoundation.org