New-WinGetSource fails to publish Azure Web App
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 45/100
Línea de trabajo
Comienza con la invocación de Publish-AzWebApp en el issue y reproduce el despliegue de New-WinGetSource con los parámetros mostrados. Comprueba el timeout y las alternativas de -Async, y verifica después que Azure Function recibe el archivo y que el despliegue se completa correctamente.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Brief description of your issue
I noticed the Microsoft.WinGet.RestSource just being released yesterday, so I was eager to try it out. When running the New-WinGetSource, it throws an error:
Steps to reproduce
Run New-WinGetSource -Name wingetsource -Verbose -InformationAction continue -ResourceGroup winget -SubscriptionName "<subscriptionName>" -ShowConnectionInstructions
Expected behavior
Deploys the WinGet source successfully.
Actual behavior
It fails uploading the .zip file to the Azure Function. This is because the default timeout is 10000 milliseconds, meaning 100 seconds. When attempting to manually upload the .zip file and set the timeout to 300 seconds, it succeeds.
The following line is responsible:
$DeployResult = Publish-AzWebApp -ArchivePath $RestSourcePath -ResourceGroupName $ResourceGroup -Name $FunctionName -Force -ErrorVariable DeployError
There are perhaps to possible solutions:
- Either increase the timeout
- Use the
-Asyncparameter
A small side note, instead of doing this:
Write-Information -MessageData "Publishing function files to the Azure Function."
$DeployResult = Publish-AzWebApp -ArchivePath $RestSourcePath -ResourceGroupName $ResourceGroup -Name $FunctionName -Force -ErrorVariable DeployError
## Verifies that no error occured when publishing the Function App
if ($DeployError -or !$DeployResult) {
$ErrReturnObject = @{
DeployError = $DeployError
DeployResult = $DeployResult
}
Write-Error "Failed to publishing the Function App. Error: $DeployError" -TargetObject $ErrReturnObject
return $false
}
## Restart the Function App
Write-Verbose "Restarting Azure Function."
if (!$(Restart-AzFunctionApp -Name $FunctionName -ResourceGroupName $ResourceGroup -Force -PassThru)) {
Write-Error "Failed to restart Function App. Name: $FunctionName"
return $false
}
You might shorten it to:
Write-Information -MessageData "Publishing function files to the Azure Function."
$DeployResult = Publish-AzWebApp -ArchivePath $RestSourcePath -ResourceGroupName $ResourceGroup -Name $FunctionName -Force -ErrorVariable DeployError -Restart # <-- Use restart right away
## Verifies that no error occured when publishing the Function App
if ($DeployError -or !$DeployResult) {
$ErrReturnObject = @{
DeployError = $DeployError
DeployResult = $DeployResult
}
Write-Error "Failed to publishing the Function App. Error: $DeployError" -TargetObject $ErrReturnObject
return $false
}
Environment
Windows Package Manager v1.9.25200
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.26100.2033
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.24.25200.0
Winget Directories
-----------------------------------------------------------------------------------------------------------------------
Logs %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\Diag…
User Settings %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\sett…
Portable Links Directory (User) %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User) %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root C:\Program Files\WinGet\Packages
Portable Package Root (x86) C:\Program Files (x86)\WinGet\Packages
Installer Downloads %USERPROFILE%\Downloads
Links
---------------------------------------------------------------------------
Privacy Statement https://aka.ms/winget-privacy
License Agreement https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale
Admin Setting State
--------------------------------------------------
LocalManifestFiles Disabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride Disabled
LocalArchiveMalwareScanOverride Disabled
ProxyCommandLineOptions Disabled
DefaultProxy Disabled
- Lenguaje dominante
- C#
- Estrellas
- 317
- Forks
- 79
- Merge medio
- 12 h 22 min
- PR fusionados (30 d)
- 3
Preparar el entorno
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de microsoft/winget-cli-restsource
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
-
Issue-Feature
Dificultad 4/5 3-5 días Aptitud para principiantes 55/100
-
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
-
Font SupportQuizá libre de nuevo @dkbennett la tomó hace 279 días y no hay ningún pull request abierto. AbiertoIssue-Feature
microsoft/winget-cli-restsource#310 · 1 comentario · 1 asignado ·
-
Issue Deploying in GCC-HAbiertoIssue-Bug
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
microsoft/winget-cli-restsource#309 · 2 comentarios ·
Todos los issues de microsoft/winget-cli-restsource
Issues similares
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
fluentassertions/fluentassertions#3353 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
Dificultad 2/5 Medio día Aptitud para principiantes 78/100
unoplatform/uno#24769 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
AvaloniaUI/Avalonia#22323 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
microsoft/onnxruntime-genai#2633 ·
Los mantenedores suelen responder en 1 día