Context Navigation

Submitted patches

Page 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 ...
Show: all, applied, pending, rejected

Patch Description	Branch	Submit Time	Status	Test Status
ticket:1155 - Implemented functionality in the configuration manager which saves the state of rasmgr to a unique file if the configuration is not explicitly saved through the rascontrol save command. Summary: In the old implementation of rasmgr a user could update rasgmr.conf through the rascontrol save command. If a user modified the internal state of rasmgr through rascontrol, but forgot to explicitly save the configuration and stopped rasmgr, the configuration was saved to a unique file in the $RMANHOME/etc folder. The new implementation of rasmgr has been changed to support this functionality. Test Plan: 1. start rasdaman, make a modification through rascontrol, stop_rasdaman -- The expected result is that files containing the backed up data are created in $RMANHOME/etc 2. start rasdaman, make a modification through rascontrol, save, stop_rasdaman -- The expected result is that rasmgr.conf and rasmgr.auth are updated and no temporary files are created. Reviewers: gmerticariu, dmisev Differential Revision: http://codereview.rasdaman.org/D77	master	2016-01-18 16:21:31	APPLIED	SUCCESS
ticket:1148 - Added exception handler to surround methods that should not throw exceptions. Summary: Methods such as abortTA or closeDB were called in the destructor of some classes and they were throwing exceptions which caused the client application to terminate. Test Plan: Start rasdaman, iniate a long running transaction, kill rasmgr. Before applying the patch rasql would terminate while now it exits. Reviewers: dmisev, gmerticariu Differential Revision: http://codereview.rasdaman.org/D78	master	2016-01-18 16:20:03	APPLIED	SUCCESS
ticket:1128 - Testing wcst_import in system. Summary: Testing wcst_import in system with 4 cases (time series irregular, time series regular, map mosaic and wcs_extract). Test Plan: Go to systemtest/testcases_services/test_wcst_import and run test.sh Reviewers: dmisev, mdumitru Differential Revision: http://codereview.rasdaman.org/D60	master	2016-01-17 20:44:56	APPLIED	SUCCESS
[PATCH] ticket:1154 - Evaluation of null values is not safe in QtDomainOperation	master	2016-01-17 16:51:17	PENDING	SUCCESS
[PATCH] ticket:1151 - Installed signal handler for rasserver for the rasnet protocol	master	2016-01-16 22:28:55	PENDING	SUCCESS
ticket:1150 - rasmgr_x now uses the etc/log-rasmgr.conf configuration file so the log level is configurable at runtime. Summary: Until now rasmgr_x did not use a default log configuration which caused the log output to be extremely verbose. From now on, rasmgr_x will use the log configuration in etc/log-rasmgr.conf by default. If this file is missing, it will use a default, hardcoded configuration. Test Plan: Start rasdaman with the default configuration and check nohup.out for log statements. Only the log levels specified in the configuration file should appear in the output file. Reviewers: dmisev, gmerticariu Differential Revision: http://codereview.rasdaman.org/D75	master	2016-01-16 19:37:59	APPLIED	SUCCESS
[PATCH] ticket:1118 - Added easylogging, googlemock and googletest as third party dependencies and changed include headers in files that use them.	master	2016-01-16 12:34:57	PENDING	SUCCESS
[PATCH] ticket:1133 fixed validation error on update for coverages having more than 128 bands	master	2016-01-15 16:48:43	PENDING	SUCCESS
[PATCH] ticket:1042 - Updated peer management implementation in rasnet to respect the specification of the old protocol.	master	2016-01-15 13:52:08	PENDING	SUCCESS
[PATCH] ticket:1137 - Using wcst_import in petascope_insertdemo.sh (http://codereview.rasdaman.org/D65)	master	2016-01-14 14:23:38	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.