[jitsi-dev] Processed: found 785299 in 2.8.5426-1


#1

Processing commands for control@bugs.debian.org:

found 785299 2.8.5426-1

Bug #785299 [jitsi] jitsi: Keeps showing severe error every minute
There is no source info for the package 'jitsi' at version '2.8.5426-1' with architecture ''
Unable to make a source version for version '2.8.5426-1'
Marked as found in versions 2.8.5426-1.

thanks

Stopping processing here.

Please contact me if you need assistance.

···

--
785299: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785299
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems


#2

Hi,

Thanks. You are right we need to swallow that exception, and do not
show it at all. But as this is ping, the reason for doing this is to
make sure the connection is alive, even when there is an error we are
sure server is responding and connection is alive and we will continue
to check this. This is the reason to continue pinging even when this
is not supported, otherwise we risk more serious problems like losing
messages.

Regards
damencho

···

On Thu, May 14, 2015 at 4:03 PM, Debian Bug Tracking System <owner@bugs.debian.org> wrote:

Processing commands for control@bugs.debian.org:

found 785299 2.8.5426-1

Bug #785299 [jitsi] jitsi: Keeps showing severe error every minute
There is no source info for the package 'jitsi' at version '2.8.5426-1' with architecture ''
Unable to make a source version for version '2.8.5426-1'
Marked as found in versions 2.8.5426-1.

thanks

Stopping processing here.

Please contact me if you need assistance.
--
785299: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785299
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#3

This is a good point. So just not showing that error would be
good.

Kurt

···

On Thu, May 14, 2015 at 04:16:11PM +0300, Damian Minkov wrote:

Hi,

Thanks. You are right we need to swallow that exception, and do not
show it at all. But as this is ping, the reason for doing this is to
make sure the connection is alive, even when there is an error we are
sure server is responding and connection is alive and we will continue
to check this. This is the reason to continue pinging even when this
is not supported, otherwise we risk more serious problems like losing
messages.