v2.1.2 contains breaking changes.
BlackGlory opened this issue · 4 comments
BlackGlory commented
I don't have a clue about this, all my related test cases failed on 2.1.2.
In addition, v2.1.2 does not have a git tag, and 2.1.1 and 2.1.0 are also very confusing in the commits.
octet-stream commented
Hi! I think this may happen because of this: #85
You'll better stick with 2.1.1 until the next version is arrive...
octet-stream commented
I mean, this PR should fix the problem
jimmywarting commented
Do you know what is failing?
can you figure out what is breaking?
BlackGlory commented