You can workaround the bug by refreshing the page before replying for now :) It's caused by stale data

I think we will release the fix on Monday (when @k00b is back from TABconf)