JasonTypesCodes opened a new pull request #1423:
URL: https://github.com/apache/groovy/pull/1423


   While putting together a Micronaut validation workflow based on the Grails 
one, I noticed that the Grails one wasn't functioning due to  
https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/
   
   I also noticed that in the event of pull requests, the workflow wasn't 
properly cloning grails-core, so I attempted to fix that too.
   
   It wasn't clear to me where this change should be applied, so I picked 
GROOVY_3_0_X.
   
   I ran this against a PR on my fork, and the workflow failed due to what 
appears to be a legitimate failure in building Grails 4.1.x:
   
   ```
   Caused by:
           groovy.lang.MissingMethodException: No signature of method: 
grails.spring.BeanBuilder$1.doCall() is applicable for argument types: 
(Script1$_run_closure1) values: [Script1$_run_closure1@111bc280]
           Possible solutions: call(), call([Ljava.lang.Object;), 
call(java.lang.Object), call([Ljava.lang.Object;), findAll(), 
equals(java.lang.Object)
               at 
org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:70)
               at 
org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.callCurrent(PogoMetaClassSite.java:80)
               at 
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:51)
               at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:171)
               at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
               at Script1.run(Script1.groovy:1)
               at groovy.lang.GroovyShell.evaluate(GroovyShell.java:501)
               at groovy.lang.GroovyShell.evaluate(GroovyShell.java:488)
               at grails.spring.BeanBuilder.loadBeans(BeanBuilder.java:480)
               ... 33 more
   ```


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to