slackapi / slackapi/slack-cli

slack create failed at step to get requirements to build editable

Open
#631 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area:bolt-python bug
Dominant language
Go
Stars
305
Forks
46
Avg merge
1d 11h
Merged PRs (30d)
23

Description

CLI Version

slack v4.6.0

Operating System

macOS 26.5.2

Description

This was the first attempt at creating an app, immediately after installing the slack CLI.

Steps to Reproduce

Run command:
slack create --template 'slack-samples/bolt-python-starter-template' --app 'A0BQ3KKMXL1' --name 'Deploy Orchestrator alpha16' --team 'T0Q4DP6DU' --environment local

Expected Result

Create app successfully.

Actual Result

All steps before this output, ran fine.
Here is the main output for the error:

     Installing build dependencies: started
     Installing build dependencies: finished with status 'done'
     Checking if build backend supports build_editable: started
     Checking if build backend supports build_editable: finished with status 'done'
     Getting requirements to build editable: started
     Getting requirements to build editable: finished with status 'error'

   Installed dependencies from requirements.txt

   Error: pip install failed: Error running 'InstallProjectDependencies' command: exit status 1 (sdk_hook_invocation_failed)
      error: subprocess-exited-with-error

        × Getting requirements to build editable did not run successfully.
        │ exit code: 1
        ╰─> [14 lines of output]
            error: Multiple top-level packages discovered in a flat-layout: ['assets', 'listeners'].

            To avoid accidental inclusion of unwanted files or directories,
            setuptools will not proceed with this build.

            If you are trying to create a single distribution with multiple packages
            on purpose, you should not rely on automatic discovery.
            Instead, consider the following options:

            1. set up custom discovery (`find` directive with `include` or `exclude`)
            2. use a `src-layout`
            3. explicitly set `py_modules` or `packages` with a list of names

            To find more information, look for "package discovery" on setuptools docs.
            [end of output]

        note: This error originates from a subprocess, and is likely not a problem with pip.

      [notice] A new release of pip is available: 25.0.1 -> 26.2.1
      [notice] To update, run: /Users/jnelson/dev/slack-app/deploy-orchestrator-alpha16/.venv/bin/python3 -m pip install --upgrade pip
      error: subprocess-exited-with-error

      × Getting requirements to build editable did not run successfully.
      │ exit code: 1
      ╰─> See above for output.

      note: This error originates from a subprocess, and is likely not a problem with pip.

   💡 Suggestion
      Run `slack doctor` to check that your system dependencies are up-to-date.


   Manually install project dependencies before proceeding with development

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure with the reported slack create command and inspect the generated project's requirements.txt and the slack-samples/bolt-python-starter-template setup. Confirm why setuptools discovers assets and listeners as top-level packages, then verify that creating the app completes successfully without the editable-build error.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, python
Domain
build-system, cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.