[pskmail] Re: jpskmail 0.3.8 beta test

  • From: John Douyere <vk2eta@xxxxxxxxx>
  • To: pskmail@xxxxxxxxxxxxx
  • Date: Sun, 11 Oct 2009 15:10:40 +1100

Per, Rein,

Some feedback on Alphas: Client 0.3.8 with Server 0.9.19.

1. When composing a new mail and the number of lines is larger than the
number of lines displayed, the right scroll bar does not shrink and allow me
to see the lines below. If I delete the top lines, the  lines below are
shifted up as they should. So the text is not lost, just not accessible on
the screen.

2. There is some interestion issue with the server. I sent a large (8K)
email for test purposes in compressed format and I got the following error
at the end:

Premature end of base64 data at /usr/local/share/pskmail_server/
rflinkserver.pl line 1604, <$reader> line 464.
Premature padding of base64 data at /usr/local/share/pskmail_server/
rflinkserver.pl line 1604, <$reader> line 464.

gzip: /home/jdouyere/.pskmail/compressed.gz: invalid compressed data--format
violated
cat: /home/jdouyere/.pskmail/compressed: No such file or directory
readline() on closed filehandle CMAIL at /usr/local/share/pskmail_server/
rflinkserver.pl line 1619.
End of mail receive...

Reviewing the TX log I found a few abnormal behaviours:

1. Server side: even is some blocks are missed the "last good block" and
"last good contiguous block" numbers are the same which is not what the
protocol states it shoudl be (as evidenced in the status block sent by the
server).

2. Client OR server side: some blocks (of a compressed email) appear in the
server window as a blank line which is not logical for a compressed data
block.

3. Client or server side: In one instance I had the client adding, at each
exchange with the server, one missing block on top of the previously
supposedly missing blocks. This until disconnect by the server. When
checking Fldigi, the blocks were received properly.

4. Server side most likely: the management of the missing blocks is not as
per the protocol: the requested list of missing blocks typically has less
than the whole list of missing blocks. Example: in a 10 blocks mail sending
exchange, if I prevent the server from receiving blocks 4,5,6 and 7, the
status block sent to the client will only request blocks 4 and 5 for
example. 6 and 7 may be requested later, sometimes right at the end.

Sorry I don't have more time to zoom in the code to describe more of the
logic issues, but I am a little short of time this weekend. But these
protocol issues are significant game breakers IMO.

Hope this helps.

Regards,

John


On Sat, Oct 10, 2009 at 5:32 PM, Pär Crusefalk <per@xxxxxxxxxxxx> wrote:

> Yes, its only a beta for 0.3.8 and I should have updated the about form
> with that info. I intend to release an updated version this weekend.
> >From beta test so far I would like to add/change:
> - Icons for the shortcut and menu items
> - An icon for the quickstart "manual"
> - Maybe add a way to clear the monitor window (the lower)..
> - Add tooltip for the checkbox "compressed" on the email settings tab.
> - We seem to have lost all of the tooltips.. I'll look into that
> - About box info (already changed)
>
> And, was kind of thinking we should add PSK500 and PSK1000 to the mode
> settings on the menu but perhaps we should wait until that is completed.
>
> Anything else needed?
>
> 73 de Per, sm0rwo
>
> P.s. Was just out and raised a new antenna for the server, a warc band
> dipole up abt 15 meters (50 feet). Nice antena weather, freezing
> cold :-)
>
>
> fre 2009-10-09 klockan 20:40 -0400 skrev Andy obrien:
> > by the way, I am running 0.3.8 but the "about" info reports that it is
> 0.3.7
> >
> > Andy K3UK
> >
>
>
>

Other related posts: