GraceDB Server issueshttps://git.ligo.org/computing/gracedb/server/-/issues2019-05-16T17:16:24Zhttps://git.ligo.org/computing/gracedb/server/-/issues/139Make server version number accessible2019-05-16T17:16:24ZPatrick BradyMake server version number accessibleMake version number of the running server code visible on the front page of the web site. It would also be nice to have an API method to get that version number.Make version number of the running server code visible on the front page of the web site. It would also be nice to have an API method to get that version number.https://git.ligo.org/computing/gracedb/server/-/issues/138issue tracker not linked from help pages2019-04-22T14:34:36ZMatthew Evansissue tracker not linked from help pagesThis issue tracker is not linked from the help pages, such as:
https://gracedb.ligo.org/documentation/queries.html
so to get here I had to rely on a kind reply to an email query.This issue tracker is not linked from the help pages, such as:
https://gracedb.ligo.org/documentation/queries.html
so to get here I had to rely on a kind reply to an email query.https://git.ligo.org/computing/gracedb/server/-/issues/137GraceDB Query problem2019-05-16T17:20:09ZMatthew EvansGraceDB Query problemHi GraceDB Authors!
I was trying to make a query string that was slightly more complicated that just "far < 1e-8" and failing, so I went to the Query Help page:
https://gracedb.ligo.org/documentation/queries.html
and copied the firs...Hi GraceDB Authors!
I was trying to make a query string that was slightly more complicated that just "far < 1e-8" and failing, so I went to the Query Help page:
https://gracedb.ligo.org/documentation/queries.html
and copied the first example string
instruments = "H1,L1,V1" & far < 1e-7
and got an error
Error: invalid query. (in★struments = "H1,L1,V1" & far < 1e-7)
In fact, I got a similar error for every one of the examples on the query help page (see image below), and every compound query I tried. For instance:
far > 0 & far < 1e-10
gives
Error: invalid query. (far > 0 ★& far < 1e-10)
while
far in 0, 1e-10
works.
So... what am I doing wrong?
Thanks,
Matt
![Screen Shot of Error](/uploads/bb15cbbbbf32ba19f764326fcb9254bc/Screen_Shot_2019-04-13_at_10.50.26_AM.png)https://git.ligo.org/computing/gracedb/server/-/issues/136Failed to receive phone call for S190408an2022-08-04T01:40:28ZBrian O'ReillyFailed to receive phone call for S190408anI received a text message for this event but my phone did not ring. I have my alert set for call and text based on the ADVREQ label.
My number is in the US, 225 area code.I received a text message for this event but my phone did not ring. I have my alert set for call and text based on the ADVREQ label.
My number is in the US, 225 area code.Backloghttps://git.ligo.org/computing/gracedb/server/-/issues/135Failed to receive GCN_PRELIM_SENT notification2019-04-10T02:35:26ZStuart AndersonFailed to receive GCN_PRELIM_SENT notificationI have a verified text contact alert registered with gracedb.ligo.org. However, I did not receive a notification of S190408an based on GCN_PRELIM_SENT.
I am not sure if it is related by all of the other labels for that super event are r...I have a verified text contact alert registered with gracedb.ligo.org. However, I did not receive a notification of S190408an based on GCN_PRELIM_SENT.
I am not sure if it is related by all of the other labels for that super event are rendered in green in my browser, however, GCN_PRELIM_SENT is black.https://git.ligo.org/computing/gracedb/server/-/issues/134File upload issues with 'gevent' worker class and more than two workers2022-08-04T01:31:48ZTanner PrestegardFile upload issues with 'gevent' worker class and more than two workersUpgrading to gracedb-2.4.1 today failed on gracedb-playground and gracedb due to issues with the asynchronous `gevent` worker class. It seemed to fail on attempts to issue alerts for file uploads. This problem was not detected in devel...Upgrading to gracedb-2.4.1 today failed on gracedb-playground and gracedb due to issues with the asynchronous `gevent` worker class. It seemed to fail on attempts to issue alerts for file uploads. This problem was not detected in development or testing so it seems to only happen when more than two workers are present. For now, we will stick with the `sync` worker class.
Some StackOverflow posts indicated we may need to turn off the `sendfile` setting, although it's not clear why.
See attached error email for more details.[_Django__ERROR__EXTERNAL_IP___Internal_Server_Error___api_events_G15070_log_.eml](/uploads/b8cac15345ed110e0e426c611a5b9c9e/_Django__ERROR__EXTERNAL_IP___Internal_Server_Error___api_events_G15070_log_.eml)https://git.ligo.org/computing/gracedb/server/-/issues/133Include link to LIGO/Virgo Public Alerts User Guide in GraceDB documentation2019-04-09T20:43:28ZLeo P. SingerInclude link to LIGO/Virgo Public Alerts User Guide in GraceDB documentationInitially reported as emfollow/userguide#92.Initially reported as emfollow/userguide#92.https://git.ligo.org/computing/gracedb/server/-/issues/132tooltip time conversion2022-08-04T01:31:07ZStuart Andersontooltip time conversionConsider having the tooltip window convert GPS to UTC and vice-a-versa, i.e., if a user hovers their cursor over a table element that contains a GPS time have the pop-up window show that same time in UTC (and vice-a-versa).Consider having the tooltip window convert GPS to UTC and vice-a-versa, i.e., if a user hovers their cursor over a table element that contains a GPS time have the pop-up window show that same time in UTC (and vice-a-versa).Backloghttps://git.ligo.org/computing/gracedb/server/-/issues/131Add link to git.ligo.org issues2019-06-18T15:12:04ZStuart AndersonAdd link to git.ligo.org issuesAdd "issues" (or "bug report" or ...) link to git.ligo.org issues page.Add "issues" (or "bug report" or ...) link to git.ligo.org issues page.https://git.ligo.org/computing/gracedb/server/-/issues/130click-to-sort for table column headings2022-08-04T01:30:14ZStuart Andersonclick-to-sort for table column headingsConsider making table column headings click-to-sort, e.g., https://gracedb.ligo.org/latest/ then click on "FAR" to sort one way and click again to reverse the sort order.Consider making table column headings click-to-sort, e.g., https://gracedb.ligo.org/latest/ then click on "FAR" to sort one way and click again to reverse the sort order.https://git.ligo.org/computing/gracedb/server/-/issues/129Add NSF acknowledgement2022-03-22T18:10:38ZStuart AndersonAdd NSF acknowledgementPublic pages should have an NSF acknowledgement, e.g., the NSF logo.Public pages should have an NSF acknowledgement, e.g., the NSF logo.https://git.ligo.org/computing/gracedb/server/-/issues/128Require FAR to be non-negative2022-08-04T01:28:20ZTanner PrestegardRequire FAR to be non-negativePipelines submitting with negative FAR is probably a sign that something is wrong. It is also triggering alerts with FAR thresholds since a negative FAR is obviously less than any reasonable FAR threshold.Pipelines submitting with negative FAR is probably a sign that something is wrong. It is also triggering alerts with FAR thresholds since a negative FAR is obviously less than any reasonable FAR threshold.Backloghttps://git.ligo.org/computing/gracedb/server/-/issues/127Drop description as a prototype system2019-04-01T13:38:49ZStuart AndersonDrop description as a prototype systemThe home page should drop the self description as a prototype system,
> GraceDB Overview
> The gravitational-wave candidate event database (GraceDB) is a prototype system toThe home page should drop the self description as a prototype system,
> GraceDB Overview
> The gravitational-wave candidate event database (GraceDB) is a prototype system tohttps://git.ligo.org/computing/gracedb/server/-/issues/126502 error for PUT requests with "large" message body2022-08-04T01:27:26ZTanner Prestegard502 error for PUT requests with "large" message bodyI can consistently produce a 502 Bad Gateway error by trying to update an event with a "large" data file. If I use a ~2 MB file it has a 100% failure rate, if I use something like 100 KB it will fail maybe 10% of the time. It seems to ...I can consistently produce a 502 Bad Gateway error by trying to update an event with a "large" data file. If I use a ~2 MB file it has a 100% failure rate, if I use something like 100 KB it will fail maybe 10% of the time. It seems to occur both on the production server and on a dev server, so it is not related to the difference in deployments.
I've monitored the gunicorn logs and the request never makes it to gunicorn when this happens. Looking in the Apache logs, I see the following error being produced by these requests:
```
[Wed Mar 27 09:56:54.238025 2019] [proxy:error] [pid 18753:tid 140701048239872] (104)Connection reset by peer: [client 75.86.138.174:37010] AH01084: pass request body failed to 127.0.0.1:8080 (localhost)
[Wed Mar 27 09:56:54.238106 2019] [proxy_http:error] [pid 18753:tid 140701048239872] [client 75.86.138.174:37010] AH01097: pass request body failed to 127.0.0.1:8080 (localhost) from 75.86.138.174 ()
```
To reproduce:
```
from ligo.gracedb.rest import GraceDb
g = GraceDb('https://gracedb-dev2.ligo.org/api/')
g.replaceEvent('T0497', './ligo/gracedb/test/integration/data/big.data')
```
I tried uploading the same file attached to a log message and it worked fine. The difference between the "replace event" request and the log upload is PUT vs POST.https://git.ligo.org/computing/gracedb/server/-/issues/125Directly modifiable attributes for external Gamma-Ray Burst events in GraceDB2019-08-30T13:25:06ZRobert CoyneDirectly modifiable attributes for external Gamma-Ray Burst events in GraceDBThere is desire in the GRB subgroup to keep GRB events in GraceDB (e.g. https://gracedb.ligo.org/events/E298046/view/ and others with the "GRB" search tag) up-to-date as their electromagnetic parameters evolve in the hours, days and week...There is desire in the GRB subgroup to keep GRB events in GraceDB (e.g. https://gracedb.ligo.org/events/E298046/view/ and others with the "GRB" search tag) up-to-date as their electromagnetic parameters evolve in the hours, days and weeks that follow an event. There are currently three GRB parameters (T90, redshift, and designation) that are modifiable by GraceDB end-users, through a series of forms present on the event page. Currently these fields are only modifiable by human beings through the web interface. We would like to be able to update these fields (and others) in an automated fashion through the python API. To this end, the GRB subgroup would like to request the following additions to GraceDB's features:
* [ ] The list of directly modifiable attributes be expanded to include location information, i.e. **RA, Dec, Err** in addition to the already-modifiable **T90, redshift** and **designation**
* [ ] The creation and distribution of a resource that would allow these attributes to be modified through the python API
Once such changes are made, GraceDB GRB entries will be continuously updated so that they are consistent with the parameter lists in-use by the GRB subgroup for LVC GRB-GW searches. These lists are curated using the Vetting Automation and Literature Informed Database (VALID) and are maintained by Rob Coyne, who will be the primary point of contact for these "sync" features. More information can be found:
* https://wiki.ligo.org/Bursts/VALID
* https://git.ligo.org/robert.coyne/VALID
Please let me know if there's any additional information needed.https://git.ligo.org/computing/gracedb/server/-/issues/124Improve LVAlert Overseer configuration2022-08-04T01:26:41ZTanner PrestegardImprove LVAlert Overseer configurationA few ideas:
* Move overseer into its own container so we don't have one instance in each gracedb container (will have to update the overseer code to allow connections from outside localhost (optionally; not by default) and secure it on...A few ideas:
* Move overseer into its own container so we don't have one instance in each gracedb container (will have to update the overseer code to allow connections from outside localhost (optionally; not by default) and secure it on AWS)
* Add some kind of monitoring to it (in AWS? via some Django URL that nagios can query?)
* Fix the client persistance with the failover to the basic LVAlert clienthttps://git.ligo.org/computing/gracedb/server/-/issues/123QOL Improvement - Login Warning2022-08-04T01:26:04ZRyan FisherQOL Improvement - Login WarningWould it be possible to add a warning to the search/search results page(s) if you aren't logged in? I noticed you almost did this during the presentation today, and it reminded me that it's easy for students and users to make this mista...Would it be possible to add a warning to the search/search results page(s) if you aren't logged in? I noticed you almost did this during the presentation today, and it reminded me that it's easy for students and users to make this mistake and waste time not finding their results.https://git.ligo.org/computing/gracedb/server/-/issues/122Open alerts should be public in GraceDb2022-08-04T01:25:41ZLeo P. SingerOpen alerts should be public in GraceDbIt's useful to be able to download old VOEvents. We should make this possible for anonymous GraceDb users. Please add the `public` tag to any VOEvent that is created with `internal=False`.It's useful to be able to download old VOEvents. We should make this possible for anonymous GraceDb users. Please add the `public` tag to any VOEvent that is created with `internal=False`.Backloghttps://git.ligo.org/computing/gracedb/server/-/issues/121\pi value in VOEvent builder erroneously truncated2019-03-27T15:02:32ZErik Katsavounidis\pi value in VOEvent builder erroneously truncated\pi in https://git.ligo.org/lscsoft/gracedb/blob/master/gracedb/events/buildVOEvent.py is set to 3.14152 which is not right at the 5th decimal point. Needs to be fixed.\pi in https://git.ligo.org/lscsoft/gracedb/blob/master/gracedb/events/buildVOEvent.py is set to 3.14152 which is not right at the 5th decimal point. Needs to be fixed.https://git.ligo.org/computing/gracedb/server/-/issues/120ConnectionReset error for some clients2019-03-11T17:12:42ZTanner PrestegardConnectionReset error for some clientsGWCelelry saw two `ConnectionReset` errors to gracedb-playground (see Sentry issue [here](https://emfollow.ligo.caltech.edu/sentry/gwcelery/issues/306/)). The error looks like
```
ConnectionResetError
[Errno 104] Connection reset by pee...GWCelelry saw two `ConnectionReset` errors to gracedb-playground (see Sentry issue [here](https://emfollow.ligo.caltech.edu/sentry/gwcelery/issues/306/)). The error looks like
```
ConnectionResetError
[Errno 104] Connection reset by peer
```