PSGallery returning 504 and 500 Errors when publishing modules

Aberta
  • Algo errado?
#354 1 comentário 3 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
31/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
powershell
Domínio
cloud

Direção de pesquisa

Start by checking the PowerShell Gallery publishing service and its request or deployment logs for the reported 500 and 504 responses. The report names no repository files or tests, so first locate the publishing entry point and trace the request against the provided PowerShell 7.6.4 environment. Done means module publishing returns 200 and completes successfully; the issue does not identify a local reproduction or test.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Prerequisites
  • Write a descriptive title.
  • Make sure you are able to repro it on the latest version
  • Search the existing issues.
Steps to reproduce

Hello, I work for AWS on the .NET SDK and Powershell team and our Powershell module publishing is taking much longer than usual.

The publishing usually finishes under 5 minutes and it is currently over 2 hours and 20 minutes and still running. We are getting 504's and 500 back from PSGallery.

The error message we are getting for both is:
Response status code does not indicate success.

Can you guys look into what is going on?

Expected behavior
Publishing should return 200 and be successfull.
Actual behavior
Publishing a module is returning 500 and 504 errors
Gateway Time-out & Internal server Error.
Error details
`Response status code does not indicate success
Environment data
Name                           Value
--
----                           -----
PSVersion                      7.6.4
PSEdition                      Core
GitCommitId                    7.6.4
OS                             Ubuntu 22.04.5 LTS
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.4
SerializationVersion           1.1.0.1
WSManStackVersion              3.0
PSVersion                      7.6.4
PSEdition                      Core
GitCommitId                    7.6.4
OS                             Ubuntu 22.04.5 LTS
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.4
SerializationVersion           1.1.0.1
WSManStackVersion              3.0
Version

7.6.4

Visuals

No response

Linguagem predominante
PowerShell
Estrelas
289
Forks
83
Merge médio
1min
PRs com merge (30d)
1

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de PowerShell/PowerShellGallery

Todas as issues de PowerShell/PowerShellGallery

Issues semelhantes

Mais issues de Cloud

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.