Came across this when looking in the logs on coop to test the PMS migration.
Every 10 minutes we get an entry like this
Job exception: 404 Not Found
/usr/local/lib/ruby/3.2.0/open-uri.rb:369:in `open_http'
/usr/local/lib/ruby/3.2.0/open-uri.rb:760:in `buffer_open'
/usr/local/lib/ruby/3.2.0/open-uri.rb:214:in `block in open_loop'
/usr/local/lib/ruby/3.2.0/open-uri.rb:212:in `catch'
/usr/local/lib/ruby/3.2.0/open-uri.rb:212:in `open_loop'
/usr/local/lib/ruby/3.2.0/open-uri.rb:153:in `open_uri'
/usr/local/lib/ruby/3.2.0/open-uri.rb:740:in `open'
/usr/local/lib/ruby/3.2.0/open-uri.rb:29:in `open'
/var/www/discourse/plugins/discourse-events/gems/3.2.2/gems/omnievent-icalendar-0.1.0.pre5lib/omnievent/strategies/icalendar.rb:69:in `ics_file'
/var/www/discourse/plugins/discourse-events/gems/3.2.2/gems/omnievent-icalendar-0.1.0.pre5/lib/omnievent/strategies/icalendar.rb:22:in `raw_events'
/var/www/discourse/plugins/discourse-events/gems/3.2.2/gems/omnievent-0.1.0.pre3/lib/omnievent/strategy.rb:162:in `list_events'
/var/www/discourse/plugins/discourse-events/gems/3.2.2/gems/omnievent-0.1.0.pre3/lib/omnievent/strategy.rb:144:in `request'
/var/www/discourse/plugins/discourse-events/gems/3.2.2/gems/omnievent-0.1.0.pre3/lib/omnievent.rb:62:in `list_events'
var/www/discourse/plugins/discourse-events/lib/discourse_events/import_manager.rb:23:in `import'
/var/www/discourse/plugins/discourse-events/lib/discourse_events/import_manager.rb:85:in `block in import_all_sources'
activerecord-7.0.7/lib/active_record/relation/delegation.rb:88:in `each'
activerecord-7.0.7/lib/active_record/relation/delegation.rb:88:in `each'
/var/www/discourse/plugins/discourse-events/lib/discourse_events/import_manager.rb:82:in `import_all_sources'
/var/www/discourse/plugins/discourse-events/app/jobs/discourse_events/scheduled/update_events.rb:9:in `execute
hostname coop-app
process_id 1252904
application_version 24feb20abc713d06106a480b0b4e2f20b3938360
current_db default
current_hostname coop.pavilion.tech
job Jobs::DiscourseEventsUpateEvents
problem_db default
time 6:27 pm
If this is an external problem in DiscourseEventsUpateEvents (sic) then it should at least tell us what the problem is using a nice exception handler.