Context Navigation

Submitted patches

Page 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 ...
Show: all, applied, pending, rejected

Patch Description	Branch	Submit Time	Status	Test Status
ticket:1076 - As per the GRPC recommendation I have implemented a HealthCheck to allow clients to detect if a server is up and running. Summary: A client must be able to detect if a server, identified by an address and running on the local machine or a remote one, is able to satisfy GRPC requests. This solution implements the recommented health check https://github.com/grpc/grpc/blob/master/doc/health-checking.md. Test Plan: Unit tests have been implemented for the service. Reviewers: mdumitru, dmisev, gmerticariu Differential Revision: http://codereview.rasdaman.org/D18	master	2015-11-23 19:43:50	REJECTED	FAILURE
ticket:1076 - As per the GRPC recommendation I have implemented a HealthCheck to allow clients to detect if a server is up and running. Summary: A client must be able to detect if a server, identified by an address and running on the local machine or a remote one, is able to satisfy GRPC requests. This solution implements the recommented health check https://github.com/grpc/grpc/blob/master/doc/health-checking.md. Test Plan: Unit tests have been implemented for the service. Reviewers: mdumitru, dmisev, gmerticariu Differential Revision: http://codereview.rasdaman.org/D18	master	2015-11-23 16:00:08	REJECTED	FAILURE
ticket:1074 - fix error when RASBASE is missing Summary: Error is wrong when rasdaman is configured with the sqlite database backend and database RASBASE is not created ("No such table: RAS_COUNTERS") Test Plan: Tested manually, the error now is "Base DBMS file not found at '/d/rasdata/RASBASE', please run create_db.sh first." Reviewers: gmerticariu Reviewed By: gmerticariu Differential Revision: http://codereview.rasdaman.org/D23	master	2015-11-23 15:45:12	APPLIED	SUCCESS
ticket:1064 wcst_import extract recipe fails when coverage is irregular and initial slice has all coefficient points (should be the first point), accepted by Alex Dumitru: http://codereview.rasdaman.org/D25 Summary: When coverage is irregular (it has multiple coeffecient points) and the first slice to initiate inside coverage should have only 1 point instead of all points, that will make coverage in local database full (can not add any slice after the first slice which follow by next coefficient from original irregular coverage) Test Plan: run wcst_import.py with wcs_extract recipe (coverage_id: "AvgLandtemp", "wcs_endpoint":"http://flanche.com:9090/rasdaman/ows") Reviewers: mdumitru Reviewed By: mdumitru Subscribers: vmerticariu Differential Revision: http://codereview.rasdaman.org/D25	master	2015-11-23 11:32:53	APPLIED	SUCCESS
ticket:1083 - revert secore EPSG database to v8.5	master	2015-11-20 17:50:53	APPLIED
ticket:1083 - update secore EPSG database to v8.7.5	master	2015-11-20 12:08:06	REJECTED	FAILURE
ticket:702 Postgis is installed but still not found (accepted by Dimitar: http://codereview.rasdaman.org/D21) Summary: I have tested with some version of PostGIS (2.0, 2.1.x) with PostgreSQL 9.1 and 8.4. There are a lot of trouble if just search postgis.sql and spatial.ref.sys.sql (in fact, it can be postgis-2.x.x.sql,...). So I've changed to a better idea to let user make sure postgis has been installed correctly (with PostgreSQL >= 9.1), keep the way to enable with PostgreSQL 8.4 (but user has to provide path to these files). Test Plan: update_petascopedb.sh --with-postgis Reviewers: dmisev Reviewed By: dmisev Differential Revision: http://codereview.rasdaman.org/D21	master	2015-11-19 11:58:40	APPLIED	SUCCESS
[PATCH] ticket:1075 - Removed bad easylogging configuration that caused rasql to segfault	master	2015-11-19 08:19:56	PENDING	SUCCESS
[PATCH] ticket:987 fixed metadata rollback on failed irregular coverage updates	master	2015-11-17 15:17:23	PENDING	SUCCESS
[PATCH] ticket:1063 Fixed the Petascope configuration for the wcs-client.	master	2015-11-17 10:11:10	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.

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.