Fix issue #1 BEACON EXEC abnormal close messages in aprx.log

This commit is contained in:
Dan Srebnick 2018-01-28 12:48:38 -05:00
parent 53a4c464f6
commit f301d8d2e9
5 changed files with 15 additions and 4 deletions

View File

@ -1,5 +1,5 @@
Package: noaacap
Version: 0.7.3
Version: 0.8
Section: hamradio
Priority: extra
Maintainer: Dan Srebnick <k2dls at k2dls.net>

View File

@ -1,3 +1,3 @@
Copyright: 2017 Daniel L. Srebnick <k2dls@k2dls.net>
Copyright: 2017-2018 Daniel L. Srebnick <k2dls@k2dls.net>
License: BSD-2-clause
Files: *

View File

@ -6,7 +6,7 @@
##
## See /usr/local/share/noaacap/CHANGELOG for change history
##
version = "0.7"
version = "0.8"
import sys
import pytz
@ -249,6 +249,13 @@ for i in range(0, count):
if parms[j].valueName.string == 'UGC':
zcs = parms[j].value.string
# This handles expired messages found to contain no UGC
try:
zcs
except:
log.debug('No zcs in message')
continue
type = pp[bytes(Phenomena, 'utf-8')].decode('utf-8')
if Action == "CAN":

View File

@ -1,5 +1,9 @@
noaacap changelog
##
Version: 0.8
Not Released Yet
Fix alerts without UGC causing BEACON EXEC abnormal close
##
Version: 0.7
Release: September 28, 2017
Added myResend parameter to control message resends.

View File

@ -1,6 +1,6 @@
BSD 2-Clause License
Copyright (c) 2017, Daniel L. Srebnick
Copyright (c) 2017-2018, Daniel L. Srebnick
All rights reserved.
Redistribution and use in source and binary forms, with or without