Tim

As the CWA project went into ramp-down mode, I don't expect this issue to be addressed anymore. I'm therefore closing this issue.

This issue is still reproducible under version 3.0, I'm still hoping for a fix in version 3.2 for this, as this should be an easy fix. I'll therefore leave this...

@dsarkar 1. Please change the label to "Fix 3.0". 2. I can confirm that this issue has been fixed in version 3.0. It can therefore be closed.

As the CWA project went into ramp-down mode, I don't expect any more new findings on the root cause of this issue. I'm therefore closing this issue.

I'll use this issue, as it doesn't seem necessary to open a new issue just for this. I also have some news reg. my participation in this project, you can...

I can confirm that this has been **fixed** with version 3.1, and I'm therefore closing this issue as completed.

This would have been an issue that I'd close now, but as @dsarkar wrote that the development team is looking into it, I'll leave it open for the time being.

This issue was opened more than 1 year ago and wasn't answered. The question itself is still valid, though. But, as the CWA project went into ramp-down mode, I'm not...

As the CWA project went into ramp-down mode, I don't expect this issue to be addressed anymore. I'm therefore closing this issue.

I suggest closing this issue, as the bug has been fixed in version 3.2.