improve three debug messages#11908
Conversation
tool evaluation: for tools with many outputs its helpful to know which datasets and collections have been created. drmaa: for debugging its more convenient to see the command that could be copy pasted
c3278a6 to
7757006
Compare
lib/galaxy/tools/actions/__init__.py
Outdated
| return True # do not create this dataset | ||
| except Exception as e: | ||
| log.debug('Tool %s output %s: dataset output filter (%s) failed: %s' % (tool.id, output.name, filter.text, e)) | ||
| log.info(f'Tool {tool.id} output {output.name}: dataset output filter ({filter.text}) failed: {e}') |
There was a problem hiding this comment.
This should be at the debug level, that's going to spam the logs even if everything is alright. The log level for this module needs to be changed in planemo.
There was a problem hiding this comment.
Alright, then I revert this. Can you tell me an example when this is triggered and you do not want to see the message?
There was a problem hiding this comment.
There was a problem hiding this comment.
That's the rough idea, would be awesome if we can tune it there.
There was a problem hiding this comment.
Maybe like so: galaxyproject/planemo#1165
debug messages are not shown in planemo output where the message can be really helpful. Co-authored-by: David López <46503462+davelopez@users.noreply.github.com>
This reverts commit 140ca74.
99bce85 to
8f22fa5
Compare
one could also pass `log_level="warning"` but this swallows some useful messages at startup and shutdown, ie. ``` INFO: Started server process [1394761] INFO: Waiting for application startup. INFO: Application startup complete. INFO: Uvicorn running on http://127.0.0.1:8296 (Press CTRL+C to quit) ... INFO: Shutting down INFO: Waiting for application shutdown. INFO: Application shutdown complete. INFO: Finished server process [1394761] ```
| from uvicorn.server import Server | ||
| from uvicorn.config import Config | ||
| config = Config(app, host=host, port=int(port)) | ||
| config = Config(app, host=host, port=int(port), access_log=False) |
There was a problem hiding this comment.
Nice! But for Galaxy tests the access logs are useful sometimes. Maybe that could be controlled with an environment variable ? GALAXY_TEST_ACCESS_LOG ? Then planemo can set this but we keep the access logs in the CI.
There was a problem hiding this comment.
sure. is there an example where an env var is used somewhere in the code base?
There was a problem hiding this comment.
6d796f0 to
0167da6
Compare
|
Do you also have a tip where in Planemo I would set the environment variable? |
|
Is there some place in the docs where such environment variables are listed and explained? If not it might be good to add it somewhere? |
There's a somewhat complete listing in https://github.com/mvdbeek/galaxy/blob/926268ce6e1acd3db4e51ceb72e689899c545b9c/run_tests.sh#L181. |
Co-authored-by: Marius van den Beek <m.vandenbeek@gmail.com>
- fix and simplify reading of env variable - shorten doc Co-authored-by: Marius van den Beek <m.vandenbeek@gmail.com>
|
This PR was merged without a "kind/" label, please correct. |
What did you do?
Small change to
twothree (debug) messagesWhy did you make this change?
tool evaluation: for tools with many outputs its helpful to know which datasets and collections have been created.
drmaa: for debugging its more convenient to see the command that could be copy pasted
filter errors: debug is not shown in planemo output where it would be really helpful.
How to test the changes?
(select the most appropriate option; if the latter, provide steps for testing below)
License
For UI Components