search

themarshallproject / klaxon

Klaxon enables reporters and editors to monitor scores of sites on the web for newsworthy changes.
https://newsklaxon.org
MIT License
646 stars 199 forks source link

Application Error #556

Closed AlphonceWadenya closed 1 year ago

AlphonceWadenya commented 2 years ago

@GabeIsman @tommeagher

My goal is to log in to the Klaxon page. I followed ALL the steps up to getting my SendGrid account activated. But when I open the app, I get an Application error. Presently, the only errors I see from Papertrail and the Heroku CLI are "App crashed" and "DEPRECATION WARNING".

application_error

In response, I did a git clone of the app on Heroku and found that the repository was empty. Eventually, I forked the Marshall Project Klaxon GitHub repository. It still didn't open the klaxon page.

PaperTrail - https://pastebin.com/4WX80eSV

HerokuCli - https://pastebin.com/N6Lu36G1

On Saturday, June 11, I saw "Zeitwerk::NameError" and "failed to load command" on the Heroku cli. Find them below:

2022-06-11T06:41:22.124673+00:00 app[scheduler.4322]: DEPRECATION WARNING: Including LoggerSilence is deprecated and will be removed in Rails 6.1. Please use ActiveSupport::LoggerSilence instead (called from <top (required)> at /app/config/application.rb:16)

2022-06-11T07:00:20.026840+00:00 app[web.1]: [4] ! Unable to load application: Zeitwerk::NameError: expected file /app/app/lib/scrape.rb to define constant Scrape, but didn't

2022-06-11T07:00:20.026908+00:00 app[web.1]: bundler: failed to load command: puma (/app/vendor/bundle/ruby/2.7.0/bin/puma)

2022-06-11T07:00:20.027163+00:00 app[web.1]: /app/vendor/bundle/ruby/2.7.0/gems/zeitwerk-2.5.4/lib/zeitwerk/loader/callbacks.rb:25:in `on_file_autoloaded': expected file /app/app/lib/scrape.rb to define constant Scrape, but didn't (Zeitwerk::NameError)

After looking at " #build failed #537", I ran "heroku run rake db:create" and "heroku run bash ./postdeploy.sh" in an attempt to load the Klaxon page. And then I saw "User does not have CONNECT privilege" error.

But once again, the only errors I see now are the "App crashed" and "DEPRECATION WARNING".

immewnity commented 2 years ago

Is this occurring from the master branch or the develop branch? I'm seeing the issue in develop, but not master.

AlphonceWadenya commented 2 years ago

It did occur from the develop branch. I should've deployed from the master branch. Thank you for your time.

scowalt commented 2 years ago

I have this same error when deploying from the current master branch

GabeIsman commented 2 years ago

Sorry for the less-than-timely response, we're stretched pretty thin for maintenance on this project. I think this should be fixed as of just now on the develop branch now. Want to try that out?