From: Max Nikulin <manikulin@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org, Bastien Guerry <bzg@gnu.org>
Subject: Re: Worg: issue with org-tools page
Date: Sun, 6 Aug 2023 18:31:45 +0700 [thread overview]
Message-ID: <ef628e66-cfc5-a5d8-38ed-a46955138a7b@gmail.com> (raw)
In-Reply-To: <87wmy9k78t.fsf@localhost>
On 05/08/2023 19:23, Ihor Radchenko wrote:
> Max Nikulin writes:
>
>> I was trying to modify publish.sh to collect errors up to a reasonable
>> number, a draft is attached.
...
>> Currently it just prints summary of failures. When allowed failures
>> count is exceeded, it fails immediately.
>>
>> ./publish.sh --maxfail 32
>
> I am not sure why it would be useful to limit the number of errors to
> anything other than 0/infinity.
You have agreed that aborting of upload on any error may be
disappointing when the error was introduced by another person.
If there are dozens of failures then something serious has happened
either with Org or with Worg and it is a reason to not upload partial
results.
I believe that list of 5-10 failed files is suitable for notification
failure (e-mail, instant messaging, etc.).
> Note that I just pushed an alternative (but very similar) change in
> https://git.sr.ht/~bzg/worg/commit/b38a1f08
It fails on first error. I find a report containing several errors much
more helpful for figuring out what has actually happened. On the other
hand there should be a strong reason to read all errors when there are
hundreds one.
P.S. You have not documented that your approach abuses --debug-init
standard Emacs option.
next prev parent reply other threads:[~2023-08-06 11:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-09 15:37 Worg: issue with org-tools page Karl Voit
2023-04-09 16:53 ` Ihor Radchenko
2023-04-09 21:51 ` Karl Voit
2023-04-18 12:29 ` Ihor Radchenko
2023-04-18 13:48 ` Karl Voit
2023-07-29 12:14 ` Ihor Radchenko
2023-07-30 2:57 ` Max Nikulin
2023-07-30 6:40 ` Ihor Radchenko
2023-07-30 7:38 ` Max Nikulin
2023-07-30 9:16 ` Ihor Radchenko
2023-07-31 16:12 ` Max Nikulin
2023-07-31 16:41 ` Ihor Radchenko
2023-08-05 12:14 ` Max Nikulin
2023-08-05 12:23 ` Ihor Radchenko
2023-08-06 11:31 ` Max Nikulin [this message]
2023-08-06 15:08 ` Ihor Radchenko
2023-08-09 7:44 ` Ihor Radchenko
2023-08-09 10:35 ` Max Nikulin
2023-08-04 10:21 ` Bastien Guerry
2023-08-05 7:12 ` Ihor Radchenko
2023-08-05 8:50 ` Bastien Guerry
2023-08-05 11:06 ` Ihor Radchenko
2023-08-05 18:07 ` Bastien Guerry
2023-08-06 6:34 ` Ihor Radchenko
2023-08-06 15:17 ` Bastien Guerry
2023-08-07 13:46 ` Ihor Radchenko
2023-08-07 14:26 ` Bastien Guerry
2023-08-10 8:45 ` Ihor Radchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ef628e66-cfc5-a5d8-38ed-a46955138a7b@gmail.com \
--to=manikulin@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).