-
Notifications
You must be signed in to change notification settings - Fork 312
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upsert merge and replace return 404 incorrectly when the entity does not exist #1565
Comments
A recent release of Azurite caused tests with upserts to fail due to Azure/Azurite#1565.
* Upgrade uvicorn * Pin version of Azurite due to bug in upsert A recent release of Azurite caused tests with upserts to fail due to Azure/Azurite#1565.
This also hit us today when running in CI. Guess we'll have to pin it to the last version until this is fixed. |
I also came across this issue after updating Azurite. |
@edwin-huber We have couple CI builds failing that depend on this. Would love to get an update. |
Changes have been merged via #1566, and will be made available with the next release. |
Is there a release date for this, or is there a nightly channel that we can get a release from? |
Looks like they release every two months or so. There's an alpha package you might try. I think |
This appears to be fixed in 3.19.0. Thanks @edwin-huber! |
Which service(blob, file, queue, table) does this issue concern?
table
Which version of the Azurite was used?
3.18.0
Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
VS Code extension
What's the Node.js version?
v16.13.0
What problem was encountered?
These sort of upsert operations returned 404 when the entity does not yet exist. This is wrong for upsert.
This problem did not occur in 3.17.1.
Steps to reproduce the issue?
I made this helper app to test a bunch of different variants of delete, update, and upsert.
This diff shows the output difference between the legacy storage emulator and v3.18.0
Have you found a mitigation/solution?
The text was updated successfully, but these errors were encountered: