oryx | Oryx 2 : Lambda architecture

We are trying to deploy a rather simple flask app to azure app service. The deployment (using local git) fails with the following output:

I have two Azure accounts. And I tried to deploy the same function to these two accounts (to the function apps). The deployment to the 1st account - successful, but to the 2nd account - failed.

The only big difference between the two accounts is that I do not have direct access to the resource group that the 2nd account's function app uses (I have access to the resource group at the 1st account). May it be the reason why I can't deploy the program to the function app at the 2nd account?

Deploy output of the function app at the 1st account:

I have deployed to azure a create-react-app that has a server.js file for dynamically generating meta tags.

The stack is Node 16 on Linux

In my startup command I have pm2 start /home/site/wwwroot/server.js --no-daemon

My server.js is as follows

I'm trying to read and save a 12bit Raw file using Python and openCV. The code I'm using saves an image but the saved image is garbled / distorted.

The image is from a FLIR Oryx Camera 23MP (5320x4600) 12Bit with BayerRG12P pixelformat, which should be RG GB bayer pattern.

I build React App and deploy it to Linux Plan at Azure App Service.

I have 2 versions of service at 2 different Service Plans.

After some changes at code, I tried to deploy it to one of the Plans and it can't start/

Locally it works normally.

But at the server I got this message ":( Application Error";

I deploy application by Visual Studio Code but got same problem with Github Actions.

At log files, I found this

Cound not find build manifest file at '/home/site/wwwroot/oryx-manifest.toml' Could not find operation ID in manifest. Generating an operation id...

Looks strange, because on the second Service Plan I have this file and this version worked.

Second message on logs

npm start npm info it worked if it ends with ok npm info using npm@6.14.14 npm info using node@v12.22.4 pm info lifecycle backup-resurge@0.1.0~prestart: backup-resurge@0.1.0 npm info lifecycle backup-resurge@0.1.0~start: backup-resurge@0.1.0

backup-resurge@0.1.0 start /home/site/wwwroot react-scripts start

/home/site/wwwroot/node_modules/.bin/../node/bin/node: 1: /home/site/wwwroot/node_modules/.bin/../node/bin/node: This: not found npm info lifecycle backup-resurge@0.1.0~start: Failed to exec start script npm ERR! code ELIFECYCLE npm ERR! syscall spawn npm ERR! file sh npm ERR! errno ENOENT npm ERR! backup-resurge@0.1.0 start: react-scripts start npm ERR! spawn ENOENT npm ERR! npm ERR! Failed at the backup-resurge@0.1.0 start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm timing npm Completed in 1606ms

But I think that's file exists

Does anyone know what I can try to solve this problem?

I have a laravel application on my azure webapp (linux). I am trying to run some php commands after deploying.

I am using Local Git to deploy to my azure's webapp.

and as per this guide, i set the "POST_BUILD_SCRIPT_PATH" to run a script named "postbuild.sh"

(Note that i am using a .sh file since i am in a Linux based webapp. )

The problem is my postbuild.sh location is in "wwwroot" (where my laravel root application is). but i keep getting the

Could not open input file: artisan

message when i try to run any artisan command like

I try to deploy a Blazor Wasm application from my Azure DevOps repo to an Azure static web app. My app is based on the standard template, but is also using a Nuget package hosted in private feed in Azure Artifacts. I have tried several combinations of pipeline tasks but none seem to do the trick.

Attempt 1: The essentials

For all of my chromium based browsers, I'm getting a very bad font within Oryx for ErgoDox. If you're not familiar with the tool, you can see my keyboard layout here.

Update: I'm seeing in "Rendered Fonts" a strange font I don't recognize. Now I'm trying to work out how this is even happening, and why it's all my chromium browsers. See bottom photo below.

Update 2: The current theory is that my system is using the first "sans-serif" font it finds because of a syntax error in ErgoDox's CSS for the font-family; "Lato" should be enclosed in single quotes ' and it is not. This is causing my system to fall back to the first sans-serif font it finds, which is normally something more useful like "Arial", but is pix PixelFJVerdana12pt in my case. I've installed both "Lato" and "LatoLatin" and it is still rendering this awful font.

Update 3: Uninstalling "pix PixelFJVerdana12pt" fixed the issue ?? Now I'm looking into that font to figure out what the heck that even is? Now it renders Lato from the web? I'm putting an updated screenshot at the bottom with it fixed.

Here's what I've discovered and tried:

• The site uses "Lato,sans-serif;" for all its fonts - loaded from woff2/woff files hosted on their site.
• This problem exists for all of my chromium browsers: Chrome, Brave, Vivaldi, Edge.
• The site loads just fine in chromium (Chrome) for a friend of mine.
• The site loads just fine for me on my mobile phone.
• Extensive searching online yields no reports of anyone else having this issue.
• The site displays fine in Firefox.
• I've installed Lato to my machine directly from Google Fonts.
• I've downloaded the woff2/woff files from ErgoDox and opened them using a woff viewer online; they display correctly there.
• Reloading the site with cache disabled does not work.
• There are no console, or network errors (in developer tools).
• The only extensions I have installed in this instance of chromium are: 1Password, Adobe Acrobat and Application Launcher for Drive (Google).
• I run Windows Defender and Malwarebytes Enterprise.

I highly suspect this issue is local to me, and not a more global issue.

Anyone else with this issue? Any suggestions?

Problem demonstration:

Weird rendered font:

After uninstalling "pix PixelFJVerdana12pt":

Out of the blue my App service (asp.net core app) is down and nothing helps (e.g. restarting). Not my field of knowledge I have to say. Few noticeable things:

• First it throwed 502.
• Cannot even access kudu (advanced tools) on https://.scm.azurewebsites.net/ (also 502)
• In Diagnose and solve problems and Web App Restarted I have found this:
• In Diagnose and solve problems and Web App Down I have found: