Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[BUG]: Bump @oclif/core from 4.14.0 -> 5.1.0 to resolve issue using --sfdx-url-stdin

Abierto Apto para principiantes
#3,657 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
72/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
node.js
Área
cli

Línea de trabajo

Comienza localizando la entrada de dependencia del proyecto para @oclif/core y revisa el punto de entrada indicado sf org login sfdx-url --sfdx-url-stdin. Reproduce el comando con stdin en un entorno similar a CI; se considera terminado cuando la sfdx-url se lee de forma consistente sin el timeout intermitente.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

investigating validated
Before You Submit
  • I'm using the latest version of Salesforce CLI
  • I've searched the existing issues
  • I've run sf doctor to diagnose common issues
Related Issue

https://github.com/forcedotcom/cli/issues/3647

Command

sf org login sfdx-url --sfdx-url-stdin

Org Type

Production

Did this work before?

No, this is a new bug

Last Working Version

No response

Summary

Issue originally reported in https://github.com/forcedotcom/cli/issues/3647 was due to issue with 3rd party package.

Issue has been fixed in https://github.com/oclif/core/releases/tag/5.1.0 that was causing sf org login sfdx-url --sfdx-url-stdin to intermittently fail in CI pipelines.

Repository to Reproduce

No response

Steps to reproduce
  1. Run sf org login sfdx-url --sfdx-url-stdin in CI pipeline
  2. Will intermittently fail due to hardcoded 10ms delay in @oclif/core
Expected Result

Should consistently read the sfdx-url from std without failing.

Actual Result

Intermittently fails as timeout reached before input is read

System Information
{
  "architecture": "win32-x64",
  "cliVersion": "@salesforce/cli/2.151.7",
  "nodeVersion": "node-v22.23.2",
  "osVersion": "Windows_NT 10.0.26200",
  "shell": "powershell",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 4.0.0 (core)",
    "@oclif/plugin-commands 5.0.0 (core)",
    "@oclif/plugin-help 7.0.0 (core)",
    "@oclif/plugin-not-found 4.0.0 (core)",
    "@oclif/plugin-plugins 6.0.0 (core)",
    "@oclif/plugin-search 2.0.0 (core)",
    "@oclif/plugin-update 5.0.0 (core)",
    "@oclif/plugin-version 3.0.0 (core)",
    "@oclif/plugin-warn-if-update-available 4.0.0 (core)",
    "@oclif/plugin-which 4.0.0 (core)",
    "@salesforce/cli 2.151.7 (core)",
    "agent 2.0.5 (core)",
    "apex 4.1.1 (core)",
    "api 2.0.9 (core)",
    "auth 5.0.6 (core)",
    "code-analyzer 5.15.0 (user) published 62 days ago (Wed Jul 29 2026) (latest is 5.16.0)",
    "data 5.1.7 (core)",
    "deploy-retrieve 4.2.0 (core)",
    "info 4.0.9 (core)",
    "limits 4.0.4 (core)",
    "marketplace 2.0.5 (core)",
    "org 6.0.11 (core)",
    "packaging 3.0.6 (core)",
    "schema 4.0.6 (core)",
    "settings 3.0.6 (core)",
    "sobject 2.0.5 (core)",
    "telemetry 4.0.6 (core)",
    "templates 57.1.0 (core)",
    "trust 4.0.10 (core)",
    "user 5.0.2 (core)"
  ]
}
Additional Information

Only breaking changes from version 4 -> 5

drop EOL Node versions
require Node >=22, drop EOL Node version

Screenshots or Log Files

No response

Lenguaje dominante
Sin datos de lenguaje
Estrellas
571
Forks
80
Merge medio
2 d 21 h
PR fusionados (30 d)
3

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de forcedotcom/cli

Todos los issues de forcedotcom/cli

Issues similares

Más issues de CLI

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.