Submitted patches

Page 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34  ...
Show: all, applied, pending, rejected
Patch Description Author Branch Submit Time Action Status Test Status
 ticket:000 - FIX - allow petascope to be able to build with java 17 and petascope should not initialize internal SECORE if secore_urls does not contain internal   release_10.2   2023-03-28 09:28:45     APPLIED   SUCCESS 
 [PATCH] ticket:000 - rename the duplicated coverage ids in test wcst_import   release_10.2   2023-03-27 08:38:20     PENDING   SUCCESS 
 [PATCH] ticket:2386 - support ceil, floor, and round functions in rasql; require C++17 for compilation   release_10.2   2023-03-24 14:48:57     PENDING   SUCCESS 
 [PATCH] ticket:2708 - FIX - execute_if setting to run hook after import failed in wcst_import   release_10.2   2023-03-23 09:34:31     PENDING   SUCCESS 
 [PATCH 1/2] ticket:2384 - FIX - supports ceil() and floor() operations in WCPS   release_10.2   2023-03-23 07:16:31     PENDING   SUCCESS 
 [PATCH] ticket:2706 - FIX - add documentation about modulo operation in WCPS cheatsheets   release_10.2   2023-03-22 11:07:17     PENDING   SUCCESS 
 [PATCH] ticket:000 - FIX update rasdapy3 version to 1.1.0 and fix failing cases in systemtest   release_10.2   2023-03-22 10:40:13     PENDING   SUCCESS 
 [PATCH] ticket:2707 - FIX - ticket:2707 - FIX - many requests to local SECORE EPSG/0/4326 when petascope starts and ticket:2703 - FIX - Enhance petascope to check which SECORE URLs are running   release_10.2   2023-03-22 08:09:21     PENDING   SUCCESS 
 [PATCH] ticket:2705 - FIX - rasj has error with NegativeArraySizeException: -1 for rasj.global.Debug.logPrefix   master   2023-03-15 06:40:23     PENDING   SUCCESS 
 [PATCH] ticket:2704 - FIX - wcst_import adds full file path for importing netCDF file via gdal   master   2023-03-14 07:55:06     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.