typelevel / typelevel/cats-parse

investigate scalacheck failure 20231113

Open
#558 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Scala
Stars
245
Forks
51
Avg merge
3h 20m
Merged PRs (30d)
1

Description

was against: 79a414082fccb2e4db217712ae121d37494344a2

==> X cats.parse.ParserTest.oneOf0(as :+ unit) ~ b == (oneOf0(as).with1 ~ b) | (unit.with1 ~ b))  0.073s munit.FailException: /home/runner/work/cats-parse/cats-parse/core/shared/src/test/scala/cats/parse/ParserTest.scala:1043 notB = Set(WithContext(,Fail(0))) notA = Set(WithContext(,OneOfStr(0,List(뚈鰊))))
1042:              )
1043:              assert(
1044:                notStringOrCharB.subsetOf(notStringOrCharA),

Failing seed: Ngc1brL8Fnvq44FiBBGJQdIkuU2tE2zDn7pjJIo5QQN=
You can reproduce this failure by adding the following override to your suite:

  override def scalaCheckInitialSeed = "Ngc1brL8Fnvq44FiBBGJQdIkuU2tE2zDn7pjJIo5QQN="

Falsified after 38 passed tests.
> ARG_0: List("Map0(StringP0(WithContextP0(,Str(뚈鰊))),org.scalacheck.GenArities$$Lambda$10062/1263960136@11389892)", "Void(Prod(CharIn(84, bitSet = ..., NonEmptyList((T,T))),SoftProd(CharIn(54503, bitSet = ..., NonEmptyList((퓧,퓧))),CharIn(32, bitSet = ..., NonEmptyList(( , ))))))")
> ARG_1: Map(WithContextP(,Fail()),org.scalacheck.GenArities$$Lambda$10062/1263960136@37fbc952)
> ARG_2: ""

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with core/shared/src/test/scala/cats/parse/ParserTest.scala around lines 1042-1044 and reproduce the failure using the provided scalaCheckInitialSeed override. Investigate the failing oneOf0 property and its reported notStringOrCharA/notStringOrCharB values. Done means identifying the cause of the failed assertion and documenting or implementing the required fix.

Written by the indexing model from the issue text.

Assessment

Tech stack
scala
Domain
testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.