View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0004149SOGoWeb Calendarpublic2017-04-20 10:302017-05-08 14:36
Reporterpennylane Assigned Toludovic  
PrioritynormalSeverityminorReproducibilitysometimes
Status resolvedResolutionfixed 
Platformx86_64OSFreeBSDOS Version10.3
Product Version3.2.1 
Fixed in Version3.2.9 
Summary0004149: Updated events accept fails
Description

Upon receiving an updated event invitation to a previously accepted event, SoGo shows "request failed" when the user tries to accept the updated invitation.

The only thing that shows up in the logs is
"POST /SOGo/so/username/Mail/0/folderINBOX/folder_U_follow_U_up/303/3/Untitled-3.ics/accept HTTP/1.1" 500 196/0 0.434 - - -

Steps To Reproduce

Sadly not always reproducible but mostly:

1) Receive event
2) Accept event
3) Receive update to event
4) Try to accept update -> "request failed"

TagsNo tags attached.

Activities

francis

francis

2017-04-20 10:37

administrator   ~0011734

Can you attach the raw source of the message or send it to me in private?

I suspect this bug to be already fixed by this commit:

https://github.com/inverse-inc/sogo/commit/ed3f7942260a35124e21a4396a6fd756de7ef060
pennylane

pennylane

2017-04-20 13:15

reporter   ~0011735

Would gladly provide the eml if you tell me how best to do that
ludovic

ludovic

2017-04-20 13:19

administrator   ~0011736

v3.2.1 is also quite old.

Try a nightly build if you want.
francis

francis

2017-04-20 13:21

administrator   ~0011737

Send it to me: flachapelle-at-inverse.ca
pennylane

pennylane

2017-04-20 13:45

reporter   ~0011738

@ludovic thanks for the advice, but running in production for quite a lot of users, I cannot just try a nightly build right away, if I'm not sure it's stable and will fix our issues.

If there's indication that a very recent build might fix our problem, I will gladly evaluate it in our testing environment!
francis

francis

2017-04-20 14:50

administrator   ~0011739

Updating to the latest nightly build (or the upcoming 3.2.9 release) will fix the problem.

Issue History

Date Modified Username Field Change
2017-04-20 10:30 pennylane New Issue
2017-04-20 10:37 francis Note Added: 0011734
2017-04-20 13:15 pennylane Note Added: 0011735
2017-04-20 13:19 ludovic Note Added: 0011736
2017-04-20 13:21 francis Note Added: 0011737
2017-04-20 13:45 pennylane Note Added: 0011738
2017-04-20 14:50 francis Note Added: 0011739
2017-04-20 15:00 ludovic Severity major => minor
2017-05-08 14:36 ludovic Status new => resolved
2017-05-08 14:36 ludovic Fixed in Version => 3.2.9
2017-05-08 14:36 ludovic Resolution open => fixed
2017-05-08 14:36 ludovic Assigned To => ludovic