# Old gitlab issue have lost their images

**URL:** https://discourse.paraview.org/t/old-gitlab-issue-have-lost-their-images/4255
**Category:** Development
**Created:** [May 5, 2020, 6:16am UTC](https://discourse.paraview.org/t/old-gitlab-issue-have-lost-their-images/4255 "2020-05-05T06:16:19Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [May 5, 2020, 6:16am UTC](https://discourse.paraview.org/t/old-gitlab-issue-have-lost-their-images/4255/1 "2020-05-05T06:16:19Z")

</div>

**All** old issues (more than 2 years) have lost their images.  
eg: [https://gitlab.kitware.com/paraview/paraview/-/issues/17860](https://gitlab.kitware.com/paraview/paraview/-/issues/17860)

Not practical at all.

@cory.quammen

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [May 5, 2020, 8:00am UTC](https://discourse.paraview.org/t/old-gitlab-issue-have-lost-their-images/4255/2 "2020-05-05T08:00:37Z")

</div>

Their data as well, this is very bad. Old issue can’t be reproduced anymore.  
[https://gitlab.kitware.com/paraview/paraview/-/issues/17048](https://gitlab.kitware.com/paraview/paraview/-/issues/17048)

---

<div class="post-metadata">

### Author: ![utkarsh.ayachit](https://discourse.paraview.org/user_avatar/discourse.paraview.org/utkarsh.ayachit/32/39_2.png) [@utkarsh.ayachit](https://discourse.paraview.org/u/utkarsh.ayachit)
#### Post date: [May 5, 2020, 2:11pm UTC](https://discourse.paraview.org/t/old-gitlab-issue-have-lost-their-images/4255/3 "2020-05-05T14:11:20Z")

</div>

that is bad indeed. Mind emailing sysadmins and letting them know? Something possibly happened during one of the upgrades. Maybe it’s fixable.

---

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [May 5, 2020, 2:19pm UTC](https://discourse.paraview.org/t/old-gitlab-issue-have-lost-their-images/4255/4 "2020-05-05T14:19:21Z")

</div>

Oof. At worst, backups should be available to rummage through and try and find them again.

---

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [May 5, 2020, 2:28pm UTC](https://discourse.paraview.org/t/old-gitlab-issue-have-lost-their-images/4255/5 "2020-05-05T14:28:38Z")

</div>

I emailed sysadmins, FYI.

---

<div class="post-metadata">

### Author: ![wascott](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/w/8e8cbc/32.png) [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [May 5, 2020, 4:31pm UTC](https://discourse.paraview.org/t/old-gitlab-issue-have-lost-their-images/4255/6 "2020-05-05T16:31:42Z")

</div>

Good catch, Mathieu! Keep up the good work!

(By the way, this is why we put a second set of eyes on resolving bugs!)

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [May 6, 2020, 1:35am UTC](https://discourse.paraview.org/t/old-gitlab-issue-have-lost-their-images/4255/7 "2020-05-06T01:35:13Z")

</div>

Quick note to inform that very old issues are not impacted since their data is still on mantis.

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [May 28, 2020, 2:14am UTC](https://discourse.paraview.org/t/old-gitlab-issue-have-lost-their-images/4255/8 "2020-05-28T02:14:14Z")

</div>

FYI, this has been fixed.
