Context Navigation

Submitted patches

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

Patch Description	Branch	Submit Time	Status	Test Status
ticket:000 - prepare for release v9.2.0	master	2015-11-26 11:52:20	APPLIED	SUCCESS
ticket:903 - add configuration files for easylogging and change log format Summary: I added two easylogging configuration files, log-client.conf and log-server.conf, and used them to replace the current inline configuration. Test Plan: All logs should have the format specified in the configuration files and the TRACE and DEBUG levels should be disabled by default. They can be enabled by modifying the configuration files from the <rasdaman_install>/etc directory and setting the ENABLED property to true. Reviewers: atoader, gmerticariu Subscribers: dmisev Differential Revision: http://codereview.rasdaman.org/D20	master	2015-11-25 23:04:20	APPLIED	SUCCESS
ticket:875 properties files get unduly modified by installation procedure. Accepted by Dimitar Misev (http://codereview.rasdaman.org/D22). Summary: I've added test script and test cases to test_services (and that means I deleted files in test_open/). But when I try to commit, it will also add these deleted files to commit so I had to use git soft reset to add all the files which I want to commit again (and it makes a new thread in "code review" - I don't know how to get over this problem. Test Plan: ./test.sh (in log4j.properties.new in test cases has added some new lines, it can work good even if one update new properties) Reviewers: dmisev Reviewed By: dmisev Differential Revision: http://codereview.rasdaman.org/D22	master	2015-11-25 12:30:29	APPLIED	SUCCESS
ticket:1045 - fix compilation with --enable-strict and --enable-debug Summary: Compilation is not working with --enable-strict and --enable-debug in the same time due to some unresolved warnings Test Plan: The compilation should work with --enable-strict and --enable-debug Reviewers: dmisev Differential Revision: http://codereview.rasdaman.org/D17	master	2015-11-24 23:17:15	APPLIED	SUCCESS
ticket:1078 - Fixed bug in the GetCoverage component of the WCS client. Summary: An error in the GetCoverageController caused the subset parameters to be ignored. Test Plan: Manually tested. Reviewers: mdumitru, bphamhuu Differential Revision: http://codereview.rasdaman.org/D26	master	2015-11-24 20:50:04	APPLIED	SUCCESS
ticket:1073 - divide tile files into subdirectories Summary: the new tile structuring uses two level nesting with subdirectories (details in the ticket). rasdaman supports both organizations (old and new); update_db.sh can be executed to migrate to the new directory structure. Test Plan: unit test -> cd relblobif/test && make check && ./test_filestorage; update_db.sh has been tested manually. Reviewers: vmerticariu, atoader, mdumitru Reviewed By: mdumitru Differential Revision: http://codereview.rasdaman.org/D24	master	2015-11-24 17:40:26	APPLIED	SUCCESS
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-24 13:34:38	APPLIED	SUCCESS
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
[PATCH] ticket:1074 - fix error when RASBASE is missing	master	2015-11-23 15:45:12	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.