Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Apps commands only accept relative path to app.yml

Open Beginner friendly
  • Is something wrong?
#6,910 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
go
Domain
cli

Research direction

Start at libs/apps/runlocal/spec.go around line 40, where the --entry-point path is combined with the app path. Reproduce with an absolute app.yml path and verify that the command starts successfully and prints the localhost URL instead of "no python file found".

Written by the indexing model from the issue text.

Description

CLI
Describe the issue

When running databricks apps run-local --entry-point <path> if the path is not relative, the app won't start and instead exit with Error: no python file found.

The problem is this line which just places the path passed with --entry-point after the app path (in my case the working directory):
https://github.com/databricks/cli/blob/419b912bb18dd06d6be2a657d7cef7cbb9e12932/libs/apps/runlocal/spec.go#L40

Steps to reproduce the behavior
  1. Run databricks apps run-local --entry-point <path> with an absolute path
  2. See error: Error: no python file found
Expected Behavior

The app starts with something like: To access your app go to http://localhost:8001

Actual Behavior

The app stops with: Error: no python file found

OS and CLI version

Databricks CLI v1.19.0
MacOS 26.3.1 (a) (25D771280a)

Is this a regression?

I'm not sure, this is the first time I encountered it

Debug Logs
23:06:25 Info: start pid=59821 version=1.19.0 args="databricks, apps, run-local, --entry-point, /var/folders/y5/****/app.yml, --log-level=debug"
23:06:25 Debug: Found bundle root at /Users/****/Projects/**** (file /Users/****/Projects/****/databricks.yml) pid=59821
23:06:25 Info: Phase: load pid=59821
23:06:25 Debug: Apply pid=59821 mutator=EntryPoint
23:06:25 Debug: Apply pid=59821 mutator=scripts.preinit
23:06:25 Debug: No script defined for preinit, skipping pid=59821 mutator=scripts.preinit
23:06:25 Debug: Apply pid=59821 mutator=ProcessRootIncludes
23:06:25 Debug: Apply pid=59821 mutator=VerifyCliVersion
23:06:25 Debug: Apply pid=59821 mutator=EnvironmentsToTargets
23:06:25 Debug: Apply pid=59821 mutator=ComputeIdToClusterId
23:06:25 Debug: Apply pid=59821 mutator=InitializeVariables
23:06:25 Debug: Apply pid=59821 mutator=DefineDefaultTarget(default)
23:06:25 Debug: Apply pid=59821 mutator=validate:no_variable_reference_in_resource_key
23:06:25 Debug: Apply pid=59821 mutator=validate:unique_resource_keys
23:06:25 Debug: Apply pid=59821 mutator=SelectDefaultTarget
23:06:25 Debug: Apply pid=59821 mutator=SelectDefaultTarget mutator=SelectTarget(dev)
Using profile: ****
23:06:27 Debug: Loading **** profile from /Users/****/.databrickscfg pid=59821 sdk=true
23:06:27 Debug: [Local Cache] using cache key: **** pid=59821
23:06:27 Debug: [Local Cache] cache hit pid=59821
23:06:27 Debug: Resolved cloud from hostname: "Azure" pid=59821 sdk=true
23:06:27 Debug: Resolved token_audience from host metadata token_federation_default_oidc_audiences: "https://adb-****.azuredatabricks.net/oidc/v1/token" pid=59821 sdk=true
23:06:27 Debug: Resolved discovery_url from host metadata: "https://adb-****.azuredatabricks.net/oidc/.well-known/oauth-authorization-server" pid=59821 sdk=true
Error: no python file found
23:06:27 Info: failed execution pid=59821 exit_code=1 error="no python file found"
23:06:27 Debug: no telemetry logs to upload pid=59821
Dominant language
Go
Stars
403
Forks
244
Avg merge
1d 13h
Merged PRs (30d)
263

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No 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.

More from databricks/cli

All issues in databricks/cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.