Daniel Hazelbaker

6.8. I might be able to try getting a backup of my production data dev environment up to latest git, but that would take a bit of time.

Isn't Lava run on the server where it should just have the single culture defined? How would something that runs on the server be affected by a browser's culture setting?...

oh wow. That would explain some random culture issues in chat that we could never figure out.

Confirmed on our installation. Also updated the steps to reproduce slightly.

Unfortunately I don't think this can be fixed. For a custom schedule, the schedule data is stored as an iCal string (which is long and cannot be parsed in SQL)....

Admittedly, I never tested this with PUT and PATCH specifically. I just included those verbs as a "why not". I wonder if IIS is internally trying to handle those rather...

Yes, I'll take a look and see if I can verify what the core issue is.

It looks like this is an issue at the web.config level. Or more specifically, at the "server" level web.config. The default handler mapping for `.ashx` files appears to only support...

It's not a **huge** issue, but the Lava Webhooks have their own Entity Command enabling, so they can use `{% sql %}` statements to make updates. We are actually doing...

The `Entity Set Property` action uses `Convert.ChangeType()` to do the conversion. Apparently, this method does not know how to convert a string to a Guid. For example, the below call...