Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SchemeSpec property failure #1790

Closed
rossabaker opened this issue Apr 16, 2018 · 1 comment
Closed

SchemeSpec property failure #1790

rossabaker opened this issue Apr 16, 2018 · 1 comment
Labels

Comments

@rossabaker
Copy link
Member

@rossabaker rossabaker commented Apr 16, 2018

[info] equals should
[info]   + be consistent with equalsIgnoreCase of the values (290 ms)
[info] compare should
[info]   + be consistent with value.compareToIgnoreCase (351 ms)
[info] hashCode should
[error]   ! be consistent with equality (411 ms)
[error]    org.specs2.execute.ErrorException: Exception raised on property evaluation.
[error]    > Exception: org.specs2.execute.ErrorException: org.http4s.ParseFailure: Exception raised on property evaluation.
[error]    > Exception: org.http4s.ParseFailure: Invalid scheme: Invalid input 'e', expected 's' or 'EOI' (line 1, column 5):
[error]    httpeg0reda0kxVhigkqxh+gA.u
[error]        ^
[error]    > caused by org.http4s.ParseFailure: Invalid scheme: Invalid input 'e', expected 's' or 'EOI' (line 1, column 5):
[error]    httpeg0reda0kxVhigkqxh+gA.u
[error]        ^ (file:1)
[error] CAUSED BY
[error]  org.http4s.ParseFailure: Invalid scheme: Invalid input 'e', expected 's' or 'EOI' (line 1, column 5):
[error]  httpeg0reda0kxVhigkqxh+gA.u
[error]      ^ (file:1)
@rossabaker rossabaker added the bug label Apr 16, 2018
@rossabaker
Copy link
Member Author

@rossabaker rossabaker commented Apr 16, 2018

Wow. I think after all this time, we stumbled into generating a scheme that starts with a known scheme.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant