<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font face="Georgia">Tim,<br>
<br>
I does not appear to be an image problem. Frank suggested this:<br>
</font><br>
<div class="moz-cite-prefix">On 4/26/13 6:17 AM, Frank Shearar wrote</div>
<blockquote
cite="mid:CAJbhyRH=8478fWaMe5UOFhDatoO6g5dKjPzYo0YXA0C=qg62Xg@mail.gmail.com"
type="cite">
<pre wrap="">For those not following the Pharo list, it looks like the root cause
is that the glibc in Ubuntu 13.04 doesn't immediately write new
content out to the file. Thus you can "write" to the file, and then
read from the file, only your RemoteString starts off the end of the
file. The fix is to make WriteStream >> #nextPutChunk: call "self
flush". I've pushed a 4.5 fix to trunk, but have not yet done the same
for the 4.4 and 4.3 update streams.
frank
</pre>
</blockquote>
Some thought this not the nicest solution, but it would be useful to
know if the image you are using has had this added or if you can add
it and try.<br>
<br>
Frank did add this later after retracting the squeak change<br>
<meta charset="utf-8">
<pre class="bz_comment_text" style="font-size: small; font-family: monospace; white-space: pre-wrap; width: 50em; word-wrap: break-word; color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">That's correct: patching #nextChunkPut: almost certainly masks the underlying problem, and the more experience Squeakers strongly suggested I revert. I'll post updates as they happen.</pre>
If I were experiencing this problem I suspect I'd make the fix and
move on rather than re-experience the problem over and over. <br>
<br>
Also see if your Linux distro has fixed it on their end.<br>
<br>
Cheers,<br>
Bob<br>
<br>
<div class="moz-cite-prefix">On 9/12/13 6:17 PM, gettimothy wrote:<br>
</div>
<blockquote
cite="mid:141143fe273.577362555135458375.-2431359141449504526@zoho.com"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div
style="font-size:10pt;font-family:Verdana,Arial,Helvetica,sans-serif;">When
I first ran into the issue, I saw some talk on it.<br>
<br>
A search for "Squeak4.5 remoteString past end of file error"
will bring up references.<br>
<br>
The error thrown is in:<br>
<br>
<blockquote style="border: 1px solid rgb(204, 204, 204);
padding: 7px; background-color: rgb(245, 245, 245);">
<div>RemoteString>> <br>
text <br>
"Answer the receiver's string asText if remote files are
enabled."<br>
<br>
| theFile |<br>
theFile := (CurrentReadOnlySourceFiles at:
(sourceFileNumber ifNil: [ ^nil ])) ifNil: [ ^nil ].<br>
theFile size < filePositionHi ifTrue: [<br>
<b>self error: 'RemoteString past end of file' </b>].<br>
^theFile<br>
position: filePositionHi;<br>
nextChunkText<br>
</div>
</blockquote>
<br>
The immediate callstack below looks like this:<br>
<br>
<br>
<blockquote style="border: 1px solid rgb(204, 204, 204);
padding: 7px; background-color: rgb(245, 245, 245);">
<div><br>
RemoteString>>text<br>
ClassOrganizer(BasicClassOrganizer)>>classComment<br>
ReleaseBuilder class (ClassDescription)>>comment<br>
Browser>>contents<br>
PluggableTextMorph......</div>
</blockquote>
<br>
This is from Squeak4.5-12568.zip that I downloaded this
afternoon from <a class="moz-txt-link-freetext" href="ftp://ftp.squeak.org/trunk/">ftp://ftp.squeak.org/trunk/</a><br>
(Note: same with the Squeak4.5-12641.zip that is there--I just
tested it while typing this email)<br>
<br>
<br>
I am running on Slackware Linux 64 with 32 bit compatability
libs installed. The same image works fine when I boot do my dos
partition and run it there.<br>
<br>
t.<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<div id="1"><br>
---- On Thu, 12 Sep 2013 14:56:52 -0700 <b>Bob
Arning<a class="moz-txt-link-rfc2396E" href="mailto:arning315@comcast.net"><arning315@comcast.net></a></b> wrote ---- <br>
</div>
<br>
<blockquote style="border-left: 1px solid #0000FF; padding-left:
6px; margin:0 0 0 5px">
<div bgcolor="#FFFFFF" text="#000000"> <font face="Georgia">Tim,<br>
<br>
</font>
<div>On 9/12/13 5:50 PM, gettimothy wrote:<br>
</div>
<blockquote cite="mid:1411427588e.-4989468610<a href="
mailto:153339913.-9097188325255487314@zoho.com"=""
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:153339913.-9097188325255487314@zoho.com">153339913.-9097188325255487314@zoho.com</a>"
type="cite">
<div
style="font-size:10pt;font-family:verdana,arial,helvetica,sans-serif;">I
want to get to where I can write a plug-in for the VM,
have the VM see it and use it, then build a release with
it. (locally, of course)<br>
</div>
</blockquote>
<br>
This doesn't depend on mastering the release process.
"Release" here just means prettying up the image in certain
ways to make it palatable to new users. The image you are
using right now is fine for developing a plugin and for a
local release.<br>
<blockquote cite="mid:1411427588e.-4989468610<a href="
mailto:153339913.-9097188325255487314@zoho.com"=""
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:153339913.-9097188325255487314@zoho.com">153339913.-9097188325255487314@zoho.com</a>"
type="cite">
<div
style="font-size:10pt;font-family:verdana,arial,helvetica,sans-serif;"><br>
One motivation is urrent issues with I recently posted
on regarding <br>
VNC client on squeak primitiive error <br>
SSL tanking on WebClient <br>
The bug on Squeak4.4 and 4.5 where modifying a
comment and attempting to save it throws a system level
exception.Bob<br>
</div>
</blockquote>
You've mentioned this one before, but I never saw any
details. Are others aware of this issue?<br>
<br>
Cheers,<br>
<br>
<blockquote cite="mid:1411427588e.-4989468610<a href="
mailto:153339913.-9097188325255487314@zoho.com"=""
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:153339913.-9097188325255487314@zoho.com">153339913.-9097188325255487314@zoho.com</a>"
type="cite">
<div
style="font-size:10pt;font-family:verdana,arial,helvetica,sans-serif;">These
are all things I want to use for projects I am working
on and I don't know how to fix them.<br>
<br>
t<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<div><br>
---- On Thu, 12 Sep 2013 13:21:53 -0700 <b>Frank
Shearar <a moz-do-not-send="true" subj=""
mailid="frank.shearar%40gmail.com"
href="mailto:frank.shearar@gmail.com"
target="_blank"><frank.shearar@gmail.com></a></b>
wrote ---- <br>
</div>
<br>
<blockquote style="border-left: 1px solid #0000ff;
padding-left: 6px; margin:0 0 0 5px">That's from quite
a while ago! Yes, it worked out, and I ended up <br>
volunteering/being volunteered to get 4.4 released.
You can find the <br>
notes for the current release cycle at <br>
<a moz-do-not-send="true"
href="http://wiki.squeak.org/squeak/6189"
target="_blank">http://wiki.squeak.org/squeak/6189</a>.
<br>
<br>
I'm certainly not _opposed_ to documenting the release
process in the <br>
HelpBrowser. Some parts of the release process are of
necessity <br>
outside the image, but that's OK. <br>
<br>
I'm a bit confused by the way you talk about the
release process <br>
though. It's not something people need to run,
usually. <br>
<br>
frank <br>
<br>
On 12 September 2013 19:15, gettimothy <<a
moz-do-not-send="true" subj=""
mailid="gettimothy%40zoho.com"
href="mailto:gettimothy@zoho.com" target="_blank">gettimothy@zoho.com</a>>
wrote: <br>
> Awesome. <br>
> <br>
> Thank you. <br>
> <br>
> I did a google on the Squeak Release process and
found a thread (by you) <br>
> here: <a moz-do-not-send="true"
href="http://forum.world.st/Squeak-release-process-td4640158.html"
target="_blank">http://forum.world.st/Squeak-release-process-td4640158.html</a>
<br>
> <br>
> Did that ever come to fruition? Would a
HelpBrowser entry be helpful? (I <br>
> will write it if so, and the information is
available) <br>
> <br>
> The goal, is that newbs like me can get the
release environment running <br>
> locally and mash around a bit without bothering
the experts too much. <br>
> <br>
> thx. <br>
> <br>
> <br>
> <br>
> <br>
> ---- On Thu, 12 Sep 2013 10:31:41 -0700 Frank <br>
> Shearar<<a moz-do-not-send="true" subj=""
mailid="frank.shearar%40gmail.com"
href="mailto:frank.shearar@gmail.com"
target="_blank">frank.shearar@gmail.com</a>>
wrote ---- <br>
> <br>
> Right. That version's somewhere around 300
commits behind Trunk. After <br>
> you update the image (open the Squeak menu in the
docking bar at the <br>
> top, on the far left), you will find only
ReleaseBuilder. <br>
> <br>
> You always have local storage available, in the
form of an <br>
> MCCacheRepository pointing to the
/your/image/path/package-cache/ <br>
> directory. <br>
> <br>
> We really ought to push out a more up-to-date
image, which requires me <br>
> to finish finding out why the continuous
integration update-image.st <br>
> script is broken. <br>
> <br>
> frank <br>
> <br>
> On 12 September 2013 17:22, gettimothy <<a
moz-do-not-send="true" subj=""
mailid="gettimothy%40zoho.com"
href="mailto:gettimothy@zoho.com" target="_blank">gettimothy@zoho.com</a>>
wrote: <br>
>> Good news on the trunk! <br>
>> <br>
>> I am confused by what you mean by 'There is
no ReleaseBuilderForXdotY'. <br>
>> <br>
>> I went here: <a moz-do-not-send="true"
href="http://ftp.squeak.org/trunk/" target="_blank">http://ftp.squeak.org/trunk/</a>
<br>
>> <br>
>> Downloaded the .image and .change, then
copied over an existing cogvm, <br>
>> sources and stuff, fired up and browsing <br>
>> ReleaseBuilder --> show hierarchy yields:
<br>
>> <br>
>> ProtoObject #() <br>
>> Object #() <br>
>> Behavior #('superclass' 'methodDict'
'format') <br>
>> ClassDescription #('instanceVariables'
'organization') <br>
>> Class #('subclasses' 'name' 'classPool'
'sharedPools' <br>
>> 'environment' 'category') <br>
>> ProtoObject class #() <br>
>> Object class #() <br>
>> <br>
>> ReleaseBuilder class #() <br>
>> ReleaseBuilderDeveloper class #() <br>
>> ReleaseBuilderFor3dot10 class #('current') <br>
>> ReleaseBuilderFor3dot11 class #() <br>
>> ReleaseBuilderFor4dot3 class #() <br>
>> ReleaseBuilderFor4dot4 class #() <br>
>> ReleaseBuilderFor4dot5 class #() <br>
>> ReleaseBuilderNihongo class #() <br>
>> ReleaseBuilderSqueakland class #() <br>
>> <br>
>> Since this is the 4.5 release series, I was
poking around in the <br>
>> ReleaseBuilderFor4.5 to see if I could solve
the image issue for you guys. <br>
>> ReleaseBuilderFor4dot5
class>>prepareNewBuild hung when it tried to put
my <br>
>> (ahem) work up on trunk. <br>
>> <br>
>> It was then, I thought I should modify <br>
>>
ReleaseBuilderFor4dot5>>releaseRepository to
store my work locally. <br>
>> <br>
>> If people commonly do that, I would like to
mirror that style to keep <br>
>> things <br>
>> consistent. <br>
>> <br>
>> <br>
>> <br>
>> <br>
>> <br>
>> <br>
>> ---- On Thu, 12 Sep 2013 07:21:23 -0700 Frank
<br>
>> Shearar<<a moz-do-not-send="true" subj=""
mailid="frank.shearar%40gmail.com"
href="mailto:frank.shearar@gmail.com"
target="_blank">frank.shearar@gmail.com</a>>
wrote ---- <br>
>> <br>
>> On 12 September 2013 14:00, gettimothy <<a
moz-do-not-send="true" subj=""
mailid="gettimothy%40zoho.com"
href="mailto:gettimothy@zoho.com" target="_blank">gettimothy@zoho.com</a>>
wrote: <br>
>>> Is there a best-practice for fiddling
with ReleaseBuilderForXdotY ? <br>
>>> <br>
>>> I downloaded the latest trunk image so I
could look at the recent <br>
>>> background <br>
>>> image issue and, after running
ReleaseBuilderFor4dot5 <br>
>>> class>>prepareNewBuild <br>
>>> discovered that it uses MCHttpRepository
to upload to the <br>
>>> source.squeak.org/trunk. <br>
>>> <br>
>>> I was going to play around with
MCFileBasedRepository to save locally, <br>
>>> but <br>
>>> decided to ask the list first. <br>
>>> <br>
>>> Also, my apologies if I accidently
clobbered /trunk <br>
>> <br>
>> There is no ReleaseBuilderForXdotY. There is
only ReleaseBuilder. <br>
>> (Imagine that in a voice from Ghostbusters.)
<br>
>> <br>
>> You probably won't be able to clobber trunk.
Or, if you did, it's an <br>
>> administrator who's to blame, because only a
few folk have commit <br>
>> rights to Trunk. (Unlike Inbox, which is
world-writable.) <br>
>> <br>
>> frank <br>
>> <br>
>> <br>
>> <br>
>> <br>
>> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
<br>
</blockquote>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre wrap=""> </pre>
</blockquote>
<br>
<br>
</div>
</blockquote>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">
</pre>
</blockquote>
<br>
</body>
</html>