# Costante non inizializzata EXIFR::JPEG

**URL:** <https://meta.discourse.org/t/uninitialized-constant-exifr-jpeg/90281>\
**Category:** Bug\
**Created:** [20 Giugno 2018, 8:53am UTC](https://meta.discourse.org/t/uninitialized-constant-exifr-jpeg/90281 "2018-06-20T08:53:41Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![tgxworld](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tgxworld/32/106117_2.png) [@tgxworld](https://meta.discourse.org/u/tgxworld)\
**Post date:** [20 Giugno 2018, 9:30am UTC](https://meta.discourse.org/t/uninitialized-constant-exifr-jpeg/90281/3 "2018-06-20T09:30:25Z")

</div>

Because the gem was accidentally upgraded again as we didn’t pin the gem version when it was fixed previously.

[https://github.com/discourse/discourse/commit/bb959e85e6a360372298107b31151ac18190fc14](https://github.com/discourse/discourse/commit/bb959e85e6a360372298107b31151ac18190fc14)

The proper solution is still to update our fork of the `image_optim` gem but that contains our patch to support timeout but I don’t expect an easy time updating it. There is some history to our fork of the gem, the timeout support that I work on previously was at the per worker level which isn’t ideal which is why the PR didn’t land into the gem. The plan is to add a global timeout across the worker.

---

_[View the full topic](https://meta.discourse.org/t/uninitialized-constant-exifr-jpeg/90281)._