Submitted patches

Page 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201  ...
Show: all, applied, pending, rejected
Patch Description Author Branch Submit Time Action Status Test Status
 ticket:1063 Fixed the Petascope configuration for the wcs-client. Summary: The wcs-client was being copied twice into the .war file as a result of an incorrect command in the Makefile. Test Plan: Manually tested the build process and the existence of the wcs-client in the rasdaman.war Reviewers: adumitru, dmisev Subscribers:   master   2015-11-17 10:11:10     APPLIED   SUCCESS 
 ticket:876 - Support PNG in WCS (add test cases)   master   2015-11-17 10:10:38     APPLIED   SUCCESS 
 ticket:1046 - start_rasdaman.sh messages (removed blank lines and redundant words)   master   2015-11-17 08:13:53     APPLIED   SUCCESS 
 ticket:1034 - crash testing of rasdaman Summary: This is a test suite for crash testing of rasdaman. The main goal is to catch potential database corruption in case of sudden server crashes, whether from internal causes (e.g. segfaults), or external factors like power outage. This can only occur in case of write queries, so it makes sense to only test create / insert / update and delete statements here. Test Plan: To run the test simply execute ./test.sh. Make sure RMANHOME is properly set to point to the rasdaman installation dir. The script establishes its own RASBASE in /tmp/rasdb, so original data is not touched. For this to work rasmgr.conf is updated (original config is restored at the end, but it is recommended to create a backup) and rasdaman is restarted automatically. Needless to say, never run this script on a production rasdaman. The test script tests rasql queries in the queries directory. To add a new query for testing copy the query.template into a new queryN.sh, which must have the functions already present, even if empty. First, all queries are executed in order to collect statistics and record checksums of the RASBASEs they generate (queries_metrics directory). This is later used to determine a random crash interval and compare database states in order to discover potential inconsistencies. Afterwards in an infinite loop: 1. a random query file is selected and loaded into test.sh 2. pre_query is executed to establish the data needed for the test query 3. run_query is executed in a background process; after a random amount of time has passed, the rasdaman server is killed with a SIGUSR1 signal 4. rasserver catches this signal, prints the stacktrace in the logs which could be useful in analysing bugs, and kills itself with a SIGKILL, in order to emulate a crash 5. rasdaman is restarted and RASBASE is compared to the expected state; in case they don't match, the logs and RASBASE are saved in bugs/bug.query_id.XXXXXXX 6. RASBASE is recreated clean for every query Reviewers: gmerticariu, mdumitru Reviewed By: mdumitru Subscribers: atoader, vmerticariu Differential Revision: http://codereview.rasdaman.org/D12   master   2015-11-16 17:02:42     APPLIED   SUCCESS 
 ticket:1061 - Implemented option No. 2 for handling client requests for an available server Summary: When an OpenDb request comes in from a client, rasmgr will try to find a suitable server for that client. In the previous version only one such attempt was made and if it failed the client the client received an error message. Now, when an OpenDb request comes from the client, rasmgr will attempt a fixed number of times to find a free server. Between each attempt, the client request will be put to sleep to allow rasmgr to manage the list of servers. Test Plan: Unit tests have already been implemented. Reviewers: dmisev, mdumitru, gmerticariu Differential Revision: http://codereview.rasdaman.org/D10   master   2015-11-16 12:38:35     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-15 18:57:38     REJECTED   FAILURE 
 ticket:1069 rasimport and wcst_import should not compile/install on --disable-java (also fix ticket 1068) Summary: I've fixed it in another system so it create a new topic. Test Plan: ./configure --disable-java and ./configure Reviewers: dmisev Reviewed By: dmisev Differential Revision: http://codereview.rasdaman.org/D11   master   2015-11-15 11:44:29     APPLIED   SUCCESS 
 ticket:999 - rasmgr.auth is now saved in CONFDIR as it was in the old rasmgr.   master   2015-11-15 08:23:20     APPLIED   SUCCESS 
 [PATCH] ticket:245 - fix insert/update distinction on client side   master   2015-11-13 13:30:28     PENDING   SUCCESS 
 [PATCH] ticket:1065 - Added the minimal dependencies for the wcs-client to the repo and updated the readme   master   2015-11-13 09:30:36     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.