Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
gwcelery
gwcelery
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 52
    • Issues 52
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 12
    • Merge Requests 12
  • Requirements
    • Requirements
    • List
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • emfollow
  • gwcelerygwcelery
  • Issues
  • #252

Closed
Open
Opened Oct 25, 2019 by Stuart Anderson@stuart.andersonMaintainer

Data file links in comments for PNGs uploaded to GraceDB are not versioned

p_astro.json files uploaded to GraceDB are not versioned, however, the corresponding p_astro.png files are.

For example, all 4 links for S190828j have the same URL (https://gracedb.ligo.org/api/superevents/S190828j/files/p_astro.json) in the EM Followup section and Full Superevent Log entries 281 and 371. 2 of these public links give users incorrect information (log 281 and the first box in the EM Followup section) since they mistakenly return the updated information and not the original.

In addition to updating the code for future events, a cleanup of existing GraceDB events with multiple p_astro.json files is needed. Note, if it is just as easy to add versions to all files in the production instance of GraceDB that might be even better.

Edited Dec 04, 2019 by Leo Pound Singer
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: emfollow/gwcelery#252