Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Attendees

General

Meetings

03/02

Sprint planning

03/03

  • Nianli
    • Yesterday: 
      • I was working on FCREPO-1371 - Getting issue details... STATUS
      • I deployed the war file on the same environment as report. 
      • I did see the errors as report at first time. But I don't have performance issue on federated files. Details I will put in JIRA comments. 
      • The interesting thing is the error gone after I turned the log to debug mode for fcrepo.log.http.api. 
    • Today:
      • I will continue working on this JIRA issue.
    • Help/Blocker: 
      • Please help on StreamingBaseHtmlProvider.java line 237, have error: Exception rendering #parse(views/common-metadata.vsl) at /views/node.vsl[line 37, column 13 ] . But use debug setting in logback.xml, error disappeared,
  • Yinlin
    • Yesterday: 
      • Work on FCREPO-1290 - Getting issue details... STATUS , add unit test casts
      • Check FCREPO-1373 - Getting issue details... STATUS  and post a new comment and wait for response.
    • Today: 
  • Jared
    • Yesterday:
      • Generated a vagrant machine for FCREPO-1377 - Getting issue details... STATUS  with the desired components, 
        • Not sure if awoods wants F4 pre-configured to index to Fuseki and/or Solr. So I am leaving it open till he confirms.
    • Today:
      • Working on FCREPO-1357 - Getting issue details... STATUS  now with the guidance of one acoburn

03/04

  • Nianli
    • Yesterday: 
      • Working on FCREPO-1371 - Getting issue details... STATUS , couldn't replicate the error. 
        • After talking with @scossu, found out that he has the errors with million records in repository. 
    • Today: 
      • Continue working one the same issue, will ingest much more files in repository and see what happened. 
    • Blocker: 
      • None. If I have, will ask around.
  • Yinlin
    • Yesterday: 
      • Work on FCREPO-1290 - Getting issue details... STATUS
        • Add unit test and submit PR-741. 
      • Check FCREPO-1382 - Getting issue details... STATUS  and post a new comment and am waiting for response.
    • Today:
      • Discuss with Andrew about JIRA tickets then continue working on it.
  • Jared
    • Created PR for FCREPO-1357 - Getting issue details... STATUS  
    • Waiting for some feedback from Andrew Woods on FCREPO-1377 - Getting issue details... STATUS  
    • Investigating FCREPO-1362 - Getting issue details... STATUS  could use some reference on the use of multi-value properties

03/05

  • Fedora Tech Call
  • Yinlin
  • Jared
    • Yesterday:
      • Finished configuring fcrepo-message-consumer on the vm for FCREPO-1377 - Getting issue details... STATUS
    • Today:
      • Trying to add a service script for Fuseki to allow machine restarts.

03/06

  • Nianli
    • Yesterday: 
      • I finished the final test on FCREPO-1371
      • Started the work on FCREPO-1376
    • Today:
      • Will try to finish FCREPO-1376 and start to look at other ticket. 
    • Blocker: 
      • I have some local work need to be done asap today, but I will make up some time tonight.
  • Yinlin
    • Yesterday: 
      • Work on FCREPO-1290 
      • Finish FCREPO-1373
      • Submit PR-743
    • Today: 
      • FCREPO-1290
        • It seems that my logic on the test case is fine as Andrew said in the meeting, however, my setup() is not enough, I reduced the nullpoint error yesterday but it seems other variable still need to have in setup(). 
        • I will try directly using the setup in ContentRdfContextTest.java and continue working on it.  
    • Blocker
      • My mac sometimes cannot build passed using mvn clean install. 
      • Spent half day on this issue but still can’t make it work. 
      • It was build fine time from time, my assumption was memory issue or underline OSX update. 
      • Post to IRC but seems no one have similar issues. 
      • My work around for this issue was using another Ubuntu to build. 
      • My department has agree to upgrade the memory so it should be fine then.

03/09

 

03/10

 

03/11

 

03/12

  • Fedora Tech Call

03/13

 

  • No labels