Apologies - I resolved this issue with further investigation. What i needed was to use the extension Sequel.extension :named_timezones, and that seems to have resolved the issues.
There is the possible question of whether this behaviour is sufficiently expected/general for the extension to be included default / opt out within the sequel-rails gem, but i will leave that decision to those in charge, they probably know better. If you think the subject should be raised over in the Sequel-rails gem let me know and i will do that On Sunday, 2 May 2021 at 12:37:25 UTC+9 [email protected] wrote: > Hi, So i am currently trying to implement devise inside a rails project > running on sequel-rails, and i have run into an issue with the setting of > the DateTime object. > > I currently have an issue open in the Devise github for reference > https://github.com/heartcombo/devise/issues/5377 > > To describe the issue here devise sets the time for reset_password sent at > in the line : > > self.reset_password_sent_at = Time.now.utc > > The model then returns the time with UTC + 9 (my timezone) rather than UTC > and this then leads to an error when validating whether the > reset_password_token is still valid. > > I am reluctant to say what should be done here, it does seem that devise > is trying to pass the time zone and sequel is failing to store it, but > there may be some deeper convention i am missing. > > Any ideas on where to go with this? it could even be a sequel-rails issue, > or maybe something i have failed to implement on my end. > > (i just updated sequel-rails to make sure it wasnt an old error, so just > tested with sequel-rails v 1.1.1 and sequel v 5.44.0 and no change) > -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sequel-talk/c3d33881-f4b5-4141-9709-073ab74b2d17n%40googlegroups.com.
