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

Azure Cosmos DB Emulator 2.1.2 #2662

Closed
IlyaFinkelshteyn opened this Issue Sep 28, 2018 · 4 comments

Comments

Projects
None yet
4 participants
@IlyaFinkelshteyn
Member

IlyaFinkelshteyn commented Sep 28, 2018

discussion

@IlyaFinkelshteyn IlyaFinkelshteyn added this to the next-images-update milestone Sep 28, 2018

@FeodorFitsner FeodorFitsner changed the title from Azure Cosmos DB Emulator 2.0.0 to Azure Cosmos DB Emulator 2.1.2 Nov 2, 2018

@john-raisingit

This comment has been minimized.

john-raisingit commented Nov 12, 2018

Is there a date for when this will be available?

@IlyaFinkelshteyn

This comment has been minimized.

Member

IlyaFinkelshteyn commented Nov 12, 2018

It should be already available, as part of recent update. We will close this issue later today.

@iscottb122

This comment has been minimized.

iscottb122 commented Nov 13, 2018

Apologies for jumping on the issue, but I can perhaps prevent others having to follow me down the same dark paths with dead ends ...

I think there may still be a problem with starting the emulator as installed on the image. I have a working build where I uninstall and reinstall the emulator as advised before attempting to start it. I can break it by making a minimal change which attempts to simply start the version already installed.

I can see that the uninstall step actually now removes two versions of the emulator, so my best guess would be that multiple installed versions do not play nicely together. This is also consistent with behaviour I have observed in other environments when old versions are not cleaned up properly. So completely removing version 1.20.108.4 from the image (if possible) may fix the problems.

Both of these builds (working, and broken after the minimal change) were run today, within a few minutes of each other. I have also run a number of other builds with different options whilst investigating, and I observe this behaviour consistently regardless of whether I use the emulator executable directly or the installed PowerShell module, other port numbers, etc.

@IlyaFinkelshteyn

This comment has been minimized.

Member

IlyaFinkelshteyn commented Nov 13, 2018

@iscottb122 thanks a lot for investigation, very helpful. We filed separate issue to track it: #2739

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment