-
Notifications
You must be signed in to change notification settings - Fork 81
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
Missing <op> in some cases #114
Comments
Job #114 is now in scope, role is |
Bug was reported, see §29: +15 points just awarded to @llorllale/z, total is +255 |
@rok-povsic/z this job was assigned to you 5 days ago. It will be taken away from you soon, unless you close it, see §8. Read this and this, please. |
@rok-povsic/z this job was assigned to you 8 days ago. It will be taken away from you soon, unless you close it, see §8. Read this and this, please. |
@yegor256 Please close the completed issue. |
@rok-povsic it's not mine |
@rok-povsic closed, thank you |
@llorllale Thank you. A new issue with the next puzzle has been open here. |
Order was successfully finished: +30 points just awarded to @rok-povsic/z, total is +90 |
@rok-povsic yes, I saw, thanks |
The job #114 is now out of scope |
@llorllale the puzzle #508 is still not solved. |
Some
<op>
are not being included in the skeleton.xml. For example, in the case of classBar
, notice howNAME
is not listed in the ops for methodgetKey
:The text was updated successfully, but these errors were encountered: