Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Print output from errors coming from subprocesses in tiled serve config? #793

Open
pbeaucage opened this issue Oct 7, 2024 · 0 comments

Comments

@pbeaucage
Copy link
Contributor

pbeaucage commented Oct 7, 2024

While trying to serve an existing catalog from filesystem, I've noticed a few times that if an underlying call inside tiled serve config ... fails (for instance: tiled catalog init --if-not-exist), the details of that error don't bubble out to the console. Instead, you get a generic error from subprocess:

subprocess.CalledProcessError: Command 
'['/path/to/env/bin/python3.9', '-m', 'tiled', 'catalog', 'init', '--if-not-exists', 'catalog.db']' returned non-zero exit status 1.

A savvy user will know to run that command alone and find out that the SQLite catalog version doesn't match the local tiled version, but it save a debugging step (and potentially a confusing one for a novice user) if the stderr output from the subprocess call was printed to the console. Are there any downsides to doing this or issues it would cause?

@pbeaucage pbeaucage changed the title Print output from errors coming from subprocesses in tiled serve config Print output from errors coming from subprocesses in tiled serve config? Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant