Submitted patches

Page 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48  ...
Show: all, applied, pending, rejected
Patch Description Author Branch Submit Time Action Status Test Status
 [PATCH] ticket:2284 - FIX - wcst_import should not allow to import different geo CRSs of input files for gdal and ticket:2345 - FIX - wcst_import removes .resume.json file if the imported coverage does not exist anymore   release_10.0   2022-05-04 10:51:44     PENDING   SUCCESS 
 [PATCH] ticket:2423 - FIX - document clipping with WCPS examples   release_10.0   2022-05-04 10:45:42     PENDING   SUCCESS 
 [PATCH] ticket:2541 - FIX - add test to check rasadmin user can bypass allowed IP addresses for write requests and ticket:2591 - FIX- wcst_import should not print a warning if all paths were already imported   release_10.0   2022-05-04 06:22:19     PENDING   SUCCESS 
 [PATCH] ticket:2473 - FIX - SECORE should extract gml.tar.gz file only when size is different and ticket:2287 - FIX - WSclient updates coverage id in WCS DescribeCoverage tab"   release_10.0   2022-05-04 03:05:12     PENDING   SUCCESS 
 [PATCH] ticket:2590 - NEW - petascope supports WCPS shorthand version for crsTransform()   master   2022-05-03 04:43:52     PENDING   SUCCESS 
 [PATCH] ticket:2480 - FIX - test oap filters non-testing coverages in system test   release_10.0   2022-05-02 09:08:57     PENDING   SUCCESS 
 [PATCH] ticket:2566 - FIX - petascope enhance XML to String for WCS DescribeCoverage / GetCoverage requests   release_10.0   2022-05-02 05:13:15     PENDING   SUCCESS 
 [PATCH] ticket:2515 - FIX improve documentation   release_10.0   2022-04-29 07:22:19     PENDING   SUCCESS 
 [PATCH] ticket:2582 - FIX - petascope supports extra setting full_stacktraces in petascope.properties - ticket:2535 - wcst_import validates non-existing settings   release_10.0   2022-04-29 03:57:26     PENDING   SUCCESS 
 [PATCH] ticket:2589 - FIX - petascope - reduce number of active and idle connections for Tomcat JDBC   release_10.0   2022-04-27 09:15:55     PENDING   SUCCESS 

Submit a new patch

Select your locally generated patch file below for upload. Note that the patch can only be accepted if you agree to the Rasdaman Contribution Agreement by ticking the checkbox.

See How to submit patches for a step-by-step guide, in particular regarding the patch subject format. In order to ensure quick processing and to avoid rejection, you may want to make sure your patch adheres to the rasdaman code guide.


Select the code branch below to which you want to commit (help); if you are not sure what this means just leave the default (master).



I agree to the Rasdaman Contribution Agreement.