I'd say check the "blame" button but then it says it was Chongsun... I know I added this block before the service was re-named. What was I thinking!? Ugh the textual hate I can convey in this text area widget!!!!
Couple questions: 1. if I'm using it correctly, I can't seem to trigger the errors through `gradle check`, `gradle pmdMain` or `gradle pmdIntegrationTest`. That is, I added duplicate imports and unused private fields and no errors popped up in `build/reports/pmd/` 2. does Klaudia now have access to Crucible?
Does transifex need to occur for Sonar to provide an analysis? It seems like we might be able to reduce some of the configuration if we didn't need to notify transfiex. Then we could add to the docker-compose.builder.yml instructions for interacting with our sonarqube server.
Looks great, thanks. I think we can close this one if we think no more needs to be added to the readme in terms of running sonar through docker compose?
You may want to consider sticking with Jackson as I believe that Spring Boot here is implicitly using it. It may make a difference if we start using Jackson Projections.
Looking great, couple questions: 1. should we incorporate nginx into the typical developer experience (here being developing one service), instead of a separate compose step? 2. We should probably add this to the service-template
Also FYI I forked/cloned this one to openlmis on github just so we have the code and know the license. We should likely establish this as a best practice.
Josh Zamor 1. Developing with nginx would require us to build deployment image each time a change is made, I think it's best to keep the dev environment as is 2. Sure, I'm gonna add it shortly
This is what I was thinking of when I asked if we could "integrate" it into the dev environment. It could be useful here as it's closer to production - security will also likely be done here (nginx) and might be applicable in development in a service. Let me know if this works for you and if you think it'd be a hindrance or a help. Thanks.
Josh Zamor Is there any way to start openlmis/dev and open service ports for nginx at the same time? I can't get the proxy running on port 80 when using config from the PR
Hi Jakub Kondrat, it works here but we're using Docker 1.12. In the PR, I changed the docker compose so that the nginx proxy was linked to the service. This creates a (fake) dependency which will bring up nginx, like it does postgres, when you run docker-compose run --service-ports requisition.
How does a non-OpenLMIS developer use this to build the service? It seems like we've made a presumption that a user will have credentials to get the translations since there is one combined process: push messages and pull new translations. I would think that to be good open source citizens, we'd need to support anyone building one of our services, regardless if they have Transifex credentials. To do this I think we'd need to:
state that our policy for all services is that the translations for all services (governed by us) are of an appropriate license and are publicly downloadable by anyone
the default/convention in the build process, should it not have credentials to transifex, is to only attempt the download of the latest translations
Unfortunately it appears that the Transifex client does not allow interacting with the Transifex server (including pulling of resources) without authentication credentials. So, how will others be able to access these resources?
I feel like we shouldn't be setting the response status here, but throw an exception and have the controller advice/exception handler return a correct status code.
I suppose we are interested in last period in the meaning of the endDate. Can we guarantee that the retrieved periods are sorted by the date and that the last element in the iterator is actually the latest one?
You are running release
CR4.8.5
FE4.8.5
(20201208124951 2020-12-08 12:52),
please report your release number when reporting bugs.