Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update to latest heroku-24 #2688

Open
jrochkind opened this issue Jul 22, 2024 · 5 comments
Open

update to latest heroku-24 #2688

jrochkind opened this issue Jul 22, 2024 · 5 comments
Labels
1-2-days 1-2 day of developer time estimate

Comments

@jrochkind
Copy link
Contributor

  • vips buildpack no longer supported, but just adding libvips-tools to Aptfile should give us a good recent vips version that will work (I've tested somewhat)
@jrochkind jrochkind added the 1-2-days 1-2 day of developer time estimate label Aug 8, 2024
@jrochkind
Copy link
Contributor Author

heroku-24 removed ghostscript as a default install, which would be inconvenient for us.

But it looks like they may be adding it back? So let's hope they do and see if we can wait for a heroku-24 release that includes it before updating. heroku/base-images#324

See also https://www.reddit.com/r/Heroku/comments/1fj3cr4/ghostscript_on_heroku24/

If they don't, it looks like this custom buildpack would probably work (have done some initial but not thorough testing that looked good). https://github.com/thegrizzlylabs/heroku-buildpack-ghostscript

@jrochkind
Copy link
Contributor Author

ok ghostscript is on heroku-24 now, so we could resume this any time!

heroku/base-images#324 (comment)

@jrochkind
Copy link
Contributor Author

OK weird thing trying to deploy to heroku-24 stack --

error on deploy,

remote:        Running: rake assets:precompile
remote:        I, [2024-12-17T12:16:40.080300 #9904]  INFO -- honeybadger: ** [Honeybadger] Reporting error id=52144093-2c98-4b02-ac52-034b4657a615 level=1 pid=9904
remote:        rake aborted!
remote:        ArgumentError: Invalid Timezone: US/Eastern (ArgumentError)
remote:
remote:              ActiveSupport::TimeZone[time_zone] || raise(ArgumentError, "Invalid Timezone: #{time_zone}")

Code is the same (including same version of Rails) that deploys properly on Heroku-22.

TZ ENV var is actually set to America/New_York, not US/Eastern -- not sure where US/Eastern is coming from, maybe heroku-24 has other timezone variables set that Rails is using preferentially? Not finding anything on that.

May file a heroku ticket if I can't find anything soon. The inability to deploy makes it hard to investigate, as I don't have a working heroku-24 with our build stack to log into and look at!

@jrochkind
Copy link
Contributor Author

OK, we do have config.time_zone = "US/Eastern" in our config/application.rb.

Maybe that stops being a valid time zone on the ubuntu version in heroku-24? Let's try setting it to America/New_York -- or even actually take it from the ENV TZ if available!

@jrochkind
Copy link
Contributor Author

jrochkind commented Dec 17, 2024

OK, solved TZ. Now it's failing our system spec for making sure tesseract languages are installed.

Because:

~ $ tesseract --list-langs
List of available languages in "/app/.apt/usr/share/tesseract-ocr/4.00/tessdata/" (0):

It's supposed to actually list hte languages.

And there is nothing at /app/.apt/usr/share/tesseract-ocr/4.00/tessdata/.

Aha, we have an ENV var TESSDATA_PREFIX set to /app/.apt/usr/share/tesseract-ocr/4.00/tessdata. Clearly that needs to be something different on heroku-24...

Aha, we now have tesseract 5.x, so it needs to be: /app/.apt/usr/share/tesseract-ocr/5/tessdata/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1-2-days 1-2 day of developer time estimate
Projects
None yet
Development

No branches or pull requests

1 participant