Closed AveshCSingh closed 11 years ago
I can't repro. I just tried editing Mallory's yo yo event and it saved just fine.
What were you editing?
-----Original Message----- From: AveshCSingh [mailto:reply@reply.github.com] Sent: Friday, April 20, 2012 1:45 PM To: MasterPie Subject: [BoredPrototype] Editing Events leads to Error (#38)
Editing an event leads to "Location invalid: Cannot be a duplicate event." Making a minor change to the Location field is a temporary fix, but we should check out a validations to see why this error occurs.
Reply to this email directly or view it on GitHub: https://github.com/ACMCMU/BoredPrototype/issues/38
Hmm I was editing A Variety of Step Performances when this occurred. It happened multiple times, though I also can't replicate it now.
Next time it happens I will try to pin down the specific circumstances
On Fri, Apr 20, 2012 at 1:54 PM, MasterPie < reply@reply.github.com
wrote:
I can't repro. I just tried editing Mallory's yo yo event and it saved just fine.
What were you editing?
-----Original Message----- From: AveshCSingh [mailto:reply@reply.github.com] Sent: Friday, April 20, 2012 1:45 PM To: MasterPie Subject: [BoredPrototype] Editing Events leads to Error (#38)
Editing an event leads to "Location invalid: Cannot be a duplicate event." Making a minor change to the Location field is a temporary fix, but we should check out a validations to see why this error occurs.
Reply to this email directly or view it on GitHub: https://github.com/ACMCMU/BoredPrototype/issues/38
Reply to this email directly or view it on GitHub: https://github.com/ACMCMU/BoredPrototype/issues/38#issuecomment-5249596
Do you know when you were editing it?
There was a time zone issue yesterday that I found in that the database was exporting all the Times correctly in EST but when you went to compare the current time with one of those times, the current time would be compared using UTC. Additionally, the times were being compared as strings, not as DateTime objects.
There might be some validation in there which checks for two events being in the same location at the same time, and if time wasn't being compared properly, this validation might have killed it for you (two events with same location were at different times, but time comparison saw them having the same time).
-----Original Message----- From: AveshCSingh [mailto:reply@reply.github.com] Sent: Friday, April 20, 2012 1:59 PM To: MasterPie Subject: Re: [BoredPrototype] Editing Events leads to Error (#38)
Hmm I was editing A Variety of Step Performances when this occurred. It happened multiple times, though I also can't replicate it now.
Next time it happens I will try to pin down the specific circumstances
On Fri, Apr 20, 2012 at 1:54 PM, MasterPie < reply@reply.github.com
wrote:
I can't repro. I just tried editing Mallory's yo yo event and it saved just fine.
What were you editing?
-----Original Message----- From: AveshCSingh [mailto:reply@reply.github.com] Sent: Friday, April 20, 2012 1:45 PM To: MasterPie Subject: [BoredPrototype] Editing Events leads to Error (#38)
Editing an event leads to "Location invalid: Cannot be a duplicate event." Making a minor change to the Location field is a temporary fix, but we should check out a validations to see why this error occurs.
Reply to this email directly or view it on GitHub: https://github.com/ACMCMU/BoredPrototype/issues/38
Reply to this email directly or view it on GitHub: https://github.com/ACMCMU/BoredPrototype/issues/38#issuecomment-524959 6
Reply to this email directly or view it on GitHub: https://github.com/ACMCMU/BoredPrototype/issues/38#issuecomment-5249687
It actually just occurred 15 minutes ago, so I do not think that is it.
On Fri, Apr 20, 2012 at 2:05 PM, MasterPie < reply@reply.github.com
wrote:
Do you know when you were editing it?
There was a time zone issue yesterday that I found in that the database was exporting all the Times correctly in EST but when you went to compare the current time with one of those times, the current time would be compared using UTC. Additionally, the times were being compared as strings, not as DateTime objects.
There might be some validation in there which checks for two events being in the same location at the same time, and if time wasn't being compared properly, this validation might have killed it for you (two events with same location were at different times, but time comparison saw them having the same time).
-----Original Message----- From: AveshCSingh [mailto:reply@reply.github.com] Sent: Friday, April 20, 2012 1:59 PM To: MasterPie Subject: Re: [BoredPrototype] Editing Events leads to Error (#38)
Hmm I was editing A Variety of Step Performances when this occurred. It happened multiple times, though I also can't replicate it now.
Next time it happens I will try to pin down the specific circumstances
On Fri, Apr 20, 2012 at 1:54 PM, MasterPie < reply@reply.github.com
wrote:
I can't repro. I just tried editing Mallory's yo yo event and it saved just fine.
What were you editing?
-----Original Message----- From: AveshCSingh [mailto:reply@reply.github.com] Sent: Friday, April 20, 2012 1:45 PM To: MasterPie Subject: [BoredPrototype] Editing Events leads to Error (#38)
Editing an event leads to "Location invalid: Cannot be a duplicate event." Making a minor change to the Location field is a temporary fix, but we should check out a validations to see why this error occurs.
Reply to this email directly or view it on GitHub: https://github.com/ACMCMU/BoredPrototype/issues/38
Reply to this email directly or view it on GitHub: https://github.com/ACMCMU/BoredPrototype/issues/38#issuecomment-524959 6
Reply to this email directly or view it on GitHub: https://github.com/ACMCMU/BoredPrototype/issues/38#issuecomment-5249687
Reply to this email directly or view it on GitHub: https://github.com/ACMCMU/BoredPrototype/issues/38#issuecomment-5249807
Checked validation, only throws this error in the event that location, start time AND end time are all the same - which should be correct.
Editing an event leads to "Location invalid: Cannot be a duplicate event." Making a minor change to the Location field is a temporary fix, but we should check out a validations to see why this error occurs.