-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
DROOLS-5249: do not store DateTimeFormatter as free form line #2859
Conversation
jenkins execute full downstream build |
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.
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.
It looks to me like this follows the convention. Fix itself is good, but it could use some test coverage.
jenkins execute full downstream build |
Failed tests:
|
jenkins execute full downstream build |
jenkins execute full downstream build |
Failed tests:
|
jenkins execute full downstream build |
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.
Thanks for your changes!
Fine for me.
jenkins execute full downstream build |
2 similar comments
jenkins execute full downstream build |
jenkins execute full downstream build |
relaunched again, job timeout increased |
jenkins execute full downstream build |
2 similar comments
jenkins execute full downstream build |
jenkins execute full downstream build |
We have two kinds of date boiler plate code snippets. For: - java.util.Date: 'java.text.SimpleDateFormat sdf' - java.time.LocalDate: 'java.time.format.DateTimeFormatter dtf' If user set value either of 'Date' or 'LocalDate' field using 'Literal Value' guided editor action, the given date boiler plate is generated automatically behind the scene. This allows users to put in just value of date, e.g. "01-Jan-2000". User do not have to use parametric constructors, builders, parsers or factory methods. It is done behind the scene using 'sdf' or 'dtf' BoilerPlate. If users set value either of 'Date' ot 'LocalDate' field using 'Formula' guided editor action, is their responsibility to construct 'Date' or 'LocalDate' instance. For more details see https://issues.redhat.com/browse/DROOLS-5249
jenkins execute full downstream build |
Kudos, SonarCloud Quality Gate passed! 0 Bugs |
jenkins execute full downstream build |
jenkins execute full downstream build |
No failure but out of memory in downstream build. @Ginxo is this something known? |
@jomarko yes it is, it is related with archiving build results. |
@Ginxo so is it fine if I ask for merge? |
@jomarko the OOME problem is not related with this particular PR, so if you consider this should be merged please go ahead! |
@kiegroup/gatekeepers may I ask for merge? Downstream failed on OOME tracked as mentioned above https://github.com/kiegroup/drools/pull/2859#issuecomment-631310987. The OOME was logged after I grepped console log:
I think it is fine to merge. |
DROOLS-5249: do not store DateTimeFormatter as free form line
We have two kinds of date boiler plate code snippets. For:
If user set value either of 'Date' or 'LocalDate' field using 'Literal Value' guided editor action, the given date boiler plate is generated automatically behind the scene. This allows users to put in just value of date, e.g. "01-Jan-2000". User do not have to use parametric constructors, builders, parsers or factory methods. It is done behind the scene using 'sdf' or 'dtf' BoilerPlate.
If users set value either of 'Date' ot 'LocalDate' field using 'Formula' guided editor action, is their responsibility to construct 'Date' or 'LocalDate' instance.
For more details see https://issues.redhat.com/browse/DROOLS-5249