[FFmpeg-devel] Fwd: Delivery Status Notification (Delay)

[Roger Pack]

Would it be possible to tweak or some how modify the trac system so
that responses to update notifications about trac items get posted
back as comments to the trac item?

Today if you respond to a ticket update, it sends an email to
"trac at avcodec.org" which just bounces [or at least have it reply to
noreply at avcodec.org or its like].
Thanks.
-roger-

---------- Forwarded message ----------
From: Mail Delivery Subsystem <mailer-daemon at googlemail.com>
Date: Tue, Apr 15, 2014 at 11:44 AM
Subject: Delivery Status Notification (Delay)
To: rogerdpack at gmail.com


This is an automatically generated Delivery Status Notification

THIS IS A WARNING MESSAGE ONLY.

YOU DO NOT NEED TO RESEND YOUR MESSAGE.

Delivery to the following recipient has been delayed:

     trac at avcodec.org

Message will be retried for 2 more day(s)

Technical details of temporary failure:
The recipient server did not accept our requests to connect. Learn more at
http://support.google.com/mail/bin/answer.py?answer=7720
[(0) sendmail.bmf.hu. [193.224.40.21]:25: Connection timed out]

----- Original message -----

DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;

h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        bh=TBqVV2f75B6igEGJXm5L9qmfaPIgnk2+qm41ESr6YUk=;
        b=wVKnBLuFlUcYp4mMoGQwTMxAid2XIQa2+mcEQKw68hSGkY3iNsyvGz+RKYaNh9zEia

 ujrkRYWcAQPk1XTR1aCxorQ0yhlNsZqritokOuaqp3HovHFkJF5iVRkjooDnr+f8w2Oj

 B81GqKJtneEKZsNLzuyHr/4V6lIopcxxUvgfGdvr1J77ja6z6eBdtr13OSUPB/FeYDjq

 kveUi0YAM4sjBsL7Sqvc1mWJVpxMR0ojomy7Wbs+TbJ7vjhdxy2avXdBNreU6ZFyKuf+

 K2e5gUF0HztAZi7pOxhanQTm9DZV7jXiAWtfTrcFfS4E/XupMj4J8Z5lAO+kew0gv5b0
         zuvg==
X-Received: by 10.194.24.194 with SMTP id w2mr33834398wjf.25.1397492996103;
 Mon, 14 Apr 2014 09:29:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.217.43.10 with HTTP; Mon, 14 Apr 2014 09:29:36 -0700 (PDT)
In-Reply-To: <055.93e5922f1ef48f2f08d6c3f58f0cc7db at avcodec.org>
References: <040.f0f731c9516226cb3bc5db78ab940174 at avcodec.org> <
055.93e5922f1ef48f2f08d6c3f58f0cc7db at avcodec.org>
From: Roger Pack <rogerdpack at gmail.com>
Date: Mon, 14 Apr 2014 10:29:36 -0600
Message-ID: <
CAPfeOnugpd-r9-f1paBQPPiEjFkZSfzUJ_-v8PF+vs16D+ezSQ at mail.gmail.com>
Subject: Re: [FFmpeg-trac] #3507(undetermined:new): console prompt to
 "overwrite file" can be lost
To: FFmpeg <trac at avcodec.org>
Content-Type: multipart/alternative; boundary=047d7b450c569be3ba04f703315a

Or I suppose you could make the logging system "input aware" somehow [like
a mutex to block new log messages until gets returns or what not]...perhaps?


On Sun, Apr 13, 2014 at 10:29 PM, FFmpeg <trac at avcodec.org> wrote:

> #3507: console prompt to "overwrite file" can be lost
>
-------------------------------------+-------------------------------------
>              Reporter:  rogerdpack   |                    Owner:
>                  Type:  defect       |                   Status:  new
>              Priority:  normal       |                Component:
>               Version:  unspecified  |  undetermined
>              Keywords:               |               Resolution:
>              Blocking:               |               Blocked By:
> Analyzed by developer:  0            |  Reproduced by developer:  0
>
-------------------------------------+-------------------------------------
>
> Comment (by michael):
>
>  One way to fix this would be to change the loglevel before printing the
>  overwrite question so other messages from other threads that arent
>  critical wouldnt be shown. And then change it back after the user
awnsered
>  the question
>
>  also reducing the noisyness of these threads in general may be a good
idea
>
>  i cant really work on either of these as iam on linux here and the
>  testcase is dshow
>
> --
> Ticket URL: <https://trac.ffmpeg.org/ticket/3507#comment:1>
> FFmpeg <https://ffmpeg.org>
> FFmpeg issue tracker
>