The GitHub Actions job "Code Style" on grails-core.git/perf/request-path-8.0.x 
has failed.
Run started by GitHub user codeconsole (triggered by codeconsole).

Head commit for run:
e972b2ca5fa1a2ad58d443c1380512af41911ce2 / Scott Murphy Heiberg 
<[email protected]>
Merge remote-tracking branch 'upstream/8.0.x' into perf/request-path-8.0.x

Upstream landed the mass-assignment hardening (#15947) and the clearMissing
work (#15950), both of which rewrote the DataBindingUtils methods this branch
had touched in "Cache the data binding collaborators and the databinding
whitelist lookup". The conflict is resolved in favour of upstream everywhere
the two overlap, so that the deny-by-default binding behaviour is exactly the
one upstream shipped.

Superseded by upstream and dropped from this branch:

* The whitelist include-list caching in getBindingIncludeList. Upstream's
  rewrite already caches the negative result behind a NO_BINDING_INCLUDE_LIST
  sentinel and resolves the runtime bindable names only on a cache miss, and it
  keys the cache on whether deny-by-default is enabled, which this branch's
  single cache could not express. The method is taken from upstream verbatim.

* The resolveBindingIncludeList helper. Upstream's getField / getPairedField /
  getStaticListFieldValue replace it and fix the same defect: the lookup no
  longer lets getDeclaredField throw for a class the AST transform never
  enhanced, so nothing is owed here any more. The helper also honoured only a
  whitelist declared on the class itself, whereas upstream deliberately walks
  the superclass chain, so DataBindingUtilsSpec now asserts that an inherited
  whitelist applies. Its test of the private include-list cache is dropped: the
  negative result is still covered through the public binding API, and upstream
  now keeps two caches rather than the one the test reached into.

Kept from this branch:

* The ContextBoundBeans cache of the data binding collaborators, which upstream
  does not touch.

* Resolving the GrailsApplication once per bind and passing it down. It now
  travels through a private bindObjectToDomainInstance overload which runs
  upstream's include normalisation, so the include.isEmpty() /
  NO_BINDABLE_PROPERTIES handling and the clearMissing && explicitInclude
  gating apply on every path, including bindToCollection.

Report URL: https://github.com/apache/grails-core/actions/runs/31899265566

With regards,
GitHub Actions via GitBox

Reply via email to