GraceDB Server issueshttps://git.ligo.org/computing/gracedb/server/-/issues2024-03-21T00:12:39Zhttps://git.ligo.org/computing/gracedb/server/-/issues/343Missing `else` clause in `check_and_serve_file`2024-03-21T00:12:39ZDaniel WysockiMissing `else` clause in `check_and_serve_file`[Sentry reported an error](https://ligo-caltech.sentry.io/issues/5081076463/?alert_rule_id=710526&alert_timestamp=1710797810690&alert_type=email&environment=test&notification_uuid=b5bfedba-abe7-4d31-b25f-280fa8935ba7&project=1456379&refe...[Sentry reported an error](https://ligo-caltech.sentry.io/issues/5081076463/?alert_rule_id=710526&alert_timestamp=1710797810690&alert_type=email&environment=test¬ification_uuid=b5bfedba-abe7-4d31-b25f-280fa8935ba7&project=1456379&referrer=alert_email) in [`core.http.check_and_serve_file`](https://git.ligo.org/computing/gracedb/server/-/blob/bebc24500045d00fc74ba56818bd9b34e184c310/gracedb/core/http.py#L62). The issue is that there's no `else` clause, and `response` is undefined. I don't know of a way to get more details behind this _instance_ of the error, however, there's only one possibility I see triggering this: `file_path` refers to a directory.
This would be solved by adding a simple `else` clause to catch all possible remaining errors, though we should probably identify exactly what happened here and see if it needs special treatment. Why did a user try accessing a file that was actually directory, assuming my assessment is correct?Daniel WysockiDaniel Wysockihttps://git.ligo.org/computing/gracedb/server/-/issues/341only send igwn-alerts to the {group}_{pipeline} topic2024-03-13T20:29:24ZAlexander Paceonly send igwn-alerts to the {group}_{pipeline} topicHistorically `igwn-alert` and `LVAlert` sends out g-event and e-event alerts to topics with the `{group}_{pipeline}` and `{group}_{pipeline}_{search}` schema. As more pipelines and searches are added, topic management is becoming a pain ...Historically `igwn-alert` and `LVAlert` sends out g-event and e-event alerts to topics with the `{group}_{pipeline}` and `{group}_{pipeline}_{search}` schema. As more pipelines and searches are added, topic management is becoming a pain across all the GraceDB tiers, especially with the lack of a scriptable API to interact with SCIMMA.
I'm proposing to change the way GraceDB issues alerts to only send to `{group}_{pipeline}` topics and have users filter on search, if need be. It would have the benefit of simplifying topic management, and also save some milliseconds in dispatching alerts. The alert contents would remain the same. Superevent topics would be unaffected by this change.
Putting out feelers to `igwn-alert` stakeholders... @deep.chatterjee @cody.messick @nicolas.arnaud @rebecca.ewing would that break your listening processes, if so, would adding an extra filter based on the search in the alert content be too much of a technical burden?O4bAlexander PaceAlexander Pacehttps://git.ligo.org/computing/gracedb/server/-/issues/340Add support for validating read access against multiple token issuers2024-02-20T15:51:31ZJosh WillisAdd support for validating read access against multiple token issuersCurrently a single gracedb instance can only accept tokens from one-and-only-one token issuer. This will need to change to support the HTCondor 'local issuer' that we will be rolling out as an alternative to vault-managed scitokens.Currently a single gracedb instance can only accept tokens from one-and-only-one token issuer. This will need to change to support the HTCondor 'local issuer' that we will be rolling out as an alternative to vault-managed scitokens.https://git.ligo.org/computing/gracedb/server/-/issues/338Ingest GCN VOEvents from SVOM2024-02-23T20:30:01ZBrandon PiotrzkowskiIngest GCN VOEvents from SVOMRequested by @rachel.hamburg, we want to start ingesting VOEvents from SVOM as another `GRB` search.
Here's an example of a notice:
[sb23041100_eclairs-wakeup_2.xml](/uploads/ad0d71686252e09b6e623e1a11eaf0e2/sb23041100_eclairs-wakeup_2...Requested by @rachel.hamburg, we want to start ingesting VOEvents from SVOM as another `GRB` search.
Here's an example of a notice:
[sb23041100_eclairs-wakeup_2.xml](/uploads/ad0d71686252e09b6e623e1a11eaf0e2/sb23041100_eclairs-wakeup_2.xml)
This will require the following changes
- [ ] Add `pipeline='SVOM'` as mentioned in https://git.ligo.org/computing/gracedb/server/-/issues/255
- [ ] Add `SVOM` external events to IGWN alert
- [ ] Modify [translator](https://git.ligo.org/computing/gracedb/server/-/blob/master/gracedb/events/translator.py) to ingest the particular notice values, such as adding `"Burst_Id"` to get the ID and `"Exposure"` to get the duration.O4bhttps://git.ligo.org/computing/gracedb/server/-/issues/336service dies with out-of-date gpstime package2024-01-10T12:05:13ZAlexander Paceservice dies with out-of-date gpstime packageI started a rolling restart of gracedb-playground and when it came back online, it 503'ed with the following error:
```
Traceback (most recent call last):
File "/app/gracedb_project/manage.py", line 44, in <module>
execute_from_co...I started a rolling restart of gracedb-playground and when it came back online, it 503'ed with the following error:
```
Traceback (most recent call last):
File "/app/gracedb_project/manage.py", line 44, in <module>
execute_from_command_line(sys.argv)
File "/usr/local/lib/python3.9/dist-packages/django/core/management/__init__.py", line 419, in execute_from_command_line
utility.execute()
File "/usr/local/lib/python3.9/dist-packages/django/core/management/__init__.py", line 395, in execute
django.setup()
File "/usr/local/lib/python3.9/dist-packages/django/__init__.py", line 24, in setup
apps.populate(settings.INSTALLED_APPS)
File "/usr/local/lib/python3.9/dist-packages/django/apps/registry.py", line 114, in populate
app_config.import_models()
File "/usr/local/lib/python3.9/dist-packages/django/apps/config.py", line 301, in import_models
self.models_module = import_module(models_module_name)
File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 790, in exec_module
File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
File "/app/gracedb_project/gracedb/alerts/models.py", line 19, in <module>
from .phone import get_twilio_from
File "/app/gracedb_project/gracedb/alerts/phone.py", line 12, in <module>
from events.permission_utils import is_external
File "/app/gracedb_project/gracedb/events/permission_utils.py", line 9, in <module>
from .models import Event
File "/app/gracedb_project/gracedb/events/models.py", line 31, in <module>
from gpstime import gpstime
File "/usr/local/lib/python3.9/dist-packages/gpstime/__init__.py", line 41, in <module>
from .leaps import LEAPDATA
File "/usr/local/lib/python3.9/dist-packages/gpstime/leaps.py", line 187, in <module>
LEAPDATA = LeapData()
File "/usr/local/lib/python3.9/dist-packages/gpstime/leaps.py", line 126, in __init__
self._load(fetch_ietf_leapfile, LEAPFILE_IETF_URL)
File "/usr/local/lib/python3.9/dist-packages/gpstime/leaps.py", line 136, in _load
raise RuntimeError(f"Error loading leap file {path}: {str(e)}")
RuntimeError: Error loading leap file https://www.ietf.org/timezones/data/leap-seconds.list: 404 Client Error: Not Found for url: https://www.ietf.org/timezones/data/leap-seconds.list
```
uhhhh does it not seem dangerous to anyone else to depend on an external file like that which just breaks the package.
I brought playground down to one container, and manually upgraded `gpstime` (from 0.6.2) to the latest version (0.8.1, https://git.ligo.org/computing/sccb/-/issues/1397) and that fixed it.
What this means is that production is waiting to break if it restarts for any reason. I'm going to upgrade `gpstime`, build new containers and redeploy while the detectors are offline.https://git.ligo.org/computing/gracedb/server/-/issues/331Unable to receive notifications2023-10-23T01:37:15ZElenna CapoteUnable to receive notificationsI am signed up to receive email alerts from graceDB, and it worked reliably well throughout the summer. Now, for the path month or so, I haven't received any alerts, although I know we are detecting many events.
I am signed up for alerts...I am signed up to receive email alerts from graceDB, and it worked reliably well throughout the summer. Now, for the path month or so, I haven't received any alerts, although I know we are detecting many events.
I am signed up for alerts tagged as "ADVREQ", which is what I was told was correct. I also tested my notifications and I receive the test email fine. The email address is my gmail address. I confirmed the test email arrives in my inbox, and I check my spam filter when event alerts go out and I have not mistakenly received the email to my spam.https://git.ligo.org/computing/gracedb/server/-/issues/330Queries based on SNR?2023-10-17T02:40:44ZKeita KawabeQueries based on SNR?It seems that [queries based on SNR are not supported](https://gracedb.ligo.org/documentation/queries.html). I learned this when I tried to quickly find [S230814h aka snr>40 event](https://gracedb.ligo.org/superevents/S230814ah/view/), b...It seems that [queries based on SNR are not supported](https://gracedb.ligo.org/documentation/queries.html). I learned this when I tried to quickly find [S230814h aka snr>40 event](https://gracedb.ligo.org/superevents/S230814ah/view/), but I can imagine that this would be useful, even if that's just for satisfying my curiosity ;)Daniel WysockiDaniel Wysockihttps://git.ligo.org/computing/gracedb/server/-/issues/327"Public events" overview must show Bilby skymap graphics not Bilby.multiorder...2023-09-28T19:12:52ZKeita Kawabe"Public events" overview must show Bilby skymap graphics not Bilby.multiorder.fits files["Public Events" overview page](https://gracedb.ligo.org/superevents/public/O4/) usually shows a thumbnail image of the skymap.
When PE update is sent out(??), Bilby.multiorder.fits file is linked instead and it appears to the users as ...["Public Events" overview page](https://gracedb.ligo.org/superevents/public/O4/) usually shows a thumbnail image of the skymap.
When PE update is sent out(??), Bilby.multiorder.fits file is linked instead and it appears to the users as if the link is broken, see attached. This should be changed to Bilby.png,0 etc.
![Screenshot_2023-09-10_at_13.49.53](/uploads/e605a14cfcfb0f2e358bb685874a1c01/Screenshot_2023-09-10_at_13.49.53.png)https://git.ligo.org/computing/gracedb/server/-/issues/326GraceDB popup before confirming the advocate signoff2023-09-01T00:17:20ZKeita KawabeGraceDB popup before confirming the advocate signoffBefore making/changing/deleting Advocate Signoff, "are you really sure?" type dialog box should be displayed. See the comment of @nicolas.arnaud in https://git.ligo.org/emfollow/followup-advocate-guide/-/issues/91:
> Yesterday we had the...Before making/changing/deleting Advocate Signoff, "are you really sure?" type dialog box should be displayed. See the comment of @nicolas.arnaud in https://git.ligo.org/emfollow/followup-advocate-guide/-/issues/91:
> Yesterday we had the case of a Lv0 shifter who used the advocate signoff interface on the wrong superevent... While what follows won't prevent this from happening again, I would suggest adding to the section https://emfollow.docs.ligo.org/followup-advocate-guide/procedures1.html#sign-off-okay-on superevent (and possibly to https://emfollow.docs.ligo.org/followup-advocate-guide/procedures1.html#sign-off-not-okay-on-superevent as well) the fact that, when pressing the signoff button, the action is not immediate. Instead, a popup window appears with an appropriate message (depending on what the action will be)
> > You are attempting to create an Advocate Sign-Off, which will generate a public alert. Do you wish to continue?
> > You are attempting to update an Advocate Sign-Off. Do you wish to continue?
> > You are attempting to delete an Advocate Sign-Off. Do you wish to continue?
>And, at this stage, the shifter should really pause for a few seconds, review what they are about to do and (only) then press OK or cancel.https://git.ligo.org/computing/gracedb/server/-/issues/325Add S-event ID to the advocate signoff popup windows2023-09-11T02:39:25ZNicolas ArnaudAdd S-event ID to the advocate signoff popup windowsMeaning: replacing the first sentence of the popup messages (three different ones I think)
> You are attempting to create/update/delete an Advocate Sign-Off (...)
by
> You are attempting to create/update/delete an Advocate Sign-Off **...Meaning: replacing the first sentence of the popup messages (three different ones I think)
> You are attempting to create/update/delete an Advocate Sign-Off (...)
by
> You are attempting to create/update/delete an Advocate Sign-Off **for Superevent SYYMMDD<abc>** (...)
That would give advocates one more chance to check they are about to signoff for the right event.https://git.ligo.org/computing/gracedb/server/-/issues/321documentation for cwb_r and cwb_s2023-07-28T18:28:52ZAlexander Pacedocumentation for cwb_r and cwb_s@roberto.depietri @marek.szczepanczyk
There is essentially [no documentation](https://git.ligo.org/computing/gracedb/server/-/blob/master/docs/user_docs/source/labels.rst?plain=1#L23-27) for what the `cWB_r` and `cWB_s` actually represe...@roberto.depietri @marek.szczepanczyk
There is essentially [no documentation](https://git.ligo.org/computing/gracedb/server/-/blob/master/docs/user_docs/source/labels.rst?plain=1#L23-27) for what the `cWB_r` and `cWB_s` actually represent.
Could you please provide one concise sentence for each label, so that can go in gracedb's documentation and toolip?https://git.ligo.org/computing/gracedb/server/-/issues/320Phone number not recognised2023-07-19T10:51:36ZDaniela PascucciPhone number not recognisedWhen I submit my mobile number in the contact list I get the error "Not a valid phone number".
I have a Belgian phone number and I use the format "+32*********".
It might be that that the problem is the country code. Just as a check, I ...When I submit my mobile number in the contact list I get the error "Not a valid phone number".
I have a Belgian phone number and I use the format "+32*********".
It might be that that the problem is the country code. Just as a check, I tried to change it from +32 to +33 (keeping the same number) and in that case there was no error.https://git.ligo.org/computing/gracedb/server/-/issues/319Fermi, Swift external triggers not being received from IGWN alerts2023-07-10T16:33:09ZKeith ThorneFermi, Swift external triggers not being received from IGWN alerts## Description of problem
Both Livingston and Hanford control-rooms are using the the igwn-alerts through scimma to get alerts for IFO stand down, etc.
We are getting events from gracedb.superevent and gracedb.test_snews. But we are no...## Description of problem
Both Livingston and Hanford control-rooms are using the the igwn-alerts through scimma to get alerts for IFO stand down, etc.
We are getting events from gracedb.superevent and gracedb.test_snews. But we are not receiving any Fermi and Swift events (from gracedb.external_fermi, gracedb.external_swift streams)
## Expected behavior
Fermi and Swift events that are retrieved by polling the GraceDB database are not seen as events from igwn-alert
## Context/environment
Using igwn-alert conda environment with scimma credentialshttps://git.ligo.org/computing/gracedb/server/-/issues/318Change public page default view to hide insignificant by default2023-07-18T15:49:20ZAlexander PaceChange public page default view to hide insignificant by defaultThe public page absolutely crawls right now because there are too many insignificant events. Changing the caching policy (https://git.ligo.org/computing/gracedb/server/-/merge_requests/150) will help, but I am also going to propose the f...The public page absolutely crawls right now because there are too many insignificant events. Changing the caching policy (https://git.ligo.org/computing/gracedb/server/-/merge_requests/150) will help, but I am also going to propose the following:
1) Keep the wording and table structure the same
2) Hide insignificant events by default
3) Change the backend behavior so that the "show significant events only" button triggers a new database transaction, instead of loading everything at once and then hiding the html elements.
Thoughts on this, @keita.kawabe?https://git.ligo.org/computing/gracedb/server/-/issues/317Document meaning of "coherence"2023-07-04T14:53:10ZJacopo TissinoDocument meaning of "coherence"I was looking at the coherence report in the superevent page; as far as I can tell there is no reference to somewhere this quantity is defined; I've looked in the gracedb page, the gracedb docs, the ligo.skymap docs.
The closest thing I ...I was looking at the coherence report in the superevent page; as far as I can tell there is no reference to somewhere this quantity is defined; I've looked in the gracedb page, the gracedb docs, the ligo.skymap docs.
The closest thing I found was in the docs for [`ligo-skymap-stats`](https://lscsoft.docs.ligo.org/ligo.skymap/tool/ligo_skymap_stats.html),
where however it's only stated that `log_bci` is the "natural log Bayes factor, coherent vs. incoherent".
From the perspective of a new user, there seems to be no way to find out what "coherence" means in this context besides asking someone.
Therefore, I think it would be useful to have somewhere a reference to section V.C in [Veitch and Vecchio 2010](http://arxiv.org/abs/0911.3820) or a page with a summarized discussion of its contents.
I'm opening this issue here since I think that the GraceDB page is the obvious candidate for where to include this information, but feel free to redirect me if this is not the case.https://git.ligo.org/computing/gracedb/server/-/issues/316actually disable error emails for 429 rate limits2023-06-28T19:46:56ZAlexander Paceactually disable error emails for 429 rate limitshttps://git.ligo.org/computing/gracedb/server/-/issues/315Proposal to enable SNR threshold setting for phone and email alerts.2023-08-30T07:06:12ZTakahiro SawadaProposal to enable SNR threshold setting for phone and email alerts.The GraceDB web page has the function to set FAR threshold for phone and email alerts. It would be helpful to be able to set SNR threshold as well.The GraceDB web page has the function to set FAR threshold for phone and email alerts. It would be helpful to be able to set SNR threshold as well.https://git.ligo.org/computing/gracedb/server/-/issues/314Typo in "preferred event information" panel2023-06-21T14:35:04ZJacopo TissinoTypo in "preferred event information" panelThere is a typo in the "Preferred Event Information" panel: "Chirp" is misspelled as "Chrip".
![Screenshot_from_2023-06-21_16-11-02](/uploads/e68aceb59fe21daae4cc4546be9cf3ac/Screenshot_from_2023-06-21_16-11-02.png)
I hope this is the ...There is a typo in the "Preferred Event Information" panel: "Chirp" is misspelled as "Chrip".
![Screenshot_from_2023-06-21_16-11-02](/uploads/e68aceb59fe21daae4cc4546be9cf3ac/Screenshot_from_2023-06-21_16-11-02.png)
I hope this is the right repository to make this issue, apologies otherwise.https://git.ligo.org/computing/gracedb/server/-/issues/311There is no migration that create EARLYWARNING label2023-06-23T17:43:50ZRoberto DePietriThere is no migration that create EARLYWARNING labelA restart of gracedb from an empty database does not create the EarlyWarning label.A restart of gracedb from an empty database does not create the EarlyWarning label.https://git.ligo.org/computing/gracedb/server/-/issues/309burst superevent skymaps on the public alerts page2023-06-02T15:04:31ZAlexander Paceburst superevent skymaps on the public alerts page@roberto.depietri: for the case of burst events (olib, cwb), is the skymap image always going to be `{olib, cwb}.png` AND tagged as `sky_loc`?
And is that the nomenclature for O3, ER15, and O4?@roberto.depietri: for the case of burst events (olib, cwb), is the skymap image always going to be `{olib, cwb}.png` AND tagged as `sky_loc`?
And is that the nomenclature for O3, ER15, and O4?publish the new public alerts pageAlexander PaceAlexander Pace