Skip to content
Snippets Groups Projects
Select Git revision
  • alert-improvements
  • api-v2
  • bug-fixes
  • catalog-dev
  • er16-and-split-O4
  • fast-get-objects-for-user
  • fix_likelihood
  • fs-fix
  • glitchdb-dev
  • gracedb-2.21.3-1
  • gracedb-2.21.8-1
  • gracedb-2.22.0-1
  • gwtc-labels
  • histogram
  • hw-inj
  • inheritance-v2
  • master default protected
  • nan-be-gone
  • new_event_superevent_types
  • no-massgap-voevent
  • gracedb-2.31.0
  • gracedb-2.30.0-1
  • gracedb-2.30.0
  • gracedb-2.29.0
  • gracedb-2.28.2
  • gracedb-2.28.1
  • gracedb-2.28.0
  • gracedb-2.27.2
  • gracedb-2.27.1
  • gracedb-2.27.0
  • gracedb-2.26.0
  • gracedb-2.25.0
  • gracedb-2.24.0
  • gracedb-2.23.2
  • gracedb-2.23.1
  • gracedb-2.23.0
  • gracedb-2.22.0-1
  • gracedb-2.22.0
  • gracedb-2.21.8
  • gracedb-2.21.7
40 results
You can move around the graph by using the arrow keys.
Created with Raphaël 2.2.06Mar42128Feb2520191812118765123Jan17159418Dec171211109654327Nov1514127229Oct231712118543126Sep252119181124Aug124Jul231312928Jun25221914851May25Apr126223Mar16157Reorganizing alerts appAlso pin python-glue-common directly since its version was not pinned by pinning python-gluePin version of python-glue for containersBump up event creation throttle to 10/secondBugfix search sorting with no resultsAdd note about Test/MDC events and superevents to search and latest pagesBugfix to event graceid fields error handling in APIBugfix to initial group data migrationBugfix to a few migrations for creating robot accountsgracedb-2.3.0gracedb-2.3.0Add ligo-ca-certs to DockerfileAdd new robot certificates for 'emfollow' accountEnsure new cleanup script is executableAdd cleanup script to be run as crontab/k8s cronjobUpdate text on notification statusUpgrading unauthenticated user throttleTemporarily remove database routing for productionUse same DB name, username, and password for replica DBRequire DJANGO_DB_USER and DJANGO_REPLICA_DB_USERTurn off views for certificate debuggingSet up 'mail_admins' handler for 'django.request' logger in container deploymentUse new tag of lvalert-overseer and update pin to lvalertSet SERVER_EMAIL = ALERT_EMAIL_FROM for containersEnable overseer to be turned on/off by env variableAdd autorestart for gunicorn with supervisord in containerized deploymentBugfix: always use settings.ALERT_EMAIL_FROM for sending emailsGet ALERT_EMAIL_FROM from envvars for container deploymentGet email credentials from environment for containerized deploymentRequire Twilio credentials for containerized deploymentAdd autorestart for supervisor config for lvalert-overseerFix API authentication unit testsTemporary pin of ligo-lvalert until a new release happensAdd dependency for ligo-lvalert-1.5.5Add DJANGO prefix to console loggingAdd new OS package dependencies for ligo-lvalert-1.5.5Upgrade to ligo-lvalert-1.5.5Small bugfix to lvalert-client failoverSend overseer logging to stdoutTemporarily use git source code for lvalert-overseer installationExplicitly set LVAalert Overseer Resource to randomized stringReconfigure overseer to write logs to /tmp