### Packages impacted by this PR
@azure/openai
### Issues associated with this PR
N/A
### Describe the problem that is addressed by this PR
This PR adds support for the following features in the
2023-12-01-preview API:
- Support for image generation using DALL-E v3 models which are now
deployable on Azure with new features such as revised prompts and larger
image sizes.
- Support for rich content filtering information for the input prompts
and for the completions
- Support for new features in chat completions such as tools
TODO:
- ~Add entries for the new features in the changelog~
- ~Document the breaking changes in the changelog~
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
N/A
### Are there test cases added in this PR? _(If not, why?)_
Yes
### Provide a list of related PRs _(if any)_
N/A
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [x] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
---------
Co-authored-by: Minh-Anh Phan <111523473+minhanh-phan@users.noreply.github.com>
***NO_CI***
The combination of `nyc` + `esm` is broken in latest versions of
NodeJS (https://github.com/istanbuljs/nyc/issues/1530#issuecomment-1773403365).
Since `esm` package is no longer actively maintained and its repo is archived,
it's less likely that the issue will be fixed soon.
This change switches to use another code coverage tool `c8` which is not
affected. `c8` respects `.nycrc` config files so those are not renamed.
***NO_CI***
- update engine.node to >=16.0.0 in package.json
- update @types/node version to ^16.0.0
- update dev-tool sample's MIN_SUPPORTED_NODE_VERSION to 16
- update eslint-plugin's rules and tests related to engine.node version
- remove TextEncoder and TextDecoder stubs as they are now on global object
- fix tests compiler error due to better typings in v16
- update some README files to not reference version like 14.x.x
- along with it, `@types/mocha` version to `^10.0.0`
- add `esm` dev dependency as they are used, but not explicitly list
- use dev-tool run command for test scripts as much as possible
- fix test issue caused by Mocha behavior change around test name
- move `import "chai/register-should"` to mocha -r command line option for core
http tests
***NO_CI***
- update `sinon` version to `^15.0.0`. The breaking changes does not
affect our usages.
- upgrade `@types/sinon` to `^10.0.0`. This reveals test issue where
mocked tokens are not compatible with `AccessToken`. This PR fixes the
tests too.
***NO_CI***
- string replace in package json: 12 => 14 for engines/node and for dependency @types/node
- eslint: update `json-engine-is-present` rule to 14.0.0 as LTS version
- identity: react to typing improvements for `readFile()`'s `options.encoding`
- trivial generated api.md file changes due to @types/node version bump
Recently the test resource deployment step for search live test pipeline can
take more than 40 minutes to finish, while the integration test step only takes
less than 10 minutes. We have contacted service team about deployment issue.
Still it is better to let the pipeline finish running than canceling the run after
all these time spent on test resource deployment.
Search Documents has already migrated to the new Core client and Core rest pipeline libraries, however, this introduced too many breaking changes. In order to minimize the braking changes, core-http-compat was created. This commit regenerates the client with the latest version of autorest, with the core-http-compat-mode flag set to true, and no longer depending on core-http.
* configureClientOptions core-v2
* configureClientOptions
* & Record<string, unknown>
* Replicate https://github.com/Azure/azure-sdk-for-js/pull/19920 for core-client-rest
* formatting
* Replicate https://github.com/Azure/azure-sdk-for-js/pull/19920 for core-client-rest
* format
* attestation test fixes
* format
* more format
* format
* more recorder.configureClientOptions
* migration guide
* more format
* mixed-reality update
* attestation simplification
* more fixes
* changelogs and gettingstarted docs
* format
* format
* changelog
* tables ci - test-proxy variable
* env.SAS_CONNECTION_STRING test fix
* sort imports
* Revert "Revert "[Search Documents] Migrating search-documents to the new recorder" (#20149)"
This reverts commit 5de8993c80.
* to avoid min-max issues - retaining how the setup was imported
* recordings
* fix test
* formatting
As discussed in #17076, we no longer have the need for the `docs` script in each of our packages. This PR removes this script and the related dev dependency on typedoc
This PR makes the following updates regarding the `nyc` dependency
- Update to v15 from v14 across all packages
- Updates to `@azure/monitor-opentelemetry-exporter` as it failed to run the tests with the updated nyc.
- Update the test scripts to use the js files in the dist-esm folder like all other packages instead of using the ts-node plugin.
- Update one of the tests for `@azure/monitor-opentelemetry-exporter` to use the right path for package.json file now that the tests are being run from the dist-esm folder.
Random set of live tests were triggered from this PR to ensure that nyc works as expected.
The failure for data-tables is an unrelated service side issue
Resolves#19232
## What
- Fix incorrect logic when suppressing chai's circular dependency warnings
- Move to the common dev-tool configuration where possible
## Why
This is a longstanding issue that we have, where an incorrect logic was copy-pasted to other places. I figured while cleaning this up that any package I touch can just convert over to the shared dev-tool configuration. Where I was unable
to do that, I just fixed this bug to avoid too many changes in one PR.
Fixes#14292Resolves#17818Resolves#17816Resolves#17815Resolves#17814Resolves#17813Resolves#17810
* Node doesn't support some samples for smoke test
* [search-documents] reprocessed samples with exp. generator
Co-authored-by: Will Temple <will@wtemple.net>
## What
- Update API Extractor to the latest version (currently 7.18.11)
- Regenerate all API reviews by building all the packages
## Why
This is something we keep bumping into. First, we needed to upgrade API Extractor to allow us to re-export directly from
`@opentelemetry/api`. Then, it looks like we needed this to upgrade TypeScript to 4.4.
We are way behind on this version, and it's time to upgrade.
## Callouts
How noisy is this?! Here's what's happening - somewhere around 7.9 I think API Extractor improved the way it detects name
collisions with predefined globals. Things like KeyType, Response, etc.
If there's a clash, the generated API markdown file will rename <Item> to <Item_2> to make the name collision explicit.
Talking to folks on the team, and the poor souls that will be doing API Review approvals, we agreed that doing the upgrade
in one fell swoop is the way to go.
Resolves#9410
* Remove leftover recordings whose tests had been deleted
* Move test secrets into file so we can suppress the file, instead of suppressing using the unstable hashes
* Update suppression list
* update to enable live testing in sovereign clouds for search
* Update search to enable live testing in sovereign clouds for multiple services
* update test-resources.json
* update recordedClient.ts
* Adding a note in the readme to release publicly
* rename `@azure/test-utils-recorder` to `@azure-tools/test-recorder`
* lock file
* delete recorder new file
* Increment package version after release of azure-search-documents
* Update dependency in perf test package
Co-authored-by: Sarangan Rajamanickam <sarajama@microsoft.com>
This PR adds missing changelog entries for the times we
- updated tracing dependencies to use the GA version of OpenTelemetry
- updated to target ES2017
Minh-Anh Phan
Deyaaeldeen Almahallawi
Jeremy Meng
Heidi Steen
Daniel Getu
Jeremy Meng
Ziheng Zhou(MSFT)
Azure SDK Bot
Jeff Fisher
Stevan Freeborn
Sarangan Rajamanickam
praveenkuttappan
Jonathan Cárdenas
Will Temple
Harsha Nalluru
Ramya Rao
Maor Leger
govardhan
Ben Broderick Phillips
ckairen
Daniel Rodríguez