Lock @azure/core-rest-pipeline to 1.16.0 #3066
Conversation
|
@BrandonStudio is attempting to deploy a commit to the LobeHub Pro Team on Vercel. A member of the Team first needs to authorize it. |
|
๐ @BrandonStudio Thank you for raising your pull request and contributing to our Community |
Codecov ReportAll modified and coverable lines are covered by tests โ
Additional details and impacted files@@ Coverage Diff @@
## main #3066 +/- ##
========================================
Coverage 93.43% 93.43%
========================================
Files 382 382
Lines 23629 23629
Branches 1718 2548 +830
========================================
Hits 22077 22077
Misses 1552 1552
Flags with carried forward coverage won't be shown. Click here to find out more. โ View full report in Codecov by Sentry. |
|
The latest updates on your projects. Learn more about Vercel for Git โ๏ธ
|
|
@BrandonStudio ๆต่ฏไธๆฏๅฆๅฏ็จ๏ผ |
@BrandonStudio Is it available for testing? |
|
Tested on GitHub Codespace |
|
โค๏ธ Great PR @BrandonStudio โค๏ธ The growth of project is inseparable from user feedback and contribution, thanks for your contribution! If you are interesting with the lobehub developer community, please join our discord and then dm @arvinxx or @canisminor1990. They will invite you to our private developer channel. We are talking about the lobe-chat development or sharing ai newsletter around the world. |
### [Version 1.1.15](v1.1.14...v1.1.15) <sup>Released on **2024-06-28**</sup> #### ๐ Bug Fixes - **misc**: Pin `@azure/core-rest-pipeline@1.16.0` to fix azure openai issue. <br/> <details> <summary><kbd>Improvements and Fixes</kbd></summary> #### What's fixed * **misc**: Pin `@azure/core-rest-pipeline@1.16.0` to fix azure openai issue, closes [#3066](#3066) ([f3b29f6](f3b29f6)) </details> <div align="right"> [](#readme-top) </div>
|
๐ This PR is included in version 1.1.15 ๐ The release is available on: Your semantic-release bot ๐ฆ๐ |
### [Version 1.44.10](v1.44.9...v1.44.10) <sup>Released on **2024-06-28**</sup> #### ๐ Bug Fixes - **misc**: Pin `@azure/core-rest-pipeline@1.16.0` to fix azure openai issue. <br/> <details> <summary><kbd>Improvements and Fixes</kbd></summary> #### What's fixed * **misc**: Pin `@azure/core-rest-pipeline@1.16.0` to fix azure openai issue, closes [lobehub#3066](https://github.com/bentwnghk/lobe-chat/issues/3066) ([f3b29f6](f3b29f6)) </details> <div align="right"> [](#readme-top) </div>
|
@arvinxx ไนๅไธๆฏdocker้จ็ฝฒไน็จไธไบๅ๏ผdockerๅ ้้ขไนๆฏedge runtimeๅ๏ผ |
|
@BrandonStudio ๆฏ็ใๅฆๆไปฃ็ ้้
็ฝฎไบ |
@BrandonStudio Yes. If |
### [Version 1.1.15](lobehub/lobe-chat@v1.1.14...v1.1.15) <sup>Released on **2024-06-28**</sup> #### ๐ Bug Fixes - **misc**: Pin `@azure/core-rest-pipeline@1.16.0` to fix azure openai issue. <br/> <details> <summary><kbd>Improvements and Fixes</kbd></summary> #### What's fixed * **misc**: Pin `@azure/core-rest-pipeline@1.16.0` to fix azure openai issue, closes [lobehub#3066](lobehub#3066) ([f3b29f6](lobehub@f3b29f6)) </details> <div align="right"> [](#readme-top) </div>
|
@arvinxx dockerๅ ้ๆฏไธๆฏๆฒกๆๅฟ ่ฆ็จedgeๅ๏ผๆไปฌ่ฆไธ่ฆ่่ๅจๆๅ docker็ๆถๅๅๆถedge่ฟ่กๆถ๏ผๅ จ้จๅจnode้่ฟ่ก๏ผ |
@arvinxx Is it unnecessary to use edge in the docker package? Should we consider canceling the edge runtime when packaging docker and running everything in node? |
|
@BrandonStudio ไปฅๅ่ฏ่ฟ๏ผ |
|
@arvinxx ๅจ dockerfile ้ๆๅ ไนๅๅ ไธๆญฅๆๆๆๆไปถ็export edge้ฝๅปๆ๏ผ่ฟๆ ทๅ็ๅ๏ผ |
@arvinxx Add a step to remove the export edges of all files in the dockerfile before packaging. Is this reasonable? |
|
@BrandonStudio ็่ฎบไธๅบ่ฏฅๅฏไปฅ |
@BrandonStudio In theory it should be possible |
### [Version 1.1.15](lobehub/lobe-chat@v1.1.14...v1.1.15) <sup>Released on **2024-06-28**</sup> #### ๐ Bug Fixes - **misc**: Pin `@azure/core-rest-pipeline@1.16.0` to fix azure openai issue. <br/> <details> <summary><kbd>Improvements and Fixes</kbd></summary> #### What's fixed * **misc**: Pin `@azure/core-rest-pipeline@1.16.0` to fix azure openai issue, closes [lobehub#3066](lobehub#3066) ([f3b29f6](lobehub@f3b29f6)) </details> <div align="right"> [](#readme-top) </div>
๐ป ๅๆด็ฑปๅ | Change Type
๐ ๅๆด่ฏดๆ | Description of Change
Lock @azure/core-rest-pipeline to 1.16.0. Workaround for #3037, #3053
๐ ่กฅๅ ไฟกๆฏ | Additional Information
This is just a workaround. We should switch backend environment to Nodecore reason:
@azure/openainot make the ege runtime as the official supported runtime: Azure/azure-sdk-for-js#30194 (comment)need to be fixed at azure side: Azure/azure-sdk-for-js#30194