-
Notifications
You must be signed in to change notification settings - Fork 52
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
Add number of suggest() attempts in Algo wrapper #883
Conversation
Signed-off-by: Fabrice Normandin <fabrice.normandin@gmail.com>
Signed-off-by: Fabrice Normandin <fabrice.normandin@gmail.com>
Hey @bouthilx there's a single test failing: Would you mind trying it on your end, whenever you have 5 mins, and letting me know if it also works on your end? |
This test seems to be randomly failed since a few weeks. I suspect it is failing for the same unknown reason in this PR which isn't related to your modifications. It would be great if we could fix it soon thought. |
) | ||
original = self.transformed_space.reverse(transformed_trial) | ||
if original in self.registry: | ||
max_suggest_attempts = 100 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be configurable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As a constructor argument to the wrapper? Or parameter to suggest
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Made it an attribute in 872f094, is this sufficient, you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the delay. It's a bit tricky here since at the constructor level it would add an argument specific for the wrapper, should I don't think should be exposed to the users since the define the algo configuration directly, they are not even aware that there is a wrapper. Same for suggest, it should follow the same interface as the algorithms it is wrapping. Maybe your solution is the best one for now and we can reassess later on if needed.
Signed-off-by: Fabrice Normandin <fabrice.normandin@gmail.com>
Signed-off-by: Fabrice Normandin <fabrice.normandin@gmail.com>
Signed-off-by: Fabrice Normandin <fabrice.normandin@gmail.com>
Signed-off-by: Fabrice Normandin <fabrice.normandin@gmail.com>
Signed-off-by: Fabrice Normandin <fabrice.normandin@gmail.com>
Signed-off-by: Fabrice Normandin <fabrice.normandin@gmail.com>
Signed-off-by: Fabrice Normandin <fabrice.normandin@gmail.com>
@bouthilx the Pickleddb backward-compatibility tests seem to be failing in CI for some reason? I don't really understand why though, would you mind taking a look? |
@bouthilx This is ready to merge on my end, would you mind taking a quick look? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All good, thanks!
Fixes #882 (at least I think it does)