external_triggers.handle_sn_lvalert is being executed for alert type log which is contrary to documentation
A connection timeout error https://emfollow.ligo.caltech.edu/sentry/gwcelery/issues/179/?query=is:unresolved occured inside handle_sn_lvalert. When I look at the information in sentry, I see that the celery job was launched because of an lvalert message of type log. Here's the celery job:
{
args: [
{
alert_type: log,
data: {
comment: DQR-compatible json generated from check_vectors results,
created: 2018-12-15 11:20:30 UTC,
file: https://gracedb.ligo.org/api/superevents/S181215j/files/gwcelerydetcharcheckvectors-S181215j.json,0,
file_version: 0,
filename: gwcelerydetcharcheckvectors-S181215j.json,
issuer: emfollow,
N: 31,
self: https://gracedb.ligo.org/api/superevents/S181215j/logs/31/,
tag_names: [
data_quality
]
},
object: {
category: Production,
created: 2018-12-15 11:20:12 UTC,
em_events: [],
far: 0.00000859257608009447,
gw_events: [],
labels: [],
links: {},
preferred_event: G323175,
submitter: emfollow,
superevent_id: S181215j,
t_0: 1228905479.599777,
t_end: 1228905480.599777,
t_start: 1228905478.599777
},
uid: S181215j
}
],
kwargs: {},
task_name: gwcelery.tasks.external_triggers.handle_sn_lvalert
}