(magpie) branch feat/body-field-contract updated (d01234bb -> 20617cb0)

[po...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

potiuk pushed a change to branch feat/body-field-contract
in repository https://gitbox.apache.org/repos/asf/magpie.git


 discard d01234bb fix(local-tracker): a custom-layout tracker is read outside the sandbox
 discard b705384e fix(local-tracker): only the user can confirm a custom body parser
 discard d7113420 fix(local-tracker): report text cannot mix a file's line endings
 discard 05fcedc7 feat(setup, local-tracker): generate a local body-field parser for a detected report format
 discard 0b6e1c4d fix(local-tracker): read and write body fields through the parser on Git and Subversion storage
 discard 42a23e14 feat(body-field-contract): a Groovy implementation of the body-field contract
 discard fd1b0fac feat(body-field-contract): a normative body-field parser contract with a shared conformance suite
 discard 3fbb8893 fix(jira): keep the JVM on IPv4 loopback in the bridge tests
     add 0d9c168b fix(agent-isolation): show the macOS touch overlay even when activation is refused (#1697)
     add 46557d47 fix(jira): keep the JVM on IPv4 loopback in the bridge tests
     add c9764c52 feat(body-field-contract): a normative body-field parser contract with a shared conformance suite
     add 904ae30d feat(body-field-contract): a Groovy implementation of the body-field contract
     add dc300ed4 fix(local-tracker): read and write body fields through the parser on Git and Subversion storage
     add d614558f feat(setup, local-tracker): generate a local body-field parser for a detected report format
     add 54d9125a fix(local-tracker): report text cannot mix a file's line endings
     add 16be81b4 fix(local-tracker): only the user can confirm a custom body parser
     add 5fc1a08e fix(local-tracker): a custom-layout tracker is read outside the sandbox
     add 20617cb0 chore(rat): exempt the body-field conformance cases, which JSON Lines cannot annotate

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (d01234bb)
            \
             N -- N -- N   refs/heads/feat/body-field-contract (20617cb0)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

No new revisions were added by this update.

Summary of changes:
 .rat-excludes                                      |  5 ++
 .../setup/setup_preflight/isolated_fingerprint.py  |  2 +-
 .../gpg-touch-overlay-window-macos.py              | 55 ++++++++++++++++++++--
 .../tests/test_gpg_touch_overlay.py                | 43 +++++++++++++++++
 4 files changed, 101 insertions(+), 4 deletions(-)