openlmis-cce

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Sure, done.

Sure, done.

We should verify with the requisition service, but it doesn't mean we shouldn't add to all of them. Thanks for doing so - I'd suggest adding the same to the template service, as it's expected that ...

We should verify with the requisition service, but it doesn't mean we shouldn't add to all of them. Thanks for doing so - I'd suggest adding the same to the template service, as it's expected that all services have this switched on.

OLMIS-4531: Added compressing to HTTP POST responses

1. The ticket states that compression should be tested on initiating a requisition, that's why it is currently added only to the requisition service. 2. I think about disabling compression in nginx...

1. The ticket states that compression should be tested on initiating a requisition, that's why it is currently added only to the requisition service.
2. I think about disabling compression in nginx configuration.

Update raml2html to 3.0

To fix security vulnerabilities of nunjucks and minimatch.

Two questions: *Why was it only added to the requisition service? *It seems that for GET requests we will now be doing double compression (on the application server and on reverse proxy); any way...

Two questions:

  • Why was it only added to the requisition service?
  • It seems that for GET requests we will now be doing double compression (on the application server and on reverse proxy); any way to avoid that?
OLMIS-4531: Added compressing to HTTP POST responses
OLMIS-4531: Added compressing to HTTP POST responses
OLMIS-5841: Added tests to fix CCE build failing in sonar

Isn't this always true? rendering the subsequent lines to be a dead code?

Isn't this always true? rendering the subsequent lines to be a dead code?

OLMIS-5841: Fixed issue with internal server error when updating a catalog item with incorrect ID
OLMIS-5841: Fixed issue with internal server error when updating a catalog item with incorrect ID
OLMIS-5841: Fixed issue with internal server error when updating a catalog item with incorrect ID

Sure, I'm still working on that.

Sure, I'm still working on that.

Please add this to template service: https://github.com/OpenLMIS/openlmis-template-service/blob/master/build.gradle#L146
Unfortunately, it does so I reverted the changes and updated task for generating new migration.

Unfortunately, it does so I reverted the changes and updated task for generating new migration.

Updated task for generating migration to paste info about editing migrations

Revert "Added info about editing migrations"

This reverts commit c38878d51ec7cb44bc844e05fa738b3f64752f00.

    • -4
    • +0
    /src/main/resources/db/migration/20170810170921962__add_decommission_date_and_rtm_and_remove_serial_number.sql
    • -4
    • +0
    /src/main/resources/db/migration/20171114101548905__add_index_for_facilityId_and_programId_fields_in_inventory_item.sql
Hopefully comments do not modify the checksum, but yes - worth checking

Hopefully comments do not modify the checksum, but yes - worth checking

From what I know if a migration that has been applied to a database and it was changed the flyway will throw an exception (about incorrect code or something like that). Could we verify that those c...

From what I know if a migration that has been applied to a database and it was changed the flyway will throw an exception (about incorrect code or something like that). Could we verify that those comments will not break anything?

Added info about editing migrations
Added info about editing migrations
Added info about editing migrations

    • -0
    • +4
    /src/main/resources/db/migration/20170810170921962__add_decommission_date_and_rtm_and_remove_serial_number.sql
    • -0
    • +4
    /src/main/resources/db/migration/20171114101548905__add_index_for_facilityId_and_programId_fields_in_inventory_item.sql
OLMIS-4596: Shrinked demo data

    • -99962
    • +959
    /src/main/resources/db/demo-data/cce.cce_alerts.csv
I would keep the file because if I understand correctly if we would have problems with npm dependencies the file will help to resolve them.

I would keep the file because if I understand correctly if we would have problems with npm dependencies the file will help to resolve them.