Closed cwant closed 2 months ago
Thanks for flagging this, I think the solution would be to convert the Icalendar::Values::DateTime
into one of the permitted Date types. I'll look into it
Thanks! By the way, the timezone issues (Errors: Timezone not found and cannot be linked to a valid timezone
) turned out to be our fault (the provider). We have Americas/Toronto
in the input instead of Eastern Time (US & Canada)
. Americas/Toronto
isn't known by ActiveSupport::TimeZone::MAPPING
.
Describe the bug
I try to test ingestion with a source of type
Ical
, and I get:To Reproduce
Steps to reproduce the behavior (which work on my machine, hopefully yours too):
Ical
source = Source.last; source.test_results
to debug.Expected behavior
Hopefully not an error (I'm new to this so still figuring out what things are supposed to do).
Additional context
Working with
docker-compose
in development (rails version7.0.8.1
, ruby3.2.2
). The following change moves it further (the order here seems important, or else it has issues withDateTime
):I'm not sure if this is the way to go (or if this is a problem due to my set up), but the read in test events say
Errors: Timezone not found and cannot be linked to a valid timezone
when I do this, so I don't know if this is just a partial solution.Cheers, Chris