search

Azure / Azurite

A lightweight server clone of Azure Storage that simulates most of the commands supported by it with minimal dependencies
MIT License
1.8k stars 320 forks source link

Logic App Workflows w/ VS Code Never Start w/ version 3.17.X #1475

Open J-Cat opened 2 years ago

J-Cat commented 2 years ago

If using Azurite 3.17 or higher, when trying to debug Logic Apps in VS Code, the Logic App workflows never run. Everything works as expected with version 3.16 and lower.

blueww commented 2 years ago

@J-Cat

Would you please follow the issue teamplate, and give the information that needed to investigate this issue? The information should include:

  1. Azurite/Node/OS version
  2. How you start Azurite?
  3. Please clarity which service you use: table/blob/queue?
  4. Which request you send to Azurite? The expected responds, and actual Azurite responds.
  5. Azurite debug log.
mhous commented 2 years ago

@blueww

My peers and I are experiencing this issue as well, and have also confirmed that the breaking change occurred with v3.17. I did a side by side test with v3.16.0 and v3.18.0, starting with no Azurite state, and have attached a snippet of each of their debug log files that appear relevant.

To answer your questions:

  1. Azurite/Node/OS version Azurite: v3.16.0 and v3.18.0 Node: 16.16.0 OS: Windows 11, Version 21H2 (OS Build 22000.795)
  2. How you start Azurite? Clear previous storage from the PS commandline: rm __*.json Launch Azurite from the PS commandline: azurite -d azurite_version.debug.log
  3. Please clarity which service you use: table/blob/queue? Because this is being executed at the startup of the Azure Functions runtime hosting Logic Apps, it's hard to tell. It appears to be table.
  4. Which request you send to Azurite? The expected responds, and actual Azurite responds. See attached debug logs for comparison.

azurite_3.16.0.debug.log azurite_3.18.0.debug.log

blueww commented 2 years ago

@edwin-huber, @XiaoningLiu It looks the issue related with some table change between v3.16.0 and v3.17.0.

From the debug log, we can see: in 3.16.0, the "Table_MergeEntityWithMerge" operation success in 3.18.0, the "Table_MergeEntityWithMerge" operation failed with error "UpdateConditionNotSatisfied".

Would you please help to look if this is an expected failure?