-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Out of IncrementingUuidGenerator capacity #2925
Comments
The But from your stacktrace and log output it looks like you are running Cucumber multiple times. Once for each test case. Used in this way the From your stack trace it also looks like you are not using |
This I don't understand. The So it seems unlikely that this problem was introduced by a change in Cucumber. Have you been adding test cases and are now exceeding 256 cases? |
I confirm that
Alternatively, you may have a custom
The default Cucumber META-INF file contains both the Are you in one of these configuration ? The Changing the |
Hi, Same problem without configuring any custom UUID generator :
It doesn't happen with 7.0.0. |
@Piscenois looks like you are running into #2930. Can you try upgrading to 7.19.0 instead. |
I reproduced the issue with the following unit test in
The error is:
I think this will be solved by #2931 |
Thank you @mpkorstanje ! It works fine. 👍 |
👓 What did you see?
✅ What did you expect to see?
I would expect, that some other UUidGenerator would be used, if MAX_SESSION_ID from IncrementingUuidGenerator is out of capacity or the existing instances are reused
📦 Which tool/library version are you using?
io.cucumber, cucumber-junit, v7.19.0
org.seleniumhq.selenium, selenium-java, v.4.17.0
🔬 How could we reproduce it?
Not sure about steps to reproduce, any calls against an api should do the trick
📚 Any additional context?
Executions.txt
The text was updated successfully, but these errors were encountered: