Closed volodya-lombrozo closed 1 month ago
@maxonfjvipon Could you take a look please?
@volodya-lombrozo thanks for the report, here is a feedback:
I would recommend adding a 'Steps to Reproduce' section to help developers recreate the issue on their end.
Please fix the bug report in order it to get resolved faster.
Analyzed with gpt-4
@yegor256 Could you release a new version, please?
@rultor release, tag is 0.39.0
@rultor release, tag is
0.39.0
@yegor256 OK, I will release it now. Please check the progress here
@rultor release, tag is
0.39.0
@yegor256 Done! FYI, the full log is here (took me 14min)
@maxonfjvipon the problem in rultor was, as expected, in the size of the machine. Now, we are using AWS t2.xlarge and it all works.
@maxonfjvipon How can I use the new version?
@volodya-lombrozo just change the version in the pom.xml
. It doesn't work? Maybe it's better to report a new ticket, if it doesn't.
@yegor256 Yes, changing version helps. Thank you.
The current version of
eo-maven-plugin
allows to declare attributes without names in abstract objects.new-KClW
is an abstract object (as far as I know,) and theΦ.org.eolang.int
is its attribute without a name. When I runxmir
->phi
transformation, I don't see any errors, but I should. Attributes in abstract objects must have names.If we ignore this issue, we will face with such errors.
I use the fooling plugin configuration in the project: