8000 Number of components being deployed goes up and says 100% before it's finished · Issue #3312 · forcedotcom/cli · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Number of components being deployed goes up and says 100% before it's finished #3312
Closed
@geoffswift

Description

@geoffswift

Summary

Some times when deploying the count of items deployed exceeds the number expected...

See below, at first it says it's deploying 4048 components, then it changes its mind.

▶ Deploying Metadata…
   Components: 0/4048 (0%)
   Components: 1816/4048 (45%)
   Components: 2151/4048 (53%)
   Components: 2170/4048 (54%)
   Components: 2815/4048 (70%)
   Components: 2894/4048 (71%)
   Components: 2966/4048 (73%)
   Components: 2972/4048 (73%)
   Components: 4005/4048 (99%)
   Components: 4048/4048 (100%)
   Components: 4048/4048 (100%)
   Components: 4049/4048 (100%)
   Components: 4049/4049 (100%)
✔ Deploying Metadata (6m 33.86s)

Steps To Reproduce

I think I'm going to struggle to create a minimum reproduction here.

Expected result

I guess it should have said there were 4049 components in the first place. Additionally we should never see 100% while the deploy is still happening - because 100% would imply it's finished.

Actual result

See above

System Information

{
  "architecture": "darwin-arm64",
  "cliVersion": "@salesforce/cli/2.91.6",
  "nodeVersion": "node-v22.12.0",
  "osVersion": "Darwin 24.5.0",
  "rootPath": "node_modules/@salesforce/cli",
  "shell": "bash",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 3.2.29 (core)",
    "@oclif/plugin-commands 4.1.25 (core)",
    "@oclif/plugin-help 6.2.28 (core)",
    "@oclif/plugin-not-found 3.2.53 (core)",
    "@oclif/plugin-plugins 5.4.38 (core)",
    "@oclif/plugin-search 1.2.24 (core)",
    "@oclif/plugin-update 4.6.41 (core)",
    "@oclif/plugin-version 2.2.28 (core)",
    "@oclif/plugin-warn-if-update-available 3.1.40 (core)",
    "@oclif/plugin-which 3.2.35 (core)",
    "@salesforce/analytics 1.4.40 (link) /node_modules/@salesforce/analytics",
    "@salesforce/cli 2.91.6 (core)",
    "agent 1.22.8 (link) node_modules/@salesforce/plugin-agent",
    "apex 3.6.19 (core)",
    "api 1.3.3 (core)",
    "auth 3.6.124 (core)",
    "community 3.3.26 (link) node_modules/@salesforce/plugin-community",
    "data 4.0.36 (core)",
    "deploy-retrieve 3.22.17 (core)",
    "info 3.4.65 (core)",
    "lightning-dev 2.10.3 (link) node_modules/@salesforce/plugin-lightning-dev",
    "limits 3.3.55 (core)",
    "marketplace 1.3.8 (core)",
    "org 5.7.12 (core)",
    "packaging 2.9.5 (link) node_modules/@salesforce/plugin-packaging",
    "schema 3.3.64 (core)",
    "settings 2.4.29 (core)",
    "sobject 1.4.58 (core)",
    "telemetry 3.6.42 (core)",
    "templates 56.3.48 (core)",
    "trust 3.7.96 (core)",
    "user 3.6.24 (core)",
    "@salesforce/sfdx-scanner 4.10.0 (user) published 100 days ago (Tue Feb 25 2025) (latest is 4.12.0)"
  ]
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    investigatingWe're actively investigating this issuevalidatedVersion information for this issue has been validated

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0