oss-fuzz/projects/croniter
Sean Gilligan 2aa8de903e
Croniter get_next fix (#10068)
Fix for an incorrect call to `get_next` that was stopping the Croniter
`fuzz_iter` executing, see
[https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=57139#c2](https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=57139#c2).

It was being called with a `datetime` object instead of a `datetime`
class as it's `ret_type` argument causing a type error. I've removed the
argument that's fixed it.

Also I've added the `undefined` sanitizer as it was missing from the
`project.yaml`. I've done a local run and it works fine with it enabled.
2023-04-12 19:55:49 +01:00
..
Dockerfile croniter: initial integration (#7753) 2022-06-08 10:39:30 +01:00
build.sh croniter: initial integration (#7753) 2022-06-08 10:39:30 +01:00
fuzz_iter.py Croniter get_next fix (#10068) 2023-04-12 19:55:49 +01:00
fuzz_match.py croniter: catch top-level exceptions (#9948) 2023-03-18 13:29:23 +00:00
fuzz_range.py croniter: catch top-level exceptions (#9948) 2023-03-18 13:29:23 +00:00
project.yaml Updating croniter project.yaml (#10041) 2023-04-11 12:41:28 -04:00