Today, if we have non notebook file in the container and we try to download the file, it fails. That is because, the filetype is always defined as notebook in the call to content provider's get method. Fixing it to use the right type in this change.
* Adds e2e baseline SQL test in puppeteer
* fix lint
* Skip index test
* add to ci
* Stop waiting for server
* Switch to headless mode
* Adds wait-for-server to package.json and uses it in puppeteer CI
* Adds waiton
* top level wait on
* Adds env var to secrets ci.yml
* use existing connection string
* redo tests
* nits and hopefully fix timeout issue
* Fix config file
* try waiting for delete container menu
* Removes statuseval
* Remove unused var
* Slow down and add quotes to selector
* Fix blocking point, remove wait
* Reduce to 50
* Adds database delete stuff
* remove logs, add back waitFors
* Finish container SQL spec test
ConfigContext defines all kinds of URLs and what not, I'm not
sure about the security implications of allowing all this stuff to
be modifiable by just anyone.
* Fix settings tab issue for cassandra and add feature flag
* Adding the rest of the changes....
Co-authored-by: Steve Faulkner <southpolesteve@gmail.com>
* Add support for no offers when serverless accounts
* Add workaround for ignoring failed /offers when using connection string
* Revert @azure/cosmos upgrade
* minro code edits
* Added support for acknowledging code of conduct
- Added CodeOfConduct component that shows links and a checkbox that must be acknwledged before seeing the public galley
- Added verbose message for notebook publish error (when another notebook with the same name exists in the gallery)
- Added a feature flag for enabling code of conduct acknowledgement
* Added Info Component
* minor edit
* fixed failign tests
* publish tab displayed only when code of conduct accepted
* added code of conduct fetch during publish
* fixed bug
* added test and addressed PR comments
* changed line endings
* added comment
* addressed PR comments
* 1) Updated mongo collection create pane to display a better error when a shard key is ill formed.
2) Updated an error message to use double quotes since no string interpolation is used. I thought it was included in a previoue PR but I guess the change didn't get staged.
