Activity
From 05/07/2017 to 06/05/2017
06/05/2017
- 04:40 PM Bug #7196 (Resolved): MN.Delete should continue even though it can't find the local file
- Add the code to continue delete the system metadata when the exception happens.
- 02:00 PM Bug #7196: MN.Delete should continue even though it can't find the local file
- The error from the delete command (from Marco):
curl -i --cert ./urn_node_UIC.pem --key ./urn_node_UIC.key -X DELETE... - 01:58 PM Bug #7196: MN.Delete should continue even though it can't find the local file
- The list of guids which have the issue (provided by Marco):
urn:uuid:23b20980-648a-4c18-ad6f-21a981b9ad1f
urn:uuid:... - 03:35 PM Revision 10340 (metacat): In the delete method, if we got not MdcDocNotFound exception, we will continue to delete the system metadata.
- 01:34 PM Bug #7195 (Resolved): LDAP-based group authorization is failing
- It turned out that the authen token doesn't include any group information. So the access rules about the group permi...
06/02/2017
- 05:35 PM Revision 10338 (metacat): Add the code to add the ldap group information for the given user.
- 05:29 PM Revision 10336 (metacat): Add a new method to get all groups for a given user.
- 05:26 PM Revision 10334 (metacat): Make a debug statement clearer.
- 02:03 PM Bug #7199 (New): Upgrade postgresql jdbc jar file on Metacat
- Please see detail on this ticket:
https://redmine.dataone.org/issues/8104 - 10:30 AM Feature #7198 (New): Format solr engine description output
- The solr engine description information from DataONE has XSLT formatted output that includes a description of each fi...
05/31/2017
- 11:05 AM Feature #7197 (Resolved): Display the dc:source field from DCX metadata documents in the stylesheet
- 10:32 AM Revision 10331 (metacat): Display the dc:source field from dublin core metadata in the onedcx-common stylesheet
05/30/2017
- 01:32 PM Bug #7196 (Resolved): MN.Delete should continue even though it can't find the local file
- The MN.delete method stops and throws an exception when it can't find the local file. Somehow this scenario, which is...
- 12:39 PM Bug #7187: Set file names correctly when reading objects from Metacat
- It is in the 2.8.3 release.
05/26/2017
- 10:44 AM Bug #7195 (Resolved): LDAP-based group authorization is failing
- In calls to @MNRead.getSystemMetadata()@ where the user logged in is a member of a group, and the group is listed in ...
05/24/2017
- 05:13 PM Revision 10329 (metacat): Modified the query to find the previous version of the ore document in the publish method.
- 04:59 PM Revision 10328 (metacat): Add a new bug was fixed in 2.8.3
- 04:54 PM Bug #7194 (Resolved): MN.publish method can't generate a new ore document when the metadata is published
- The query for choosing the old version of the ore document is wrong. After I rewrote the query, it works.
- 04:53 PM Bug #7194 (Resolved): MN.publish method can't generate a new ore document when the metadata is published
- After publish a metadata object created from the R client, the package information was missing.
- 04:51 PM Bug #7193 (Resolved): MN.publish fails because of the mismatched checksum
- Added code to change the checksum. It works right now.
05/23/2017
- 03:56 PM Revision 10325 (metacat): Add the release node for 2.8.3
- 03:37 PM Bug #7188 (Resolved): MNodeService.replicate() is failing
- We use the DigestOutputStream to wrap the output stream which will write the bytes to disks. The checksum are compute...
- 03:34 PM Bug #7192 (Resolved): MN.update method doesn't check the checksum
- 03:32 PM Bug #7187 (Resolved): Set file names correctly when reading objects from Metacat
- Tested it and it worked.
05/22/2017
- 01:56 PM Revision 10323 (metacat): Change the test metacat deployment directory.
- 12:52 PM Revision 10321 (metacat): Fixed a bug that the eml object wasn't changed checksum but its content was modified in the publish method.
- 08:55 AM Bug #7193 (Resolved): MN.publish fails because of the mismatched checksum
- The MN.publish method will modify the eml document's content, but it doesn't compute the new checksum and only uses ...
- 08:50 AM Bug #7192 (In Progress): MN.update method doesn't check the checksum
- The the update and create method share the same mechanism to check the checksum.
- 08:49 AM Bug #7192 (Resolved): MN.update method doesn't check the checksum
- The MN.update doesn't check the checksum - it doesn't compute the checksum of the coming object and compare the compu...
05/20/2017
- 10:36 PM Revision 10318 (metacat): Make the checksum match during the create method.
- 10:12 PM Revision 10315 (metacat): Add the code to reget the object input stream after generating the system metadata. Otherwise, the checksum will be wrong.
- 10:01 PM Revision 10313 (metacat): Exclude the MockReplicationMNode class in the test method.
- 03:42 PM Revision 10311 (metacat): Add the script to update the version to 2.8.3
- 03:41 PM Revision 10310 (metacat): Add the script which update the db to 2.8.3.
05/19/2017
- 09:44 PM Revision 10302 (metacat): Add the script to update db.
- 09:41 PM Revision 10301 (metacat): Add the db upgrade from 2.8.1 to 2.8.2
05/18/2017
- 11:51 AM Revision 10300 (metacat): Add the code to remove the pid from the identifier table if the update method failed.
- 11:33 AM Revision 10298 (metacat): Add tests to test the miss-matched checkup in the update method.
05/17/2017
- 09:58 PM Revision 10296 (metacat): Reget the object inputstream in order to calculate the correct checksum.
- 08:45 PM Revision 10294 (metacat): Add the checksum as the parameter to the method write.
- 08:42 PM Revision 10292 (metacat): Add the code to computer the checksum.
- 08:39 PM Revision 10290 (metacat): Add the checksum parameter to the write method.
- 08:37 PM Revision 10288 (metacat): Move the checking if the checksum exists into the create method.
- 08:34 PM Revision 10286 (metacat): Add the checksum parameter to the method DocumentImple.write.
- 08:26 PM Revision 10284 (metacat): Add a method to test the miss-matched checksum for creating a metadata object.
- 03:37 PM Revision 10282 (metacat): Add a new test method to test the miss-matched checksum for the data object.
- 03:32 PM Revision 10280 (metacat): Add the checksum as a parameter to the method handleInsertOrUpdate.
- 03:26 PM Revision 10278 (metacat): Add the checksum parameter to the handleInsertorUpdate method.
- 03:15 PM Revision 10276 (metacat): Add the checksum parameter to the handleInsertAndUpdate method.
- 03:12 PM Revision 10274 (metacat): Change the signature of the method handleInsertAndUpdate.
- 03:06 PM Revision 10272 (metacat): Add code to check the check sum by the DigestOutputStream.
- 09:36 AM Revision 10270 (metacat): Removed the duplicated code to check the checksum in the replicate method since the method D1Node.create, which is called by the replicate method, has the mechanism.
05/16/2017
- 09:54 PM Revision 10268 (metacat): Revised the method for testing replication. It did nothing but does test the replication between the mock mn and the local host.
- 09:50 PM Revision 10266 (metacat): Add the replication source node into the node locator.
- 09:47 PM Revision 10264 (metacat): Add some methods to support the replicate.
- 09:14 PM Revision 10262 (metacat): Add a mock mn node as the source node during a replication operation.
- 02:23 PM Revision 10260 (metacat): Add a integration test.
- 02:22 PM Revision 10259 (metacat): Add two properties will be used in the dataone replication test.
- 04:10 AM Bug #7188: MNodeService.replicate() is failing
- The purpose of the checksum is to ensure integrity of content written to the data store. Computing a checksum enroute...
05/12/2017
- 12:17 PM Bug #7188: MNodeService.replicate() is failing
- It would be best if the stream only has to be read once to be serialized and have the checksum checked, so we don't i...
- 11:41 AM Bug #7188: MNodeService.replicate() is failing
- Chris and I discussed the issue today. We propose the solution this way:
1. Since MN.replicate and D1NodeService.cr...
05/11/2017
- 08:10 PM Bug #7188: MNodeService.replicate() is failing
- But from Chris' table, those failures have started recently (May, 2017). So I am confused.
Before releasing Metaca... - 06:12 PM Bug #7188: MNodeService.replicate() is failing
- Bummer that its been there a while. Such a hugely serious bug as this should have been caught by a test. I suggest ...
- 04:12 PM Bug #7188: MNodeService.replicate() is failing
- Rob confirmed that we have been use the AutoCloseInputStream a while ago. And Metacat has been use the d1_libclient_j...
- 04:09 PM Bug #7188: MNodeService.replicate() is failing
- I debug the replicate method and found the class of input stream is org.apache.commons.io.input.AutoCloseInputStream....
- 07:19 AM Bug #7188 (Resolved): MNodeService.replicate() is failing
- Laura Moyers reported that she is seeing many failed replication attempts in the Coordinating Node index. In particu...
- 10:43 AM Revision 10249 (metacat): Add some debug information.
05/10/2017
- 08:15 AM Bug #7187 (In Progress): Set file names correctly when reading objects from Metacat
- I've modified @generateOutputName@ to use @SystemMetadata.fileName@ when it's available. We'll need to test this in a...
- 08:05 AM Bug #7187 (Resolved): Set file names correctly when reading objects from Metacat
- We now store file names in @SystemMetadata.fileName@. In @MetacatHandler.readFromMetacat()@, we are currently genera...
- 08:12 AM Revision 10247 (metacat): Change MetacatHandler.generateOutputName() to use the SystemMetadata.fileName value when it is available. Needs testing.
- refs https://projects.ecoinformatics.org/ecoinfo/issues/7187
05/08/2017
Also available in: Atom