开云体育

Hello all,

The python3 d-rats fork is progressing slowly and there is still a lot that needs to be done.

The fork now should have the various e-mail gateways and APIs working.

The pluginsrv module is now working and there is a test program in the repositories.

Winlink and Mac support is now implemented.

All is not roses though.

I have a report that file transfers are not working between Mac systems, but is working with Mac to or from Windows.

The Mac user that reported this is trying to get more data to determine why this failure is occurring.

We are still seeing random segfault events.

We are also seeing random GTK Critical events logged to the console.

There are two main known causes of both those events:

1. Using deprecated GTK code. There is still a lot of this to be removed.

2. Calling GTK code improperly from threads.

Unfortunately neither the segfaults or the GTK Critical events messages usually give useful information as to the failure.

Sometimes we can find the cause of the GTK Critical event by noticing the operation that preceded it, other times by adding additional logging.

The segfaults really need learning the current program flow of the threads and making sure that it is done properly, and that also involves learning more about how GTK programming on python works,

My current course of action is going to be to start documenting the program flow module by module in my wiki, and at the same time doing code cleanups for those modules.



73,
-John, wb8tyw

Thanks for all your dedication and work on this fork.

Any way to crank up the logging verbosity so we can help make better/useful error reports?

73
Mark

On 5/1/2022 5:53 PM, N5TXZ via groups.io wrote:

Thanks for all your dedication and work on this fork.
Any way to crank up the logging verbosity so we can help make better/useful error reports?

The fork has been converted to use the logging module, most messages in D-rats are at logging level INFO, and there is still quite a lot of them that do not seem really useful to always have enabled.

The other logging level in the fork is debug, which is set by "--loglevel=DEBUG". This will get more logging.

As time goes by, I will probably be moving more messages in to the DEBUG class, and possibly using additional features of the logging module.

The --loglevel parameter can take any name or number that is valid for the logging module.

In most cases that I am getting the segfault or GTK crash reports, there is not enough built in logging in d-rats to identify the location.

Which means that with out a reproducer, only adding custom logging or examining the code is the only way to find where these issues are showing up.

I just started looking into the mainapp module to try to figure out the data flow.

Regards,
73,
-John, wb8tyw

I believe I have the most current revision operating-maps seem quick-log is functioning!

Looks great!

Thanks!!

Ralph Barbakoff (WA9LKZ)