| Summary: | During practice, parley ignores the block vocabulary options and asks me confidence 7 words two days in a row. | ||
|---|---|---|---|
| Product: | [Applications] parley | Reporter: | michaelweber |
| Component: | general | Assignee: | parley bug tracker <parley-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | grave | CC: | henkel.daniel, mdspam |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Mageia RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
michaelweber
2016-05-05 05:38:27 UTC
I can confirm this grave bug for version 16.08.3. The same vocabularies are asked again every time I start parley, not matter what level they are in. But all of them should be blocked for weeks or months as they are in high level. Other vocabularies are never asked until they drop to the unknown-level. This is because in recent versions of Parley, in addition to the 7 confidence levels there are 7 "pre-confidence" or "early learning" levels to go through. The blocking parameters only start to work once you get through the early learning stage. To be honest, this confused me at first as well, and I personally think that 7 early learning stages is too many. Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |