No, we need a stack trace. For all we know this is a duplicate of another bug or possibly a bug that is already fixed in 2.1.0.
No, we need a stack trace. For all we know this is a duplicate of another bug or possibly a bug that is already fixed in 2.1.0.