-
-
Notifications
You must be signed in to change notification settings - Fork 22
Description
Hello,
When I try to feed a Google Calendar Private ICS URL, specifically for a TickTick calendar that syncs with my Google account, it throws an error claiming that event_data is null.
I will say, I inspected the ICS, and there are multiple records in the ICS that do not include the description field, which is what I am trying to match off of. However, some of them do have description fields.
When I test on another ICS file where all records have description fields, it succeeds.
Does ical-filter-proxy require / anticipate the description field to properly function?
Here's the traceback:
Traceback (innermost first)
/app/lib/ical_filter_proxy/filter_rule.rb: in evaluate
event_data.include?(value)...
/app/lib/ical_filter_proxy/filter_rule.rb: in match_event?
negation ^ evaluate(event_data, values)...
/app/lib/ical_filter_proxy/calendar.rb: in block in filter_match?
filter_rules.empty? || filter_rules.all? { |rule| rule.match_event?(event) }...
/app/lib/ical_filter_proxy/calendar.rb: in all?
filter_rules.empty? || filter_rules.all? { |rule| rule.match_event?(event) }...
/app/lib/ical_filter_proxy/calendar.rb: in filter_match?
filter_rules.empty? || filter_rules.all? { |rule| rule.match_event?(event) }...
/app/lib/ical_filter_proxy/calendar.rb: in block in filtered_events
filter_match?(FilterableEventAdapter.new(e, timezone: timezone))...
/app/lib/ical_filter_proxy/calendar.rb: in select
original_ics.events.select do |e|...
/app/lib/ical_filter_proxy/calendar.rb: in filtered_events
original_ics.events.select do |e|...
/app/lib/ical_filter_proxy/calendar.rb: in filtered_calendar
filtered_events.each do |original_event|...
/app/lib/ical_filter_proxy/servers/rack_app.rb: in call
[200, { 'content-type' => 'text/calendar' }, [ical_calendar.filtered_calendar]]...
/usr/local/bundle/gems/rack-3.0.9.1/lib/rack/tempfile_reaper.rb: in call
_, _, body = response = @app.call(env)...
/usr/local/bundle/gems/rack-3.0.9.1/lib/rack/lint.rb: in response
@response = @app.call(@env)...
/usr/local/bundle/gems/rack-3.0.9.1/lib/rack/lint.rb: in call
Wrapper.new(@app, env).response...
/usr/local/bundle/gems/rack-3.0.9.1/lib/rack/show_exceptions.rb: in call
@app.call(env)...
/usr/local/bundle/gems/rack-3.0.9.1/lib/rack/common_logger.rb: in call
status, headers, body = response = @app.call(env)...
/usr/local/bundle/gems/rack-3.0.9.1/lib/rack/content_length.rb: in call
status, headers, body = response = @app.call(env)...
/usr/local/bundle/gems/rackup-0.2.3/lib/rackup/handler/webrick.rb: in service
status, headers, body = @app.call(env)...
/usr/local/bundle/gems/webrick-1.8.2/lib/webrick/httpserver.rb: in service
si.service(req, res)...
/usr/local/bundle/gems/webrick-1.8.2/lib/webrick/httpserver.rb: in run
server.service(req, res)...
/usr/local/bundle/gems/webrick-1.8.2/lib/webrick/server.rb: in block in start_thread
block ? block.call(sock) : run(sock)
Let me know if you need any more details. The ICS contains sensitive information, but here are some safe records from it as an example. Again, this is straight from Google Calendar's ICS.
UID:xxx
CREATED:20250304T183930Z
LAST-MODIFIED:20250306T161827Z
SEQUENCE:2
STATUS:CONFIRMED
SUMMARY:blah blah
TRANSP:OPAQUE
END:VEVENT
BEGIN:VEVENT
DTSTART;VALUE=DATE:20250305
DTSTAMP:20250307T020216Z
UID:xxx
CREATED:20250304T183929Z
LAST-MODIFIED:20250306T161827Z
SEQUENCE:1
STATUS:CONFIRMED
SUMMARY:blah blah 2
TRANSP:OPAQUE
END:VEVENT
BEGIN:VEVENT
DTSTART;VALUE=DATE:20250305
DTSTAMP:20250307T020216Z
UID:xxx
CREATED:20250304T183932Z
LAST-MODIFIED:20250306T161827Z
SEQUENCE:1
STATUS:CONFIRMED
SUMMARY:blah blah 3
TRANSP:OPAQUE
END:VEVENT
BEGIN:VEVENT
DTSTART;VALUE=DATE:20250310
DTSTAMP:20250307T020216Z
UID:xxx
CREATED:20250304T183937Z
LAST-MODIFIED:20250306T161827Z
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:blah blah 4
TRANSP:OPAQUE
END:VEVENT
BEGIN:VEVENT
DTSTART;VALUE=DATE:20250304
DTSTAMP:20250307T020216Z
UID:xxx
CREATED:20250304T183934Z
LAST-MODIFIED:20250306T161827Z
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Log time
TRANSP:OPAQUE
END:VEVENT
BEGIN:VEVENT
DTSTART;VALUE=DATE:20250305
DTSTAMP:20250307T020216Z
UID:xxx
CREATED:20250304T183933Z
LAST-MODIFIED:20250306T161827Z
SEQUENCE:1
STATUS:CONFIRMED
SUMMARY:blah blah 5
TRANSP:OPAQUE
END:VEVENT
BEGIN:VEVENT
DTSTART;VALUE=DATE:20250308
DTSTAMP:20250307T020216Z
UIDxxx
CREATED:20250304T183930Z