Submitted patches

Page 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130  ...
Show: all, applied, pending, rejected
Patch Description Author Branch Submit Time Action Status Test Status
 [PATCH] ticket:1884 - Deserialize old coverage's metadate error as it is not XML/JSON   master   2018-10-08 10:56:20     PENDING   SUCCESS 
 [PATCH] ticket:1866 - WCPS enforce encode() if result is not scalar   master   2018-10-08 08:48:00     PENDING   SUCCESS 
 [PATCH] ticket:1881 - Delete coverage should not throw exception if its rasdaman collection was deleted manually   master   2018-10-08 08:46:06     PENDING   SUCCESS 
 [PATCH] ticket:1879 - Add test for importing coverage from tuple list in GML file   master   2018-10-08 08:44:23     PENDING   SUCCESS 
 [PATCH] ticket:1860 - WCST_Import should not analyse files if they were imported and added in track file (*.resume.json)   master   2018-10-04 13:16:15     PENDING   SUCCESS 
 [PATCH] ticket:1876 - WCST_Import checks coverage's exist from WCS GetCapabilities instead of WCS DescrobeCoverage to avoid exception in petascope's log   master   2018-10-04 08:59:27     PENDING   SUCCESS 
 [PATCH] ticket:1877 - remove support for $RASDATA   master   2018-09-20 15:59:42     PENDING   SUCCESS 
 [PATCH] ticket:1878 - fix transaction abort when commit fails   master   2018-09-07 15:59:59     PENDING   SUCCESS 
 [PATCH] ticket:1127 - templated systemtest for rasql + ticket:1874 - fix parallel transactions with sqlite backend and incorrect use of LFATAL log statements   master   2018-09-04 22:50:24     PENDING   SUCCESS 
 [PATCH] ticket:1872 - Petascope translate irregular coefficients to grid indices properly when coverage's origin is not the zero index in list of coefficients   master   2018-09-04 13:54:44     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.