Please test devel and PR #2523

Edward K. Ream

unread,

Mar 25, 2022, 1:21:22 PM3/25/22

to leo-editor

Today's work should complete Leo 6.6.

Please test both the devel and ekr-leoid2 branches.

PR #2523 (ekr-leoid2 branch) is experimental. It has not been merged into devel. It should affect only Leo's bridge, including leoserver.py. Although the PR's changes seem small, it's difficult for me to be sure of their consequences. I'll wait until I hear from Félix before merging this PR into devel.

Work already merged into devel should (finally!!) make cff and cfa work as intended.

Edward

Viktor Ransmayr

unread,

Mar 26, 2022, 12:15:18 PM3/26/22

to leo-editor

Hello Edward,

FYI: 'devel' is working fine for Fedora 34 and Debian 11 VMs on Qubes-OS.

Running the 'test-all' cmd returns the following results:

Debian: OK (skipped=6)

Fedora: OK (skipped=11) - and - in addition it reported the following failed assertions ...

###

.........
(python:1832): Gdk-CRITICAL **: 09:37:44.401: gdk_atom_intern: assertion 'atom_name != NULL' failed

(python:1832): Gdk-CRITICAL **: 09:37:44.401: gdk_atom_intern: assertion 'atom_name != NULL' failed
..........
----------------------------------------------------------------------
Ran 819 tests in 9.372s

###

Please let me know if I should provide any further information.

With kind regards,

Viktor

Edward K. Ream

unread,

Mar 26, 2022, 6:08:31 PM3/26/22

to leo-editor

On Sat, Mar 26, 2022 at 11:15 AM Viktor Ransmayr <viktor....@gmail.com> wrote:

FYI: 'devel' is working fine for Fedora 34 and Debian 11 VMs on Qubes-OS.

Running the 'test-all' cmd returns the following results:

Debian: OK (skipped=6)

Fedora: OK (skipped=11) - and - in addition it reported the following failed assertions ...

###

.........
(python:1832): Gdk-CRITICAL **: 09:37:44.401: gdk_atom_intern: assertion 'atom_name != NULL' failed

(python:1832): Gdk-CRITICAL **: 09:37:44.401: gdk_atom_intern: assertion 'atom_name != NULL' failed

Thanks, Viktor, for your testing.

These kinds of messages are not likely a problem, and certainly do not arise from Leo.

Edward

Félix

unread,

Mar 26, 2022, 8:44:20 PM3/26/22

to leo-editor

Hello Leonistas! 🦁

I've tested, no errors found, and I've made a last pr 2526 for the server to go along with it. And I'll be coding with that through the week before release, to see if any bugs remain when using it in real world instead of unit tests.

(also tested independently 2526 pr on felix-server4, and found no errors after running Leo's tests, test-leoserver and test-all, and using it in 'Standard' Leo & through leobridge via leointeg. on both windows and ubuntu)

Thanks for including 2523 and 2526 in 6.6! I'm hoping to release leointeg 1.0.7 in the following days after that, to go along with it :)

Félix

Edward K. Ream

unread,

Mar 27, 2022, 6:22:46 AM3/27/22

to leo-editor

On Sat, Mar 26, 2022 at 7:44 PM Félix <felix...@gmail.com> wrote:

Hello Leonistas! 🦁

I've tested, no errors found, and I've made a last pr 2526 for the server to go along with it. And I'll be coding with that through the week before release, to see if any bugs remain when using it in real world instead of unit tests.

(also tested independently 2526 pr on felix-server4, and found no errors after running Leo's tests, test-leoserver and test-all, and using it in 'Standard' Leo & through leobridge via leointeg. on both windows and ubuntu)

Thanks for including 2523 and 2526 in 6.6! I'm hoping to release leointeg 1.0.7 in the following days after that, to go along with it :)

Excellent. I've merged the two PRs relating to leoserver.py into devel.

I am declaring that Leo 6.6 is code complete.

Edward

Reply all

Reply to author

Forward