-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Liquibase - fix floatType for mariadb #9063
Conversation
Closing/Reopening lo launch tests |
@pvliss Nice catch! Thanks for the PR. |
@DanielFran Thanks for merging BTW, in the case you need some extra help for getting the spring boot 2.1.0 released I would be really happy to help out. Not sure what still needs to be done though |
@pvliss Actually it is only missing the fix for the 2 tests (https://jhipster.visualstudio.com/generator-jhipster/_build/results?buildId=1565):
And a final update for spring-cloud to Greenwich.RELEASE expected Jan 17th (https://github.com/spring-cloud/spring-cloud-release/milestones) |
@DanielFran Thanks. I actually submitted another PR #9065 that fixes the issue with elastic docker not launching but now it fails at the frontend tests. Also the Travis build failed and I do not think it is related to my change. If you could rerun it I would be obliged. Currently investigating the react-noi18n-es-ws-gradle-session. In my local tests it fails with a
It seems that it has been introduced in elastic 6.4.0(first commit link), hence upgrading jhipster to 6.4.3 to also match the one used by spring boot will probably solve this issue as well. Will create a PR for that too. |
@pvliss We needed to downgrade to Elasticsearch 6.2.2 (instead of 6.4.3) because spring-data-elasticsearch Lovelace-SR4 is targetting 6.2.2 |
Oh, I see. Weird though that this is somehow requested. Will investigate further, thanks |
@dancancro So it seems there are currently currently 2 clients available as explained in the docs and the REST client uses 6.4.x. Would you like me to investigate switching temporarily to the Jest client or is this something you do not want or tried already? |
Hmmm. I now see that a Jest client is already used. |
@pvliss I downgrade docker elasticsearch version, let see if it fix the current issue! |
We need to review the docker-compose file and compare with https://www.elastic.co/guide/en/elasticsearch/reference/6.2/docker.html Note: port is 9300 due to jest |
Regarding the webflux-mongodb, I have found the error in Judging from the title it could also fix the frontend test failures for react-noi18n-es-ws-gradle-session as well. Can you try merging this to the spring-boot_2.1.0 as well? |
I have already submitted PR #9065 that fixes the issue with elastic docker. if not merged then azure CI build will continue to fail at that point |
@DanielFran As I see the webflux-mongodb is server side only I will submit a PR that fixes this compilation problem as 84c9b06 seems to be huge and maybe better to handle when the branch is merged back to master. What do you think? |
@DanielFran It seems that |
Yes, but this is failing the build as the 6.2.4 is not available from what I understand at docker hub. |
@DanielFran With the PR #9074 everything has turned green for both Travis and Azure. So once #9074 is also merged then I think that spring_boot_2.1.0 is ready? |
Thank you so much @pvliss !! |
@jdubois Again thank you for creating such an awesome project and community!!! Glad to be able to help!!! |
Fixes #9061
Please make sure the below checklist is followed for Pull Requests.
Travis tests are green
Tests are added where necessary
Documentation is added/updated where necessary
Coding Rules & Commit Guidelines as per our CONTRIBUTING.md document are followed