Cormac McCarthy

@abhishek19994 Hey there, thanks for the contribution ☺️ In the future, I'll be looking for more examples of dynamic programming problems and how to solve them (including the corresponding code),...

@xK3v @riptusk331 @EPanni -- Hey folks, apologies that this issue is still affecting you; I attempted to reproduce this `bad interpreter` error with a few different images and command configurations,...

@joe-kimmel-vmw Hey Joe, thanks for the detailed response! For our specific case, our build stack is a "locked-down" (_i.e._, network restricted) image that pulls down binaries via a built-in command-line...

@natalieparellano Thanks for the detailed response as always, Natalie! Please find responses below: > re `Operation not permitted` - are you invoking the extender as root? For the information outlined...

@kilasuit Hey Ryan, thanks for the feedback 😀 we will need to have some internal discussions about how to properly implement this, and then roll out some experimental modules with...

@kilasuit Hey Ryan, we haven't made any progress on this item yet -- our focus since May has been on engineering tasks and preparing the new `Az` module built for...

@Tasin5541 Hey Miftaul, thanks for filing this issue -- just to clarify: the two sets of logs you've provided are both from executions of the `AzureStaticWebApp@0` task? I just want...

@kdhoermann Hey Kyle, apologies for the delayed response -- the image in the PR you linked above is an older LTS build image that contained the LTS versions of various...

@kjaymiller Hey Jay, thanks for the question -- the Oryx team actually chatted about this recently after we bumped the default version for a few other platforms (.NET, Go, Node,...

@sander110419 Hey there, apologies that you're facing this issue -- it appears that Azure Functions is using an older version of the Oryx build image which predates some changes we...