Context Navigation

Submitted patches

Page 1 ...
Show: all, applied, pending, rejected

Patch Description	Branch	Submit Time	Status	Test Status
[PATCH] ticket:2585 - FIX invalid shell syntax in secore Makefile	release_10.0	2022-04-21 12:20:42	PENDING	SUCCESS
[PATCH] ticket:2583 - FIX - wcst_import is killed with ctrl + c or pkill -f then it should add current updating file to resume.json file	release_10.0	2022-04-20 09:39:58	PENDING	SUCCESS
[PATCH] ticket:2578 - FIX - fix test web interfaces in system tests and ticket:2209 - test web interfaces in multiple threads and ticket:2579 - wcst_import checks if user can create resume file in folder containing ingredients file before analyzing files"	release_10.0	2022-04-20 03:05:07	PENDING	SUCCESS
[PATCH] ticket:2581 - petascope - enhance parsing UCUM label from opengis.net	release_10.0	2022-04-19 06:48:14	PENDING	SUCCESS
[PATCH] ticket:2580 - wcst_import wrong error cannot create resume file	release_10.0	2022-04-19 05:41:05	PENDING	SUCCESS
[PATCH] ticket:2471 - FIX - SECORE embedded in petascope supports JSP	release_10.0	2022-04-13 09:47:12	PENDING	SUCCESS
[PATCH] ticket:2577 - FIX improve thread-safety in rasmgr	release_10.0	2022-04-12 14:32:00	PENDING	SUCCESS
[PATCH] ticket:2576 - FIX - wcst_import - get axes defined in COSMO CRS 101 properly	release_10.0	2022-04-12 08:35:38	PENDING	SUCCESS
[PATCH] ticket:2573 - FIX - petascope fixes some errors for WCS scale extent and SOAP requests	release_10.0	2022-04-11 13:11:09	PENDING	SUCCESS
[PATCH] ticket:2575 - FIX - petascope adds failed rasql queries with log counters	release_10.0	2022-04-11 13:09:09	PENDING	SUCCESS
[PATCH] ticket:2574 - FIX - configurable size of gdal datasets cache in wcst_import	release_10.0	2022-04-11 08:14:17	PENDING	SUCCESS
[PATCH] ticket:2572 - FIX automatically run pylint on wcst_import when building rasdaman	release_10.0	2022-04-06 19:14:26	PENDING	SUCCESS
[PATCH] ticket:2571 - FIX - wcst_import fixed attributes of objects not initialized before invoking	release_10.0	2022-04-06 11:02:09	PENDING	SUCCESS
[PATCH] ticket:2571 - wcst_import object has no attribute evaluator_slice	release_10.0	2022-04-06 07:14:22	PENDING	SUCCESS
[PATCH] ticket:2658 - FIX wcst_import to open each file with GDAL only once	release_10.0	2022-04-05 11:16:12	PENDING	SUCCESS
[PATCH] ticket:2569 - FIX - petascope - create indexes for database relationships in Hibernate and ticlet:2570 - FIX - wsclient not show	release_10.0	2022-04-05 06:29:36	PENDING	SUCCESS
[PATCH] ticket:2542 - FIX add a guide to the docs on how to migrate rasdaman to another machine	release_10.0	2022-04-04 15:39:53	PENDING	SUCCESS
[PATCH] ticket:2276 fixed json output for printiles=1 Summary: Fixed json ouptut, no more double "	master	2020-03-26 15:07:48	PENDING	SUCCESS
[PATCH] ticket:2200 - fix javadoc generation on centos	release_9.8	2019-12-13 09:53:14	PENDING	SUCCESS
[PATCH] ticket:1240 - Handle crsSet from WCPS query	feature_wcps2	2016-05-09 10:51:46	PENDING	SUCCESS
[PATCH] ticket:1243 - Parse identifier() expression	feature_wcps2	2016-05-04 09:05:07	PENDING	SUCCESS
[PATCH] ticket:1242 - 1245 Handle trimming expression	feature_wcps2	2016-03-31 08:54:23	PENDING	SUCCESS
[PATCH] ticket:406 - fix problem with omitting space in WCPS query.	feature_wcps2	2016-03-22 08:16:58	PENDING	SUCCESS
[PATCH] ticket:821 - Change range constructor in compliance with Rasql convention.	feature_wcps2	2016-03-17 13:54:23	PENDING	SUCCESS
[PATCH] ticket:1206 - Handle axis iterator trimming expression	feature_wcps2	2016-03-17 13:27:56	PENDING	SUCCESS
[PATCH] ticket:1221 - 1228, 1232 Fix problem with multiple opertion and NULL expression	feature_wcps2	2016-03-17 13:26:03	PENDING	SUCCESS
[PATCH] ticket:000 - Remove mistake .PATCH_ACCEPT/tmp when submiting	feature_wcps2	2016-03-17 09:28:36	PENDING
[PATCH] ticket:1229 - Allow space between 'nodata = 1, 2, 3, 4' in WCPS encoding.	feature_wcps2	2016-03-16 13:19:13	PENDING	SUCCESS
[PATCH] ticket:1202 - and 1204, 1211, 1213, 1217, 1226, 1235, 1241 WCPS1.5 fix problems with slicing and trimming interval.	feature_wcps2	2016-03-15 16:21:36	PENDING	SUCCESS
[PATCH] ticket:1208 - Content: change to WCPS1.5 in test wcps and update correct test cases for ticket 1208, 1210 and 1238, also remove all the unfixed test cases when waiting for other patch.	feature_wcps2	2016-03-15 10:33:23	PENDING
[PATCH] ticket:429 - disable checks for a local postgres, so that the rasdaman init script can work even with remote postgres databases (v8.5)	release_8.5	2014-10-02 13:29:47	PENDING	SUCCESS
[PATCH] ticket:584 - fix compile with bison 3	release_8.5	2014-06-12 11:38:38	PENDING
[PATCH] ticket:439 - Fix ows:descriptions when abstract or keywords are not stored in petascopedb.	release_8.5	2014-04-10 17:09:28	PENDING
[PATCH] ticket:417 - more robust blob reading	release_8.5	2014-04-05 15:18:36	PENDING
[PATCH] ticket:417 - fix tile cache leak in v8.5	release_8.5	2014-04-04 11:44:12	PENDING
[PATCH] ticket:618 - fix segfault in clientcomm 8.5	release_8.5	2014-02-09 12:38:46	PENDING
[PATCH] ticket:609 - Fix datatypes for mr and rgb test coverages.	release_8.5	2014-01-27 18:24:09	PENDING
[PATCH] ticket:605 - Fix cell bounds of mr and rgb.	release_8.5	2014-01-22 18:02:55	PENDING
[PATCH] ticket:109(EarthServer) for 8.5.1. Added the autogenerated wcpsLexer.java and wcpsParser.java to the patch. These files are generated by antlr from wcps.g Shouldn't this action be performed at build time?	release_8.5	2013-11-25 16:15:03	PENDING
[PATCH] ticket:439 - Do not ignore content of ps_descriptions for DescribeCoverage responses.	release_8.5	2013-11-21 17:55:34	PENDING
[PATCH] ticket:440 - Do not ignore UoMs for domain elements.	release_8.5	2013-11-21 13:06:44	PENDING
[PATCH] ticket:109 Earthserver for 8.5.1 - Added XQuery switch to WCPS & conditional evaluation for rasql CASE on top of 8.5	release_8.5	2013-11-19 22:13:42	PENDING

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.

Rasdaman Contributor Agreement v1.0

These terms apply to your contribution of materials to a product or project owned or managed by us ('project'), and set out the intellectual property rights you grant to us (rasdaman GmbH, Germany, see www.rasdaman.com) in the contributed materials. If this contribution is on behalf of a company, the term 'you' will also mean the company you identify below. If you agree to be bound by these terms, fill in the information requested below and provide your signature. Alternatively, when provided together with a submission of your contribution by email, you agree to be bound by the agreement as it can be downloaded from www.rasdaman.org and that no other terms potentially supplied with your submission in addition apply.

Read this agreement carefully before signing and/or submitting.

  1. The term 'contribution' means any source code, object code, patch, tool, sample, graphic, specification, manual, documentation, or any other material posted or submitted by you to a project.

  2. With respect to any worldwide copyrights, or copyright applications and registrations, in your contribution:

    2.1. you hereby assign to us joint ownership, and to the extent that such assignment is or becomes invalid, ineffective or unenforceable, you hereby grant to us a perpetual, irrevocable, non-exclusive, worldwide, no-charge, royalty-free, unrestricted license to exercise all rights under those copyrights. This includes, at our option, the right to sublicense these same rights to third parties through multiple levels of sublicensees or other licensing arrangements;

    2.2. you agree that each of us can do all things in relation to your contribution as if each of us were the sole owners, and if one of us makes a derivative work of your contribution, the one who makes the derivative work (or has it made) will be the sole owner of that derivative work;

    2.3. you agree that you will not assert any moral rights in your contribution against us, our licensees or transferees;

    2.4. you agree that we may register a copyright in your contribution and exercise all ownership rights associated with it; and

    2.5. you agree that neither of us has any duty to consult with, obtain the consent of, pay or render an accounting to the other for any use or distribution of your contribution.

  3. With respect to any patents you own, or that you can license without payment to any third party, you hereby grant to us a perpetual, irrevocable, non-exclusive, worldwide, no-charge, royalty-free license to:

    3.1. make, have made, use, sell, offer to sell, import, and otherwise transfer your contribution in whole or in part, alone or in combination with or included in any product, work or materials arising out of the project to which your contribution was submitted, and

    3.2. at our option, to sublicense these same rights to third parties through multiple levels of sublicensees or other licensing arrangements.

  4. Except as set out above, you keep all right, title, and interest in your contribution. The rights that you grant to us under these terms are effective on the date you first submitted a contribution to us, even if your submission took place before the date you sign these terms. Any contribution we make available under any license will also be made available under a suitable FSF (Free Software Foundation) or OSI (Open Source Initiative) approved license which we choose at our discretion.

  5. With respect to your contribution, you represent that:

    5.1. it is an original work and that you can legally grant the rights set out in these terms;

    5.2. it does not to the best of your knowledge violate any third party's copyrights, trademarks, patents, or other intellectual property rights; and

    5.3. you are authorized to sign this contract on behalf of your company (if identified below).

  6. These terms will be governed by the laws of Germany. Any choice of law rules will not apply.

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.