Versions Compared

Old Version 1

changes.mady.by.user Danny Bernstein

Saved on

compared with

New Version Current

changes.mady.by.user Daniel Lamb

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Danny Bernstein
  2. Andrew Woods   
  3. Peter Winckles 
  4. Ben Pennell 
  5. Ben Cail 
  6. David Wilcox 
  7. Jared Whiklo 
  8.  Calvin Xu 
  9. Thomas Bernhart (star) 
  10. Daniel Lamb (star) 

Agenda

  1. Announcements/Updates
    1. Alpha !is  released as yesterday
    2. fcrepo-docker updates
    Alpha Release Logistics
  2. Release date: Monday, Nov 16th
  3. Top-level release documentation - Road to Fedora 6.0
  4. Focus this week: resolving documentation tickets:
    1. Jira
      serverLYRASIS JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyFCREPO-3459
    2. Jira
      serverLYRASIS JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyFCREPO-3512
    3. Jira
      serverLYRASIS JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyFCREPO-3513
  5. Upgrade bugs
    1. Jira
      serverLYRASIS JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyFCREPO-2983
    2. Jira
      serverLYRASIS JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyFCREPO-2985
    3. Jira
      serverLYRASIS JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyFCREPO-3521
    4. Jira
      serverLYRASIS JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyFCREPO-3522
    6. After documentation and before next Monday, review/merge following tickets (note, none of these are Alpha blockers. Documentation is the priority):
    Expand

    Jira
    serverLYRASIS JIRA
    jqlQueryfilter=13100
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5

  6. Fedora 6 Feature Tracking
    7. Expand
    titleFedora 6.0 open issues

    Jira
    serverLYRASIS JIRA
    jqlQueryfilter=15700
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5

  7. Transitioning away from Travis-CI
    1. Buildkite
    2. Circle-CI
    3. GitLab
    4. GitHub Actions

    5. https://semaphoreci.com/pricing

    6. https://www.appveyor.com/

  8. Transitioning away from DockerHub
    1. Amazon ECR
    2. Quay.io
    1. update
  10. Beta planning
    1. Prioritized Beta List
    2. What can we accomplish by the end of the December sprint?
  11. Cross database compatibility issues related to maximum field sizes, functions, index performance.
    1. Review the issue(s)
    2. Confirm the approach
  12. Transitioning away from Travis-CI
    1. Github Actions are ready to go on fcrepo/fcrepo
    2. Next steps?
  13. Transitioning away from DockerHub?
    1. Amazon ECR
    2. Quay.io
  14. Fedora 6 Feature Tracking

  15. Planned breaking changes

  16. Question related to postgresql on AWS

    1. Failed to truncate search index tables

      Expand

      Caused by: org.fcrepo.kernel.api.exception.RepositoryRuntimeException: Failed to truncate search index tables
       at org.fcrepo.search.impl.DbSearchIndexImpl.reset(DbSearchIndexImpl.java:467)
       at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
       at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
       at java.base/java.lang.reflect.Method.invoke(Method.java:566)
       at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
       at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:208)
       at com.sun.proxy.$Proxy47.reset(Unknown Source)
       at org.fcrepo.search.impl.SearchIndexMetrics.lambda$reset$3(SearchIndexMetrics.java:93)
       at io.micrometer.core.instrument.composite.CompositeTimer.record(CompositeTimer.java:79)
       at org.fcrepo.search.impl.SearchIndexMetrics.reset(SearchIndexMetrics.java:92)
       at org.fcrepo.persistence.ocfl.impl.ReindexService.reset(ReindexService.java:187)
       at org.fcrepo.persistence.ocfl.impl.IndexBuilderImpl.rebuild(IndexBuilderImpl.java:85)
       at org.fcrepo.persistence.ocfl.impl.IndexBuilderImpl.rebuildIfNecessary(IndexBuilderImpl.java:76)
       at org.fcrepo.persistence.ocfl.RepositoryInitializer.initialize(RepositoryInitializer.java:67)
       at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
       at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
       at java.base/java.lang.reflect.Method.invoke(Method.java:566)
       at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleElement.invoke(InitDestroyAnnotationBeanPostProcessor.java:389)
       at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleMetadata.invokeInitMethods(InitDestroyAnnotationBeanPostProcessor.java:333)
       at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:157)
       ... 56 common frames omitted
      Caused by: java.sql.BatchUpdateException: Batch entry 0 ALTER TABLE search_resource_rdf_type DISABLE TRIGGER ALL was aborted: ERROR: permission denied: "RI_ConstraintTrigger_c_16508" is a system trigger  Call getNextException to see other errors in the batch.
       at org.postgresql.jdbc.BatchResultHandler.handleCompletion(BatchResultHandler.java:199)
       at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:532)
       at org.postgresql.jdbc.PgStatement.internalExecuteBatch(PgStatement.java:870)
       at org.postgresql.jdbc.PgStatement.executeBatch(PgStatement.java:893)
       at com.mchange.v2.c3p0.impl.NewProxyStatement.executeBatch(NewProxyStatement.java:1013)
       at org.fcrepo.search.impl.DbSearchIndexImpl.reset(DbSearchIndexImpl.java:465)
       ... 77 common frames omitted
      Caused by: org.postgresql.util.PSQLException: ERROR: permission denied: "RI_ConstraintTrigger_c_16508" is a system trigger
       at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2553)
       at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2285)
       at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:521)
       ... 81 common frames omitted

    ...


Tickets

  1. In Review

    Expand

    Jira
    serverDuraSpace JIRA
    jqlQueryfilter=13100
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  2. Please squash a bug!

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13122
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  3. Tickets resolved this week:

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13111
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  4. Tickets created this week:

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13029
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


Notes

  1. Announcements

...

  • No anouncments

Planned Breaking Changes (standing topic)

  • No breaking changes to be discussed

Alpha Release Logistics

  • Alpha Release scheduled for Monday, 16th
  • Beta release, once feature completeness has been reached → ideally after next months sprint
  • Andrew Woods : Are there any tickets/PRs that need to be resolved/merged before Monday?
    • see also agenda item 3.e
    • Jira
      serverLYRASIS JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyFCREPO-3530
       
    • Jira
      serverLYRASIS JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyFCREPO-3523
  • Documentation
    • description of Alpha release features
    • overview of features which will be in the Beta release
      • might be possible to resolve
        Jira
        serverLYRASIS JIRA
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-3522
        (Migration of Fedora 5 repositories rooted at '/fcrepo' to Fedora 6") before Monday
    • discussion regarding breaking changes:
    • upgrading process is currently not straightforward → could be streamlined
  • Daniel Lamb : Doesn't expect any problems integrating Islandora with Fedora 6
  • David Wilcox : Trying to assemble a group of testers that would be willing to test integration of various Samvera applications with Fedora 6
    • ActiveFedora will not be migrated to Fedora 6
    • Valkyrie should be migrated to Fedora 6, but not all Samvera applications have been migrated to Valkyrie
    • testing will happen probably early next year with the beta release
    • migration scenario for Samvera is still unclear (migration-utils alone won't be enough)
  • Peter Winckles : Beta after next months sprint is probably optimistic; Andrew Woods agrees
  • Focus this week: resolving documentation tickets; links to artifacts will have to be added on Monday
  • Open tickets for Fedora 6:
    • some tickets will take a lot of time to resolve
  • Jira
    serverLYRASIS JIRA
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyFCREPO-3514
    should be resolved for Alpha

Transitioning away from Travis-CI

...


    1. Alpha is released. Many shout-outs to Jared, who is the alpha because of his magnificent mustache.
  2. Beta planning
    1. API Compatibility Test Suite: A lot of tests are failing not because the test suite is wrong, but because the Fedora instance that's being tested in misconfigured
  3. Cross database compatibility issues
    1. Don't do anything until we know what people want during beta
    2. Would cause a re-index if the 491 character limit to Fedora IDs were to be increased
    3. Most likely not neccessary, since it's a big limit and workaround are possible
  4. Github actions are ready to go and can be merged in
  5. Other dockerhub alternatives aren't free?
  6.  Skipped feature tracking
  7.  No new planned breaking changes
  8.  AWS Postgres seemingly has premissions issues with deleting tables
    1. May be a deal with foreign keys?

...

Actions

  •  Danny Bernstein to ensure that a JIRA exists for scenario of transaction does not succeed completely, but rollback does succeed (see: 2020-08-13- Fedora Tech Meeting)
  •  Peter Winckles to create a JIRA to investigate support for optimistic locking and mutable head (see: 2020-08-13- Fedora Tech Meeting)
  •  Who:  Clarify in documentation that multiple simultaneous writes to OCFL are not supported
  •  migration-utils - translating RELS-EXT/INT into RDF in Fedora 6: is the functionality there? If not, add it.
  •  Andrew Woods  will look into releasing jetty-console
    Jira
    serverLYRASIS JIRA
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyFCREPO-3530
  •  Peter Winckles will look into resolving
    Jira
    serverLYRASIS JIRA
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyFCREPO-3522
  •  David Wilcox will add remarks regarding Samvera beta testing to Road to Fedora 6.0
  •  Andrew Woods will look again at the upgrade documenation pages
  •  Danny Bernstein and Andrew Woods will go through open tickets and update priorities for Beta release