Forum Widgets
Latest Discussions
az mysql flexible-server command returns 'flexible-server' is not in 'az mysql' command group in WSL
I recently started scripting with Azure CLI within my Windows Subsystem for Linux (WSL) environment and tried to create a database on an Azure Database for MySQL Flexible-Server instance and received an error 'flexible-server' is not in the 'az mysql' command group. I also tried to list out the flexible-servers in my subscription, but it also give the same error! I tried to see if maybe my Azure CLI was out of date, but it was already at the newest version! As I test, I tried running the command in Microsoft's pre-package Azure CLI Docker container within my WSL Ubuntu environment: (You will need Docker Desktop installed) ~$ docker run -it mcr.microsoft.com/azure-cli Sure enough, it worked just fine! Something is wrong with my installation of Azure CLI within the WSL environment. It is a relatively new install, so possibly Azure CLI did not install completely when setting up WSL… Not matter, I found the instructions for reinstalling Azure CLI here… (https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-linux?pivots=apt) 1) Get packages needed for the install process: ~$ sudo apt-get update ~$ sudo apt-get install ca-certificates curl apt-transport-https lsb-release gnupg 2) Download and install the Microsoft signing key: ~$ curl -sL https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor | ~$ sudo tee /etc/apt/trusted.gpg.d/microsoft.gpg > /dev/null 3) Add the Azure CLI software repository: ~$ AZ_REPO=$(lsb_release -cs) ~$ echo"deb [arch=amd64] https://packages.microsoft.com/repos/azure-cli/ $AZ_REPOmain"| sudo tee /etc/apt/sources.list.d/azure-cli.list Note: This step did not work as expected in the WSL Ubuntu environment, lsb_release doesn't return any information, so you have to set AZ_REPO environment variable manually: ~$ cat /etc/*release Look for VERSION_CODENAME, or UBUNTU_CODENAME, which in our case is focal Now you can continue with the rest of the command ~$ AZ_REPO=focal ~$ echo"deb [arch=amd64] https://packages.microsoft.com/repos/azure-cli/ $AZ_REPOmain"| sudo tee /etc/apt/sources.list.d/azure-cli.list 4) Update repository information and install the azure-cli package: ~$ sudo apt-get update ~$ sudo apt-get install azure-cli The az mysql flexible-server module did not light up right away, I had to restart my Ubuntu WSL session. After that, it works fine!
Create Function App using arm template
Creating a function app in premium plan requires two app settings: WEBSITE_CONTENTAZUREFILECONNECTIONSTRING WEBSITE_CONTENTSHARE Based on the documentation App settings reference for Azure Functions | Microsoft Docs, When using an Azure Resource Manager template to create a function app during deployment, don't include WEBSITE_CONTENTSHARE in the template. However, including only WEBSITE_CONTENTAZUREFILECONNECTIONSTRING will cause the deployment error: "Required parameter WEBSITE_CONTENTSHARE is missing".
[Thread X] Problem auto-filling thread stack
Hi, First of all, sorry for my english! I am making a degree project in which I am using Thread X and It is my first time working with Azure RTOS. It took me a long time to understand how Thread X and Trace X worked. If I am not wrong, Thread X has a system thread called System Timer Thread that contains the "_tx_thread_priority_list" list whitin its stack. This list allocates the threads that are ready at a specific priority. Well, there is an option in Thread X which allows to check the stack size in run-time and it gets enabled with the flag "TX_ENABLE_STACK_CHECKING". However, within this option appears another one that specifies if you want to initialize the stack with constants values during a thread creation in order to check how many stack memory has been used. The problem is when the creation process calls "tx_thread_system_resume()" function and this one checks whether there already was an element in the corresponding entry of the "_tx_thread_priority_list". For that, it compares the value of that element with "TX_NULL" - that equals to 0. If we had the filling stack option enabled, we will be comparing a fake element - composed by 0xEF EF EF EF - whit 0, thus the comparison will be false provoking a Hard Fault, since we will be trying to access to an illegal memory position. The solution is simple: define TX_DISABLE_STACK_FILLING flag. Is this problem a bug? Or have I made a previous mistake? Regards, Óscar
