Re: [Zim-wiki] 0.66 was pushed to my machine

[Jaap Karssenberg]

Hi Sara,

Yes, we need to improve on release testing, as I just wrote in a new mail
thread, I think we should start working with release candidates for future
releases. However, the problem remains that putting out a release candidate
with a lot of issues still impacts a lot of people who may want to test,
but also do want to do actual work. I fear that not pushing the candidates
to the PPA will mean they are only seen by a limited audience.

Best way to improve the quality before anyone is impacted is by improving
the automated test suite. I was very surprised that the issue with the
headers going missing was not caught by the test suite. Part of my fix is
to make sure the test will now detect this if it ever happens again.

Maybe for other parts of your workflow you can put small scenarios in a bug
report (yes please use github issues) that can be turned in an automatic
test. That will better secure bugs not returning without the burden of
manual testing.

Regards,

Jaap



On Mon, May 1, 2017 at 12:19 PM Sara Ziner 
wrote:

> Hi Jaap,
>
> thanks a lot for the kind answer!
> Don't get me wrong: With all these little this-and-that's, Zim is simply
> awsome.
> Let alone the verbatim storage in text files and the serverless setup. In
> fact these both are the reason why I have chosen to use Zim strategically
> for each and every note I take, image set I want to comment and archive,
> even to keep my personal document file: There is no lock-in to some strange
> data format which tomorrow can cease to exist.
> I even restrain from upgrading my corporate MacBook to Sierra because I
> heard there are issues with Zim.
>
> Regarding the testing:
> Now that zim is maintained in GitHub, I would happliy vounteer to do a
> manual test with my personal workflow before new releases. You even could
> employ a dev branch that can be merged to produce a release to support
> close test cycles.
> I admit that my workflow is a bit biased towards image archiving (off the
> Notebook's folder to allow SCM for that one) and automatic generation,
> manipulation and tree movement of pages from scraped web content – but
> maybe this will complement other tester's workflows.
>
> (And, regarding the background spawning, I had to learn that I now at
> least see quite error messages and would be able to report them. Do you
> plan to switch to GitHub issues for error messages? – Would be fantastic
> because they work like a charm.)
>
> Again: Thanks for caring!
> Sara
>
>
>
>
>
> 2017-05-01 8:52 GMT+02:00 Jaap Karssenberg :
>
>>
>> Hi Sara,
>>
>>
>> ___
> Mailing list: https://launchpad.net/~zim-wiki
> Post to : zim-wiki@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~zim-wiki
Post to : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp

Re: [Zim-wiki] 0.66 was pushed to my machine

[Sara Ziner]

Hi Jaap,

thanks a lot for the kind answer!
Don't get me wrong: With all these little this-and-that's, Zim is simply
awsome.
Let alone the verbatim storage in text files and the serverless setup. In
fact these both are the reason why I have chosen to use Zim strategically
for each and every note I take, image set I want to comment and archive,
even to keep my personal document file: There is no lock-in to some strange
data format which tomorrow can cease to exist.
I even restrain from upgrading my corporate MacBook to Sierra because I
heard there are issues with Zim.

Regarding the testing:
Now that zim is maintained in GitHub, I would happliy vounteer to do a
manual test with my personal workflow before new releases. You even could
employ a dev branch that can be merged to produce a release to support
close test cycles.
I admit that my workflow is a bit biased towards image archiving (off the
Notebook's folder to allow SCM for that one) and automatic generation,
manipulation and tree movement of pages from scraped web content – but
maybe this will complement other tester's workflows.

(And, regarding the background spawning, I had to learn that I now at least
see quite error messages and would be able to report them. Do you plan to
switch to GitHub issues for error messages? – Would be fantastic because
they work like a charm.)

Again: Thanks for caring!
Sara





2017-05-01 8:52 GMT+02:00 Jaap Karssenberg :

>
> Hi Sara,
>
>
>
___
Mailing list: https://launchpad.net/~zim-wiki
Post to : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp

Re: [Zim-wiki] 0.66 was pushed to my machine

[Jaap Karssenberg]

Hi Sara,

Sorry to hear that this release causes you so much trouble. To answer your
last question first: this release is not intended to have major
incompatibilities. Afraid that the reality of a project like zim is that we
do not find all issues unless we actually make a new release. There isn't a
big group of people testing changes before they are released, and although
I try very hard my own testing and the unittest suite do not catch
everything.

- headers are now removed at will
- removing an image while a page showing it is loaded now generates memory
fault and terminates zim (worked great before)
- renaming a page from outside while displayed in zim changed behavior to
the worse

These 3 are new issues for me - you are the first to report them. Will try
to reproduce and fix them.

- forking to background changed to blocking a terminal window

Here zim is now more inline with other applications. This was necessary to
remove a lot of issues other users where having with the background
spawning. This part of the code is now greatly simplified and *still*
giving issues :(

- new unremovable "attachments" button wastes room under the text area
(compromising my layout optimization)

This is a "rough edge" in the design. Side panes now "collapse" instead of
"hiding". Keeping the tabs of the side pane visible at all times makes the
behavior much more predictable for most users.  It costs more real estate,
and I'm open for design suggestions how to gain it back - maybe we should
combine it with the statusbar for the bottom pane?

Regards,

Jaap




On Mon, May 1, 2017 at 4:29 AM Sara Ziner  wrote:

> Thanks, Jiri, for that hint. Helps a lot.
>
> @all
> Unfortunately, I had to find yet another unexpected incompatibility:
> Headers are removed even from existing files.
> For my workflow this means that I have to remove most well-formed-checks
> for the extension I have developed.
>
> Now it's 5 I found during the first day:
> - headers are now removed at will
> - forking to background changed to blocking a terminal window
> - new unremovable "attachments" button wastes room under the text area
> (compromising my layout optimization)
> - removing an image while a page showing it is loaded now generates memory
> fault and terminates zim (worked great before)
> - renaming a page from outside while displayed in zim changed behavior to
> the worse
>
> All those compromise my workflow and I will need a day's work or so (which
> I do not have at the moment) to recover.
>
> Is it really necessary to have such incompatibilities pushed to automatic
> updates?
> Usually incompatibilities will give rise to a change of the major release
> and shall not be pushed automatically.
>
> All the best,
> Sara
>
>
>
> 2017-04-29 16:39 GMT+02:00 Jiří Janoušek :
>
>> Or define an alias: `alias zim="nohup /usr/bin/zim > /dev/null 2>&1 &"`
>>
>
> ___
> Mailing list: https://launchpad.net/~zim-wiki
> Post to : zim-wiki@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~zim-wiki
Post to : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp

Re: [Zim-wiki] 0.66 was pushed to my machine

[Sara Ziner]

Thanks, Jiri, for that hint. Helps a lot.

@all
Unfortunately, I had to find yet another unexpected incompatibility:
Headers are removed even from existing files.
For my workflow this means that I have to remove most well-formed-checks
for the extension I have developed.

Now it's 5 I found during the first day:
- headers are now removed at will
- forking to background changed to blocking a terminal window
- new unremovable "attachments" button wastes room under the text area
(compromising my layout optimization)
- removing an image while a page showing it is loaded now generates memory
fault and terminates zim (worked great before)
- renaming a page from outside while displayed in zim changed behavior to
the worse

All those compromise my workflow and I will need a day's work or so (which
I do not have at the moment) to recover.

Is it really necessary to have such incompatibilities pushed to automatic
updates?
Usually incompatibilities will give rise to a change of the major release
and shall not be pushed automatically.

All the best,
Sara



2017-04-29 16:39 GMT+02:00 Jiří Janoušek :

> Or define an alias: `alias zim="nohup /usr/bin/zim > /dev/null 2>&1 &"`
>
___
Mailing list: https://launchpad.net/~zim-wiki
Post to : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp

Re: [Zim-wiki] 0.66 was pushed to my machine

[Jiří Janoušek]

Hello Sara,

Zim 0.66 seems to exhibit a typical behaviour for a desktop app. The
previous behaviour - forking into background - was rather unusual. You
can use `nohup zim &` for your workflow to get closer to the previous
state.

Or define an alias: `alias zim="nohup /usr/bin/zim > /dev/null 2>&1 &"`

Best regards,

Jiri Janousek

On Sat, Apr 29, 2017 at 4:01 PM, Sara Ziner  wrote:
> Hi,
>
> I am using zim for about a year now and everything was fine. After a manual
> upgrade to 0.65 I decided to add the repo to my Ubuntu:
> http://ppa.launchpad.net/jaap.karssenberg/zim/ubuntu
>
> And today it pushed 0.66 to my machine.
>
> It was, of course, my fault to trust the repo, but now it happened: 0.66 is
> a HUGE step back.
> I cannot longer just say "zim" at the shell and then continue working,
> because it now does not go to background any longer, and it pollutes the
> terminal like so:
>
> --- snip ---
>
> $ zim
> INFO: This is zim 0.66
> WARNING: Could not find all icon sizes for the application icon
> INFO: Using default notebook: file:///home//Notebooks/
> INFO: VCS detected: git - /home//Notebooks/Netzindex
> INFO: Open page: 
> INFO: Flushing index
> INFO: VCS detected: git - /home//Notebooks/
> INFO: Open page: 
>
> ** (zim:21627): CRITICAL **: pygtk_generic_tree_model_iter_nth_child:
> assertion 'parent == NULL || parent->stamp ==
> PYGTK_GENERIC_TREE_MODEL(tree_model)->stamp' failed
>
> ** (zim:21627): CRITICAL **: pygtk_generic_tree_model_unref_node: assertion
> 'VALID_ITER(iter, tree_model)' failed
>
> ** (zim:21627): CRITICAL **: pygtk_generic_tree_model_unref_node: assertion
> 'VALID_ITER(iter, tree_model)' failed
>
> ** (zim:21627): CRITICAL **: pygtk_generic_tree_model_iter_nth_child:
> assertion 'parent == NULL || parent->stamp ==
> PYGTK_GENERIC_TREE_MODEL(tree_model)->stamp' failed
>
> ** (zim:21627): CRITICAL **: pygtk_generic_tree_model_unref_node: assertion
> 'VALID_ITER(iter, tree_model)' failed
>
> ** (zim:21627): CRITICAL **: pygtk_generic_tree_model_unref_node: assertion
> 'VALID_ITER(iter, tree_model)' failed
> INFO: Open page: SaraZiner (SaraZiner)
> INFO: Running: ['git', 'add', '.txt'] (cwd: /home//Notebooks/)
> INFO: Running: ['git', 'add', '.txt'] (cwd: /home//Notebooks/)
> INFO: Running: ['git', 'add', '.txt'] (cwd: /home//Notebooks/)
> INFO: Running: ['git', 'add', '.txt'] (cwd: /home//Notebooks/)
> INFO: Running: ['git', 'add', '.txt'] (cwd: /home//Notebooks/)
> INFO: Running: ['git', 'add', '.txt'] (cwd: /home//Notebooks/)
> INFO: Open page: 
>
> --- snap ---
>
> I cannot close the terminal because this will close the Zim windows also.
> Sending zim in background via zim& leaves my terminal under constant fire
> also.
> The "critical" messages do not increase trust too much, too.
>
> These incompatible changes effectively renders zim useless for me for the
> time being.
>
> Besides certain upcoming questions about outbound QA:
> - Any ideas how I can get back the version 0.65 that worked?
> - Will 0.66 already have introduced incompatible changes in data?
>
> All the best,
> Sara
>
>
>
> ___
> Mailing list: https://launchpad.net/~zim-wiki
> Post to : zim-wiki@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~zim-wiki
Post to : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp

Re: [Zim-wiki] 0.66 was pushed to my machine

[Sara Ziner]

Oh and –daring to use the new Zim because I won't push to git unless I'm
back to 0.65– there is now a useless new button "Attachments" under the
text area which costs almost 2 lines of text (this is much on my 12"
screen) and that can only be removed by completely disabling the Attachment
Browser.


2017-04-29 16:01 GMT+02:00 Sara Ziner :

>
> It was, of course, my fault to trust the repo, but now it happened: 0.66
> is a HUGE step back.
>
>
___
Mailing list: https://launchpad.net/~zim-wiki
Post to : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp